This section describes how to set up message logging and tracing.
These settings can be made by using The Edit Configuration option in System
Manager and by manually editing the InterchangeSystem.cfg
file. The following tasks are described:
"Steps for opening the Edit Configuration tool"
"Steps for configuring InterChange Server Express logging and tracing destinations"
Steps for configuring other InterChange Server Express logging and tracing parameters
Steps for configuring the connector agent logging destination
Steps for configuring tracing levels for InterChange Server Express, business objects, and collaborations
Steps for configuring the collaboration object trace level
Steps for configuring connector tracing
Steps for configuring map tracing
InterChange Server Express must be running and in the Connected state to
use the Edit Configuration tool. The Edit Configuration tool can manage
only one InterChange Server Express per session.
Perform the following steps to open the Edit Configuration tool:
- Open System Manager.
- Right-click a server instance in the InterChange Server Component
Management view and click Edit Configuration. The Edit
Configuration tool opens in the upper-right section of System Manager, where
you can edit the InterchangeServer.cfg file in the
Perform the following steps to configure the destination for InterChange
Server Express message logging and tracing:
- In the Edit Configuration tool, click the Trace/Log Files
tab.
The logging and tracing configuration window appears (see Figure 50).
Figure 50. Edit Configuration tool, Trace/Log Files tab

- Under Logging, select the destination for system
logging. You can log to both system console and a log file, but use
this option only for debugging and only on development systems. Do the
following:
- To log to the system console (standard output), which is the default,
select the To console (STDOUT) check box. To
disable the console as the logging destination, clear the To
console (STDOUT) check box.
- Note:
- If you plan to run InterChange Server Express as a service, you must set
logging and tracing to file destinations. Setting logging and tracing
to STDOUT prevents InterChange Server from being configured as a
Windows service.
- To log to a file, select the To File check box and either type
in the full path name of the file or click the browse button to navigate to
the log file.
- If you select a log file, you can configure the size of the file in MB (or
keep the default, Unlimited) and the number of archive files to create.
For information about archives, see "Maintaining event archives".
- Under Tracing, select the destination for system
tracing. Do the following:
- To configure IBM WebSphere MQ tracing, accept the default path name of the
file or click the browse button to navigate to the log file.
- Click OK to save changes and exit.
Your changes take effect immediately, and if you already had a log file
configured, it is saved and dated, and a new file created using the newly
entered configuration.
When InterChange Server Express stack tracing is enabled, the stack trace
information is printed to the InterChange Server Express log file. This
can be useful for troubleshooting a newly installed system.
Perform the following steps to configure the stack tracing feature:
- Open the Edit Configuration tool (see Steps for opening the Edit Configuration tool).
- Click the Trace/Log Files tab.
- Select the Enable Stack Tracing check box. When you
enable stack tracing, the Tracing Severity Level list is
available.
- In the Tracing Severity Level list, select the severity level
for which you want to print the stack tracing. The choices are:
INFO, WARNING, ERROR, and
FATAL. When stack tracing is printed to the log file, it
prints the level you select and all levels above it. For example, if
you select ERROR, both ERROR and FATAL
messages are printed to the log file.
Perform the following steps to set file size and number of archived files
for log and trace files:
- Open the Edit Configuration tool (see Steps for opening the Edit Configuration tool).
- Click the Trace/Log Files tab.
- To limit the log file, select the To File and the
Unlimited check boxes, and select a number to represent the maximum
log file size from the Log file list, and then select
Byte, KB (kilobyte), MB (megabyte), or
GB (gigabyte).
- To limit the trace file, select the To File and the
Unlimited check boxes, select a number to represent the maximum
trace file size from the Trace file list, then select
Byte, KB (kilobyte), MB (megabyte), or
GB (gigabyte).
- To set the number of log or trace file archives, select a number from the
Number of archives list under either Logging or
Tracing section.
- Stop and restart InterChange Server Express.
The two connector components have separate mechanisms for logging.
Connector controller logging is sent to the
InterchangeServer.log file. This section describes
configuring the connector agent log file name and location.
For background information on connector agent logging, see "Connector Agent logs".
You can set the destination for connector agent logging using one of the
following methods:
- If you are installing Remote Agent, you can configure the logging
destination during the installation. For more information about
installing Remote Agent, see the System Implementation
Guide.
- If you are not using Remote Agent, you can use Connector Configurator
Express to configure the connector agent logging destination.
Perform the following steps to configure the destination for connector
agent logging using Connector Configurator Express:
- Connect to a server.
- In System Manager, right-click a connector object, then select Edit
definition. The Connector Configurator Express widow
appears.
- Click the Standard Properties tab.
- Select one of the logging property values (see Table 18 for an explanation of these values), and click
Edit.
- Type the new value in Value field and click
OK.
For example, change the LogAtInterchangeEnd value to
true to send messages to the InterChange Server Express log.
If InterChange Server Express is configured to send e-mail when error and
fatal messages are logged, e-mail is sent for the connector agent messages as
well.
- Repeat Steps 3 and 4 to edit the other logging property value if
necessary.
For example, to send connector agent messages to a message file instead of
the default STDOUT, enter the full path name of the file in the
Value field.
- Restart the connector for changes to take effect.
- Note:
- If you want to specify a logging and tracing file for the connector agent,
you must specify a local configuration file when starting the agent.
Perform the following steps to configure tracing:
- Open the Edit Configuration tool (see Steps for opening the Edit Configuration tool).
- Click the Tracing Levels tab (see Figure 51).
Figure 51. Edit Configuration tool, Tracing Levels tab

