Skip to main content

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

How do the Constellation SDKs work?

Updated on October 10, 2022

The following figure shows the interplay between the Pega Infinity server and the SDK content server:

Flow diagram showing the flow of information between Constellation and the SDK
Constellation client architecture

The user session obtains static content from the SDK content server when the user initiates contact with a Pega embedded UI or portal application implemented with the SDK. This includes the ConstellationJS Engine and the SDK bridge and components. After loading the static content from the SDK content server, the web application communicates with the configured Infinity server through the following means:

  • DX APIs for authentication
  • SPA portal load
  • REST API calls

The ConstellationJS Engine, loaded from the SDK content server, uses the public Constellation JS APIs to coordinate communication between the web application and the Infinity server. 

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