Question 4 Replies 67 Views × Close popover Siva komana (HiPEGA) CPFB Siva komana CPFB SG View Profile Send Message HiPEGA Member since 2015 3 posts CPFB Posted: July 5, 2019 Last activity: July 6, 2019 Posted: 5 Jul 2019 3:11 EDT Last activity: 6 Jul 2019 5:37 EDT Closed How to remove soap12 binding from pega created Service Pega by default generates two bindings ServicesBindingSOAP and ServicesBindingSOAP12 , How to remove one binding , Current version is PegaPRPC 7.4 Other system is not compatable of choosing the binding . ***Edited by Moderator: Lochan to update platform capability tags*** Pega Platform Data Integration × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × 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. Posted: 1 year ago Posted: 5 Jul 2019 10:21 EDT × Close popover Nandita Das (dasn1) PEGA Senior Technical Solutions Engineer Pegasystems Inc. IN View Profile Send Message dasn1 PEGA replied to HiPEGA Hi , You can edit the WSDL and remove the undesired Binding element as per you need manually as the wsdl is editable. Thank You, Posted: 1 year ago Posted: 6 Jul 2019 2:12 EDT × Close popover Siva komana (HiPEGA) CPFB Siva komana CPFB SG View Profile Send Message HiPEGA CPFB replied to HiPEGA As the pega generates WSDL by default 2 bindings , Service Package, Service soap does not provide options to edit. Could you please explains the steps to edit. Posted: 1 year ago Posted: 6 Jul 2019 2:39 EDT × Close popover Udhay Raman (ramau) Cognizant Technology Limited Lead Technical Architect Cognizant Technology Limited IN View Profile Send Message ramau Cognizant Technology Limited replied to HiPEGA Hi, 1. Create a Webservice and get the .wsdl file from PRPC. 2. Manually remove any attributes, ports and bindings that reference SOAP12. 3. For example, the following references been removed in this case. xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/ <binding name="ServicesBindingSOAP12" type="nslt1:ServicesType"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="CreateTaskID"> <soap12:operation soapAction="urn:PegaRULES:SOAP:PegaSampleSimpleTask2:Services#CreateTaskID" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> </binding> <port name="ServicesPortSOAP12" binding="nslt1:ServicesBindingSOAP12"> <soap12:address location= "https://xxx.com:443/prweb/PRSOAPServlet /SOAP/PegaSampleSimpleTask2/Services"/> </port> 4. Click ‘Setup’ link. 5. Consume wsdl and parse it. Posted: 1 year ago Posted: 6 Jul 2019 5:37 EDT × Close popover Siva komana (HiPEGA) CPFB Siva komana CPFB SG View Profile Send Message HiPEGA CPFB replied to HiPEGA Hi Ramu, I think you are answer about connect soap . My question is on when pega is service provider , Issue : Other legacy system is not able to consume when the WSDL has 2 bindings . So other integration system asking us to provide only one binding.