Customizing the Product › Workbench Compatibility with Database Character Encoding › Workbench on Linux and zLinux

Workbench on Linux and zLinux

Note: The instances of Linux in this section refer to both the Linux and zLinux operating environments.

On Linux systems, character encoding varies depending upon the system’s locale settings. Linux distributions typically use UTF-8 as their default encoding. If your installation uses UTF-8 as the default character encoding for its locale, you can use one of the following methods to make the Workbench compatible with your CA Harvest SCM server:

• Change your entire Linux system to use a legacy (non-UTF-8) character encoding.

  This method is the easiest to implement. A single change to the operating system allows all CA Harvest SCM clients to work properly by default, but it may have side-effects on other applications.

• Make changes to the startup configuration for the Workbench so that it is started with character encoding settings that match the CA Harvest SCM database.

  If you select this method, the CA Harvest SCM agent expects files on your file system to be named with a character encoding that matches your database. Files checked-out from CA Harvest SCM will use a legacy (non-UTF-8) character encoding for their names on the file system, even though other files on your file system are likely to use UTF-8 encoding for their names. New files being checked in to CA Harvest SCM must also have names encoded in a legacy (non-UTF-8) character encoding.

The method that you select depends upon your environment and needs.