Question
Scotiabank
CA
Last activity: 20 Sep 2017 20:59 EDT
PostgreSQL support for 7.2 and 7.3
As per the platform support guide (https://pdn.pega.com/documents/platform-support-guide) "PostgreSQL is only supported for the Tomcat webserver, or JBoss with WAR installations only"
My question is why do we need to do do "war" deployments only? This is for PRPC 7.2 and 7.3
What functionality do we lose if we use "war" deployments?
If we only want to use PostgreSQL DB for development but Oracle or DB2 for production to go and an "ear" deployment for the application server, what should we be looking out for?
Pegasystems Inc.
IN
Dear Saurabh,
Tomcat is a WebContainer and only war deployments are supported. For JBoss ear deployment is not supported with Postgre SQL as its not tested and coded to support it. During Server Start you will get issues related to DatabaseException as query generation is not supported.
Thanks,
Naresh
Scotiabank
CA
Hi Naresh - I don't think you understood my question.
The platform support guide clearly states that if you want to use PostgreSQL you need to use WAR deployments. I can deploy the WAR file on Tomcat or JBoss. There is even an install guide to deploy PRPC on JBoss EAP/PostgreSQL (https://docs-previous.pega.com/pega-73-platform-installation-guide-jboss-redhat-eap-and-postgresql)
My question is more along the lines of why is my choice of database (PostgreSQL) impacting my choice of 'ear' or 'war' install. As far as I know, PostgreSQL supports two-phase commit since version 8.1 and secondly what do I lose (functionality, performance, security, connectivity to other protocols etc.) by using "war" files instead of "ear" files.
From what I have read, PostgreSQL supports dynamic SQL.
Pegasystems Inc.
IN
Hi Saurabh,
As explained, its not if DB is supporting 2 PC or other functionality. The CodeBase(Pega here) also should support the logic in relation with Application Server Containers.
Ex:- Each DB will have its own way DateTime & Function Calculations, to support with each DB like PostgreSQL or other DB the core logic also should understand what DB is expecting and what response DB would be giving. In the same context, each Application Server will use its own libraries to calculate the input/output.
With the above, JBoss with PostgreSQL is supported for WAR deployements for now. You will see many below exceptions like below if you start JBoss with ear & PostgreSQL. Hope this helps!
2016-09-30 16:52:42,624 [ pdevlrkisrwap01] [ STANDARD] [ ] [ ] ( internal.access.DatabaseImpl) ERROR - Encountered database exception in saveAllOrNone
com.pega.pegarules.pub.database.DatabaseException: Database-General 0 25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block
Hi Saurabh,
As explained, its not if DB is supporting 2 PC or other functionality. The CodeBase(Pega here) also should support the logic in relation with Application Server Containers.
Ex:- Each DB will have its own way DateTime & Function Calculations, to support with each DB like PostgreSQL or other DB the core logic also should understand what DB is expecting and what response DB would be giving. In the same context, each Application Server will use its own libraries to calculate the input/output.
With the above, JBoss with PostgreSQL is supported for WAR deployements for now. You will see many below exceptions like below if you start JBoss with ear & PostgreSQL. Hope this helps!
2016-09-30 16:52:42,624 [ pdevlrkisrwap01] [ STANDARD] [ ] [ ] ( internal.access.DatabaseImpl) ERROR - Encountered database exception in saveAllOrNone
com.pega.pegarules.pub.database.DatabaseException: Database-General 0 25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block
DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
| SQL Code: 0 | SQL State: 25P02
From: (B77A7347AB187AEF19D7FE84A8AD6917D:(Engine Startup Finish Init))
SQL: INSERT INTO pegarules.pr_sys_ruleset_index (pzInsKey , pxCommitDateTime , pxcreatedatetime , pxcreateopname , pxcreatesystemid , pxinsname , pxobjclass , pxsavedatetime , pyrulesetversion , pzrulesetindex , pzrulesetlisthash , pzrulesetname , pzrulesetversionmajor , pzrulesetversionminor , pzrulesetversionminorpatch , pzrulesetversionpatch) VALUES (? , CURRENT_TIMESTAMP , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
SQL Inserts: <SYSTEM-RULESET-INDEX 53085E7C15C7840A74D6DBC9517BC471!PEGA-LP-PROCESSANDRULES> <2016-09-30 16:52:42.621> <<null>> <98a29833ad61aed4a9047b273f0341fa> <53085E7C15C7840A74D6DBC9517BC471!PEGA-LP-PROCESSANDRULES> <System-RuleSet-Index> <2016-09-30 16:52:42.621> <07-10> <0> <53085e7c15c7840a74d6dbc9517bc471> <Pega-LP-ProcessAndRules> <7> <10> <10-AA> <-1>
Caused by SQL Problems.
Problem #1, SQLState 25P02, Error code 0: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
Problem #2, SQLState 23505, Error code 0: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "pr_sys_ruleset_index_pk"
Thanks,
Naresh