|
![]() |
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.
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:
Axis2
is specified in the
Axis Version field.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.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.
To perform SOAP connector processing asynchronously: 5.5 GRP-255
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.Queue
.