Skip to main content

On-premises update checklist for Pega Infinity release 8.4.2 and later for Tomcat and PostgreSQL

Suggest edit
Updated on April 12, 2022

This checklist details the minor update requirements and actions that are needed during an update of all of your on-premises environments with Pega Infinity release 8.4.2 and later to Pega Infinity release 8.5.1 or later for 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 the following checklist:

Update preparation checklist

StakeholderRequired actions with each stageDate completed
To familiarize yourself with the process, review On-premises update process for Pega Infinity release 8.4.2 and later for Tomcat and PostgreSQL.

To 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, explore the following topics:
If applicable, run the Pega-provided pre-update checker on your applications to ensure that Pega Infinity seamlessly integrates with your applications. Examples of pre-update checkers include:

For Pega Platform, Pega provides a pre-update checker that identifies the rules that you have customized in your application, to help you understand the impact of the update. You should then 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 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:
  • Configure your staging environment similarly to, but not necessarily the same as, your production environment. This requires that:
    • The rules and data schema Data Definition Language (DDL) are the same as the production rules and data schema DDL.
    • The rules content is identical except for configurations specific to production environments.
    • The staging environment contains the appropriate test data. Copying production data is not allowed.
  • You must already have a deployment pipeline configured with a minimum number of development, staging, and production environments. You use the pipeline to promote the latest application functionality to your production environments. You are encouraged to use Deployment Manager for your standard deployment pipeline, although Pega supports the use of third-party automation services for your application change adoption pipeline. For details, see Using Deployment Manager for model-driven DevOps.

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. 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 clone the database of your staging environment based on 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

StakeholderRequired actions with each stageDate completed
If necessary, plan 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.
Perform pre-update tasks on your cloned, staging environment. For more information about Pega Platform, see Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL. For more information about industry applications, see the appropriate application update guide.
Update your cloned, staging environment. For more information, see Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL.

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 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 any were 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 Pega Infinity that are done later, during the Feature Adoption phase of the update process.

Basic update validation checklist

StakeholderRequired actions with each stageDate completed
For each application, import the following applicable testing assets into the updated, cloned staging environment:
  • Test operators and access groups
  • Test data and test cases

The clone maintains your application and data from the staging environment. Unless you want to use the following assets for testing, you do not have to clone them:

  • Decision data store (DDS) data sets
  • Kafka data sets
  • Archived data, case attachments, and SFTP data

While you must ensure that appropriate test data exists in the staging environment, copying production data is not recommended.

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 artifacts:
  • Case types
  • User roles
  • Data and integrations
  • Background agents
  • End user portals
  • Web mashups
  • Any other critical functional components

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 during 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, as well as confidence testing assets and all data instances required 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 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.

Optionally, before the rolling restart of Pega Platform, you can promote any necessary changes from the updated staging clone to a temporary production URL for testing. You can then complete your confidence testing and communicate a Go-NoGo (accept or abandon) decision; you should only update your production environment following a go decision.

Production environment basic update checklist

StakeholderRequired actions with each stageDate completed
Update your production environment. For more information, see Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL. For more information about updating industry applications, see the appropriate update guide.
Optionally, before the rolling restart of Pega Platform, you can promote any necessary changes from the updated staging clone to a temporary production URL for testing. You can then complete your confidence testing and communicate a Go-NoGo (accept or abandon) decision; you should only update your production environment following a go decision. For more information about bringing up a temporary URL, see the Optional: accessing a temporary URL to perform Go-NoGo testing of your production environment section in Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL.
Update the DMReleaseAdmin auth profile and the DMAppAdmin operator passwords to interact with Deployment Manager and complete your Go-NoGo confidence testing. If required, you may have to re-create the profile and operator.

For each application, use Deployment Manager to start a new deployment to promote the following instances from the cloned staging environment to the temporary production environment:

  • The update fixes that you identified during Stage 3:Validate the Basic update using application testing .
  • The confidence testing assets that you created during Stage 3: Validate the Basic update using application testing.
  • Existing web mashups.

For more information, see Migrating update fixes to production.

On the temporary production URL, enable the operators that are needed for confidence testing.
Perform the application confidence testing on the temporary production URL. For details, see Understanding confidence testing.
Indicate approval for the update on production and perform a rolling restart.

For more information, see Performing a rolling restart in Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL.

After your go approval, delete the temporary production URL and update your production environment to the latest version of Pega Infinity.
After the rolling update of the production environment is complete, for each application, you use Deployment Manager to promote the update fixes that you identified during Stage 3: Validate the Basic update using application testing to the production environment. This is a required step to re-import any data instance or schema changes. For details, see Migrating update fixes to production.

Verify that your application is working as expected.
Remove the outdated rule schema in your production environment after the update.

Step 4: 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

StakeholderRequired actions with each stageDate completed
Update non-production environments. For more information about updating Pega Platform, see Near-zero downtime Update Guide for Pega Platform version 8.4.2 and later for Apache Tomcat and PostgreSQL. For more information about updating industry applications, see the appropriate update guide.
After every non-production environment update, for each application, import any required rules and data changes discovered during Stage 2, 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.
Remove the outdated rule schema in your non-production environment after completing all of the non-production environment updates.
Delete the updated, cloned staging environment.

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 adopt new features in your application using the standard DevOps process.

Feature Adoption checklist

StakeholderRequired actions with each stageDate completed
Complete post-update tasks for Pega Platform and your industry applications.

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 Tomcat and PostgreSQL
  • Next topic On-premises update process for Pega Infinity release 8.4.2 and later for other application servers and databases
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us