Platform Deployment Guide › Before You Start using CA Data Protection › Set Up Support for Unicode Characters

Set Up Support for Unicode Characters

CA Data Protection consoles support Unicode character sets. For example, you can search in the iConsole emails associated with trigger names that were defined using Korean characters in the user policy.

CMS and Gateways

• Oracle: To implement Unicode support on Oracle CMSs or gateways, set up the database for CA Data Protection to use UTF-8 encoding for the DBMS code page. For details, see the Database Guide; search for ‘UTF-8’.
• SQL Server: There is no equivalent requirement for SQL Server CMSs or gateways. SQL Server databases automatically support Unicode characters.

Endpoint Computers

Implement Unicode support on all CA Data Protection endpoint computers running non-double byte character set versions of Windows (that is, non-DBCS Windows) and which are likely to capture events containing Unicode characters. For example, this applies to Japanese email trigger details captured on a computer running an English version of Windows.

To implement Unicode support:

1. Stop the 'CA Data Protection infrastructure' service. From a command prompt, run:

   net stop wgninfra
   

2. Edit the startup.properties file. Find this file in the \system subfolder of the CA Data Protection installation folder.
3. Open this file and add the following line to the [Database] section:

   db.charset=UTF-8
   

4. Restart the CA Data Protection infrastructure service. From a command prompt, run:

   net start wgninfra
   

Important! Do not make this change to startup.properties on CA Data Protection computers running Japanese, Korean or Chinese versions of Windows.