IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

data collector configuration fails

The following content provides solutions when the Data Collector configuration fails.


Net Weaver data collector cannot be configured

The problem: Net Weaver data collector configuration fails when the data collector is installed in an English locale but configured in a Turkish locale.

The solution: Re-install the data collector in a Turkish locale.


WebLogic 9 data collector configurator cannot create Startup/Shutdown class

The problem: The data collector configurator cannot create the Startup/Shutdown class. The admin server returns an error like:

weblogic.management.provider.EditFailedException: [Management:141201] 
Unable to modify the configuration using the compatibility MBean server 
as other changes are pending. 
Activate the pending changes before modifying the configuration with the 
compatibility MBean server.

The solution: The WebLogic 9 configuration is locked by the admin console, try to release the configuration lock from admin console and try again. Restart the WebLogic server after you try this.


WebLogic data collector cannot be configured with Weblogic 9 and JRocket

The problem: When configuring WebLogic data collector with Weblogic 9 and JRocket, the configuration process fails.

The cause: This problem is caused by the WebLogic 9 admin console. data collector configurator is unable to add, update, or remove the MBean while the meta repository is locked by the admin console.

The solution: Unlock the WebLogic 9 application server by clicking Release Configuration in the Change Center panel of the admin console before configuring the data collector. If there are pending changes, save your changes and then click Activate Changes in the Change Center panel.


WebLogic Server rejects data collector configuration - JNDI connection

The problem: The WebLogic Server rejects the data collector configuration JNDI connection and reports Certificate chain receieved from <ip> was incomplete on the console. But from the admin console, the SSL attribute Two Way Client Cert Behavior has been set to Client Certs Not Requested.

The solution: Change the attribute Two Way Client Cert Behavior to Client Certs Request But Not Enforced and save it. Then change the attribute value to Client Certs Not Requested.


Parent topic:

data collector

+

Search Tips   |   Advanced Search