Possibility of extending Maximum Pega Production Level/ application environments
Hi All - As we all know that pega by default supports at max 5 production levels i.e. we can have at most 5 environments(DEV, PreQA, QA, UAT and PROD) for a given pega application. I want to check with forum experts if we can have more than 5 environments for application like DEV, CI, QA1, QA2, QA3, UAT and PROD(total 7 environments)? When I say Q1, Q2, Q3 I mean these environments will have their own separate DB schema's Web-logic servers and everything.
Request you all to express your thoughts on the same, Thank you!!
**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.
Accepted Solution
Pegasystems Inc.
US
JPMC
US
Any thoughts guys?
Updated: 14 Dec 2015 16:44 EST
Pegasystems Inc.
US
Hi Dhirendra,
Currently you have the ability to set the system level to a value from 1 - 5, where 5 is the production level. There is built in conditional checks that use system level and clients added their own as well.
You can have X number of environments, separate DB schemas and app servers, and the separate environments can share the name system level. For example Q1, Q2, Q3 could all use the same system level of 3. If you need to add addition system level conditional checking you could add the system name into the condition. So if system level = 3 and system name = Q2 then do something different.
Does this answer you question?
JPMC
US
Thank you @Chris koyl for your response!! Okay, so it means we can not assign or change Production level more than 5?
I think the alternative you suggested would work for my scenario, As per my understanding affected area is environment settings which we have implemented using data page and table. Do you foresee any other area which I might have to address/update if we go by this alternative approach of using production level and system name combination to decide the environment?
And also, can you please confirm that changing systemname DSS to something like pegaDEV, pegaQA1, PegaQA2... etc wont affect anything else?
Accepted Solution
Pegasystems Inc.
US
Correct, the valid values for the production level setting in a Data-Admin-System instance are 1 (Lowest) to 5 (Highest). The OTB system level conditional checking is based on 1 - 5.
I don't see any other areas that you might need address with an alternative approach of using production level and system name. These conditional checks are your own custom conditional checks.
When you change the system name you also need to add the APP, BROWSER and BATCH requestor types. During the install these were added for you based on the system name you chose to use within the installer but since you are now possibly changing the name make sure you add these requestor type instances before you restart the server. Just do a save as on the three instances that have your current system name and use the new system name in the Save As screen.
Hope this helps.
JPMC
US
Thank you again Chris Koyl!! Will try this alternative way.
Highmark Health
US
Hi Chris,
IS there any specific use other then security by setting production level to 5 ( we have one internal application with production level 2 in prod) , I am mainly looking for performance improvement does this changes in caching /logging or rule resolution process , please can you provide any document if you have any
Thank you
Correct, the valid values for the production level setting in a Data-Admin-System instance are 1 (Lowest) to 5 (Highest). The OTB system level conditional checking is based on 1 - 5.
I don't see any other areas that you might need address with an alternative approach of using production level and system name. These conditional checks are your own custom conditional checks.
When you change the system name you also need to add the APP, BROWSER and BATCH requestor types. During the install these were added for you based on the system name you chose to use within the installer but since you are now possibly changing the name make sure you add these requestor type instances before you restart the server. Just do a save as on the three instances that have your current system name and use the new system name in the Save As screen.
Hope this helps.