Click Control. Select Adminserver by clicking on the checkbox next to it. Shut down Adminserver by selecting Force Shutdown Now under Shutdown Click Yes.

Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-57 5. Start the Administration Server from the local Domain Home. cd DOMAIN_HOMEbin .startWeblogic.sh 6. Transform the Administration Server instance to Cold Failover Cluster: Log into the Oracle WebLogic Server Administration Console. Create a Machine for the Virtual Host.

a. Select Environment, and then Machines.

b. In the Change Center, click Lock Edit.

c. Click New.

d. In the Name field, enter cfcvip.mycompany.com

e. Select the appropriate operating system.

f. Click OK.

g. Select the machine you just created.

h. Click the Servers tab.

i. Click Add.

j. Select an existing server, and associate it with this machine.

k. In the Select Server drop-down list, ensure AdminServer is selected.

l. Click Finish.

m. Click Activate Changes.

Configure the administration server to listen on cfcvip.mycompany.com.

a. Select Environment, and then Servers from the Domain Structure menu.

b. In the Change Center, click Lock Edit.

c. Click on the Administration Server AdminServer.

d. Change the Listen Address to cfcvip.mycompany.com

e. Click Save. Stop the Administration Server from the Administration Console.

a. Select Environment, and then Servers from the Domain Structure menu.

b. Click Control.

c. Select Adminserver by clicking on the checkbox next to it.

d. Shut down Adminserver by selecting Force Shutdown Now under Shutdown

pull-down menu.

e. Click Yes.

Ensure that the VIP is enabled on the system and start the Administration Server from the command line: cd DOMAIN_HOMEbin .startWeblogic.sh 7. Validate the Administration Server by accessing the consoles on the virtual IP: ■ http:cfcvip.mycompany.com:7001console 12-58 Oracle Fusion Middleware High Availability Guide ■ http:cfcvip.mycompany.com:7001em 8. Shut down the Administration Server on Node1 using the Administration Console. 9. Ensure that the shared disk is provisioned and mounted on Node1. 10. Pack the entire domain on Node1: cd ORACLE_COMMON_HOMEcommonbin .pack.sh -managed=false -domain=localdiskuser_projectsdomainsdomain_name -template=cfcdomaintemplate_all.jar -template_name=cfc_domain_template_all 11. Unpack it on the shared disk: .unpack.sh -domain=shareddiskuser_projectsdomainsdomain_name -template=cfcdomaintemplate_all.jar -app_dir=shareddiskuser_projectsapps -server_start_mode=prod 12. Product suite-specific changes: In the Oracle Identity Management Product Suite: ■ Back up the config.xml file, located in the shareddiskuser_ projectsdomainsdomain_nameconfig directory in this example. ■ Edit the config.xml file, located in the shareddiskuser_ projectsdomainsdomain_nameconfig directory in this example, and make the following changes to source-path: For dipapp, change source path to ORACLE_ HOMEldapodidipappdipapps.ear. For example: app-deployment nameDIP11.1.1.2.0name targetcluster_odstarget module-typeearmodule-type source-pathORACLE_HOMEldapodidipappdipapps.earsource_path security-dd-modelDDOnlysecurity-dd-model staging-modenostagestaging-mode app-deployment For the ODSM app, change the source path to ORACLE_ HOMEldapodsmodsm.ear For example: app-deployment nameodsm11.1.1.2.0name targetcluster_odstarget module-typeearmodule-type source-pathORACLE_HOMEldapodsmodsm.earsource-path security-dd-modelDDOnlysecurity-dd-model staging-modenostagestaging-mode app-deployment ■ For the OIF: Change the source path of OIF-APP to ORACLE_ HOMEfedinstalloif.ear: app-deployment nameOIF11.1.1.2.0name Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-59 targetcluster_oiftarget module-typeearmodule-type source-pathORACLE_HOMEfedinstalloif.earsource-path security-dd-modelAdvancedsecurity-dd-model staging-modenostagestaging-mode app-deployment Change the source path of oif-libs to ORACLE_ HOMElibjavasharedoracle.idm.oif11.1.1.0.0oif-libs.ea r: library nameoif-libs11.1.1.2.011.1.1.2.0name targetcluster_oiftarget module-typeearmodule-type source-pathORACLE_ HOME libjavasharedoracle.idm.oif11.1.1.0.0oif-libs.earsource-path security-dd-modelDDOnlysecurity-dd-model library 13. Start the Administration Server: cd shareddiskuser_projectsdomainsdomain_namebin .startWeblogic.sh 14. Validate the Administration Server by accessing the consoles on the virtual IP. ■ http:cfcvip.mycompany.com:7001console ■ http:cfcvip.mycompany.com:7001em

