Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

SAP Connector form - Completing the Request tab

Updated on April 6, 2022

Use the Request tab to configure the data mapping for the outgoing SOAP message to the SAP system. 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.

Note: This tab is displayed for the SOAP connector type only.
Important: Connect SAP rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Connect SAP rules does not follow Pega development best practices. Use Connect SOAP rules instead. For more information, see Connect SOAP rules.

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 that 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.

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.

FieldDescription
NameEnter the external name of the SOAP request header.
DescriptionEnter a text description.
Map from Do one of the following:
  • If the Applies To class of the XML rule that provides the value for this header is the same as the Applies To class of the connector rule, select XML Stream.
  • To manually enter the XML content to be included in the header, select Constant.
  • If the Applies To class of the XML rule is different from that of the connector rule, select Clipboard.
Map from key Do one of the following:
  • If you map from XML Stream, enter the Stream Name (the second key part) of the XML Stream rule. The system uses the first key part (the Applies To class) to find the XML rule.
  • If you map from Constant, enter the well-formed XML to be included in the request header.
  • If you map from Clipboard, select the property that holds the XML text. You can use a linked property reference to identify the property containing the value.

Request parameters

FieldDescription
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 XML Literal data type if the parameter is an XML object and you want to map the actual (literal) XML from an XML stream rule or a single-value text property. In this case, you must also specify Axis2 on the Advanced tab. For more information, see More about SOAP Connectors.

If the SOAP operation style is document-literal and you are creating this rule manually, you can either specify simple argument-property mapping entries for the values in the message or use the XML Literal data type.

NameEnter the external name of the request parameter.
DescriptionEnter 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:
  • Clipboard — The source is a property or page on the clipboard.
  • Constant — The source is a fixed value that does not change.
  • XML Stream — The source is a stream of XML data formatted by an XML Stream rule.

If more choices appear, they each identify a custom function rule in a MapFrom library. Review the function rule to determine what it does.

Map from key Specify the key to locating the property or rule in the source specified in the Map from field.
  • If you map from Clipboard Enter a reference to a single value or page property.Click the Open icon to review the property.

    You can use a linked property reference to identify the property containing the value.

  • If you map from Constant, enter a literal text string. To include blank spaces in your text string, surround the string with double quotation marks.
  • If you map from XML Stream, enter either the Stream Name—second key part—of the appropriate XML Stream rule or a page name and Stream Name using the syntax PageName.StreamName.

    The page must be on the clipboard for rule resolution to find the rule. If you specify the stream name only, the system uses the Applies To key part of this connector rule as the first key part of the XML rule.

  • If you map from a Rule-Utility-Function from a MapFrom library, either select the property that holds the value to be processed by the function or leave this field blank, as appropriate for the function.
  • Previous topic SAP Connector form - Completing the Service tab
  • Next topic SAP Connector form - Completing the Response tab

Related articles

Connect SAP rules - Completing the Create, Save As, or Specialization form

Tags

Pega Platform 8.6 Data Integration

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us