Documentation forWeb Performance Monitor

Configure Web Transaction Recorders on remote systems

After deploying a Web Transaction Recorder to a remote system, you can configure it to communicate with Orion server so recordings are immediately available for use in WPM. If you plan to use recordings as Transaction Checks in SolarWinds Pingdom, you can also connect a recorder to your Pingdom account.

Depending on your needs, you can also add client certificates to recorders, or set them up to support proxy servers.

To support Image Matching, keep Windows Display settings for "Scale and layout" on the remote system at the default value: 100%.

Sections in this topic include:

Connect a Web Transaction Recorder to the Orion server

To configure a recorder to communicate directly with the Orion server:

  1. Launch the Web Transaction Recorder from the Windows Start menu.
    1. Click Start.
    2. Type WPM.
    3. Click WPM Recorder.

      You can also open the recorder in File Explorer. Navigate to C:\Program Files (x86)\SolarWinds\Orion\SEUM\Recorder, and double-click TransactionRecorder.exe.

  2. Open the options menu and click Orion server configuration.

  3. Provide details about the Orion server and the Orion account to be used to create recordings.
    • IP or hostname
    • Username
    • Password
  4. (Optional) Select the "Remember my configuration" check box.
  5. Click Configure to save your settings.
  6. (Optional) Configure the recorder for Pingdom, as described next. You can also:

Connect a Web Transaction Recorder to your Pingdom account

Integration with Pingdom is not available in FIPS-enabled environments.

Starting in WPM 2020.2, you can create recordings that can be used as Transaction Checks in SolarWinds Pingdom, as detailed in the WPM Administrator Guide. To support this integration, connect the Web Transaction Recorder to your Pingdom account with a Pingdom API token that has Read-Write access, as described here.

Not using Pingdom yet? Click here to start your 14-day free trial.

  1. Log into your Pingdom account to generate an API token.
    1. Navigate to and click Pingdom.
    2. Enter your Pingdom credentials and click Login.
    3. Click Integrations > The Pingdom API.
    4. Click Add API token.
    5. Enter a name, select Read-Write access, and then click Generate token.
    6. When the token appears, click Copy to add the token to the Windows Clipboard.

      Pingdom doesn't store API tokens. Copy the token immediately, or store it in a secure location for later use.

  2. Launch the Web Transaction Recorder from the Windows Start menu.
    1. Click Start.
    2. Type WPM.
    3. Click WPM Recorder.
  3. Open the options menu and click Pingdom configuration.
  4. In the Pingdom API Token field, click Ctrl+V to paste the token into the field.
  5. Click Save.

    The link at the bottom of the window displays a green check mark.

Install client certificates

Unlike the Deprecated WPM Recorder, the Web Transaction Recorder does not save client certificates in recordings, so you'll need to install them on the remote system that hosts the recorder, and any remote systems where transactions created from the recording will be played back.

Install a client certificate into the personal certificate store for each SEUM-User account used by the WPM Player service to play transactions on remote systems. SolarWinds recommends installing certificates with a Group Policy Object (GPO), and then using domain accounts for playback. You can also install certificates individually, as described here.

To import certificates with the Microsoft Management Console (MMC):

  1. Download or copy the certificate file to the remote system that hosts the Web Transaction Recorder.
  2. In the MMC, use the Certificate Import Wizard to add the certificate to the Personal store.

For reference, see Distribute Certificates to Client Computers by Using Group Policy (© Microsoft Corp., available at, obtained on March 29, 2020)

Configure support for proxy server authentication

There are two ways to configure remote systems to support recordings in environments that use proxy servers:

  • Modify the configuration file for the Web Transaction Recorder, or
  • Force the proxy by adjusting the Internet Properties on the entire remote system.

To learn how proxies are handled in recordings and transactions, see the WPM Administrator Guide.

To add support for a proxy server by editing the Web Transaction Recorder configuration file:

  1. In File Explorer, navigate to the following default folder:
    C:\Program Files (x86)\SolarWinds\Orion\SEUM\Recorder
  2. Run a text editor as an Administrator and open WPM Recorder.exe.config
  3. Scroll down to the proxyUrl section and add the proxy server address (for example,
  4. Save changes to the config file.
  5. Restart the Web Transaction Recorder to apply changes.

To support proxy server authentication by updating a remote system's Internet Properties:

  1. Open the Internet Properties tool from the Windows Start menu.
    1. Click Start.
    2. Type Internet Prop.
    3. Click Internet Properties.

      These changes will impact how remote systems communicate via network for all processes, including the WPM Player service.

  2. Switch to the Connections tab and click LAN settings.
  3. In the Local Area Network (LAN) Settings dialog box:
    1. Select the "Use a proxy server for your LAN" option.
    2. Enter the Address and Port for the proxy server.
    3. (Required) Enable the "Bypass proxy server for local addresses" option so WPM can communicate with probes, and then click OK.
  4. Click OK again to close the Internet Properties tool.
  5. Restart the remote system to apply the new settings.

Remove the Orion server or Pingdom configuration from a Web Transaction Recorder

Links at the bottom of the Web Transaction Recorder indicate if it's currently configured for the Orion server or Pingdom, as shown here:

To remove the Orion server or Pingdom configuration:

  • Click the related link at the bottom of the recorder.
  • In the Configure Pingdom (shown here) or Configure Orion dialog box, click Remove configuration.