Moving Oracle Enterprise Content Management Suite to an Existing Production Environment

Moving from a Test to a Production Environment 21-75 UNIX ORACLE_INSTANCEconfigWebCachewebcache_namefiles Windows ORACLE_INSTANCE\config\WebCache\webcache_name\files 7. If a non-default wallet was used at the test environment for either an SSL-enabled listen address or an OSwallet, or both, export the wallets from the test environment and import them at the production environment. For information about exporting and importing wallets, see Section 8.4.4 .

21.4.6.2 Moving the Web Tier to an Existing Production Environment

In this scenario, you have a working production environment and want to test changes in your applications or configuration before rolling those changes into the production environment. ■ For Oracle HTTP Server, see Section 21.4.6.2.1 . ■ For Oracle Web Cache, perform Task 2 in Section 21.4.6.1.2 . 21.4.6.2.1 Moving Oracle HTTP Server to an Existing Production Environment To move Oracle HTTP Server to an existing production environment, you update the configuration: 1. Copy any custom contents, such as contents that have been changed or added to the htdocs directory, to the production environment Oracle HTTP Server. 2. If any changes have been made to auditconfig.xml, which is located in the following directory, make a backup copy of the file in the production environment. Then, copy auditconfig.xml from the test environment to the corresponding production environment: ORACLE_INSTANCEconfigOHSohs_component_nameauditconfig.xml 3. If any changes have been made to component-log.xml, make a backup copy of the file in the production environment. Then, copy the file, which is located in the following directory, from the test environment to the production environment: ORACLE_INSTANCEdiagnosticslogsOHSohs_component_name

21.4.7 Moving Oracle Business Intelligence to a Production Environment

This section describes the steps for moving Oracle Business Intelligence from a test environment to a production environment. The following scenarios assume that you have already installed and configured Oracle Business Intelligence components in a test environment and that you want to move them to either a new or an existing production environment: ■ Moving Oracle Business Intelligence to a New Production Environment ■ Moving Oracle Business Intelligence to an Existing Production Environment When There are Few Patches to Apply ■ Moving Oracle Business Intelligence Components to an Existing Production Environment When There are Many Patches to Apply See Also: Managing the Repository Lifecycle in a Multiuser Development Environment in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for detailed information about the life cycle for the Oracle Business Intelligence repository, including test to production considerations for the repository. 21-76 Oracle Fusion Middleware Administrators Guide If you are applying patches to an existing production environment, the steps you take depend on how many patches you need to apply. If there are few patches, you use the steps in Section 21.4.7.2 , which apply the patches to the master host and all cluster hosts in the environment. If there are many patches to apply, consider using the steps in Section 21.4.7.3 , which apply the patches to one host and use different means to propagate that to the other hosts, depending on whether or not new hardware is available.

21.4.7.1 Moving Oracle Business Intelligence to a New Production Environment

