IBM App Connect Enterprise logs

IBM® App Connect Enterprise 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:

Activity log

Activity logs help you to understand what your message flows are doing by providing a high-level overview of how IBM App Connect Enterprise interacts with external resources. They do not require detailed product knowledge, and can be used to enhance understanding of the overall system. Use activity logs as the first point of investigation when something unexpected happens in a message flow and associated external resources. For more information, see Activity logs.

Admin log

IBM App Connect Enterprise stores a log of administration activity for each integration node and integration server. You can view the events that are held in memory by integration nodes or servers, either in the Admin Log tab of the web user interface or by using the administration REST API. You can also configure an integration node or server to write admin log entries to a file. For more information, see Viewing administration activity in the admin log and Writing admin log entries to a file.

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/ACET13/workspace/
  • Windows platformWindows: C:\Users\user_ID\IBM\ACET13\workspace\

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

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 App Connect Enterprise 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.