Click Apply to save the changes. Select Administration - Session Configuration at the top of the page. In the Session Binding section, select Cookie based Session Binding with any Set In the Navigator window, expand the Web Tier tree. Click on the Web App

14-40 Oracle Fusion Middleware High Availability Guide

3. Click OK to store the site.

4. Ensure that the site mysite.mycompany.com:44380 appears first in the list of site-to-server mappings.

5. Click Apply to save the changes.

Enable Session Binding The session binding feature in Oracle Web Cache is used to bind user sessions to a given origin server to maintain state for a period of time. Although almost all components running in a default Oracle Fusion Middleware mid-tier are stateless, session binding is required for Oracle Portal. Enabling session binding forces all the user requests to go to a specific Oracle Portal middle tier, resulting in a better cache hit ratio for the portal cache. Follow these steps to enable session binding:

1. Select Administration - Session Configuration at the top of the page.

2. Select the site mysite.mycompany.com:44380 from the drop down list.

3. In the Session Binding section, select Cookie based Session Binding with any Set

Cookie .

4. Click Apply to save the changes.

14.6.4.5.6 Change the Web Cache Passwords Web Cache passwords are randomly

generated, however they are required in later stages. It is therefore recommended that the Web Cache passwords be changed from the default value to a new known value. To change the default password, follow these steps:

1. In the Navigator window, expand the Web Tier tree.

2. Click on the component wc1.

3. From the drop down list at the top of the page, select Administration - Passwords.

4. Enter new invalidation and administration passwords, confirm them, and click Apply . 14.6.4.5.7 Restart Web Tier Oracle HTTP Server and Web Cache After making the previous changes, restart the Web Tier components using these commands: opmnctl stopall opmnctl startall

14.6.4.5.8 Register with Single Sign-On Server Perform these steps from the Single

Sign-On server: 1. Set the ORACLE_HOME variable to the Single Sign-On Server ORACLE_HOME location. 2. Execute ORACLE_HOMEssobinssoreg.sh ssoreg.bat on Windows with the following parameters: -site_name mysite.mycompany.com -mod_osso_url http:mysite.mycompany.com -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -config_file tmposso.conf -admin_info cn=orcladmin Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-41 -virtualhost -remote_midtier 3. Copy tmposso.conf to the mid-tier home location, which is: ORACLE_INSTANCE configOHSohs1 4. Restart Oracle HTTP server on APPHOST1 using the following command: opmnctl restartproc process-type=OHS 5. Log into the Single Sign-On Server using the following URL: http:login.mycompany.complsorasso 6. Go to the Administration page and then Administer Partner applications. Delete the entry for apphost1.mycompany.com.

14.6.4.5.9 Enabling the WebLogic Plug-in For security purposes, turn on the WebLogic

plug-in enabled flag for the domain. To do this, follow these steps: The Oracle web tier sits in front of the Oracle WebLogic server, routing requests from the Oracle HTTP Servers to the Oracle WebLogic managed servers. In this scenario, you must tell WebLogic that the Oracle WebLogic plug-in is being used. To do this: 1. Log on to the Oracle WebLogic Server Administration Console. 2. In the Domain Structure window, click on the domain name.

3. Click on the Web Applications tab.

4. Click Lock Edit.

5. Select the WebLogic Plugin Enabled box.

6. Save and activate the changes. 7. Restart the Administration Server.

14.6.4.5.10 Change Host Assertion in WebLogic Because the Oracle HTTP server acts as a

proxy for WebLogic, by default certain CGI environment variables are not passed through to WebLogic. These include the host and port. WebLogic must be told that it is using a virtual site name and port so that it can generate internal URLs appropriately. 1. Log into the Oracle WebLogic Server Administration Console using the following URL: http:apphost1.mycompany.com:7001console

2. Select Clusters from the home page or choose Environment - Clusters from the

Domain structure menu.

3. In the Change Center, click Lock Edit.

4. Click on the Cluster Name cluster_portal, cluster_forms, cluster_ reports, cluster_disco.

5. Select HTTP and enter the following values:

Parameter Value Frontend Host mysite.mycompany.com Frontend HTTP Port 80 14-42 Oracle Fusion Middleware High Availability Guide This ensures that any HTTPS URLs created from within WebLogic are directed to port 443 or 80 on the load balancer.

6. Click Activate Changes in the Change Center window to save the changes.

7. Restart the WLS_PORTAL, WLS_FORMS, WLS_REPORTS, WLS_DISCO Managed Servers using the following steps:

a. Select Servers from the Home page or Environment Servers from the

Domain structure menu. b. Select the Control tab. c. Select the box next to each Managed Server.

d. Choose Shutdown Force Shutdown Now.

e. Click Yes to shut down the Managed Server.

f. Once the Managed Server is shut down, select the box next to the Managed Server.

g. Click Start.

h. Click Yes to start the Managed Server.

14.6.4.6 Configure Oracle Portal for High Availability

The following steps are required to configure Oracle Portal only.

14.6.4.6.1 Rewire Portal Repository Follow these steps to rewire the Oracle Portal

repository: 1. Log into the domain using Oracle Fusion Middleware Enterprise Manager using the following URL: http:apphost1.us.oracle.com:7001em

2. Expand the Fusion Middleware menu on the left hand side.

3. Expand the Portal menu under Fusion Middleware menu.

4. Click Portal.

5. Right-click Portal and select settings Wire Configuration.

6. Enter the following information for Portal midtier: 7. Enter the following information for Web Cache: Frontend HTTPS Port 443 Parameter Value Host Enter the DNS name of the load balancer. For example: mysite.mycompany.com Port Enter the port that the load balancer is listening on. For example, 443 for SSL TerminationSite Enabled SLL or 80 for HTTP SSL Protocol Select this if SSL TerminationSite Enabled SSL is being used. Parameter Value