Learn about the Messaging Service and its various use cases.
The Messaging Service serves as a bridge between information publishers and subscribers. It forwards the published information to WebSocket subscribers.
The publishers are typically third party integration services or the Infinity Case engine, while the subscribers are UI components in browsers running Constellation UI.
The Messaging Service is exposed to browsers and publishers through a network IP address. This IP address is passed to the browser during the initial portal load from a Dynamic System Setting (DSS) in Infinity. This IP address is used by publishers for HTTP POST calls and by subscribers for Web Socket Secure (WSS) connections.
In a client/browser, the Messaging Service is accessed through the PCore getMessagingServiceManager() API.
- Architectural overview
Learn about the components of the Messaging Service and how they are organized.
- Message schema
Learn about the standard formats for messages to be sent between the Messaging Service and a browser.
- Client-side subscriptions
Learn how a client can use Messaging Service to subscribe to WebSocket events.
- Server-side publishing
Learn how events are published to subscribed clients.