|
Default Parameters for IIBCICSStatTest
This test auto discovers the CICS Transaction servers integrated with the target IBM Integration Bus and reports the numerical statistics of the requests that were successfly and the requests that failed. Using this test administrators can identify the processing ability of the CICS Transaction server and be proactively alerted to processing bottlenecks, if any.
This page depicts the default parameters that need to be configured for the IIBCICSStatTest.
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.
In the USERDN and PASSWORD text boxes, provide the credentials of the Active Directory user created as explained in the Monitoring IBM Integration Bus document, 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.
Specify the name of the JMS destination that you have created for storing the Resource statistics in the JMS RESOURCE STATS text box. To know the JMS destination name for storing Resource statistics (for both agent based and agentless monitoring of the IIB server), refer to the Monitoring IBM Integration Bus document.
Specify the name of the JMS destination that you have created for storing the Message flow statistics in the JMS FLOW STATS text box. To know the JMS destination name for storing Message flow statistics (for both agent based and agentless monitoring of the IIB server), refer to the Monitoring IBM Integration Bus document.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.
|