Manage WPM transactions
After creating a recording, you can assign it to the location where you want the recording to run, thus creating a WPM transaction. The transaction location (also called a "playback location") can be the Orion server or any system where you've deployed the WPM Player service.
Transactions are more than just recordings matched up with locations. The original recording is a raw file but the transaction is an active monitor that performs web actions based on the steps in the file to gauge performance. You can schedule transactions to play at regular intervals (the default is 5 minutes) and set timing thresholds so WPM triggers alerts in the Orion Web Console if transactions exceed their expected run time.
FIPS mode can impact the ability to play transactions, depending on the steps involved. For example, a "401 Unauthorized" message appears if a step requires authentication but FIPS mode is enabled.
To learn more about transactions, see:
- Create WPM transaction monitors
- Manage transaction locations in WPM
- Configure proxies for WPM transaction locations and transactions
- Set thresholds in WPM
- Group related WPM transactions
- Stop and start WPM transaction monitoring
- Configure WPM transaction dependencies
Click here for a quick overview video about recordings, transactions, and dependencies.