Integrating your application with external resources

Parent topic: Integrating your application with external resources

Integration-Services category

The rule types in the Integration Services category support service interfaces between Pega Platform and external systems.

About Service BPEL rules
The rule type Rule-Service-BPEL is deprecated. Use Service SOAP rules instead.
About Service COM rules
The rule type rule-service-COM is deprecated. Use Service dotNET rules instead.
Service dotNet rules
Use a package of Service dotNet rules to provide Pega Platform services to an external system based on the Microsoft .NET Framework for Web services.
About Service EJB rules
Using the Java Business Delegate pattern and the Java Session Facade pattern, the Enterprise JavaBeans® (EJB) service interface in the Pega Platform makes service rules available to external, Java-based applications as if the service rules were methods of a session bean.
Service File rules
Use Service File rules to define a package of rules for importing the contents of character-based files into your Pega Platform system. This facility can import a wide variety of record-oriented files to create or update objects in your system, including text files, Comma-Separated-Value files, and completed PDF forms.
Service HTTP rules
The HTTP integration interface in the Pega Platform supports interactions between your Pega Platform applications and other systems through the HTTP protocol.
Service Java rules
Using the Java Business Delegate pattern and the Java Session Facade pattern, the Java service interface makes service rules available to external, Java-based applications as if the service rules were public methods of a Java class.
Service JMS rules
The JMS integration interface supports interactions between your Pega Platform application and other systems through the Java Message Service (JMS). The Pega Platform supports JMS through both services and connectors. JMS services can receive (consume) messages from a JMS topic or queue and produce responses to those messages.
Service JSR94 rules
Java Specification Request 94 (JSR 94) describes an Application Programming Interface (API) for rules engines defined by the Java Community Process (JCP). The JSR 94 integration interface makes Pega Platform processing available to external Java applications through JSR 94 invocations to JSR94 service rules.
Service MQ rules
Use a package of Service MQ rules to let external systems and users access the Pega Platform data and processing using the IBM WebSphere MQ middleware messaging standard. Each Service MQ rule identifies an activity providing the service. The external system passes an MQ message to the Pega Platform, which runs the activity and then may return an output MQ message.
Service Portlet rules
Service REST rules
Representational State Transfer Protocol (REST) applications use HTTP instead of the more complex SOAP protocol to make calls between machines. The REST integration interface in the Pega Platform supports interactions with external systems through Web services.
Service SAP rules
Create Service-SAP rules in your Pega Platform application when you want to allow an SAP system to connect to the Pega 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.
Service SAPJCo rules
Using the SAP Java Connector Architecture (JCo), the SAPJCo service interface makes service rules available to external, JCo-based SAP applications as if the service rules were public methods of a Java class.
Service SOAP rules
Using Simple Object Access Protocol (SOAP) over HTTP, the SOAP integration interface in Process commander supports interactions with external systems through Web services. Use SOAP service rules when your Pega Platform applications need to act as a Web service.
About Service Type data instances
Use the Service Type form to define aspects of a custom service. Supplementing the service types supported by standard Rule-Service- rule types, a custom service can use other protocols, middleware technology, and formats.
How to call through Java-based services
How to call Pega Platform through Java-based services
How to provide test data when unit testing service rules
When unit testing service rules, you can provide some representative data for the service rule either by typing or pasting in text, or by identifying an activity that will generate the test data.

Related information:

Integrating your application with external resources

Tools for integration development tasks

Integration Services landing page

About Service Package data instances

Data mapping for SOAP and dotNet services

Lengthy service operations

Debugging listeners by using remote logging

Parent topic: Integrating your application with external resources