This page describes the requirements, supported environments, and versions supported by the Cisco Secure Application.

Cisco and AppDynamics and its products are not affiliated with Google or Google products. All references to Google products herein are for informational purposes only and Google retains all rights in all Google product names, logos, marks, and other trademarks.

Software Requirements

The Cisco Secure Application capabilities are integrated with the Java APM Agent, and therefore works on the following platforms:

  • Operating Systems - AIX, Linux, and Windows
  • Containers - All major container systems 
  • Languages - Java versions 7 to 14,  inclusive, Oracle, OpenJDK, Azul, and BM
  • Application Framework Support - All major frameworks such as Spring (see Java Supported Environments)
  • Application Server Platform Support - All major Application Servers (see Java Supported Environments)

Review Install App Server Agents for instructions and guidance. AppDynamics provides an Agent Installer that simplifies the agent installation process and streamlines the deployment of Java and Machine Agents.

Resource Utilization and Performance Impact

Within the Java Agent, the Cisco Secure Application capabilities require:

  • Disk - 4 MB (install) and <15 mb (daily usage)
  • Memory - consistently heap/mem usage should be 4-6 MB
  • CPU - consistently < 1% - spikes < 5%
  • Latency - consistently < 4-6 ms per transaction (average is lower) - spikes < 10ms
  • Classes Instrumented:  rules (12) classes (generally < 30 - based on implementations of some of the interface rules)

Browser Requirements

Currently, Google Chrome is the supported browser for accessing Cisco Secure Application dashboard.

Before You Begin 

To use Cisco Secure Application within the Java APM Agent, ensure:

  • That you have met the preceding Cisco Secure Application Requirements.
  • You have enough Cisco Secure Application licenses to cover your Java APM agent usage within the applications you plan on securing. To get a Cisco Secure Application license, contact the AppDynamics sales representative, or email salesops@appdynamics.com.
  • A Java APM Agent >= 21.3.0 is installed and licensed.
  • Controller >= 21.4.2.
  • That you have successfully configured the Java Agent in your application environment.
  • If you are using reverse proxy, ensure you configure properties to communicate from the APM Agent to the Controller. See Configure Properties to Use Reverse Proxy.

Configure Properties to Use Reverse Proxy

Cisco Secure Application automatically interprets the APM agent setting for an HTTP Proxy server and uses the same server for communication between the agent and Controller. However, you must configure these settings for the APM agent to communicate with Controller through a reverse proxy:

The reverse proxy configuration may change based on the reverse proxy solution that you use. Ensure that you use a pass-through reverse proxy to forward any requests containing /argento-agent/v1 or auth/v1/oauth to <tenant-name>.saas.appdynamics.com.

  1. In the JVM, configure the reverse proxy details for Cisco Secure Application:
    1. Specify the reverse proxy URL:

      -Dargento.management.server.reverse.proxy.url=http://<reverse-proxy-host>:<reverse-proxy-port>/
      CODE

      Here, reverse-proxy-host and reverse-proxy-port are the hostname and port of the reverse proxy that will direct communications to the Controller.

    2. Specify the domain:
      -Dargento.management.server.add.headers=Host:<tenant-name>.saas.appdynamics.com
      CODE

      Here, tenant-name is the tenant name of the Controller.

  2. In the JVM, configure these Cisco Secure Application system properties to use the reverse proxy:

    1. Dargento.management.server.authentication.access.key

      -Dargento.management.server.authentication.access.key=<access-key>
      CODE

      Here, access-key is the access key specific to the tenant.

    2. Dargento.management.server.authentication.user

      -Dargento.management.server.authentication.user=singularity-agent@<tenant-name>
      CODE

      Here, tenant-name is the tenant name of the Controller.