Skip to main content

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

Messaging service for Pega Constellation

Updated on October 21, 2022

The Pega Constellation messaging service intermediates between the case engine and UI components in browsers that act as information publishers and subscribers. The new service accepts HTTP-based information and forwards it to WebSocket subscribers.

A third-party integration service can also act as a publisher.

The following diagram represents the messaging service architecture.

Messaging service architecture
The service is exposed to the browsers and the publishers through a network IP address

An IP address exposes the messaging service to browsers and publishers. The URL for the service is passed to the browser during the initial portal load from the dynamic system settings in Pega Platform. The publishers and subscribers use the same IP address for HTTP POST calls and WSS connections.

For more information about installing and configuring the service, see the Constellation messaging installation site with advanced developer documentation.

For more information about the Messaging Service, see Working with Messaging Service.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us