Moving Oracle Hyperion Enterprise Performance Management System to a Production Environment

21-64 Oracle Fusion Middleware Administrators Guide ■ Configured Oracle IPM, extending the SOA domain, as described in Extending an Existing Domain in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. To move Oracle IPM to the new production environment: 1. Start the Administration Server and the Oracle IPM Managed Server. 2. Ensure that the Oracle UCM 11g Managed Server is running, or, if you are using Oracle UCM 10g, that the Oracle UCM 10g services are running. 3. If you have moved Oracle Internet Directory to the production environment, export Oracle IPM users and groups from the test environment. The user who logs in first to an Oracle IPM Managed Server is provisioned with full security throughout the server. It is easier to reassociate the identity store for Oracle IPM with an external LDAP authentication provider before the first user logs in, completes the configuration of the Oracle IPM Managed Server, and connects it to the Oracle UCM repository. Export the users and groups from LDAP identity store on the test environment, using the ldapsearch command. This produces an ldif file that you later import into the LDAP identity store in the production environment. The ldapsearch command is located in the ORACLE_HOMEbin directory of the Identity Management components. For example: ORACLE_HOMEbinldapsearch -h test_oid_host -p test_oid_port -D cn=orcladmin -w test_orcladmin_passwd -b cn=Users,dc=us 4. Export the system definitions from the test environment. Note the following: ■ This procedure does not transfer any documents from the test environment to the production environment. This procedure only moves the structure defined by the applications, inputs, and searches. ■ The documents reside within the supporting Oracle UCM repository. Oracle IPM does not recognize any documents that were transferred using Oracle UCM test-to-production procedures or database utilities. The documents will not be accessible from Oracle IPM. Use Oracle IPM to upload new documents into the Oracle UCM repository. a. Log into the test environment as administrator to export the definitions, using the following URL: http:hostname:16000imaging b. Expand Tools, then select Export Definitions. c. For Export Comments, enter any comments, then click Next. d. Select the applications to export, then click Next. e. Select the searches to export. All dependent applications for each search are included in the export. Click Next. f. Select the inputs to export. All dependent applications for each input are included in the export. Click Next. g. Review your selections for accuracy, then click Next. If you need to make any changes, select the appropriate type of definition at the top of the page, such as Applications, and correct the selections. Then, select the Summary at the top of the page. Moving from a Test to a Production Environment 21-65 h. Select Create Export File. i. Depending on your browser, a dialog box is displayed allowing you to open or save the file. The file is saved to the location you specify. 5. If the sample files are outside the domain directory, copy the files from the test environment to the production environment. The location of the files is specified in the Oracle IPM MBean SampleDirectory. For information about the Oracle IPM MBeans, see Oracle IPM MBeans in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. For more information about using Input sample files to create input definitions, see Creating Input Definitions in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. 6. If you have moved Oracle Internet Directory to the production environment, import users and groups into the LDAP identity store on the production environment by importing the ldif file that you exported from the test environment into the production environment, using the ldapaddmt command, as shown in the following example. ORACLE_HOME is the Oracle home for Identity Management. ORACLE_HOMEbinldapaddmt -h production_oid_host -p production_oid_port -D cn=orcladmin -w production_orcladmin_passwd -r -f ldif_filename 7. Enable SSL, as described in System Security in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. 8. 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 . 9. Configure connections on the production environment. Before you can import the applications into the production environment, you must set up the Oracle IPM system connection objects that establish links to Oracle UCM repository and Workflow servers in the production environment. If the connections in the production environment are named the same as in the test environment, the imported definitions link correctly without further action. If the names are different, you can select the desired connection name using the using the Oracle IPM import tool. 10. Modify configuration settings. You use Fusion Middleware Control to modify the system MBean values, which control the execution of Oracle IPM. If any MBean values need to be changed, follow the procedures in Configuring the AgentUser and GDFontPath MBeans in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. 11. If the Work Manager configuration for the Input Agents does not already specify values for the production environment, update the configuration, as described in Changing Oracle WebLogic Server Work Manager Settings in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. 12. If the Work Manager configuration for the Workflow Agents does not already specify values for the production environment, update the configuration, as described in Changing WebLogic Server Work Manager Settings in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. 13. Note that User preferences are not migrated. Users must reconfigure their preferences on the production Oracle IPM system. 21-66 Oracle Fusion Middleware Administrators Guide 14. Import the system definitions to the production environment. a. Log into the production environment system as administrator to import the definitions, using the following URL: http:hostname:16000imaging b. Expand Tools, then select Import Definitions. c. For File Location, click Browse, and browse to the location of the file you exported from the test environment in step 4. When you select the file, the File Date, and File Comments fields are populated. d. Click Next. e. From each table, select the applications, inputs, and searches, to be imported. Selecting the Plus sign +, shows the description for the definition. Selecting the pull down for the repository allows you to place each definition in any of the defined repository connections. f. Click Next. g. In the validation phase, you can see the status of each definition and you can select Document Security, Storage Policy, Workflow, and Full-Text options. See Import Definitions: Validate Imports Page in the Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. If any of the definitions are marked by a red X, the definition cannot be imported. Some of the likely causes are: – For search and input definitions, a required application was not imported. – The security checks failed. – The connection specified by the application does not exist. – The Workflow validation failed. h. Correct any problems. When all the definitions are valid, select Submit. If the validation is successful, the changes are committed. If there are errors, the page shows new exceptions. Correct any errors and click Submit. 15. Move the Oracle Application Extension Framework AXF configuration database: a. Export the following tables from the test database schema and insert them into the production database schema: – AXF_ACTIONS – AXF_ACTION_MENU – AXF_ACTION_PARAMETERS – AXF_COMMANDS – AXF_ENUM_ITEMS – AXF_ENUM_TYPES – AXF_METADATA_ATTRIBUTES – AXF_METADATA_BLOCKS – AXF_SOLUTIONS Moving from a Test to a Production Environment 21-67 – AXF_SOLUTION_ATTRIBUTES – AXF_SOLUTION_PARAMETERS – AXF_XPATH_NAMESPACES – AXF_XPATH_ATTRIBUTES b. Modify the Workflow Connection information to point the connection to the production Workflow system. If you are using a different Workflow Connection name in the production environment,update the PARAMETER_VALUE column. Using the Workflow connection created in step 9, update the PARAMETER_VALUE column for the BPEL_CONNECTION row in the AXF_SOLUTION_ATTRIBUTES table using your preferred SQL utility: UPDATE AXF_SOLUTION_ATTRIBUTES SET PARAMETER_VALUE = ConnectionName WHERE PARAMETER_KEY = BPEL_CONNECTION c. If you have created any SOA Composites for an AXF solution in the test environment, deploy those versions of composites in the production environment, as described in the AXF11g Solution Template Guide. 16. If you cannot retrieve documents from the IPM Viewer, you must change the permissions for the following file: DOMAIN_HOMEoracleimagingimaging-serverixTransformer Task 6 Move Oracle Universal Records Management to a New Production Environment To move Oracle Universal Records Management to a new production environment: 1. On the test environment, export the configuration settings, such as retention schedule, security classifications, and triggers, as described in Exporting an Archive in the Oracle Fusion Middleware Administrators Guide for Universal Records Management. 2. Copy the archive to the production environment. 3. Import the archive to the production environment, as described in Importing an Archive in the Oracle Fusion Middleware Administrators Guide for Universal Records Management.

