Configuring for multiple locales on MariaDB
To configure Unica Campaign for multiple locales when your system tables or user tables are MariaDB, you must adjust encoding properties, date/time settings, environment variables, and the application server startup script.
First, identify the MariaDB database code set and code page. For localized environments, the MariaDB database must have the following configuration:
- Database code set = UTF-8
Configuring encoding properties (MariaDB)
Choose
, then specify the encoding property values listed in the following table.For important information, see the property descriptions in "Setting properties for integration with Unica products" in the Campaign Installation Guide.
Property |
Value |
---|---|
Campaign > partitions > partition[n] > dataSources > [data_source_name] > StringEncoding |
UTF-8 |
Campaign > partitions > partition[n] > server > encoding > stringEncoding |
UTF-8 |
Campaign > unicaACListener > logStringEncoding |
UTF-8 |
Campaign > unicaACListener > systemStringEncoding |
UTF-8 |
Configure date/time settings (MariaDB)
When you configure Unica Campaign for multiple locales on MariaDB, be sure to adjust the date and time values.
Choose
, then specify the values for the properties listed in the following table.
Property |
Value |
---|---|
Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateOutputFormatString |
%Y-%m-%d |
Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateTimeFormat |
DT_DELIM_Y_M_D |
Campaign > partitions > partition[n] > dataSources > [data_source_name] > DateTimeOutputFormatString |
%Y-%m-%d %H:%M:%S For Japanese databases, the delimiter for the time portion must be a period (.) So, for Japanese databases set the value to: %Y/%m/%d %H.%M.%S |