Recovering Oracle Data Integrator

18-20 Oracle Fusion Middleware Administrators Guide -Dweblogic.system.StoreBootIdentity=true e. Start the Managed Servers, specifying the Administration URL for the host: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url f. Start Node Manager: java weblogic.WLST wls:offline startNodeManager

18.3.2.2 Recovering the Administration Server to a Different Host

In this scenario, the Administration Server is running on Host A and the Managed Server is running on Host B. Host A has failed for some reason and the Administration Server must be moved to Host C. To recover the Administration Server to a different host: 1. Recover the Middleware home to Host C the new Host: cd MW_HOME tar -xf mw_home_backup_092010.tar 2. If the domain directory does not reside in the Middleware home, recover the domain directory from backup: cd DOMAIN_HOME tar -xf domain_backup_092010.tar 3. If the Administration Server has a Listen address, create a new machine with the new host name, as described in Section 18.3.5.5 . 4. Start Node Manager on Host C if it was configured on the original host: java weblogic.WLST wls:offline startNodeManager 5. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true 6. Start the Managed Servers. The section Restarting a Failed Administration Server in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server describes different ways to restart them, depending on how they were configured. One option is to use the following script, specifying the Administration URL of the new host: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url 7. Ensure that additional application artifacts are available. For example, if the deployment mode is nostage or external_stage, applications may reside in directories outside of the domain directory. Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server. If the application is staged, the Administration Server copies the application bits to the staged directories on the Managed Server hosts. Recovering Your Environment 18-21 8. Update Oracle Inventory, as described in Section 18.3.5.7 . 9. If your environment contains Oracle HTTP Server, modify the mod_wl_ohs.conf file, as described in Section 18.3.5.4 . 10. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2 . 11. Oracle Management Service, which is part of Fusion Middleware Control, is on the original host and is recovered to the new host when you restore the Administration Server. Oracle Management Agent connects to Oracle Management Service to monitor certain components. If your environment contains components, such as Oracle Internet Directory and Oracle Virtual Directory, that use Oracle Management Agent, but they are located on a different host, you must take the following steps on each host containing the components. For example, the Administration Server was on Host A, but is restored, along with Oracle Management Service, to Host B. Oracle Internet Directory is on Host C and Oracle Virtual Directory is on Host D. You must take these steps on both Host C and Host D. a. Edit the following file: UNIX ORACLE_INSTANCEEMAGENTemagent_namesysmanconfigemd.properties WindowsORACLE_INSTANCE\EMAGENT\emagent_name\sysman\config\emd.properties Update the following entries, replacing the host name with the new host for the Administration Server: emdWalletSrcUrl=http:newhost.domain.com:portemwalletsemd REPOSITORY_URL=http:newhost.domain.com:portemupload b. Shut down and restart the EM Agent process: cd ORACLE_INSTANCEEMAGENTemagent_dir .emctl stop agent .emctl start agent .emctl status agent The status command shows the REPOSITORY_URL pointing to the new host. Now you can start and stop the Managed Server on Host B using the Administration Console running on Host C. If you are recovering the Administration Server for a Web Tier installation, see Section 18.3.5 for information about additional actions you must take.

18.3.3 Recovering After Loss of Managed Server Host

If you lose a host that contains a Managed Server, you can recover it to the same host or a different host, as described in the following topics: ■ Recovering a Managed Server to the Same Host ■ Recovering a Managed Server to a Different Host ■ Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory This section pertains when Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server.