This section describes how to configure high availability for Oracle WebCenter products.
This section includes the following topics:
Section 10.1, "About Extending WebCenter Content: Inbound Refinery Components"
Section 10.3, "About Creating WebCenter Portal Components on Multiple Nodes"
Section 10.4, "About Creating a WebCenter Capture Domain with Oracle SOA"
Section 10.5, "About Scaling Out WebCenter Capture and Configuring OWSM"
For more information on WebCenter, see:
Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Content
Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Portal
Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Sites
Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Portal
WebCenter Content: Inbound Refinery components do not use WebLogic Server clustering for scale up and failover. You can deploy and configure multiple, independent Inbound Refinery Managed Servers for WebCenter Content to use.
You cannot scale up Oracle WebCenter Content.
In a WebCenter Portal high availability setup, you might see a delay of data appearing on the second node due to a 10-minute default refresh interval. For example, you may see this if you are trying to access a new Portal component that you just created on Node 2 if the Node 1 is processing the request.
If you create a WebCenter Capture domain with an Oracle SOA component, you must select the JRF-MAN-SVR and WSMPM-MAN-SVR server groups. These server groups ensure that the oracle JRF and Oracle Web Services Manager (OWSM) services target the Managed Servers you are creating.
OWSM uses cross-component wiring to auto-discover the Policy Manager in a domain. When you use the Configuration Wizard to create or update a domain that includes OWSM, Policy Manager URLs publish to the Local Service table. The OWSM Agent is automatically wired to the OWSM Policy Manager using endpoint entries published to the Local Service table. If, however, you change the domain using tools other than the Configuration Wizard (such as WebLogic Administration Console, Fusion Middleware Control, or WLST), any changes to the Policy Manager URL automatically publish to the Local Service table but the OWSM Agent client is not automatically bound to the new URL. In this case, you must manually bind OWSM Agent to the Policy Manager URL. For more information, see Verifying Agent Bindings Using Fusion Middleware Control in Oracle Fusion Middleware Securing Web Services and Managing Polices with Oracle Web Services Manager.
WebCenter Sites requires that an external component be up and running when trying to establish connections. If the external component is not up and running or the connection has timed out, WebCenter Sites doesn't reestablish the connection.
WebCenter Sites verifies that database connections are active and reestablishes connections only when they are active.
WebCenter Sites relies on multicast support to provide inCache replication across nodes in a clustered environment. For more about the inCache support in WebCenter Sites, see Using the inCache Framework in Oracle Fusion Middleware Administering Oracle WebCenter Sites.