Moving the Web Tier to an Existing 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 .