|
Default
Parameters for CBWorkQueueTest
The job queue contains Connection Broker processes that are independent of the Web interface. If you think your Connection Broker is not functioning correctly, you can use the job queue as a diagnostics tool. For instance, if you requested an action and it has not taken place, check if the action is pending in the job queue.
The CBWorkQueueTest monitors the job queues and reports the status of jobs queued on the Connection Broker. This page depicts the default parameters that need to be configured for the CBWorkQueueTest.
By default, SSL flag is set to No, indicating that by default, the test connects to the Connection Broker via HTTP. If the Connection Broker is SSL-enabled, then set this flag to Yes.
-
To enable the test to log into the Connection Broker and extract statistics of interest from it, specify the login name of a user in the USER textbox on the Connection Broker who is assigned the Administrator role. If need be, you can even create a special Administrator user on the Connection Broker for this purpose, and pass the credentials of that user to the test.
-
This test also reports the number of jobs in the queue that were recently completed. The detailed diagnosis of this measure, if enabled, will provide the details of all the newly finished jobs. In some environments, the count of the newly finished jobs could run to a thousand. In such environments naturally, the detailed diagnosis data for this measure, if available, will consume a considerable amount of database space, and can sometimes even choke the database. To reduce the strain on the database, the eG agent, by default, does not collect detailed diagnosis information for the New finished jobs measure. Accordingly, the SHOWFINISHEDDDflag is set to No, by default. If you want to view the detailed diagnosis for this measure, then set this flag to Yes.
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.
|