Confirmation of Pega 7.2.2 Installation Guide for Websphere/MSSQL
Hi team,
I have questions on the installation guide for Websphere/MSSQL of Pega 7.2.2.
https://docs.pega.com/pega-722-platform-installation-guide-ibm-websphere-and-microsoft-sql-server
1. On Page 31, step 4 and 5 of Creating binding identifiers, it says "Binding identifier: dataSourceAdmin " twice. Is this correct?
2. On Page 31, step 4 and 5 of Creating binding identifiers, it says "String Value: the JNDI name of the Admin data source for your data schema " and "String Value: the JNDI name of the Admin data source for your rules schema ". However the installation guide, on page 37 step 5, tells creating only one JNDI name of the Admin data source, not specifying rules schema nor data schema. What should be entered for String Value of step 4 and 5 on Page 31?
Hi team,
I have questions on the installation guide for Websphere/MSSQL of Pega 7.2.2.
https://docs.pega.com/pega-722-platform-installation-guide-ibm-websphere-and-microsoft-sql-server
1. On Page 31, step 4 and 5 of Creating binding identifiers, it says "Binding identifier: dataSourceAdmin " twice. Is this correct?
2. On Page 31, step 4 and 5 of Creating binding identifiers, it says "String Value: the JNDI name of the Admin data source for your data schema " and "String Value: the JNDI name of the Admin data source for your rules schema ". However the installation guide, on page 37 step 5, tells creating only one JNDI name of the Admin data source, not specifying rules schema nor data schema. What should be entered for String Value of step 4 and 5 on Page 31?
Thanks,
Jun
Accepted Solution
Pegasystems Inc.
US
On Tomcat I have a datasource jdbc/AdminPegaRULES and then I have entries like this which would be the equivalent to the bindings you need to create in WAS. So in answer to your question #2 you would have a single jdbc/AdminPegaRULES datasource and then set both of the bindings to it.
<Environment name="prconfig/database/databases/PegaRULES/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>
<Environment name="prconfig/database/databases/PegaDATA/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>
I will check on first question if the binding identifiers should both be dataSourceAdmin.
Pegasystems Inc.
US
Please post the URL to the document on the pdn you are looking at. I don't see the references you mention in the guide I am looking at.
Pegasystems Inc.
JP
This is the document.
Accepted Solution
Pegasystems Inc.
US
On Tomcat I have a datasource jdbc/AdminPegaRULES and then I have entries like this which would be the equivalent to the bindings you need to create in WAS. So in answer to your question #2 you would have a single jdbc/AdminPegaRULES datasource and then set both of the bindings to it.
<Environment name="prconfig/database/databases/PegaRULES/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>
<Environment name="prconfig/database/databases/PegaDATA/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>
I will check on first question if the binding identifiers should both be dataSourceAdmin.
Pegasystems Inc.
US
I think that is a typo in the guide. Create one called PegaRULESDataSourceAdmin and another called PegaDATADataSourceAdmin.
- Created the JNDI binding identifier. E.g:
|
Binding identifier |
Name |
Value |
|
PegaRULESDatasourceAdmin |
prconfig/database/databases/PegaRULES/dataSourceAdmin |
jdbc/AdminPegaRULES |
I think that is a typo in the guide. Create one called PegaRULESDataSourceAdmin and another called PegaDATADataSourceAdmin.
- Created the JNDI binding identifier. E.g:
|
Binding identifier |
Name |
Value |
|
PegaRULESDatasourceAdmin |
prconfig/database/databases/PegaRULES/dataSourceAdmin |
jdbc/AdminPegaRULES |
Pegasystems Inc.
IN
Hello!
Thank you for identifying a gap in the documentation. I have raised a request internally with the Pega documentation team for a detailed investigation. I will update this post as I get to know more!
Thank you!
Pegasystems Inc.
US
Thank you for the feedback!
I've updated and reposted the IBM WebSphere guides and the Upgrade guides for the Pega 7.2.2 Platform. For example, see:
https://docs-previous.pega.com/pega-722-platform-installation-guide-ibm-websphere-and-microsoft-sql-server
Because the IBM WebSphere Application Server Liberty Core uses the server.xml file to configure communication between the Pega 7 Platform and the application server, the Liberty documentation does not change.