Configure the Agent to Use Legacy Mode Transaction Tracing

You need to run your agent in legacy mode only if you are using an extension that has not been ported to new mode. CA APM versions before version 9.1 do not have new mode.
apmdevops106
You need to run your agent in legacy mode only if you are using an extension that has not been ported to new mode. CA APM versions before version 9.1 do not have new mode.
Follow these steps:
  1. Stop the monitored application.
  2. Archive and delete existing log files in the
    <Agent_Home>
    /logs directory to prepare for new logs.
  3. Back up the existing .pbl and .pbd files in the
    <Agent_Home>
    /core/config directory.
  4. Back up the existing
    <Agent_Home>
    /core/config/IntroscopeAgent.profile.
  5. Copy the legacy .pbl and .pbd files from the
    <Agent_Home>
    /examples/legacy directory to the
    <Agent Home>
    /core/config directory.
  6. Open
    <Agent_Home>
    /core/config/IntroscopeAgent.profile and make the following changes:
    • Add property introscope.agent.configuration.old=true
    • Update the agent property introscope.autoprobe.directivesFile to point to the appropriate legacy .pbl and .pbd files that have been copied over. For example, replace spm.pbl with spm-legacy.pbl
  7. Restart the monitored application.
Agent Legacy Mode Limitations
The following capabilities are not available when running the agent in legacy mode:
  • Agent CPU usage and response time optimizations in version 9.1
  • Dynamic Instrumentation for the .NET agent
  • SQL Agent properties
    introscope.agent.sqlagent.sql.artonly
    introscope.agent.sqlagent.sql.turnoffmetrics
  • Smart instrumentation
  • SAP Passport propagation
Running legacy tracers with the CA APM agent in new mode is known as “mixed mode” configuration. Never run the agent in mixed mode as it often consumes extra memory heap resulting in application outages.