Table of Contents

Configuring Robot Runtime 19.1 and later to work with Robot Manager 6 in RPA implementations

If you are using Pega Robotic Automation version 19.1 or later, to configure Robot Runtime, complete the following instructions.

If you are using a different version, see Configuring Pega Robot Runtime in RPA implementations.

Before you begin

Perform the steps in Enabling the Pega RPA Service to simulate a Secure Attention Sequence.

To run Pega Robot Runtime in Robotic Process Automation (RPA) implementations as a user who differs from the currently logged in Windows user, you must relocate and modify the configuration files. Although the default location for configuration and logging files is the user-specific %AppData%\Pegasystems folder, instead use the %ProgramData%\Pegasystems folder, which is accessible to all Windows users.

  1. From the %ProgramFiles%\Pegasystems folder, copy the RuntimeConfig.xml file into the C:\programdata\Pegasystems folder.
  2. From the C:\programdata\Pegasystems folder, open the CommonConfig.xml file and change the ConfigurationLocation key. For example:
<ConfigurationLocation>CommonApplicationData</ConfigurationLocation>
  1. Save and then close the CommonConfig.xml file.
  2. From the C:\programdata\Pegasystems folder, open the RuntimeConfig.xml file and make the following changes:
    • In the fileName key for Log4Net files, specify the appropriate file names.
    • In the packageServer key, set the baseUrl to the location of the Package Server.
    • In the Shutdown section, set the Behavior value key to WaitForAutomations. For more information, see Runtime configuration settings.
  3. Save and then close the RuntimeConfig.xml file.
  4. From the C:\programdata\Pegasystems\RPAService folder, open the RPAService.config file and confirm the following entries:
    • The enabled key for Pega RPA Service, is set to true.
    • For the Mode key, if you use schedules provided by Pega Robot Manager 6, it should be set to OnDemand. If you use schedules that are defined locally in the RpaSchedule.json file, it should be set to Scheduled.
    • The authorizedGroup key should specify who is granted access. The default is Everyone, which does not restrict access.
  5. If you made changes, save and then close the RPAService.config file.
  6. From the C:\programdata\Pegasystems\RPAService folder, open the SchedulerDefinitions.xml file and ensure that the LogonDisclaimer key is set to False. The enabled key is configured in the appropriate operating system section in the SchedulerDefinitions.xml file. For example:
<MatchSet name="Disclaimer" mode="SignIn" matchSuccess="Continue" matchFailure="Stop" enabled="true">
    <Match type="PushButton" name="OK">
        <Action type="execute" />
    </Match>
 </MatchSet>
  1. If you made changes, save and then close the SchedulerDefinitions.xml file.
    • Add WindowsUser credentials by using the Credentials Manager (credmgr.exe or credmgrui.exe). For more information about the Credentials Manager, see Pega Robotic Automation Credentials Manager utility.
    • Add RegistrationOperator credentials by using the Credentials Manager.
    • Start the Pega RPA Service.
    The install folder contains the default version of the RPAService.config file. You must manually move this file to the C:\programdata\Pegasystems folder.

    For more information on the configuration files discussed in this topic, see Main Robotic Automation Configuration Files.

    For information on how to use the Pega RPA Service to schedule when Pega Robot Runtime can run RPA robots, see Scheduling when a Robotic Process Automation robot runs.

    Suggest Edit

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.