1. Open the terminal in your Linux machine and change the directory to the path of the OAS jar file.

   cd <patch of OAS jar file>

2. Run the following command to launch the OAS installation process:

   java -jar Oracle_Analytics_Server_Linux_6.4.0.jar

1. Click Next on the Welcome screen.

2. Select Skip Auto Updates and click Next.

3. Click on Browse and select Oracle Home (which has FMW 12.2.1.4 installation).

4. Click on Open and click Next.

5. Once the Prerequisite Checks for verifying the installation environment are complete, click on Next.

6. Click on Install.

7. Once the Installation is complete, click on Next and then click on Finish.

1. Navigate to $ORACLE_HOME/oracle_common/bin.

2. Run the ./rcu command to initiate the repository creation process.

3. Select Create Repository, then System Load and Product Load.

4. Add the database details and click on Next.

5. Add a prefix (OASTEST in this case) and select Oracle Business Intelligence. Then click on Next.

6. Click on Next in Map Tablespaces.

7. Click on Create.

8. After the repository is created, click on Finish.

1. Navigate to the directory $ORACLE_HOME/bi/bin.

2. Run the following command: ./config.sh.

3. Click Next on the Welcome screen.

4. Select Oracle Analytics Server and Oracle Analytics Publisher and click on Next.

5. After all the Prerequisite Checks are done, click Next.

6. Add a Unique Domain Name and add Username, Password for login to OAS. Click Next.

7. Click on Use Existing Schemas.

8. Add the database details and RCU details that were created in step 6 and click Next.

9. Add an available port. If the default ports (9500-9999) are not available, click Next.

10. Select Clean Installation (selected by default) and click Next.

11. Click on Save Response file for future reference and click Configure.

12. Once the configuration is successful, click on Next and then click Finish.

The Scan History Report shows the discovery and discrepancy summaries for each scan for each scan configuration falling within the specified start and end dates. This report is accompanied by the following graphs:

• Discovery Scan History: A graph showing a history of the run discovery scans.

• Discrepancy Scan History: A graph showing a history of the run discrepancy scans.

• Discrepancy Severity History: A graph showing a history of the discrepancies by severity.

The following fields are used to generate this report:

• Start Time: the date stamp indicating when a scan started.

• End Time: the date stamp indicating when a scan finished.

The Discovery Scan Summary Report shows the summary of the latest scan for each scan configuration, per vendor and per device type. This report generates a pie-chart, illustrating the summary findings, for each scan configuration.

The following fields are used to generate this report:

• Vendor: The name of the vendor for the discovered device.

• Device Type: The type of device discovered.

The Device Discrepancy Detection Summary Report shows the summary of the latest scan for each scan configuration. This report generates a pie-chart that shows the accuracy of the latest scans for each scan configuration.

The following fields are used to generate this report:

• Vendor: The name of the vendor for the discovered device.
• Device Type: The type of device discovered.

The Device Discrepancy Detection Detail Report lists details of all discrepancies for the latest scan for each scan configuration.

The following fields are used to generate this report:

• Vendor: The name of the vendor for the discovered device.

• Root device name: The name of the root device in the scan result tree.

• Root device type: The type of the root device in the scan result tree.

• Owner: The user name of the owner of the discrepancy.

• Parent entity type: The type of the parent entity on which discrepancy occurred.

• Parent entity name: The name of the parent entity on which discrepancy occurred.

• Entity type: The type of the entity on which discrepancy occurred.

• Inventory value: The value of the field on the inventory side on which discrepancy occurred.

• Network value: The value of the field on the network side on which discrepancy occurred.

• Severity: The severity of the discrepancy (for example, major, critical, minor, warning).

• Discrepancy type: The type discrepancy (for example, entity+, entity-, attribute).

• Description: The description of the discrepancy.

• Status: The status of the discrepancy (for example, processed, failed, ignored).

• Scan name: The name of the scan in which the discrepancy is found.

The Discrepancy Corrective Action Report shows corrective actions against specified discrepancies for the latest scan for each scan configuration. Discrepancies against which no actions are taken are not considered in this report.

The following fields are used to generate this report:

• Submitted By: The user who submitted the discrepancy for correction.

• Action: The action taken against the discrepancy.

• Discrepancy Status: Status of the discrepancy.

• Owner: The user name of the owner of the discrepancy.

• Priority: The priority of the discrepancy.

• Failure Reason: The reason for failure for the corrected discrepancy.

• Discrepancy Type: The type discrepancy (for example, entity+, entity-, attribute).

• Entity Type: The type of the entity on which discrepancy occurred.

• Inventory Value: The value of the field on the inventory side on which discrepancy occurred.

• Network Value: The value of the field on the network side on which discrepancy occurred.

1. Select Data Model folder and click on Upload.

2. Select the files inside Data Models folder ending with .xdmz extension.

3. Click on Upload.

4. Repeat the above steps 1 to 3 for all the xdmz data models.

1. Select the BiPubReports folder and click on Upload.

2. Select the files which end with .xdoz extension.

3. Click on Upload.

4. Repeat the above steps 1 to 3 for all xdoz reports.