Configuring Oracle HTTP Server on WEBHOST1

Configuring High Availability for Enterprise Content Management 11-31 Click Next. 15. On the Specify Webtier Port Details screen: ■ Select Specify Custom Ports. If you specify a custom port, select Specify Ports using Configuration File and then use the Browse function to select the file. ■ Enter the Oracle HTTP Server port, for example, 7777. Click Next. 16. On the Oracle Configuration Manager screen, enter the following: ■ Email Address : Provide the email address for your My Oracle Support account ■ Oracle Support Password: Provide the password for your My Oracle Support account. ■ I wish to receive security updates via My Oracle Support : Click this checkbox. 17. On the Installation Summary screen, ensure that the selections are correct. If they are not, click Back and make the necessary fixes. After ensuring that the selections are correct, click Next. 18. On the Installation Progress screen on UNIX systems, a dialog appears that prompts you to run the oracleRoot.sh script. Open a window and run the script, following the prompts in the window. Click Next. 19. On the Configuration Progress screen, multiple configuration assistants are launched in succession; this process can be lengthy.

20. On the Configuration Completed screen, click Finish to exit.

11.3.4.2 Configuring Oracle HTTP Server on WEBHOST1

After installing Oracle HTTP Server on WEBHOST1, add the following lines to the OHS_HOMEinstancesohs_instance1configOHSohs1mod_wl_ ohs.conf file: UCM Location cs WebLogicCluster ecmhost1:16200,ecmhost2:16200 SetHandler weblogic-handler WLCookieName JSESSIONID Location Location adfAuthentication WebLogicCluster ecmhost1:16200,ecmhost2:16200 SetHandler weblogic-handler WLCookieName JSESSIONID Location URM Location urm WebLogicCluster ecmhost1:16250,ecmhost2:16250 SetHandler weblogic-handler WLCookieName JSESSIONID Location 11-32 Oracle Fusion Middleware High Availability Guide Location urmadfAuthentication WebLogicCluster ecmhost1:16250,ecmhost2:16250 SetHandler weblogic-handler WLCookieName JSESSIONID Location IBR Location ibr WebLogicCluster ecmhost1:16300,ecmhost2:16300 SetHandler weblogic-handler WLCookieName JSESSIONID Location Location ibradfAuthentication WebLogicCluster ecmhost1:16300,ecmhost2:16300 SetHandler weblogic-handler WLCookieName JSESSIONID Location IPM Application Location imaging SetHandler weblogic-handler WebLogicCluster ECMHOST1VHN1:16000,ECMHOST2VHN1:16000 Location AXF WS Invocation Location axf-ws SetHandler weblogic-handler WebLogicCluster ECMHOST1VHN1:16000,ECMHOST2VHN1:16000 Location These lines configure Oracle HTTP Server on WEBHOST1 to route requests to the clustered applications on ECMHOST1 and ECMHOST2. After adding these lines, restart Oracle HTTP Server, and then ensure that the applications can be accessed at: http:WEBHOST1:7777cs http:WEBHOST1:7777urm http:WEBHOST1:7777imaging Note: The value of WLCookieName is different in earlier software releases. The value was IDCCS_SESSIONID in earlier releases but is JSESSIONID in this release. Note: More Location tags may need to be added depending on how the applications will be used. For example, Oracle UCM also requires access at _dav for WebDav access and idcws for web services access. Consult the product documentation for more details. Configuring High Availability for Enterprise Content Management 11-33

11.3.5 Configuring the Load Balancer

Configure the load balancer so that the virtual host for example, ucm.mycompany.com routes to the available Oracle HTTP Servers using round-robin load balancing. You should also configure the load balancer to monitor the HTTP and HTTPS listen ports for each Oracle HTTP Server. Verify that Oracle Content Server can be accessed at http:WEBHOST1:7777cs.

11.3.6 Installing and Configuring ECMHOST2

This section describes the installation and configuration steps to perform on ECMHOST2.

11.3.6.1 Installing Oracle WebLogic Server on ECMHOST2

To install Oracle WebLogic Server on ECMHOST2, perform the steps in Section 11.3.3.1, Installing Oracle WebLogic Server on ECMHOST1 on ECMHOST2.

11.3.6.2 Installing ECM on ECMHOST2

To install Oracle ECM on ECMHOST2, perform the steps in Section 11.3.3.2, Installing Oracle ECM on ECMHOST1 on ECMHOST2.

11.3.6.3 Using pack and unpack to Join the Domain on ECMHOST1

The pack and unpack commands are used to enable the WLS_UCM2 managed server on ECMHOST2 to join the ECM domain on ECMHOST1. First, execute the pack command on ECMHOST1: pack -managed=true -domain=u01apporacleproductWLS11Guser_projectsdomains ecmdomain -template=ecm_template.jar -template_name=my ecm domain After copying the ecm_template.jar file to ECMHOST2, execute the unpack command on ECMHOST2: unpack -domain=u01apporacleproductWLS11Guser_projectsdomainsecmdomain -template=ecm_template.jar

11.3.6.4 Start Node Manager and the WLS_UCM2 Server on ECMHOST2

To start Node Manager on ECMHOST2, use this command: ECMHOST2 MW_HOMEoracle_commoncommonbinsetNMProps.sh ECMHOST2 WL_HOMEwlserver_10.3binstartNodeManager.sh Access the Administration Console at http:ECMHOST1:7001console. In the Administration Console, start the WLS_UCM2 managed server.

11.3.6.5 Start the Managed Servers on ECMHOST2

Access the Administration Console at http:ECMHOST2:7001console. In the Administration Console, start the WLS_UCM2, WLS_URM2, and WLS_IPM2 managed servers.

11.3.6.6 Configure the WLS_UCM2 Managed Server

Access the WLS_UCM2 configuration page at http:ECMHOST2:16200cs.