Question
Bank Of America
US
Last activity: 31 Oct 2019 16:16 EDT
Using a service reference in a robotic automation
I am trying to use a service reference in an automation. I made a console application to test it, and it works. I can not figure out how to use the ServiceClient from the toolbox (of course I have looked at the pega documentation for it), so I added a class library to the solution with the pega project for the purpose of using the service. the library is exactly the same as the console app, I have removed it and added it 3 or 4 times, it is the same code exactly. it has the same appconfig. when I run it in the pega project it throws
"Could not find default endpoint element that references contract 'LIQCED.IWSWrapper' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element."
If someone knows why this is happening or else how to actually use the ServiceClient, that is what I'm after. the endpoint address starts with net.tcp so I don't know if pega only knows how to query http WSDL files or something like that.
Pegasystems Inc.
US
The ServiceClient is for connecting to SOAP services via a WSDL only. We also have a REST client component that can connect to REST services. Is the service you are connecting to a SOAP service? It sounds like the service itself has a reference internally to something that the component cannot find. If you already have the means to write the code to connect to it, then I would suggest creating a Component yourself that you can use to call that service. Without looking at the exact mechanisms of how your service works, I can only speculate. I would suggest that you open a support request if you want to try to use the Pega Robotics component as there may be an issue with how it is handling invalid or otherwise inaccessible pieces of the service.