TCP Client Node Statistics Test

This test monitors the TCP connections to the TCP client node and reports the count of the connections that were open, closed and failed. In the process, this test proactively alerts administrators to processing bottlenecks on the TCP client node.

Target of the test : An IBM Integration Bus

Agent deploying the test : An internal/remote agent.

Outputs of the test : One set of results for each Execution Group:TCP Client node of the IBM Integration Bus that is to be monitored.

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port on which the specified host listens.
JNDI Namespace Location	Indicate where the JNDI namespace has been created. For this, select one of the following options: File or LDAP. Select File if the JNDI namespace is created in the same location as that of the IIB server.
SSL	If you have chosen LDAP as the JNDI Namespace Location wherein the LDAP server communicating with the IIB server that is to be monitored is an SSL-enabled server, then set the SSL flag to Yes. By default, this flag is set to No.
User DN and Password	Here, provide the credentials of the Active Directory user created as explained in Creating a user in the Active Directory server, if the target IIB server is monitored in an agentless manner. If the IIB server is to be monitored in an agent based manner, specify none against these parameters.
Confirm Password	Confirm the Password by retyping it in this text box.
JNDI Provider URL	Specify the URL that was specified as the provider URL while creating the initial context. To know the Provider URL, refer to Agent based monitoring of the IIB server if you choose to monitor the target IIB server in an agent based manner and Agentless Monitoring of the IIB server if you chose to monitor the target IIB server in an agentless manner.
TopicConnectionFactory	Specify the name of the connection factory in this text box. If you have chosen to monitor the target IIB server in an agent-based manner, refer to Creating a Connection Factory and if you have chosen to monitor the target IIB server in an agentless manner, refer to Creating a Connection Factory.
JMS Resource Stats	Specify the name of the JMS destination that you have created for storing the Resource statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.
JMS Flow Stats	Specify the name of the JMS destination that you have created for storing the Message flow statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Open connection	Indicates the number of connections that were open on this TCP Client node during the last measurement period.	Number
Closed connections	Indicates the number of connections that were closed on this TCP Client node since the start of the Integration server.	Number
Failed connections	Indicates the total number of attempted connections that failed since the start of the Integration server.	Number	Ideally, the value of this measure should be zero.
Message received rate	Indicates the rate at which messages were received by this TCP Client node during the last measurement period.	Messages/sec	These measures are good indicators of the load on the TCP Client node. Comparing the value of these measures across the TCP client nodes will help you identify the node that is busy processing messages/data.
Message sent rate	Indicates the rate at which messages were sent through this TCP Client node during the last measurement period.	Messages/sec	These measures are good indicators of the load on the TCP Client node. Comparing the value of these measures across the TCP client nodes will help you identify the node that is busy processing messages/data.
Data received rate	Indicates the rate at which data is received by this TCP Client node during the last measurement period.	Bytes/sec
Data sent rate	Indicates the rate at which data is sent by this TCP Client node during the last measurement period.	Bytes/sec
Data sent rate	Indicates the rate at which data is sent by this TCP Client node during the last measurement period.	Bytes/sec