Hope it helps you in differencing the modes -
##############################################################
CA APM/Introscope 9.1 introduced a new agent transaction structure with new
tracers that replaces the transaction blame stacks that the old tracers
were using in previous releases. This new mode implementation optimizes
computation and processing to improve overall agent performance.
With CA APM/Introscope 9.1 customers can configure and run their agents in
the traditional pre-APM 9.1 transactional blame stacks instead of the new
transaction structure. This legacy mode of the agent is fully supported
but agent enhancements in future releases will only be implemented in the
new agent architecture. In CA APM 9.1.x, 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
Running old or legacy tracers with the APM 9.1.x agent in new mode is
known as mixed mode configuration. Do not run in mixed mode as this can
lead to additional memory consumption and service interruption. Customers
who have legacy mode tracers must also run the agent in legacy mode
until their tracers have been upgraded to the new agent mode. The following
message is written to the agent log to inform customers when they have
legacy tracers that must be updated. Revert to run the agent in legacy
mode in the interim.
"An agent tracer using legacy API s has been detected. Running legacy
tracers with the agent in new mode is not recommended. Please contact
support who can refer you to documentation on how to upgrade your legacy
tracers. In the interim, please configure the agent to use legacy mode or
use the pre-configured version of the legacy agent package. For example,
the legacy package for the Oracle WebLogic agent on UNIX is
IntroscopeAgentFiles-Legacy-NoInstallerx.x.x.xweblogic.unix.tar"
In addition, customers using the following out-of-the-box extensions must
configure their agents to run in legacy mode.
- CA APM for IBM WebSphere Portal
- CA APM for IBM CICS Transaction Gateway
- CA APM for IBM z/OS
- CA APMfor CA SiteMinder Web Access Manager
- CA APM Integration for CA LISA
########################################################################################
Regrads,
Vaibhav