Discussion

4
Replies
1166
Views
tallr1 Member since 2013 9 posts
PEGA
Posted: February 7, 2016
Last activity: April 6, 2018
Closed

Enterprise Application Upgrade approach – DEV to UAT, PROD - what tables to copy?

Hello Upgrade experts,

We are planning to upgrade from Pega 7.1.4 to Pega 7.1.9 or later. As part of this, we would also upgrade CPM, CPMFS Strategic Applications. We use IAC extensively and also have BIX installed.

Question 1: The page 4 of the document "Pega719_UpgradeGuide.pdf", discusses "Typical Enterprise Application upgrade process", and talks about tables and database object to copy from DEV to UAT, as pasted below. Can someone please list the tables and database objects that need to be copied from DEV to UAT?

---------------------------------------------------------------------------------------------------------------------------

In this example, a project is initiated to upgrade and enhance an existing PRPC enterprise application to
run on Pega 7.1.9. The project requires three environments, each of which with slightly different sizing
and uptime requirements:

l Development— a small instance targeted at the development team for rule development and unit
testing, with small amounts of transaction data

l User Acceptance Testing (UAT) — a moderate instance which contains a representative sample of
production-like data where system and performance testing can be completed to certify the
application readiness for production

l Production — the full-size deployment that manages the production user population and production
transaction volumes.

By employing a different upgrade approach for each type of system, you minimize the critical production
outage window and reduce overall migration risk by ensuring that only tested and proven rules are
moved into production. The basic process design is:

1. Prior to upgrade, ensure that the Development system reflects Production.
2. Upgrade the Development system using the standard in-place upgrade process.
3. Conduct unit testing in Development and correct any issues. Exploit new capabilities that will need
to roll into Production.
4. Set up the UAT system as a copy of the Production rulebase with a suitable subset of the
transaction data.
5. When development is complete, upgrade the UAT system:
a. Replace the rulebase with the one from Development; copy the appropriate tables and other
database objects.

b. Replace the base engine classes with those from Development.
6. Test the system and verify that the UAT system executes correctly. Fix any problems in
Development and re-upgrade UAT periodically using the same table-copy technique. After testing,
the Development and UAT contains identical rulebases.
7. Complete the Production upgrade using the using the same table-copy to replace the PRPC base
engine classes.

At this point, Development becomes the Production Support system, and you can create a new
development system to commence build-out of new capabilities for subsequent release.

--------------------------------------------------------------------------------------------------------------------

Question 2: Will copying tables from DEV to UAT, override the Customer Applications rulesets in UAT?

Say DEV has CustomApp:01-05-06 after cloning from PROD. But UAT has CustomApp:01-05-07, which is yet to be promoted from UAT to PROD. Is the CustomApp:01-05-07 ruleset version in UAT overridden after copying tables and database objects as per above suggested approach? If so, what is the best way to handle this scenario, meaning retaining CustomApp:01-05-07 in UAT? (Hope exporting CustomApp:01-05-07 rules as JAR file is sufficient, to be imported after table copy)

Many thanks for your time and response.

Thanks

Raghu

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn