SOAP Connector form – Completing the Request tab
Use the Request tab to configure the data mapping for the outgoing SOAP message. Use the Request headers section to specify the data needed (if necessary) for the SOAP envelope header. Use the Request parameters section to specify the data for body of the SOAP message.
The data types of the outgoing parameters can be any of the primitive data types specified
in the W3C XML Schema standard. If you used the Connector and Metadata wizard to
generate the connector rules and the WSDL file you identified defines its own complex types,
the Data type for a parameter is XML Page
, which indicates that the
outgoing parameter is an XML object.
Soap Action HTTP Request Header Field
Use this section to specify a custom header that servers such as firewalls can use to appropriately filter SOAP request messages in HTTP. If the SOAPAction header field value is an empty string (because you did not provide a header), the server presumes the intent of the SOAP message is provided by the HTTP Request-URI.
- Select the Specify custom SOAP action URI check box to include the SOAPAction URI.
- The SOAP action URI field is required if you have selected the check box above. In this field, enter the URI of the custom SOAPAction that you wish to include.
Request headers
Use this section to map values for SOAP headers. The data type of a SOAP header is an
element (an instance of the W3C DOM object
org.w3c.dom.Element
). The value
of a SOAP header must be well-formed, namespace-qualified XML, typically generated by an XML
Stream rule. If your application requires SOAP headers that conform to a WS-Security format
rather than using HTTP Basic authentication, you can define that header content here.
- If the Applies To class of the XML Stream rule is the same as the Applies To class of the connector rule, you can create a data mapping that specifies the XML Stream rule in this section.
- If the Applies To class of the XML Stream rule is different from that of the connector rule, call the XML rule from the connector activity and then create a data mapping for the property that holds the stream in this section.
See also Pega Community article How to map a SOAP Header in the request message of a SOAP connector.
Field | Description |
---|---|
Name | Enter the external name of the SOAP request header. |
Description | Enter a text description. |
Map from |
Do one of the following:
|
Map from key |
Do one of the following:
|
Request parameters
Field | Description |
---|---|
Data type | Select the XML schema data type of the external value you are mapping. Select
any primitive data type in the W3C XML Schema standard. See How to complete mapping details for SOAP and dotNet connectors for details
about data types. Select the If the SOAP operation style is |
Name | Enter the external name of the request parameter. |
Description | Enter a text description for this row. |
Map from |
Specify the source or the type of source of the value in
Pega Platform. The choices that appear in the selection list depend on
the data type specified in the Data Type field:
If more choices appear, they each identify a custom function rule in a
|
Map from key | Specify the key to locating the property or rule in the source specified in
the Map from field:
|