15. Shut down

the Administration Server. 16. Perform the following on Node1: mv localdiskuser_projectsdomainsdomain_name localdiskuser_projectsdomainsdomain_name_old mv localdiskuser_projectsapplicationsdomain_name localdiskuser_projectsapplicationsdomain_name_old cd ORACLE_COMMON_HOMEcommonbin .pack.sh -managed=true -domain=shareddiskuser_projectsdomainsdomain_name -template=cfcdomaintemplate_mngd.jar -template_name=cfc_domain_template_mngd .unpack.sh -domain=localdiskuser_projectsdomainsdomain_name -template=cfcdomaintemplate_mngd.jar 17. Copy the template to Node2: scp ORACLE_COMMON_HOMEcommonbincfcdomaintemplate_mngd.jar Node2:ORACLE_COMMON_HOMEcommonbin 18. Log in to Node2, and unpack on Node2 mv localdiskuser_projectsdomainsdomain_name localdiskuser_projectsdomainsdomain_name_old mv localdiskuser_projectsapplicationsdomain_name localdiskuser_projectsapplicationsdomain_name_old cd ORACLE_COMMON_HOMEcommonbin .unpack.sh -domain=localdiskuser_projectsdomainsdomain_name Note: These commands assume an applications directory exists under user_projects. 12-60 Oracle Fusion Middleware High Availability Guide -template=cfcdomaintemplate_mngd.jar 19. For Oracle Identity Manager Suite, the following addition steps are required: For DIP: a. Locate the applications directory in the Oracle WebLogic Server domain directory on Node1: MW_HOME user_projectsdomainsIDMDomainconfigfmwconfigserverswls_ ods1applications b. Copy the applications directory and its contents on Node1 to the same location in the domain directory on Node2. scp -rp MW_HOMEuser_projectsdomainsIDMDomainconfigfmwconfigservers wls_ods1applications userIDMHOST2:MW_HOMEuser_projectsdomainsIDMDomainconfigfmwconfig serverswls_ods2applications For OIF: a. Locate the applications directory in the Oracle WebLogic Server domain directory on Node1: MW_HOME user_projectsdomainsOIFDomainconfigfmwconfigserverswls_ oif1applications b. Copy the applications directory and its contents on Node1 to the same location in the domain directory on Node2. scp -rp MW_HOMEuser_projectsdomainsOIFDomainconfigfmwconfigservers wls_oif1applications userIDMHOST2:MW_HOMEuser_projectsdomainsOIFDomainconfigfmwconfig serverswls_oif2applications 20. Start the Administration Server: cd shareddiskuser_projectsdomainsdomain_namebin .startWeblogic.sh 21. Start the node manager if used on Node1 and Node2: cd WL_HOMEserverbin .startNodeManager.sh 22. Start the component Managed Servers on Node1 and Node2 from the Administration Server Console if Node Manager used or from the command line. 23. Validate the deployment using component-specific functional tests. 24. Test Administration Server failover. Failover the Administration Server manually to the second node: a. Stop the Administration Server process and any other process running out of a given Middleware Home. Note: These commands assume an applications directory exists under user_projects. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-61 b. Unmount the shared storage from Node1 where the Middleware Home or domain directory exists. c. Mount the shared storage on Node2, following storage specific commands. d. Disable the virtual IP on Node1: For Linux: ifconfig interface:index down In the following example, the IP address is disabled on the interface eth0: ifconfig eth0:1 down For Windows: netsh interface ip delete address interface addr=IP Address Where IP Address is the virtual IP address. In the following example, the IP address is enabled on the interface Local Area Connection. netsh interface ip delete address Local Area connection addr=130.35.46.17 e. Enable the virtual IP on Node2. f. Start the Administration Server process using the following command: DOMAIN_HOME binstartWebLogic.sh Where DOMAIN_HOME is the location of your domain directory. Validate access to both the Administration Server and Oracle Enterprise Manager Administration Console. Validate with component-specific tests. 25. After validation, fail back the Administration Server to the node where it will normally run this could be Node1 or Node2 and run normal operations. 12-62 Oracle Fusion Middleware High Availability Guide 13 Using Oracle Cluster Ready Services 13-1 13 Using Oracle Cluster Ready Services This chapter describes conceptual information as well as configuration procedures for Oracle Cluster Ready Services. It contains the following sections: ■ Section 13.1, Introduction to Oracle Clusterware