Installing Constellation by using Docker
Explore the latest React-based run-time environment, which improves performance and responsiveness, and offers a revised set of user-friendly tools for authoring views and portals. You can use Docker to install the Constellation engine framework in your on-premises development environment.
- Pega Platform is hosted on Pega Cloud services.
- Pega Platform is hosted on a client-managed cloud environment.
- Constellation was installed with Pega Infinity.
- If you are an internal Pega user.
- Ensure that you have the Docker command line interface installed on your on-premises environment.
- Obtain an API key from the Pega Digital Delivery site. For more information,
see Using Pega-provided Docker images.
Note: If you cannot see the Request access key tile on the Digital Delivery site, contact Pega Support. For internal users, you can create a Service Management request to get the Docker image access privilege. - Prepare docker authentication. For more information, see Configuring Docker authentication.
- Review the process of implementing Constellation on your system. For more information, see Setting up the Constellation service in Pega Platform.
- Log in to Pega's Docker repository.
For example: docker login pega-docker.downloads.pega.com/constellationui/service:8.6.0-rc-latest - In a terminal window, pull the Constellation container by entering docker pull pega-docker.downloads.pega.com/constellationui/service:8.6.0-rc-latest.
- Start the service by entering docker run -v /<path to
folder with key certificate>:/host_folder -p 3443:3443 --name
<container name>
pega-docker.downloads.pega.com/constellationui/service:8.6.0-rc-latest
httpsKey=<SSL key> httpsCert=<SSL
certificate> urlPath=<service URL path>
port=3443 logLevel=infoThe variables have the following values:
<path to folder with key certificate> is the absolute path to the local folder that contains the HTTPS key file and the certificate file. <container name> is the name of the Docker container. <SSL key> is the name of the key file. <SSL certificate> is the name of the certificate file. <service URL path> is the URL path on which the service is deployed. The path must match the load balancer or router traffic routing. For example: docker run -p 3443:3443 -v /usr/abc/certs:/host_folder --name constellation-service pega-docker.downloads.pega.com/constellationui/service:8.6.0-rc-latest port=3443 urlPath=/c11n httpsKey=afile.key httpsCert=bfile.cert logLevel=info Note: When you deploy behind a load balancer, the load balancer usually holds the SSL certificate. In this case, you do not need to add the certificate at this point.
# sample compose file to show use of Constellation Static Service
# host_folder needs to be mapped to the host folder containing the ssl cert and key files
# docker-compose -f docker-compose.yml up / docker-compose -f docker-compose.yml down -v
version: "3.2"
services:
constellation:
image: "pega-docker.downloads.pega.com/constellationui/service:8.6.0-rc-latest"
ports:
- "3443:3443"
volumes:
- /Users/johnn/ssl-cert:/host_folder
command: httpsKey=tomcat.key httpsCert=tomcat.cer info
Previous topic Constellation service, deployment, and network configuration Next topic Configuring Docker authentication