Getting started with monitoring

Monitoring for AS4 Microservice includes monitoring document exchanges between AS4 Microservice and trading partners, AS4 Microservice operating status, and monitoring the WebSphere MQ queues.

If you are going to use the AS4 Microservice user interface to monitor document exchanges, and not a third-party application you do not have to configure anything in AS4 Microservice. If you want to use a third-party application to monitor AS4 Microservice document exchanges, you create a visibility event subscription for the application. If you want to be alerted when the system cache memory usage is getting high, you configure the low and high water mark for memory usage warnings. Use this checklist to track the configuration tasks that you need to do.

Checklist for monitoring document exchanges

Use this checklist to track the tasks you need to do for your installation for monitoring document exchanges.
Are you using the AS4 Microservice user interface to monitor document exchanges? Action
Yes, the AS4 Microservice user interface is the only method to be used for monitoring document exchanges. You do not have to configure anything for monitoring.
Yes and I will also use a third-party application monitoring system.
You need to:
  1. Create a custom visibility event subscription for the third-party application. An associated queue that the application can listen on is created with the subscription.
  2. Configure your third-party application to listen on the associated queue. The application listens on the queue that is created with the subscription to receive messages.
No, I will use only a third-party application monitoring system
You need to:
  1. Create a visibility event subscription for the third-party application. An associated queue that the application can listen on is created with the subscription.
  2. Configure your third-party application to listen on the associated queue. The application listens on the queue that is created with the subscription to receive messages.
  3. Remove the default visibility event subscription, internal.
    Remember: There must always be at least one visibility event subscription. Create the visibility event subscription for the third-party application before you remove the default subscription.

Checklist for system cache memory usage

Use this checklist to track the tasks you need to do for your installation for monitoring document exchanges.
Do you want to receive warning message about cache memory usage? Action
Yes
You need to:
  1. Configure the cache memory watermarks in the \Members\WXSContainer\usr\servers\WXSContainer\customerPostServer.xml file.
No You do not need to configure anything for monitoring.