Skip to main content


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

Defining highly available integration services

Updated on July 8, 2022

Deployments of Pega Platform integration services that are part of highly available production environments require additional configuration that might not be necessary in development.

Be mindful of high availability when you deploy listeners, service packages, service request processors, and service rules.

  • Listeners

    Listeners are background processes in the Pega Platform that wait for inbound network requests or messages. In a high availability environment, listeners should be distributed across hosts and Pega Platform servers by using node types to assure redundancy.

  • Service packages

    A service package is a Pega Platform data instance for a collection of services. It controls access to the listeners for the services with defined Pega Platform Access Groups. The service package also defines the service processing mode (stateless or stateful) and pooling options for stateless unauthenticated services.

  • Service request processors

    Service request processors are also Pega Platform data instances that provide configuration options for asynchronous processing.

  • Service rules

    The processing of service requests is handled by service rules as appropriate for each service type.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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