On-premises update checklist for Pega Infinity release 8.4.2 and later for other application servers and databases
This checklist details the update requirements and actions that are required during an update of all your environments that are running Pega Infinity release 8.4.2 or later on application servers and databases other than Tomcat and PostgreSQL. Use this checklist to plan and complete your update process steps and stages.
Stage 1: Prepare for the update
During the Pega Infinity update process, you perform and manage all the update tasks as described in this checklist.
Update preparation checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | Become familiar with the update process by reviewing On-premises update process for Pega Infinity release 8.4.2 and later for other application servers and databases. | |
| ⬜ | Learn about the benefits of keeping current with Pega, read about the latest features, and learn about any features or processes that Pega has identified with update impact, by exploring: | |
| ⬜ | If applicable, run the Pega-provided pre-update checker on your applications to ensure that
Pega Infinity seamlessly integrates with your
applications. Examples of update checkers include:
For Pega Platform, Pega provides a pre-update checker that identifies the rules that you have customized in your application to understand the impact of the update; you are expected to use the results to retrofit these rules after the update. As a best practice, do not overwrite or customize Pega rules. For more information, see Pega Update Tools. | |
| ⬜ | Maintain a standard, consistent DevOps approach so that you can
assess the effect of the latest Pega Platform and
Pega industry application
capabilities and plan your new feature adoption strategy across your
environments after you update to Pega Infinity.
This standardization includes the following structure:
| |
| ⬜ | Review these application development best practices to ensure that your background processing takes only several minutes to complete: | |
| ⬜ | Plan for your update journey in an upcoming sprint. Updates of your production environment are typically verified and completed within two weeks of initiation. During the sprint, do not promote any new application changes to the production environment. |
Stage 2: Start the Basic update process
The Basic update process enables you to update your Pega industry applications to the latest Pega Infinity version with minimum disruption.In this phase you initiate the update process by cloning a staging environment according to your database vendor's tooling. You prepare this environment for update testing using test data, test cases, and any operators as needed.
Basic update process checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | If necessary, plan a maintenance communication with your application users around your schedule for the update. | |
| ⬜ | Clone the database of your staging environment according to your database vendor's tooling. | |
| ⬜ | Update your staging environment. For details, see the appropriate update guides for your industry applications and for Pega Platform. | |
| ⬜ | If you have existing web mashups, create new mashup code on the updated, cloned staging environment. For more information about migrating mashups, see Migrating existing mashups. |
Stage 3: Validate the Basic update by using application testing
In this stage, you test all applications in your updated, cloned staging environment. You should also plan to make any critical changes if recommended as part of the update impact assessment that you complete in Stage 1: Prepare for the update.This phase does not include adopting features of the new version of the keyref="companyNameShort"/> Infinity platform which are done later, during the Feature Adoption phase of the update process.
Basic update validation checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | For each application, import the following applicable testing
assets into the updated, cloned staging environment:
The clone maintains your application and data from the staging environment. Unless you need them for testing, you do not need to clone the following artifacts:
While you must ensure that appropriate test data exists in the staging environment, copying production data is not allowed. | |
| ⬜ | For each application, sync selected rules from the production environment to the updated, cloned staging environment. For more information, see Syncing rules between the production environment and the updated, cloned, staging environment in Deployment Manager. | |
| ⬜ | If applicable, run the Pega-provided Customer Service post-update checker on your applications to ensure seamless integration. For more information, see Pega Customer Service Update Checker and "Checking for rule overrides in Pega Customer Service" in Pega Customer Service and Pega Sales Automation Update Guide. | |
| ⬜ | For each application, perform application compatibility testing
and validation on the cloned, updated staging environment. Ensure
you have test coverage for the following Pega capabilities and configurations:
Helpful resources include Testing updates. | |
| ⬜ | For each application, make required changes to address issues
identified during the testing. The required rules and data changes
include addressing critical security-related enhancements, as well
as problematic configurations identified by the pre-update
assessment tools in Stage 1: Prepare for the
update. In later stages of the update process, you
promote these changes accordingly, depending on the stage. | |
| ⬜ | Create an update pipeline in Deployment Manager to migrate rules from the
updated cloned, staging environment to the production environment
for each application. The update pipeline includes two product
rules that contain any update fixes and confidence testing assets
along with all required data instances to test the application.
For more information about configuring update pipelines, see Configuring update pipelines in Deployment Manager. | |
| ⬜ | Optionally, if you are migrating existing mashups and want to access them during the update, create a product rule that contains the mashup and promote it to the production environment. For details, see Migrating existing mashups. | |
| ⬜ | If you are migrating existing web mashups, add them to the application product rule in the update pipeline and promote the product rule to production. For details, see Migrating existing mashups. |
Stage 4: Perform a Basic update of your production environment
In this phase, you update your production environment after you prepare the environment for the update. After the update, you must perform any required post-update steps that your application requires.Production environment basic update checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | Before the update, perform the following steps that apply on the
production environment:
| |
| ⬜ | Update your production environment. For more information, see the appropriate update guide for your industry applications and for Pega Platform. | |
| ⬜ | After the update, perform any required steps applicable to your application. For details, see the appropriate update guide for your industry applications and for Pega Platform. | |
| ⬜ | Import any fixes that you identified during Stage 3:
Validate the Basic update using application testing of
your update pipeline in Deployment Manager. For more information, see Migrating update fixes to production. |
Stage 5: Perform a Basic update of non-production environments
During this stage, you update all non-production environments during your defined maintenance window after completing the update on the production environment.Non-production basic update checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | Perform any pre-update and post-update tasks on the non-production environments as outlined in Stage 3. | |
| ⬜ | Update each non-production environment. For more information, see the appropriate update guide for your industry applications and for Pega Platform. | |
| ⬜ | After every non-production environment update, for each
application, import any required rules and data changes discovered
during Stage 3: Validate the Basic update using application
testing, during application compatibility testing and
validation from your updated, cloned staging environment. To
promote these changes by using Deployment Manager, review Migrating application update changes to non-production environments. | |
| ⬜ | Log in to each updated, non-production environment and verify that your application is working as expected. |
Stage 6: Maintain Feature Adoption in your environments
At this point, the Basic update phase is complete and the Feature Adoption phase begins. Use this phase as part of your standard application development life cycle with which you complete optional post-update steps, verification steps and recommended configuration changes, or adopting new features in your application using the standard DevOps process.Feature Adoption checklist
| Stakeholder | Required actions with each stage | Date completed |
| ⬜ | Complete post-update tasks as detailed in the update guides for your industry application and for Pega Platform. | |
| ⬜ | In your development environment, enable and integrate the new
features of the latest release that you identified during
Stage 1: Prepare for the update of the update
process into each of your relevant applications.Use your existing deployment pipeline with a minimum number of development, staging, and production environments and use the pipeline to promote the latest application functionality to your production environments. For details, see Configuring pipelines and deploying applications in Deployment Manager. |
Previous topic On-premises update process for Pega Infinity release 8.4.2 and later for other application servers and databases Next topic On-premises update process for Pega Infinity release 8.4.1 and earlier