JVM-Level TRA File Configuration

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.

At run time, 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, 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 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 additional information about system configuration, see the following:

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.

Note: 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-2.0.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 directory BE_HOME/lib/ext/tpcl.
This location is specified in the standard classpath in the be-engine.tra file as shipped.
For instructions on configuring the system to work with ActiveMatrix BusinessWorks see ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developer’s Guide.

Subtopics