Set Campaign language and locale property values
Use Marketing Platform to set the values of configuration parameters that control how Campaign performs the following tasks:
*
*
*
The configuration of the Campaign web application determines the language and locale used both for translated Campaign messages (for example, text in the Campaign user interface) as well as the format of dates, numbers, and currency symbols on the application’s web pages. It is also vital for allowing flowcharts to display non-ASCII text, because the display language is used to initialize the flowchart editor.
*
Campaign supports non-ASCII column names, table names, and database names; however, it supports NCHAR, NVARCHAR, etc. columns on SQL Server databases only. On DB2®, NCHAR and NVARCHAR format columns are treated as if they were regular text fields; on Oracle, they are treated as numeric fields.
Log in to Marketing Platform and configure the following properties. Record these values for future reference. For information about these properties, see the Campaign Installation Guide.
*
*
*
*
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
*
*