We are planning to setup Pega in AWS with the following stack - Tomcat &AWS RDS Oracle. I would like to know the Pega platform compatibility with AWS RDS - Oracle.
Does Pega/PRPC support AWS RDS Oracle? Has any Clients went with this setup in PROD?
Does Pega require "Java" to be enabled in the Database either in the current or future versions of Pega?
I could see the below dependency for enabling Java in DB -
UDF's require Java to be enabled. Pega uses UDF's only in the reports rules where unexposed properties are used. The work-around for this is to expose the property, and this should address the problem. Are there any other scenarios where Pega uses UDF's and we do not have a workaround?
AWS RDS does not support Java and UDF's. From the above point, this shouldn't be a show-stopper in moving away from AWS RDS to EC2. Are any Clients using this Stack - Pega + Tomcat + AWS RDS (Oracle/DB2), and is this supported?
***Updated by Moderator: Marissa to add SR Details & update categories***
**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.
What does work is using a full AWS VM, where you can access the underlying OS - this has drawbacks compared to AWS RDS, but it will work if that's what you want. Or PegaCloud, if you're looking at multiple Cloud solutions and not just at AWS.
With respect to your statement "AWS RDS has one major issue, which is that Pega requires Java in the database to work and AWS RDS does support it" - Is it a typo? Do you mean AWS RDS does not support it?
"we use a lot of Java in the database and Pega won't work without it - I believe it won't even install" - What's the dependency of Java for Pega to run? The only dependency as per multiple forums over here are that UDF's require Java to enabled. UDF is only required for report definitions which uses unexposed properties. If we expose all the properties, the dependency on Java, UDF is gone? So do you still think Pega wouldn't work? By the way, I have setup an instance and it works fine. But I would like to know from the experts if there are are unforeseen issues?
"What does work is using a full AWS VM" - Do you mean setting up EC2 and Oracle on top of it?
Sorry, typo - AWS RDS does not support Java in the database for Oracle. I've fixed the original post.
Java in the database is bit different per database type. It's possible it will run, but you might run in to problems in the future (other than UDFs as you already mentioned). I'm not certain exactly what needs Java - it's a bit out of my area. I'll see if I can find the answer.
Yes, setting up EC2 and Oracle on top of a full VM. Pega will work in a VM in general just like it does on an OS running on a physical machine.
In Legacy Cloud we use Oracle running on EC2 instances. In the "on-premise" world it would be just like spinning up a VM or standing up a physical server and installing Oracle on it. The app nodes handle all the Java functionality and "talk" to the database via jdbc. As Adam points out this will work, but is not as robust as an RDS cluster. We use it for All-In-One DEV instances that have an app node and an Oracle DB node on the same AWS instance.
In PegaCloud 2x we use Postgres running on Amazon RDS clusters. This solution is more robust and more easily managed than standalone servers. This is the optimal solution for PROD environments. We also actively develop PegaCloud and PRPC using this model so it is constantly improving.
As Adam also points out - you should consider implementing a PegaCloud solution that has all this taken care of for you. After the purchasing and onboarding happens - just paste the URL we provide into your browser and start developing.