Change the character encoding of the log file for a BlackBerry EnterpriseServer component
You can change the character encoding of the log files of a BlackBerry Enterprise Server component so that the encoding
supports the tools that you use to parse and examine the log files. You can specify a different character encoding for each
BlackBerry Enterprise Server component. You can use the ANSI, UTF-8, and UTF-16LE character encoding methods.
1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution
topology > BlackBerry Domain > Component view > Logging.
2. Click the instance that contains the logging settings that you want to change.
3. On the Logging details tab, click Edit instance.
4. In each section, in the Log encoding drop-down list, click one of the following character encodings:
ANSI
UTF-8
UTF-16LE
5. Click Save all.
6. On the Servers and components menu, locate and restart the components that contain the logging settings that you
changed.
Related information
Restarting BlackBerry Enterprise Server components, 392
Restore logging settings to default values for all components
1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution
topology > BlackBerry Domain > Component view > Logging.
2. Click the instance that you want to restore to default values.
3. On the Logging details tab, click Edit instance.
4. Click Reset logging defaults.
5. Click Save all.
6. For the changes to take effect, perform any of the following actions to restart the BlackBerry Enterprise Server
services:
To restart services other than the BlackBerry Administration Service, on the Servers and components menu,
locate and restart the services that you restored to default values.
To restart the BlackBerry Administration Service, on the computer that hosts the BlackBerry Administration
Service, in the Windows Services, restart the BlackBerry Administration Service - Native Code Container service.
Administration Guide BlackBerry Enterprise Server log files
438