Moving Oracle HTTP Server to a New Production Environment In this scenario, you

Moving from a Test to a Production Environment 21-79 ■ 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 10 Enable New Agents and Oracle BI Publisher Scheduled Jobs If new agents were created in the test environment, 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 that are created in the test environment should be available. 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 11 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 12 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 new production environment. For information, see Section 21.4.4 . Task 13 Validate the Production Environment Validate that the production environment accurately represents the test environment. 21.4.7.2 Moving Oracle Business Intelligence to an Existing Production Environment When There are Few 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 few patches to apply. See Section 21.4.7.3 if you have many patches to apply. The following steps 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. 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.