Pega continuously makes new features available to you so that you can incrementally and rapidly deliver value to your customers using the latest capabilities, feature enhancements, performance improvements, and security fixes.
The information provided in this document is for planning purposes and is subject to change at the discretion of Pegasystems Inc.
To accelerate the time-to-value and pave the path to your digital transformation, the update process helps you stay current in a predictable and consistent manner from release to release. Pega is committed to the highest software update quality so that you can experience as little downtime during update as possible. After you complete an update to Pega Infinity, you should always consider updating to the latest software to ensure that you can take advantage of the latest features and capabilities to maximize your investment in Pega.
To get started right away with a checklist of responsibilities to complete an update from Pega Infinity release 8.4.2 or later to release 8.5.1 or later for application servers and databases other than Tomcat and PostgreSQL, see On-premises update checklist for Pega Infinity release 8.4.2 and later for other application servers and databases. To prepare for the update process, review the following articles:
- For details about the latest Pega Infinity changes with which you can maximize your Pega software investment, see What's New in Pega Technology.
- For general details about how Pega keeps you current, see Updating and patching Pega Infinity.
Planning considerations for updates of Pega Infinity release 8.4.2 on application servers and databases other than Tomcat and PostgreSQL
Pega encourages you to assess and decide on when you adopt new features and functionality available in Pega Infinity. Pega is committed to the highest software update quality so that you experience an automated update with less downtime and fewer post-update steps than earlier versions of Pega Platform. Pega uses the following feature development standards to ensure it seamlessly integrates with applications that are guardrail compliant:
- Backwards compatibility for Pega Platform and Pega industry application software changes, which ensures trouble-free software updates.
- Fewer required post-update steps in most Pega industry applications. The update process includes a post-update, feature adoption phase for completing mandatory and optional post-update steps, recommended configuration changes, verification steps, or for adopting new features in your application.
- Identification of new features or performance improvements with a potential for update impact. To see changes with known update impact, see Pega Platform changes with update impact.
- Development of analytical tools with which you can assess the update impact
on your application to ensure that it is ready for an update. Examples
- Pre-Upgrade Check for Pega Customer Decision Hub
- Pega Customer Service Update Checker
- Pega Sales Automation Update Checker
For Pega Platform, Pega provides a pre-update tool that identifies the rules that you have customized in your application to understand the impact of the update; your 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.
For any software update to Pega Infinity, Pega uses a two-phased software update process so that you can adopt the latest performance and security improvements without affecting your existing Pega applications. This two-phased life-cycle approach provides flexibility for you to adpot the latest features and enhancements in the latest version into your Pega application:
- Basic update
- Updates Pega Infinity rules to the latest version, with minimum disruption. Typically, the Basic update phase takes you about four weeks to complete. In this phase, you make any necessary application changes to ensure functional correctness and update compliance. You can adopt the latest performance and security improvements and can test existing functionality using you current testing processes.
- Feature adoption
- After the Basic update is complete, use this phase to take advantage of the latest Pega Infinity and application features using your standard DevOps process.
This phased approach requires that you 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 following your Pega Infinity update. This standardization includes the following structure:
- You configure your staging environment similar 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.
- There is appropriate test data in the staging environment; copying production data is not allowed.
- You must already use a 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. 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.
The on-premises experience for updating Pega Infinity release 8.4.2 or later on application servers and databases other than Tomcat and PostgreSQL
You clone the database of your staging environment according to your database vendor's tooling. On this cloned environment, you can test using existing test suites, which minimizes efforts and shortens the update life cycle environments.
The standard software update process integrates the latest Pega automation technology to support seamless adoption of the latest Pega Infinity features and improvements across environments using your development pipeline.
The following limitations and expected behaviors within your environments apply but are not limited to a your software update experience:
- During the environment updates, you experience environment downtime, during which time you cannot access Pega applications.
- Any data saved to the database before the update process is never lost during the update process.
- User sessions are not persisted: active users might be logged off during the environment restart.
- Reschedule any upcoming activities, such as job schedulers, before you initiate the update process.
- If you update from Pega Platform version 8.2 or earlier, stop all background processes you initiate the update process and restart the stopped processes after you complete the update process.
- If you update from Pega Platform version 8.3 or later, the update process waits up to 30 minutes for any activity that is running in the background to finish its work; if the activity is not finished after 30 minutes, the background process is terminated. Review these application development best practices to ensure that your background processing takes only several minutes to complete:
In addition, you must migrate your existing mashups; beginning in Pega Platform 8.5.1, Pega Web Mashups include a channel ID in the mashup code for validation with your mashup server. Create new mashup code on your updated, cloned environment running release 8.5.1 so the mashup rule form includes a Mashup channelID that is automatically included in your application testing rule in your update pipeline. To create a new mashup, see Creating a mashup. Be sure to update existing website configurations with the new mashup code.
Details of the new on-premises software update process for Pega 8.4.2 and later for application servers and databases other than Tomcat and PostgreSQL
The software update process phases are broken into the following discrete steps:
- You clone the database of your staging environment and update this cloned
environment to the latest Pega Platform and industry
application software. Unless you need them for testing, it is not recommended
that you clone the following artifacts:
- Decision data store (DDS) datasets
- Kafka data sets
- Archived data, case attachments, and SFTP data
- In Deployment Manager, you migrate rules from the updated cloned, staging environment to the production environment for each application using an update pipeline. 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 details, see Configuring update pipelines in Deployment Manager.
- If required, you select rules to sync from the production environment to the updated, cloned staging environment. For details, see Syncing rules between the production environment and the updated, cloned, staging environment in Deployment Manager.
- You perform application compatibility testing and validation on the cloned staging environment, during which time they can make any changes or fixes necessary to verify expected application functionality while using the new version of Pega Infinity. Within this period, you complete your regression testing and then indicate your readiness to consent to update your production environment. During this testing phase, you can complete your regression testing on the updated, cloned staging environment. Helpful resources include:
- You perform any of the following steps that apply on the production
- Perform a limited number of pre-update steps. For more information, see the applicable update guides.
- Reschedule any upcoming activities, such as job schedulers, before you initiate the update process.
- If you update from Pega Platform version 8.2 or earlier, stop all background processes before you initiate the update process and restart the stopped processes you complete the update process.
- If you update from Pega Platform version 8.3 or later, the update process waits up to 30 minutes for any activity that is running in the background to finish its work; if the activity is not finished after 30 minutes, the background process is terminated.
- You update your respective production environments during your standard maintenance window.
- You perform any of required steps applicable to Pega Platform
and to your applications on the production environment as detailed in the
appropriate update guides.
After completing required post-update steps in your application, you use Deployment Manager to promote the update fixes identified during step 3. For details, see Migrating update fixes to production.
- You update all non-production environments during your defined maintenance window after completing the update on the production environment.
- You perform any post-update tasks on the non-production environments as outlined in Step 6.
- You import any update fixes discovered as part of step 3 to all non-production environments. It is recommended to use Deployment Manager to promote these changes. To promote these changes using Deployment Manager, review Migrating application update changes to non-production environments.
- You remove the outdated rule schema in each updated environment after completing the update.
- You delete the updated, cloned staging environment after completing all of the live environment updates.
At this point, the Basic update phase is complete and the Feature Adoption phase begins. Use the second phase for completing optional post-update, verification steps and recommended configuration changes, or adopting new features in your application using your standard DevOps process.