Connect to WebLogic

After you install OverOps on your machine, you’ll need to connect it to your WebLogic server.

Please choose the WebLogic launch configuration you’re using:

Standalone WebLogic

Clustered WebLogic Servers

 

Standalone WebLogic

Linux / macOS:
  • Edit startWebLogic.sh located at <weblogic_<version#>_install_dir>/user_projects/domains/<domain_name>/bin/startWebLogic.sh.
  • Add the following to the beginning of your application server start script -agentlib:TakipiAgent
  • Restart WebLogic.
  • Test the installation – head back to app.overops.com and click .

    If the connecting process was successful, you will get a “Monitoring” message next to your JVM.

  • Throw an exception, or make sure your application throws exceptions.
Windows:
  • Open the startWebLogic.cmd file, located at <weblogic_version_install_dir>\user_projects\domains\<domain_name>\bin.
  • Add Add following argument to the application server start script - agentlib:TakipiAgent
  • Restart WebLogic.
  • Test the installation – head back to app.overops.com, and click .


    If the installation was successful, a “OverOps is active” message will be displayed, and a green “Monitoring” message will appear next to your JVM(s).

  • Throw an exception, or make sure your application throws exceptions.

 

Clustered WebLogic Servers

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

  • Open the WebLogic Server Administration Console.
  • Navigate to Environment > Servers and click your server in the Server List.
  • Click the Server Start tab.
  • Add the agentlib argument:
    -agentlib:TakipiAgent
  • Restart your machine.
  • Test the installation – head back to app.overops.com and click .

    If the connecting process was successful, you will get a “Monitoring” message next to your JVM.
  • Throw an exception, or make sure your application throws exceptions.
Have more questions? Submit a request