Deploying the ADF Application Validating Access through Oracle HTTP Server

Configuring High Availability for Oracle ADF and WebCenter Applications 6-27 adfc:adf-controller-configadfc:adf-scope-ha-supporttrueadfc:adf-scope-ha-sup portadfc:adf-controller-config Applications must also have replication enabled. Oracle WebLogic Server allows several types of persistent stores for replication. For more information on persistent stores, see the Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server manual. The ADF application can be enabled by for this by default with the following setting in the weblogic.xml file: session-descriptor persistent-store-typereplicated_if_clusteredpersistent-store-type session-descriptor The replicated_if_clustered setting disables replication for standalone application environments, and uses in-memory replication within a cluster environment. Ensure that any custom application is configured for in-memory replication.

6.2.9.4 Deploying the ADF Application

After the cluster has been set up, the ADF application can be deployed. Be aware of the following: ■ Deploy the ADF application to an EAR file and deploy using the Administration Server Console. ■ Ensure that the deployment is to a cluster. ■ If your application uses MDS, register the MDS with the domain using the instructions in the Registering a Database-Based MDS Repository section in the Oracle Fusion Middleware Administrators Guide manual. 6.2.9.5 Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers Enable Oracle HTTP Server to route to the Administration Server that contains Oracle WebCenter Managed Servers by setting the WebLogicCluster parameter to the list of nodes in the cluster. Follow these steps: 1. Add the following lines to the OHS_HOMEinstancesohs_ instance1configOHSohs1mod_wl_ohs.conf file: Spaces Location applicationMountpoint WebLogicCluster apphost1.com:8888,apphost2.com:8889 SetHandler weblogic-handler Location 2. Restart Oracle HTTP Server on WEBHOST1: WEBHOST1 OHS_HOMEinstancesohs_instance1binopmnctl restartproc ias-component=OHS_COMPONENT1

6.2.9.6 Validating Access through Oracle HTTP Server

Verify the URLs to ensure that appropriate routing and failover is working from the HTTP Server to Oracle WebCenter cluster. Follow these steps: 6-28 Oracle Fusion Middleware High Availability Guide 1. Start WC_Spaces1, WC_Spaces2, WC_Collaboration1, WC_Collaboration2, WC_Portlet1, and WC_Portlet2 from the WebLogic Server Administration Console as follows: a. Access the Administration Console at the following URL: http:APPHOST1console b. Click on one of the Managed Servers, for example, WC_Spaces1.

c. Select the Control tab.

d. Select Start to start the Managed Server.

e. Repeat the previous steps for each Managed Server. f. Verify direct access to the Managed Servers using the following URLs: apphost1:8888applicationMountpoint apphost2:8888applicationMountpoint apphost1:8889applicationMountpoint apphost2:8889applicationMountpoint 2. While WLS_ADF2 is running, stop WLS_ADF1 from Oracle WebLogic Server Administration Console. 3. Access the following URL and verify the appropriate functionality: WebHost1:7777applicationMountpoint 4. Start WLS_ADF1 from the WebLogic Server Administration Console. 5. Stop WLS_ADF2. 6. Access the following URL and verify the appropriate functionality: WebHost2:7777applicationMountpoint

6.2.10 Scaling the Topology

You can scale out and scale up an Oracle ADF topology. When you scale up the topology, you add new managed servers to nodes that are already running one or more managed servers. When you scale out the topology, you add new managed servers to new nodes.

6.2.10.1 Scaling Up the Topology Adding Managed Servers to Existing Nodes

In this case, you already have a node that runs a managed server configured with Oracle ADF. The node contains a Middleware home in shared storage. You can use the existing installations Middleware home, and domain directories for creating new servers. There is no need to install Oracle Fusion Middleware binaries in a new location, or to run pack and unpack. Follow these steps for scaling up the topology: 1. Using the Oracle WebLogic Server Administration Console, clone WLS_ADF1 into a new managed server. The source managed server to clone should be one that already exists on the node where you want to run the new managed server. To clone a managed server: