This test is used to report the server activities such as number of used connections with the server, the number of messages that are sent to the queue and the number of messages that are retrieved from the queue , number of sessions created and the number of messages that are present in the durable subscriptions. These statistics can be pertained either by using the show server or show config commands.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• Prior to monitoring the Tibco EMS server, you will have to build a .bat or .sh file (depending upon the operating system on which Tibco EMS is functioning) bundled with the commands that the eG agent needs to execute on the Tibco EMS server for collecting the required metrics. The commands to be invoked by the the .bat or .sh file are as follows:

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show server

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show durables

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show queues

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show topics

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show connections

  For instance, if the IP address of your Tibco EMS server is 192.168.10.28 and its port is say, 9090, then a sample command in the .bat or .sh file would be:

  tcp://192.168.10.28:9090 show server

  The .bat/.sh file so created can be saved to any location on the Tibco EMS host. Then, while configuring this test, make sure you provide the full path to this .bat or .sh file in the COMMANDPATH text box so that, the agent can execute the file, invoke the commands bundled into it, and extract the desired metrics from the server.

• Once the above value is provided, click on the Update button to register the changes made.