WebLogic Edition Recognition

[AAlbert1]

An enhancement for WebLogic edition recognition is planned for June 02nd ARL.

The goal is to better recognize the editions and decrease the risk of false positives coming from Oracle Universal Installer (OUI) and BEA installer evidence.

The approach is that every time the Flexera Agent will have performed a middleware scan, the OUI or BEA evidence will be ignored because the agent data will be of better quality.

• A new “Unspecified (FMW)” edition (FMW -Fusion Middleware) will be created for WebLogic Server, positioned above Unspecified (renamed Unspecified (OUI & BEA))
• A new Flexera “Oracle FMW Recognition” application will be created and recognized when the Flexera agent has run the middleware scan.
• New precedence rules will be created that will remove the Unspecified (OUI & BEA) every time the “Oracle FMW Recognition” application has been reported on a device.

The implementation has multiple dimensions, but the goal is simple: the WebLogic Unspecified (OUI & BEA) application that sometimes turns out to be a false positive will be deleted every time a “better edition” has been found or every time the agent has performed an FMW scan and has found no WebLogic installation.

[PrasadAmin]

Hi all, 
These changes are part of the ARL #2747 build.
https://community.flexera.com/t5/FlexNet-Manager-Content-Blog/FlexNet-Manager-Update-Application-Recognition-Library-2747-and/ba-p/278999

Thanks,
Team Content

[avi0408]

Hello @PrasadAmin 

After ARL #2747 release , we still see that Weblogic Server And Coherence editions are missing.

Do we need to upgrade the agent to latest version?

Thanks,

Awadh

[nrousseau1]

Hello,

Please find some guidance and explanations of WebLogic editions recognitions

• The 2021R1 version released in June 2021 became "Middleware verified", which means it can collect middleware evidence for the GLAS file. Note that to collect the data, you need to set in the Discovery and Inventory / inventory settings the Middleware data collection.

  

• If you want the data to be in the GLAS file, you need also to mention it in the System Settings / Inventory

•  Then, later, in 2022R1, GLAS evidences have been used to recognize the editions of WebLogic. The backend process for import and recognition has been modified to allow the recognition. This means the FNMS must be of at least version 2022R1 and the agent of 2021R1 to recognized the editions of WebLogic.
• Finally, in June 2023,
  • The ARL has been modified last week to add a mechanism to remove OUI & BEA false positives.
  • This change came with another change in the Inventory Import logic to "fabricate" a "I have been scanned by the Oracle Middleware script" (named actually "Oracle FMW Recognition") evidences and application that allow to remove the OUI recognition with precedence rule.

To take advantage of the "remove false positives", you need a 2021R1 or later agent, 2747 build, and be in ITAM (or wait for 2023R1 on-premises to get the change in import é recognition).
If you see no editions of WebLogic (which seems to be the case), check

• That you use the 2021R1+ agent
• That the data collection is activated for Oracle Middleware
• That your version of FNMS is 2022R1 or later

If you see editions but see false positives:

• If you are on premise,
  • Migrate to FNMS 2023R1 that brings a lot (SAM Operations Hub and related reports, Oracle Java Worksheet).
  • You can also ask a to customer Support a hot fix that will allow to implement the backend changes to 

If you are Cloud, it worth investigating further.

• Check that the "Oracle FMW Recognition" application is recognized and never co-located with a WebLogic Server Unspecified (OUI & BEA) installation.

Best regards,

Nicolas Rousseau

Principal Product Manager

Flexera - ITAM

[nrousseau1]

Coherence is not (yet) enhanced for recognition.