Resolution:
Description:
===========
How to set a JMX port for each service instance deployed to TIBCO Administrator?

Environment:
============
TIBCO BusinessEvents 4.x
All Operating Systems

Resolution:
===========
It was not possible to choose an engine's JMX port number in the CDD. You can now add the following property to the CDD at the processing unit level and set the port number as desired:

be.engine.jmx.connector.port

This property is effective with Cache OM only. (It is ignored and is harmless in In Memory OM.) Depending on your configuration you may have to create
additional PU definitions in the CDD so that you can assign different connector ports for PU instances.

If be.engine.jmx.connector.port is set, either do not set com.sun.management.jmxremote.port in the tra file or set it to a different
port number (in this case two JMX connections will be open).

Setting a JMX port for each Service Instance in Administrator for TIBCO BusinessEvents(BE) 4.0.1 deployments.