Question

4
Replies
672
Views
GunawanD Member since 2013 14 posts
Accenture
Posted: July 31, 2017
Last activity: September 12, 2017
Closed

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:

<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaDATA"/>
<env name="database/databases/PegaRULES/defaultSchema" value="PegaRULES" />
<env name="database/databases/PegaDATA/defaultSchema" value="PegaDATA" />

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

  1. How do achieve that so that Pega instance 2 can read from schema PegaRULESCRM and PegaDATACRM?
  2. 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

Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn