WebCenter Dependencies Oracle WebCenter Topology

Introduction to Oracle WebCenter Administration 1-9 Serverservice unavailability does not prevent WebCenter applications from starting up, although errors may display while the application is running. The only exception is the Oracle Metadata Repository MDS, as WebCenter applications do not work without it. WebCenter Spaces partially works without the WebCenter repository but only if it is a different physical database from the MDS repository. The WebCenter repository stores information for several services, including Events, Links, Lists, People Connections, Polls, and Tags, and these services do not work if the WebCenter repository is not available.

1.3.5 WebCenter Configuration Considerations

The main configuration files for WebCenter applications are listed and described in Table 1–4 . Both these files are supplied within the WebCenter application deployment .EAR file. WebCenter applications and portlet producers both use the Oracle Metadata Services MDS repository to store their configuration data; both access the MDS repository as a JDBC data source within the Oracle WebLogic framework. The MDS repository stores post deployment configuration changes for WebCenter applications and portlet producers as application customizations. MDS uses the original deployed versions of adf-config.xml and connections.xml as base Oracle Content Server Documents Socket connection to the Administration Server. HTTP access is required only if the Oracle Content Server must be accessed outside 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 Personalization server JBDC access to the personalization server JDBC REST Portlets HTTP location of provider WSDLs SOAPHTTP Search server HTTP access to search server HTTP Worklist HTTP access to BPEL server SOAPHTTP MDS and Schemas JDBC JDBC Table 1–4 Oracle WebCenter Configuration Files Artifact Purpose adf-config.xml Stores basic configuration for Application Development Framework ADF and WebCenter application settings, such as which discussions server or mail server the WebCenter application is currently using. connections.xml Stores basic configuration for connections to external services. Table 1–3 Cont. Dependent Resources - Access Types External Server Service Configuration Access 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