|Action||A single event within a step, such as clicking a mouse, entering text, or pressing the Enter key. Multiple actions can be included in a single step, and a group of steps makes a sequence.|
|Authentication binding||When a client certificate is selected during a recorded sequence, the Web Transaction Recorder saves the name, issuer, and other identifying data about the certificate in the recording as an authentication binding. The certificate itself is not stored.|
|FIPS mode||You can run WPM and other Orion Platform products in Federal Information Processing Standard (FIPS) mode to comply with computer security and interoperability standards used by non-military US government agencies and contractors.|
|Managed transaction||A transaction that is assigned to a location and actively reporting statistics to the Orion Web Console. Managed and unmanaged transactions count against your WPM license.|
The primary server used by the Orion Web Console and Orion Platform products.
|Orion Web Console||The web interface where you interact with Orion Platform products. In addition to displaying WPM data and reviewing events, you can use the Orion Web Console to deploy the Web Transaction Recorder and WPM Player service to remote machines, schedule transactions to play at specific intervals, or configure thresholds for alerts.|
SolarWinds Pingdom is a subscription-based, SaaS application that provides synthetic monitoring and Real User Monitoring (RUM) to provide insights into the behaviors and experiences of actual end users. Starting in WPM 2020.2, you can use WPM recordings as Transaction Checks in Pingdom.
Not using Pingdom yet? Click here to start a free trial.
|Recording||A series of navigational steps and actions that are recorded. Once assigned to a transaction location for playback, a recording becomes a transaction. Recordings do not count against your license, but managed and unmanaged transactions do.|
When the WPM Player service plays back transactions, it uses a WPM worker process to perform steps and collect data during playback. Each worker process requires its own SEUM-User account because different processes handle different transaction steps at different times.
SEUM-User accounts isolate playback transactions; they don't share resources such as the browser cache or cookies.
By default, the Orion server includes 2 SEUM-User accounts. When you deploy WPM Players to remote systems, 7 accounts are included. You can adjust accounts to make environmental changes, such as adding proxy settings or adjusting permissions. You can also add accounts if necessary, with a recommended maximum of 12. The limit of accounts on a player depends on the power of the host system (CPU, RAM, and so on).
Synthetic End User Monitor (SEUM) was the original product name for WPM.
|Transaction||A transaction is a recorded sequence of web browser steps assigned to a specific location.|
|Transaction location||After creating a transaction, you can designate the location from which the transaction plays, which can be the Orion server, a cloud instance, or a remote system. Transaction locations are sometimes referred to as "player locations" or "playback locations."|
|Transaction step||A step is a collection of actions within a transaction. For example, the actions required to navigate to a specific URL make up one transaction step.|
|Unmanaged Transaction||An unmanaged transaction is a transaction currently assigned to a specific transaction location, but purposely set as inactive so it does not report statistics to the Orion Web Console. When a transaction is unmanaged, historical data is retained. Unmanaged transactions count against your license.|
|Web Transaction Recorder||A program, accessible from the Windows Start menu, that captures web browser steps as you perform them to simulate typical steps performed by end users, such as mouse clicks, text input, and authentication.|
A Windows service that deploys, manages, and communicates with WPM worker processes to simulate end user experiences by playing back transactions. The formal name of the service is the WPM Playback Player service, but it is also known as the WPM Player.
WPM Players are sometimes called "transaction locations," which refers to how recorded transactions can be assigned to various locations to be played back at scheduled intervals.
|Webview||The area of a web page that is captured in a recording, and then later tracked during playback.|
|WPM worker process||
The WPM Player service uses WPM worker processes to play back transactions, collect statistics, and return results to the WPM Player. Each WPM worker process requires its own SEUM-User account because different processes handle different transactions at different times, and may require specific permissions.