Part II Configuring WebCenter Sites Components
After you install and configure Oracle WebCenter Sites, you need to configure its component applications. See the topics in this section to configure component applications.
- Sites Configuration Setup
Before configuring the WebCenter Sites Configuration Setup, ensure the you meet all the prerequisites. - Configuring WebCenter Sites
After you configure the Oracle WebCenter Sites Managed Servers, you can configure a WebCenter Sites instance by completing the browser-based WebCenter Sites Configurator. WebCenter Sites runtime consists of WebCenter Sites and CAS web applications (WAR files) and the following components shared across cluster members: aconfig
directory, adata
directory, and a database instance. - Configuring Site Capture
After you configure Oracle WebCenter Sites: Site Capture Managed Servers, you can configure Site Capture with the Site Capture Configurator. You can also integrate Site Capture with the WebCenter Sites publishing process. - Configuring Visitor Services
After you set up the Oracle WebCenter Sites: Visitor Services Managed Servers, you can configure Visitor Services with the browser-based Visitor Services Configurator. Visitor Services runtime consists ofvisitors-webapp
applications (WAR files), aconfig
directory, a database instance, sample bundle code, providers, and a visitors client. - Configuring Remote Satellite Server
After you set up a WebLogic domain for Oracle WebCenter Sites: Satellite Server, you can run the Satellite Server Configurator to complete the configuration process. - Switching to External Authentication
For maximum security in production environments, Oracle recommends integrating Oracle WebCenter Sites with Oracle Access Management, for an advanced identity management solution and a seamless single sign-on user experience. You also have the option of integrating WebCenter Sites with an external LDAP authentication provider directory. - Setting Up a CAS Cluster
You can set up a Central Authentication Server (CAS) cluster in the same WebLogic domain as Oracle WebCenter Sites, in a different WebLogic domain on the same machine, or for high availability, in a different WebLogic domain on a different machine. - Setting Up a Cluster
For high availability, you can set up a WebCenter Sites cluster in a WebLogic domain with a primary cluster node on one machine and one or more secondary cluster nodes on the same or different machines. The first WebCenter Sites Managed Server you create is the primary node, and any additional WebCenter Sites Managed Servers in the same domain are secondary nodes. - Moving the Shared File System to a Database
WebCenter Sites can leverage a database to store its shared file system using the Java Nonblocking I/O (NIO) API. This eliminates the need for a network file share in a clustered environment and allows file locking to be handled by a Coherence cache. - Switching from Test Mode to Production Mode
After you install and configure an Oracle WebCenter Sites domain in a Fusion Middleware test environment, you can switch WebCenter Sites (and its component applications) to an equivalent production environment.