Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 JVM-Level TRA File Configuration

Chapter 2
The engine executable files each have an associated configuration file with the extension .tra. These files are updated only for JVM-level property settings.
As needed, configure the TRA file for JVM-level settings that must be set before the TIBCO BusinessEvents engine starts. Other settings go in the CDD file. JVM-level settings in the CDD file are ignored.
For non-TIBCO BusinessEvents related JVM settings, see Java documentation as needed. The TRA file also contains some helpful comments for such properties.
Updating Classpath, Environment Variables, Path, and Copying JAR Files
At runtime the software uses the classpath set in the be-engine.tra file to locate the libraries (third-party libraries and custom function libraries) needed to execute the code. Ensure that you have added all the classpaths needed before you deploy.
For example, you must update the classpath to specify the locations of libraries for TIBCO Enterprise Message Service, TIBCO Rendezvous, third party software, and custom functions.
In some cases you must also copy the JAR files. If a JAR has dependencies on native libraries, edit BE_HOME/bin/be-engine.tra and as needed, update PATH LD_LIBRARY_PATH, SHLIB_PATH, and LIBPATH as needed, depending on the operating system.
For the design-time equivalent of these tasks, see Adding and Working with Launch (Debug or Run) Configurations and Enabling the Test Connection Feature in TIBCO BusinessEvents Developer’s Guide.
For TIBCO Enterprise Message Service and TIBCO Rendezvous Channels
If the software is installed locally, set the EMS_HOME variable or RV_HOME variable in the BE_HOME/bin/be-engine.tra files. The classpath already contains entries for these variables.
For JMS channels that use TIBCO Enterprise Message Service version 5, installed locally, you must change the existing setting in the be-engine.tra property tibco.env.STD_EXT_CP: Change %EMS_HOME%/clients/java to %EMS_HOME%/lib.
Local installation is the only option for TIBCO Rendezvous, which is not a pure Java API.
If TIBCO Enterprise Message Service is not installed locally, copy the jms.jar and tibjms.jar files to BE_HOME/lib/ext/tpcl. This location is specified in the standard classpath in the be-engine.tra file as shipped.
For WebSphere MQ Channels
Copy the copy the relevant JAR files and the binding file to the following directory:
BE_HOME/lib/ext/tpcl
This location is specified in the standard classpath in the be-engine.tra file as shipped.
For Integration with TIBCO ActiveMatrix BusinessWorks
For instructions on configuring the system to work with ActiveMatrix BusinessWorks, see Chapter 38, ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developer’s Guide.
Property for Cache Based Object Management on AIX
When TIBCO BusinessEvents is installed on AIX and uses cache-based object management, you must add this property to all TRA files, and set the value to true.

 
java.net.preferIPv4Stack=true

 
Remember to set this property on all internal TIBCO BusinessEvents engines’ TRA files too, such as in be-mm.tra for the TIBCO BusinessEvents Monitoring and Management (MM) server and the MM broker properties set in the MM CDD file. Add-on products also have engine TRA files you must update.
If you do not add this property, you see the following exception:
java.net.SocketException: The socket name is not available on this system
 
Setting JMX Properties
For TIBCO BusinessEvents Monitoring and Management
For the MM component to monitor the cluster, you must configure various JMX settings. For details see Configure JMX Properties in To-Be-Monitored Engine TRA Files.
For Other Purposes
Using a JMX-compliant monitoring tool such as JConsole can be useful for other purposes. For example, MBeans enable you to see cache details if you are using Coherence as the cache provider.
To enable a JMX-compliant monitoring tool to view the exposed MBeans, set these properties in the BE_HOME/bin/be-engine.tra files:

 
java.property.com.sun.management.jmxremote=true
java.property.com.sun.management.jmxremote.ssl=false
java.property.com.sun.management.jmxremote.port=5558

 
You can also set the JMX connector port for deployment with TIBCO Administrator using this CDD property:
be.engine.jmx.connector.port

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved