WebCenter Configuration Considerations Oracle WebCenter Topology

1-10 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter documents and stores all subsequent application customizations separately into MDS using a single customization layer. When a WebCenter application starts up, application customizations stored in MDS are applied to the appropriate base documents and the WebCenter application uses the merged documents base documents with customizations as the final set of configuration properties. For WebCenter applications that are deployed to a server cluster, all members of a cluster read from the same location in the MDS repository. Typically, there is no need for administrators to examine or manually change the content of base documents or MDS customization data for files such as adf-config.xml and connections.xml, as Oracle provides several administration tools for post deployment configuration. If you must locate the base documents or review the information in MDS, read Appendix A, WebCenter Configuration . To find out more about WebCenter application configuration tools available, see Section 1.13, Oracle WebCenter Administration Tools. While WebCenter applications store post deployment configuration information in MDS, configuration information for portlet producers and Oracle WebCenter Discussions Server is stored in the file system or the database see Table 1–5 . Oracle WebCenter Discussions Server The Oracle WebCenter Discussions Server stores configuration information in its database. Additionally, it stores startup configuration information in DOMAIN_HOMEconfigfmwconfigserversWC_COLLABORATIONowc_discu ssions. This directory contains jive_startup.xml, jive.license files, and a logs directory containing log files for the discussions server instance.

1.3.6 WebCenter State and Configuration Persistence

WebCenter applications run as J2EE applications with application state and configuration persisted to the MDS repository. User session information within the application is held locally in memory. In a cluster environment, this state is replicated to other members of the cluster. Application customizations within a portlet or service environment are persisted by that service. Out-of-the-box, Oracle portlets, any custom portlets you build, and Oracle WebCenter Discussions Server, all have their own database persistence mechanisms. Note: Oracle does not recommend that you edit adf-config.xml or connections.xml by hand as this can lead to misconfiguration. Table 1–5 Oracle WebCenter Configuration Location Application Configuration Stored in MDS Configuration Stored in File System Configuration Stored in Database WebCenter Spaces Yes No No WebCenter Portal applications Yes No No Portlet producers No Yes No Discussions server No Yes Yes Introduction to Oracle WebCenter Administration 1-11 WebCenter Analytics WebCenter Analytics is stateless. Requests received by Analytics Collectors are executed immediately. Any in-transit state, such as a request initiated by a WebCenter application or a request processed by the Analytics Collector, is not guaranteed. WebCenter Activity Graph WebCenter Activity Graph consists of two components: ■ Activity Graph service - does not maintain any in-memory state. The Activity Grpah task flows query the Activity Graph database and display results as a list of recommendations. State is updated by the following: ■ Task flow configuration parameters ■ Personalization settings ■ Not-interested feature The first two are built on the standard Oracle ComposerOracle ADFMDS framework, which manages the state. The last is a feature where the user can indicate that they are not interested in a particular recommendation. This input is persisted synchronously in the database. ■ Activity Graph Engine - runs a batch data analysis process that updates tables in the database transactionally. Although the engine does not support clustering or failover, it can recover from failure. Administrators use the Activity Graph Scheduler to set up and monitor the nightly schedule. The results of the analysis the recommendations are presented through the Activity Graph task flows. The Activity Graph Engine is a singleton application that has a background thread that wakes up periodically to check if it is time to run the nightly job, which can last several hours. The schedule is persisted in the database. If the managed server fails, the job continues when the managed server next starts up. WebCenter Personalization Server WebCenter Personalization Server is a stateless RESTful application. All state is managed in the client requests.

1.3.7 WebCenter Log File Locations

Operations performed by WebCenter applications, portlet producers, discussion servers, and so on, are logged directly to the WebLogic managed server where the application is running: base_domainserversWC_ServerlogsWC_Server.log For example, WebCenter Spaces diagnostics are logged to: base_domainserversWC_SpaceslogsWC_Spaces-diagnostic.log You can view the log files for each WebLogic managed server from the Oracle WebLogic Server Administration Console. To view the logs, access the Oracle WebLogic Server Administration Console http:admin_server_host:portconsole, and click Diagnostics-Log Files . You can also view and configure diagnostic logs through Fusion Middleware Control, see Section 36.3, Viewing and Configuring Log Information.