Deploy WPM to remote systems
When you install the primary WPM application on the Orion server, the Web Transaction Recorder and WPM Player service are added to the Orion server automatically.
You can also deploy Web Transaction Recorder and WPM Players to remote systems to:
- Simulate the physical location of end users. Deploy a Web Transaction Recorder and WPM Player to a remote system in the same geographical location as a large group of your end users to receive more accurate WPM data that represents the typical user experience over time. For example, add a WPM Player to a server in Europe to monitor a web application hosted in the US.
- Test firewalls and proxies. Add a WPM Player to a remote system to mimic the authentication that end users must navigate to access a web application. For example, deploy a WPM Player to a remote system located outside of your firewall, perhaps using a proxy.
- Mimic end user permissions. WPM worker processes rely on permissions provided by SEUM-User accounts to perform transaction steps. You can use this type of monitoring to check the security and accessibility of your web applications.
See these topics for details:
- Deploy Web Transaction Recorders to remote systems
- Deploy WPM Players to remote systems
- Enable FIPS mode for WPM on remote systems
You can also use steps in these topics to upgrade WPM components on remote systems.