Enhanced Logging XML Reference

Enhanced logging captures the step-by-step logic of a business process rather than at the package level (that is, captured by the log level you choose in the <installation directory>\EAServer\bin\logging.properties ).

Elements Used in Enhanced Logging

Use enhanced logging to complement and extend the Service Container log levels you have configured for your service package.

Note: If you enable enhanced logging, use a text editor to browse the log file rather than use a console or log viewer. A text editor renders the XML elements more clearly.
Element name Description Usage
<Activity> The root element of the log entry.  
<BP_Name> The business process service target namespace. There are two important parts to the namespace: the service name and service operation name. To correlate the activity back to a given business process.
<InstanceID> The unique identifier for a specific instance of the business process. This ID never changes.  
<TimeStamp> The date and time that the activity was executed.  
<ProcessingTime> The duration (in milliseconds) the activity took to execute. To analyze the performance of a business process and help pinpoint issues.
<ActivityType> The type of activity being processed. Can be one of:
  • receive request (BPEL receive)
  • send response (BPEL reply
  • invoke service (BPEL invoke)
  • assign
  • throw exception
  • terminate
  • delay (BPEL wait)
  • single-rule (BPEL switch)
  • complex activity (BPEL scope)
  • loop (BPEL while)
  • compensate
  

<ActivityID>

 The unique identity for the activity. To correlate the activity back to an instance on the WorkSpace Business Process Service perspective.
<ParentID> The ID of the parent node that contains this activity. The root level scope does not have a parent. However, all others have an enclosing scope as the parent ID.  
<Level> The depth of the business process activity being logged: the root level scope of a BPEL process is level 0; processes nested below that are level 1, and so on. To provide a reference point from the log to the business process diagram.
<OperationInfo> If an activity calls to another service (that is, where <ActivityType>= Invoke), this element captures information about the service and operation being called:
  • <Operation>--the name of the operation being invoked.
  • <PortType>--the PortType name of the service being invoked.
To capture information on receive, reply, or invoke activities only.
<Variables> A list of variable names and values used in the activity. To evaluate data for input and output variables.
Related tasks
Setting Service Container Log Properties
Disabling Service Container Logging to EAServer Log Files

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.