Complete the following steps if an Oracle Analytics Server (OAS) was set up for Empirica Topics reporting.

1. As the non-privileged user, on the application server running OAS, start a command shell (for example, Putty).
2. Create a temporary directory <OAS_9201> (for example, /u01/stage/OAS_9201), and unpack ESI_9.2.0.1.zip into it.
3. In the temporary directory, open the file update_oas_catalog.sh.
   1. Verify that the DOMAIN_HOME directory, specified in the file, exists.
      If necessary, update the path in the script to point to the correct location.
   2. Set the value for HOST_NAME.
   3. Verify that BI_PORT and ADMIN_USER are correct. If not, update them accordingly.
   4. Note the BACKUP_DIR directory specified in the file.
      This backup directory will be created as it appears in the script. If desired, you can update the path in the script to point to an existing location on your server.
4. From the temporary directory, give the shell script execute permissions and run it:
   $ chmod +x update_oas_catalog.sh
   $ ./update_oas_catalog.sh

   Enter the admin user password when prompted.

5. When the script completes, verify the following:
   1. The script prints the following as the last two lines of output:
      Command 'unarchive' completed successfully.
      Return status from Catalogmanager command : 0
   2. The Topics_9_2_0_0.catalog file exists in the BACKUP_DIR directory.
6. In the temporary directory, open the file update_oas.sh.
   1. Verify that the WEBLOGIC_HOME directory, specified in the file, exists.

      If necessary, update the path in the script to point to the correct location.

   2. Note the BACKUP_DIR directory specifiedin the file.

      This backup directory will be created as it appears in the script. If desired, you can update the path in the script to point to an existing location on your server.

7. From the temporary directory, give the shell script execute permissions and run it:
   $ chmod +x update_oas.sh
   $ ./update_oas.sh

   Verify that the script prints Completed and that there are no errors.

8. Verify the <WEBLOGIC_HOME>/wlserver/server/lib/mbeantypes directory includes the following files:
   log4j-api-2.17.1.jar
   log4j-core-2.17.1.jar