Question

1
Replies
153
Views
SimonF37 Member since 2013 6 posts
Sopra Steria Group
Posted: 4 years ago
Last activity: 4 years ago
Closed

What is the best approach to upgrade AES from 3.5 to 7.1.7

Hi Everyone,

I have some questions about upgrading AES version from AES 3.5 (PRPC 6.3SP1) to AES 7.1.7 (PRPC 7.1.9). In fact, I want to know what is the best way to perform this upgrade, considering the following requirements :

1.    Because we are upgrading from a 6.3SP1 version to a 7.1.9 version of PRPC, PRPC database schemas have changed (single schema to split schemas)

2.    Our customer will bring up new JVMs for the new Pega 7 nodes, nodes existing in Pega 6 will not be used anymore

 

I identify the two following possible options :

 

Option 1 :
-    Bring up a new database (with split schema) and perform a fresh install of PRPC 7.1.9.
-    With the PDF document “Autonomic Event Services (AES) Enterprise Edition Installation and Upgrade Guide 7.1.7” :
     o    Install AES 7.1.7 by following the “Installing AES” section
     o    Perform actions described in the “Configuring AES” section if necessary
-    Because new Pega 7 nodes will be created (requirement #2 above), with the PDF document “Autonomic Event Services (AES) Enterprise Edition Monitored Node Configuration Guide 7.1.7”, follow the “Configuring the AES nodes” section by performing the following steps :
     o    Step 4: “Create a Unique System Name and Update All Nodes”
     o    Step 7: “Update landing page to Send Alerts to AES”
     o    Step 10: “Update the Data-Admin-Nodes description”

 

Option 2 :
-    Use the existing 6.3SP1 database where AES is installed and perform a classic full “single schema to split schema“ upgrade to PRPC 7.1.9. 
-    With the PDF document “Autonomic Event Services (AES) Enterprise Edition Installation and Upgrade Guide 7.1.7” :
     o    Install AES 7.1.7 by following the “Upgrading from v3.4 or v3.5 to v7.1.7” section
-    Because new Pega 7 nodes will be created (requirement #2 above), with the PDF document “Autonomic Event Services (AES) Enterprise Edition Monitored Node Configuration Guide 7.1.7”, follow the “Configuring the AES nodes” section by performing the following steps :
     o    Step 4: “Create a Unique System Name and Update All Nodes”
     o    Step 7: “Update landing page to Send Alerts to AES”
     o    Step 10: “Update the Data-Admin-Nodes description”
-    Delete old nodes used in Pega 6

Am I missing something in the two options above ?
Do you see another alternative ? 
What is the best way to perform this upgrade ?

 

I'm already aware that unlike option #2, we are loosing historical datas with option #1.

 

Additional question : we have some framework layers (CustomerService, HCIF, CustomerService for HealthCare) in our PRPC database, do we need to install them in the AES database too ?

 

Thank you in advance for your answers.

***Updated by Moderator: Marissa. Removed user added Ask the Expert group tag. Apologies for confusion, shouldn't have been an end-user option***

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