Installing Pega Robot Runtime Parameters

General
, , , ,
1

I have the following command lines to Install Pega Robot Runtime:

PegaNativeFoundationSetup.exe /qn /norestart /L*v PegaNativeFoundationSetup-Install.log

PegaSynchronizationEngineSetup.exe AI_DESKTOP_SH=0 AI_QUICKLAUNCH_SH=0 /qn /norestart /L*v PegaSynchronizationEngineSetup-Install.log

PegaBrowserExtensionSetup.exe INST_EDGE=1 INST_CHROME=1 /qn /norestart /L*v PegaBrowserExtensionSetup-Install.log

PegaRPAServiceSetup.exe /qn /norestart /Lwe PegaRPAServiceSetup-Install.log ENABLE_RPA_SERVICE=“True” INST_RPA=0 RPA_GROUP=“Everyone” RPA_MODE=“OnDemand” RPA_LOGGING=“True” ROBOT_WORKGROUP=“WorkGroup@Name” ROBOTNAME=“{MachineName}” RPA_SERVICE_OPERATOR=“{MachineName}_RPA”

After these installs, the Robot Runtime is installed with the following command line:

PegaRobotRuntimeSetup.exe /qn /norestart /L*v PegaRobotRuntimeSetup-Install.log ENABLE_RPA=“True” ENABLE_PRM=“True” INST_PBE=“True” INST_RPA=“True” PRM_SERVER=“https://www.sample.url:1234/pr”

However the log states the following where it seems to read the already present CommonConfig.xml and overwriting command line parameters.

Action start 11:39:03: AI_XmlLocator.

MSI (s) (E0!E8) [11:39:03:969]: PROPERTY CHANGE: Deleting PRM_SERVER property. Its current value is 'https://www.sample.url:1234/pr'.

MSI (s) (E0!E8) [11:39:03:969]: PROPERTY CHANGE: Modifying ENABLE_PRM property. Its current value is 'True'. Its new value: 'false'.

How should the command line be constructed to stop this from happening?

2

@SajidR17441484To clarify, are you saying that you already have a CommonConfig setup with the parameters you are supplying in the installation command line and that after running this command, the CommonConfig.xml now has incorrect settings for these values? Which build of 22.1 are you using?

3

@ThomasSasnett We are using 22.1.45

It came in a zip file called RAR-22.1.45.

4

@SajidR17441484Would you please also confirm that the problem is not the message appearing in your install log, but that your CommonConfig.xml ultimately does not have the settings you specified? If that log message you mentioned were not present, would everything be working as intended?

5

@ThomasSasnettI can confirm that CommonConfig.xml is not updated as a result.

6

@ThomasSasnett Are there any workarounds to this issue?

How do I raise a support request?

Thanks for all your help thus far.

7

@SajidR17441484I suggest that you open a support request, so that this can get corrected by the product team. If you do, please note the INC value on this post.

8

@SajidR17441484You can go to https://msp.pega.com to raise a support request.

A workaround would be to configure your own CommonConfig.xml outside of the installer and then copy it over after the installations have taken place.