Introduction to Moving Oracle Fusion Middleware Components

Moving from a Test to a Production Environment 21-9 -targetOracleHomeLoc scratchOracleMiddlewareOracle_WebTier -targetInstanceHomeLoc scratchOracleMiddlewarewebtier_2 -targetInstanceName webtier_2 -targetComponentName ohs_cl -domainHostName myhost -domainPortNum 7001 -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file When you complete this task, you need to perform additional steps for each component, as described in Section 21.4 .

21.3.6 Configuring Users, Groups, Security Polices, and Credential Stores for Components

You must configure security in the new production environment. The steps you take depends on the configuration of your environment and application. The following steps assume that you are using Oracle Internet Directory, JKS certificates, Oracle Web Services Manager, and Oracle Platform Security: 1. The production environment LDAP identity store may not use the same users and groups as the test environment, or it may already be populated with users and groups. Take the following steps only if you need to export users, groups, and passwords from the test environment. If necessary, move users and groups to the production environment. For example, if you are using the Oracle Business Activity Monitoring or Human Workflow demo, move those users a. 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 b. Import 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 2. If the security policies are stored in an external LDAP or database-based store, import the security policies, for example those that are related to the Human Workflow application roles, from the test environment to the production environment, as described in Task 12, Move Oracle Platform Security to a New Production Environment in Section 12 . 3. If the credential policies are stored in an external LDAP or database-based store, import the credential store information from the test environment to the production environment, as described in Task 12, Move Oracle Platform Security to a New Production Environment in Section 12 . 21-10 Oracle Fusion Middleware Administrators Guide

21.4 Moving Oracle Fusion Middleware Components

The following sections describe the steps you must take to move Oracle Fusion Middleware components. In many cases, the steps use the common procedures described in Section 21.3 . All components require additional steps as described in the following topics: ■ Moving Identity Management Components to a Production Environment ■ Moving Oracle SOA Suite to a Production Environment ■ Moving Oracle WebCenter to a Production Environment ■ Moving Oracle Hyperion Enterprise Performance Management System to a Production Environment ■ Moving Oracle Enterprise Content Management to a Production Environment ■ Moving the Web Tier to a Production Environment ■ Moving Oracle Business Intelligence to a Production Environment ■ Moving Oracle Real-Time Decisions to a Production Environment ■ Moving Oracle Portal, Oracle Forms Services, Oracle Reports, and Oracle BI Discoverer to a Production Environment ■ Moving Oracle Data Integrator to a Production Environment

21.4.1 Moving Identity Management Components to a Production Environment

The following topics describe how to move Identity Management from a test environment to a production environment: ■ Moving Identity Management to a New Production Environment ■ Moving Identity Management to an Existing Production Environment In both scenarios, you have performed the following in the test environment: ■ Installed a database to be used for Identity Management components such as Oracle Internet Directory, Oracle Directory Integration Platform which depends on Oracle Internet Directory, and Oracle Identity Federation. ■ Created needed schemas using RCU. ■ Installed and configured Identity Management, including some or all of the following components: Oracle Internet Directory, Oracle Virtual Directory, Oracle Web Services Manager, or Oracle Adaptive Access Manager. ■ For Oracle Internet Directory, created the desired LDAP trees and entries, in particular, users and groups. ■ For Oracle Virtual Directory, created adapters to various data sources, such as LDAP and databases, and you may have configured a Local Store Adapter LSA to create local LDAP data, which resides in the local file system. In addition, you may have made other configuration changes such as adding ACLs, changing schemas, the Listener configuration, server configuration, plug-ins, mappings, auditing, logging, and keystores. ■ For Oracle Directory Integration Platform, created synchronization profiles to various targets. These profiles are in the form of LDAP entries residing in Oracle Internet Directory.