Customizing the Product › Workbench Compatibility with Database Character Encoding › Web Server on UNIX

Web Server on UNIX

On UNIX systems, the Java System Property file.encoding varies depending upon the system’s locale settings. Most Linux distributions use UTF-8 as their default encoding. If file.encoding is set to UTF-8, use one of the following methods to make Java file.encoding compatible with the CA Harvest SCM database encoding:

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

  This method is the easiest one. 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. The procedure to make this change will vary by system.

• Change the startup configuration for your Web Server so that it is started with character encoding settings that match the CA Harvest SCM database.

  An easy way to alter file.encoding on UNIX systems is to change the LANG variable in the environment from which Tomcat is started.

Example: Alter Locale When Starting Tomcat

This example shows how to start Tomcat on a UNIX system with a locale that matches the CA Harvest SCM database character encoding. In this example, Tomcat is started on a German UNIX system as follows:

export LANG=de_DE@euro
./startup.sh

The Java VM initializes file.encoding based upon the locale specified by LANG. In this example, file.encoding is initialized automatically to the value ISO-8859-15. If LANG is set to de_DE, file.encoding is initialized to ISO-8859-1.