Support Article
Multiple installation documentation issues with 7.3.1 on JBoss
Summary
The following documentation issues have been discovered while installing Pega 7.3.1 on JBoss with Oracle and with Postgres.
- No explicit statement of the JVM parameter -Djava.awt.headless=true
The Pega JBoss deployment guides state only that there should be a “headless AWT setting” with no mention of what it is. The guides also state that it should be added to a SetDomainEnv.bat or SetDomainEnv.sh script. These scripts do not exist in JBoss.
The setting should be added to the standalone.conf.bat or the standalone.conf file as correctly mentioned elsewhere in the guides for other JVM parameters. This information is missing for the JBoss with Postgres and Oracle deployment guides and, most likely, other deployment guides.
- The format of the module.xml file is wrong in the guides and is actually invalid XML
As shown in the JBoss Oracle and JBoss Postgres guides, here is the invalid XML:
>
<properties>
<property name="jboss.api" value="unsupported"/>
</properties>
<resources>
<resource-root path="ojdbc7.jar"
/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name>="javax.servlet.api" optional="true"/>
</dependencies>
</module>
Here is the correct XML:
<module xmlns="urn:jboss:module:1.1" name="org.postgresql">
<properties>
<property name="jboss.api" value="unsupported"/>
</properties>
<resources>
<!-- Insert resources here -->
<resource-root path="ojdbc7.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
</dependencies>
</module>
- Insufficient example of the <driver> entry to be used in the standalone-full.xml file (Postgres version only, Page 45).
<drivers>
</driver-class>
</driver>
Here is the correct entry:
<drivers>
<driver name="postgresql" module="org.postgresql">
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
</driver>
</drivers>
- There is no mention of the pooled connection factory in the Postgres guide.
This is correct in the Oracle guide and should be copied into the Postgres document.
Here is the section, starting with the following text:
factory. Follow the example for your version of JBoss:
JBoss deployments require EAR files; therefore, this information is important.
- The datasources contain no connection details or driver reference for the Postgres version of the guide.
<datasource jta="false" jndi-name="java:/jdbc/PegaRULES" poolname="
PegaRULES"enabled="true" use-ccm="false">
<security>
<user-name>user_name</user-name>
<password>password</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
</validation>
<statement>
<share-prepared-statements>false</share-prepared-statements>
</statement>
<pool>
<min-pool-size>30</min-pool-size>
<max-pool-size>100</max-pool-size>
</pool>
</datasource>
The correct entry is this:
<datasource jta="false" jndi-name="java:/jdbc/PegaRULES" pool-name="PegaRULES" enabled="true" use-ccm="false">
<connection-url>jdbc:postgresql://localhost:5433/SID</connection-url>
<driver>postgresql</driver>
<pool>
<min-pool-size>30</min-pool-size>
<max-pool-size>100</max-pool-size>
</pool>
<security>
<user-name>user_name</user-name>
<password>password</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
</validation>
<statement>
<share-prepared-statements>false</share-prepared-statements>
</statement>
</datasource>
Steps to Reproduce
See the sections cited in the Summary above for the following Deployment Guides:
https://pdn.pega.com/documents/pega-731-platform-installation-guide-jboss-redhat-eap-and-postgresql
https://pdn.pega.com/documents/pega-731-platform-installation-guide-jboss-redhat-eap-and-oracle
Resolution
Corrected JBoss deployment guides are available for Pega 7.4.
Published December 19, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.