Dev and Prod have different PegaRules database
Development environment setup is like below,
JBOSS and ORACLE Database.
For Production we have different database setup,
JBOSS and postgresql Database.
What are the issues will be during setup.
Thanks
Ravi.
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
Comments
Keep up to date on this post and subscribe to comments
First of all, nonono, please don't do that, you must NOT have different DB in DEV and PROD.
Second, if you still want to do that, then you should review all your Connect SQL rules. They could be DBprovider specific. And in future, never write custom Connect SQl rules.
And, the last.. It's simple - Just DON'T DO THAT. You will never be sure that your code you're going to deploy on prod will work.
- reply
Also if you manage to move data to different DB, you would need to do extensive testing in PROD as well.
- reply
Hi
As mentioned in other comments, its a definite NO for such a setup.
Would really be interested to know why do you want to go for this?
Regards
Bhavya
- reply
- Restricted access to PROD dev access.
- Enterprise Application Upgrade approach – DEV to UAT, PROD- what tables to copy?
- Deploying/promoting a JMS MDB Listener changes to Non-Dev(SIT/UAT/PROD) environments
- Authentication Timeout is working in Dev/SIT/PAT environments but not working in Prod environments
- Dev and Prod not the same DB