FNM Update: Application Recognition Library #2433 and Service Life Data Pack #282 are available

0 6 1,802

The Application Recognition Library (ARL), as used by FlexNet Manager, has been updated. The updated version for the ARL is #2433.

The Service Life Data Pack has been updated to version #282.


What's new in this release

 Changes to note:

  • 25 commercial applications have been added with lifecycle dates.

Count of new applications added:

Publisher Number of Applications
Oracle 141
Red Hat 79
IBM 27
Microsoft 18
Tableau Software 13
Kaspersky Lab 6
CA Technologies 6
TIBCO Software 5
VMware 5
TransVault 4
21 other publishers 34
Total 338


Current Library Totals:

  • Number of applications in ARL: 284,221 across 17,394 publishers.
  • Number of evidence recognition rules: 971,219
    • Installer evidence rules: 635,501
    • File evidence rules: 334,085
    • WMI evidence rules: 1,274
    • Application suite evidence rules: 359
  • Number of commercial applications with service life dates: 32,227


Details of changes in the ARL

You can inspect changes made in this ARL release as per the following links:


Updating library data

FlexNet Manager Cloud: These updates are expected to be installed prior to Monday, July 01, 2019.

FlexNet Manager On-premises: This library release will be applied to your FlexNet Manager according to schedule settings and processes configured for your instance. If your environment requires to you manually download and update library data, see the following article for guidance: Downloading the FlexNet Manager Suite Content libraries manually.

You can inspect the versions of currently installed libraries using the system Menu > System Health > System Health Dashboard menu option in FlexNet Manager.

Upcoming ARL and Service Life Data Pack updates: We nominally expect the next ARL and Service Life Data Pack updates to be published on or around Thursday, July 04, 2019.


Reporting issues with ARL and SLDP updates

Should you have any issues related to FlexNet Manager library data, please submit a case by logging in to the Flexera Community and then select the Get Support > Open new case menu option.

We are interested in feedback on these announcements. If you have any questions or suggestions for improvements, please comment below.

We trust that you will find this update helpful and look forward to continually improving your application recognition results.


Flexera Content Team

Frequent contributor

Have any members had issues with this update?  I am experiencing issues with recognition of  Oracle Database 11g R1 Enterprise immediately after this ARL update.  Sudden spike in recognition numbers, and devices consume directly against licenses without the need for Oracle DB introspection

Community Manager Community Manager
Community Manager

@Nico_Erasmus - good observation. This does appear to be a problem in this ARL update. I expect somebody who works on ARL will be looking at this and a new ARL release will be published in due course. In the meantime you could try setting the Minimum installations for suite recognition value on the affected applications to 20 to see if that helps (thanks @spierce for the tip!):


If you find that this change does help, please post here to confirm.

See the following post for more information: Error in Application Recognition Library (ARL) #2433 affecting some Oracle applications

Frequent contributor

Thanks Chris and Stuart.  

Happy to apply a work around.  The application is not part of a suite and that configuration change should not have been made.


Is it the suite recognition that bypasses the need to DB introspection in the reconciliation process?

Community Manager Community Manager
Community Manager

@Nico_Erasmus - I’m not sure I understand your question about introspection and recognition, but I think you’re right that these applications should not be configured as suites.

Frequent contributor


When it comes to Oracle Enterprise and related options and management packs,  the recognition of  the raw application only results in a change to the Unlicensed Installation report.  The applications are removed from the unlicensed installations report,when our agent (or other means of executing the LMS scripts) interrogates the databases present on a device to confirm a database instance is in fact running - only a running DB instance requires a license; for options, the options must be confirmed as in use by the DB instance.

Community Manager Community Manager
Community Manager

@Nico_Erasmus - yes, symptoms of the problem you have described here in relation to database options are consistent with the problem in this ARL release.