Moving Oracle WebCenter to an Existing Production Environment

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. Moving from a Test to a Production Environment 21-63 To set up an Oracle Secure Enterprise Search instance and configure it for Oracle UCM on the production system: a. Install Oracle Secure Enterprise Search as described in the Oracle Secure Enterprise Search Installation and Upgrade Guide. b. Create a new data source to connect to Oracle Secure Enterprise Search. See Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server. Oracle recommends that you use the same data source name as in the test environment. c. On the Oracle Universal Content Management Post Configuration page, choose External Full Text Search, and enter the name of the data source. See Configuring Oracle SES and Oracle UCM in the Oracle Fusion Middleware System Administrators Guide for Content Server. 4. If you configured the IntradocDir, WeblayoutDir, and VaultDir directories to be outside of the domain structure, copy the directories to the production environment. 5. In the production environment, modify the following file, updating the entries for IntradocDir, WeblayoutDir, VaultDir, and IdcHomeDir: DOMAIN_HOMEbinintradoc.cfg This step is not necessary if the directory structures of the production environment is the same as the test environment. 6. On the production system, delete the following file: IntradocDirdatacontenttrackerconfigsct.cfg The file is regenerated when you restart the server. 7. Modify the following file, updating the HttpServerAddress to reflect the correct address: instance_dirconfigconfig.cfg 8. Restart the Administration Server and the Managed Server. To use the new production environment as a template and replicate it in multiple production environments, you follow the procedures in Task 2, Move Oracle Universal Content Management to an Existing Production Environment , except that you must also change the parameters IDC_Name, InstanceMenuLabel, InstanceDescription, HttpServerAddress, and AutoNumberPrefix in the following file: instance_dirconfigconfig.cfg You may also need to change the parameters MailServer and SysAdminAddress. Task 5 Move Oracle Imaging and Process Management to a New Production Environment Note that no Oracle IPM data is migrated in this procedure. Data migrated with Oracle UCM will not be accessible from production Oracle IPM system. Before you begin this procedure, if you use Workflow Integration or Oracle Application Extension Framework AXF, make sure that you have: ■ Installed and configured Oracle SOA Suite and moved its test environment to the production environment, as described in Section 21.4.2.1 . 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.