Guided Business Process query Service API

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. Building a Guided Business Process Client Application 25-15 When you read a log file you must look for the message text, this text describes what happened. The message type helps you identify how serious the problem is. For more information about the different message types, see Table 25–2 . You can use the date and time of the log message to identify the action that caused the problem. Example 25–6 Log Message Example DefaultServer-diagnostic.log:[2009-07-10T17:39:35.220-07:00] [DefaultServer] [NOTIFICATION] [AGU-12605] [oracle.bpel.activityguide.ui.beans] [tid: [ACTIVE].ExecuteThread: 1 for queue: weblogic.kernel.Default self-tuning] [userId: jstein] [ecid: 0000I9bG2R3DScQ6ube9UH1ALxd1000007,0] [APP: AGNonUIshellAppV2.0] [arg: jstein] Setting user, jstein as the loginUserId in server interfacing bean.[[ Example 28-12 shows a notification log message that contains information about a loginUserId change. In this example the different log message items are: ■ Date and Time: 2009-07-10T17:39:35.220-07:00 ■ Message Type: NOTIFICATION ■ Execution Context ID: ecid: 0000I9bG2R3DScQ6ube9UH1ALxd1000007,0 ■ Application Name: APP: AGNonUIshellAppV2.0 ■ Class Package Name: oracle.bpel.activityguide.ui.beans ■ Message ID: AGU-12605 ■ Message Text: Setting user, jstein as the loginUserId in server interfacing bean. Execution Context ID ECID A global unique identifier and a sequence number that correspond to the thread where the originating component is running. You can use it to correlate messages from multiple components that may be involved in the same thread. Application Name Specifies the name of the application that generated the log message. Class Package Name Specifies the package of the class that generated the log message. Message ID Specifies a short identifier that uniquely identifies the message. Message Text Describes the event. This message is localized, thus it displays in the language that corresponds to the locale of your system. Note: before contacting Oracle Support make sure you can provide them the message ID and the execution context ID. Table 25–3 Cont. Log Message Items Log Message Item Description 25-16 Modeling and Implementation Guide for Oracle Business Process Management