Get to know some of the high-level components necessary for a successful Deployment Manager implementation before installation.
You require the following systems for implementation:
The orchestrator handles all elements of a deployment pipeline, from initial branch merge to a production deployment. The orchestrator exposes the pipeline modeling experience to design pipelines, and resides on a Pega server for interaction with each of the candidate systems.
- Candidate environments
Each Pega environment managed by Deployment Manager is known as a candidate system. Candidate systems execute most deployment tasks at the direction of the orchestrator.
- Development environment
The development environment is where you generate application packages and perform merges. This may also be known as the System of Record (SoR) to highlight these responsibilities.
Candidate systems use repositories to store application artifacts as you promote them between environments. The deployment process versions artifacts automatically, and a separate repository stores production-ready artifacts.
Deployment Manager is made up of two rule components:
- The PegaDeploymentManager application on the orchestrator environment includes all rules necessary for authoring and executing Deployment Manager pipelines. Users logging into the application will log into the Deployment Manager Studio.
- The PegaDevOpsFoundation application on each candidate environment facilitates deployments, and adds the merge wizard and App Studio integration.
To get started with Deployment Manager, see Installing or upgrading Deployment Manager 5.x.
- Understanding default authentication profiles and operator IDs
When you install Deployment Manager on all the systems in your ecosystem participating in the release process, there are applications, operator IDs, and authentication profiles installed by default. Authentication profiles enable communication between the orchestration server and candidate systems.