Adding the Pega Loader program on the Citrix server
Use the Pega Loader program to start Robot
Runtime on your Citrix server. On the Citrix client, Robot Runtime passes information to the published
virtual application (
Pega.Loader.exe). The Pega Synchronization Engine uses this information to ensure that the correct
verson of Robot Runtime is installed on the
- In Windows, start Citrix Studio.
- In the Citrix Studio window, select Delivery Groups.
- In the Actions pane, click Add Applications.
- In the Create Application dialog box, click Next.
- In the list of applications, click Add applications manually.
- In the Add Applications Manually dialog box, in the Path to executable file field, click Browse.
- In the Choose share dialog box, select the share that you want to browse, and then click Continue.
- In the Open dialog box, browse to the Pega.Loader
installation folder. The installation folder is typically located at:
...\Program Files (x86)\Pegasystems\Pega Synchronization Engine.
- Select the
Pega.Loader.exeprogram and then click Open.
- In the Add Applications Manually dialog box, in the
Command line argument (optional) field, enter a
percent sign and two asterisks (%**).
C:\Program Files (x86)\Pegasystems\Pega Synchronization Engine\Pega.Loader.exe” %**This command allows the ICA client to pass arguments to Robot Runtime when it launches. There are additional configuration screens that contain options such as color depth, which Citrix server to run on, and so on. Refer to the Citrix documentation for information about these fields.
- In the Application name (for user) field, enter Pega.Loader.
- In the Application name (for administrator) field, enter Pega Robot Runtime, and then click OK.
- In the Create Applications dialog box, click Next.
- In the Summary dialog box, click Finish.
- In the Citrix Studio window, click the Application tab.
- Highlight Pega Robot Runtime and confirm the application
setup on the Details tab.
Note: For solutions that have groups of users with varying Published Application names, you can use environment overrides to set custom values for properties such as the Published Application based on the deployed environment (for example: "Group1", "Group2", "Group3"). Previous topic Adding a Pega virtual channel to the allow list Next topic Citrix pass-through authentication