Moving the Middleware Home and the Binary Files

Moving from a Test to a Production Environment 21-13 c. Using the value in obtained in Step b, perform an ldapdelete, deleting the following dns from Oracle Internet Directory: cn=replication dn, orclreplicaid=replicaid, cn=replication configuration orclreplicaid=replicaid, cn=replication configuration For example: ldapdelete -p port -h host cn=replication dn, orclreplicaid=replicaid, cn=replication configuration d. Set the orclreplicaid value in the root entry to 0. For example: ORACLE_HOMEbinldapmodify -p port -h host -f file.ldif The ldif file contains the following: dn: changetype: modify replace: orclreplicaid orclreplicaid: 0 e. Restart Oracle Internet Directory. 3. If you have configured Oracle Internet Directory replication in the test environment, you must reconfigure it again in the production environment after moving. The replication configuration is not moved from the test to the production environment. See Setting Up Replication in the Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory. Task 3 Move Oracle Virtual Directory to a New Production Environment To move Oracle Virtual Directory to a new production environment: 1. Move the Oracle Virtual Directory configuration, as described in Section 21.3.5 . Note that, during the pasteConfig operation, if you have not provided a password file for the Oracle Virtual Directory adapter or you specify an incorrect location for the password file in the move plan, the adapter configuration is not changed and the script returns the following message: Password file is either not provided or invalid for adapter adapter_name. Nothing will be changed for this adapter configuration. Task 4 Move Oracle Directory Integration Platform to a New Production Environment To move Oracle Directory Integration Platform to a new production environment: 1. Move Oracle Internet Directory, as described in Task 2 . Oracle Directory Integration Platform profiles reside in Oracle Internet Directory. If you have correctly moved Oracle Internet Directory to the production environment, the profiles are carried over to the production environment. 2. If you configured SSL on the test environment, that configuration is not moved to the production environment. You must configure SSL on the production environment. See Section 6.5.4.3 . 21-14 Oracle Fusion Middleware Administrators Guide Task 5 Move Oracle Access Manager 11g to a New Production Environment To replicate the policy configuration information from the test environment into the production environment: 1. Update Oracle Access Manager server instances to reflect new host names and ports. See Viewing or Editing Individual OAM Server and Proxy Settings in the Oracle Fusion Middleware Administrators Guide for Oracle Access Manager with Oracle Security Token Service. 2. Register the client, as described in Registering Partners Agents and Applications Remotely in the Oracle Fusion Middleware Administrators Guide for Oracle Access Manager with Oracle Security Token Service. 3. The registration process generates a new modified ObAccessClient.xml file. Copy this file to the following location: WebGate_instance_dirwebgateconfig 4. Set the environment variable JAVA_HOME and add JAVA_HOME to the PATH. 5. Export the policies from the test environment, using the following WLST command: exportPolicypathTempOAMPolicyFile=path_of_Temp_PolicyFile 6. Copy the policy file to the production environment. 7. Import the policies into the production environment, using the following command: importPolicypathTempOAMPolicyFile=path_of_Temp_PolicyFile 8. Export the partner information from the test environment, using the following WLST command: exportPartnerspathTempOAMPartnerFile=path_of_Temp_PartnerFile 9. Copy the partner file to the production environment. 10. Import the partner information to the production environment, using the following WLST command: importPartnerspathTempOAMPartnerFile=path_of_Temp_PartnerFile 11. Start the Managed Servers. Task 6 Move Oracle Access Manager 10g to a New Production Environment To move Oracle Access Manager 10g to a new production environment: 1. Move the Directory Server from the test environment to the production environment. That is, migrate the o=oblix node. See Preparing the New Directory Server Instance in the Oracle Access Manager Installation Guide. 2. Remove the entries that are associated with the Identity Server, Policy Manager, and Access Servers. The entries are under the following: obcontainerId=DBAgents,Configuration DN Note: The Administration Servers in both the test environment and the production environment must be started.