Getting to know the systems and components
You should understand some of the high-level components necessary for a successful Deployment Manager implementation before installation. This article provides descriptions of each component you need.
The following systems are required for implementation:
- Orchestrates all the elements of a deployment pipeline from initial branch merge to production deployment.
- Exposes the pipeline modeling experience for users to design their deployment pipelines.
- Resides on a dedicated Pega server which is configured to interact with each of the candidate system.
- Candidate environments
- Each Pega environment managed by Deployment Manager is referred to as a Candidate system.
- Candidate systems execute most deployment tasks at the direction of the orchestrator.
- Among the candidate environments, development uses special responsibilities as it is the environment on which merges are performed, and all application packages are generated.
- The development environment is referred to as the System of Record (SoR) to highlight these responsibilities.
- Candidate systems use repositories to store application artifacts as they are being promoted between environments.
- The deployment process versions application artifacts automatically.
- A separate repository definition can store artifacts that a CICD pipeline determines “Production Ready”.
Deployment Manager is made up of two rule components
- The PegaDeploymentManagerApplication installed 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 Studio.
- The PegaDevOpsFoundation application is installed on each candidate environment. Each managed application must include PegaDevOpsFoundation as a built-on application. This component facilitates deployments and adds 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.