Constellation service, deployment, and network configuration
Constellation requires a static content microservice that delivers content to the browser. This approach improves overall application performance.However, proper operation of the service requires careful configuration of network and deployment settings.
The Constellation service can be deployed either to a production environment, where it can support numerous Pega Infinity clusters, or to the desktop of a developer who is running a local installation of the Pega Infinity engine from a local browser. Both Constellation and Pega Infinity services require HTTPS.
Local deployment is the least complex deployment. The developer works with a local Pega Infinity environment on a desktop computer, and installs a local Constellation service. The developer launches the browser from the same computer that hosts Constellation.
The following table lists the default URLs for a local deployment:
In any other deployment, the browser, the Pega Infinity server, and the Constellation service are not on the local computer.
The following table lists the URLs for non-local deployments:
Domain and path to the Constellation service
Domain and path to the Pega Infinity