Support Article
Not able to connect to PegaData in split schema
SA-25441
Summary
During upgrade from PRPC 6.2 SP2 to split-schema configuration, application is not able to connect to the PegaData.
Upon binding Data Source to the PegaData schema, the system does not boot. Namespace bindings are configured at node level for Websphere 8 Node
Error Messages
[7/6/16 14:14:55:134 EDT] 00000051 PRBootstrapDa Z com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource Loading bootstrap properties from /prbootstrap.properties
[7/6/16 14:14:55:136 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:55:137 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:55:137 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:55:138 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find prconfig in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:55:138 EDT] 00000051 PRBootstrapDa Z com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource Bootstrap datatables schema: null
[7/6/16 14:14:56:178 EDT] 00000051 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Engine schema defined in allclasses: null
[7/6/16 14:14:56:179 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:56:179 EDT] 00000051 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find prconfig in the local JNDI context, skipping prconfig setting lookup
[7/6/16 14:14:56:180 EDT] 00000051 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Engine classes schema: null
[7/6/16 14:14:56:180 EDT] 00000051 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Assembled classes schema: null
Steps to Reproduce
Configure PRPC SplitSchema Namespace bindings at IBM Websphere "Node" or "Cluster" scope.
Root Cause
Refer to the product documentation: https://pdn.pega.com/documents/pega-72-platform-installation-guide-websphere-and-db2-luw
The spilt schema namespace bindings are looked up from PRPC engine code using a local java JNDI context (Server roots partition) and existing lookup code does not handle lookup of namespace bindings bound to Node persistent or Cell persistent JNDI partitions.
Resolution
Make the following change to the operating environment:
- Delete the PegaRULES and PegaDATA namespace bindings from "Node" scope and re-create the same bindings at the "Server" scope.
- If there are more than one PRPC Node or servers, one must re-create the same bindings for each of the servers.Once the bindings successfully defined at the "Server" scope, restart each of the servers. This will help you get the PRPC application started with the spilt schema configuration.
Published July 26, 2016 - 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.