Configure remote systems that host 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.
- The Web Transaction Recorder does not save client certificates in recordings. You'll need to install them on remote systems used to create recordings, as well as remote systems that host the WPM Player service where transactions that check certificates will be played back. See Add client certificates to support WPM playback.
- Starting in WPM 2020.2.2, several Windows settings are updated during WPM Player deployment:
- Net.Tcp Port Sharing Service: The Startup Type is set to Manual on the Orion server and any Additional Polling Engines (APEs). On remote systems, the Startup Type is set to Automatic.
- SolarWinds WPM Playback Player service: A dependency with the Net.Tcp Port Sharing Service is added.
For the latest requirements for remote systems that host WPM Players, see the WPM System Requirements.
To configure the WPM Player service:
- Log into the system that hosts the WPM Player service.
- Open the WPM Player Settings tool from the Start menu.
- In the WPM Player Settings tool, select a communication method and provide values, as prompted.
- Server-initiated communication sets the WPM Player service 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 the WPM Player service on remote systems to actively initiate communication with the Orion server on port 17782. Active agents 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.
- (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.
- Click Save.
- After two minutes, check logs for an entry that indicates the WPM Playback Player service is ready to receive commands from the Orion server or an Additional Polling Engine:
INFO SolarWinds.SEUM.Agent.Service.AgentServiceApp - HTTPS Server listening at https://localhost:17781/
The default location for WPM logs is
- (Optional) Configure support for proxy server authentication, as described next.
- (Optional) Enable FIPS by adjusting Windows OS settings.
If you change WPM Player settings later, be sure to update the Orion server with the latest information. In the Orion Web Console, click Settings > All Settings > WPM Settings > Manage Player Locations and edit settings for the player's transaction location.
To configure the WPM Player service to support recordings that authenticate proxy servers:
- In File Explorer, navigate to the following default folder:
C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\
- Run a text editor as an Administrator and open
- Scroll to the
agentConfigurationsection and "uncomment" the
<proxyTrustedHosts>section, as shown in this example:
Note the following details about updating this file:
<proxyTrustedHosts>section should appear between the following tags:
- By default, the
<agentConfiguration>tag doesn't have a closing tag because it has no content except attributes. The tag ends with "
/>" instead. Remove "
/" from the end of the
- If the file contains errors, the WPM Player ignores it during startup and uses default settings.
- Save changes to the config file.