Question
3
Replies
87
Views
Posted: November 16, 2018
Last activity: November 20, 2018
Closed
Unable to find robotic automation
When trying to invoke the robotic automation from my flow I get this error:
Unable to invoke robotic automation from this screen. The automation service is either unavailable or this system is not authorized to execute automations. You have the option of either quitting or continuing with your work flow.
Upon reviewing other posts I checked my configuration in Runtime.xml and it seems to be correct. Am attaching the runtimeconfig file here.
In another post, it recommended me to try accessing the API directly using http://pegaserver:portnumber/api/v1/runtime/IsAvailable. This threw the following exception
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
I have set the URL in hosts file under etc directory as well. The test connection works well when I try logging into RunTime.
Am I missing anything in the setup?
thanks
***Edited by Moderator Marissa to update platform capability tags****
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Hi Karthik,
When you installed Robotics Studio/Runtime onto your local laptop, there is a checkbox called "Enable RDA" in one of the screens in the installation wizard. Did you check this box? This is an important step because it installs a named certificate into your local Windows certificate store. This certificate is required for successful communication with the locally-hosted REST service inside the Runtime.
Aside from the certificate, you will want to ensure that the RuntimeConfig <Robotics> block has allowedOrigins="*".
<LocalApiService enabled="true" SSL="false" port="9443" allowedOrigins="*" JWTSecurity="false" PegaServerURL="http://10.60.215.106:9080/prweb/api/v1"/>
I downloaded your RuntimeConfig.xml file, and it looks like this is already configured properly. So my guess is that the cert is not installed. Try re-installing Studio/Runtime and let me know if that resolves your issue.