How to get Robotics solution from Package Server
Hi,
In a RPA solution, I have these 3 machines:
M1- Pega Platform with Pega 7.4
M2- Package Server: with PackageServer and Robotics Studio 8.0.1100.0
M3- Runtime: with Robotics Runtime 8.0.1100.0
And I do the following steps:
1- I deploy and publish a robotics solution from M2 and I can check that this solutions appears in Robot Manager and is saved in Packages folder in M2.
2- I have modified in M3 the commonconfig.xml:
<Server name="RobotManager" baseURL="https://*****:8443/prweb" enabled="true" proxyAddress="" RPA="true" authenticationType="Basic" workgroup="*****" robotName="{MachineName}"/>
and in RuntimeConfig.xml:
<PackageServer baseUrl="http://M2:5000" />
3- I assign from Robot Manager a solution to Runtime M3
4- When I execute Runtime of M3, it starts nice but it is not able to load its openspan solution assigned from M2.
Any ideas? Is missing something in configuration files?
Thanks a lot,
Capgemini
ES
Hi,
I attach the log and in its lines I have found:
Error. No package assignment is on Robot Manager for this user.
But in Robot Manager it is assigned, see another attachment.
Thanks
Pegasystems Inc.
US
Please check which Operator ID you use for Runtime registration. It seems there is a wrong one in place or it is set up incorrectly. If you need to try with another one - delete RPAStartup.info file under %appdata%/OpenSpan and try to start Runtime once again.
Operator Id's access group should have PEGARULES:RoboticAdministrator role.
Please also check if you have set up pyGetAccessGroupForRobotByWorkGroupdecision decision table.
See section "Configuring Pega Platform to register virtual machines" for more details: https://community.pega.com/knowledgebase/articles/tutorial-automating-processes-your-pega-platform-application-robotic-process
Capgemini
ES
Hi,
The registration is OK and I can see the name of M3 machine as an operatorID I know these points about deleting RPAStartup.info to enter credentials another time and about the rule pyGetAccessGroupForRobotByWorkGroupdecision I can asume it is correct because on the contrary the registration of the robot would be wrong.
I have done the following test: I have load manually the openspan solution in the runtime and on creating a work case the assignation is queued and executed correctly by the M3 runtime.
I am thinking it is possible this happens because the robot manager version is the 5. I have seen in robot manager there is a dropdownlist to change the status of the queue of workgroup with options "running" and "stop", could it be reason? may I change the status of this queue to "running"?
Thanks,
Pegasystems Inc.
US
Hi,
I believe workgroup queue options affect only ability to send work items to queues, but it is not related to package assignments.
I'm able to reproduce the issue if I delete "AutomationPackageManagement:RuntimeUser" role from the access group. Could you please double check that this role is in place? It allows to retrieve a package.
If it still doesn't work, I don't have other ideas - maybe someone else can help.