Question
Deploying multiple Pega instances (different Pega instances) on the same WebSphere App server
Currently, we are trying to setup more than 1 Pega instance in the same WebSphere App Server.
We managed to change all JNDIs (explicittempdir, ejb/EngineBMT, etc.) to be unique.
One thing we are unable to change is Name space bindings. The Name space binding need to be unique
- prconfig/database/databases/PegaRULES/defaultSchema
- prconfig/database/databases/PegaDATA/defaultSchema
- prconfig/database/databases/PegaRULES/dataSourceAdmin
- prconfig/database/databases/PegaDATA/dataSourceAdmin
What we've tried to workaround the issue is we change prconfig.xml to include defaultSchema.
Pega instance 1:
Pega instance 2:
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULESCRM"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaDATACRM"/>
<env name="database/databases/PegaRULES/defaultSchema" value="PegaRULESCRM" />
<env name="database/databases/PegaDATA/defaultSchema" value="PegaDATACRM" />
When I started Pega instance 2, the server log showed the following:
(ccess.DatabaseConfigurationMap) INFO - Base database information:(ccess.DatabaseConfigurationMap) INFO - Database name:pegadata(ccess.DatabaseConfigurationMap) INFO - Defined by:JNDI name(ccess.DatabaseConfigurationMap) INFO - Data source name:java:comp/env/jdbc/PegaRULESCRM(ccess.DatabaseConfigurationMap) INFO - Minimum connection count:0(ccess.DatabaseConfigurationMap) INFO - Maximum connection count:unlimited(ccess.DatabaseConfigurationMap) INFO - Default Schema:PegaDATA(ccess.DatabaseConfigurationMap) INFO - Base database information:(ccess.DatabaseConfigurationMap) INFO - Database name:pegarules(ccess.DatabaseConfigurationMap) INFO - Defined by:JNDI name(ccess.DatabaseConfigurationMap) INFO - Data source name:java:comp/env/jdbc/PegaDATACRM(ccess.DatabaseConfigurationMap) INFO - Minimum connection count:0(ccess.DatabaseConfigurationMap) INFO - Maximum connection count:unlimited(ccess.DatabaseConfigurationMap) INFO - Default Schema:PegaRULES
Question
- How do achieve that so that Pega instance 2 can read from schema PegaRULESCRM and PegaDATACRM?
- How do change the lookup name so that Pega will lookup different key instead? Like the example below, instead of looking up by PegaRULES database, it should look up by using PegaRULESCRM.
- prconfig/database/databases/PegaRULESCRM/defaultSchema
- prconfig/database/databases/PegaDATACRM/defaultSchema
- prconfig/database/databases/PegaRULESCRM/dataSourceAdmin
- prconfig/database/databases/PegaDATACRM/dataSourceAdmin
Thanks
Hi HabeebBaig,
There are both using the same app profile. If they are using different WebSphere app profile, we don't have this issue.
Thanks
Hi,
If you are using different app profiles then I believe that's way it should be.
Thanks,
Hi,
Please create data source node level, it should resolve the issue. Please give JNDI name as jdbc/PegaRULES for both nodes but at the time creating datasource you can map it to different schemas. You can create name space bindings also node level.
I hope this will resolve the issue.
Probably in your case the Pega instance 2 is pointing to the same datasource with name space bindings given for pega instance 1.
Can you help us with some more information as below?
Are both nodes on different app profiles?
What is the scope of datasource jdbc/PegaRULES configured? Cell/Node?
I presume if both nodes are configured with different app profiles and pointing to same JNDI but the difference can be made from their name space bindings.