This page describes the compatibility mapping between Agent and Controller Tenant versions.
Agent and Controller Tenant Compatibility Mapping
Please refer to the Language Agent Backward Compatibility table for AppDynamics Agents and AppDynamics Controller Tenant compatibility.
As long as all agents are compatible with the Controller Tenant version, a monitored environment may have different agent versions deployed in it at a given time. However, the oldest agents should be on originating tiers of any business transactions. This ensures that agents on downstream nodes can process the correlation header created by the originating tier.
When rolling out agent upgrades, be sure to start upgrading the agents on the nodes of downstream tiers first, and then upgrade the agents on the originating tier nodes last.
Language Agent Backward Compatibility
This table outlines the Controller Tenant and language agent releases that are compatible.
Starting in release 20.2, the AppDynamics language agents are backward-compatible with any Controller Tenant, including those using Calendar Versioning >= 20.3.
The Database Agent >= 20.7 is compatible only with the Controller Tenant >= 20.2.
| Controller Tenant Release | Language Agent Release | Notes |
|---|
| >= 20.3 | >= 20.2 | Controller Tenants >= 20.3 can accept connections from Agents >= 20.2 that use Calendar Versioning. |
The above table is only a reference for general software compatibility. For specific maintenance and support terms, refer to your specific EULA.
Backward compatibility is supported on these agents:
- C/C++ SDK
- Cluster
- Go SDK
- Java
- IBM Integration Bus (IIB)
- Machine
- .NET
- Node.js
- PHP
- Python
While using the Enterprise Console to upgrade the Controller Tenant, several folders (including the appagent folder) are removed and reinstalled. If you deployed a Java Agent with a newer version than the Controller Tenant in the controller/appserver/glassfish/domains/domain1/appagent folder, the upgrade will fail and internal monitoring will be lost. To prevent this, you must update the domain.xml file to point to the new Java Agent or avoid using the custom installation for Java Agents.
For notes on SSL protocol compatibility between versions of the agent and Controller Tenant, see SSL Compatibility Matrix for App Agent for Java - Controller.
Agent Versions Compatible with Controller Tenant 22.x
For compatibility of the agents with the Controller 23.x, see Agent Versions Compatible with Controller Tenant 23.x.
| Agent Version/Agent Type | Languages Agents | Cluster Agent | | AppDynamics for Databases | Machine Agent | Network Agent | Analytics Agent |
|---|
| IIB Agent | Java Agent | .NET Agent | Node.js Agent | PHP Agent | Python Agent | Web Server Agent | Go SDK | C/C++ SDK |
|---|
| >= 22.x | | | | | | | | | | | |
| | | |
| >= 21.x | | | | | | | | | | | |
| | | |
| >= 20.x | | | | | | | | | | | |
| | | |
SSL Compatibility between Java Agent and Controller Tenant
The default protocol used by the Controller Tenant is TLSv1.2. See Secure the Platform for information on changing the default security protocol used by the Controller Tenant or agent.
For the Java Agent, the default protocols are:
- For Java 8 SE applications: TLSv1.2.
- For Java >= 7 applications: TLSv1.2.
SSLv3 has been disabled for SaaS Controller Tenants because of the CVE-2014-3566 vulnerability. SSLv3 connections are no longer supported.
Introduction of New Agent Features
Even when new and old agents are supported by the same up-to-date Controller Tenant, new functionality introduced by later agents is not available on the older agents.
