More about SOAP connector rules

Development

For information about how to build a SOAP connector, see Building SOAP Connectors, a document on the Integration section of the Pega Developer Network. For information about testing SOAP connectors, see Testing Services and Connectors, also on the Pega Developer Network.

Axis2, SOAP attachments, XML Literal data type, SOAP 1.2

The Process Commander SOAP connector architecture uses an Axis client that serializes and deserializes the SOAP messages. Connectors created in V5.5 or later use the Axis2 Axis client. However, SOAP connectors created in a version prior to V5.5 may continue to use Axis 1.2.1.

As described in PRKB-24093 How to verify and troubleshoot rules created from XSD or WSDL by Accelerators, some XSD constructs are too ambiguously defined to be interpreted by the Accelerators. For many of these issues, a work-around is to modify the generated Parse XML or XMLstream rule yourself so that it interprets the data as you intended. For SOAP connectors, however, XML objects are mapped to and from XML Page parameters whose schema is described in model rules, not Parse XML and XML stream rules. If the generated model rules cannot handle the XSD constructs in your WSDL file, complete the following steps to map the data to and from Parse XML and stream rules instead:

1. Use the Metadata and Connector Accelerator to generate Parse XML and stream rules from the WSDL.
2. Open the connector rule, select the Advanced tab and ensure that Axis2 is specified in the Axis Version field.
3. Still on the Advanced tab, delete the rows in the Schema Definitions sections.
4. On the Request tab, change the data type of the parameters being mapped from XML Page to XML Literal, change the Map From option from Clipboard to XML Stream, and then identify the stream name in the Map From Key field.
5. On the Response tab, change the data type of the parameters being mapped from XML Page to XML Literal, change the Map To option from Clipboard to XML Parse, and then identify the stream name in the Map To Key field.

You can also map the values to and from single-value clipboard properties and then call the parse or stream rule from the connector activity.

Asynchronous execution by the Pega-IntSvcs agents

To perform SOAP connector processing asynchronously: 5.5 GRP-255

1. Create a Connector Request Processor data instance that defines the characteristics and classes of queued requests. Associate this data instance with the RuleSet that contains the Connect SOAP rules.
2. On the Service tab of the Connect SOAP rule, select queuing in the Intended for field and identify the Connector Request Processor created in step 1. Leave the Response tab blank; it is not used.
3. Update one or more Data-Agent-Queue instances to ensure that the ProcessConnectQueue agent entry within the Pega-IntSvcs agent is enabled with an appropriate time period.
4. In the activity steps that execute the Connect-SOAP method, set the Execution Mode parameter value to Queue.
5. Test.

Performance Statistics

For information on gathering performance information about this connector see Testing Services and Connectors, a document on the Integration pages of the Pega Developer Network.

Related PDN articles

• PRKB-26032 How to create a SOAP connector that uses a digital signature and encryption
• PRKB-25654 How to create SOAP connectors that use WSS username tokens and timestamps
• PRKB-25656 How to test a SOAP connector using sample data

	Integrator task, connector, SOAP
	Creating Connector Simulations About Connect Request Processor data instances Connect-SOAP method How to detect lengthy connector executions Understanding the Pega-IntSvcs agent
	W3C SOAP 1.1 Specification W3C HTTP 1.0 Specification
	Atlas — Standard SOAP Connector rules

About Connect SOAP rules