IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

---

Enable Asynchronous Bean request monitoring

If your applications use asynchronous bean requests, and the requests are not displayed in the Tivoli Enterprise Portal or the Visualization Engine, enable Asynchronous Bean request monitoring using the Toolkit custom properties file..

First, check whether custom requests have been defined on the Data Collector.

Open the toolkit custom properties file and, if it exists, the global toolkit custom properties file. Check both of these files for the following property (not commented out):

am.camtoolkit.gpe.customxml.custom=xml_filename

If this property exists, custom requests have been defined. Edit the XML file named in the property. If both the instance specific toolkit custom properties file and the global toolkit custom properties file have this property, use the filename from the instance specific file. If the filename does not have a path, the file is located in directory...

DC_home/runtime/app_server_version.node_name.server_name/custom

Find the tag...

</customEdgeRequests>

...and add the following text immediately before this line:

   
  <edgeRequest>
    <requestName>AsyncWorkBean</requestName>
    <Implements>com.ibm.websphere.asynchbeans.Work</Implements>
    <type>application</type>
    <methodName>run</methodName>
   </edgeRequest>
   <edgeRequest>
    <requestName>AsyncTimerBean</requestName>
    <Implements>commonj.timers.TimerListener</Implements>
    <type>application</type>
    <methodName>timerExpired</methodName>
   </edgeRequest>
   <edgeRequest>
    <requestName>AsyncAlarmBean</requestName>
    <Implements>com.ibm.websphere.asynchbeans.AlarmListener</Implements>
    <type>application</type>
    <methodName>fired</methodName>
   </edgeRequest>

If the property does not exist (or is commented out), custom requests have not been defined. In this case:

1. create a new file: DC_home/runtime/app_server_version.node_name.server_name/custom/custom_requests_async.xml, with the following text:

   <gpe>
    <bci>
     <customEdgeRequests>
      <edgeRequest>
       <requestName>AsyncWorkBean</requestName>
       <Implements>com.ibm.websphere.asynchbeans.Work</Implements>
       <type>application</type>
       <methodName>run</methodName>
      </edgeRequest>
      <edgeRequest>
       <requestName>AsyncTimerBean</requestName>
       <Implements>commonj.timers.TimerListener</Implements>
       <type>application</type>
       <methodName>timerExpired</methodName>
      </edgeRequest>
      <edgeRequest>
       <requestName>AsyncAlarmBean</requestName>
       <Implements>com.ibm.websphere.asynchbeans.AlarmListener</Implements>
       <type>application</type>
       <methodName>fired</methodName>
      </edgeRequest>
     </customEdgeRequests>
    </bci>
   </gpe>

2. In the toolkit custom properties file (see The Toolkit properties file), set the property:
   am.camtoolkit.gpe.customxml.custom=custom_requests_async.xml

After performing the changes described in this section, restart the application server instance monitored by the data collector.

Parent topic:

Tune data collector performance and monitoring scope

---

+

Search Tips   |   Advanced Search