Create Service-SAP rules in your Pega 7 Platform application when you want to allow an SAP system to connect to the Pega 7 Platform using SOAP web service protocols. SAP service rules are designed for both traditional SAP R/3 (ECC) application integration and SAP NetWeaver application integration.
An SAP service is a SOAP service package that provides one or more service methods for an external SAP application to use. Each method in the service package corresponds to an SAP service rule that identifies an activity to run and maps the incoming and outgoing data.
SAP services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured response while the calling application waits. However, you can configure SAP services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous SAP services to check for specific error conditions that you expect will be temporary — work item locks, for example — and then queue service requests for another attempt at a later time.
Use the Application Explorer to see Service SAP rules in your application. Use the Records Explorer to list all Service SAP rules that are available to you.
After all the Service SAP rules in one package are created, access the Service Package data instance again to generate a WSDL file to support client-side development.
For a comprehensive description of the development process and a sample, see the PDN document Building SOAP Services. See also:
Service SAP rules use SOAP protocols and belong to the Integration-Services category. A Service SAP rule is an instance of the Rule-Service-SAP class.
|
|
How to unit test a Service SOAP rule |
|
|
Standard Service SAP rules |
Integration-Services category