Guidelines for Object Names

Configuring and Managing the Oracle BI Presentation Catalog 17-7 ps:HashUserHomeDirectories2ps:HashUserHomeDirectories ps:Catalog ServerInstance 4. Save your changes and close the file. 5. Restart Presentation Services.

17.2.2 Manually Creating a New Oracle BI Presentation Catalog

You can manually create a new catalog. To manually create a new catalog: 1. Stop the service for Presentation Services. The Oracle BI Server and WebLogic Server must be running.

2. Specify a new location one that does not exist for the catalog on the Repository

tab of the Deployment page in Fusion Middleware Control. See Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

3. Ensure that the new location for the catalog is empty.

4. Save your changes and close the file.

5. Restart Presentation Services.

When manually creating a new catalog in a clustered environment, you must restart each instance of Presentation Services separately using the Availability tab of the Capacity Management page in Fusion Middleware Control. Do not click Restart on the Business Intelligence Overview page. Wait a short time after restarting the first Presentation Services instance to give the system enough time to create the new catalog, then verify that the catalog was successfully created in the Presentation Services log file before restarting the other Presentation Services instances in the cluster.

17.2.3 Deploying Catalogs and Objects to Production

You can deploy catalogs and simple objects for example, a dashboard with privileges to a production environment from a test environment, as described in the following sections: ■ Section 17.2.3.1, Deploying Catalogs to Production ■ Section 17.2.3.2, Deploying Objects to Production

17.2.3.1 Deploying Catalogs to Production

Use the 7-Zip utility to archive an entire catalog in a test environment, then use the utility to unarchive the file in the production environment. Do not use Catalog Manager for archiving and unarchiving entire catalogs. You might deploy a catalog in a cluster configuration in which different security environments are used. Some servers in the cluster might share the same LDAP server, Caution: Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once. 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.