Monitoring Swift AMH JBoss
The eG agent periodically executes tests on the SWIFT AMH using the JBoss AS/EAP server and JVM, collects the necessary statistics, and reports them to the eG manager. These tests are mapped to specific layers of the SWIFT AMH layer model (see Figure 1).
Figure 1 : The layer model of the Swift AMH JBoss
Using the metrics reported, administrators can find quick and accurate answers for the following performance questions:
-
How many JMS connection are currently active?
-
How many connections are inactive or timed out and can be recycled?
-
How many total JMS connections are currently established?
-
Are all the services currently fully operational?
-
What is the current status of services which are not fully operational?
-
How many services are currently in recovering state?
-
How many services are in stopping, stopped or start failed status?
-
How many services are in disabled status?
-
Is the input channel operational?
-
What is the status of input channel if not operational?
-
Are all the queues currently fully operational?
-
What is the current status of queues which are not fully operational?
The Operating System, Network, TCP, Application Processes and Windows Services layers of the AMH monitoring model is similar to that of a Microsoft Windows server model. Refer to the Monitoring Unix and Windows Servers document to know more about the tests pertaining to these layers. The JVM layer of this server is similar to that of the Java Application server monitoring model. Since the tests pertaining to these layers have been dealt with in the Monitoring Java Application servers document let us now discuss only the AMH Channels, AMH Connections, AMH Queue and AMH Services Layers in the forthcoming section. The JBoss Container Layer focuses on
