IBM Integration Bus logs

IBM® Integration Bus writes information to a number of product-specific logs to report the results of actions that you take.

The following logs are used for reporting errors and events:

Eclipse error log

The Eclipse error log captures internal errors from Eclipse and the code associated with your user-defined extensions. Check this log at run time for exceptions that you might have caused during development. When errors are triggered, they are added to the Error Log view of the Plug-in Development perspective, and you can double-click each one to examine details. Entries are sorted in reverse chronological order; that is, most recent first. You can open the Properties view to see entry details. You can also clear the view when you have fixed all the errors, although you cannot clear individual errors.

Some errors might be hierarchical; that is, a general entry for a complex problem might be followed by a number of child entries that list the individual problems in detail.

The same information that is shown in the Error Log view is stored in the .log file in the .metadata directory of the workspace. The default location for the workspace directory depends on your operating system:

  • Linux platformLinux®: user_home_dir/IBM/IIBT10/workspace/
  • Windows platformWindows: C:\Users\user_ID\IBM\IIBT10\workspace\

The Eclipse error log shows errors that are generated only by the user ID that is working with that particular IBM Integration Toolkit session.

Integration node Administration log or Deployment log

Integration node Administration log information is written to the Administration log. This log is stored and managed by the integration node. The Administration log displays messages about events that occur within the integration node, such as the results of a deployment, or a change to integration node properties. The messages can be information, errors, or warnings. You view the messages in the Deployment log in the IBM Integration Toolkit.

The Problems or Alerts view

Either the Problems or the Alerts view is displayed, depending on the perspective being used at the time.
  • In the Integration Development perspective the Problems view shows information messages, warnings, and errors for message flow applications and associated resources, such as message flows, message sets, ESQL, Java™, and mapping.

TDS log

When you use the Tagged/Delimited String (TDS) physical format messages, you must conform to a number of rules that apply to the setting of values of properties. These rules are checked at deploy time, and, if an inconsistency is found, error message BIP1836 is displayed in the IBM Integration Toolkit. Details of the error are written to the TDS.log file in the install_dir/log directory.

For more information about the rules for TDS physical format properties, see Message Sets: TDS message model integrity.