I want to use prconfig.xml instead of context.xml for DB connection.
Hi,All
I described DB connection settings in prconfig.xml according to the following flow, but it does not work.
1.I added the settings to prconfig.xml referring to item #2 below.
https://docs-previous.pega.com/how-encrypt-database-passwords-using-jce-keyring-file?
2.Comment out DB connection statement in context.xml
3.tomcat service restart
4.Connect to http://"ip":8080/prweb
Question1: Is the prconfig.xml setting correct?
Question2: What other settings are needed to enable DB connection with prconfig.xml?
prconfig.xml:
Hi,All
I described DB connection settings in prconfig.xml according to the following flow, but it does not work.
1.I added the settings to prconfig.xml referring to item #2 below.
https://docs-previous.pega.com/how-encrypt-database-passwords-using-jce-keyring-file?
2.Comment out DB connection statement in context.xml
3.tomcat service restart
4.Connect to http://"ip":8080/prweb
Question1: Is the prconfig.xml setting correct?
Question2: What other settings are needed to enable DB connection with prconfig.xml?
prconfig.xml:
# cat /opt/pega/Additional_Products/BIX/config/prconfig.xml <?xml version="1.0" encoding="UTF-8"?> <pegarules> <!-- This is a minimum format prconfig.xml file. Only the settings which are required to access settings in the database are included. All other settings which were formerly located only in this file are now Data-Admin-System-Settings. --> <env name="identification/systemName" value="pega" /> <env name="initialization/settingsource" value="merged" /> <env name="fua/conclusionQueryPerformance" value="false" /> <env name="initialization/minimalStartup" value="true" /> <env name="ruleresolution/useclassancestorjoin" value="false" /> <env name="ruleresolution/userulesetindexjoin" value="false" /> <env name="ruleresolution/usejoinsforallclasses" value="false" /> <env name="agent/enable" value="false" /> <env name="fua/enableAssemblyAvoidance" value="false" /> <env name="agent/masteragentenable" value="false" /> <env name="initialization/daemonenable" value="false" /> <env name="asyncservices/enable" value="false" /> <env name="asyncExecutor/enable" value="false" /> <env name="/compatibility/BIXUseOptimizedClipboardXML" value="true" /> <env name="/compatibility/BIXdisableForwardChaining" value="true" /> <env name="/compatibility/BIXdisableBackwardChaining" value="true" />
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/> <env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/> <!-- Most nodes have a 'default' classification and for these nodes, no additional changes need to be made to this file. However, if this is node has a non-general purpose, for example: 'Agent', then the node classification setting should be added to this file. --> <!--env name="initialization/nodeclassification" value="Agent" / -->
<!-- Settings can still be put in this file. If they are, then the value in this file will override the value in the database for this node. This is useful for settings which are specific to this node and should not be shared by multiple nodes on this system. -->
<!-- Pegasystems recommends that you use Application Server connection pooling to the database for Websphere and Weblogic. These examples are provided if you need to use Pega Connection Pooling for Tomcat or for testing purposes. If you are using Application server connection pooling, there is no longer a need to edit this file.
****The new format for this file is only valid if you are using Application Server connection pooling. If you are not, please replace this file with an older version. ***
Oracle 10g (Type 4) oracle.jdbc.OracleDriver jdbc:oracle:thin:@serverName:1521:db IBM DB/2 Type 4 com.ibm.db2.jcc.DB2Driver jdbc:db2://serverName:port/dbName SQL Server 2005 com.microsoft.sqlserver.jdbc.SQLServerDriver jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false -->
<env name="database/drivers" value="oracle.jdbc.OracleDriver" /> <env name="database/databases/PegaRULES/url" value="jdbc:oracle:thin:@// Proprietary information hidden:1521/ORCLPDB1" /> <env name="database/databases/PegaRULES/userName" value="HOGE" /> <env name="database/databases/PegaRULES/password" value="HOGEPASS" /> <env name="database/databases/PegaDATA/url" value="jdbc:oracle:thin:@// Proprietary information hidden:1521/ORCLPDB1" /> <env name="database/databases/PegaDATA/userName" value="HOGE" /> <env name="database/databases/PegaDATA/password" value="HOGEPASS" />
<env name="identification/KeyringPrefix" value="BIX-extract" /> <env name="identification/KeyringAlgorithm" value="AES" /> <env name="identification/KeyringLength" value="256" />
</pegarules> #
Supplementary information: As background, we wanted to encrypt DB connection information in context.xml, but could not do so.
thank you.