Frequently asked questions regarding the application structure and configuration of Deployment Manager.
Can I use Deployment Manager as a built-on application?
You should avoid using Deployment Manager as a built-on application. Log onto Deployment Manager portal directly with DMReleaseAdmin operator. See Installing or upgrading Deployment Manager 5.x for a minimal set of step by step instructions to start using Deployment Manager.
How should I configure an application product rule?
Our recommendation is to always package the entire application for multiple reasons.
- Introduce failure tolerance- Creating an entire application package that needs to be deployed to production for each deployment, ensures that if any of your environments get corrupted it is less difficult to reconstruct it. Having the entire application packaged from the last successful run of the pipeline, means not having to figure out what was validated (tested) and approved for deployment.
- Platform handles delta deployments- The Pega platform already handles delta deployments automatically and the exact rules and data that were imported is documented and captured in the log.
- The initial first time deployment might be large I the application does not exist on the target system, however subsequent deployments will be quick as only the changes rules and data will be imported as explained above.
- The Platform import process and subsequently Deployment Manager leveraging the platform import have been tested for multi-gigabyte application packages and it does work but it will take a proportionally long time to deploy.
- • Simpler and easier packaging process for developers – by maintaining a consistent product rule, it is significantly easier for application developers as they do not have to keep creating a product rule for every single deployment which can be error prone. This is particularly true if they follow the recommended best practices for a development workflow using Deployment Manager.
How do I prevent test cases from being migrated to production?
Deployment Manager provides you an ability to specify a test application and product rule for the test artifacts. This artifact is deployed independently of your application artifact in the same pipeline, up until the stage chosen by you in the pipeline. For example, you can choose your tests to deploy only on Quality Assurance and not on Staging and Production stages in a pipeline.
Starting in version 5.x, deploy task offers a checkbox Deploy test artifact? that must be selected if the test artifacts shall be deployed on the selected stage.
To understand how to manage test cases seamlessly through Deployment Manager pipelines, see Configuring an application.
How do I deploy a new application?
The getting started guide for Deployment Manager assumes that you already have an application deployed to each of your environments, and it needs to be updated to be built-on PegaDevOpsFoundation. However, if you are deploying a new application it is not necessary to manually import it to each environment. Deployment Manager will handle migrating the new application. We call this a "First time deployment".
If your application is built-on PegaDevOpsFoundation in the development/SoR environment, and the application's access group does not exist in the target candidate environment the application RAP will be deployed, and the pipeline will progress successfully.
If the application and access group already exist on the candidate environment, but the application is not built on PegaDevOpsFoundation then you can expect to see an error during deployment.
Also, when creating a new application make sure you are familiar with the recommended structure. See Configuring an application for more information.