Displaying unicode and non-unicode characters
The probe can support multibyte characters and so can display both unicode and non-unicode characters.
Before using the probe to process data that contains multibyte characters, perform the following steps:
- Ensure that the Nokia NFM-P server is configured to send data
to the probe in UTF-8 format.
The probe can support only multibyte characters if the incoming data has been configured in correct UTF-8 format. Consult your Nokia NFM-P server documentation for details about how to configure the server to send data in UTF-8 format.
- Check that the probe server has UTF-8 support enabled and that
the correct locale is set; for example, set the locale to Chinese.On Windows operating systems, use the following steps:
- Access the Region and Language section of the Control Panel.
- Select the tab.
- Select .
- Select the tab.
- Select .
- Select .
- Click OK.
- Click OK.
On UNIX and Linux operating systems, set the system locale using theLANG
andLC_ALL
environment variables:export LANG=zh_CN.utf8 export LC_ALL=zh_CN.utf8
- Restart the ObjectServer.
- Configure the ObjectServer to enable the insertion of UTF-8 encoded data. See the Netcool/OMNIbus Installation and Deployment Guide.
- If you are running the probe on a Windows operating system, you must use the -utf8enabled command-line option each time you start the probe.
Note: Netcool/OMNIbus can only receive multibyte characters
from the Network Element (NE) custom properties using the
additionalText
field
sent in the alarm. The custom text field also supports multibyte characters.
However, this is an attribute of the alarm policy, which is not sent
in the alarm. UTF-8 encoding is used for all fields in the Nokia NFM-P
server, but multibyte character support only applies to these few
selected attributes. This is because the NE does not support multibyte
characters.