Question
SYNTEL
GB
Last activity: 14 Jun 2016 15:32 EDT
Recommendations to setup Pega platform in customer chosen public / private cloud environment
We are doing a Pega fitment evaluation for one of our clients. The client is currently evaluating PaaS / public cloud as part of its future strategic architecture for IT services however seldom are applications developed and run on a PaaS platform completely standalone – commonly these applications must integrate with existing enterprise systems – applications, services, data – some of which are likely to reside in an existing enterprise environment outside the cloud system.
There are couple of areas where we need guidance from Pega Product Support Team however any response or case study is welcome to elaborate awareness in this space -
1) Can Pega 7.x installation be done in a way where the Jboss Application server is in cloud and Pega DB server is in existing enterprise environment?
2) Can Pega application running in cloud have database connectivity to the enterprise data system?
3) With Pega installation in public cloud environment, does it support database to database connections to connect with enterprise data system(s)?
4) Are there any known challenges, limitations and recommendations that should be considered while evaluating setting up Pega platform as PaaS for an enterprise in public / private cloud environment?
Many thanks for your invaluable response in advance.
Accepted Solution
Updated: 8 Jun 2016 10:15 EDT
Hi Piyush,
I am from Cloud PM.
On questions 1, 2, 3 - there is nothing in the Pega 7 Platform that technically prevents you from doing these things. If you require a particular deployment architecture, you should test it to ensure it meets your requirements.
On question 4 - the answer is yes, of course. For example: JDBC connections between a Cloud-based app server and a DB located on a private network (e.g. customer on-prem, some other Cloud, etc) may be more susceptible to timeouts; this can probably be mitigated through careful tuning of the connection pool and/or a private, point-to-point network connection between the 2 environments (vs. using public Internet). Testing is essential to uncover these types of potential issues.
Cheers,
Jimmy
Pegasystems Inc.
IN
Hi Piyush,
I would suggest you to kindly check with our cloud team. They will be able to answer all the above questions.
Regards,
Ravi
Accepted Solution
Updated: 8 Jun 2016 10:15 EDT
Hi Piyush,
I am from Cloud PM.
On questions 1, 2, 3 - there is nothing in the Pega 7 Platform that technically prevents you from doing these things. If you require a particular deployment architecture, you should test it to ensure it meets your requirements.
On question 4 - the answer is yes, of course. For example: JDBC connections between a Cloud-based app server and a DB located on a private network (e.g. customer on-prem, some other Cloud, etc) may be more susceptible to timeouts; this can probably be mitigated through careful tuning of the connection pool and/or a private, point-to-point network connection between the 2 environments (vs. using public Internet). Testing is essential to uncover these types of potential issues.
Cheers,
Jimmy
Pegasystems Inc.
US
I want to add that for question 1, the only db platform we do not yet support (as of 7.2) for JBoss is postgres, which only runs on tomcat container. Another question you should ask yourself when considering using pega cloud is: are there any special reasons you have to run JBoss versus tomcat? (e.g., you need to run message-driven beans). Are you open to migrating your data from your current DB platform to postgres, which should be significantly more cost-effective versus an Oracle for example?
SYNTEL
GB
Thank you very much for your advice and response. I might require your help again in future if my customer has specific query where a second opinion is preferable.