Skip to main content


Defining highly available integration services

Suggest edit Updated on August 25, 2021

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.

  • Previous topic Setting up the components of highly available environments
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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us