IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Re-enabling data collectors

If re-enable a data collector after you have disabled it, perform this procedure.

  1. Log into the IBM WAS administrative console.

  2. Depending on your application server version, complete one of the following steps:


    Navigation to Custom Services in the IBM WAS administrative console

    Version 6 or 7 application servers

    1. Click Server > Application Servers and select the server_name.

    2. Navigate to Server Infrastructure: Administration > Custom Services.

    Version 5 application servers

    1. Click Server > Application Servers and select the server_name.

    2. Navigate to Additional Properties: Custom Services.

  3. Highlight AM Custom Services.

  4. Click Edit.

  5. Check the Enabled box or change the server startup value to True.

  6. Click OK and then Apply.

  7. To re-enable the data collector Home Runtime, go back to your server_name link page and navigate to one of the following options:


    Navigation to Generic JVM arguments in the IBM WAS administrative console

    Windows, UNIX, and Linux

    • For version 5 application servers: Process Definition > Java Virtual Machine

    • For version 6 or 7 application servers: Server Infrastructure: Process Definition > Java Virtual Machine

    IBM z/OS

    • For IBM WAS 5.x: Process Definition > Servant > Java Virtual Machine

    • For IBM WAS 6.x: Server Infrastructure: Process Definition > Servant > Java Virtual Machine

  8. Enable the parameters that begin with the following strings of text (if they exist) in the Generic JVM arguments of the JVM command line properties section by removing the D after the dash (-):

    • -DXbootclasspathaffix:

    • -DXrunam_affix:

    • -Djlog.propertyFileDir.CYN=

    • -Dcom.ibm.tivoli.itcam.toolkit.util.logging.qualDir=

    • -Dcom.ibm.tivoli.jiti.injector.IProbeInjectorManager=

    • -Dibm.websphere.preload.classes=

    • -Dverbosegc

    • -DXverbosegclog:

    • -DXloggc

    For example, 

    -Xbootclasspath/p:${ITCAM61HOME}/toolkit/lib/jiti.jar;
${ITCAM61HOME}/toolkit/lib/bcm-bootstrap.jar;
${ITCAM61HOME}/itcamdc/lib/ppe.probe-bootstrap.jar 
-Xrunam_ibm_00:${ITCAM61HOME}/runtime/was60.esb60.tivoliNode01.server1/
    jiti.properties 
-jlog.propertyFileDir.CYN=${ITCAM61HOME}/toolkit/etc 
-com.ibm.tivoli.itcam.toolkit.util.logging.qualDir=tivoliNode01.server1 
-com.ibm.tivoli.jiti.injector.IProbeInjectorManager=
    com.ibm.tivoli.jiti.injector.ProbeInjectorManagerChain 
-ibm.websphere.preload.classes=false 
-verbosegc 
-Xverbosegclog:C:\Program~1\IBM\WebSphere\AppServer\
    profiles\AppSrv01\logs\server1\itcam_dc_gclog.log

    It is required to enable the following parameters only if they are parameters that were enabled before the data collector was disabled:

    • -jlog.propertyFileDir.CYN=

    • -com.ibm.tivoli.itcam.toolkit.util.logging.qualDir=

    • -com.ibm.tivoli.jiti.injector.IProbeInjectorManager=

    • -ibm.websphere.preload.classes=

  9. Add the following string to JVM Custom Properties: 
    com.ibm.tivoli.itcam.toolkit.ai.bcm.helper.class=
    com.ibm.tivoli.itcam.was.bcm.websphere.DefaultWASBCMHelper

  10. Click Apply.

  11. To re-enable the JNDI, add the following value in the class path. 
    DC_homeinstall_home/toolkit/lib/ext/

  12. Click Save.

  13. In the messages Dialog box, click Save.

  14. In the Save to Master Configuration dialog box:

    • If you are under Network Deployment environment, be sure the check box Synchronize changes with Nodes is selected and then click Save.

    • If you are not under Network Deployment environment, click Save.

  15. Restart the application server.


Parent topic:

Start and stop the monitoring environment

+

Search Tips   |   Advanced Search