Set Campaign language and locale property values

This is one of the required steps when configuring Campaign to use a non-ASCII language or a non-US locale.

Campaign supports multiple languages and locales for a single installation. Setting the Campaign language and locale property values is a required step when configuring Campaign to use a non-ASCII language or a non-US locale.

Use the Campaign configuration settings in Marketing Platform to set the values of configuration properties that control how Campaign performs the following tasks:

reads and writes data in text files and log files

reads and writes date, time, and text fields within the database

handles text it receives from the database.

The configuration settings determine the language and locale that is used for translated Campaign messages (for example, text in the Campaign user interface) and the format of dates, numbers, and currency symbols on the application's web pages. The display language is also used to initialize the flowchart editor, which is vital for enabling flowcharts to display non-ASCII text.

Campaign supports non-ASCII column names, table names, and database names. However, Campaign supports NCHAR, NVARCHAR, etc. columns on SQL Server databases only. DB2® treats NCHAR and NVARCHAR format columns as if they were regular text fields. Oracle treats them as numeric fields.

Choose Settings > Configuration .

Adjust the following properties, and record the values for future reference.

Campaign > currencyLocale

Campaign > supportedLocales

Campaign > defaultLocale

Campaign > partitions > partition[n] > dataSources > [data_source_name ] > DateFormat

Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateOutputFormatString

Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateTimeFormat

Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateTimeOutputFormatString

Campaign > partitions > partition[n] > dataSources > [data_source_name] > EnableSelectOrderBy

Campaign > partitions > partition[n] > dataSources > [data_source_name] > ODBCunicode

Campaign > partitions > partition[n] > dataSources > [data_source_name] > StringEncoding

Campaign > partitions > partition[n] > dataSources > [data_source_name] > SuffixOnCreateDateField

Campaign > partitions > partition[n] > server > encoding > stringEncoding

Campaign > partitions > partition[n] > server > encoding > forceDCTOneBytePerChar

Campaign > unicaACListener > logStringEncoding

Campaign > unicaACListener > systemStringEncoding

The next step is to unmap and remap system tables.