You can configure the conversion, collation, and case processing of Unicode data in TIBCO Object Service Broker. TIBCO Object Service Broker comes with a set of source configuration files and you can:
These source files may be used to generate binary configuration files which, if present, are read at initialization time replacing the default configuration data. The defaults in the system correspond to the IBM-037 code page. There are no External User Syntaxes defined by default.
The fifth source configuration file type is a ucm (UniCode Mapping) file which specifies a mapping between Unicode and a user-defined external syntax. You can have up to 16 files of this type to map up to 16 different external user syntaxes.
Data lines contain a single significant field: a hex value (0000 to FFFF) representing a Unicode code point. The data lines list the code points in order of their collation. The file must contain 65,536 unique data lines to specify all possible code points.
The format is described at http://icu.sourceforge.net/userguide/conversion-data.html. Data lines contain three significant fields, separated by white space:
This is a list of the names of the sample configuration files shipped with TIBCO Object Service Broker (on Solaris, the names are case sensitive). These files appear in your %HURON%/UnicodeConfig directory. The 3- or 4-digit numbers in the filenames refer to the IBM-xxx EBCDIC code page they are based on. Use the files as they are, or modify copies of them to create the desired configuration specification.
The unigen utility program is used to convert the source configuration files into binary files which will be read at initialization time. You need to run unigen to create binary files for the first 4 file types if the defaults are not suitable for you. You also need to run unigen for type 5 if you wish to define any external user syntaxes. All binary files generated by unigen should be written to the directory specified by the UNICODEDIR parameter or environment variable (see next section). Usage for the unigen executable is as follows:
You use the UNICODEDIR Data Object Broker parameter, the UNICODEDIR Execution Environment parameter, and the UNICODEDIR environment variable (for the offline batch utilities) to specify the directory where the Unicode configuration files reside, for example, %HURON%/database/UNICODEDIR.
If UNICODEDIR is not specified, no configuration files are read and the default configurations, which are part of the TIBCO Object Service Broker application, are used and no external user syntaxes are defined. If UNICODEDIR is specified, the TIBCO Object Service Broker initialization code looks for each of the first four files in the specified directory. If the file is present, TIBCO Object Service Broker uses it to configure its Unicode processing. Otherwise, it uses the default configuration for that file. All files with names matching UniXCnn (where nn may be from 01 to 16) are read and are used to configure up to 16 external user syntaxes XC01 to XC16.
