Installing eG BTM on a Multi-Server SAP Web Application Server Instance

In a multi-server environment, two/more Java server processes run within a single SAP WAS instance. For the eG agent to monitor business transactions to a multi-server SAP WAS instance, you need to BTM-enable each server Java process in that instance, separately.

To achieve this, follow the steps detailed below.

  1. First, login to the SAP WAS instance to be BTM-enabled.
  2. Open a browser on that instance and connect to the eG management console.
  3. Login to the eG admin interface.
  4. Follow the Agents -> BTM Profiler Download menu sequence in the eG admin interface.
  5. Figure 1 will appear listing the servers that can be instrumented for APM by eG. In this list, locate the SAP Web Application server instance that you want to BTM-enable. Once you locate the server instance, click the Download icon corresponding to that instance to download the APM Profiler Agent to that instance.

    Figure 1 : Download the APM Profiler Agent to the SAP WAS instance

  6. A zip file named javaagent_<Nick_name_of_SAPWAS_instance>_<Port_number_of_SAPWAS_instance will get downloaded. For instance, if you have managed the SAP WAS instance using the nickname 'sapwas' and the port number '50000', then the name of the zip file will be javaagent_sapwas_50000. Extract the contents of this file to any location on the SAP WAS instance.
  7. Next, navigate to the cluster folder of the SAP WAS instance. Within this folder, you will find Java server process-specific sub-folders. Create a folder named btm under each of these sub-folders.
  8. Figure 2 : Navigating to the cluster folder in the <SAP_WAS_INSTANCE_INSTALL_DIR>

  9. Copy the contents of the javaagent_sapwas_50000 zip to the btm folder of each of the Java server process-specific folders (indicated by Figure 2).

  10. Next, follow the steps below for each Java server process:

    • Edit the btmOther.props file in the btm folder of the Java server process.

      Figure 3 : Configuring the BTM port for a server process

    • In the btmOther.props file, search for the BTM_Port parameter. Once found, specify a unique BTM port for the Java server process.

      Typically, each Java server process in a multi-server SAP WAS instance is assigned a node index - eg., the node index for server0 is 0, for server1 is 1, for server2 is 2, and so on. When configuring a BTM port for a Java server process, its recommended that the node index of that server process be set as the last digit of the BTM port number. For instance, the BTM port for server0 can be 13930, server1 can be 13931, server2 can be 13932 and so on.

    • Finally, save the file.
    • Repeat this procedure for every server process in the SAP WAS instance.

  11. Next, connect to the SAP Netweaver administrator tool by providing the URL: http://<IP_address_of_tool>:<Port_number_of_tool>/nwa/sysinfo

    Figure 4 : The login page of the SAP Netweaver administrator tool

  12. A login screen then appears (see Figure 4). Login to the system information application using administrator or j2ee_admin credentials. Upon successful login, Figure 5 will appear.

    Figure 5 : Clicking the VM Additional Parameters link

  13. Select the instance to be BTM-enabled from the list of Instances in Figure 5. Then, click the VM Additional Parameters link indicated by Figure 5. This will open the Additional VM Parameters tab page (see Figure 6). Click the Add button in that tab page to add a new VM parameter.

    Figure 6 : Clicking the Add button in the Additional VM Parameters tab page

  14. Figure 7 will then appear.

    Figure 7 : Adding a new VM parameter

  15. Specify the following in the Name text box in Figure 7:


    Here, you can specify the full path to the eg_btm.jar file that is in the btm folder of any of the Java server processes in the target instance.

  16. Then, in the Value text box, specify the following:


    The path to these files will be different for each Java server process in the instance. Hence, when referring to the server process-specific sub-folder that contains these files, your path specification should include the ${NODE_INDEX} variable. This variable represents the node index of a Java server process - eg., the node index of server process server0 is 0, for server1 it is 1, and so on. SAP WAS will automatically substitute this variable with the node index of the corresponding server process, at runtime. A sample specification is provided below:


  17. Finally, click the Add button in Figure 7 to add the new VM parameter.
  18. When Figure 7 appears, click the Save button to save the changes. A Confirmation message box (see Figure 8) will appear prompting you to confirm whether you want to restart the server now or later. Click Later in the message box and then click the Back button indicated by Figure 8.

    Figure 8 : Saving the changes

  19. Restart the Java server processes that have been BTM-enabled.