You are on page 1of 3

Understanding SOAP Protocol

SOAP Protocol supports XML Data Structure.

While using SOAP, being a consumer or provider, we must have to implement below two techniques

1. Converting from Clipboard to XML (XML Streaming) For this in Pega We have to Create
XMLStream Rule.
2. Converting from XML to Clipboard (Parsing XML) We have to create ParseXML rule.

While Working with Web Services of SOAP Protocol,

1. As a consumer we have to create Connector Rules (connect SOAP Rule)


2. As a provider we have to create Service Rule. (Service SOAP Rule)

To locate the service, we need END POINT URL.

While Working with Building of SOAP service, once service is create we need to generate WSDL URL and
provide it Requestor.

WSDL : Web Service Description Language. This document contains details about web service (SOAP
Service)

Details Are:

1. End Point URL


2. Request Parameters, Response Parameters.
3. Request Data Structure, Response Data Structure.
4. Authentication Details.

Providing WSDL URL to requestor’s means, providing all the Meta Data about service.

After we build SOAP service, we need to generate WSDL URL.

To work with building a SOAP service, we need to create below rules.

1. Service Package
2. Classes
3. Properties
4. Data Type (Table)
5. Service SOAP
6. XML Stream
7. Parse XML
8. Activity to perform Processing.
9. Work Integration.

All these rules, can be create in Integration Rule Sets and Under Integration Classes.

For services, we need to create under Work Integration Layer.

All these rules gets automatically created by an OOTB Service wizard

You might also like