Service SOAP rules
Pega Platform supports Web service interactions with external systems by using the SOAP messaging standard. Use SOAP service rules when your Pega Platform applications need to act as a web service.
A SOAP service requires a SOAP service package that provides one or more service methods for an external application to use. Each method in the service package corresponds to a SOAP service rule that identifies an activity to run and maps the incoming and outgoing data.
To call a Pega Platform SOAP service, an external application collects
data values, wraps them in an XML document envelope (SOAP envelope) that contains the name
of the requested service, and posts the envelope to the URL of the Pega Platform
PRSOAPServlet servlet. The PRSOAPServlet servlet routes
the request to the appropriate SOAP service package and rule.
SOAP services are run by using requestors with access restrictions that are defined by the service package to which they belong. At run time, the package, class, and method names are passed in as part of a SOAP request so that your Pega Platform application can look up the corresponding Service SOAP rule and run the service activity.
Access
Use the Application Explorer to view Service SOAP rules in your application. Use the Records Explorer to list all Service SOAP rules that are available to you.
Client-side development
After you create all the Service SOAP rules in one package, you can access the Service Package data instance again to generate a WSDL file to support client-side development.
For more information, see Service Packages.
Asynchronous processing
For a comprehensive description of asynchronous processing and instructions on how to configure that functionality, see the following articles:
Category
Service SOAP rules belong to the Integration-Services category. A Service SOAP rule is an instance of the Rule-Service-SOAP class.
- Creating a Service SOAP rule
To process service requests in your Pega Platform synchronously or asynchronously, create a Service SOAP rule. You use SOAP service rules when your Pega Platform applications needs to act as a web service.
- Configuring the request for a Service SOAP rule
Configure the data mapping of the incoming SOAP request from the external client application to Pega Platform on the Request tab.
- Configuring the response for a Service SOAP rule
Configure the data mapping for the reply message on the Response tab of the Service SOAP rule.
- Configuring Service SOAP fault messages
Use the Faults tab of the Service SOAP form to specify data that is returned to the client application when the service encounters a fatal processing error and must return a SOAP fault message. You can also use the Faults tab for other conditions that you want to cause SOAP fault messages to be returned.
- Enabling Web service security in a Service SOAP rule
Configure Web service security (WS-Security) settings to ensure content integrity and confidentiality for SOAP requests and responses.
- Service SOAP form - Working with the Test Cases tab
This tab is visible only to operators who have the AutomatedTesting privilege through an access role.
- Building SOAP services based on an XML Schema Definition
You can build a SOAP service based on your own schema, rather than on Pega Platform definitions. By building a SOAP service this way, the generated WSDL file references the original XML schema document (XSD).
- WSDL generation for Service SOAP rules
After you have created all the Service SOAP rules that are to be included in a service package, generate WSDL files that describe the services in the package.
- Unit testing a Service SOAP rule
Services start their processing in response to a request from an external application. Before you add the external application to your testing process, use the Simulate SOAP Service Execution feature to verify that the service processes data appropriately. When using this feature, you manually provide some representative data to process. You specify a test page for the rule to use, provide sample data as the input, run the rule, and examine the results to see if they are what you expect.
Previous topic Use case: Process inbound file attachments for storage in a repository Next topic Creating a Service SOAP rule