- To configure subsystem tracing, under IBM WebSphere Business
Integration Trace Levels, select a Trace level for the
subsystems you want to configure.
Setting these trace levels updates parameters in the
InterchangeSystem.cfg file. For details about what
information is produced at the various tracing levels, see WebSphere
Business Integration Server Express Installation Guide.
- To configure tracing for collaborations, do the following:
- To configure tracing for business objects, do the following:
- Under Flow Tracing Levels, select Business Objects
from the Component list. The business object names that are
configured for the system appear in the table.
- For each component, select a level for tracing in the Level
column.
- Click OK to save changes and exit.
The trace levels for the subsystems, business objects and collaborations
are immediately in effect.
This section describes one of two methods that can be used to configure
collaboration object trace levels. For the alternative method, see Steps for configuring tracing levels for InterChange Server Express, business objects, and collaborations.
Perform the following steps to configure the collaboration object trace
level:
- In System Manager, go to the InterChange Server Component Management view,
right-click the collaboration object, and click Properties.
The Properties dialog box appears.
- Do one of the following on the Collaboration General Properties tab:
Perform the following steps to configure connector tracing:
- From System Manager, right-click the connector object, then click
Edit definition. The Connector Configurator Express window
appears.
- Do one of the following:
- To set a connector controller's tracing level, from the Standard
Properties tab, click in the Value field of the
ControllerTraceLevel property, then set the controller tracing
level.
- To set a connector agent's tracing level, from the Standard Properties
tab, click the Value field of the AgentTraceLevel
property, then set the agent tracing level.
- Click File > Save > To Project.
- Close Connector Configurator Express.
Any changes to these properties take effect immediately. Trace
messages for connector controllers appear wherever InterChange Server Express
sends its trace messages, and trace messages for connector agents appear
wherever the connector agent logs messages.
- Note:
- If you want to specify a logging and tracing file for the connector agent,
you must specify a local configuration file when starting the agent.
Perform the following steps to set the trace level for a map:
- In System Manager, go to the InterChange Server Component Management view,
right-click the map object, and click Properties. The Maps
Property Page appears (see Figure 52).
Figure 52. Maps Property Page

- In the Trace Level field, type the appropriate value.
- Click OK.
