Content Manager Service Test

Content Manager is the IBM Cognos BI service that manages the storage of customer application data, including interactive visualization discovery, relational metadata service, security, configuration data, models, metrics, report specifications, and report output. Content Manager is needed to publish packages, retrieve or store report specifications, manage scheduling information, and manage the Cognos namespace. Content Manager stores information in a content store database. The Content Manager Service is responsible for managing the content store. In addition to managing the content store, this service also performs authentication-related activities. If the Content Manager service is unavailable or fails to process the requests, then, data could not be stored in the content store database. This will lead to out dated data being stored in the content store and the reports using the data too will eventually be outdated. Also, the businesses using those reports too will be severly affected. To avoid such an outcome and to ensure that the content store is up to date, it is necessary for the administrators to monitor the Content Manager Service at all times. The Content Manager Service helps administrators in this regard!

This test monitors the Content Manager Service and reports the current status of the service. This test also throws light on the number of 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. Using this test, administrators can also figure out the count of documents that were successfully imported / failed to be imported into the Content store from an external data source.

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

Configurable parameters for the test

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.

Measurements made by the test

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: Measure Value Numeric Value Available 100 Unavailable 0 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
Free space	Indicates the amount of space that is available for use in the Content store.	MB	A high value is desired for this measure. A value close to 0 indicates that the Content store is running out of space. Administrators should add additional space before the Content store can no longer store information in it.
Used space	Indicates the amount of space that was already utilized in the Content store.	MB
Successful externalized documents	Indicates the number of documents that were successfully imported into the Content store during the last measurement period.	Number
Percentage of successfully externalized documents	Indicates the percentage of documents that were successfully imported into the Content store during the last measurement period.	Percent
Failed externalized documents	Indicates the number of documents that failed to be imported into the Content store during the last measurement period.	Number
Percentage of failed externalized documents	Indicates the percentage of documents that failed to be imported into the Content store during the last measurement period.	Percent