Moving Oracle WebCenter to a New Production Environment

Moving from a Test to a Production Environment 21-57 ■ Task 5, Move Oracle Hyperion Provider Services to a Production Environment ■ Task 6, Move Oracle Hyperion Smart View to a Production Environment ■ Task 7, Move Oracle EPM Workspace to a Production Environment Task 1 Move the Database, Middleware Home, and Perform the Initial Configuration To move the database, Middleware home, and perform the initial configuration: 1. Move or create the database, as described in Section 21.3.2 . 2. Move Identity Management components, as described in Section 21.4.1 . 3. Move the Middleware home and binary files, as described in Section 21.3.3 . 4. Move the configuration, as described in Section 21.3.4 . 5. Configure users, groups, the security policies, and the credential store, as described in Section 21.3.6 . Task 2 Move Oracle Essbase to a Production Environment For Oracle Essbase, only configuration settings need to be moved from a test environment to a production environment. For example, copy essbase.cfg from a test to a production environment: ORACLE_INSTANCEEssbaseessbaseserver1binessbase.cfg Task 3 Move Oracle Hyperion Calculation Manager to a Production Environment To move Oracle Hyperion Calculation Manager from a test environment to a production environment, do one of the following: ■ Back up the repository Since the Calculation Manager schema does not change, you can use the same repository with the new Calculation Manager environment. All pre-existing Calculation Manager objects and other related information are available in the new environment. ■ Exportimport allocation rules and rule sets Export Calculation Manager rules and rule sets from the test environment in Calculation Manager, select File, and then Export and then import them back into the production environment in Calculation Manager, select File, and then Import . Notes: ■ Use only one not both of the above options to move from a test environment to a production environment. Use the option that makes the most sense for your environment. The exportimport option is simpler; however, backing up the repository saves more information in the database. ■ Rules that have already been deployed to Fusion GL and have since been modified in Calculation Manager will not be handled by Calculation Manager. Calculation Manager does not keep versions of rules. 21-58 Oracle Fusion Middleware Administrators Guide Task 4 Move Oracle Hyperion Financial Reporting to a Production Environment You can export Oracle Hyperion Financial Reporting content from the test environment and import it into the production environment: 1. Export Financial Reporting report content from the test environment: a. Log in to the test environment. b. Select File, and then Export. c. Navigate to and select the content or directory that you want to move to the production environment. d. Export the selected content or directory to the local file system. 2. Import Financial Reporting report content into the production environment: a. Log in to the production environment and select File, then Import, and then Financial Reporting. b. Browse to the target location where you want to import the Financial Reporting report content, and select the local file to which you saved the exported content. Task 5 Move Oracle Hyperion Provider Services to a Production Environment Oracle Hyperion Provider Services artifacts need to be copied from test environment to a production environment. ■ To move Provider services when it is used by Smart View: 1. Use Smart View client to manually add any Essbase servers created in the test server to the production server. 2. Copy essbase.properties found in ORACLE_ INSTANCEproductsEssbaseapsbin to the production environment. 3. From Smart View, re-create any Cube views created under the test environment in the production environment. ■ To move Provider Services when it is used by the Oracle Essbase Java API: If the default Java API preferences are changed in the essbase.properties file on the Java API client program configuration, then copy essbase.properties to the production environment. Task 6 Move Oracle Hyperion Smart View to a Production Environment Because Oracle Hyperion Smart View for Office is a client side application, spreadsheet and other Microsoft Office documents created with test servers must be associated with production server connections. You can point an existing report from test to production if the metadata remains the same. To associate shared connections: 1. Open the existing report. The location of existing reports depends on where you stored the reports when you first created them. Note: Oracle Hyperion Financial Reporting annotations and scheduler output cannot be migrated from the test environment to the production environment. Moving from a Test to a Production Environment 21-59 2. In Excel with Smart View installed, select Smart View, then Options, and then Advanced. 3. Change the Shared Connections URL to the new connection URL; for example: https:host.example.comworkspaceSmartViewProviders 4. Select Smart View, then Open, then Smart View Panel, then Shared Connections, and do one of the following: ■ If Essbase Server is not listed, click Create New Connection. ■ If Essbase Server is listed, enter the user name and password, and click Connect . 5. From the drop-down list, select Essbase Server. a. From the drop-down list, select Locate worksheet connection. The connection is created under cube. b. Select the connection and right-click to connect. 6. Click Refresh. 7. For ad-hoc analysis, you need to connect to a new server and choose to maintain POV. To do this, select Reuse sheet contents and POV when prompted. To associate private connections: 1. Select Smart View, then Open, and then Smart View Panel. 2. Select Private Connections. 3. Enter the Provider Services URL: for example: https:host.example.comapsSmartView 4. Log in to Oracle Hyperion Provider Services. 5. Select the Essbase application and log in. 6. Select the Oracle Essbase application, right-click, and select Add to Private Connections. 7. Enter the connection name or use the default name, and click OK. 8. Associate the connection SVC, then Open, and then Active Connection and select the connection. Click OK to confirm the message. 9. Click Refresh. 10. For ad-hoc analysis, you need to connect to a new server and choose to maintain POV. Select Reuse sheet contents and POV when prompted. Task 7 Move Oracle EPM Workspace to a Production Environment When you move Oracle Enterprise Performance Management Workspace information from a test environment to a production environment, the system settings and user preferences must be manually migrated. Any changes to server settings and user preferences must be made in the target system. See Administering EPM Workspace in the Oracle Enterprise Performance Management Workspace, Fusion Edition Administrators Guide. 21-60 Oracle Fusion Middleware Administrators Guide

