Runtime Routing Service
In attended robotic automation implementations that are hosted on virtual machine servers, like a Citrix server or a Remote Desktop Service server, and are integrated with Pega Platform™ applications, the Runtime Routing Service directs communication between the Pega Platform applications and the Robot Runtime clients that are running in the same session. The Runtime Routing Service is included in build 19.1.98 and later and works with Pega Platform applications version 8.5 and later.
Note: In addition to installing Pega Robotic Automation build 19.1.98 or later, contact the My Support Portal to request the hotfix for your Pega Platform application that allows you to use the Runtime Routing Service. To request the hotfix, create a support ticket and indicate that the hotfix is for the Runtime Routing Service. For more information, see Applying hotfixes. For more information, see Configuring the Runtime Routing Service.
You can use the Runtime Routing Service with any supported environment, such as Citrix or Windows terminal server, if your automations meet the following criteria:
- Your automations are attended.
- The automations are launched from a Pega Platform application.
The Runtime Routing Service allows you to have multiple attended Robot Runtime clients that are running in the same session as the Pega Platform applications that are integrated with those clients.
For example, if your Pega Customer Service™ application launches a Start My Day automation for your customer service representatives, use the Runtime Routing Service to allow for communication between the Pega Platform application and the Robot Runtime clients that the customer service representatives use for their work.
How the routing service works
In earlier builds, you configure your Pega Platform application to talk to a specific port. You then configure a Robot Runtime client's REST service to monitor the same port for communication purposes; you could not define a port for each Robot Runtime client.
The following illustration shows how communications are routed with this setup:
In build 19.1.98 and later, you configure the Runtime Routing Service to monitor a specific port on the Pega Platform application and the Runtime Routing Service handles the incoming and outgoing messages and automatically routes them to the correct Robot Runtime client.
The Pega Platform application communicates with the Runtime Routing Service on a single port. The Runtime Routing Service and the individual Robot Runtime clients communicate on a range of ports to ensure optimal communication capacity.
The following diagram shows how the Runtime Routing Service handles message traffic.
Communication between Pega Platform applications and Robot Runtime with the Runtime Routing Service.
On Pega Platform, add a custom claim on the RoboticAutomationToken token. This token, which is included with Pega Platform, provides the OperatorID that the system uses to route the message to the correct Robot Runtime. To update the token profile, select Security > Token Profile from the Records menu.
The following is an example:
