Migrating application changes
With minimal disruption, you can safely migrate your application changes throughout the application development life cycle, from development to deployment on your staging and production environments. In the event of any issues, you can roll back the deployment and restore your system to a state that was previously known to be working.
The process that you use to release changes to your application is different depending on the types of changes that you are making. This topic describes the Standard Release process that you can use to deploy changes to rules, data instances, and dynamic system settings. The Standard Release process is a self-service way to deploy changes without downtime. Other methods for releasing changes to your application are not covered in this article. For more information, see Application release changes, types, and processes.
This Standard Release process applies to both on-premises and Pega Cloud Services environments. As a Pega Cloud Services customer, if you use this self-service process to release changes to your application, you are responsible for those changes. For more information, see Change management in Pega Cloud Services and Service level agreement for Pega Cloud Services.
The Standard Release process includes the following steps and is scalable to the number and types of environments that you have:
- Package the release on your shared development environment. For more information, see Packaging a release on your development environment.
- Deploy the changes to your staging or production environment. For more information, see Deploying application changes to your staging or production environment.
- Understanding application migration requirements
Before you migrate your application, both your environment and application must meet certain requirements. For example, you must be able to download a RAP archive to a file system location with the required available space.
- Understanding application migration scenarios
The Standard Release migration process supports the following scenarios:
Previous topic Using the RuleSet Stack Landing Page Lock and Roll features for managing ruleset versions Next topic Understanding application migration requirements