Question
Bank of America
IN
Last activity: 13 Sep 2017 19:58 EDT
How to consume a wsdl and perform a soap call from openspan
Hi.. I am consuming a complex wsdl. The request looks like below. How to form this request xml in open span and how to hit the target URL?
Hi.. I am consuming a complex wsdl. The request looks like below. How to form this request xml in open span and how to hit the target URL?
<soapenv:Envelope >
<soapenv:Header/>
<soapenv:Body>
<v001:xxxxxx>
<v0011:retrieveRequest>
<v0011:osaRequestHeader>
<v0012:providerService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:providerService>
<v0012:component>?</v0012:component>
<v0012:channel>?</v0012:channel>
<v0012:requestorService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:requestorService>
<!--Optional:-->
<v0012:serverInstance>?</v0012:serverInstance>
<v0012:traceId>?</v0012:traceId>
<v0012:applicationId>?</v0012:applicationId>
<!--Optional:-->
<v0012:userId>?</v0012:userId>
<!--Optional:-->
<v0012:userIdType>?</v0012:userIdType>
<!--Optional:-->
<v0012:role>?</v0012:role>
<!--Optional:-->
<v0012:entitlements>
<!--Zero or more repetitions:-->
<v0012:entitlement>?</v0012:entitlement>
</v0012:entitlements>
<!--Optional:-->
<v0012:timestamp>?</v0012:timestamp>
<!--Optional:-->
<v0012:isReplyExpected>?</v0012:isReplyExpected>
<!--Optional:-->
<v0012:intermediaryService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:intermediaryService>
<!--Optional:-->
<v0012:rulesBag>
<!--Optional:-->
<v0012:sets>
<!--Zero or more repetitions:-->
<v0012:set>
<v0012:name>?</v0012:name>
<!--Optional:-->
<v0012:sets/>
<v0012:attributes>
<!--Zero or more repetitions:-->
<v0012:attribute>
<v0012:name>?</v0012:name>
<v0012:value>?</v0012:value>
<v0012:type>?</v0012:type>
</v0012:attribute>
</v0012:attributes>
</v0012:set>
</v0012:sets>
<!--Optional:-->
<v0012:attributes>
<!--Zero or more repetitions:-->
<v0012:attribute>
<v0012:name>?</v0012:name>
<v0012:value>?</v0012:value>
<v0012:type>?</v0012:type>
</v0012:attribute>
</v0012:attributes>
</v0012:rulesBag>
</v0011:osaRequestHeader>
<v0011:retrieveCriteria>
<!--Optional:-->
<v0013:ids>
<!--Zero or more repetitions:-->
<v0014:id>
<!--You have a CHOICE of the next 2 items at this level-->
<!--Optional:-->
<v0014:cedPartyId>?</v0014:cedPartyId>
<!--Optional:-->
<v0014:partyAltIdentifier action="?">
<!--Optional:-->
<v0014:type id="?" srcSystem="CED" desc="?"/>
<!--Optional:-->
<v0014:value>?</v0014:value>
</v0014:partyAltIdentifier>
</v0014:id>
</v0013:ids>
<!--Optional:-->
<v0013:uris>
<!--Zero or more repetitions:-->
<v0014:uri>
<!--Optional:-->
<v0014:type id="?" srcSystem="CED" desc="?"/>
<!--Optional:-->
<v0014:value>?</v0014:value>
</v0014:uri>
</v0013:uris>
<v0013:pathExpression>?</v0013:pathExpression>
<!--Optional:-->
<v0013:srcSystems>
<!--Zero or more repetitions:-->
<v0015:srcSystem>?</v0015:srcSystem>
</v0013:srcSystems>
</v0011:retrieveCriteria>
</v0011:retrieveRequest>
</v001:xxxxx>
</soapenv:Body>
</soapenv:Envelope>
Westpac Banking Corporation
AU
Hi Balaraja,
If you have web service wsdl url then you can configure wsdl file in the serviceclient as shown below.
If other than wsdl then write wrapper class in .net and then use that component in OpenSpan.
Bank of America
IN
Hi JeyaChandra - Thanks for replying.
I have configured the URL in Service Client. But I dont know how to proceed.
How do I build the xml and how do I hit the end point.
1 difference I see in properties when compared to mine is - I am not able to find any bindings
Regards,
Bala
Bank of America
IN
Have attached the service client properties screen print. Sorry, I cant share wsdl file as per our policy. But have mentioned the bits and pieces of the wsdl below for your reference.
In the toolbox, I only see the osaRequestHeader tag.. I am not able to see other tags like providerservice,name,operation,version etc.. But in wsdl all the tags are present under complex type.
Below is the xml, when imported the wsdl using soap ui
<v0011:osaRequestHeader>
<v0012:providerService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:providerService>
<v0012:component>?</v0012:component>
<v0012:channel>?</v0012:channel>
<v0012:requestorService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:requestorService>
in wsdl below is the complex type for retrieve request.
Have attached the service client properties screen print. Sorry, I cant share wsdl file as per our policy. But have mentioned the bits and pieces of the wsdl below for your reference.
In the toolbox, I only see the osaRequestHeader tag.. I am not able to see other tags like providerservice,name,operation,version etc.. But in wsdl all the tags are present under complex type.
Below is the xml, when imported the wsdl using soap ui
<v0011:osaRequestHeader>
<v0012:providerService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:providerService>
<v0012:component>?</v0012:component>
<v0012:channel>?</v0012:channel>
<v0012:requestorService>
<v0012:name>?</v0012:name>
<v0012:operation>?</v0012:operation>
<v0012:version>?</v0012:version>
</v0012:requestorService>
in wsdl below is the complex type for retrieve request.
Doesnt OPENSpan support complex types? Why does all the tags not available under toolbox?
Regards,
Bala
JPMorgan Chase & Company
US
Hi Balaraj,
The service client component is the component that you would need to use for handling web service calls through your Robotic automation
If the input complex type resides within the schema of your wsdl, you should be able to find the complex type in the list of properties once you extract the proxy of that type within your automation.
If the complex type does not reside within the schema of your wsdl, you will need to use a script component to handle creating an instance of the complex type to pass into the service client functions. The same goes for output as well.
The service client component only consumes and outputs simple types by default.
Another option would also be to create a custom service client component yourself and adding the component to your automation.
Below is a blog that goes into creating a web service component through c#.
Make sure that the custom web service inherits from the IComponent Class so that it can be added to the Pega Project.
Thanks,
Bank of America
IN
Hi Sudhakar - I get below error message when I extract the proxy
Error executing link in Automation: Automation1 - From: Automation1.serviceProxy1.Proxy To: Automation1.serviceProxy1.Properties
GetWorkingInstance() could not get instance from TypeProxy. InstanceName: serviceProxy1
return (Outputs);
Westpac Banking Corporation
AU
Hi Bala,
Hope, OpenSpan will support complex type (as per my analysis) by creating instance of the complex type.
Attached reference doc.
Note: you can create instance for complex types as place cursor on 
(blue circle) right click and then create instance.