Copyright © TIBCO Software Inc. All Rights Reserved |
After the cluster engines are started, they use JMX MBeans to expose monitoring and management information to the MM server, and for remote method invocation. The JMX port number must be specified before the engine’s JVM starts. A variable for the port number is provided in the TRA file so that the actual value can be specified before the engine starts.
Do the following for all TRA files for all monitored TIBCO BusinessEvents engines as needed.To expose JMX for monitoring and management (without authentication), uncomment this property:Ensure that the value of the port property is set to this literal value: %jmx_port%. The actual value is substituted at runtime. See How the JMX Remote Port Number is Set at Runtime.
When more than one PU (engine) is deployed on the same host, ensure that a different JMX port is used for each of the PUs, in the site topology file.java.property.be.engine.jmx.connector.authenticate=trueConfigure the authentication technology you want to use in the emonitor project as explained in Chapter 13, Configuring User Authentication.When you use the MM UI to start TIBCO BusinessEvents engines remotely, MM reads the port number from the PU configuration setting in the site topology file. See (Processing Unit Settings.)MM passes this value to the TRA file’s jmx_port variable, in the command line it composes when starting a TIBCO BusinessEvents engine: --propVar jmx_port=portnum.
If you start an engine manually from the command line, provide the port number in the same way, that is, using the option --propVar jmx_port=portnum.Use the same port number as specified in the PUC so that MM treats the engine as a predefined engine. If you use a different number, the engine starts as an unpredefined engine. See Predefined and Unpredefined Members.
Copyright © TIBCO Software Inc. All Rights Reserved |