This test closely observes the time taken by the messaging engine to send a message to the MessageBox and to send a message in the MessageBox to the target destination, and proactively alerts administrators to delays; this way, administrators will not only be able to promptly detect latencies experienced by the messaging engine, but will also be able to pin-point where the delay originated - while delivering messages to the MessageBox? or while delivering messages to the destination application?

This page depicts the default parameters that need to be configured for the BTMsgLatTest.

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

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• Specify the port at which the specified host listens in the PORT text box.

• If the ISPASSIVE parameter is set to YES, then it means that, by default, all BizTalk servers being monitored by the eG system are the passive servers of a BizTalk cluster. No alerts will be generated if the servers are not running. Measures will be reported as "Not applicable" by the agent if the servers are not up.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.