Documentation forWeb Performance Monitor

Configure WPM Players

After deploying WPM Players to remote systems in your environment, decide how you want them to communicate with the Orion server, and if you want them to be updated automatically when new versions of the WPM Player service are available. As described in How WPM works, the WPM Player is a actually a Windows service that simulates end user experiences with web applications by playing back recorded transactions.

Note the following details about setting up WPM Players on remote systems:

  • Additional configuration may be required, depending on the transactions involved. When a WPM Player runs recorded transactions, it uses a separate WPM Worker process to perform each step, and each WPM Worker process requires its own SEUM-User account with the necessary permissions. After you create transactions and decide where to run them, you can adjust SEUM-User accounts so a WPM Player has adequate permissions to run transactions.
  • If a computer hosts a hypervisor or Virtual Machine Monitor (VMM) running various servers (for example, print or file servers), consider hosting the WPM Player on another server instead.

To configure a WPM Player:

  1. Log into the system that hosts the WPM Player.
  2. Open the WPM Player Settings tool from the Start menu.
  3. In the WPM Player Settings tool, select a communication method and provide values, as prompted.
    • Server-initiated communication sets a player in passive mode to wait for requests from the Orion server on port 17781. If you select this option, configure firewall and Network Address Translation (NAT) settings on each system that hosts a WPM Player so agents can communicate with the Orion server.
    • Player-initiated communication allows a player to actively initiate communicate with the Orion server on port 17782. With this setting, active agents on remote systems can navigate the Firewall/NAT configuration and connect to polling servers using a HTTP(S) protocol. Managed Service Providers (MSPs) and larger distributed deployments may prefer this option.
  4. (Optional) Clear the "Enable automatic update" check box if you want WPM to prompt you before installing new versions of the WPM Player when they are available.
  5. Click Save.
  6. (Optional) Configure support for proxy server authentication, as described next.
  7. (Optional) Enable FIPS by adjusting Windows OS settings.
  8. (Recommended) Exclude file paths and volumes from antivirus software scans.

If you change WPM Player settings later, be sure to update the Orion server with the latest information. Click Settings > WPM Settings > Manage Player Locations and edit settings for the player's transaction location. See the WPM Administrator Guide for details.

Configure support for proxy server authentication on WPM Players

To configure the WPM Player service to support recordings that authenticate proxy servers: 

  1. In File Explorer, navigate to the following default folder:
    C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\
  2. Run a text editor as an Administrator and open SolarWinds.SEUM.Agent.Service.exe.config
  3. Scroll down to the agentConfiguration section and "uncomment" the <proxyTrustedHosts> section, as shown in this example:

    Note the following details about updating this file:

    • The <proxyTrustedHosts> section should be within the <agentConfiguration> and </agentConfiguration> tags.
    • By default, the <agentConfiguration> tag has no closing tag because it doesn't have any content except attributes. The tag ends with "/>" instead. Remove "/" from the end of the <agentConfiguration>.
    • If the file contains errors, the WPM Player ignores it during startup and uses default settings:
  4. Save changes to the config file.