Install OneAgent on AIX

To install DESK OneAgent on AIX

If you have a DESK SaaS deployment, go to dexp.ae and Login using the username and password you received from DESK in your signup confirmation email.
If you have a DESK Managed deployment, access the Cluster Management Console and choose the environment you want to monitor.

Then continue with the installation steps provided below.

Requirements

You need administrator rights for the servers where DESK OneAgent will be installed as well as for changing firewall settings (necessary only if your internal routing policy may prevent DESK software from reaching the Internet).
You need permissions and credentials for restarting all your application services.
You need to check also the disk space requirements.
The host on which you install OneAgent needs at least 300 MB RAM.
OneAgent installation isn't supported on networked storage mount points that are managed by standards such as NFS or iSCSI.
All hosts that are to be monitored need to be able to send data to the DESK cluster. Depending on whether your DESK deployment is SaaS or Managed, and on your network layout and security settings, you may choose to either provide direct access to the DESK cluster, or to set up an ActiveGate.

Installation

Select Deploy DESK from the navigation menu.

Select Start installation and then select AIX.

Click Copy to copy the wget command to the clipboard.

Log into your AIX host and then paste and execute the wget command.

Important

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 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.

After 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.

Copy the command provided in the And run the installer with root rights text field.

Paste the command into your terminal and execute it.

You 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 DESK-OneAgent-AIX-1.0.0.sh
If your environment is segmented (for example, into development and production), consider organizing your hosts into host groups.

For a summary of the changes made in your system by OneAgent installation, see System changes on AIX.

On AIX, DESK supports deep monitoring for Java, Apache HTTP Server, and IBM Integration Bus 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/desk/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 OneAgent installation folder. You can omit either the 32-bit or 64-bit entry, depending on your environment.

Note:
If you are upgrading OneAgent from a version earlier than v1.141, be sure to change the paths for Java and Apache instrumentation to point to the files mentioned above. Only those files are automatically updated during 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.

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/desk/oneagent
LDR_PRELOAD64=/opt/desk/oneagent/agent/lib64/liboneagentproc.so
LDR_PRELOAD=/opt/desk/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 WebSphere server.

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 DESK OneAgent
export DT_HOME=/opt/desk/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.

Monitoring every Java and Apache HTTP service in your execution context

To monitor every application in your current application context, add the following lines to the startup script of the application you want to monitor. Make sure these lines are executed prior to the application itself. You should not do this system-wide or for login users.

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

Manual OneAgent injection

If you have problems with the unified monitoring approach, you can inject OneAgent manually.

Manual OneAgent injection

IBM Java 1.6 – 1.8 IBM/Apache HTTP Server

Modify the command line of your Java application:

DT_HOME=/opt/desk/oneagent
. $DT_HOME/desk-java-env.sh 64
java $JAVA_OPTS <MainClass>

Make sure that you include the $JAVA_OPTS variable in your command. For 32-bit Java processes, omit the 64 parameter.

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

LoadModule oneagent_module /opt/desk/oneagent/agent/bin/aix-ppc-64/liboneagentloader.so
OneAgentConfig tenant=<tenant-id>,tenantToken=<tenant-token>,server=https://<server-url>/communication

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

apachectl -c "LoadModule oneagent_module /opt/desk/oneagent/agent/bin/aix-ppc-64/liboneagentloader.so"
        -c "OneAgentConfig tenant=<tenantUUID>,tenantToken=<tenant-token>,server=<communicationEndpoints>"
        -k start

tenantUUID is the environment ID of your DESK environment that should be pulled from desk-env.sh (located in the OneAgent installation root directory). The tenantUUID parameter is represented in the script as DT_TENANT.
tenantToken is the token that OneAgent uses to connect to DESK Server. It should be pulled from desk-env.sh (or ruxitagent.conf, depending on your OneAgent version), which is located in the OneAgent installation root directory. The tenantToken parameter is represented in the script as DT_TENANTTOKEN.
Attention: This token should not be confused with DESK API or PaaS tokens. Those tokens can't be used here.
communicationEndpoints corresponds to one or multiple HTTP addresses that represent DESK Servers or ActiveGates. The communicationEndpoints parameter is represented in the script as DT_CONNECTION_POINT. For example, the desk-env.sh (located in the OneAgent installation root directory) may contain the following:
```
export DT_CONNECTION_POINT="https://x1.live.desk.com/communication;https://x2.live.desk.com/communication;https://x3.live.desk.com/communication"
```
In this case, the parameter would be
```
server=https://x1.live.desk.com/communication;https://x2.live.desk.com/communication;https://x3.live.desk.com/communication
```

You've arrived!

Great, setup is complete! You can now take a look around your new monitoring environment. If you are a SaaS customer, you can access your monitoring environment anytime by going to DESK website and clicking the Login button in the upper-right corner. If you are a Managed customer, you can access your monitoring environment through the Cluster Management Console.

home dashboard

One last thing: to monitor your processes, you need to restart them. At any time, you can check which processes aren't monitored and need to be restarted. Just select Deployment status from the navigation menu, click the All hosts or Recently connected hosts tab, and expand the host you are interested in.