Install OneAgent on Solaris

Latest Dynatrace
7-min read

This page describes how to download and install Dynatrace OneAgent on Solaris.

To get started, log in to your Dynatrace SaaS environment at Dynatrace.com using the credentials provided during signup. Then follow the installation steps below.

Requirements

Permissions

You need administrator rights for the servers where OneAgent will be installed as well as for changing firewall settings (necessary only if your internal routing policy may prevent Dynatrace software from reaching the Internet).
You need an API token with permissions to download and install OneAgent.
You need permissions and credentials for restarting all your application services.

Resources

All hosts that are to be monitored need to be able to send data to Dynatrace. Depending on your Dynatrace deployment and on your network layout and security settings, you may choose to either provide direct access out to Dynatrace or to set up an ActiveGate.

Limitations

OneAgent installation isn't supported on networked storage mount points that are managed by standards such as NFS or iSCSI.
Infrastructure and Discovery monitoring modes aren't supported on Solaris hosts.

Allow connections through firewall

Ensure that your firewall settings allow communication to Dynatrace.
Depending on your firewall policy, you may need to explicitly allow certain outgoing connections. The remote Dynatrace addresses to add to the allow list are given on the installation page for OneAgent.

Installation

Generate an access token with the Download OneAgent and ActiveGate installers (InstallerDownload) scope. This token is required to authenticate your API request when downloading the OneAgent installer.
Identify the CPU architecture of your target Solaris host. Use x86 for x86 systems or sparc for SPARC systems. You'll pass this as the arch parameter in the download URL.
Log into your Solaris host and download the installer via the Dynatrace Deployment API using the wget command.

Replace {your-environment-id} with your Dynatrace environment ID, x86 with your target architecture, and <access-token> with the token generated in the previous step.

The wget command isn't installed on Solaris by default. Either install it or use an alternative means of downloading OneAgent.
```
wget -O Dynatrace-OneAgent-Solaris.zip "https://{your-environment-id}.live.dynatrace.com/api/v1/deployment/installer/agent/solaris/paas/latest?arch=x86" --header="Authorization: Api-Token <access-token>"
```
Create a folder on your local system for OneAgent (for example, /opt/dynatrace/oneagent) and unzip the ZIP archive into the folder.
Root access isn't required for installation of OneAgent on Solaris. OneAgent can be installed in any directory.
All monitored applications must be able to read the OneAgent library. Set the following permissions:
Give global read permissions to /opt/dynatrace/oneagent
Give global write permissions to /opt/dynatrace/oneagent/logs

Be sure to reference the folder correctly in the subsequent steps of your deployment.
Dynatrace supports only Java and Apache HTTP Server applications on Solaris. Choose whether to monitor a single application or configure monitoring shell-wide, then follow the relevant instructions below.
Monitor a single application
To monitor a single application, execute your command and prepend it with the following commands.
```
DT_HOME=/opt/dynatrace/oneagent
export DT_HOME
LD_PRELOAD_64=$DT_HOME/agent/lib64/liboneagentproc.so
export LD_PRELOAD_64
LD_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so
export LD_PRELOAD
```
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.
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.
1. Start the WebSphere server via the WebSphere UI or the command line. For example: /opt/ibm/WebSphere<version>/AppServer/bin/sh startServer.sh server1
2. 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.
3. Enter your user ID and password and then log in.
4. Navigate to Server > Application servers > [yourprofilename]> Java and Process Management > Process Definition > Environment Entries > New.
5. Add 3 entries to the list.
  
  DT_HOME=/opt/dynatrace/oneagent
  LD_PRELOAD_64=/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so
  LD_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.
6. Apply the changes and save the configuration.
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
DT_HOME=/opt/dynatrace/oneagent
export DT_HOME
LD_PRELOAD_64=$DT_HOME/agent/lib64/liboneagentproc.so
export LD_PRELOAD_64
LD_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so
export LD_PRELOAD

# 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.
Monitor every Java and Apache HTTP service in your execution context
You can set up OneAgent to monitor every application in your current application context. To do this, add the following lines to the startup script of the application you want to monitor. Ensure that they're executed prior to the application itself. You should not do this system-wide or for login users.
OneAgent version 1.141+
```
DT_HOME=/opt/dynatrace/oneagent
export DT_HOME
LD_PRELOAD_64=$DT_HOME/agent/lib64/liboneagentproc.so
export LD_PRELOAD_64
LD_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so
export LD_PRELOAD
```
LD_PRELOAD will not carry over into sudo or su calls. Moreover, calling sudo in an execution context that has LD_PRELOAD set will lead to an error message that the library is in a non-secure location. This has no negative impact. This message can be ignored.

If you use the WebLogic admin server to restart managed nodes on Solaris, see Troubleshoot OneAgent installation on Solaris to learn how to modify the startup script.

Fallback method

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

Manual OneAgent injection

Modify the command line of your Java application:

DT_HOME=/opt/dynatrace/oneagent
. $DT_HOME/dynatrace-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.

You've arrived!

Great, the setup is complete! You can now take a look around your new monitoring environment.

You can access your monitoring environment anytime by going to Dynatrace website and selecting Login in the upper-right corner.

One last thing: to monitor your processes, you need to restart them. You can restart your processes at any time, even during your organization's next planned maintenance period. For details, see Infrastructure & Operations and Processes.