Logging information is provided by each application component through the OSGi Log Service.

These log entries are temporarily stored in the <XPDINTEG_HOME

/workspace/log folder. These log entries fire log events that are retrieved by the Custom Log Service and the iTMS (see micro broker and micro broker bridge Logging). The Custom Log Service and the iTMS can be configured to forward these events to either as defined LogQ in the back-end Message Broker or to a Tivoli Enterprise back-end Console.

Tivoli monitoring is provided through the Expeditor integrator Tivoli Monitor (SATM) service. This service uses the EIF (Event Invocation Framework) and forwards Log events to a Tivoli Enterprise Console® (TEC) in the back-end directly or through a locally installed Tivoli Endpoint. It can also be configured which log events are forwarded.

The forwarded event classes are as follows.

XPDINTEG_BUNDLEEVENT

XPDINTEG_LOGEVENT

The TEC log and trace files are stored in the following locations.

<XPDINTEG_HOME

/persistent/tec/eif.log

<XPDINTEG_HOME

/persistent/tec/eif.trc

The TEC libraries do not provide options to limit the trace and log file size. The Expeditor integrator v1.0 passes the log file names as parameters on to the used TEC libraries. Currently, there is no way to limit the size of these two files (even from XPDinteg).

It is recommended to turn the logging and tracing only on in defined environments by setting TecLogLevel=ALL and TecTraceLevel=ALL (in XPDinteg.xml) and OFF again under production conditions.