For information about implementing an SAP connector, see Pega Process Extender for SAP Business Suite. For general information about SOAP-based Connect SAP rules, see Building SOAP Connectors, a document on the Integration section of the PDN. For information about testing SOAP connectors, see Testing Services and Connectors, also on the PDN.
The Pega 7 Platform SOAP connector architecture uses an Axis client that serializes and deserializes the SOAP messages. Connectors created in PRPC Version 5.5 or later use the Axis2 Axis client. However, SOAP connectors created in releases before PRPC Version 5.5 can continue to use Axis 1.2.1.
As described in PDN article How to verify and troubleshoot rules created from XSD or WSDL by Accelerators (Note: The Connector and Metadata Accelerator is now known as the Connector and Metadata Wizard), some XSD constructs are too ambiguously defined to be interpreted by the Connector and Metadata Wizard. For many of these issues, a work-around is to modify the generated Parse XML or XML stream rule yourself so that it interprets the data as you intended. For SAP connectors, however, XML objects are mapped to and from
XML Page parameters whose schema is described in data transforms, not Parse XML and XML stream rules. If the generated data transforms 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:
Axis2is specified in the Axis Version field.
XML Literal, change the Map From option from
XML Stream, and then identify the stream name in the Map From Key field.
XML Literal, change the Map To option from
XML Parse, and then identify the stream name in the Map To Key field.
Note: 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.
For more information about how to handle attachments with SOAP connectors, see Using attachments with SOAP, .NET, and HTTP connectors and services
To perform SAP connector processing asynchronously:
queuingin the Intended for field and identify the Connector Request Processor created in step 1. Leave the Response tab blank; it is not used.
You can use the following Dynamic System Settings to modify the behavior of SOAP-based Connect-SAP processing on your system:
Set to false to switch from JCIFSEngine to default NTLM engine provided by Apache HTTP component
Set the Must Understand header
Set the Addressing Version
Set the Addressing Must Understand header
For information about how to use Dynamic System Settings, see Prconfig settings and classifications.
For a simple example of a Dynamic System Setting that replaces a prconfig.xml file setting, see PDN article How to set prconfig values in a Dynamic System Setting value.
When a customer has a Connector rule for an HTTP-based protocol such as HTTP, SOAP, REST, and sometimes Email, they may point to an SSL-enabled ("https") endpoint. The service that is connected to will provide an SSL certificate in order to identify itself and secure the connection.
The Pega 7 Platform relies on the Application Server in order to "trust" the certificate that another service provided. When the Pega 7 Platform is deployed in tomcat, this usually means that the default java trust store is in use. IBM Websphere has its own trust store, controlled in the Admin Console.
When the certificate provided by a service is not in the trust store, or otherwise not trusted (for instance, it is out of date or issued to a different organization), the Pega 7 Platform cannot complete the connection and an exception such as "Peer not authenticated" results.
It is the responsibility of the customer to ensure that the application server's trust store is set up correctly.
Open topic with navigation