Closed
Multiple Pega instances on same box
hi,
We have a VM where we have JBOSS 6.4 and Pega 7.3 running hosting our application 1. We are currently developing application 2 and want to do it on later (or latest) version of Pega. Hence, the advice we have worked on is that we can get JBOSS 7.1 installed on the same VM (on a different JVM) and have Pega 8.5 deployed on that to host the new application. However, we are facing challenges as the new installation is trying to listen to the ports already used by previous JBOSS. Wondering if anyone has been in the same boat and what magic did they do to resolve the issue.
***Edited by Moderator Marissa to update Platform Capability tags****
To see attachments, please log in.
Posted: 5 years ago
Pegasystems Inc.
SE
Hi,
We have this configuration working. Base install is 8.2 (but that should not matter), on the same machine we have a secondary instance of version 8.5.
Apart from changing the listener ports (obviously, in the Jboss setup) we saw that the second instance could not be started with the first one running.
To successfully start both instance at the same time we had to also switch the ports for several services (otherwise the second instance, no matter which, would not come up) on the secondary instance. To do that, create four Dynamic System Setup values as follows:
All: Owning Ruleset - "Pega-Engine"
Description: Stream pyBrokerPort default 9092
prconfig/dsm/services/stream/pyBrokerPort/default
set this to eg 19092
Description: Stream pyKeeperPort default 2181
prconfig/dsm/services/stream/pyKeeperPort/default
set this to eg 12181
Description: Stream pyJmxPort default 9999
prconfig/dsm/services/stream/pyJmxPort/default
set this to eg 19999
Description: Stream pyPort default 7003
prconfig/dsm/services/stream/pyPort/default
set this to eg 17003
Restart the instance, start the other instance. This solved it for us.
https://community.pega.com/knowledgebase/articles/decision-management-overview/advanced-configurations-stream-service#6