Go to Robotic Automation version 22.1 documentation

RdaRouter.config file

The settings in the RdaRouter.config file contain information that the Runtime Routing Service uses to direct communications between Pega Platform™ applications and Robot Runtime clients that are hosted on virtual machine servers like a Citrix server or a Remote Desktop Service server. For more information, see Runtime Routing Service.

The RdaRouter.config file is installed with the Runtime Routing Service in builds 19.1.98 and later, and is located in the following folder:

C:\ProgramData\Pegasystems\RdaRouter\RdaRouter.config

The following figure is an example of the RdaRouter.config file, with the keys that you can modify highlighted:

The following table describes the keys in the LocalApiSection of this configuration file that you can modify:

Key

Description

SSL

Enter True if the Runtime Routing Service uses SSL and should be accessed using HTTPS.

port

Specify the port that you want the Runtime Routing Service to monitor when communicating with your Pega Platform application. 

You can modify the corresponding setting in your Pega Platform application using the pegarobotics/runtime/DesktopRoboticsURL dynamic system setting.

runtimePortRangeStart

Enter the number of the first port in the range of ports that you want the Runtime Routing Service to use when communicating with the Robot Runtime clients.

runtimePortRangeEnd

Enter the number of the last port that you want the Runtime Routing Service to use when communicating with the Robot Runtime clients.

allowedOrigins

Specify the domains that the Runtime Routing Service should accept requests from. You can specify a specific domain, a comma-delimited list of domains, or use wildcards, for instance, *.pega.com. 

The following excerpt is an example entry in the RdaRouter.config file:

<LocalApiService SSL="true" port="9443" runtimePortRangeStart="9444" runtimePortRangeEnd="9460" allowedOrigins="*.pega.com" />

 

 


Privacy | Trademarks | Terms of Use | Feedback

Updated: 28 March 2024

© 2016 - 2024 Pegasystems Inc.  Cambridge, MA All rights reserved.

 

OpenSpan data classification label