IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Data is not correctly shown

The following content provides some solutions when data is not correctly shown.


Database Connection Pool information is not showing up

The problem: Database Connection Pool information is not present on the Managing Server.

The solution: Perform the following:

  1. Verify that the JDBC Connection Pools PMI setting is enabled in WAS for the data collector.

    • beanModule=X

    • cacheModule=H

    • connectionPoolModule=X

    • j2cModule=H

    • jvmRuntimeModule=H

    • orbPerfModule=H

    • servletSessionsModule=H

    • systemModule=H

    • threadPoolModule=H

    • transactionModule=H

    • webAppModule=H

    • webServicesModule=H

    • wlmModule=H

    • wsgwModule=H

  2. For z/OS, verify that com.ibm.websphere.management.enableConfigMbean is set to 'true' in WAS for the data collector.
  3. Once the above mentioned items are set, stop and start the AppServer on the data collector. It is important to remember that the System Resources > DB Connection Poolsdisplays data only after a request is running in the monitored WAS and accesses the Datasource. Before that happens, the display for the Datasource will continue to show 'Data Not Available'.

To force DB Connection Pool data:

  1. Run a request in the server where the 'Data Not Available' message is. Set the monitor on demand level to L2 and 100% sampling to collect a trace on the request. Ensure that the L2 trace shows that traffic is flowing to the JDBC dataSource successfully in that server before proceeding.

  2. After 1) is confirmed, then check the System Resources > DB Connection Pools display for the common DataSource in the server and look for processing statistics to appear then.

If the value is showing up as 0 (zero), there is a fix if the data collector is on z/OS (APAR PK17518). A 0 value has not been an issue that has been identified on the other Operating Systems at this time so there are no APARs for those platforms.


No data received on custom MBean

The problem: After configuring a custom MBean, on the VE side, the user can see the custom category but when they click the category it returns a NO DATA AVAILABLE error message.

The solution: Check your custom MBean configuration file, make sure all category names are in uppercase and contain only letters, no blanks and no other characters.


No GC data is available in the Recent Active Display and Memory Diagnosis page of the Managing Server Virtual Engine

The problem: No GC data is available in the Recent Active Display and Memory Diagnosis page of the Managing Server Virtual Engine.

The reason: Verbose GC is not enabled and the path to the WebSphere native_stderr.log file is not specified in the TEMAGCCollector.gclog.path property.

The solution: You can solve this problem according to the following steps:

  1. Enable verbose GC for WAS in the Admin Console or adding -verbose:gc to JVM arguments in the server.xml file.

  2. Append the next property in the DC_home/runtime/RUNTIME/SERVER.kwjdc.properties file: 
    TEMAGCCollector.gclog.path = <PATH_TO_WebShere native_stderr.log>

  3. Restart WAS.


No Tivoli Enterprise Portal event reported on Alerts and Events page

The problem: An event is reported on Tivoli Enterprise Portal but not on the Alerts and Events page.

The solution: Follow these steps to set the Tivoli Enterprise Monitoring Server information:

  1. Edit MS_home/etc/dal/dal.properties and enter the Tivoli Enterprise Monitoring Server host information: 

    dal.tema.hostName=[TEP hostname or IP address]
dal.tema.port=[TEP port number]
dal.tema.useHttps=[true or false]

  2. Edit MS_home/etc/dal/TEMAQuerySchema.xml and enter the Tivoli Enterprise Monitoring Server login information: 

    <parameter name="userid" value="sysadmin"></parameter>
<parameter name="password" value="password"></parameter>
<parameter name="passwordEncrypted" value="false"></parameter>

  3. Restart Managing Server.

A Managing Server can retrieve data from one Tivoli Enterprise Monitoring Server only and you cannot configure a Managing Server to retrieve event data from multiple Tivoli Enterprise Monitoring Server. Therefore, it is recommended that all data collectors under the same Managing Server are connected to the same Tivoli Enterprise Monitoring Server.


System Data not available in WAS ND and cluster configurations

The problem: System level statistics are not available at the server level in an ND or cluster environment. The following fields are not available ("N/A") on the JVM/System Detail report:

The reason: They are collected from the Node Agent. This is due to the design of ND, which typically places one Node Agent on each system in place. The Node Agent is responsible for information gathering and reporting when there are multiple servers on a single system.


Parent topic:

Run the Managing Server

+

Search Tips   |   Advanced Search