Question
Incessant Technologies Pvt Ltd.
AU
Last activity: 18 Dec 2015 7:57 EST
pegarules.keyring in Pega 7.1.8
Hi,
@We upgraded our applications from Pega 5.5 SP1 to Pega 7.1.8 with split schema.
pegarules.keyring was generated and used in pega 5.5 SP1 for pega applications to connect to database.
What is the process to configure pega to use pegarules.keyring file in Pega 7.1.8 with split schema?
Regards,
Hareen
Pegasystems Inc.
US
The general process is described here and largely unchanged: https://pdn.pega.com/how-encrypt-database-passwords-using-jce-keyring-file#classpath. The default database connecting user for split schema is data user but it can be any application user with proper privilege. See the installation guide for details. There are settings specify rules and data schema with the details specific to the application server. If you run into any issues along the way, please report back.
Incessant Technologies Pvt Ltd.
AU
Hi Kevin,
- Link provided is suggesting us to set the jar files in class path, these files are not available in prweb.war file of pega 7, is there any other approach for generating the keyring files?
- lib\pega\prprivate.jar
- lib\pega\prpublic.jar
- lib\pega\prlogging-1.2.14.jar
- lib\pega\prlucene-1.4.3.jar
- lib\base\java6\prjsr166java6-3.0.jar
- lib\pega\pricu2jdk.jar
- lib\prdbcp.jar
2. Please check if below prconfig.xml looks good in case of using keyring file for database connectivity and advise if any changes are needed
Hi Kevin,
- Link provided is suggesting us to set the jar files in class path, these files are not available in prweb.war file of pega 7, is there any other approach for generating the keyring files?
- lib\pega\prprivate.jar
- lib\pega\prpublic.jar
- lib\pega\prlogging-1.2.14.jar
- lib\pega\prlucene-1.4.3.jar
- lib\base\java6\prjsr166java6-3.0.jar
- lib\pega\pricu2jdk.jar
- lib\prdbcp.jar
2. Please check if below prconfig.xml looks good in case of using keyring file for database connectivity and advise if any changes are needed
| <env name="database/drivers" value="com.microsoft.sqlserver.jdbc.SQLServerDriver" /> |
| <env name="database/databases/PegaRULES/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaRULES/userName" value="prpcuser_trn" /> |
| <env name="database/databases/PegaDATA/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaDATA/userName" value="prpcuser_trn" /> |
3. Where are we specifying the schema names in prconfig.xml
4. If one table is available in both schemas, how does pega identify which table needs to be updated if an Obj-Save is done in pega on the class name that is associated with the table (that is available in both schemas).
Regards,
Hareen
Pegasystems Inc.
US
Use this article instead, https://pdn.pega.com/how-encrypt-passwords-properties-and-blobs
The other article was written before the engine code was moved into the database and thus wants you to include jars like prprivate and prpublic which are no longer needed. These are the jars that you need, along with your JDBC jar file.
- jsr94-1.0.jar
- prbootstrap.jar
- prdbcp.jar
- prbootstrap-api.jar – Only for Pega 7.1.7 and subsequent releases
Pega 7.1.7 introduced the new file, prbootstrap-api.jar.
Are you trying to generate the keyring file to use with command line tools like prpcUtils or BIX?
Incessant Technologies Pvt Ltd.
AU
We are trying to use runpega batch / shell file to generate keyring file.
Can you please advise on the other three questions also?
2. Please check if below prconfig.xml looks good in case of using keyring file for database connectivity and advise if any changes are needed
| <env name="database/drivers" value="com.microsoft.sqlserver.jdbc.SQLServerDriver" /> |
| <env name="database/databases/PegaRULES/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaRULES/userName" value="prpcuser_trn" /> |
| <env name="database/databases/PegaDATA/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaDATA/userName" value="prpcuser_trn" /> |
3. Where are we specifying the schema names in prconfig.xml
We are trying to use runpega batch / shell file to generate keyring file.
Can you please advise on the other three questions also?
2. Please check if below prconfig.xml looks good in case of using keyring file for database connectivity and advise if any changes are needed
| <env name="database/drivers" value="com.microsoft.sqlserver.jdbc.SQLServerDriver" /> |
| <env name="database/databases/PegaRULES/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaRULES/userName" value="prpcuser_trn" /> |
| <env name="database/databases/PegaDATA/url" value="jdbc:sqlserver://pegatrndb;SendStringParametersAsUnicode=false;SelectMethod=cursor;DatabaseName=prpc_trn" /> | |
| <env name="database/databases/PegaDATA/userName" value="prpcuser_trn" /> |
3. Where are we specifying the schema names in prconfig.xml
4. If one table is available in both schemas, how does pega identify which table needs to be updated if an Obj-Save is done in pega on the class name that is associated with the table (that is available in both schemas).
Regards,
Hareen
Pegasystems Inc.
US
I understand that you are trying to use the runPega script to generate a keyring file. What I am trying to understand is utlitmately what command line tool do you plan to use this keyring file with in 7.1. If you have that tool, such as prpcUtils, working in 7.1 with an unencrypted password in prbootstraps and prconfig then we can use those files when generating the keyring file.
2. Since you have not generated the keyring file yet you also need to include the properties for the unencrypted password.
3.
In your prconfig.xml file you will have properties like this to specify the default schemas
<env name="database/databases/PegaRULES/defaultSchema" value="v718rules" />
<env name="database/databases/PegaDATA/defaultSchema" value="v71data" />
4. A class maps to a table in a particular schema so from the class mapping the obj-save will be schema qualified correctly. Why would you have the same table in both schemas? Are you talking about old rules tables which you have not cleaned up from your data schema after the upgrade?