Moving Oracle Web Cache to a New Production Environment In this scenario, you

21-80 Oracle Fusion Middleware Administrators Guide To move Oracle Business Intelligence components to an existing production environment when there are few patches to apply, perform the following tasks: ■ Task 1, Patch the Test and Existing Production Environments ■ Task 2, Deploy the Test Repository File to the Existing Production Environment ■ Task 3, Deploy the Test Oracle BI Presentation Catalog to the Existing Production Environment ■ Task 4, Optional Refresh Global Unique Identifiers GUIDs ■ Task 5, Enable New Agents and Oracle BI Publisher Scheduled Jobs ■ Task 6, Update Links to External Systems ■ Task 7, Optional Move Oracle Business Intelligence Related Applications ■ Task 8, Validate the Production Environment Task 1 Patch the Test and Existing Production Environments A patch applies a collection of bug fixes to an existing environment and includes new binary files and metadata updates. 1. Patch the test environment as required, and test until ready. 2. Patch the existing production environment to the same level as the test environment on the master host and on all cluster hosts. Note: Patching also includes non-Oracle Business Intelligence patches and one-off patches. For information, see Patching Oracle Business Intelligence Systems in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. Task 2 Deploy the Test Repository File to the Existing Production Environment 1. 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. You must complete this task only if you are moving to an existing production environment and have made changes to the RPD file in the test environment. See Performing Patch Merges in the Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information. 2. Use Fusion Middleware Control in the production environment to upload the RPD file to use. For information, see Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location in the Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. 3. If necessary, use the Administration Tool or the Oracle BI Server XML API to update connection pool and database settings in the repository. The RPD 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 the Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition for information about performing this step using the Oracle BI Server XML API. Moving from a Test to a Production Environment 21-81 4. 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 3 Deploy the Test Oracle BI Presentation Catalog to the Existing Production Environment 1. Drag and drop new or updated folders 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 that you want from the test catalog into the production catalog. Note: If you copy and paste folders where the same content has been changed in the test or production environments, then the test content overwrites the production content. For information, see the Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. 2. Use Fusion Middleware Control in the existing production environment to specify the location of the new catalog. For information, see Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location in the Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition. Task 4 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. ■ Oracle Business Intelligence test servers are configured against a test LDAP and the production servers against the corporate LDAP, but the test LDAP is not a fan-out copy of the corporate LDAP directory. A refresh of the LDAP GUIDs is needed. For information, see Section 21.4.7.4 . Task 5 Enable New Agents and Oracle BI Publisher Scheduled Jobs If new agents were created in the test environment, then click each agent in the Oracle BI Presentation Services Catalog Manager in the production environment to enable it. Oracle BI Publisher reports are stored in the Oracle BI Presentation Catalog and so existing reports and new reports created in the test environment should be available. 21-82 Oracle Fusion Middleware Administrators Guide In a production environment, Oracle WebLogic Server administrators should create JNDI connections to be used by Oracle BI Publisher reports, using the same names as in the test environment. The connections should point to the production databases instead of the test databases. In this way, all reports automatically point to the production environment databases, instead of test environment databases, without any modification. Task 6 Update Links to External Systems Ensure that you move the static content that relates to external systems to the production environment, as described in the following steps: 1. Copy the Action Framework configuration file from its location on the source system to the same location on the target system. In addition, the ActionFramework configuration file might contain policy elements that refer to files in the same directory as the configuration file. Copy these files to the same location on the target system. 2. Edit the Action Framework configuration file and ensure that the endpoints refer to relevant resources in the target system. For information on configuring for different types of actions, see Configuring the Action Framework in Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition. Task 7 Optional Move Oracle Business Intelligence Related Applications Move Oracle Business Intelligence related applications such as Calculation Manager, Financial Reporting, and Oracle BI for Microsoft Office to the existing production environment. For information, see Section 21.4.4 . Task 8 Validate the Production Environment Validate that the production environment accurately represents the test environment. 21.4.7.3 Moving Oracle Business Intelligence Components to an Existing Production Environment When There are Many Patches to Apply This section describes the steps for moving Oracle Business Intelligence from a test environment to an existing production environment when there are many patches to apply. 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 an existing production environment. Use one of the following strategies to move Oracle Business Intelligence components to an existing production environment when there are many patches to apply: ■ Moving Oracle BI EE to an Existing Production Environment When New Hardware Is Available ■ Moving Oracle BI EE to an Existing Production Environment When New Hardware Is Not Available

21.4.7.3.1 Moving Oracle BI EE to an Existing Production Environment When New Hardware Is

Available Perform the following tasks to move Oracle Business Intelligence components to an existing production environment when there are many patches to apply and new hardware is available: ■ Task 1, Follow the Steps for Moving to a New Production Environment Moving from a Test to a Production Environment 21-83 ■ Task 2, Switch Users from the Existing Production Environment to the New One ■ Task 3, Remove the Existing Production Environment and Prepare It for the Next Patch Task 1 Follow the Steps for Moving to a New Production Environment Complete the steps in Section 21.4.7.1 for moving to a new production environment. These steps include merging the new test RPD file and catalog with those in the existing production environment. Ideally you merge once and resolve the issues while users continue using the existing environment. When the files are correct, you lock the production environment and repeat the merge to access the latest changes. Task 2 Switch Users from the Existing Production Environment to the New One Use a load balancer such as Oracle Web Cache to redirect users from a standard URL to the new production environment. Task 3 Remove the Existing Production Environment and Prepare It for the Next Patch Shut down the existing environment and deinstall all software. When needed, you can apply the next patchset to this host, and the sequence can start all over again.

21.4.7.3.2 Moving Oracle BI EE to an Existing Production Environment When New Hardware Is

Not Available Perform the following tasks to move Oracle Business Intelligence components to an existing production environment when there are many patches to apply and new hardware is not available: ■ Task 1, Scale the Production Environment Back to One Host ■ Task 2, Patch the Host in the Production Environment ■ Task 3, Remove the Existing Software on the Cluster Hosts ■ Task 4, Move the Production Environment and Then Copy to the Cluster Hosts Task 1 Scale the Production Environment Back to One Host Use the Capacity Management tab of the Scalability page in Fusion Middleware Control in the production environment to scale back system components to apply only to the first host in the list. This scaling makes it much easier to patch the existing production environment. For more information, see the Fusion Middleware Control Help system. Task 2 Patch the Host in the Production Environment Patch the host in the production environment. Doing so imposes less downtime on users than having to patch multiple cluster hosts. For information, see the Oracle Fusion Middleware Patching Guide. Task 3 Remove the Existing Software on the Cluster Hosts Deinstall all the Oracle Business Intelligence software on the cluster hosts. For information, see the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. Task 4 Move the Production Environment and Then Copy to the Cluster Hosts Complete the tasks beginning with Task 8, Copy and Scale Out to New Cluster Hosts in the Production Environment in Section 21.4.7.1 .