Skip to main content

 –

Integration-Services category

Suggest edit Updated on August 16, 2021

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

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

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

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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