This section describes the steps for moving Oracle Business Intelligence from a test environment to a new production environment. This scenario assumes that you have already installed and configured Oracle Business Intelligence components in a test environment and that you want to move them to a new production environment. The steps for moving to a new production environment are identical to the migration process. To move Oracle Business Intelligence components to a new production environment, perform the following tasks: ■ Task 1, Patch and Move the Test Environment ■ Task 2, Patch-Merge the Repository File ■ Task 3, Extract the Archive into the New Production Environment ■ Task 4, Create a BI Domain in the New Production Environment ■ Task 5, Configure Security in the New Production Environment ■ Task 6, Move the Repository File and Oracle BI Presentation Catalog from the Test Environment to the New Production Environment ■ Task 7, Deploy the Test Repository File and Oracle BI Presentation Catalog in the New Production Environment ■ Task 8, Copy and Scale Out to New Cluster Hosts in the Production Environment ■ Task 9, Optional Refresh Global Unique Identifiers GUIDs ■ Task 10, Enable New Agents and Oracle BI Publisher Scheduled Jobs ■ Task 11, Update Links to External Systems ■ Task 12, Optional Move Oracle Business Intelligence Related Applications ■ Task 13, Validate the Production Environment Task 1 Patch and Move the Test Environment 1. Patch the test environment, and test the environment until it is ready. For information, see Oracle Fusion Middleware Patching Guide. 2. If you are trying new configuration settings, then note down the changes that you made so that they can be replicated. 3. Copy the Middleware home containing the Oracle BI EE components from the test environment using the copyBinary script, as described in Section 21.3.3 . Task 2 Patch-Merge the Repository File In the test environment, use the Administration Tool and the Oracle BI Server XML API to perform a patch merge of the test repository file .rpd with the production file. Moving from a Test to a Production Environment 21-77 See Performing Patch Merges in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information. Task 3 Extract the Archive into the New Production Environment 1. Copy the archive file created in Task 1, Patch and Move the Test Environment from the test environment to the production environment. 2. Ensure that JDK 1.6.4 or later or JRockit which is installed with the Oracle Business Intelligence installer is installed in the production environment. 3. Use the pasteBinary script to recreate the Middleware home in the new production environment, as described in Section 21.3.3 . Task 4 Create a BI Domain in the New Production Environment For information, see Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. Task 5 Configure Security in the New Production Environment Configure security if you use something other than the default Oracle WebLogic Server LDAP. For information, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. For information about migrating security data for example, users, groups, policies, and roles, see the appropriate documentation for your authentication provider. The following list provides sources for various components: ■ Oracle Internet Directory: See Task 2, Move Oracle Internet Directory to the New Production Environment ■ Oracle WebLogic Server: See Oracle Fusion Middleware Securing Oracle WebLogic Server ■ Oracle Platform Security Services: See Oracle Fusion Middleware Application Security Guide Task 6 Move the Repository File and Oracle BI Presentation Catalog from the Test Environment to the New Production Environment 1. Copy the repository file .rpd to the production environment. 2. Zip the entire Oracle BI Presentation Catalog in the test environment using zip. 3. Unzip the catalog in the new production environment. For information, see Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. 4. Use Fusion Middleware Control to set the catalog location in the production environment. For information, see Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. Task 7 Deploy the Test Repository File and Oracle BI Presentation Catalog in the New Production Environment 1. Use Fusion Middleware Control in the new production environment to upload the repository file .rpd. 21-78 Oracle Fusion Middleware Administrators Guide For information, see Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. 2. If necessary, use the Administration Tool or the Oracle BI Server XML API to update connection pool and database settings in the repository file. The file might contain data source connection information from the test environment that must be changed to the production environment connection settings. See Moving from Test to Production Environments in Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition for information about performing this step using the Oracle BI Server XML API. 3. Optional Make the production repository file read-only by selecting Disallow Online RPD Updates in the Performance tab of the Capacity Management page in Fusion Middleware Control. Task 8 Copy and Scale Out to New Cluster Hosts in the Production Environment 1. Copy the archive file created in Task 1, Patch and Move the Test Environment to the new cluster host. 2. Copy the following files to the new cluster host: ■ UNIX: ORACLE_COMMON_HOMEbinpasteBinary.sh ORACLE_HOMEjlibcloningclient.jar ■ Windows: ORACLE_COMMON_HOME\bin\pasteBinary.cmd ORACLE_HOME\jlib\cloningclient.jar 3. Use the pasteBinary script to copy the Middleware home to the new cluster host, as described in Section 20.2.1 . Note : You must use exactly the same Middleware home name on the new cluster host that is used on the master host. 4. Use Fusion Middleware Control to scale out to the new cluster host. For information, see Using Fusion Middleware Control to Scale System Components in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. 5. Repeat the previous steps for each new cluster host. Task 9 Optional Refresh Global Unique Identifiers GUIDs You do not normally refresh GUIDs in the LDAP directory identity store users between test and production environments, because the LDAP directories that contain the GUIDs should be fan-out replicas in both the test and the production environments. Possible scenarios for refreshing are described in the following list: ■ Oracle Business Intelligence test servers and production servers are both configured against the corporate LDAP directory. There is no need to refresh LDAP GUIDs. ■ Oracle Business Intelligence test servers are configured against a test LDAP and the production servers against the corporate LDAP, but the test LDAP is a fan-out replica of the corporate LDAP directory. There is no need to refresh LDAP GUIDs.