21.4.5 Moving Oracle Enterprise Content Management to a Production Environment

The following topics describe how to move Oracle Enterprise Content Management Suite to a production environment: ■ Moving Oracle Enterprise Content Management Suite to a New Production Environment ■ Moving Oracle Enterprise Content Management Suite to an Existing Production Environment In both scenarios, you have performed the following in the test environment: ■ Installed a database to be used for required schemas. ■ Created needed schemas using RCU. See the Oracle Fusion Middleware Repository Creation Utility Users Guide. ■ Installed Oracle WebLogic Server and created the Middleware home. ■ Installed and configured Oracle Enterprise Content Management Suite. ■ If Oracle Imaging and Process Management uses Workflow or Oracle Application Extension Framework AXF, installed and configured Oracle SOA Suite. ■ Configured Oracle Universal Content Management. ■ Configured Oracle Imaging and Process Management. If Oracle IPM uses Oracle Universal Content Management 10g repository, ensure that the repository was manually configured for Oracle IPM. ■ Configured Oracle Universal Records Management. ■ Defined several definitions, such as Connections, Applications, Searches, and Inputs for Oracle IPM. ■ Installed and configured Identity Management components, such as Oracle Internet Directory.

21.4.5.1 Moving Oracle Enterprise Content Management Suite to a New Production Environment

