install 2 different pega instances on single Jboss instance.
Hi Support,
trying to install 2 different pega instances on single Jboss instance. is this supported setup by Pega ? if yes, can you pleas share an example of datasource setup in jboss domain.xml etc. please.
Thanks !
Pegasystems Inc.
IN
You cannot maintain multiple pega instance in single jboss instance because in Pega either you can have single schema or split schema(rules and data) .
There’s no way you can specify multiple schemas .
Let us know if you have any further questions .
Thanks,
Arun
Scotiabank
CA
Hi Arun and pega support,
thanks for reply, how about if we have 2 different databases to hold the schemas of each pega instance? can these 2 pega instances share same jboss instance? my guess is that, maybe pega code has 'hard-coded" JNDI reference names, that might be the root cause of conflict in this setup ?
thanks!
Frank
Pegasystems Inc.
GB
Hi Frank,
This is more like a JBoss maintenance task. You could have a separate startup script pointing to a different standalone.xml.
After deploying the first instance, the standalone.xml will be updated with <deployments> elements like below:
<deployments>
<deployment name="prhelp.war" runtime-name="prhelp.war">
<content sha1="9b479b8967dbc04efd767e28877817034efd02a1"/>
</deployment>
<deployment name="prpc_j2ee14_jboss61JBM.ear" runtime-name="prpc_j2ee14_jboss61JBM.ear">
<content sha1="0eddcecbdaa06954d3d233bb7d79079431d1a121"/>
</deployment>
<deployment name="prsysmgmt_jboss.war" runtime-name="prsysmgmt_jboss.war">
<content sha1="cb54c39e0f96a7b6d404e6c5f7f297ed21bca501"/>
</deployment>
</deployments>
The deployment contents will be stored in %JBOSS_HOME%\standalone\data\content directory.
In the deploying process of the second instance, new contents will be also be created in %JBOSS_HOME%\standalone\data\content directory. However, JBoss now believes the content in the first deployment are redundant and will remove these files. At this point you will only be able to startup the second instance, but not the first one.
Hi Frank,
This is more like a JBoss maintenance task. You could have a separate startup script pointing to a different standalone.xml.
After deploying the first instance, the standalone.xml will be updated with <deployments> elements like below:
<deployments>
<deployment name="prhelp.war" runtime-name="prhelp.war">
<content sha1="9b479b8967dbc04efd767e28877817034efd02a1"/>
</deployment>
<deployment name="prpc_j2ee14_jboss61JBM.ear" runtime-name="prpc_j2ee14_jboss61JBM.ear">
<content sha1="0eddcecbdaa06954d3d233bb7d79079431d1a121"/>
</deployment>
<deployment name="prsysmgmt_jboss.war" runtime-name="prsysmgmt_jboss.war">
<content sha1="cb54c39e0f96a7b6d404e6c5f7f297ed21bca501"/>
</deployment>
</deployments>
The deployment contents will be stored in %JBOSS_HOME%\standalone\data\content directory.
In the deploying process of the second instance, new contents will be also be created in %JBOSS_HOME%\standalone\data\content directory. However, JBoss now believes the content in the first deployment are redundant and will remove these files. At this point you will only be able to startup the second instance, but not the first one.
To overcome this, I copied the content of %JBOSS_HOME%\standalone\data\content before deploying the 2nd instance and then merge it back after the deployment process of the 2nd instance.
So far, I am unable to find an easier way.
Regards
Simon