Java and Apache Agents configuration on Linux PPC-LE

AppMon 2018 April feature

Linux PPC-LE support available in AppMon 2018 April and on AppMon Agent platform only.

Supported Agent Technologies

  • Java
  • Apache Webserver

Required Port-Configuration

The Linux PPC-LE support is only available through the new AppMon Agent platform. This requires additional ports to be configured for the Agent->Collector as well as the Collector->Server communication. For more details see Required Port Configuration.

Download agent-binaries

Download the Java and Apache Agent for PPC64LE archive for your operating system. The archive contains only the boostrap Agent for Linux PPC-LE. Extract archive into your DT_HOME folder e.g. /opt/dynatrace/

Instrument WebSphere Application Server

The following steps are required to monitor applications on WebSphere running on AIX:

Start the WebSphere server via the WebSphere UI or the command line. For example:

/opt/ibm/WebSphere<version>/AppServer/bin/sh startServer.sh server1

Open the Administrative Console via the WebSphere UI or enter the URL in your web browser, such as http://localhost:9060/ibm/console.

When accessing the server remotely, specify the machine's hostname rather than localhost.

Enter your user ID and password and then log in.

Navigate to Server > Application servers > [yourprofilename] > Java and Process Management > Process Definition > Java Virtual Machine.

In the text field Generic JVM arguments, enter the following:

-agentpath:/opt/dynatrace/agent/bin/linux-ppcle-64/liboneagentloader.so=name=<agentname>,server=<communicationEndpoint>

Where <communicationEndpoint> is the endpoint of your Collector. For example, if you collector runs on IP 10.168.11.1 and port 8043, your communicationEndpoint is https://10.168.11.1:8043/communication, and the full agentpath looks like this:

-agentpath:/opt/dynatrace/agent/bin/linux-ppcle-64/liboneagentloader.so= name=myjavaagent,server=https://10.168.11.1:8043/communication

Apply the changes and save the configuration.

Restart the server.

The newly started WebSphere should show up in AppMon.

Instrument Java

The following steps are required to monitor generic Java applications running on Linux-PPC(LE):

Modify the command line of your Java application or modify the JAVA_OPTS environment variable, if applicable.

Add the following to the Java command line:

JAVA_OPTS -agentpath:/opt/dynatrace/agent/bin/linux-ppcle-64/liboneagentloader.so=name=<agentname>,server=<communicationEndpoint>

Where <communicationEndpoint> is the endpoint of your Collector. For example, if you collector runs on IP 10.168.11.1 and port 8043, your communicationEndpoint is https://10.168.11.1:8043/communication, and the full JAVA_OPTS looks like this:

JAVA_OPTS -agentpath:/opt/dynatrace/agent/bin/linux-ppcle-64/liboneagentloader.so=name=myjavaagent,server=https://10.168.11.1:8043/communication

Adapt the installation path as needed.

Restart your Java process.

The newly started Java process should show up in AppMon.

Instrumenting Apache HTTP Server

The following steps are required to configure AppMon to monitor Apache web service running on LinuxPPC(LE):

Edit your httpd.conf and add the following two lines at a location of your choice:

LoadModule agent_module /opt/dynatrace/agent//bin/linux-ppcle-64/liboneagentloader.so

OneAgentConfig name=<agentname>,server=<communicationEndpoint>

Where <communicationEndpoint> is the endpoint of your Collector. For example, if you collector runs on IP 10.168.11.1 and port 8043, your communicationEndpoint is https://10.168.11.1:8043/communication, and the full OneAgentConfig looks like this:

OneAgentConfig name=<agentname>,server=https://10.168.11.1:8043/communication

Alternatively, if you prefer to keep your httpd.conf untouched, you can specify the same directives using the command line:

apachectl \
-c "LoadModule agent_module /opt/dynatrace/agent/bin/linux-ppcle-64/liboneagentloader.so"\
-c "OneAgentConfig name=<agentname>,server=<communicationEndpoint>"\
-k start

Adapt the installation path and as needed.

Perform a full restart of Apache.

The newly started Apache process should show up in Dynatrace.