bj55030_.htm |
Last updated Friday, 21 July 2017Activity logs help users to understand what their message flows are doing by providing a high-level overview of how IBM® Integration Bus interacts with external resources. They do not require detailed product knowledge, and can be used to enhance understanding of the overall system.
Activity log messages are concise and avoid technical complexity, although more information is provided in the message detail. Because the log entries are short, uncomplicated, and focused on single activities, they can be quickly scanned and understood. Patterns of behavior and changes to such patterns are easier to identify than in more extensive product trace. The qualitative data about resources provided in Activity logs complements the quantitative resource data provided by resource statistics.
The Activity Log view in IBM Integration Explorer provides a graphical view of recent Activity log events, as well as extensive facilities for organizing and filtering data. Logs can be generated for individual message flows or resource types. You can have multiple Activity Log views for flows and resource types open simultaneously. You can also save a view to a file in Comma Separated Value (CSV) format or copy and paste a selection of the data.
Activity logs can also be written to a circular file system. Use the ActivityLog configurable service to set up file logging if you want continuous logging of activities over a long period.
The configurable service and the IBM Integration Explorer Activity Log view both have extensive filtering capabilities, based on tags. Tags allow you to search or filter on various attributes, such as resource types or message flow names. All Activity log messages have several tags which are displayed in the log entries and can be used as search and filter keys. Individual resource types also have resource-specific tags that you can use to retrieve the data that you are interested in.
Activity logs can be retrieved programmatically by using the IBM Integration API (CMP).
Because Activity logs are enabled by default, they can be useful for troubleshooting. For example, if the Activity log for a message flow shows a prolonged period of inactivity, review the Activity logs for associated resource types. You might discover that a problem with an external resource is the reason why messages are no longer being processed by your message flow.
Last updated Friday, 21 July 2017