Configuring the ObjectServer for multicultural support
Tivoli Netcool/OMNIbus supports various single-byte and multi-byte character encodings for use in different locales.
About this task
The following ObjectServer properties are relevant for
multi-byte character processing:
- Store.LocalizedSort: Use this property to enable localized sorting. Localized sorting is disabled by default for optimal system performance.
- Store.LocalizedSortCaseSensitive: Use this property to control case sensitivity in localized sorting.
- RegexpLibrary: Use this property to enable use of the POSIX 1003.2 extended regular expression library (TRE). The standard NETCOOL regular expression library is enabled by default for optimal system performance.
You can set these properties in either of the following
ways:
- Set the properties in the ObjectServer properties file $NCHOME/omnibus/etc/servername.props, where servername is the name specified for the ObjectServer during its creation.
- Change the settings from the command line when starting the ObjectServer with the nco_objserv command. The command-line option for the Store.LocalizedSort property is -storelocalesort. The command-line option for the Store.LocalizedSortCaseSensitive property is -storecasesort. The command-line option for the RegexpLibrary property is -regexplib.
Note: If your username and password are being
verified against an external authentication source, you must check whether this source also supports
multi-byte characters. If multi-byte characters are not supported, you must specify usernames and
passwords with ASCII characters.
The
names of the following ObjectServer objects are restricted to ASCII
characters, starting with a letter or underscore, and continuing with
letters, digits, and underscores:
- Memstores
- Databases
- Tables
- Columns
- Restriction filters
- Privileges
- Trigger groups
- Triggers
- Signals
- Procedures
- Parameters
- Variables
- Properties
- File objects
File object names are restricted to the specified ASCII characters, whereas file path names are restricted to characters that are supported by the operating system. The character encoding that is used to create the files is the encoding that is used by the ObjectServer; this encoding might differ from that of the client.