The following tools provide graphical user interfaces for configuring and viewing message logging and tracing. Use the:
In addition to using Log Viewer to view logs, you can open the log with a text editor.
During startup, the connector generates a temporary log file. This file contains all messages that are logged during startup, including connector properties and business object definitions that are passed to the connector framework. The file name is broker_name_connector_name_tmp.log, and it is written to the ProductDir directory. Once the connector is running, it handles logging and tracing as configured in the standard connector configuration properties.
While logging and tracing messages are written using UTF-8 encoding in the locale specified in the connector's configuration file, time information is written in a locale-independent format.
At connector startup, a log file is also created, if one does note already exist, in the location specified in the connector's configuration file. If a log file already exists, new entries are simply added to it. Unless a limit has been placed on the size of the connector log file, its size depends on the amount of time since it was last managed and the volume of transactions passing through the system. If the connector log file is configured with no size limit, it can continue to grow until it cannot be opened or it exhausts its disk space.
If tracing is enabled, a trace file is created at startup if one does not already exist. The size of the trace file must be managed in the same manner as the connector log file to avoid the problems caused by excessively large files.
Table 12 lists the files used by the connector to store logging and tracing information.
To manage log and trace files, you can use the Connector Configurator to:
For more information about using the Connector Configurator to set these options, see Configuring logging and tracing options.
If archival logging is enabled, each time the connector's log or trace file reaches its maximum size, it is renamed as a new archive file. The archive file's name is derived from the original log or trace file name, with the following inserted into the name: _Arc_number.
For example, if five archive files are to be used and the log file has the name Connector.log, then:
See the configuration task Configuring logging and tracing options for details.
While log and trace files can be managed by means of archival logging, other log files specific to each application need to be managed manually. Most of these files are created during runtime if they do not already exist. New information is appended to any existing file.
Any file management procedure can be used, but IBM suggests the following periodic log file management: