System-Level (TRA File) Configuration

System-Level (TRA File) Configuration
The engine executable files each have an associated configuration file with the extension .tra. These files are updated only for system-level property settings. All other runtime project configuration is entered in the CDD file.
As needed, configure the TRA file for system-level settings that must be set before the TIBCO BusinessEvents engine starts. Other settings go in the CDD file.
Java and JVM Level Settings
TRA file settings at this level are not documented here. See Java documentation as needed. The TRA file also contains some helpful comments for such properties.
Update Classpath and Environment Variables
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 (see Manually Copy Custom Function and Third-Party Jars at Deploy-time).
For the design-time equivalent of these tasks, see Adding and Working with Launch (Debug or Run) Configurations 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 Integration with TIBCO ActiveMatrix BusinessWorks
For instructions on configuring the system to work with ActiveMatrix BusinessWorks, see Chapter 21, ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developer’s Guide, especially the topics Configuring the Environment for ActiveMatrix BusinessWorks Containers and Configuring the Environment For TIBCO BusinessEvents Containers.
Property for Cache Based Object Management on AIX
When TIBCO BusinessEvents installed on AIX uses use cache-based object management, you must add this property to all TRA files, and set the value to true.

 
java.net.preferIPv4Stack=true

 
If you do not add this property, you see the following exception:
java.net.SocketException: The socket name is not available on this system
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. See Chapter 6, Basic MM Configuration for details.
JMX Properties for TIBCO BusinessEvents Monitoring and Management
For the MM component to monitor the cluster, various JMX settings are required. For details see Configure JMX Properties in To-Be-Monitored Engine TRA Files.