Previous Topic: Java Agent Component FilesNext Topic: Uninstall the Java Agent Component Files


Running with Legacy Mode PBDS

You can run with legacy versions of the PBDS instead of the new mode versions that are already placed in the directory <Agent_Home>\wily\core\config.

Follow these steps:

  1. Select and run the Java agent installer for your environment.

    Note: For more information about legacy mode pbds, see the CA APM Java Agent Implementation Guide.

    After you run the installer, verify that these files are in the following directories:

  2. Enable the legacy tracers:
    1. Copy the CTG_ECI_Tracer_For_SYSVIEW-legacy.pbd and WS_Tracer_For_SYSVIEW-legacy.pbd from the <Agent_Home>\wily\examples\legacy directory to the existing <Agent_Home>\wily\core\config directory of the Introscope agent.
    2. Make the following edits:
      • Append CTG_ECI_Tracer_For_Sysview-legacy.pbd to the introscope.autoprobe.directives property. For example:

        introscope.autoprobe.directivesFile=CTG_ECI_Tracer_For_Sysview-legacy.pbd,hotdeploy.

      • Edit <EM hostname> to point to the Enterprise Manager computer. For example:

        introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=<EM hostname>.

    3. Add the ctgclient.jar file to the classpath. For example, "C:\Program Files\IBM\CICS Transaction Gateway\classes\ctgclient.jar;". This path must be the same location that the monitored CTG client application uses.
    4. Configure the CTG CA SYSVIEW Agent:

      Copy the contents of the configuration template file Cross-Enterprise_APM_CTG_Config_Template.profile in the <Agent_Home>\wily\core\config directory into the IntroscopeAgent.profile file in the <Agent_Home>\wily\core\config directory. The template contains directions on how to use these additional configuration options. The options allow you to specify whether your installation supports CTG channels, and the transactions to be traced by matching on the program.

    5. Restart the CTG-based legacy client application that the Java agent monitors. The client application can itself be an application server.
  3. Enable the web services CA SYSVIEW tracer:
    1. Install the SOA Performance Management tracer in <Agent_Home>\wily\examples\SOAPerformanceManagement by copying all files in the ext directory to the <Agent_Home>\wily\core\ext directory.

      Note: For more information, see the CA APM for SOA Implementation Guide. Install the legacy version of the SOA tracer.

    2. Copy the ext\com.wily.introscope.ext.sysview.agent_<version>.jar and ext\WS-SYSVIEW-Tracer.jar files from the <Agent_Home>\wily\examples\Cross-Enterprise_APM\ext directory to the existing <Agent_Home>\wily\core\ext directory of the Introscope agent.
    3. Verify that the WS-SYSVIEW-Tracer.jar and com.wily.introscope.ext.sysview.agent_<version>.jar files are in the <Agent_Home>\wily\core\ext directory.
    4. Verify that the WS_Tracer_For_SYSVIEW-legacy.pbd file is in the <Agent_Home>\wily\core\config directory.
    5. Make the following edits to the IntroscopeAgent.profile file in the <Agent_Home>\wily\core\config directory:
      • Append WS_Tracer_For_SYSVIEW-legacy.pbd to the introscope.autoprobe.directives property. For example:

        introscope.autoprobe.directivesFile=websphere-typical.pbl, hotdeploy, spm.pbl,WS_Tracer_For_SYSVIEW-legacy.pbd

      • Edit <EM hostname> to point to the Enterprise Manager computer. For example:

        introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=<EM hostname>

    6. Restart the web services client application that the Java agent monitors. The client application can itself be an application server.
  4. Enable the configuration templates by copying the Cross-Enterprise_APM_CTG_Config_Template.profile to the IntroscopeAgent.profile.