Recovering a Composite Application

18-24 Oracle Fusion Middleware Administrators Guide pack.sh -domain=MW_HOMEuser_projectsdomainsdomain_name -template=scratchtemp.jar -template_name=test_install -template_author=myname -log=scratchlogsmy.log -managed=true Specifying the -managed=true option packs up only the Managed Servers. If you want to pack the entire domain, omit this option. b. Unpack the domain template jar file on Host C, using the unpack utility: unpack.sh -template=scratchaime1ms.jar -domain=MW_HOMEuser_projectsdomainsdomain_name -log=scratchlogsnew.log -log_priority=info If you are recovering to a different domain home, use the -app_dir switch in the unpack command. 4. Ensure that the application artifacts are accessible from the Managed Server host. That is, if the application artifacts are not on the same server as the Managed Server, they must be in a location accessible by the Managed Server. 5. Start Node Manager on Host C, if it is not started: java weblogic.WLST wls:offline startNodeManager 6. Using WLST, connect to the Administration Server and then enroll Node Manager running in the new host with the Administration Server: connectusername,password,http:host:port nmEnrollMW_HOMEuser_projectsdomainsdomain_name, MW_HOMEwlserver_ncommonnodemanager 7. Change the Managed Server configuration to point to the new host: a. In the WebLogic Server Administration Console, create a machine, which is a logical representation of the computer that hosts one or more WebLogic Servers, and point it to the new host. From the Home page, select Machines. Then, click New. Follow the directions in the Administration Console help. If you identify the Listen Address by IP address, you must disable Host Name Verification on the Administration Servers that access Node Manager. For more information and instructions, see Using Hostname Verification in Oracle Fusion Middleware Securing Oracle WebLogic Server. b. Change the Managed Server configuration to point to the new machine. From the left pane of the Console, expand Environment and then Servers. Then, select the name of the server. Select the Configuration tab, then the General Note: ■ For applications that are deployed in nostage and external_stage mode, copy the application artifacts from the Administration Server host directory. ■ For applications that are deployed in stage mode, the Administration server copies the application bits to the staged directories on the Managed Server hosts. See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications. Recovering Your Environment 18-25 tab. In the Machine field, select the machine to which you want to assign the server. Change Listen Address to the new host. If the listening address was set to blank, you do not need to change it. 8. Start the Managed Server. For example: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url The Managed Server connects to the Administration Server and updates its configuration changes. 9. Update Oracle Inventory, as described in Section 18.3.5.7 . 10. If your environment contains Oracle HTTP Server, modify the mod_wl_ohs.conf file, as described in Section 18.3.5.4 . 11. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2 . Now you can start and stop the Managed Server on Host C using the Administration Server running on Host A.

18.3.3.3 Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory

When Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, you must restore the Managed Server directory. For example, a domain contains two Managed Servers, one of which contains Oracle SOA Suite, but neither of the Managed Servers directories are in the same directory structure as the Administration Server. To recover to the same host or a different host, use the procedures in Section 18.2.6.3 .

18.3.4 Recovering After Loss of Component Host

If you lose a host that contains a component and its Managed Server, if applicable, you can recover most components to the same host or a different host using the procedures described in the following topics: ■ Recovering a Java Component to the Same Host ■ Recovering a Java Component to a Different Host ■ Recovering a System Component to the Same Host ■ Recovering a System Component to a Different Host Some components require additional actions, which are described in the sections listed in Table 18–2 . Table 18–2 Recovery Procedures for Loss of Host for Particular Components Component Procedure Oracle Access Manager Section 18.3.4.5.7 Oracle Adaptive Access Manager Section 18.3.4.5.8 Oracle BI Discoverer Section 18.3.4.8.4 Oracle BI Enterprise Edition Section 18.3.4.9 Oracle BI Publisher Section 18.3.4.10