How to check the BusinessWorks runtime environment
BusinessWorks is a Java application that relies on a Java Virtual Machine (JVM) in the runtime environment.
To make the BusinessWorks JVM independent from the local user environment a JVM wrapper, the TIBCO wrapper, is used to manage the runtime environment as a set of properties defined in a tra file, this includes the JVM classpath, JVM properties, and etc…
While analyzing runtime issues it is sometimes useful to check the exact runtime environment of a BusinessWorks 6.X appnode or a BusinessWorks 5.X engine.
This can be done using the — debug option (with two hyphens) of the TIBCO Wrapper and this article is meant to explain how to use this option in BusinessWorks 6.X context and BusinessWorks 5.X context.
Businessworks 6.X
This can be done with the following:
. Change directory to <TIBCO_HOME>\bw\6.X\domains\<DOMAIN_NAME>\appnodes\<APPSPACE_NAME>\<APPNODE_NAME>\bin
. Edit the startBWAppnode.bat script (or startBWAppnode.sh in Linux)
. Add the — debug (with two hyphens) option to the command
. Start the appnode from the command line using the startBWAppnode.bat script
. At start-up the wrapper will write the runtime environment details in the stdout
You can see below an example showing the actual values of the tra file properties and the actual values of the JVM options.
Businessworks 5.X
This can be done with the following:
. Change directory to <DOMAIN_HOME>\application\<APPLICATION_NAME>
. Edit the <Application_Name-ProcessPackage_Name>.cmd script (or .sh script in Linux environment)
. Add the — debug option (with two hyphens) to the command
. Start the application from the command line using the .cmd script
. At start-up the wrapper will write the runtime environment details in the stdout
You can see below an example showing the actual values of the tra file properties and the actual values of the JVM options.
Additional elements
This approach can be used with any TIBCO components using the wrapper (Hawk components, BusinessWorks 5.X adapters, etc).
