Recovering a Managed Server to a Different Host

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: Recovering Your Environment 18-31 1. Create a new machine with the new host name, as described in Section 18.3.5.5 . 2. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6 . 18.3.4.5.7 Recovering Oracle Access Manager to a Different Host To recover Oracle Access Manager to a different host: 1. Follow the instructions in Section 18.2.7.5 . 2. To restore the WLS Agent, restore the Managed Server, as described in Section 18.3.3.2 . 3. Log into the Oracle Access Manager console. 4. Select the Oracle Access Manager proxy server. 5. Modify Host, specifying the new host name. 6. If you have protected pages, you must reregister Oracle Single Sign-On or WebGate as partners with Oracle Access Manager, using the oamreg tool, described in About the Remote Registration Tool in the Oracle Fusion Middleware Administrators Guide for Oracle Access Manager with Oracle Security Token Service. Also see OSSO Remote Registration Request in the same manual. 7. Create a new machine with the new host name, as described in Section 18.3.5.5 . 8. Edit the WebGate configuration file, obAccessClient.xml, to update the host name for the Oracle Access Manager server. The file is located in the following directory: DOMAIN_HOMEoutputagentName 9. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6 . 18.3.4.5.8 Recovering Oracle Adaptive Access Manager to a Different Host To recover Oracle Adaptive Access Manager to a different host: 1. Follow the instructions in Section 18.2.7.6 . 2. Create a new machine with the new host name, as described in Section 18.3.5.5 . 3. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6 .

18.3.4.6 Recovering Oracle SOA Suite After Loss of Host

Note that when Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, take the steps described in Section 18.3.3.3 . Otherwise, follow the steps in this section. To recover the Oracle SOA Suite Managed Server to the same host, recover the Managed Server, as described in Section 18.3.3.1 . To recover the Oracle SOA Suite Managed Server to a different host after loss of host: 1. Before you recover, update the WSDL file to point to the new host name and port. 2. Recover the Managed Server, as described in Section 18.3.3.2 . 3. After you recover the Oracle SOA Suite Managed Server, take the following actions: – If the ant command is used to deploy composites, edit the deploy-sar.xml file, which is located in: UNIX ORACLE_HOMEbin Windows ORACLE_HOME\bin 18-32 Oracle Fusion Middleware Administrators Guide In the following line, replace the previous host name with the new host name: property name=wlsHost value=newhostname If a Load Balancer is used, do not modify this property. Instead, register the new host with the Load Balancer. – Change the host name in the soa-infra MBean: a. In Fusion Middleware Control, navigate to the Managed Server. b. From the WebLogic Server menu, choose System MBean Browser. c. Expand Application Defined MBeans, then oracle.as.soainfra.config, then Server: server_name and then SoaInfraConfig. Select soa-infra. d. In the Attributes tab, click ServerURL. If the ServerURL attribute contains a value, change the host name to the new host name. e. Click Apply. – Redeploy all applications which have the WSDL files updated to the new host name. If a Load Balancer is configured with the environment, take the following additional steps: 1. Log in to the Oracle WebLogic Server Administration Server. 2. In Domain Structure, navigate to Servers. For each Managed Server, select the Protocol tab, then the HTTP tab. 3. For Frontend Host, enter the new host name. 4. For Frontend HTTP Port and Frontend HTTPs Port, if applicable, enter the new port number. 5. Restart each Managed Server.

18.3.4.7 Recovering Web Tier Components to a Different Host

The Web tier consists of Oracle HTTP Server and Oracle Web Cache. The following topics describe how to recover these components to a different host: ■ Recovering Oracle HTTP Server to a Different Host ■ Recovering Oracle Web Cache to a Different Host

18.3.4.7.1 Recovering Oracle HTTP Server to a Different Host To recover Oracle HTTP

Server to a different host: 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 . 3. Modify the ServerName entry in the following file to have the new host name: Note: If there is no Load Balancer configured with the environment and Oracle SOA Suite must be recovered to a different host, then in-flight instances that are pending a response from task flow and asynchronous responses are not recovered. Oracle recommends that you use a Load Balancer to ensure that you can recover to a different host.