Oracle WebCenter External Dependencies

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

Oracle WebCenter Spaces is the client for Oracle WebCenter Analytics, Oracle WebCenter Activity Graph, and Oracle WebCenter Personalization Server. Oracle WebCenter Analytics uses the database that includes the Activities schema. Oracle WebCenter Activity Graph uses the data stored in the Activities schema to provide recommendations. Oracle WebCenter Personalization Server uses a database for its Personalization schema and MDS schemas. Clients connect to Oracle WebCenter Personalization Server using JDBC and UDP. Oracle WebCenter Personalization Server uses REST, JDBC, the ADF Connection architecture, and MDS JMX. Oracle WebCenter Activity Graph uses JDBC to mine statistical data in the Activities schema, and the client Oracle WebCenter Spaces also uses JDBC to connect to the Activities schema to present the data to users. Configuring High Availability for Oracle ADF and WebCenter Applications 6-35 Oracle WebCenter Spaces uses the Java Client API that is based on Open Usage, and which uses multicasting over UDP, to communicate with Oracle WebCenter Analytics. Table 6–2 shows the access type for each of the Oracle WebCenter components and services. The Configuration column lists the type of information provided to Oracle WebCenter to configure or initialize the connection. The Access column lists the protocol used in runtime access of the service. The Oracle Discussion Server is a service provider to Oracle WebCenter Spaces. Oracle Portlets also exposes Portlet Producers as services. Unavailability of these services does not prevent Oracle WebCenter Spaces application from starting, although application errors may be seen when running. Oracle WebCenter Spaces requires the MDS and WebCenter schemas. Configure each of the external services independently for high availability. Oracle WebCenter’s framework provides a single point of access for external services. ■ For HTTP services, for example, direct the access URL to a load balancer which provides access to multiple service providers on the back-end. Instructions for configuring Oracle WebCenter Discussions servers for high availability are provided in Section 6.4.5, Running Oracle Fusion Middleware Configuration Wizard on APPHOST1 to Create the WebLogic Server WebCenter Domain. ■ For the MDS repository and schemas, Oracle recommends an Oracle Real Application Clusters Oracle RAC database as the back-end database. Table 6–2 Oracle WebCenter Access Types External Server Service Configuration Access Oracle Discussion server HTTP access to discussions server administration SOAPHTTP Oracle Content Server Documents Socket connection to the Administration Server. HTTP access is required only if the content server must be accessed outside Oracle WebCenter. JCR 1.0 over socket or HTTP Instant Messaging and Presence server HTTP access to instant messaging and presence server administration SOAPHTTP Mail server IMAPSMTP server IMAPSMTP Personal events server HTTP access to calendar services SOAPHTTP Portlets HTTP location of provider WSDLs SOAPHTTP Search server HTTP access to search server HTTP Worklist HTTP access to BPEL server SOAPHTTP MDS repository and schemas JDBC JDBC Oracle WebCenter Analytics UDP access to Oracle WebCenter Analytics Collectors UDP Oracle WebCenter Activity Graph HTTP access to Oracle WebCenter Activity Graph HTTP Oracle WebCenter Personalization Server JDBC access to Oracle WebCenter Personalization Server JDBC, REST 6-36 Oracle Fusion Middleware High Availability Guide Instructions for configuring Oracle RAC as a database provider are in Section 6.4.5, Running Oracle Fusion Middleware Configuration Wizard on APPHOST1 to Create the WebLogic Server WebCenter Domain. For information about multi data source configuration with Oracle RAC and the MDS repository, see Section 4.1.2, Using Multi Data Sources with Oracle RAC.

6.3.1.5 Oracle WebCenter Configuration Considerations