Oracle UCM Component Characteristics

11-12 Oracle Fusion Middleware High Availability Guide There are two entry points into the Oracle UCM application. One is a listening TCP socket, which can accept connections from clients such as Oracle IPM or Oracle WebCenter. The second is an HTTP listening port, which can accept Web services invocations. The HTTP port is the same port as the Managed Server listen port. The UCM Server also contains several embedded applications. These can be run as applets within the clients browser. They include a Repository Manager RM for file management and indexing functions, and a Workflow Admin for setting up user workflows. For more information on any of these applications, refer to the Oracle Fusion Middleware Application Administrators Guide for Content Server. The UCM Server has three types of persistent stores: the repository which can be stored in an Oracle database, the search index which can be stored in an Oracle database, and metadata and web layout information which can be stored on the file system.

11.2.1.1 Oracle UCM Component Characteristics

Oracle UCM is a servlet that resides in WebLogic Server. A servlet request is a wrapper of a UCM request. Oracle UCM includes various standalone administration utilities, including BatchLoader and IdcAnalyzer. JMS and JTA are not used with Oracle UCM.

11.2.1.1.1 Oracle UCM State Information A request in Oracle UCM is stateless. The session

can be persisted in the database to retain authentication information.

11.2.1.1.2 Oracle UCM Runtime Processes Oracle UCM has a service-oriented

architecture. Each request comes into the system as a service. The Shared Services layer parses out the requests and hands the request to the proper handler. Each handler typically accesses the underlying repository to process the request. The three types of repositories and the data that they store are shown in Figure 11–3 .

11.2.1.1.3 Oracle UCM Process Lifecycle You can start and stop Oracle UCM as a

WebLogic Server Managed Server. The UCM Administration Server can also be used to start, stop, and configure the UCM instance; the UCM Administration Server still works in the WebLogic Server environment, although it has been deprecated in favor of the WebLogic Administration Console. The load balancer can use the PING_ SERVER service to monitor the status of the UCM instance. During startup, Oracle UCM loads initialization files and data definitions, initializes database connections, and loads localization strings. Through the Oracle UCM internal component architecture, the startup sequence also discovers internal components that are installed and enabled on the system, and initializes those components. The SearchIndexing engine and file storage infrastructure are also initialized. A client request is typically serviced entirely by one Oracle UCM instance. Existence of other instance in a cluster does not impact client request.

11.2.1.1.4 Oracle UCM Configuration Artifacts Initialization files are stored in the file

system and stored in Oracle UCM system directories.

11.2.1.1.5 Oracle UCM Deployment Artifacts Oracle UCM uses nostage deployment. That

is, all deployment files are local.

11.2.1.1.6 Oracle UCM External Dependencies Oracle UCM requires WebLogic Server and

an external Oracle database. Configuring High Availability for Enterprise Content Management 11-13 The following clients depend on Oracle UCM: ■ Oracle Universal Records Management Oracle URM ■ Oracle Imaging and Process Management Oracle IPM ■ Oracle WebCenter The connection from clients is short-lived, and is only needed for the duration of sessionless service. Clients can connect to Oracle UCM using the HTTP, SOAPWeb Services, JCR, and VCR protocols.

11.2.1.1.7 Oracle UCM Log File Locations Oracle UCM is a J2EE application deployed on

WebLogic Server. Log messages are logged in the server log file of the WebLogic Server that the application is deployed on. The default location of the server log is: WL_HOME user_projectsdomainsdomainNameserversserverNamelogs serverName -diagnostic.log Oracle UCM can also keep logs in: WebLayoutDir groupssecurelogs Oracle UCM trace files can be configured to be captured and stored in: IntraDocDir datatrace To view log files using the Oracle UCM GUI, choose the UCM menu and then choose Administration Logs. To view trace files using the Oracle UCM GUI, choose the UCM menu and then choose System Audit Information . Click the View Server Output and View Trapped Output links to view current tracing and captured tracing.

11.2.2 Oracle UCM High Availability Concepts