To move Oracle Enterprise Content Management Suite to a new production environment, perform the following tasks: ■ Task 1, Move the Database, Middleware Home, and Perform the Initial Configuration ■ Task 2, Configure Full-Text for Oracle UCM ■ Task 3, Modify Oracle Information Rights Management Settings ■ Task 4, Move Oracle Universal Content Management to a New Production Environment ■ Task 5, Move Oracle Imaging and Process Management to a New Production Environment ■ Task 6, Move Oracle Universal Records Management to a New Production Environment Note that in a production environment, Oracle Enterprise Content Management Suite applications need to use an external Lightweight Directory Application Protocol LDAP authentication provider rather than the Oracle WebLogic Server embedded LDAP server, which is part of the default configuration. You reassociate the identity Moving from a Test to a Production Environment 21-61 store for your application with one of the following external LDAP authentication providers before you complete the configuration of a Managed Server, before you connect a Managed Server to a repository, and before the first user logs in to the application: ■ Oracle Internet Directory ■ Oracle Virtual Directory ■ A third-party LDAP Server Task 1 Move the Database, Middleware Home, and Perform the Initial Configuration To move the database, the Middleware home, and perform the initial configuration: 1. Move or create the database, as described in Section 21.3.2 . 2. Move Identity Management components, as described in Section 21.4.1 . 3. Move the Middleware home and binary files, as described in Section 21.3.3 . 4. Move the configuration, as described in Section 21.3.4 . Note that when you move the configuration, the pasteConfig script copies the configuration of the domain, including the domain, Administration Server, and Managed Servers. In addition, that step: ■ Modifies information about the database that contains Oracle IRM metadata. ■ Copies the Oracle IPM sample input files, if they are in the domain directory. ■ Copies the BPEL credentials. ■ Moves Oracle Web Services Manager policies. ■ Sets the Listen address for the Managed Server that contains Oracle Application Extension Framework AXF. ■ Starts the Administration Server and Managed Servers. 5. Configure users, groups, the security policies, and the credential store, as described in Section 21.3.6 . Task 2 Configure Full-Text for Oracle UCM If you are using an Oracle UCM 10g repository, ensure that Full-Text is configured correctly on the production Oracle UCM system, if configured on the test Oracle UCM 10g system. Note that if you are using an Oracle UCM 10g server, it is not configured when you move the Oracle Enterprise Content Management Suite. you must install it, similar to the way you installed it in the test environment, using the procedures described in the Oracle Universal Content Management page at: http:www.oracle.comtechnetworkmiddlewarecontent-managementoverviewindex.h tml Task 3 Modify Oracle Information Rights Management Settings You need to modify some Oracle IRM settings in the new production environment: 1. Set up SSL. For Oracle IRM, SSL should be enabled so that Oracle IRM Desktop does not show prompts to accept certificates when it contacts the Managed Server. The certificate used must be trusted by Microsoft Internet Explorer on computers running Oracle IRM Desktop. Follow the standard SSL setup instructions for 21-62 Oracle Fusion Middleware Administrators Guide Oracle WebLogic Server, as described in Configuring SSL in Oracle Fusion Middleware Securing Oracle WebLogic Server. 2. Each Oracle IRM installation requires access to a keystore with installation specific keys. The unpacked domain may have a keystore. If it does and if the Content Tracker component is enabled and being used in their test environment., delete this keystore, clear the passwords details, and create a new keystore: a. Delete the keystore file. By default, the keystore is located in the following directory: DOMAIN_HOMEconfigfmwconfig By default, the file name is irm.jks. It may be named differently or use a different type, depending on the template used. b. Keystore passwords are stored in the credential store. If passwords have been set in the template domain, clear the passwords using the following WLST commands: connectusername, password, localhost:7001 deleteCredIRM, keystore:keystore_filename deleteCredIRM, key:irm.jks:oracle.irm.wrap For the key, you use the keystore file name stored in the template. c. Create a new keystore, as described in Configuring the Keystore for Oracle IRM in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. 3. If the production environment is not using the same LDAP store as the test environment, migrate the users from the test environment to the production environment. See Reassociating the Identity Store with an External LDAP Authentication Provider in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. Task 4 Move Oracle Universal Content Management to a New Production Environment To move Oracle Universal Content Management to a new production environment: 1. Export the OCS database schema from the test environment, using the following command ORACLE_HOME is the Oracle home for the Oracle Database: ORACLE_HOMEbinexpdp \syspassword as sysdba\ schemas=test_env_schema_name directory=directory dumpfile=ucm.dmp Make sure that the dumpfile is in a location that can be accessed by the production database. 2. Import the OCS database schema that you exported from the test environment, using the following commands ORACLE_HOME is the Oracle home for the Oracle Database: ORACLE_HOMEbinimpdp \syspassword as sysdba\ remap_schema=test_env_schema_name:prod_env_schema_name directory=directory dumpfile=ucm.dmp TABLE_EXISTS_ACTION=REPLACE 3. For a system that has a full text search solution using external databases, set up a new database to hold the new search collection.