System-wide loggers are used for logging information about infrastructure, AXIS and WSIF bindings. They can be configured through the BPEL Admin Console (http://hostname:port/BPELAdmin) > logging or by editing log4j-config.xml in $BPEL_HOME\integration\orabpel\system\config

The different systems to log about:· org.collaxa.thirdparty.apache.wsif – logger for system-wide WSIF· org.collaxa.thirdparty.apache.axis.transport – logger to see what axis is sending on the wire· org.collaxa.thirdparty.apache.axis – general axis related logging· collaxa.cube.services – all BPEL PM wide services· collaxa.cube.infrastructure – infrastructure such as DB connectors

1.1.1.3. Log Level

The following logging levels are available and listed here from highest priority to lowest priority. When a logging level is specified, all messages with a lower priority level than the one selected are ignored.

· Offo Disables logging. This selection is the highest priority.· Fatalo Logs critical messages. After logging occurs, the application quits abnormally.· Erroro Logs application error messages to a log; the application continues to run (for example, an administrator-supplied configuration parameter is incorrect and you default to using a hard-coded value).· Warno Logs warning messages to a log; the application continues to run without problems.· Infoo Logs messages in a format similar to the verbose mode of many applications.· Debugo Logs debugging messages that should not be printed when the application is in a production environment.· Allo Enables all logging. This selection is the lowest priority.

Note that logging with sensors impacts performance because sensor data objects are built even when logging is disabled.

You add sensors to specific activities and then extract data from variables. To do this, you must implement a custom sensor publishing action to do the log4j logging. For example, you can create a sensor on an invoke activity and create a message that issent to a JMS queue.