📘

Naming Your Application and Deployment

Naming your applications and deployment allows us to aggregate your data and to sort, view, and compare them from version over version. The data then feeds into our dashboards (without using a naming convention your data loses value):

• Give the application a name you'll be able to easily track
• Give your deployment a distinct name so that whenever you deploy new code to your application, you'll be able to distinguish between different deployments that will show up in the OverOps Dashboard

Use the following arguments:
-Dtakipi.application.name=<APPLICATION_NAME>
-Dtakipi.deployment.name=<DEPLOYMENT_NAME>

To learn more, see Naming the Application, Server, Deployment.

📘

If you are attaching OverOps Agent to a JVM that is running Java 10 or 11, please follow these guidelines:

1. In IBM Java, Class Data Sharing should be turned off using the following flags:
   ‑Xshareclasses:none -XX:ReservedCodeCacheSize=512m
2. The Agent should appear last in the VM arguments list before specifying the main class or jar.
3. When adding/removing 3rd party packages, the Agent should be restarted.

Additionally, if you wish to upgrade your own compiler to target Java 10/11, then you'll have to upgrade your Collector (SaaS) or Collector + backend (On-Premises) to support it.

❗️

Rootless Agent Installation Method (Linux only)

When Using the Rootless Agent Installation Method replace the
-agentlib:TakipiAgent JVM startup Argument
with
-agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so JVM startup Argument

WebSphere 7.x and 8.x

1. In the admin console of each WebSphere node, go to Servers > Server Types > WebSphere application servers.
2. For each Server Infrastructure, go to Java and Process Management > Process Definition.
3. Under the Additional Properties section, click Java Virtual Machine.
4. In the Generic JVM arguments field, enter the OverOps Agent argument:
   -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
5. Click OK.
6. Restart the application.
7. Test your Installation.

WebSphere 6.x

1. In the WebSphere admin console, go to Servers > Application servers.
2. For each server, in the Configuration tab, click Java and Process Management.
3. In the Generic JVM arguments field, enter the OverOps Agent argument
   -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
4. Click OK.
5. Restart the application.
6. Test your Installation.

WebSphere 5.x

1. In the WebSphere admin console, click Servers > Application Servers.
2. For each Server, under Additional Properties, click Process Definition > Java Virtual Machine.
3. Add the OverOps Agent argument:
   -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
4. Click OK.
5. Restart the application.
6. Test your Installation.