To properly interpret text, such as member names, Essbase must know how it is encoded. Many files contain an encoding indicator, but occasionally you may be prompted to specify the encoding; for example, in the following cases:
Administration Services creates a file and stores it in a different location than the Essbase Server
Administration Services reads a file created by a non-Unicode, pre-7.0 release of Essbase
The type of encoding indicator depends on the type of file:
Files that are internal to applications and databases and that users cannot directly edit are primarily binary files and do not contain encoding indicators.
Character text in these files is encoded based on the application mode:
Binary files that you can edit (such as outline and rules files)
As needed, Essbase keeps track internally of whether the character text is in UTF-8 encoding. If not UTF-8, Essbase uses an internal locale indicator to identify the locale used for character text encoding.
The following text files that you can edit use a UTF-8 signature or a locale indicator to indicate their encoding:
Caution! | Do not use non-Unicode-encoded files containing locale indicators with pre-7.0 release Essbase Server installations, which are not Unicode enabled. To remove the locale indicators, use Essbase Unicode File Utility. See Essbase Unicode File Utility. |