Question
Eclatprime Digital Pvt. Ltd
AU
Last activity: 19 Jul 2024 5:58 EDT
ClientConfiguration Service.DownloadConfigIfNeed:Error While getting etag from server in pega robotics
Hi,
We are getting below error..
Could you please help me on this.
ConfigurationLocation not defined. Using default Configuration location = "XXXX" ClientConfigurationService.DownloadConfigIfNeeded:error while getting etag from server:'WebException:Response Code = InternalServerError'. Response Content Type 'Application/xml;charset=UTF-8'. Friendly Messgae 'The remote server returned an error(500)', internal server error = server url : api/robotics/v1/runtimeconfigs Failed to downloaded new PegaRuntimeConfig.xml from server, will use cached file.
Thank you so much in advance:)
Regards,
Sarveswara Reddy . P
***Edited by Moderator Rupashree to add Capability tags***
Pegasystems Inc.
US
@Sarveswara ReddyThis seems to indicate that you are not correctly configured to connect to your instance of Robot Manager. I would make sure that your CommonConfig is setup properly. You might also check your log to see if there are other messages before this indicating where in the process you are and what server it is trying to connect to.
Eclatprime Digital Pvt. Ltd
AU
@ThomasSasnettCould you please let me know which are properties need to check for reslove this issue in common config file. it 22.1.16 version i am using. and also please confirm is it reqiored runtimeconfig for latest version becuase already it is available PegaRuntimeConfig and common config.
Pegasystems Inc.
US
@Sarveswara Reddy I am not sure I understand your questions. The CommonConfig is fairly simple. If you are connecting to Pega Robot Manager, then you would adjust the following line to your specific values.
<Server name="RobotManager" baseURL="https://myPegaApp.pega.com/prweb" enabled="true" proxyAddress="" RPA="false" authenticationType="Basic" maximumRobots="1" suppressNotificationsForRPA="false" RPAServiceOperator="RPAOperator" robotName="{MachineName}" workgroup="Default"/>
If you are using Basic authorization (i.e. username and password), then you don't need to configure the IdP section.
If you have deployed a Package to your Pega Robot Manager instance, then your developer machine likely has their CommonConfig setup correctly.
Eclatprime Digital Pvt. Ltd
AU
@ThomasSasnettkinldy find my local setting up
<ServerConfiguration tenant=""> <Servers> <Server name="RobotManager" baseURL="http://xxxxx:8080/prweb" enabled="true" proxyAddress="" RPA="true" suppressNotificationsForRPA="false" authenticationType="Basic" RPAServiceOperator="RPAOperator" workgroup="RobotWG2" robotName="{MachineName}" maximumRobots="1" /> <Server name="Config" baseURL="" enabled="false" proxyAddress="" /> <Server name="Intelligence" baseURL="" enabled="false" proxyAddress="" /> <Server name="IdP" baseURL="" enabled="false" proxyAddress="" /> <Server name="CredentialManager" baseURL="" enabled="false" mappingFileLocation="CommonApplicationData" providerType="DPAPI" /> <Server name="PegaDevServer" baseURL="http://xxxx:8080/prweb" enabled="false" proxyAddress="" authenticationType="" /> </Servers> </ServerConfiguration>
<ConfigurationLocation>CommonApplicationData</ConfigurationLocation> <DisplayConnectionError>True</DisplayConnectionError>
@ThomasSasnettkinldy find my local setting up
<ServerConfiguration tenant=""> <Servers> <Server name="RobotManager" baseURL="http://xxxxx:8080/prweb" enabled="true" proxyAddress="" RPA="true" suppressNotificationsForRPA="false" authenticationType="Basic" RPAServiceOperator="RPAOperator" workgroup="RobotWG2" robotName="{MachineName}" maximumRobots="1" /> <Server name="Config" baseURL="" enabled="false" proxyAddress="" /> <Server name="Intelligence" baseURL="" enabled="false" proxyAddress="" /> <Server name="IdP" baseURL="" enabled="false" proxyAddress="" /> <Server name="CredentialManager" baseURL="" enabled="false" mappingFileLocation="CommonApplicationData" providerType="DPAPI" /> <Server name="PegaDevServer" baseURL="http://xxxx:8080/prweb" enabled="false" proxyAddress="" authenticationType="" /> </Servers> </ServerConfiguration>
<ConfigurationLocation>CommonApplicationData</ConfigurationLocation> <DisplayConnectionError>True</DisplayConnectionError>
But still my runtime is not coming to tray. even register service is unchecked (Require TLS/SSL for REST services in this package).. i am reading package from pega reposiroty (file system) and also added runtime config in Robotmanager as well see in below.
Runtime config.xml (Robot Manger file)
<Robotics> <LocalApiService enabled="false" useRouter="true" SSL="false" port="9443" allowedOrigins="*" JWTSecurity="false" PegaServerURL="http://xxxx:8080/prweb"/> <PackageServer baseUrl="http://xxxxxxxx:8080/prweb" UseRobotManagerPackageServer="true"/> </Robotics>
<AppSettings> <!-- ContextResponseTimeout key is used to set the amount of time a context will wait for a response from a remote context --> <add key="ContextResponseTimeout" value="35000" /> <add key="StartupProject" value="C:\Deployment\abc.pega" /> <add key="SingleCopy" value="true" />...........
Pegasystems Inc.
US
@Sarveswara Reddy I would suggest that you open a support request as you likely need to talk this out with someone. The general issue is that your bot is unable to download the RuntimeConfig.xml from your Robot Manager instance. The error also indicates that it cannot find the configuration file location. As far as I know, that is defined in your CommonConfig.xml. If you removed that section, you can find the "stock" CommonConfig.xml in the installation directory. You can copy that and modify the Robot Manager section as needed. If you have your RuntimeConfig.xml published in Robot Manager and available, then it should be able to download. I suspect that I am missing some information as to what it is that you have already accomplished. Is this working as expected on other machines?
Updated: 19 Jul 2024 5:58 EDT
Aflac Inc.
IN
I advise you to look over the following items:
1. Verify the tags in your CommonConfig.xml file. Verify that each and every XML tag is closed correctly.
2. Would you kindly attempt to upload a test deployment package file to Pega Robot Manager from Pega Robotics Studio?
The message stating "Successfully pushed the package to Robot Manager" should to be visible to you.
3. Verify your Pega Dev Studio's (Pega Application) repository settings.
Examine the repository's root folder, which contains the packages that have been stored.
b. Examine the Records -> Sysadmin -> Application Settings -> PyPackageBinariesRepository (located in the setting purpose column). Verify that all of the values (repositories names) have been added.
4. Check your Runtime User Operator ID's Access groups and roles for all the users ( Runtime User, RPA Robot Registrator user, and Developer )
a. Make sure you have the following roles for an RDA User ( Attended User ), RPA=false ( to be set in CommonConfig.xml )
I advise you to look over the following items:
1. Verify the tags in your CommonConfig.xml file. Verify that each and every XML tag is closed correctly.
2. Would you kindly attempt to upload a test deployment package file to Pega Robot Manager from Pega Robotics Studio?
The message stating "Successfully pushed the package to Robot Manager" should to be visible to you.
3. Verify your Pega Dev Studio's (Pega Application) repository settings.
Examine the repository's root folder, which contains the packages that have been stored.
b. Examine the Records -> Sysadmin -> Application Settings -> PyPackageBinariesRepository (located in the setting purpose column). Verify that all of the values (repositories names) have been added.
4. Check your Runtime User Operator ID's Access groups and roles for all the users ( Runtime User, RPA Robot Registrator user, and Developer )
a. Make sure you have the following roles for an RDA User ( Attended User ), RPA=false ( to be set in CommonConfig.xml )
- AutomationPackageManagement:RuntimeUser
- PegaRULES:PegaAPI
- PegaRULES:User4
- PegaRULES:RepositoryUser
b. Make sure you have the following roles for an RPA User ( Unattended User/Robt Registration User), RPA= true( to be set in CommonConfig.xml )
- AutomationPackageManagement:RuntimeUser
- PegaRULES:PegaAPI
- PegaRULES:User4
- PegaRULES:RepositoryUser
c. Make sure you have the following roles for BOT Developers (To push packages from Pega Robot Studio)
- AflacPegaRPA:Administrator
- AflacPegaRPA:PegaAPI
- AutomationPackageManagement:Developer
- PegaRULES:RepositoryUser
Regards,
Aashish