Oracle WebCenter Single-node Architecture Oracle WebCenter State and Configuration Persistence

Configuring High Availability for Oracle ADF and WebCenter Applications 6-33 ■ Search - Provides a means of searching tags, services, the application, or an entire site. This includes integrating Oracle Secure Enterprise Search for Oracle WebCenter searches. ■ Tags - Provides a means of assigning one or more personally relevant keywords to a given page or document. ■ Worklists - Provides a means of viewing notifications from the various workflows established in your enterprise. For information about how to configure these Oracle WebCenter services, see Oracle Fusion Middleware Administrators Guide for Oracle WebCenter.

6.3.1.2 Oracle WebCenter Single-node Architecture

Oracle WebCenter installation creates a WebCenter directory under the Middleware home directory. The installation creates a WebCenter domain wc_domain, which contains the Administration Server and four WebLogic Managed Servers: WC_ Spaces1 which hosts Oracle WebCenter Spaces, WC_Portlets which hosts Oracle WebCenter Portlets, WC_Collaboration1 which hosts Oracle WebCenter Discussion server, WC_Utilities1 which hosts Oracle WebCenter Analytics, Oracle WebCenter Activity Graph, and Oracle WebCenter Personalization Server, and any additional WebCenter services that you choose to integrate. An optional fifth managed server an application server must be used to run Oracle WebCenter Portal Applications. When you create additional managed servers, they are provisioned with the appropriate libraries to enable them to draw upon the same external resources as Oracle WebCenter Spaces. For more information about managed servers, see “Understanding Oracle Fusion Middleware Concepts” in the Oracle Fusion Middleware Administrators Guide. Figure 6–4 shows a basic single-node Oracle WebCenter architecture. Figure 6–4 Basic Single-Node Oracle WebCenter Architecture

6.3.1.3 Oracle WebCenter State and Configuration Persistence

Oracle WebCenter Spaces runs as a Java EE application. Application state and configuration persist to the MDS repository. Local memory holds user session information. In a cluster environment, this state replicates to other cluster members. All out-of-the-box Oracle WebCenter Portlets use the database to persist customizations. Oracle WebCenter Discussion Server uses its own database persistence mechanisms for data and metadata. Oracle Webcenter Analytics has two components: the Oracle Webcenter Analytics service, which consists of task flows and data controls, and the Oracle WebCenter Analytics Collector Service. MDS WebCenter Domain wc_domain Managed Server WC_Portlets Managed Server WC_Collaboration Managed Server WC_Utilities Managed Server WC_Spaces Administration Server WLS Administration Console Fusion Middleware Control 6-34 Oracle Fusion Middleware High Availability Guide Events sent to the Oracle WebCenter Collector are placed into a configurable queue of incoming events for persisting to the database. If an Oracle WebCenter Collector Service fails, these events are lost. Typically, however, the queue doesnt contain many events. The Oracle WebCenter Analytics Collector supports clustering and failover, but collectors do not share the queue. The Oracle WebCenter Analytics service task flows, which provide the reporting UI for WebCenter are stateless. These features are built on the standard ComposerADFMDS framework, which manages the state if a failure occurs. Oracle WebCenter Activity Graph has two components: the Oracle WebCenter Activity Graph service, which consists of task flows and data controls, and the Oracle WebCenter Activity Graph engine. The engine runs a batch data analysis process to update database tables. It does not support clustering or failover but can recover from failure. The Oracle WebCenter Activity Graph service does not maintain any in-memory state; it is primarily a read-only process. The Oracle WebCenter Spaces task flows query the Oracle WebCenter Activities database and produce a list of recommendations. State updates in these areas: 1. Personalization settings 2. Task flow configuration parameters 3. Not-interested feature The first two areas are built on the standard ComposerADFMDS framework, which manages the state. With the not interested feature, you can indicate that you are not interested in a recommendation. This input persists synchronously in the Oracle WebCenter Activity Graph database. Use the Oracle WebCenter Activity Graph user interface to set up and monitor the nightly schedule. The schedule persists to the database. If the managed server fails, the job continues when the server restarts. Some recommendations may be stale if you do not run the backend daily. Oracle WebCenter Personalization Server is a stateless RESTful application. All state is managed in the client requests. Oracle WebCenter Personalization metadata produced by JDev tools persists in MDS; additional configuration data such as connection information persists in domain scoped managed beans.

6.3.1.4 Oracle WebCenter External Dependencies