This documentation supports the 9.1 version of BMC Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.



Unicode compatibility considerations

The following topics are provided:

Non-Unicode and version 9.x

A non-Unicode client can access specific language data stored on a Unicode BMC Remedy AR System server installed on a Unicode database if the non-Unicode client is installed on the computer with the same character set to which that language belongs.
For example, if an English computer has Unicode BMC Remedy AR System server installed on it with a Unicode database, and the data stored is in German, Japanese, and Russian, then:

  • A mid tier that is installed on a Japanese computer (Japanese character set) can work with the Japanese data on that database.
  • A mid tier that is installed on a French, English, or Spanish computer (Western European character set) can work with German data on that database.
  • A mid tier that is installed on a Bulgarian computer (Cyrillic character set) can work with Russian data on that database.

Unicode clients and non-Unicode servers

You can run a Unicode client on a non-Unicode server without restrictions.

BMC Remedy AR System components and Unicode considerations

If you run the following BMC Remedy AR System components in Unicode mode, they do not corrupt data when run against a Unicode-enabled BMC Remedy AR System server:

  • BMC Remedy AR System server
  • BMC Remedy AR System Plug-in Server
  • BMC Remedy Approval Server
  • Assignment Engine
  • BMC Remedy Distributed Server Option (DSO)
  • Remote Desktop Protocol (RDP)
  • BMC Remedy Email Engine

The following sections discuss considerations for running specific BMC Remedy AR System components with Unicode.

BMC Remedy AR System server

A BMC Remedy AR System server running in Unicode mode might be required to run another program (as a Run Process action, for example) and to accept characters written by the program through the program's standard output.

On UNIX systems, the program must write UTF-8 characters to its output. For example, a BMC Remedy AR System server running in Unicode mode requires data returned from a Set Fields filter action to be in UTF-8. A non-Unicode server running in the Japanese locale requires data to be returned in EUC.

On Windows systems, BMC Remedy AR System checks the first 2 bytes of the program's output. If it is in UTF-16 character encoding, BMC Remedy AR System treats it as Unicode. Otherwise, BMC Remedy AR System treats the program's output as characters from the system's active code page. For example, a Japanese server runs on an operating system using Windows codepage 932 (Shift-JIS character set).

Plug-in server

Two codesets affect the plug-in server and the plug-ins that run under it:

  • The codeset in which the server provides characters when it calls the plug-in's callback routines
  • The codeset that the plug-in uses when it makes API calls to the server

The server always uses its own codeset when delivering characters to plug-in callback routines. Therefore, a Unicode server always delivers characters in the UTF-8 codeset.

Mid Tier

Mid Tier is a Unicode client for the BMC Remedy AR System server. A single mid tier can manage clients and transfer data in any language supported by BMC Remedy AR System.

The mid tier's Flashboards service renders characters for display. Ensure that fonts are available for the characters of all languages in which you provide Flashboards.

API programs

When operating in Unicode mode, the API accepts and returns characters in the UTF-8 character encoding. It does not support the UTF-16 character encoding.

runmacro

The runmacro program, which is sometimes used to do batch exports of data, is not Unicode-safe. Do not use runmacro with a Unicode server.

BMC Remedy ODBC driver

The BMC Remedy ODBC driver is a multithreaded, ODBC 3.5-compliant Unicode driver that runs a BMC Remedy AR System API client under Windows.

If you connect ANSI applications to a BMC Remedy AR System Unicode server through the BMC Remedy ODBC driver, any data transferred is converted from ANSI to UTF-16, and then from UTF-16 to UTF-8. If the BMC Remedy AR System server is non-Unicode, the data is converted from ANSI to UTF-16, from UTF-16 to UTF-8, and then from UTF-8 to the server's native character set.

Utilities

The following utilities are compatible with Unicode servers:

  • artext
  • arhelp
  • archgsel
  • archgid
  • arworkflow
  • ardisabled
  • arlabel

BMC Remedy Developer Studio

BMC Remedy Developer Studio is Unicode-safe. It has no character set restrictions.

BMC Remedy Data Import

BMC Remedy Data Import is Unicode-safe whether you run it under standard operating conditions or from the command line (arimportcmd).

For BMC Remedy AR System use the Java-based import utility. For more information, see  Enabling the Data Import utility  in the BMC Remedy AR System documentation.

BMC Remedy AR System Administration Console

The BMC Remedy AR System Administration Console form is Unicode-safe.

For more information about the console, see  Configuring AR System servers  in the BMC Remedy AR System documentation.

BMC Remedy Migrator

BMC Remedy Migrator is Unicode-safe.

Was this page helpful? Yes No Submitting... Thank you

Comments