How do I install Dynatrace OneAgent on AIX?

Follow the steps below to download and install Dynatrace OneAgent on AIX:

Click Copy to copy the wget command.

Log into your AIX host and execute the wget command.

Attention:

  • The wget command isn't installed on AIX by default. Either install it or use an alternative means of downloading OneAgent.
  • If you receive an error while downloading OneAgent, install the required certificate by downloading the root CA file from Comodo and then concatenating the content of the CRT file to /var/ssl/cert.pem. You can alternatively skip the certificate check by adding the parameter --no-check-certificate.
  • If you plan to download Dynatrace OneAgent directly to a server, note that outdated or missing libraries (for example, CA certificates or OpenSSL) will prevent the installer from downloading. We use encrypted connections. OpenSSL is required to enable wget to access the server.

Once the download is complete, you can verify the signature by copying the command from the Verify signature text field, then pasting the command into your terminal window and executing it. Make sure your system is up to date, especially SSL and related certificate libraries.

Installation on AIX depends on the OneAgent version.

  • Copy the command that's provided in the And run the installer with root rights text field.

  • Paste the command into your terminal and execute it. Note that you’ll need root privileges. You'll need to make the script executable before you can run it as root. You can use su or sudo to run the installation script. To do this, type the following command into the directory where you downloaded the installation script.
    sudo /bin/sh Dynatrace-OneAgent-AIX-1.0.0.sh

On AIX, Dynatrace supports deep monitoring for Java and Apache HTTP Server applications. This however requires some more configuration on AIX, which can be easily done both for single applications as well as shell-wide.

Monitoring a single application

To monitor a single application, execute your command and prepend it with the following commands.

export DT_HOME=/opt/dynatrace/oneagent
export LDR_PRELOAD64=$DT_HOME/agent/lib64/liboneagentproc.so
export LDR_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so

The DT_HOME variable points to your Dynatrace OneAgent installation folder. You can omit either the 32-bit or 64-bit entry, depending on your environment.

Note:
If you are upgrading Dynatrace OneAgent from version prior to v1.141, make sure to change the paths for Java and Apache instrumentation to point to the files mentioned above. Only those files will be automatically updated during the consecutive OneAgent upgrades.

Configure WebSphere Application Server via the Administrative console

The unified approach works just as well for WebSphere, however you may want to configure your WebSphere via the Administrative console. This works for OneAgent v1.141 and above.

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. For example: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 > Environment Entries > New.

Add 3 entries to the list.

DT_HOME=/opt/dynatrace/oneagent
LDR_PRELOAD64=/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so
LDR_PRELOAD=/opt/dynatrace/oneagent/agent/lib/liboneagentproc.so

You can omit either the 32-bit or 64-bit entry, depending on your environment. The DT_HOME variable must point to your OneAgent installation folder.

Apply the changes and save the configuration.

Restart the server. The newly started WebSphere server should show up in Dynatrace.

Configure Oracle WebLogic via the startup script

To monitor Oracle WebLogic you need to add the following lines to the WebLogic startup script (startWebLogic.sh)

# Monitor WebLogic with Dynatrace OneAgent
export DT_HOME=/opt/dynatrace/oneagent
export LDR_PRELOAD64=$DT_HOME/agent/lib64/liboneagentproc.so
export LDR_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so

# WebLogic checks and startup, this is part of your script, add the 3 lines prior to this.
echo "starting weblogic with Java version:"

${JAVA_HOME}/bin/java ${JAVA_VM} -version

if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
   echo "Starting WLS with line:"
echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
         -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}"

   ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
         -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}

else
   echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"

   ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
         -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS}
         ${SERVER_CLASS} 2>&1 >"${WLS_REDIRECT_LOG}"

fi

You can omit either the 32-bit or 64-bit entry, depending on your environment. The DT_HOME variable must point to your OneAgent installation folder. Restart the server. The newly started WebLogic server should show up in Dynatrace.

Monitoring every Java and Apache HTTP service in your execution context

You can set up monitoring of every application in your current application context. To do this, add the following lines to the startup script of your script or shell. Ensure that they are executed prior the application you want to monitor. You should not do this system-wide or for login users.

export DT_HOME=/opt/dynatrace/oneagent
export LDR_PRELOAD64=$DT_HOME/agent/lib64/liboneagentproc.so
export LDR_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so

Customize installation

AIX installer can be used with command line parameters when you can't use the default settings. Note that all parameters are optional.

Troubleshooting

OneAgent versions earlier than v1.137 and fallback

If your OneAgent is older than v1.137, or if you have problems with the unified monitoring approach, you can inject OneAgent manually.

Continue with finalization of OneAgent installation on AIX.