Tibco ActiveMatrix BusinessWorks Service Engine Settings

With Tibco ActiveMatrix BusinessWorks Service Engine, each application is started in its own JVM. As a result, for each application that you want to monitor, you must configure the Java Agent in the startup settings for the configuration file of that application.

The file to configure is usually the TRA file named for the application. For example:

<application_name>.tra

Instrument the Tibco Application

  1. Open the TRA file for the application you want to monitor and add this code to the file:
    java.extended.properties=-javaagent:/opt/appagent/javaagent.jar
    Splunk AppDynamics recommends that you include all -D system property arguments in one java.extended.properties line. Otherwise, the -javaagent property may be overwritten.
  2. Restart the application to have the changes take effect using the command-line tool bwengine.sh (or.exe) or the Tibco Admin UI.
Since Tibco traffic commonly takes the form of incoming SOAP actions sent through HTTP requests to a single URL (for example, /BusinessServices/WebGateway), it's likely that you will need to create a POJO split rule in the Splunk AppDynamics configuration to differentiate business transactions for Tibco. For information, see See "Split by POJO Method Call" on Split Servlet Transaction by Payload Examples.