Installing the Sun Java System Web Server BTM extension


This topic describes how to install the Sun Java System Web Server BTM Extension on Windows and UNIX.

Before you begin

  • If you do not have an instance of the web server to use, create a new instance using the Sun Java System Web Server administrative server, which is typically run on port 8888.
  • Deploy the runtime toolkit. See Working-with-the-runtime-toolkit for details.
  • Install the Microsoft Visual C++ 2017 Redistributable Package by installing vcredist_x86.exe located in the agent distribution directory. This extension is 32-bit and even if your Windows operating system is 64-bit you need to install the 32-bit runtime libraries. You might have already done this for other BTM extension types. It only needs to be done once but make sure the correct version (32-bit or 64-bit) is installed.

Note

Sun Java System Web Server fails to load the library. If you see an event in the Windows Event Viewer System log with a source of SideBySide when you start the Sun Java System Web Server or the first http request is received by the Sun Java System Web Server make sure you have installed the Microsoft Visual C++ 2017 Redistributable Package as outlined in the installation steps.

Related topics

Running-application-transaction-tracing-transaction-monitoring-extensions

Running-the-Sun-Java-System-Web-Server-BTM-extension

Uninstalling-TMTM-transaction-monitoring-extensions

To install the Java Web Server BTM extension

This procedure requires you to open the files magnus.conf and obj.conf. Locate these files (possible locations are indicated):

  • Windows: C:\sun\WebServer6.1\https-servername\config
  • UNIX: /opt/SUNWwbsvr/https-servername/config

  1. Open magnus.conf in the Sun Java System Web Server installation in a text editor and add the following anywhere in the file:

    • Windows: Init fn="load-modules" shlib="c:/path/to/btmsunwbsvr.dll" btmGroup="servername" MQS_HOME="/path/to/QPLog.ini"
    • UNIX: Init fn="load-modules" shlib="/path/to/btmsunwbsvr.so" btmGroup="servername" MQS_HOME="/path/to/QPLog.ini"

    where:

    btmGroup     is the name of the server instance you are monitoring. If you have more than one web server running on a given server, each must have a unique value. If you want to have more than one activity implementation for the same web server, each activity implementation would have the same value. In such a case, we suggest using the web server's port.

    The btmGroup matches the Group values specified on the activity implementation dialog box. The deprecated name QnamiName can be specified but make sure you use the deprecated filter names when doing so. Support for the deprecated names might be removed in a future release; change existing installations to the non-deprecated values as soon as possible.

    The MQS_HOME portion is optional in both cases. The MQS_HOME system environment variable must be defined as the directory containing QPLog.ini. Do not include the QPLog.ini file name in that path. Save the file.

  2. Open obj.conf in the Sun Java System Web Server installation in a text editor and add the following to the default object section:

    Windows and UNIX:

    Input fn=insert-filter filter="btm-input"
    Output fn=insert-filter filter="btm-output"

    The name of the input filter is btm-request. The deprecated name qnami-request must be used when QnamiName is specified in magnus.conf. The name of the output filter is btm-response. The deprecated name qnami-response must be used when QnamiName is specified in magnus.conf.
  3. Repeat Steps 1 and 2 for magnus.conf and obj.conf for all existing server instances.
  4. Restart the Sun Java System Web Server for the changes to take effect. Output is generated and appears in the web server's error logs. Use the administrative server to view the output.

Where to go from here

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*