How to Configure the Supported Locales for a Guided Business Process Client Application

Building a Guided Business Process Client Application 25-13

25.7 Using Guided Business Process Logging

Guided Business Processes use a log file to store information about the different operations they perform. This file contains log messages that track the application behavior and possible errors that might occur while running the application. You can use the information in this log file to find out the cause of an unexpected behavior in your application. The importance of the log messages varies according to their level. The level of the messages used for debugging purposes is different to the level of the messages that contain warnings or errors. You can configure Guided Business Process Logging to log only certain level of messages according to your needs.

25.7.1 How to Enable Client Side Logging

You can configure Guided Business Processes to generate a log file on the client side. To enable client side logging: 1. Locate the logging.xml file in the directory DOMAIN_ HOMEconfigfmwconfigservers Server Name

2. Open the logging.xml file for editing.

3. Add the following entry in the loggers element:

logger name=oracle.bpel.activityguide.ui level=NOTIFICATION:1 useParentHandlers=’false’ handler name=odl-handler logger 4. Save the changes. 5. Re-start Web Logic Server.

25.7.2 How to Enable Server-Side Logging

You can configure Guided Business Processes to generate a log on the server side. To enable server-side logging: 1. Locate the logging.xml file in the directory DOMAIN_ HOMEconfigfmwconfigservers Server Name 2. Open the logging.xml file for editing. 3. Add the following entry to the loggers element: logger name=oracle.bpm.services.activityguide.query level=NOTIFICATION:1 useParentHandlers=true 4. Save the changes. 5. Re-start Web Logic Server.

25.7.3 Configuring Log Levels

Log messages contain a level that identifies the severity of the problem. 25-14 Modeling and Implementation Guide for Oracle Business Process Management Table 28-3 shows the available log levels. The Severity column describes the common term used to identify a certain severity. The Log Level Value common specifies the value that you must use in the logging.xml file. You can configure Guided Business Process Logging to specify the level of detail of the information stored in the Guided Business Process logs. To set the log level must change the value of the attribute level in the logger element in the logging.xml file. When you set the log level to a certain severity, all the messages that correspond to higher severities are also stored. For example, if you set the log level to severe, then the log messages of severity fatal are also logged.

25.7.4 How to View Guided Business Process Log Messages

Log messages are stored in the following file: DOMAIN HOMEserversServer Namelogs Server Name-diagnostic.log You can view the file that contains the log messages using a text editor.

25.7.5 Understanding Guided Business Process Log Messages

A log message contains information that helps you identify the problems in your Guided Business Process application. Table 28-3 describes the items that compose a log message. Table 25–2 Log Level Values Severity Log Level Value Description Fatal INCIDENT_ERROR:1 Indicates a serious problem caused by unknown reasons. Users cannot fix the problem by themselves, they must contact Oracle Support. Severe ERROR:1 Indicates a serious problem that requires immediate attention from the System Administrator Warning WARNING:1 Indicates a potential problem. The System Administrator should review these log messages. Information NOTIFICATION:1 Indicates a major lifecycle event such as the activation or deactivation of a primary sub-component or feature. Configuration NOTIFICATION:16 Specifies a normal event occurred at a lower level. Fine TRACE:1 Specifies trace or debug information for events that are meaningful to end users of the product, such as public API entryexit points. Finer TRACE:16 Specifies a detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. Table 25–3 Log Message Items Log Message Item Description Date and Time Specifies the date and time when this log message was generated. Message Type Specifies the severity of the message.