Log Messages

Generally, Lotus® Expeditor integrator can display log messages in the OSGi Console, if Expeditor integrator was started in console mode.

For more details on starting in console mode, see Starting/Stopping Expeditor integrator in Launching the Lotus Expeditor Client on the desktop

These console log messages are switched OFF by DEFAULT. They can be switched back ON by editing the following line in <XPDINTEG_HOME

/rcp/eclipse/features/com.ibm.rcp.base_<version

_<build

/rcpinstall.properties

-Dcom.ibm.rcp.integrator.showflowstatus=true

Note:

Changes to the rcpinstall.properties file require re-starting the Expeditor integrator platform.

Log messages can also be received by the back-end. There are three options available for retrieving log entries through messaging.

OSGi / Eclipse standard logging (see Level of Log Messages)
Custom Log Service (see Level of Log Messages)
Tivoli® Monitoring (see Tivoli Monitoring)

Local log files are also created and could be retrieved by FileRequest messages (see the table in int_limits_firstaid_log with available log files).

Level of Log Messages

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.

The log levels can be configured in the XPDinteg.xml (see chapter Custom Log Service configuration).

micro broker and micro broker bridge Logging

The Lotus Expeditor micro broker and the micro broker bridge create their own log files.

They are located in <XPDINTEG_HOME

/persistent/microbroker/XPDinteg_broker and contain information about the broker status, connection to the back-end and message handling.

The size of the log file can be set with MicrobrokerLogSize in XPDinteg.xml.

Transaction Service Log

The Expeditor integrator transaction log service creates log files.

They are located in <XPDINTEG_HOME

/persistent/txlogdir/partnerlog and <XPDINTEG_HOME

/persistent/txlogdir/tranlog where the status of the transactions is logged. The transaction log directory can be configured in the XPDinteg.xml file (TransactionLogDirectory).

Tivoli Monitoring

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.

Refer to Application Control Service Configuration for configuration details.

Previous Page | Next Page