RPAService.config.xml file
The settings in the RPAService.config.xml file contain information that the Pega RPA Service uses to connect to the Pega Synchronization Server. These settings also control how the Pega.Loader responds when there is no package to run.
The RPAService.config configuration file is installed with the Pega RPA Service and is located in the following folder:
C:\ProgramData\Pegasystems\RPAService\RPAService.config
The following is an example of the RPAService.config file, with the keys that you update highlighted:
The following table describes the keys in this file:
Key |
Description |
|
enabled |
Enter True to enable logging. The default is False. |
|
Mode |
This key determines the scheduling behavior of the Pega RPA Service. If you enter Scheduled, the schedules are pulled from the RpaSchedule.json file. If you enter OnDemand, the schedules are received from Robot Manager. |
|
AuthorizedGroup |
Enter the name of the authorized group for the remoting channel. |
|
BaseURL Available in Pega RPA Service 3.1.4.0 or later. |
Enter a URL here if you want to override the BaseURL key value in the RobotManager section of the CommonConfig.xml file. Note: This key only applies to the Pega RPA Service. |
|
RuntimeLaunchRetryCount |
This setting only applies if you entered Scheduled in the Mode key. Enter the number of times the Pega RPA Service should attempt to start Pega Robot Runtime if it is not running during a scheduled period. This running count is reset when Pega RPA Service is restarted, or a new schedule is processed. |
|
RuntimeLaunchRetryIntervalMins |
Specify, in minutes, the interval between attempts to start Pega Robot Runtime if Pega Robot Runtime fails to launch. |
|
ConsecutiveInvalidLoginLimit |
Set to the maximum number of times that you want to allow the Pega RPA Service to fail to register before it stops trying. Once the issue that is preventing a successful connection is resolved, the RPA Service must be restarted. Set the value to zero (0) to allow unlimited attempts. The following is an example: <add key=" ConsecutiveInvalidLoginLimit " value=“20"/> |
|
LogCategories:Service |
Enter a number from zero (0) to four, with four (4) being the most verbose to indicate the log level for the Service portion of the Pega RPA Service. This controls communication with the Robot Manager. |
|
LogCategories:Scheduler |
Enter a number from zero (0) to four, with four (4) being the most verbose to indicate the log level for the Scheduler portion of the Pega RPA Service. This controls implementing the schedules. |
|
LogCategories:Loader |
Enter a number from zero (0) to four, with four (4) being the most verbose to indicate the log level for the Loader portion of the Pega RPA Service. This controls the loading of Pega Robot Runtime. |
|
ScheduledTaskStartBoundary Available in Pega RPA Service 3.1.4.0 or later. |
Enter the number of seconds to wait before scheduled task is allowed to start after screen unlock or user login. Use this setting to set a longer custom start boundary for slow environment. |
|
LogCategories:SessionManager |
Enter a number from zero (0) to four, with four (4) being the most verbose to indicate the log level for the SessionManager portion of the Pega RPA Service. |
