Recovering a Java Component to the Same Host

Recovering Your Environment 18-33 UNIX ORACLE_INSTANCEconfigOHSohs_namehttpd.conf Windows ORACLE_INSTANCE\config\OHS\ohs_name\httpd.conf

18.3.4.7.2 Recovering Oracle Web Cache to a Different Host To recover Oracle Web Cache

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. Edit the webcache.xml file, replacing the previous host name with the new host name. The file is located in: UNIX ORACLE_INSTANCEconfigWebCachewebcache_name Windows ORACLE_INSTANCE\config\WebCache\webcache_name 18.3.4.8 Recovering Oracle Portal, Oracle Reports, Oracle Forms Services, and Oracle Business Intelligence Discoverer to a Different Host The following topics describe how to recover these components to a different host: ■ Recovering Oracle Portal to a Different Host ■ Recovering Oracle Forms Services to a Different Host ■ Recovering Oracle Reports to a Different Host ■ Recovering Oracle Business Intelligence Discoverer to a Different Host

18.3.4.8.1 Recovering Oracle Portal to a Different Host To recover Oracle Portal to a

different host: 1. Restore the Middleware home, the domain directory, and the Oracle instance directory to the new host. See Section 18.3.3.2 for more information. 2. Recover Oracle Management Agent, as described in Section 18.3.5.3 . 3. If the instance has been deregistered, 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. Update the registration of the Oracle instance with the Administration Server, using the opmnctl updateinstanceregistration command on the new host. For example: opmnctl updateinstanceregistration -adminHost admin_server_host This command updates OPMNs instance.properties file. 5. Modify the following files, replacing the old host name with the new host name: ORACLE_INSTANCEconfigOHSohs_namehttpd.conf ORACLE_INSTANCEconfigOHSohs_namemoduleconfportal.conf 6. Run the ssoreg script, which is located in: Identity_Management_ORACLE_HOMEssobin Use the following command: 18-34 Oracle Fusion Middleware Administrators Guide ssoreg.sh -site_name newhost:http_listen_port -mod_osso_url http:newhost:http_listen_port -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -config_file any_new_file_path -admin_info cn=orcladmin -virtualhost -remote_midtier For example: ssoreg.sh -site_name example.com:8090 -mod_osso_url http:example.com:8090 -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -config_file tmploh_osso.conf -admin_info cn=orcladmin -virtualhost -remote_midtier 7. Copy the file from the previous step to the new host. 8. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 6: ORACLE_INSTANCEconfigOHSohs1moduleconfmod_osso.conf For example: IfModule mod_osso.c OssoIpCheck off OssoSecureCookies off OssoIdleTimeout off OssoConfigFile tmppath_of_file_created 9. Edit the following files, replacing the previous host name with the new host name: ■ webcache.xml. This file is located in: UNIX ORACLE_INSTANCEconfigWebCachewebcache_name Windows ORACLE_INSTANCE\config\WebCache\webcache_name Replace all occurrences of the previous host name with the new host name. ■ instance.properties. The file is located in: UNIX ORACLE_INSTANCEconfigOPMNopmn Windows ORACLE_INSTANCE\config\OPMN\opmn In the following line, replace the previous host name with the new host name if the Administration Server host name has changed. adminHost=host_name 10. If the published host used to access Oracle Portal is changing, take the following steps. This could happen if you have a single node install which contains both Oracle Web Cache and WLS_PORTAL, and those processes must move to a different host. Another scenario is when you have Oracle Web Cache running on a node remotely from WLS_PORTAL, and Oracle Web Cache must move to a different host. In both these cases, take the following steps to update the Published Host information within Oracle Portal. Note: If you have a load balancer or reverse proxy configuration, the steps are not needed. a. Recursively delete all content from the following directory, but do not delete the directory itself: ORACLE_INSTANCEportalcache b. Log in to Fusion Middleware Control. Expand the farm and right-click Portal. Then, choose Settings, then Wire Configuration. c. In the Portal Midtier section, update Published Host with the new host name.