Oracle GLAS data collection using patterns

  • Release version: Australia
  • Updated June 4, 2026
  • 10 minutes to read

    • The ServiceNow Discovery application uses the Oracle GLAS Data Collection pattern extensions to discover Oracle GLAS data. This data includes discovered Oracle Database, Middleware, and Java configuration items.

    Oracle GLAS Data Collection patterns are extensions of the following patterns:
    • Oracle Database on UNIX and Windows patterns
    • Oracle Middleware on Linux for the following patterns:
      • Oracle Tuxedo
      • WebLogic
      • Linux
    • Oracle Java on Java installation pattern

    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

    Install the Data Collection for Oracle Global Licensing and Advisory Services store app
    Navigate to System Definition > Plugins and install the Data Collection for Oracle Global Licensing and Advisory Services app.
    • The minimum version for Database collection is 1.4.0
    • The minimum version for Middleware collection is 1.7.1
    • The minimum version for Java collection is 1.8.4
    Note:
    The Data Collection for Oracle Global Licensing and Advisory Services app requires the Discovery (com.snc.discovery) plugin to work correctly.
    Verify the following applications are installed
    • Discovery and Service Mapping Patterns
    • CMDB CI Class Models
    Verify operating system privileges
    Verify that your Windows or UNIX user can write temporary files under /tmp.
    Verify that you can run the following operating system commands:
    • ls
    • cat
    • ps
    Create operating system credentials
    Verify that you have the following credentials for your operating system, and then create credentials for them on the ServiceNow AI Platform:
    • UNIX credentials using SSH. For more information, see SSH credentials.
    • Windows credentials using PowerShell/WMI. For more information, see Windows credentials.
      Note:
      PowerShell and WMI credentials are required only for Database collection.
    Verify the following Oracle privileges
    Verify that you have applicative credentials for the Oracle instance (cmdb_ci_db_ora_instance) that have the following privileges:
    • Read permissions on the tnsnames.ora file.
    • Permissions to execute the sqlplus command.
    • (For middleware collection) Sudo permissions to run the following command: sudo su - oracle -c "$ORACLE_INSTANCE/bin/opmnctl status"

    Verify you have the user name and password for the relevant Oracle Database, with read permissions on the following tables.

    DBA_ADVISOR_TASKS DBA_USERS SYS.MODEL$
    DBA_CPU_USAGE_STATISTICS DMSYS.DM$MODEL SYS.REGISTRY$HISTORY
    DBA_ENCRYPTED_COLUMNS DMSYS.DM$OBJECT SYSMAN.MGMT_INV_CONTAINER
    DBA_FEATURE_USAGE_STATISTICS DMSYS.DM$P_MODEL SYSMAN.MGMT_LICENSES
    DBA_FLASHBACK_ARCHIVE_TABLES DVSYS.DBA_DV_REALM SYSMAN.MGMT_LICENSE_DEFINITIONS
    DBA_INDEXES GV$IM_SEGMENTS SYSMAN.MGMT_TARGETS
    DBA_LOBS GV$INSTANCE SYSMAN.MGMT_VERSIONS
    DBA_LOB_PARTITIONS GV$PARAMETER V$ARCHIVE_DEST_STATUS
    DBA_LOB_SUBPARTITIONS MDSYS.SDO_FEATURE_USAGE V$BLOCK_CHANGE_TRACKING
    DBA_OBJECTS MDSYS.SDO_GEOM_METADATA_TABLE V$CONTAINERS
    DBA_RECYCLEBIN MGMT$TARGET V$DATABASE
    DBA_REGISTRY ODM.ODM_MINING_MODEL V$DATAGUARD_CONFIG
    DBA_SQLSET ODM_DOCUMENT V$LICENSE
    DBA_SQLSET_REFERENCES ODM_RECORD V$OPTION
    DBA_SQL_PROFILES REDACTION_POLICIES V$PARAMETER
    DBA_TABLES SCHEMA_VERSION_REGISTRY V$SESSION
    DBA_TABLESPACES SYS.CDC_CHANGE_SETS$ V$VERSION
    DBA_TAB_PARTITIONS SYS.CDC_CHANGE_TABLES$ dba_aws
    DBA_TAB_SUBPARTITIONS SYS.DBA_MINING_MODELS
    Create applicative credentials for Oracle Instance
    Create applicative credentials on the ServiceNow AI Platform. For more information, see Applicative credentials.
    For UNIX: You can use Oracle Wallet authentication instead of applicative credentials
    For more information, see Enable Oracle Wallet authentication for discovery.
    For virtual machines: Verify virtual machine credentials
    For virtual machines, verify you have the relevant credentials to collect hardware data for machines hosted on the following virtual providers:
    • VMware
    • Nutanix
    • IBM
    • Hyper-V
    For virtual machines: Collect hardware data
    To populate the CPUQ folder in your GLAS report download, run the Oracle-provided hardware script on each target virtual machine. The following table lists the required script and credentials for each operating system.
    Operating system Script Required credentials
    Windows cpuq.cmd Username and password
    Linux or UNIX cpuq.sh Root username and password
    Access to the operating system command line is required. Use Command Prompt on Windows systems and a UNIX Shell on Linux or UNIX systems.
    1. Log in to the target virtual machine using the required credentials.
    2. Open the command-line interface for the operating system.
    3. Run the hardware script for the operating system.
    4. Repeat for each target virtual machine.
    For large-scale or high-volume environments: You can enable Oracle GLAS V2 data collection
    To use V2 database data collection instead of the default V1 method, set the sn_itom_pattern.enable_large_env_glas_data_collection system property to true. For more information about V2, see the "Oracle GLAS Data Collection V2" section. For instructions, see Enable the Oracle GLAS V2 data collection method.

    V1 database CI relationships

    CI Relationship/Reference CI
    ORCL V SESSION [cmdb_ci_orcl_vsession] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]
    ORCL DETAIL [cmdb_ci_ora_lms_detail] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]
    ORCL OVERVIEW [cmdb_ci_ora_lms_overview] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]
    ORCL OPTIONS [cmdb_ci_orcl_options] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]
    ORCL DBA USERS [cmdb_ci_orcl_dba_users] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]
    ORCL V LICENSE [cmdb_ci_orcl_vlicense] Contains::Contained by Oracle Instance [cmdb_ci_db_ora_instance]

    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:

    Table 1. Oracle GLAS Database Audit Data [sn_itom_oracleglas_glas_data_for_database]
    Field Description
    Host Name [hostname] Host name of the server running the Oracle instance.
    DB Name [dbname] Name of the Oracle database.
    Type [type] Identifies the type of GLAS data stored in the record. Possible values:
    • ORCL_OVERVIEW
    • ORCL_DETAILS
    • ORCL_LICENSE
    • ORCL_SESSION
    • ORCL_OPTIONS
    • ORCL_DBA_USERS
    Order [order] Sequential order of the record. If the content for a type exceeds 10 megabytes (MB), it is stored in multiple records ordered sequentially starting from 0.
    Content [content] Collected GLAS data for the record type. Maximum size is 10 MB per record.
    Oracle Instance [oracle_instance] References the Oracle Instance [cmdb_ci_db_ora_instance] 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

    Tuxedo license configuration and log files collected:
    • *_InstallLog.log
    • *ubbc*
    • bdmconfig*
    • comps.xml
    • dmconfig*
    • JSconfig.xml
    • lic.txt
    • registry.xml
    • tuxconfig*
    • tuxwsvr.ini
    Note:
    The asterisk represents one or more characters in the file name.
    Processes collected:
    • BBL
    • DBBL
    • GWWS
    • JSH
    • JSL
    • TMJAVASVR
    • TMMETADATA

    WebLogic middleware extension

    Files collected:
    • beahomelist
    • biee-domain.xml
    • cluster.properties
    • comps.xml
    • config.xml
    • domain-registry.xml
    • opmn.xml
    • portalconfig.xml
    • pthome.xml
    • registry.xml
    • server.xml
    • sessions.xml
    • setupinfo.txt
    WebLogic processes and files collected for the following middleware products:
    • WebLogic
    • OAS
    • SOA
    • OBI
    • WebCenter
    • FormsReports
    Table 2. Processes
    WebLogic OAS OBI
    startWebLogic httpd f90 iooomgrrmi r30rbe32 rwrqm60 nqsserver
    java apache frmweb javaw r30rqm32 rwrqm sawserver
    startWLS java ifbld60 java r30run32 rwrun60 coreapplication_obijh1
    nodemanager opmn ifbld90 jre r30sxc32 rwserver nqscheduler
    beasvc dis3 ifcgi60 oad r30sxu32 rwsxc60 nqsclustercontroller
    beasvc64 dis4 ifcmp60 odisrv rwbld60 rwsxu60 essbase
    beasvcX64 dis51pr ifcmp90 ofcguard rwbuilder vdeserver essvr
    oraclesvc dis51ws ifctrl60 oidrepld rwcgi60 webcachea essbasestudio
    opmn dis51 ifdbg60 oidmon rwcli60 webcached hyperion
    wlsvc dwfde61 ifrun60 oidldapd rwcon60 webcache
    wlsvc64 f45des ifsrv60 opmn rwconverter
    wlsvcX64 f45run ifwdb60 r30cli32 rwisv60
    jmc f50dbg32 ifweb60 r30con32 rwmts60
    httpd f50run32 ifweb90 r30isv32 rwqmu60
    jrmc f60 imapds r30qmu32 rwrbe60

    Middleware CI relationships

    CI Relationship/Reference CI
    cmdb_ci_ora_lms_overview Contains::Contained by cmdb_ci_linux_server
    cmdb_ci_config_file_tracked Contains::Contained by cmdb_ci_linux_server

    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

    To access the installed application properties, navigate to All > System Properties > All Properties. You must have the admin role to modify these properties.
    System property Default value Description
    sn_itom_oracleglas.isMaskingIp true Determines whether to mask the IP Address in Oracle middleware tracked files by replacing the value with "text_removed."
    sn_itom_oracleglas.isMaskingUserName true Determines whether to mask the user name in Oracle middleware tracked files by replacing the value with "text_removed."
    sn_itom_oracleglas.isMaskingPort true Determines whether to mask the port in Oracle middleware tracked files by replacing the value with "text_removed."

    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.

    Note:
    In Data Collection for Oracle Global Licensing and Advisory Services versions earlier than 1.10.2, the property name is sn_itom_pattern.disable_glas_data_collection.

    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.