Enable Socket Collection on the App Agent
- Configure the Java App Agent startup command to perform these tasks, as shown in the example: Enable
for the Network Agent to map network metrics to application flows. For example:appdynamics.socket.collection.bci.enable
java -javaagent:<
>app_server_agent_home
/javaagent.jar
\
-
Dappdynamics.socket.collection.bci.enable=true
The following examples illustrate how editing the Agent startup command can differ, depending on the framework of the monitored application. See and its relevant framework documentation.Framework Example (App Agent ZIP) IBM WebSphere and InfoSphere In the WebSphere/InfoSphere UI, navigate to the Java Virtual Machine properties page for the monitored server. Then, add
javaagent
andappdynamics.socket.collection.bci.enable=true
as a Generic JVM argument. For example:javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true
Apache Tomcat Add the full command as a Catalina environment variable in file
CATALINA_BASE/bin/setenv.sh
(Tomcat 6 and later). For example:export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true"
Glassfish Add the full command as a
-javaagent
JVM option in the GlassFish domain. You can add the Agent using the asadmin tool. For example:export LD_PRELOAD=/usr/appd/agents/netviz/lib/appd-netlib.so
glassfish4\bin\asadmin create-jvm-options "-
javaagent\:/usr/appd/agents/apm/javaagent.jar:-Dappdynamics.socket.collection.bci.enable=true"
JBoss Standalone Add the full command to the
standalone.sh
file. For example:export JAVA_OPTS="$JAVA_OPTS -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true"
Jetty Add the full command to the
start.ini
config file in the Jetty base directory. For example:--exec -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true
- To verify that the App Agent is running correctly, enter:
strings /proc/<app_pid>/environ