ubb2ex — Oracle Tuxedo UBB Configuration file migration to Enduro/X
Tuxedo UBBCONFIG converter to Enduro/X configuration parses Tuxedo text version of configuration and produces as close as possible Enduro/X configuration.
It is expected that provided UBBCONFIG is valid. ubb2ex performs limited validation of the input configuration file, and if file is invalid, at some scenarios, error cause may be determined only in debug mode (-D5 flag) and by checking the stack trace/line number in the ubb2ex.pscript file (provided in distribution).
As input UBBCONFIG_file or stdin is used. Enduro/X parses the structure of the UBB configuration file, loads it into platform script data structures, after which a script (built in ubb2ex or provided from command line) starts to compose the equivalent Enduro/X configuration. Additionally converter script deference ENVFILE from the UBB configuration and copies values to app.ini [@global] section.
ubb2ex produces following files TUXCONFIG directory:
The migration tool produces different sets of configuration files, because Enduro/X uses peer-to-peer clustering principles, thus for each of the peer servers different set of files are produced (and separated by lower-case LMID identifier from UBB configuration).
Additionally as the result directories are created (if not exist):
Where ${NDRX_APPHOME} is determined by following principles: It is common part between Tuxedo’s APPDIR and TUXCONFIG. If common part is not found (i.e. it is root directory /), then ${NDRX_APPHOME} is set to APPDIR.
Migration script supports following Tuxedo features:
Tool performs mappings of the such processes as:
Table 1. UBBCONFIG - Enduro/X process mappings
Tuxedo process | Enduro/X process |
---|---|
TMS | |
TMSYSEVT and TMUSREVT | |
TMQUEUE and TMQUEUE | |
WSL and JSL | restincl(8) from endurox-connect package. Basic configuration is provided. |
For more details on how the configuration is mapped to Enduro/X, please read Migrating from Oracle Tuxedo to Enduro/X user guide.