Managing Oracle GLAS (Global License Advisory Services) exports

Data Collection

1. Scan all systems with the data collection script (refer to Running the scripts on Unix/Linux, Running the scripts on Windows,  Collecting data from Oracle databases  and Collecting data for Java installations for details).
2. Assure that all systems and databases have been inventoried.
3. Check completeness of data:

• Go to the Systems navigation item and check essential data for systems, such as the host-VM relation and the Max Sockets value are present for virtual machines. To obtain the missing data, run the "M42DataCollection" script on hosts (like for eg. a Solaris global Zone), and/or run the data providers for VMware, Hyper-V and Citrix inventory.
• Go to the Database Products navigation item and check for completeness and check the values in the Instance State and DB Mode columns.

4. For the Databases: some data has to be added manually using the Database Instance edit dialogue. Verify that no crucial data is missing. For the Database Instances the fields that need to be checked and edited are:

• License Metric in the  Specific section of the General tab of the Oracle Database Instance dialog. Check if the metric is correctly set. If the Database is not licensed by Processor (CPU) Metric (default setting),  then use the the Change License Metric action to set it accordingly.
• Licensed Database Edition and Environment Usage under the Additional Information for Oracle GLAS section on the General tab of the Oracle Database Instance dialog.
  Licensed Database Edition should not to be confused with the installed edition. The field Licensed Database Edition represents the edition used to license this server. The installed Edition represents what has been installed and detected using the DataCollection. The installed Edition is set as a the pre-configured value for the Licensed Edition.

• The Environment Usage field represents the type/purpose of the environment where the Oracle product is deployed (e.g., Prod, Dev, Test, etc). Default value is Prod.

5. For Java Installations: some data has to be manually edited after the GLAS Java-Report is being exported, please refer to step 10).

Data Masking (optional)

6. Decide if data masking is necessary.  By default the data masking is off. It means that the generated Oracle GLAS exports will contain user names and IP addresses. To avoid this, go to the Settings navigation item in the Oracle Compliance app and select the Enable Data Masking checkbox.

File Generation

7. Run the Oracle Database Compliance - Oracle GLAS Export Files Generator engine activation via Administration > Services & Processes > Engine Activations to generate the Oracle GLAS Export files. This will generate all required files for the systems, databases, Java installations, Oracle Fusion Middleware products as well as the VMware.
8. Download Oracle GLAS Export files from the Home > Oracle GLAS Export Files dashboard. 
   • When only Java data is required, download all files in the "Oracle GLAS Java Export Files" section.
   • When only Database data is required, download all files in the "Oracle GLAS Database Export Files" section.
   • When only Oracle Fusion Middleware data is required, download all files in the "Oracle GLAS Fusion Middleware Export Files" section.
   • When Database, Java and Oracle Fusion Middleware data is required, download all files in the "All Oracle GLAS Export Files" section.

Finalization

9. For Oracle Java, please review the csv in the 3PTV_JAVAReport_<date>.zip file and update the info regarding the following columns accordingly with your current usage and needs:
   • Machine Type: Server (S) or Desktop (D). The solution will automatically determine the type based on Operating system, Virtualization and other criteria.
   • Environment Type: If the environment is not set on the Computer level, then the solution will use "Prod" as a default value
   • Used with OCI: Y if it's included in an OCI subscription, N otherwise
   • Part of other product: Y if it's included in other Oracle Product license, N otherwise
   • Support required: Y if the customer requested Oracle Support, N otherwise
   • OTN: Y if under the Oracle Technology Network (OTN) license agreement, N otherwise
   • BCL: Y if under the Binary Code License (BCL) development license grant, N otherwise
   • NFTC: Y if under the No-Fee Terms and Conditions (NFTC), N otherwise
   • BLRA: Y if under the Binary License and Redistribution Agreement (BLRA), N otherwise