21.4.5.2 Moving Oracle Enterprise Content Management Suite to an Existing Production Environment

In this scenario, you have installed Oracle Enterprise Content Management Suite components, such as Oracle Information Rights Management, in a test environment and you want to move them to a production environment that already exists. On the existing production environment, you have installed and configured the components. You want to move an application from the test environment to the production Oracle Enterprise Content Management Suite environment. To move Oracle Enterprise Content Management Suite to an existing production environment, perform the following tasks: ■ Task 1, Move Oracle Information Rights Management to an Existing Production Environment ■ Task 2, Move Oracle Universal Content Management to an Existing Production Environment 21-68 Oracle Fusion Middleware Administrators Guide ■ Task 3, Move Oracle Imaging and Process Management to an Existing Production Environment ■ Task 4, Move Oracle Universal Records Management to an Existing Production Environment. Task 1 Move Oracle Information Rights Management to an Existing Production Environment Organizations that run a proof of concept or pilot test deployment can copy the operational service into a production environment and continue to use all existing test content, contexts, and rights. The IRM server URL for example protocol_schema:\\hostname:port\irm_desktop is sealed into test content. Therefore, this value must not change on moving from test to production. For this reason, make sure you consider the following points when installing the test deployment: ■ Configure SSL in the test deployment because switching from the HTTP protocol in the test environment to the HTTPS protocol in the production environment would prevent test-sealed content from working in a production environment. ■ Use a generic host name such as irm.example.com for the test deployment rather than a machine-specific host name such as mytestdeploymachine.example.com. After the test to production installation has been completed, the DNS entries for domain name can be switched from the test server to the production environment. If needed, you can use port redirection to ensure that the test deployment IRM Server URL points to the production environment deployment. To move a test deployment into a production environment: 1. If the production database is different from the test database, you should back up the Oracle IRM schema. Restore the backup into the production database. 2. Copy the Oracle IRM keystore set up during the test installation to the production environment. This is typically called irm.jks. This file is usually located in the following directory: DOMAIN_HOMEconfigfmwconfig 3. The Oracle IRM Java EE application needs a password for the keystore copied in the previous step and each key stored in that keystore. If the passwords are not specified, the Oracle IRM Java EE application will not be able to retrieve the keys. To switch to using more secure passwords than those used in the test environment, use the keytool command line to change the passwords before proceeding. See the keytool Help for syntax. 4. With secure passwords in place, use WLST commands to specify these passwords to the Oracle IRM Java EE application. The following example connects to an Administration Server and sets the keystore credentials: connectusername, password, t3:adminServerHost:adminServerPort createCredIRM, keystore:irm.jks, dummy, secureproductionpassword createCredIRM, key:irm.jks:oracle.irm.wrap, dummy, secureproductionpassword For more information, see Setting Passwords for the Keystore in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.