Limitation of SPS Group Configuration
I had multiple instances of SPS on my machine.
SPS1 with ports 8442, 8443, 8080, 543, 8005 and 8009.
SPS2 with ports 9442, 9443, 7070, 643, 7005 and 7009.
I grouped these 2 SPS instances running on the same box. I then created a new VH on this group. After that SPS2 wouldn't start. The reason being the configurations got synced i.e. Apache Ports of SPS1 8442 got replicated into Apache ports of SPS2 (thus overwritting original port of 9442). Hence SPS2 started listening on 8442. So simple logic how can 2 process start using same port on the same server, one has to fail.
We support multiple instances of SPS on the same server. However when it comes to using the SPS Group feature we override the support of multiple instances of SPS. Hence at the onset that if we are using SPS Group Feature, then group SPS on different servers. Do not Group SPS on the same server OR one may run into these challenges.
Thought to share this finding and I've asked this to be updated in Doc WiKi too.
Message was edited by: Hubert Dennis
Included a Best Practice Diagram