Locations for the Catalog

17-8 System Administrators Guide for Oracle Business Intelligence Enterprise Edition while others might not. If you deploy the catalog to a server that is communicating with a different LDAP server, then you must regenerate the user GUIDs for the catalog. See Regenerating User GUIDs in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information. Optionally, if you are deploying the catalog from test to a new production environment, then use Fusion Middleware Control to specify the location of the new catalog in the production environment. For information, see Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

17.2.3.2 Deploying Objects to Production

You can deploy simple objects for example, a dashboard with privileges to a production environment from a test environment. Deploying a complex object for example, an object that includes references to external filters is a more advanced process. Oracle offers advanced training courses to guide you through this process. It is recommended that you attend one of these courses before you attempt to deploy a complex object to production. To deploy a simple catalog object to a production environment: 1. Optional If you are deploying a catalog object to a new production environment. Archive the catalog object in the test environment and unarchive it in the production environment as follows:

a. Archive the catalog object in the test environment using one of the following:

– Oracle BI Presentation Services. – Catalog Manager. For information, see Section 17.10, Archiving and Unarchiving Using Cat- alog Manager.

b. Copy the archived file to the production computer.

c. On the production computer, unarchive the object.

For information about how to unarchive an object, see Section 17.10, Archiving and Unarchiving Using Catalog Manager. d. Set the permissions on the object as appropriate. 2. Optional If you are deploying the catalog to an existing production environment. Copy and paste new or updated objects from the test catalog into the production catalog as follows: a. Open two Catalog Manager windows: one with the test catalog, and another with the production catalog. b. Selectively copy and paste the folders from the test catalog into the production catalog. If you copy and paste folders where the same content has been changed in the test or production environments, then test content overwrites the production content. 3. Optional If you are deploying the catalog from test to a new production environment, then use Fusion Middleware Control to specify the location of the new catalog in the production environment. Configuring and Managing the Oracle BI Presentation Catalog 17-9 For information, see Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

17.2.4 Validating the Catalog

Over time, inconsistencies can develop in the catalog as links are broken, users are deleted, or NFS file system issues are encountered. These inconsistencies can eventually lead to incorrect behavior, such as the inability to edit an agents recipient list. You can periodically take the production system offline and validate the catalog, to be informed of and to take corrective action on inconsistencies.

17.2.4.1 Performing a Basic Validation of the Catalog

Use the following procedure to perform a basic validation of the catalog. To validate the catalog: 1. Stop Presentation Services. For information, see Section 4.3, Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components. 2. In 11g only, regenerate the user GUIDs for the catalog. See Regenerating User GUIDs in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information 3. Back up the catalog by using the 7-Zip utility to create a compressed file for it. 4. Create a backup copy of the instanceconfig.xml file. For the location of the file, see Section 3.6, Where Are Configuration Files Located? 5. Edit the instanceconfig.xml file so that it contains the appropriate elements for performing the validation. For information on these elements, see Section 17.2.4.2, Specifying the Elements for Validating the Catalog. 6. Start Presentation Services to run the validation according to the values that you specified in the instanceconfig.xml file. 7. Stop Presentation Services. 8. Create a backup copy of the instanceconfig.xml file in which you added the validation elements, renaming the file similar to instanceconfig_validate.xml. In this way, you have a version of the file to use as a starting point for subsequent validations. 9. Restore the backup version of the instanceconfig.xml that you created earlier to use as the current version. 10. Start Presentation Services. Caution: Ensure that you regenerate the user GUIDs before validating the catalog. Failure to do so can result in the removal of all accounts, permissions, and privileges from the catalog.