Since I can't get the built-in broker to spawn network connections I am now trying to convince the NMR to use an external broker for JMS flow.
There are quite a few examples showing how to do that with SMX3, but I cannot find anything on how this is to be configured on SMX4.
Basically, say I have two SMX instances, smx1 and smx2, and I want to use a single, external AMQ broker for JBI clustering, where do I configure that?
I still cannot figure out why the network connectors in the embedded broker did not start. However, since I am using external brokers for JBI clustered I worked around this problem.
Thanks for the posted link. The document is not clear on how to change the default cluster engine's JMS broker. What I did is put an 'jbi-cluster.xml' in /deploy directory and in there, changed the connection factory to a custom one:
<property name="destinationName" value="$" />
JBI clustering is still not working and I think I made two blunders in the process:
1) I assumed etc/activemq-broker.xml is the file to edit. In fact it is not; I have to copy it to deploy/activemq-broker.xml and make configuration changes there. This is counter-intuitive. I will test the configuration more but looks like now my original question is answered.
2) creating an additional jbi-cluster.xml under deploy/ directory actually resulted in TWO clusterEngine being created. So I still cannot make the cluster engine use an external JMS broker.
Any pointer on the second problem will be much apprieciated!
problem still not solved - can't configure smx to use an external broker for clustering