The Oracle Database and Middleware patterns execute the pattern extensions, and the data collected is stored in the ServiceNow tables for GLAS data.

For details on how to view and download the collected Oracle GLAS data, see Download Oracle Global License Advisory Services (GLAS) data.

To learn about the supported versions of Oracle, refer to Detailed information on products discovered by ITOM Visibility.

The Data Collection for Oracle Global Licensing and Advisory Services application supports two database data collection methods. The default method, V1, stores data across six CMDB CI tables. V2, available starting with Data Collection for Oracle Global Licensing and Advisory Services version 1.12.0, is an alternative method optimized for large-scale or high-volume Oracle database environments that consolidates data into a single non-CMDB table. For more information about V2, see the "Oracle GLAS Data Collection V2" section.

Request apps on the Store

Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

Prerequisites

V1 database CI relationships

Oracle GLAS Data Collection V2

Oracle GLAS Data Collection V2 is an alternative database data collection method that uses the Oracle GLAS Data Collection V2 pattern extension. V2 optimizes database data collection for large-scale or high-volume Oracle database environments. The V2 method applies to database data collection only; middleware and Java data collection aren't affected.

In V2, the MID Server collects data from the Oracle GLAS scripts and uses the GlideRecord API to populate the Oracle GLAS Database Audit Data [sn_itom_oracleglas_glas_data_for_database] table directly. As a result, GLAS data appears in the Content field and not in the discovery payload. To verify data population, navigate to the Oracle GLAS Database Audit Data table and review the Content field. If data is missing or incomplete, see MID Server ECC Queue for information about accessing MID Server logs.

V2 stores all database GLAS data in the Oracle GLAS Database Audit Data table. Each record directly references the Oracle Instance [cmdb_ci_db_ora_instance] table; in V1, this association is established through a CI relationship (see the "V1 database CI relationships" section).

The Oracle GLAS Data Collection V2 pattern extension populates the following fields in the Oracle GLAS Database Audit Data table:

When V2 is enabled, the navigation menu updates automatically, hiding the six V1 database modules and displaying the GLAS V2 - Databases module. To enable V2 data collection, see Enable the Oracle GLAS V2 data collection method.

Tuxedo middleware extension

WebLogic middleware extension

Middleware CI relationships

These relationships are created by a containment rule that describes the valid objects that the Linux CIs can contain.

Properties installed with the Middleware data collection application

Control GLAS data collection

The following MID Server property controls the GLAS data collection: sn_itom_oracleglas.disable_glas_data_collection

The property is set to False by default.

Oracle Java process discovery

ITOM Visibility can discover Java-running processes in your infrastructure, allowing you to comply with Oracle licensing agreements and prepare for GLAS Audits. You can perform the discovery using the Java Installation pattern (IP-based), Agent Client Collector with application patterns, or Agent Client Collector with file-based discovery.

In the pattern flow, the Java processes are discovered by Application Dependency Mapping (ADM). When the processes are discovered, the Java Installation pattern triggers and collects the data.

For information about privileged user access, see KB1705845.

For more information about Agent Client Collector with patterns, see Application patterns for the Agent Client Collector.

For more information about Agent Client Collector with file-based discovery, see Discover java installation data using Agent Client Collector for Visibility - Content file-based discovery.

Data collected

Table 3. Java Audit [ora_java_audit]

Field	Description
Name	Name of the record. For example: Java@hostname
Physical Machine Name	Name of the host CI
Machine Type	Either Server(S) or Desktop(D)
Java Publisher/Runtime Vendor	Java Vendor name
Operating System	Operating system in which the java is run
Environment Type	Production or Development or QA environment
Java Release/Version/Build	Java Version
Installation Path	Absolute installation path of the java binary
Installation Date (DateTime)	The date and time of the java binary file created on the filesystem
Release File (Y / N)	Indicates if a release.md file exists in the installation
Processor Make/Model	Processor model name
Sockets (Integer)	Number of CPU sockets
Cores (Integer)	Number of CPU cores
V6 and earlier	Indicates if you have a 6 or earlier java version
Open Source	Indicates if you have an open-source java installation
Unlock Commercial features	Indicates if you have the commercial features (like JFR) enabled
Mission Control	Indicates if the mission control plugin is enabled
AMC Agent	Indicates if the AMC agent plugin is enabled
Usage Tracker	Indicates if the Usage Tracker feature is enabled
Virtual Machine Object ID	Object ID of the Virtual machine instance
PID	Running process PID
IP Address	IP address of the host/VM
First Discovered	The date of the first discovery
Most recent discovery	The date of the most recent discovery
Discovery Source	The discovery method.
Application	Reference to the [cmdb_ci_appl] table
Software installation	Reference to the [cmdb_sam_sw_install] table
Java evidence	Reference to the [cmdb_ora_java_evidence] table
Host	Reference to the [cmdb_ci] table

Java Evidence [ora_java_evidence]

Field	Description
Running process	Reference to the [cmdb_running_process] table
Host CI	Reference to the [cmdb_ci_computer] table
File information	Provides a reference to the [cmdb_file_information] table. Relevant only for file-based discovery (FBD); in pattern-based discovery, this field remains empty.

Download the Oracle GLAS report in the Discovery Admin Workspace. For more information, see Download Oracle Global License Advisory Services (GLAS) data.

Oracle GLAS Data Collection

After Discovery finishes discovering the components of your database or middleware deployment, you can view the relevant statistics in the Oracle GLAS Data Collection.

After upgrading to Discovery Admin Workspace version 1.3.1 (August 2024 Store), you can navigate to Workspaces > Discovery Admin Workspace > Insights to view and access the Oracle GLAS Data Collection.