Configuring Web Transactions monitoring
This topic provides information about configuring BMC PATROL for Web Transaction KM in the Central Monitoring Administration and TrueSight console. To configure the KM, set the following preferences on the Add Monitoring Configuration dialog.
Monitoring Solution | Version | Monitor Profile | Monitor Type |
|---|---|---|---|
Web Transaction | 9.0.30 | Web Transaction | Web transaction |
Click 
button to add the web transaction for monitoring.
Field | Description |
|---|---|
Instance Name | Enter a valid instance name. If the instance name contains a space, it is not considered. Example: If "bmc software" is the instance name, it would be considered as "bmcsoftware". |
Web transaction file name | Enter a valid web transaction file name, the name of the file you capture using the web recorder utility. The file is saved on the server where the PATROL Agent is running, at %PATROL_HOME%\WTX\Shared\usr_apps\webtranx\<Web transaction file name>.tran |
Poll interval (sec) | Specify the time interval between two consecutive statistical data polls, in seconds. Default value is 60 seconds. |
Timeout (sec) | Specify the time-out period for each poll of statistical data, in seconds. Default value is 30 seconds. |
Download full page | Select this check box to download all the contents on the page (including images and other linked components). By default, only text data is downloaded. |
Enable monitoring | Select/clear this check box to enable/disable monitoring for the configured instance. By default, monitoring is enabled (check box is selected). |
Proxy | The details of the proxy server used to connect to the host. |
Host | Specify the name/IP address of the computer hosting the proxy server. |
Port | Specify the port on which the proxy server is configured to listen for connections. |
Username | Specify the user name used to access the proxy server. |
Password | Specify the password corresponding to the user name. |
OK | Click to save the configuration. |
Cancel | Click to close the configuration window. |
After you add the Web Transaction, enter the details in the Client Certificate Database Details and Administration section:
Field | Description |
|---|---|
Client Certificate Database Details | |
The KM supports monitoring of URLs that require Client Certificates by importing the Java key store database file (known as the .jks file) into the KM. When you configure the URLs to be monitored that require a client certificate, those client certificates should be already imported into the .jks file so it can be used while communicating with the URLs. An authorization error will occur if the required certificates are not found in the .jks database file. | |
.jks file path | Enter the path (along with the file name and .jks extension) where the Java key store database file is located. The Java key store database file must be accessible from the host where the PATROL Agent is running. BMC PATROL default account must have read permission on the directory where the .jks file is located. |
KeyStore password | Enter a password for the Java keystore database file. This password is used by the KM to open the java keystore database (aka .jks file). |
Administration | |
Root application display name | Specify the display name of the root application. By default, the name is Web Transaction. |
Enable device mapping | Select/clear this check box to enable/disable device mapping. Enabling device mapping consolidates Web Transaction monitoring at device level. By default, device mapping is enabled (check box is selected). |
Enable debug | Select/clear this check box to enable/disable debugging. The logs are located at %PATROL_HOME%\WTX\logs By default, debugging is disabled (check box is cleared). |
JAVA_HOME | Enter the complete path of the Java home directory if you are not using the JRE that is installed with the PATROL Agent. Example:
|
OK | Click to save the configuration. |
Cancel | Click to close the configuration window. |