Recovering the Administration Server to a Different Host

Recovering Your Environment 18-27

18.3.4.2 Recovering a Java Component to a Different Host

To recover a Java component to a different host, such as Oracle SOA Suite: 1. Recover the Managed Server, as described in Section 18.3.3.2 . 2. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2 . However, note that some components require additional steps, as noted in Table 18–2 .

18.3.4.3 Recovering a System Component to the Same Host

To recover a system component, such as Oracle HTTP Server, to the same host, you take the following general steps. However, note that some components require additional steps, as noted in Table 18–2 . 1. Stop all relevant processes. That is, stop all processes that are related to the component. For example, to stop Oracle HTTP Server: opmnctl stopproc ias-component=component_name For information on stopping components, see Section 4.3 . 2. Recover the component-specific files from backup. Section 16.5 lists the directories and files needed for each component. For example, to recover Oracle HTTP Server files, you recover the following directories: ORACLE_INSTANCEconfigOHScomponent_name ORACLE_INSTANCEdiagnosticslogsOHScomponent_name 3. If the Oracle instance home has been deregistered from the Administration Server, register the Oracle instance: opmnctl registerinstance -adminHost admin_server_host -adminPort admin_server_port -adminUsername username -adminPassword password -wlserverHome wlserver_home_location If only the file system is being recovered, you do not need to register the Oracle instance. 4. Start all relevant processes, as described in Section 4.3 .

18.3.4.4 Recovering a System Component to a Different Host

To recover a system component, such as Oracle HTTP Server, to a different host, you take the following general steps. However, note that most components require additional steps, as noted in Table 18–2 . 1. Recover the Middleware home, as described in Section 18.2.1 . 2. Start all relevant processes. Section 4.3 explains how to start components. 3. Update the registration of the Oracle instance with the Administration Server, using the opmnctl updateinstanceregistration command on the new host. For example: opmnctl updateinstanceregistration -adminHost admin_server_host This command updates OPMNs instance.properties file. 4. Update the registration of the component with the Administration Server, using the opmnctl updatecomponentregistration command on the new host. For 18-28 Oracle Fusion Middleware Administrators Guide example, to update the registration for Oracle Virtual Directory, use the following command: opmnctl updatecomponentregistration -Host new_host -Port nonSSLPort -componentName ovd1 -componentType OVD 5. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2 .

18.3.4.5 Recovering Identity Management Components to a Different Host

For most Identity Management components, you recover the Managed Server, as described in Section 18.3.3.2 . Some components require additional steps to recover the components to a different host, as described in the following topics: ■ Recovering Oracle Internet Directory to a Different Host ■ Recovering Oracle Virtual Directory to a Different Host ■ Recovering Oracle Directory Integration Platform to a Different Host ■ Recovering Oracle Identity Federation to a Different Host ■ Recovering Oracle Identity Manager to a Different Host ■ Recovering Oracle Identity Navigator to a Different Host ■ Recovering Oracle Access Manager to a Different Host ■ Recovering Oracle Adaptive Access Manager to a Different Host

18.3.4.5.1 Recovering Oracle Internet Directory to a Different Host To recover Oracle Internet

Directory to a different host: 1. Recover the component, as described in Section 18.3.4.4 . 2. On UNIX and Linux systems, before you attempt to start Oracle Internet Directory, set the following file to have root permission: ORACLE_HOMEbinoidldapd For example: chown root oidldapd chmod 4710 oidldapd 3. Recover Oracle Management Agent, as described in Section 18.3.5.3 . 4. If the Managed Server on which Oracle Directory Services Manager is deployed is moved to different host and if SSL is enabled, you must delete the following file on the new host: DOMAIN_HOMEserverswls_ods1tmp_WL_userodsm_ 11.1.1.1.0randomidwarconfodsm.cer Oracle Directory Services Manager uses this file as its keystore and trust store and the password is stored in JKS. However, when Oracle Directory Services Manager is copied to another host and is started, it generates a different password. If you delete the file, Oracle Directory Services Manager creates a new file when it starts, with the new password.

18.3.4.5.2 Recovering Oracle Virtual Directory to a Different Host To recover Oracle Virtual

Directory to a different host: