📘

Attaching the OverOps Agent to a JVM Running Java 10 or 11

When attaching an OverOps Agent to a JVM that is running Java 10 or 11 or any IBM java versions, follow these guidelines:

1. Turn off Class Sharing: This can be done using the following flags:
   for IBM Java
   ‑Xshareclasses:none
   for HotSpot
   -Xshare:off -XX:-UseTypeSpeculation

2. Increase ReservedCodeCache to at least 512mb by adding the following flag
   -XX:ReservedCodeCacheSize=512m

3. The Agent should appear last in the VM arguments list before specifying the main class or jar.

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

After you install OverOps on your machine, you’ll need to connect it to your WebLogic server.
Choose the WebLogic launch configuration you’re using:

• Standalone WebLogic
• Clustered WebLogic Servers

Standalone WebLogic

Linux / macOS:

1. Edit the file startWebLogic.sh, located in <weblogic_<version#>_install_dir>/user_projects/domains/<domain_name>/bin/startWebLogic.sh.
2. Add the following argument to the application server start script:
   -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so

🚧

Important

This argument should appear at the beginning of the arguments list before including any other agents

3. Restart WebLogic.
4. Test your Installation.

Windows:

1. Open the startWebLogic.cmd file, located in <weblogic_version_install_dir>\user_projects\domains\<domain_name>\bin.
2. Add the following argument to the application server start script:
   -agentlib:TakipiAgent

# --- Start Functions ---

...

overopsAgent()
{
        echo "Adding OverOps Agent..."
        JAVA_OPTIONS="${JAVA_OPTIONS} -agentlib:TakipiAgent"
        export JAVA_OPTIONS
}

# --- End Functions ---

📘

Note

If you're attaching the OverOps Agent to a JVM that is running Java 10 or 11, you'll need to turn off Class Data Sharing using one of the following flags:
‑Xshareclasses:none → for J9
-Xshare:off → for HotSpot
-XX:-UseTypeSpeculation → Java 11 HotSpot
The relevant flag should be added to the same location in the WebLogic.cm file as the agentlib:TakipiAgent argument.

3. Next, add the OverOps Agent in the following way before starting WebLogic.
4. Restart WebLogic.

# Add OverOps Agent:
overopsAgent

# START WEBLOGIC

🚧

Important

This argument should appear at the beginning of the arguments list before including any other agents

5. Test your Installation.

Clustered WebLogic Servers

For clustered WebLogic servers, you'll need to start and stop using Node Manager, and configure server startup in the WebLogic Server Administration Console.

1. Open the WebLogic Server Administration Console.
2. Navigate to Environment > Servers and click your server in the Server List.
3. Click the Server Start tab.
4. Add the agentlib argument:
   -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so

🚧

Important

This argument should appear at the beginning of the arguments list before including any other agents

5. Restart your machine.
6. Test your Installation.