Writing Activity Logs to files

You can define an Activity Log policy to write your Activity Logs to a file system. Configure the policy to capture the Activity Log data that you are interested in.

About this task

Use the filtering capabilities of this feature to customize the log content and make it relevant to your needs. You can configure the size and number of log files and the criteria by which the log rotates from one file to the next. You can also identify the location and file name of the log files.

You can use the Activity Log policy to configure the following Activity Log file characteristics:

  • Whether file logging is enabled
  • The maximum number of files used for each log
  • The maximum size of the log files (before the log rotates to the next file). If the maximum size is not reached, and the integration server is restarted, a new log file is created.
  • The maximum age of the log files (before the log rotates to the next file)
  • Filters that determine the content of the logs
  • The severity levels of messages logged
  • The log path and file name
  • Whether messages are formatted with inserts included in the message text
  • The scope of the policy (which integration server it applies to)

For more information about the properties that can be set and their possible values, see Activity Log policy (ActivityLog). The scope of the settings is the integration server. For example, if you set the Number of log files property to 5, each integration server has a maximum of five files for its Activity Log.

The files are in UTF-8 format.

Procedure

  1. Create an Activity Log policy by using the Policy editor in the IBM® App Connect Enterprise Toolkit (see Creating policies with the IBM App Connect Enterprise Toolkit).
  2. Define appropriate values for the properties in the policy, as described in Activity Log policy (ActivityLog).

What to do next

Deploy the Activity Log policy before or with the message flows that it applies to.