Posted: 16 Nov 2015 9:06 EST Last activity: 24 Nov 2015 3:02 EST
Approach for creating a new soap service
I would like to create a soap service in PEGA 7. From my java background, I follow one of the two approaches below.
1. Wsdl first approach where in we create the wsdls/xsd first and generate the template in tools like exlipse. Suitable for new services.
2. Process as service where we can enable the existing functionality as webservice. Can be achieved in Eclipse. Suitable to enabled existing functionality as service.
Now in PEGA, how do I achieve both. In Service accelerator, I could not notice it receiving wsdl/xsd as input to generate the parse and stream rules (It is available in connector and metadata accelerator)
Thanks for the reply. I am finding some difficulty in create a soap service. Below is my scenario.
I have to develop a new service and I have arrived at a wsdls and xsds using some tools. The service has around 15 operations. Request and Response types of each service operations are very huge and I have around 25 xsds. Now how do I generate the rules?
If I import using the connector and metadata accelerator, it is considering as a connect-soap and trying to create a connect-soap rule with XML Stream and Parse XML for the request and response types mapped in the wsdl. It is a actually a reverse of service-soap where XML Stream of connector should be a parseXML for service.
How do I proceed here? Wont PEGA cleanly support the wsdl first approach? Please clarify
Use Conector Metadata wizard and generate ur class structure. Then delete the connector activity, parse xml, xml streams and connect soap generated from Connector Metadata wizard. Just keep the class structure.
And then run the Service Wizard using the serivceclass generated from connector metadata wizard..... and then u r done :)
Thanks Amitabh. That is one of the workarounds. but i was expecting PEGA to handle it in much cleaner way because I thought wsdl first approach is very common for soap services and PEGA should take wsdl as an option to generate servicepackage, service soap rule and xml rules. Now I am clear that its not possible in PEGA.