Enabling ARM on a server separate to the Transaction Collector

To enable ARM on an IBM HTTP Server with a WebSphere plugin installed, and which is separate to the Transaction Collector, additional steps are required.

Tip: You can also use the following steps to enable other ARM applications.

To enable ARM data to be sent to a remote Transaction Collector, complete the following steps:

Install WASTT. Ensure that you install the correct package to match the web server, either 32-bit or 64-bit. As an example for this procedure, WASTT_INSTALL_PATH=/opt/IBM/ITM/aix713/tj/wastt
In the environment variables file, HTTP_HOME/bin/envvars, set the WASTT installation that contains the libarm4 library:
- On Linux or Solaris systems, set LD_LIBRARY_PATH:
```
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:WASTT_INSTALL_PATH export LD_LIBRARY_PATH
```
- On AIX systems, set the above commands for LIBPATH instead of LD_LIBRARY_PATH.
- On Windows systems, append WASTT_INSTALL_PATH to the PATH environment variable. See Native ARM libraries for further information.
Set the CANDLE_HOME environment variable in HTTP_HOME/bin/envvars:
- On Linux or Solaris systems, set CANDLE_HOME=ITM_HOME export CANDLE_HOME
  For example, CANDLE_HOME=/opt/IBM/ITM
- On Windows systems, set CANDLE_HOME in the Windows environment variable.

Create ITM_HOME/tmaitm6/arm/armconfig.xml using the following configuration, or copy it from the computer on which the Transaction Collector is installed:

<configuration>
<performancelogging>-1</performancelogging>
<resetperfonlog>false</resetperfonlog>
<traceenabled>true</traceenabled>
<filebuffersize>32767</filebuffersize>
<queuesize>2048</queuesize>
<perfdetaillevel>0</perfdetaillevel>
<ttconnectionstring>tcp:127.0.0.1:5455</ttconnectionstring>
</configuration>

Note: Ensure you add the location of the remote Transaction Collector to the ttconnectionstring parameter. See Configuration files for further information.

Modify plugin-cfg.xml. Set the following variable:
```
RequestMetrics armEnabled="true" 
```