Recovering Oracle HTTP Server to a Different Host To recover Oracle HTTP

Recovering Your Environment 18-39 Identity_Management_ORACLE_HOMEssobin Use the following command: 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 6. Copy the file from the previous step to the new host. 7. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 5: ORACLE_INSTANCEconfigOHSohs1moduleconfmod_osso.conf For example: IfModule mod_osso.c OssoIpCheck off OssoSecureCookies off OssoIdleTimeout off OssoConfigFile tmppath_of_file_created

18.3.4.9 Recovering Oracle BI Enterprise Edition to a Different Host

You can recover Oracle BI Enterprise Edition to a different host. The following topics describe how to move Oracle BI EE to a different host with the same name: ■ Recovering Oracle BI Enterprise Edition to a Different Host in a Non-Clustered Environment ■ Recovering Oracle BI Enterprise Edition to a Different Host in a Clustered Environment

18.3.4.9.1 Recovering Oracle BI Enterprise Edition to a Different Host in a Non-Clustered

Environment The steps you take to recover Oracle BI EE to a different host depends on the operating system. Note that the host must have the same name as the original host. ■ On UNIX, take the following steps: 1. Restore the Middleware home, as described in Section 18.2.1 . 2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6 . ■ On Windows, take the following steps: 1. Restore the Middleware home from backup, as described in Section 18.2.1 , overwriting the Middleware home that you created with the new installation. 2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6 . 3. Install the C++ libraries from Microsoft, by executing the following file: 18-40 Oracle Fusion Middleware Administrators Guide Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe 4. Import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4 .

18.3.4.9.2 Recovering Oracle BI Enterprise Edition to a Different Host in a Clustered

Environment In this scenario, you have an Oracle BI EE cluster on two hosts, Host A and Host B. Host A must be replaced for some reason, such as a host crash, and you must recover to Host C. Take the following steps: 1. Restore the Middleware home from backup to Host C, as described in Section 18.2.1 . 2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6 . 3. On Windows, install the C++ libraries from Microsoft, by executing the following file: Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe 4. On Windows, import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4 . 5. If the failed node contained the Administration Server, recover it, as described in steps 1 through 5 in Section 18.3.2.2 . 6. Scale out the Oracle BI EE system, as described in Scaling Out the BI System on APPHOST2 in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. Note the following: ■ When you enter the directory specifications for the Domain Home and Applications Home, enter specifications for directories that do not yet exist or that are empty. ■ If the Domain Home field is empty, update the following file with the domain directory: MW_HOMEwlserver_10.3commonnodemanagernodemanager.domains Before you start Node Manager, take the following steps: a. Stop Node Manager process if it is running. b. Run the setNMProps.sh script, which is located in the ORACLE_ COMMON_HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: cd ORACLE_COMMON_HOMEcommonbin .setNMProps.sh c. Restart Node Manager and enable dynamic registration using the following commands: cd WL_HOMEserverbin export JAVA_OPTIONS=-DDomainRegistrationEnabled=true .startNodeManager.sh