Monitoring exchanges with third-party applications

Exchange event messages that are generated in AS4 Microservice can be made available to third-party monitoring applications with a configured visibility event subscription.

You can enable your third-party monitoring applications to retrieve exchange event messages that are generated in AS4 Microservice. Configure the application to listen on the queue that is associated with the custom visibility event subscription to retrieve event messages from that queue. MEG.UI.VISIBILITY.EVENT.INTERNAL is the default queue that is created at installation to which all exchange and event messages are delivered for the default internal subscriber. You can use Advanced Search and Exchange and Event Details to view all exchange and event messages sent to this queue.

Exchange event monitoring

A visibility event message is generated for each event that occurs during an exchange. You can view all of the events for a particular exchange on the Exchange and Event Details page, if you click the Transaction ID for the exchange. You can search for exchanges by the transaction identifier, process identifier, or reference identifier. You can also filter the search results by time, exchange profile, status, pattern, trading partner, external references, and receiver.

Custom visibility event subscriptions and AS4 Microservice queues

When you create a custom visibility event subscription, an associated queue is created in WebSphere® MQ. Creating a subscription puts a subscriber on default publish/subscribe endpoint, MEG.UI.VISIBILITY.EVENT. The queue that is created includes the name of the new visibility event subscription in the suffix. For example, if a visibility event subscription with the name, subscription_name, is created, a queue that is named MEG.UI.VISIBILITY.EVENT.SUBSCRIPTION_NAME is also created.

All of the custom visibility event subscriptions that are created in AS4 Microservice, receive the same event messages that are sent to the default visibility event queue, MEG.UI.VISIBILITY.EVENT.INTERNAL. Any third-party monitoring application that listens to a custom subscription receives the same event messages that are generated in the default visibility queue.