Configuring for multiple locales on OneDB
To configure Unica Campaign for multiple locales when your system tables or user tables are OneDB, you must adjust encoding properties, date/time settings, environment variables, and the application server startup script.
Settings for Campaign Non-Ascii in UA_system_tables
Select Settings > Configurations and then specify the values for string related properties listed in the following table.
Property | Values |
---|---|
Campaign > partitions > partitions[n] > dataSource >[data_source_name] > StringEncoding | WIDEUTF-8 |
Campaign > partitions > partitions[n] > dataSource >[data_source_name] > ODBCUnicode | UCS-2 |
Campaign > partitions > partitions[n] > server >encoding > stringEncoding | UTF-8 |
Campaign > unicaACListener > logStringEncoding | UTF-8 |
Campaign > unicaACListener > systemStringEncoding | UTF-8 |
Select Settings -> Configurations, then specify the values for date related
properties listed in the following table.
Property | Values |
---|---|
Campaign > partitions > partition[n] > dataSource >[data_source_name] > DateFormat | DELIM_Y_M_D |
Campaign > partitions > partition[n] > dataSource >[data_soruce_name] > DateOutputFormatString | %Y-%m-%d |
Campaign > partitions > partition[n] > dataSource >[data_soruce_name] > DateTimeFormat | DT_DELIM_Y_M_D |
Campaign > partitions > partition[n] > dataSource >[data_soruce_name] > DateTimeOutputFormatString | %Y-%m-%d %H:%M:%S |