IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Manually removing data collector configuration from an application server instance - WAS agent

If the agent has been uninstalled but the data collector was still configured to monitor any application server instances, these instances may fail to start. In this case, you need to manually remove data collector configuration from each instance.

Perform the following procedure:

  1. Log on to the WebSphere Administration Server Console.

  2. Click Server > Application Servers and select the server name.

  3. In the Configuration tab, navigate to Server Infrastructure > Java and Process Management > Process Definition > Additional Properties: Java Virtual Machine.

  4. Remove any of the following JVM Custom Properties, if they are present:

    • am.home

    • java.security.policy

    • com.ibm.tivoli.jiti.injector.ProbeInjectorManagerChain. primaryInjectorFile (if it is present)

  5. Remove the custom service named com.cyanea.ws6.ITCAMNotifierCustomService, if it is present.

  6. In Generic JVM Arguments:

    • Remove any JVM arguments that include the DC_home directory if they are present. There can be a -Xbootclasspath argument and a -agentlib argument.

    • Remove the -Xshareclasses:none and -verbosegc arguments if they are present. Remove the -Xtrace argument if it is present.

  7. Click Apply or OK.

  8. In the Messages dialog box, click Save.

  9. In the Save to Master Configuration dialog box, complete one of the following steps:

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

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

  10. In the Navigation Pane, click Environment > Shared Libraries.

  11. Change the scope to the specific application server instance.

  12. In the shared library named WPSlib, remove ${ITCAMDCHOME}/itcamdc/lib/wpsaspect.jar (the environment variable name may be different) from the classpath if it is present. If this was the only entry in the classpath, remove the WPSlib shared library.

  13. Click Apply or OK.

  14. In the Messages dialog box, click Save.

  15. In the Save to Master Configuration dialog box, complete one of the following steps:

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

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

  16. Back up the file: DC_home/installer/configured/WasConfiguredServers.xml

  17. Open the file for editing: DC_home/installer/configured/WasConfiguredServers.xml

  18. Look for an entry similar to the following text and referring to the application server instance for which the data collector was unconfigured:
    <instance id="C:\was7\profiles\AppSrv02|cells/CellIT71/nodes/NodeIT71
      /servers/server1">
    <node>CONFIG_FILE_STORE_DIR=C:/IBM/ITM/TMAITM6/wasdc/
      7.1.0.1\installer\configured\was70.NodeIT71.server1</node>
        <node>WAS_BASEDIR=C:\was7</node>
    </instance>

  19. If the entry was found, remove it.

  20. Save the file. Do not delete the file, even if no entries for application server instances remain.

  21. Restart the application server instance that was monitored by the data collector.


Parent topic:

Manual changes to application server configuration for the data collector