Help Connecting Pega 7.2.1 to Pega Robotics studio 8.0
Hello, I have been unable to get Pega to communicate with the Pega Robotics REST service and I have been following the steps in https://pdn.pega.com/pega-robotic-automation-studio-and-runtime-configuration-pega-7-platform-applications
- I Have installed Pega 7.2.1 and Pega Support SE-28846
- My Pega instance is SSL
- I have added my domain to allowedOrigins in RuntimeConfig.xml to be able to whitelist my domain
- LocalApiService is enabled
- port is 9443
- DesktopRoboticsURL in Pega is set to localruntime.pega.com:9443
When I run the flow action, I get the "Unable to invoke robotic automation from this screen." Message and the following information is in the Console.
Additionally, if i try to access the Relevant Record from Robot Activity in Studio, i get an Error popup - Error connecting to Studio.
Hello, I have been unable to get Pega to communicate with the Pega Robotics REST service and I have been following the steps in https://pdn.pega.com/pega-robotic-automation-studio-and-runtime-configuration-pega-7-platform-applications
- I Have installed Pega 7.2.1 and Pega Support SE-28846
- My Pega instance is SSL
- I have added my domain to allowedOrigins in RuntimeConfig.xml to be able to whitelist my domain
- LocalApiService is enabled
- port is 9443
- DesktopRoboticsURL in Pega is set to localruntime.pega.com:9443
When I run the flow action, I get the "Unable to invoke robotic automation from this screen." Message and the following information is in the Console.
Additionally, if i try to access the Relevant Record from Robot Activity in Studio, i get an Error popup - Error connecting to Studio.
- baseURL in StudioCOnfig is set to httpsL//[my pega server] + /prweb/prweb/api/v1/
- Username and password are supplied and that user has the PegaRULES:PegaAPI role
Is anyone able to help?
David
Accepted Solution
Pegasystems Inc.
US
This issue was resolved via Openspan ticket. There were stale StudioConfig.xml and RuntimeConfig.xml files and after correcting the former with appropriate URL, user was able to connect to Pega and get Relevant Records. Also, the config files were enabled by checking the runtime icon setting. This allowed visibility to "C:\Users\sandbox\AppData\Roaming\OpenSpan where the stale files were". After every uninstall/reinstall, these need to be cleared.
Pegasystems Inc.
US
Hey David,
Let's start simple.
Can you ping the server? Can you access the server (and login) from a browser? What happens when you attempt to access the baseUrl from a browser?
One more thing to try:
You should also confirm that you can make Pega API calls from the Designer Studio. Access the Pega API from this menu:
And try and do something simple like GET /cases (which returns all the cases in your application)
If there is something fundamentally wrong, then then you won’t be able to hit the API from the designer studio, etiher.
Accepted Solution
Pegasystems Inc.
US
This issue was resolved via Openspan ticket. There were stale StudioConfig.xml and RuntimeConfig.xml files and after correcting the former with appropriate URL, user was able to connect to Pega and get Relevant Records. Also, the config files were enabled by checking the runtime icon setting. This allowed visibility to "C:\Users\sandbox\AppData\Roaming\OpenSpan where the stale files were". After every uninstall/reinstall, these need to be cleared.
EPAM Canada
CA
Can you let me know the sizing of your pega rpa console server
PEGA 7.2.1 + hotfix + console zip
what RAM/CORES/CPU/HD size/ DB schema size?
how many robots are you monitoring or targed for ?