Invoking the Tool
Prerequisites
- Before running TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE), shut down the tibcohost instance you are managing to avoid severe errors by running the "
tibcohost stop -wait true
" command. The TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) does NOT verify that the tibcohost is shut down. - When run in the update mode, the JRE Updater tool only updates files in the TIBCO_HOME from which it is run. However, in the discover mode, it discovers all tibcohost and node instances in a TIBCO_CONFIG_HOME irrespective of which TIBCO_HOME they point to.
- The operation of the utility depends on the location from where the utility is being run. For example, if the tool is run from $TIBCO_HOME/amx/3.4.2/bin/, only the tibcohost and node instances that are of version 3.4.2 are discovered.
- The bit version of the JRE to which you are upgrading must match the bit version of the operating system architecture.
Modes
- Interactive Mode (default) — To run the TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) in the interactive mode, run the following command from
<TIBCO_HOME>/amx/<version>/bin/.
amx_jre_updater.exe
(Microsoft Windows)./amx_jre_updater
(UNIX)The tool enters an interactive shell where you can run all TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) commands, including any command-specific arguments. The exit command exits the shell.
- Non-interactive Mode—To run the TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) in a non-interactive (scripted) mode, run the following from
<TIBCO_HOME>/amx/<version>/bin/:
./amx_jre_updater <command> -jreHome <JRE_HOME_PATH> <Optional arguments>
(UNIX)amx_jre_updater.exe <command> -jreHome <JRE_HOME_PATH> <Optional arguments>
(Microsoft Windows)where
<command>
is one of the TIBCO ActiveMatrix Updater Tools for Java Runtime Environment (JRE) commands, followed by command-specific arguments.
Note:
- For the
-jreHome
argument, provide the JRE_HOME (and not the JDK_HOME) bundled inside the JDK. If you point to JDK_HOME, the path updated for .tra or .ini does not work for Runtime. - The tool uses the existing JRE when it is invoked. The tool’s own TRA is updated during every update operation.