Configuration of CogConMngrCaTest

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.

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

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

• In the HOST text box, specify the IP address of the IBM Cognos BI that is being monitored.

• In the JMX REMOTE PORT text box, 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.

• By default, JMX requires no authentication or security (SSL). This is why, by default, the JMX USER and JMX PASSWORD 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.

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

• Once the above values are provided, click on the UPDATE button to register the changes made.

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.