Enabling JMX monitoring
Before TrueSight Middleware and Transaction Monitor can monitor the process instances, JMX access must be enabled in the TIBCO BusinessWorks engine.
Always refer to the TIBCO BusinessWorks documentation to understand the appropriate settings for the version of TIBCO BusinessWorks being monitored. Enabling JMX Monitoring is covered in Appendix B of the TIBCO BusinessWorks Administration Guide. The following should only be used as a guide.
In the case of a standalone BusinessWorks application, create a new .tra file based on your existing .tra file, and use the "-propFile" argument to the bwengine command to start the application using the new properties.
In the case of a deployed BusinessWorks application, modify the .tra after the BusinessWorks application has been deployed. It is important to locate the correct file.
For example in a domain named BTMDomain, and an application called BTMApplication, the .tra file would be deployed to %TIBCO_HOME%/tra/domain/BTMDomain/application/BTMApplication/BTMApplication-Process_Archive.tra.
In either case, the following properties should be added to the .tra file:
Jmx.Enabled=true
java.property.com.sun.management.jmxremote=true
java.property.com.sun.management.jmxremote.port=$port_number$
java.property.com.sun.management.jmxremote.authenticate=false
java.property.com.sun.management.jmxremote.ssl=false
The port number must be an available, unique port number. The same port number cannot be used by more than one application.
Note that these settings enable unauthenticated access to the JMX agent. Review the settings to be sure that they comply with your site's security policy. Increased security can be configured, but ensure that the BTM JMX Service configuration uses a matching configuration.
You can put these settings in the bwengine.tra file (e.g. %TIBCO_HOME%/bw/5.10/bin/bwengine.tra), so that they are in your applications .tra file after deployment by default. However, while convenient, this enables JMX monitoring for all deployed applications.