Recovering Oracle Identity Manager

18-16 Oracle Fusion Middleware Administrators Guide To recover the cluster membership: 1. Stop all processes, such as the Managed Servers and the Administration Server. For example, to stop the Administration Server on Linux: DOMAIN_HOMEbinstopWeblogic.sh username password [admin_url] 2. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location: DOMAIN_HOMEconfig 3. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true The deleted member is now back in the cluster. 4. Start all processes, such as the Managed Servers. For example, to start the Managed Server on Linux, use the following script: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url 5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST: startclusterName, Cluster The deleted member is now part of the cluster. 6. Start all cluster members if they are not started: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url

18.2.9 Recovering Applications

The following topics describe how to recover an application: ■ Recovering Application Artifacts ■ Recovering a Redeployed Application That Is No Longer Functional ■ Recovering an Undeployed Application ■ Recovering a Composite Application Note the following about recovering applications: ■ If the application is staged, the Administration server copies the application bits to the staged directories on the Managed Server hosts. ■ If the deployment mode is nostage or external_stage, ensure that additional application artifacts are available. For example, 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 Caution: Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost. Recovering Your Environment 18-17 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.

18.2.9.1 Recovering Application Artifacts

If an applications artifacts, such as the .ear file, have been lost or corrupted, you can recover the application. To recover the application: 1. Start the Managed Server to which the application was deployed. For example: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url This synchronizes the configuration with the Administration Server. On each Managed Server restart, the configuration and application artifacts are retrieved from the Administration Server.

18.2.9.2 Recovering a Redeployed Application That Is No Longer Functional

If a Java EE application was redeployed to a Managed Server whether or not the Managed Server is part of a cluster and the application is no longer functional, you can recover it. To recover the application: 1. Recover the application files from backup, if needed. 2. Redeploy the old version of the application from the backup. You cannot just copy the original ear file. Even if the original ear file from the backup is copied back to the Managed Server stage directory and you restart the Managed Server, the application is still not recovered. You must redeploy the original version.

18.2.9.3 Recovering an Undeployed Application

If a deployed application was undeployed from Oracle WebLogic Server, you can recover it. To recover the application: 1. Recover the application files from backup, if needed. 2. Redeploy the old version of the application from the backup. If the application was deployed to a cluster, redeploy the application to the same cluster. You cannot just copy the original ear file. Even if the original ear file from the backup is copied back to the Managed Server stage directory and you restart the Managed Server, the application is still not recovered. You must redeploy the original version.

18.2.9.4 Recovering a Composite Application

A new version of a composite application such as SOA application was redeployed to a Managed Server or cluster. The application is no longer functional. To recover the application: 1. Recover the application files from backup, if needed. See Also: Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications