search

kannan-raveendran-nair / pega-pe-docker

Pega Personal Edition made docker deployable
14 stars 17 forks source link

Version 8.3 #1

Closed jayglenn closed 4 years ago

jayglenn commented 4 years ago

Great work! Now is this possible to do with 8.3? Unfortunately I don't have 7.2 and Pega doesn't make the older versions available (unless I'm missing them).

FYI I tried to follow the instructions but got hung up on one of the .war files that's not in the .ZIP file.

kannan-raveendran-nair commented 4 years ago

Thank You! You are right, older versions are not made available by Pegasystems. I have never tried this for Pega 8.x versions, but I can try. Which .war file is missing for 8.3? I'm away from my computer for the weekend, but hopefully I can check this Monday night.

arvindg80 commented 4 years ago

Hi Kannan,

I am trying with 8.3. Once all good, what URL we need to hit for accessing prweb? Thank you for all help.

31-Oct-2019 00:55:50.928 WARNING [main] org.apache.catalina.core.NamingContextListener.addResource naming.jmxRegistrationFailed 31-Oct-2019 00:55:50.930 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 31-Oct-2019 00:55:50.932 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat/webapps/prsysmgmt] has finished in [51] ms 31-Oct-2019 00:55:50.934 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 31-Oct-2019 00:55:50.941 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"] 31-Oct-2019 00:55:50.944 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [1,106] milliseconds

wioefjj34 commented 4 years ago

Hello!

Did you try the docker-compose.yml file "as-is" without modification?

If the below said lines are used, then you should try http://localhost:8085/prweb/. Else just use http://localhost:8080/prweb/ ports:

Regards,

Kannan R

On Wed, Oct 30, 2019 at 9:00 PM arvindg80 notifications@github.com wrote:

Hi Kannan,

I am trying with 8.3. Once all good, what URL we need to hit for accessing prweb? Thank you for all help.

31-Oct-2019 00:55:50.928 WARNING [main] org.apache.catalina.core.NamingContextListener.addResource naming.jmxRegistrationFailed 31-Oct-2019 00:55:50.930 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 31-Oct-2019 00:55:50.932 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat/webapps/prsysmgmt] has finished in [51] ms 31-Oct-2019 00:55:50.934 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 31-Oct-2019 00:55:50.941 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"] 31-Oct-2019 00:55:50.944 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [1,106] milliseconds

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kannan-raveendran-nair/pega-pe-docker/issues/1?email_source=notifications&email_token=AAQQHWJNUV7UDD7TLHZYWETQRIU2TA5CNFSM4I3HRIPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWHNKA#issuecomment-548173480, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQQHWNWWXAPNLMR35J5HDLQRIU2TANCNFSM4I3HRIPA .

arvindg80 commented 4 years ago

Thank you Kannan. In the docker-compose, I gave like this. 

environment:
 - JDBC_URL=jdbc:postgresql://172.22.0.2/pega   #replace this with your postgresql installation ip

From the logs, I could see different issue. Not sure whether it is related to version. 

pega721                    | 31-Oct-2019 04:45:52.152 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null
postgresql-pega721         | 2019-10-31 04:45:52.197 UTC [81] ERROR:  relation "pr_data_admin" does not exist at character 34
postgresql-pega721         | 2019-10-31 04:45:52.197 UTC [81] STATEMENT:  select pypurpose, pysetting from pr_data_admin where pypurpose like $1 and pyowner = 'Pega-Engine'
pega721                    | 31-Oct-2019 04:45:52.203 SEVERE [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Unable to connect to database.  Will only use properties from file.
pega721                    |    org.postgresql.util.PSQLException: ERROR: relation "pr_data_admin" does not exist
pega721                    |   Position: 34
pega721                    |        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476)
pega721                    |        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189)
pega721                    |        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300)
pega721                    |        at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428)
pega721                    |        at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354)
pega721                    |        at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169)
pega721                    |        at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117)
pega721                    |        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
pega721                    |        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
pega721                    |        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
pega721                    |        at java.lang.reflect.Method.invoke(Method.java:498)
pega721                    |        at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)
pega721                    | 31-Oct-2019 04:45:52.208 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0      ]
pega721                    | 31-Oct-2019 04:45:52.208 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings
postgresql-pega721         | 2019-10-31 04:45:52.215 UTC [81] ERROR:  relation "pr_engineclasses" does not exist at character 40
postgresql-pega721         | 2019-10-31 04:45:52.215 UTC [81] STATEMENT:  select distinct pzcodesetversion from  pr_engineclasses where pzcodeset = 'pega-enginecode' 
pega721                    | 31-Oct-2019 04:45:52.216 WARNING [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: ERROR: relation "pr_engineclasses" does not exist
pega721                    |   Position: 40
pega721                    | 31-Oct-2019 04:45:52.220 INFO [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:
postgresql-pega721         | 2019-10-31 04:45:52.221 UTC [81] ERROR:  relation "pr_engineclasses" does not exist at character 38
postgresql-pega721         | 2019-10-31 04:45:52.221 UTC [81] STATEMENT:  select pzbinarycontent, pzstate from pr_engineclasses where pzpackage = $1 and pzclass = $2 and pzjar = $3 and pzcodeset = 'pega-enginecode' and pzcodesetversion = $4 ORDER BY pzpatchdate DESC
pega721                    | 31-Oct-2019 04:45:52.221 WARNING [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. PRMiniLoader - unable to load classes from the database: ERROR: relation "pr_engineclasses" does not exist
pega721                    |   Position: 38
pega721                    | /usr/local/tomcat/webapps/prweb/WEB-INF/lib/boot/prbootphase2.jar (No such file or directory)
pega721                    | Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
pega721                    | 31-Oct-2019 04:45:52.227 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. 
pega721                    | ============ PegaRULES Bootstrap Configuration ============
pega721                    |            Date: Thu Oct 31 04:45:52 GMT 2019
pega721                    |    Java Version: Private Build 1.8.0_222
wioefjj34 commented 4 years ago

Oh, I remember seeing this issue while developing for Pega7.x. I think the pega.dump file uses a different schema or database name than the one you used for POSTGRES_DB or POSTGRES_USER. Please check these details in restore script in the folder where pega.dump was found. I'm afraid I'm away from my computer, and will be away for 2more weeks, so I will not be able to find this detail for you directly, sorry about that. But I will try to support you over phone as much as possible.

On Thu, Oct 31, 2019, 12:50 AM arvindg80 notifications@github.com wrote:

Thank you Kannan. From the logs, I could see different issue. Not sure whether it is related to version.

pega721 | 31-Oct-2019 04:45:52.152 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null postgresql-pega721 | 2019-10-31 04:45:52.197 UTC [81] ERROR: relation "pr_data_admin" does not exist at character 34 postgresql-pega721 | 2019-10-31 04:45:52.197 UTC [81] STATEMENT: select pypurpose, pysetting from pr_data_admin where pypurpose like $1 and pyowner = 'Pega-Engine' pega721 | 31-Oct-2019 04:45:52.203 SEVERE [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Unable to connect to database. Will only use properties from file. pega721 | org.postgresql.util.PSQLException: ERROR: relation "pr_data_admin" does not exist pega721 | Position: 34 pega721 | at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476) pega721 | at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189) pega721 | at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300) pega721 | at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428) pega721 | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354) pega721 | at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169) pega721 | at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117) pega721 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) pega721 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) pega721 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) pega721 | at java.lang.reflect.Method.invoke(Method.java:498) pega721 | at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kannan-raveendran-nair/pega-pe-docker/issues/1?email_source=notifications&email_token=AAQQHWLEXTVI2JRP4LEGTGTQRJP2FA5CNFSM4I3HRIPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWRXTY#issuecomment-548215759, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQQHWJPJT3T3GINQWSALGDQRJP2FANCNFSM4I3HRIPA .

On Thu, Oct 31, 2019, 12:50 AM arvindg80 notifications@github.com wrote:

Thank you Kannan. From the logs, I could see different issue. Not sure whether it is related to version.

pega721 | 31-Oct-2019 04:45:52.152 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null postgresql-pega721 | 2019-10-31 04:45:52.197 UTC [81] ERROR: relation "pr_data_admin" does not exist at character 34 postgresql-pega721 | 2019-10-31 04:45:52.197 UTC [81] STATEMENT: select pypurpose, pysetting from pr_data_admin where pypurpose like $1 and pyowner = 'Pega-Engine' pega721 | 31-Oct-2019 04:45:52.203 SEVERE [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Unable to connect to database. Will only use properties from file. pega721 | org.postgresql.util.PSQLException: ERROR: relation "pr_data_admin" does not exist pega721 | Position: 34 pega721 | at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476) pega721 | at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189) pega721 | at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300) pega721 | at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428) pega721 | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354) pega721 | at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169) pega721 | at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117) pega721 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) pega721 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) pega721 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) pega721 | at java.lang.reflect.Method.invoke(Method.java:498) pega721 | at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kannan-raveendran-nair/pega-pe-docker/issues/1?email_source=notifications&email_token=AAQQHWLEXTVI2JRP4LEGTGTQRJP2FA5CNFSM4I3HRIPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWRXTY#issuecomment-548215759, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQQHWJPJT3T3GINQWSALGDQRJP2FANCNFSM4I3HRIPA .

samaniji commented 4 years ago

I am new to this. I tried to perform the steps for a Pega8.3 personal edition.

  1. Created folder /home/root/DockerBuild/resources added pega.dump added docker-compose.yml and changed postgress and pegadum dir values as suggested. Also changed references to Pega721 to Pega83

2.Added folder /home/root/DockerBuild/resources/PegaPRPC-WebApp/resources added prhelp.war added prweb.war

  1. Added folder /home/root/DockerBuild/resources/PegaPRPC-WebApp/jdbc_drivers added postgresql-42.1.1.jre7.jar

  2. Switched to folder /home/root/DockerBuild/resources execute docker-compose build --no-cache

fails with ERROR: yaml.scanner.ScannerError: mapping values are not allowed here in "./docker-compose.yml",line 119, column 71

kannan-raveendran-nair commented 4 years ago

Seems like you have violated one of the yaml syntax. Please recheck your change in the said line. If possible can you post the modified yaml file here, perhaps i may be able to spot.

kannan-raveendran-nair commented 4 years ago

Great work! Now is this possible to do with 8.3? Unfortunately I don't have 7.2 and Pega doesn't make the older versions available (unless I'm missing them).

FYI I tried to follow the instructions but got hung up on one of the .war files that's not in the .ZIP file.

Hi, its a bit outdated reply. Still, i have made the project compatible for Pega 8.3. Please try and let me know if you face any roadblocks.

kannan-raveendran-nair commented 4 years ago

Hi Kannan,

I am trying with 8.3. Once all good, what URL we need to hit for accessing prweb? Thank you for all help.

31-Oct-2019 00:55:50.928 WARNING [main] org.apache.catalina.core.NamingContextListener.addResource naming.jmxRegistrationFailed 31-Oct-2019 00:55:50.930 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 31-Oct-2019 00:55:50.932 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat/webapps/prsysmgmt] has finished in [51] ms 31-Oct-2019 00:55:50.934 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 31-Oct-2019 00:55:50.941 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"] 31-Oct-2019 00:55:50.944 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [1,106] milliseconds

Hi, let me know if you still face this issue. I have made some change to make the project compatible for Pega 8.3.

kannan-raveendran-nair commented 4 years ago

Thank you Kannan. In the docker-compose, I gave like this.

environment:
 - JDBC_URL=jdbc:postgresql://172.22.0.2/pega   #replace this with your postgresql installation ip

From the logs, I could see different issue. Not sure whether it is related to version.

pega721                    | 31-Oct-2019 04:45:52.152 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null
postgresql-pega721         | 2019-10-31 04:45:52.197 UTC [81] ERROR:  relation "pr_data_admin" does not exist at character 34
postgresql-pega721         | 2019-10-31 04:45:52.197 UTC [81] STATEMENT:  select pypurpose, pysetting from pr_data_admin where pypurpose like $1 and pyowner = 'Pega-Engine'
pega721                    | 31-Oct-2019 04:45:52.203 SEVERE [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Unable to connect to database.  Will only use properties from file.
pega721                    |  org.postgresql.util.PSQLException: ERROR: relation "pr_data_admin" does not exist
pega721                    |   Position: 34
pega721                    |      at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476)
pega721                    |      at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189)
pega721                    |      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300)
pega721                    |      at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428)
pega721                    |      at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354)
pega721                    |      at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169)
pega721                    |      at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117)
pega721                    |      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
pega721                    |      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
pega721                    |      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
pega721                    |      at java.lang.reflect.Method.invoke(Method.java:498)
pega721                    |      at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)
pega721                    | 31-Oct-2019 04:45:52.208 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0      ]
pega721                    | 31-Oct-2019 04:45:52.208 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: null
pega721                    | 31-Oct-2019 04:45:52.210 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings
postgresql-pega721         | 2019-10-31 04:45:52.215 UTC [81] ERROR:  relation "pr_engineclasses" does not exist at character 40
postgresql-pega721         | 2019-10-31 04:45:52.215 UTC [81] STATEMENT:  select distinct pzcodesetversion from  pr_engineclasses where pzcodeset = 'pega-enginecode' 
pega721                    | 31-Oct-2019 04:45:52.216 WARNING [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: ERROR: relation "pr_engineclasses" does not exist
pega721                    |   Position: 40
pega721                    | 31-Oct-2019 04:45:52.220 INFO [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:
postgresql-pega721         | 2019-10-31 04:45:52.221 UTC [81] ERROR:  relation "pr_engineclasses" does not exist at character 38
postgresql-pega721         | 2019-10-31 04:45:52.221 UTC [81] STATEMENT:  select pzbinarycontent, pzstate from pr_engineclasses where pzpackage = $1 and pzclass = $2 and pzjar = $3 and pzcodeset = 'pega-enginecode' and pzcodesetversion = $4 ORDER BY pzpatchdate DESC
pega721                    | 31-Oct-2019 04:45:52.221 WARNING [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. PRMiniLoader - unable to load classes from the database: ERROR: relation "pr_engineclasses" does not exist
pega721                    |   Position: 38
pega721                    | /usr/local/tomcat/webapps/prweb/WEB-INF/lib/boot/prbootphase2.jar (No such file or directory)
pega721                    | Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
pega721                    | 31-Oct-2019 04:45:52.227 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. 
pega721                    | ============ PegaRULES Bootstrap Configuration ============
pega721                    |            Date: Thu Oct 31 04:45:52 GMT 2019
pega721                    |    Java Version: Private Build 1.8.0_222

Hi, reason for this is due to multiple non-compatible changes in Pega 8.3 PE compared to Pega 7.2.1 PE. Pega 7.2.1 used database name as pega, 8.3 used db name as postgres. There were changes in context.xml contents and search paths for postgresql. All of these are fixed in the latest commit.

Please try the latest commit and let me know if you still face any issues.