Documentation forWeb Performance Monitor

Manage WPM Player service accounts

As described in the How WPM works, when a WPM Player simulates end user activities by playing back recorded transactions, it uses WPM worker processes to:

  • Log into the host system,
  • Perform steps in a recorded transaction, and
  • Collect statistics and screenshots during playback.

Because worker processes can be run simultaneously to handle separate playback of transaction steps, each worker process requires its own WPM Player service account. By default, the WPM Player on the SolarWinds Platform server includes two WPM Player service accounts, and WPM Players deployed to remote systems include seven accounts. You can add up to 15 WPM Player service accounts; however, SolarWinds recommends using seven accounts during playback. The limit of accounts on a player depends on the power of the host system (CPU, RAM, and so on). More than seven accounts can consume too much CPU and RAM, resulting in poor performance.

You can adjust WPM Player service accounts to make environmental changes, such as adding proxy settings or adjusting permissions. For example, customize a WPM Player service account to mimic the authentication a typical user requires to access a web application so you can simulate customer traffic. For a transaction with a step that accesses secured resources, you can adjust a WPM Player service accounts to provide rights to those secured resources.

Note the following details about WPM Player service accounts:

In addition to describing how to configure WPM Player service accounts permissions, this section explains how to:

Configure WPM Player service account permissions

To perform a transaction step, each WPM worker process requires its own WPM Player service account with the necessary permissions. If playback fails due to permission issues, make sure that all WPM Player service accounts belong to the local Administrators group on the host system.

To set permissions for WPM Player service accounts:

  1. Log into the system that hosts the WPM Player.
  2. Open the Computer Management tool from the Windows Start menu.
  3. Double-click Local Users and Groups, and then double-click Users.
  4. Right-click SEUM-User-1, and then click Properties.
  5. Switch to the Member Of tab, and then click Add.
  6. Type the local Administrator's group name for this user. To find all available groups, click Advanced > Find now, and then select the Administrators group and click OK.
  7. Press OK twice.
  8. Repeat steps 3—6 for each SEUM-User, and then click OK.

Add WPM Player service accounts

WPM worker processes rely on specific WPM Player service accounts. These service accounts provide the necessary permissions for the proper functioning of WPM worker processes. Each transaction performed by the WPM Player involves multiple steps. For playback of recorded transactions, individual WPM worker processes execute these steps, gathering data during playback. To ensure proper segregation and control, each process has its own unique WPM Player service account. This is crucial for effective permission and access management during concurrent execution of distinct transaction steps.

To add a WPM Player service account:

  1. (Recommended) Back up the AgentSettings.dat file, located at C:\ProgramData\SolarWInds\SEUM\Data, before proceeding.
  2. Log into the system that hosts the WPM Player.
  3. Use the SolarWinds Platform Service Manager to stop the SolarWinds WPM Playback Player service.
  4. Navigate to the following default folder: C:\ProgramData\SolarWinds\SEUM\Data.
  5. In a text editor:
    1. Open AgentSettings.dat.
    2. Search for numberOfWorkerProcesses in the AgentSettings.dat file and edit the value.
    3. Save changes.
  6. Start the SolarWinds WPM Playback Player service.
  7. Open the Computer Management tool from the Windows Start menu.
  8. (Optional) Click Local Users and Groups > Users, and then confirm the number of WPM Player service accounts.
  9. Make sure all WPM Player service accounts belong to the local Administrator group.

  10. Repeat these steps for each WPM Player remote locations.

Set passwords for WPM Player service accounts

For information configuring WPM Player service accounts, see Use domain accounts as WPM Player service accounts.