Question
Capgemini
IN
Last activity: 22 Dec 2021 12:09 EST
Pega Application running on 7.x if upgraded to 8.6 what are V8.6 specific challenges?
Currently Pega Application running on Pega 7.2 and we are planning to upgrade to 8.6.
The existing Pega application does not have Case management. However, sections are using Dynamic layouts.
Is there any 8.6 version specific challenge that we could face if we do Basic upgrade (Not feature upgrade) to 8.6 ?
Will the application run in 8.6 env without having Case Management in place?
Thanks in advance!
EvonSys India Pvt Ltd
IN
Hi,
Please follow detailed typical upgrade process which I outlined high level step wise step.
Review below topics before upgrade
Latest Pega infinity changes
Stay current with pega
Platform Patches
Pega Cloud maintenance and types of system updates
Two types of pega maintenances for pega cloud services
Standard
-Scheduled during an available Maintenance Window. Pega will provide advance notice of at least five (5) days prior to the work commencing.
-Infrastructure updates(database, servers, include latest security and performance updates, service enhancements and new capabilities), infrastructure updates are zero-downtime
-Standard patches, patches do not require cloned environment
-Pega platform upgrades(require cloned environment for validation)
Emergency
-Performed with immediate or near-immediate timing to remediate or avoid an incident, can not guaranty delivery advance notification like Critical Hotfix Deployment
Two phased software upgrade process
-Basic
-Feature Adoption
Hi,
Please follow detailed typical upgrade process which I outlined high level step wise step.
Review below topics before upgrade
Latest Pega infinity changes
Stay current with pega
Platform Patches
Pega Cloud maintenance and types of system updates
Two types of pega maintenances for pega cloud services
Standard
-Scheduled during an available Maintenance Window. Pega will provide advance notice of at least five (5) days prior to the work commencing.
-Infrastructure updates(database, servers, include latest security and performance updates, service enhancements and new capabilities), infrastructure updates are zero-downtime
-Standard patches, patches do not require cloned environment
-Pega platform upgrades(require cloned environment for validation)
Emergency
-Performed with immediate or near-immediate timing to remediate or avoid an incident, can not guaranty delivery advance notification like Critical Hotfix Deployment
Two phased software upgrade process
-Basic
-Feature Adoption
Upgrade checklist for Pega Infinity release 8.4.1 and earlier
Stage 1:-Preparation
-Familiar with the upgrade process
-Review the Pega standard maintenance procedures
-If applicable, run the Pega-provided pre-upgrade checker on your applications to ensure that Pega Infinity seamlessly integrates with your applications. Ex:Pre upgrade checker for Pega Marketing. Check Pre upgradation Tool
>Configure your staging environment similar to, but not necessarily the same as, your production environment, DDL for rules and data schema same as production
>Rules content is identical
>Coping production test data not allowed
>Pega Cloud you will use Deployment Manager for you standard deployment pipeline.
>Review these application development best practices to ensure that your background processing takes only several minutes to complete
>Plan for your upgrade journey as separate sprint. During the sprint, do not promote any new application changes to the production environment.
Stage2:-Basic upgrade process
Enables you to upgrade your Pega applications to the latest Pega Infinity version with minimum disruption.
upgraded clone of a specified staging environment for 30 days.
Basic upgrade process checklist
-Complete request for upgrade in my pega cloud portal, clone stage screen, create SR->My Support Portal
-Plan maintenance communication with your application users around your schedule for the upgrade
-Create new mashup codes
Stage3:-Validate Basic upgrade
Test all application in your upgraded and cloned staging environment(Automated, manual testing)
Basic upgrade validation checklist
-import test operators and access groups, test data(not production) and test cases, archived data, case attachments
-Sync selected rules from prod to upgraded and cloned environment
-If applicable run post upgrade checker
-Perform application capability for case types, User roles, Data and integrations, Background agents, End user portals, Web mashups, Any other critical functional components
-Monitor your application using PDC
-Make required changed which addressed during testing
-Create upgrade pipeline in deployment manager
-Create a product rule that contains the mashup and promote it to the production
-Notify Pega that you have completed UAT
Stage4:-Accept the Basic upgrade Prod
Perform post upgrade steps
Basic production upgrade acceptance checklist
-Pega Platform version 7.3 or earlier software, perform a limited number of pre-upgrade steps in coordination with Pega
-If your upgrading 8.2 or ealier stop all background process and restart after upgrade in contrast 8.3 or later upgrade process wait 30 min and terminate process automatically
-Perform post upgrade tasks with respect to which version to version
-Use deployment manager to promote upgrade fixes
-verify prod environment in My Pega Cloud
-Pega removed outdated rule schema in prod within 7 days of upgrade
Stage5:-Accept the Basic upgrade non Prod
Pega upgrades all non prod environments in defined maintain window
Most of the steps similar to upgrade experience of prod
The following limitations and expected behaviors during upgrade
-Downtime(before 8.4)
-user Session not persisted
-reschedule jobs before upgrade
Pega Cloud does not support modifying the production level of any environment
Pega Infinity upgrades starting from version 8.4.2 feature a near-zero-downtime process
Note: Upgrade process differs by cloud provider(Pega or other third party) and on premise/cloud
Let me know If you required any further info
Capgemini
IN
EvonSys India Pvt Ltd
IN
Hi,
from technical verification point of view there list of technical checklist provided by pega need to be verified something like below as i remember
Pega Overidden rules check with pre upgrade tool in marketplace Automatic management of run-time context for background processing at application level BIX ruleset is now included with Pega Platform Change tracking tab removed from declare expressions Personalized views in table layouts and table layout should replace with layout groupd Instances of the OAuth 2.0 provider are now deprecated. As a best practice, use the new, unified authentication profile configuration instead. Pega Web Mashup loading needs to updated any unintended validations on properties that have configured Declare Expression rules, both default and user-defined, might cause issues in an application upon saving work objects and data objects that refer to Declare Expression rules.
found similar article for 8.4 https://community.pega.com/knowledgebase/articles/pega-platform-84-changes-upgrade-impact
Set up call with Pega and they provide all post impact areas as required
Ford Motor Company
US
@sumansinha This is a very generic question. Recently, I've done system upgrades for Pega 7.19 and Pega 7.3.1 to Pega 8.x [8.4.x and 8.5.x]. Didn't see much of issues. This was a basic upgrade. Since it's basic upgrade, we were focusing on the Breakfixes.
There were couple area's we had to make changes, Case Management was not the problem.
Had to rewrite custom xml Menu's which were developed in Peg 6.x to Navigation Rules
Had to convert few section layouts to support Edge and Chrome Browsers [HTML5]
There was some dependencies on the Framework Rules, those created some problem with date time conversion.
I suggest to refer the Resolved issues section in community when you are troubleshooting particular issue.
https://community.pega.com/knowledgebase/products/platform/resolved-issues
Best Wishes.
Updated: 7 Sep 2021 11:42 EDT
Tech Mahindra Ltd
CA
@SUMAN_GUMUDAVELLY Hi Suman, we have a similar requirement where in - we need to upgrade
from On-Premise to On-Premise | App server - Web logic Proprietary information hidden | DB - Oracle Proprietary information hidden | From Pega 7.1.9 to Pega 8.6 ?
Wondering if there is any specific document/approach you have followed and any reference of those would be of great help :)
And which of the below options did you follow ?
Option 1 : Existing Pega 7.1.9 --> upgrade tools/scripts --> upgrade to Pega 8.6 and run any post upgrade steps ? Option 2 : Take fresh Pega 8.6 --> Migrate RAPs , etc other rules from Pega 7.1.9 to Pega 8.1.6 --> run any post upgrade steps ?
Ford Motor Company
US
I've scrambled and prepared a deck for you, please see attached. This document will explain the Upgrade Approach we followed for upgrading an Env from Pega 7.1.9 to Pega 8.5.x, essentially, we followed:
"Option 1 : Existing Pega 7.1.9 --> upgrade tools/scripts --> upgrade to Pega 8.6 and run any post upgrade steps ? "
I draw some high level pictures to upgrade a DEV Environment. Once the Upgraded Dev Environment is Ready, we used Pega provided Migrate Tools to migrate the Pega 8.x Rule Schema from Upgraded DEV and did an inplace upgrade for Data Schema to make a QA or an higher environment.
Review the attached PPT and let me know if you have any questions.
Tech Mahindra Ltd
CA
@SUMAN_GUMUDAVELLY This really helps. Thanks much Suman. Few basic questions 1. In order to upgrade Dev , did you follow upgrade guide of Pega 8.5 and in-place or out -of place upgrade ?
2. Single migration or double migration ?
3. Any specific docs you followed for Pega provided Migrate Tools to migrate the Pega 8.x Rule Schema from Upgraded DEV
4. Any specific docs you followed for inplace upgrade for Data Schema to make a QA or an higher environment ?
Thank you once again.
Updated: 8 Sep 2021 1:44 EDT
Ford Motor Company
US
1. In order to upgrade Dev , did you follow upgrade guide of Pega 8.5 and in-place or out -of place upgrade ?
- We did followed Pega's Upgrade Guide for the technology stack we have [MS SQL with WebSphere]
- In Place Upgrade [ PROD DB Copied to a new DB Server as illustrated in the Picture]
2. Single migration or double migration ?
- DEV is a In Place Upgrade, so there is no Migration
- From QA onwards, it's Double Migration
3. Any specific docs you followed for Pega provided Migrate Tools to migrate the Pega 8.x Rule Schema from Upgraded DEV
- I didn't follow any other documentation other than Pega provided Upgrade guides
4. Any specific docs you followed for inplace upgrade for Data Schema to make a QA or an higher environment ?
- In QA and few other Non PROD Environments, we actually replaced entire database with DEV DB Copy, where we didnt have need to keep the test data.
- Where as Pre-PRODUCTION and PROD, we followed the Migration scripts provided by Pega for Rules Schema Changes, while doing a In place upgrade for data schema.
Updated: 6 Oct 2021 4:01 EDT
TCS
IN
Hi Suman,
I was looking for details on 8.6 upgrade and stumbled upon this post. I had a couple of queries on the upgrade process (from 7.2 to 8.6). I'm planning for upgrade via IUA and have created new rules and data schema.
1. Is migrating the structure from old to new schema required or will be taken care by IUA?
2. Should I login with PegaRULES:HighAvailabilityAdministrator role and enabling System as High Availability before upgrade?
3. In order to leverage capabilities of latest version like Customer Decision Hub, Automation Testing, should I put in a separate request?
Thanks in advance.
Ford Motor Company
US
@AparnaGopakumar Please see my responses below.
1. Is migrating the structure from old to new schema required or will be taken care by IUA? --> No need to create the Structure [if you wish to do so], By ensuring Not to check the box for bypassing the schema generation.
2. Should I login with PegaRULES:HighAvailabilityAdministrator role and enabling System as High Availability before upgrade?
Never got a chance to work on High Availability :(
3. In order to leverage capabilities of latest version like Customer Decision Hub, Automation Testing, should I put in a separate request?
CDH is a separate product that you need to install in Pega 8.x , but Automated Testing is Part of Pega's Quality Dashboard, you dont have to do any additional installation. However, if you wish to integrate with Third Party tools like selenium or Pega's own Pega Test Automation Kit, you can download them from Market Place and install them.
Pega Test Automation Kit: https://community.pega.com/marketplace/components/pega-test-automation-kit
Pega Selenium Integration: https://community.pega.com/marketplace/components/selenium-starter-kit
Updated: 6 Oct 2021 4:55 EDT
TCS
IN
Thanks for your quick response Suman!
I wanted a bit more information on point 1.
When I ran the IUA with the new rules and data schema it resulted in error - No Pega version found on these schemas. Which was strange so I attempted with the old schemas (this is new db and env just for upgrade purpose). It resulted in ERROR: relation "sqlj.jar_repository" does not exist. On analysis I find conflicting options - some say to place the file in repository, other say to bypass the UDF generation by setting setupDatabase.properties. Any idea which is a better approach given that the upgrade schemas are the old and existing ones.
Ford Motor Company
US
Can you please send me screenshot of the IUA via Direct Message [DM] . jar_repository is not a valid extension. Typically we copy the driver in our local and refer the folder path along with the driver.
I would suggest to sticking to UDF Generation by the tool rather than running manually its so much unnecessary wrok if you do manually,
Process360
SA
Hi Suman, Recently we have upgraded from 7.2.2 to 8.6; After the upgrade there are few aspects I am looking for more info.
1. Regarding Case ID generation -We have used database sequence generator; Is there any specific example i can follow on how to take a record from pc_data_uniqueid tabe for 1 case, find out the pylastreserveID and then update it to max+1... can you please help me.
2. We are not able to open workobjects form when we are trying to open it. I am getting BOLD ERROR when trying to open it - anything thoughts.
3. Images are missing even though they are in webweb folder - They are not reflecting on screen after the upgrade.
Please advise when you get a chance.
Ford Motor Company
US
@SrikarY89 Please see my answers.
1. Regarding Case ID generation -We have used database sequence generator; Is there any specific example i can follow on how to take a record from pc_data_uniqueid tabe for 1 case, find out the pylastreserveID and then update it to max+1... can you please help me.
==> If you are using a different database after the upgrade, yes, it does make sense to refer the [pyLastReservedID] for the [pyPrefix] for that row. pyLastReservedID represents the last case ID used for that case type in the source environment.
2. We are not able to open workobjects form when we are trying to open it. I am getting BOLD ERROR when trying to open it - anything thoughts.
==> Without looking at the logs or error message, it would be hard to come for a conclusion. However, couple thoughts:
- Ensure the URL you are using doesn't have anything after /prweb
- Delete the Browser Cache
- Check if any local cache's corrupted
- Most importantly look at PDC/AES/Pega Logs [ALERT and PegaRULES]
3. Images are missing even though they are in webweb folder - They are not reflecting on screen after the upgrade.
==> Same answer as above
Process360
SA
@SUMAN_GUMUDAVELLY Thank you Suman, Will check and get back.