Creation of Oracle IPM Artifacts in a Cluster Troubleshooting Oracle IPM

11-10 Oracle Fusion Middleware High Availability Guide secondary servers. In case of a failure in the primary UCM server, Oracle IPM retries the next UCM server in the list. If all the UCM servers are down, an exception is returned and traced in the Oracle IPM server´s log.

11.1.2.3 Creation of Oracle IPM Artifacts in a Cluster

Searches, inputs, applications all Oracle IPM structural configurations are stored within the Oracle IPM database. They become immediately available to all machines in the cluster, including the Web UI layers. The Web UI does not automatically refresh when a new entity is created in another Oracle IPM server in the cluster or in the same server by a different user session; however, you can refresh your web browser to cause a navigation bar refresh for the imaging application.

11.1.2.4 Troubleshooting Oracle IPM

This section describes how to trouble shoot the Oracle IPM server, Advanced Viewer, and Input Agent in a high availability environment. Additional Oracle IPM troubleshooting information can be found in Oracle Fusion Middleware Administrators Guide for Oracle Imaging and Process Management. Oracle IPM Server Troubleshooting OracleIPM is a JEE application deployed on WebLogic Server. All log messages are logged in server log files of the WebLogic Server that the application is deployed on. The default location of the diagnostics log file is: WL_HOME user_projectsdomainsdomainNameserversserverNamelogs serverName -diagnostic.log You can use Oracle Enterprise Manager to easily search and parse these log files. Advanced Viewer Troubleshooting Oracle IPM primarily provides server side logging, although it does have a client-side component called the Advanced Viewer. This Java Applet uses the standard logging utilities; however, these utilities are disabled in client situations. These utilities can be configured to direct the logging output to either a file or the Java Console via appropriate changes to the logging.properties file for the Java plug-in. Input Agent Troubleshooting When the Input Agent for Oracle IPM is uploading documents, if Oracle Universal Content Management fails, messages such as these are generated: Filing Invoices Input completed successfully with 48 documents processed successfully out of 50 documents. In addition, an exception similar to this is generated: [2009-07-01T16:43:01.549-07:00] [IPM_server2] [ERROR] [TCM-00787] [oracle.imaging.repository.ucm] [tid: [ACTIVE] .ExecuteThread: 10 for queue: weblogic.kernel.Default self-tuning] [userId: anonymous] [ecid: 0000I8sgmWtCgon54nM6Ui1AIvEo00005N,0] [APP: imaging11.1.1.1.0] A repository error has occurred. Contact your system administrator for assistance. [[oracle.imaging.ImagingException: TCM-00787: A repository error has occurred. Contact your system administrator for assistance. stackTraceId: 5482-1246491781549 faultType: SYSTEM Configuring High Availability for Enterprise Content Management 11-11 faultDetails: ErrorCode = oracle.stellent.ridc.protocol.ServiceException, ErrorMessage = Network message format error. at oracle.imaging.repository.ucm.UcmErrors.convertRepositoryErrorUcmErrors. java:109 . . . The Input Agent handles errors by placing the failed documents in an error file, so this behavior and the error messages that are generated under these circumstances are expected.

11.2 Oracle Universal Content Management High Availability

This section provides an introduction to Oracle Universal Content Management Oracle UCM and describes how to design and deploy a high availability environment for Oracle UCM.

11.2.1 Oracle Universal Content Management Component Architecture

Figure 11–3 shows the Oracle UCM single instance architecture. Figure 11–3 Oracle Universal Content Management Single Instance Architecture An instance of Oracle UCM runs within an Oracle WebLogic Managed Server environment. WebLogic Server is responsible for the lifecycle of the Oracle UCM application, such as starting and stopping it. WebLogic Server: Socket J2EE, COM, Command Line Relational Database: - Content Metadata - Workflow Information - Security Information - Product Information - Vault and Web Layout Depending on File Store Provider Settings Search index: - Full Text Index of Content - Metadata Index of Content - Security Information File Store: - Vault Source File - Web Layout: Renditions Directly Available from the Web Server Web Server Cache - Shared Data Web Server HTTP, SOAP, WebDAV Universal Content Management: Document Management Shared Services: Security, Personalization, Search, Metadata Repository Services: Content, File, Data Web Content Management Records Management Digital Asset Management