Creating a Record of Your Oracle Fusion Middleware Configuration

18-6 Oracle Fusion Middleware Administrators Guide e. 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.

18.2.6.2 Recovering a Managed Server When It Does Not Function Correctly

In this scenario, the Managed Server is running, but the file system for the Managed Server has been lost or corrupted. To recover the Managed Server: 1. Stop the Managed Server. For example: DOMAIN_HOMEbinstopManagedWeblogic.sh managed_server_name admin_url username password 2. Recover the Middleware home from the backup, if required: tar -xf mw_home_backup_092010.tar 3. Create a domain template jar file for the Administration Server, using the pack utility. For example: pack.sh -domain=MW_HOMEuser_projectsdomainsWLS_SOAWC -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. 4. Unpack the domain template jar file, using the unpack utility: unpack.sh -template=scratchaime1ms.jar -domain=MW_HOMEuser_projectsdomainsWLS_SOAWC -log=scratchlogsnew.log -log_priority=info 5. 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. Note: ■ For stage mode applications, the Administration server copies the application bits to the staged directories on the Managed Server hosts. ■ For nostage and external_stage mode applications, ensure that application files are available in the stage directories of the Managed Server. See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about stage, nostage and external_stage modes. Recovering Your Environment 18-7 6. Restart the Managed Server. For example: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url

18.2.6.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. In this case, you must restore the Managed Server from backup: 1. Restore the Managed Server from backup: cd ManagedServer_Home tar -xf managed_server_backup_092010.tar 2. Restart the Managed Server: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url

18.2.7 Recovering Components

For most components, the following topics describe how to recover a component: ■ Recovering a Component That Is Not Functioning Properly ■ Recovering a Component After Cluster Configuration Change For some components, you must take different steps. Table 18–1 lists those components and the section that describes the procedures to recover them. Note: ■ For stage mode applications, the Administration server copies the application bits to the staged directories on the Managed Server hosts. ■ For nostage and external_stage mode applications, ensure that application files are available in the stage directories of the Managed Server. See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications. Table 18–1 Recovery Procedures for Particular Components Component Procedure Oracle Access Manager Section 18.2.7.5 Oracle Adaptive Access Manager Section 18.2.7.6 Oracle BI Enterprise Edition Section 18.2.7.10 Oracle Business Intelligence Publisher Section 18.2.7.11 Oracle Business Process Management Section 18.2.7.7 Oracle Essbase Section 18.2.7.13 18-8 Oracle Fusion Middleware Administrators Guide

18.2.7.1 Recovering a Component That Is Not Functioning Properly

You can recover a component if the components files have been deleted or corrupted or if the component cannot be started or is not functioning properly because the components configuration was changed and committed. You may not be able to ascertain what change is causing the problem and you want to revert to an earlier version. ■ For Java components, such as Oracle SOA Suite, you recover the Managed Server, as described in Section 18.2.6 . ■ For system components, such as Oracle HTTP Server or Oracle Web Cache: 1. Stop 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. Start the component. For example, to start Oracle HTTP Server: opmnctl startproc ias-component=component_name For information on starting components, see Section 4.3 .

18.2.7.2 Recovering a Component After Cluster Configuration Change

You can recover components in a cluster when the components cannot be started or are not functioning properly because the configuration was changed and committed at the cluster level. You may not be able to ascertain what change is causing the problem and you want to revert to an earlier version. Oracle Data Integrator Section 18.2.7.17 Oracle Hyperion Calculation Manager Section 18.2.7.14 Oracle Hyperion Financial Reporting Section 18.2.7.15 Oracle Hyperion Smart View Section 18.2.7.16 Oracle Identity Manager Section 18.2.7.3 Oracle Identity Navigator Section 18.2.7.4 Oracle Imaging and Process Management Section 18.2.7.19 Oracle Information Rights Management Section 18.2.7.18 Oracle Real-Time Decisions Section 18.2.7.12 Oracle Universal Content Management Section 18.2.7.20 Oracle Universal Records Management Section 18.2.7.21 Oracle WebCenter Activity Graph Section 18.2.7.8 Oracle WebCenter Analytics Section 18.2.7.9 Table 18–1 Cont. Recovery Procedures for Particular Components Component Procedure