Event Management Service Test
The Event Management service is responsible for the management of events. An event is any task that has run, is currently running, or will be run in future. The event management service manages the event execution queue. Events in the queue can be held for execution at a later time or removed from the queue. Events that are held can later be released for execution. Events to be run on an irregular basis can also be manually added to the event execution queue. These events are usually on-demand tasks or tasks that are executed in response to an external trigger condition.
The Content Manager Service works in conjunction with the Event Management Service to update the event execution queue whenever a schedule is added to, updated in, or deleted from the content store.
If the Event Management Service is unavailable, the event could not be executed on time and hence, the event execution queue may overflow with events. Also, the other services that are dependent of this service will be affected. Also, event execution may be hampered if multiple requests to the service failed. To avoid such issues, it is essential for an administrator to periodically monitor the Event Management Service. The Event Management Service test helps administrators in this regard!
This test monitors the Event Management Service and reports the current status of the service. This test also throws light on the number of Event Management Service requests that were successful/failed. This test helps administrators initiate troubleshooting to determine the reason for request failures and resolve the same at the earliest.
Target of the test : An IBM Cognos Business Intelligence
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the target IBM Cognos Business Intelligence suite being monitored
Parameter |
Description |
---|---|
Test period |
How often should the test be executed . |
Host |
The host for which the test is to be configured. |
Port |
The port number at which the specified host listens. By default, this is NULL. |
JMX Remote Port |
Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the p2pd.deploy_defaults.properties file available in the <IBM_COGNOS_BI_HOME>\webapps\p2pd\WEB-INF folder used by the target application server. |
JMX User, JMX Password, and Confirm Password |
By default, JMX requires no authentication or security (SSL). This is why, by default, the JMX User and JMX Password parameters are set to none. If JMX requires authentication only (but no security), then ensure that the JMX User and JMX Password parameters are configured with the credentials of an authorized user with access to JMX using the JMX Remote Port. Confirm the password by retyping it in the Confirm Password text box. |
Measurement | Description | Measurement Unit | Interpretation | ||||||
---|---|---|---|---|---|---|---|---|---|
Status |
Indicates the current status of the service. |
|
The values that this measure can report and their corresponding numeric values are listed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the current status of the service. In the graph of this measure however, the same is represented using the numeric equivalents only i.e., 0 or 100. |
||||||
Processed requests |
Indicates the number of requests that were processed during the last measurement period. |
Number |
|
||||||
Successful requests |
Indicates the number of service requests that were successful during the last measurement period. |
Number |
A high value is desired for this measure. |
||||||
Percentage of successful requests |
Indicates the percentage of processed requests that were successful during the last measurement period. |
Percent |
A value close to 100 percent denotes that most of the requests were processed successfully. |
||||||
Failed requests |
Indicates the number of service requests that failed during the last measurement period. |
Number |
A high value is a cause of concern. Administrators must analyze why the requests are failing frequently and initiate troubleshooting measures at the earliest. |
||||||
Percentage of failed requests |
Indicates the percentage of processed requests that failed during the last measurement period. |
Percent |
A value close to 100 is a cause of concern. A sudden / gradual increase in the value of this measure warrants administrators to initiate troubleshooting at the earliest. |
||||||
Successful requests per second |
Indicates the rate at which the requests were processed successfully during the last measurement period. |
Requests/sec |
|