AMH Physical Node Test

Alliance Messaging Hub (AMH) is a modular, financial messaging solution for corporate networks. It allows extensive throughput and sophisticated data management through the use of latest technology to manage messages and files. The AMH system is composed of a number of physical nodes which are nothing but servers running AMH software. Given that each node is the building block of entire system and provides all compute power, it is important that each node works optimally.

This test monitor the nodes, and collects key statistics about node performance its state, heartbeat, etc. These metric provide administrators with valuable insights about the health of the node and any potential issues which can be handled before it affects the entire system.

Target of the test : A Swift AMH Node instance

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Swift AMH physical node being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port at which the specified host listens.
SSL	If the target node being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No.
JMX Remote Port	Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target node.
JNDI Name	Specify the lookup name for connecting to the JMX connector of the Swift AMH.
JMX User, JMX Password and Confirm Password	These parameters appear only if the Measurement Mode is set to jmx. If JMX requires authentication only (but no security), then ensure that the JMX User and JMX Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter. Confirm the password by retyping it in the Confirm Password text box.
Execrule.sh location	Specify the full path of execrule.sh file which provides details of physical nodes.
Cluster Static Info File location	Specify the full path of cluster static file which contains details of logical cluster.
Process	Provide the details of the two processes which are to be monitored by test. There are 2 ways to configure the processes: Using the get process button which shows all the processes running in the Swift AMH Physical Node machine wherein the agent is deployed. The other option is to manually provide key value pair of process name and process pattern.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measures made by the test

Measurement

Description

Measurement Unit

Interpretation

Is this node part of the cluster?

Indicates if the current node is part of cluster or standalone.

The numeric values that correspond to these measure values are as follows:

Measure Value	Numeric Value
Yes	10
No	0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate Is this node part of the cluster?. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Physical node state

Indicates the current state of current physical node.

The numeric values that correspond to these measure values are as follows:

Measure Value	Numeric Value
Running	20
Degraded	10
Stopped	5
Not running	0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the Physical node state. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Time since last heartbeat

Indicates the time since the last heartbeat check was received by current physical node.

Minutes

If it has been very long and over the threshold value, it needs to be investigated.

Logical nodes recently added to physical node

Indicates the number of logical nodes that were added to current physical node since last measurement.

Number