Recovering a Managed Server to the Same Host

Recovering Your Environment 18-29 1. Recover the component, as described in Section 18.3.4.4 . 2. Recover Oracle Management Agent, as described in Section 18.3.5.3 . 18.3.4.5.3 Recovering Oracle Directory Integration Platform to a Different Host To recover Oracle Directory Integration Platform to a different host: 1. Recover the Managed Server, as described in Section 18.3.3.2 . 2. Before starting the Managed Server, restore the files in the following directory: DOMAIN_HOMEserverswls_ods1stageDIP11.1.1.1.0 3. Start the Managed Servers and Oracle instances. 4. If Oracle Internet Directory is also moved to a different host, execute the following commands immediately after the Managed Server and the Oracle instance are started: set ORACLE_HOME Oracle_home_path set WLS_HOME WLS_Home_path cd ORACLE_HOMEbin .manageDIPServerConfig set -h dip_server_host -p dip_server_port -D weblogic_user -attribute oidhostport -value oid_host:oid_ssl_port The manageDIPServerConfig command prompts you for a password. For example: .manageDIPServerConfig set -h hostname -p 19523 -D weblogic -attribute oidhostport -value hostname.domain.com:24163 5. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example: opmnctl registerinstance -adminHost admin_server_host -adminPort admin_server_port -adminUsername username -adminPassword password -wlserverHome wlserver_home_location

18.3.4.5.4 Recovering Oracle Identity Federation to a Different Host Because Oracle Identity

Federation provides SSO functionality, if the host name on which Oracle Identity Federation runs is changed as part of loss of host recovery, it impacts remote partners. In that case, remote partners must make changes regarding the host name to continue to operate. It may take many days for remote partners to update their data and this may cause production delays that are unacceptable. Oracle strongly recommends that you do not change the host name of a standalone Oracle Identity Federation server. If a load balancer is part of the environment and the host where Oracle Identity Federation is being recovered is in the list of VIPs, then no host name changes are required. In the case of a standalone installation of Oracle Identity Federation, Oracle recommends using a new host with the same name to minimize the impact. However, if, for whatever reason, you must use a different host name for recovering Oracle Identity Federation, then the host name must be updated manually for Oracle Identity Federation and remote partners. To recover Oracle Identity Federation to a different host: 1. Recover the Managed Server, as described in Section 18.3.3.2 . 18-30 Oracle Fusion Middleware Administrators Guide 2. Recover Oracle Management Agent, as described in Section 18.3.5.3 . 3. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example: opmnctl registerinstance -adminHost admin_server_host -adminPort admin_server_port -adminUsername username -adminPassword password -wlserverHome wlserver_home_location 4. Provide the updated data to remote partners. 5. Modify the host name using Fusion Middleware Control: a. In the navigation pane, expand the farm and then Identity and Access. b. Select the Oracle Identity Federation instance. c. From the Oracle Identity Federation menu, choose Administration, then Server Properties. The Server Properties page is displayed. d. For Host, replace the old host name with the new host name. e. For Port, replace the port number if it has changed. f. For SOAP Port, replace the port number if it has changed. g. Click Apply. h. Restart the Managed Server to which Oracle Identity Federation is deployed: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url 6. If Oracle Identity Federation is acting as an SSL server, you must replace the SSL certificate presented by Oracle Identity Federation to clients with a new one that has the new host name. Otherwise, host name verification by clients may fail.

18.3.4.5.5 Recovering Oracle Identity Manager to a Different Host To recover Oracle Identity

Manager to a different host: 1. Restore the domain, as described in Section 18.3.2 . 2. Restore the Oracle home, as described in Section 18.2.3 . 3. Restore the database containing the OIM, OID, MDS, and SOAINFRA schemas, if necessary. See Section 18.2.10 . 4. Synchronize the Oracle Identity Manager database and the LDAP provider. See the Oracle Fusion Middleware Command Reference for Oracle WebLogic Server for more information. 5. Export the oim-config.xml file, using the weblogicExportMetadata.sh script. Then, edit the file, changing the host name or IP address for the SOA URL. Import the file into MDS, using the weblogicImportMetadata.sh script. 6. Create a new machine with the new host name, as described in Section 18.3.5.5 . 7. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6 . 18.3.4.5.6 Recovering Oracle Identity Navigator to a Different Host To recover Oracle Identity Navigator to a different host: