Home
Administrator Guides
Administrator Guide
Non-ASCII data in Unica Campaign
Unica Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the application.
Configuring Unica Campaign for multiple locales
Configuring for multiple locales on DB2
To configure Unica Campaign for multiple locales when your system tables are DB2®, you must adjust encoding properties, date/time settings, environment variables, and the application server startup script.
Configure environment variables (DB2)
To configure environment variables for DB2®, identify the DB2 database code page, then set the DB2CODEPAGE DB2 environment variable to the same value. For localized environments, the DB2 database code page must be 1208.

Administrator Guides
- Administrator Guide
  - Unica Campaign administration overview
    The Settings menu provides access to most of the tasks that Unica Campaign administrators typically perform.
  - Security in Unica Campaign
    Security policies control user access to the objects and features in Unica Campaign.
  - Database table administration
    Unica Campaign administrators must perform initial one-time tasks and routine administration tasks that pertain to database tables.
  - Customizing campaigns
    Administrators can customize campaigns by using custom campaign attributes, initiatives, and products.
  - Offer template concepts
    Before administrators perform offer template management tasks, there are several important concepts to understand.
  - About audience level administration
    Unica Campaign is delivered with a single audience level called Customer. You can define any additional audience levels that you need. Audience levels let flowchart designers target specific groups, such as Households, in marketing campaigns.
  - Before you begin working with contact history
    Contact history is stored in the Unica Campaign system database in separate tables by audience level. Therefore, you need to set up audience levels before you begin working with contact history.
  - Response history administration
    Before you begin working with response history, you should read the audience level administration topics and set up required audience levels.
  - Monitoring and controlling flowchart runs
    Choose Campaign > Monitoring and use the All monitored runs page to view the status of all active flowcharts and suspend, resume, or stop flowchart runs.
  - Dimension hierarchy concepts
    A dimension hierarchy is a data construct that groups data into bins based on value ranges. Dimension hierarchies are the basis for a variety of reports.
  - Triggers administration
    Unica Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
  - Unica Campaign log files
    Unica Campaign records information in several different log files.
  - JVM Parameters
  - About codes in Unica Campaign
    Each campaign, cell, offer, and treatment in Unica Campaign has an identifying code that is generated by code generators, and conforms to a specified format.
  - Accessing the Advanced settings
    When a flowchart is open for editing, administrators can choose the Advanced settings option on the Admin menu to make administrative changes that affect only the current flowchart.
  - Unica Campaign integration with other products
    Unica Campaign optionally integrates with a number of other products.
  - Unica Campaign listeners
    The listener is a key component of Unica Campaign. It provides an interface between front-end clients and back-end analytical server processes.
  - Unica Campaign utilities
    Administrators use the Unica Campaign utilities to manage listeners, sessions, and flowcharts, and perform other important administrative tasks.
  - Configuring the ACOOptAdmin tool
    Configure the ACOOptAdmin tool to run Unica Optimize sessions from the command line.
  - Non-ASCII data in Unica Campaign
    Unica Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the application.
    - About using non-ASCII data or non-US locales
      Before you perform any of the configuration procedures, you should understand the basic concepts as they apply to data and locale configuration in your Unica application.
    - Configuring Unica Campaign for a non-ASCII language or a non-US locale
      Several steps need to be performed in a specific order to correctly configure Unica Campaign.
    - Configuring Unica Campaign for multiple locales
      - Before you begin: Unica Campaign must be installed
      - Configuring for multiple locales on SQL Server
      - Configuring for multiple locales on Oracle
      - Configuring for multiple locales on DB2
        To configure Unica Campaign for multiple locales when your system tables are DB2®, you must adjust encoding properties, date/time settings, environment variables, and the application server startup script.
        Configure encoding properties (DB2)
        When you configure Unica Campaign for multiple locales on DB2®, it is important to set the correct encoding properties.
        Configure date/time settings (DB2)
        When you configure Unica Campaign for multiple locales on DB2®, be sure to adjust the date and time values.
        Configure environment variables (DB2)
        To configure environment variables for DB2®, identify the DB2 database code page, then set the DB2CODEPAGE DB2 environment variable to the same value. For localized environments, the DB2 database code page must be 1208.
        Configure application server startup scripts (DB2)
      - Configuring for multiple locales on MariaDB
      - Configuring for multiple locales on OneDB
  - Configuration properties for Unica Campaign
    The configuration properties of Unica Campaign are located at SettingsConfiguration. For more details on the configuration properties, see the Campaign Administrator Guide.
  - About special characters
    Some special characters are not supported in any Unica Campaign object names. In addition, some objects have specific naming restrictions.
  - Introduction to character encodings
    This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Unica Campaign.
  - About Unica Campaign Error Codes
    Unica Campaign notifies users of error events when they occur with error messages that consist of a code number and error text.
  - Troubleshooting
- System Tables

Configure environment variables (DB2®)

To configure environment variables for DB2®, identify the DB2® database code page, then set the DB2CODEPAGE DB2® environment variable to the same value. For localized environments, the DB2® database code page must be 1208.

About this task

Follow these steps to set the DB2CODEPAGE DB2® environment variable to 1208.

Procedure

On Windows™, add the following line to the Unica Campaign Listener startup script (<CAMPAIGN_HOME>\bin\cmpServer.bat):
db2set DB2CODEPAGE=1208
On UNIX™:
1. After DB2® is started, the system administrator must type the following command from the DB2® instance user:
  $ db2set DB2CODEPAGE=1208
  After completing this step, the administrator does not need to run the db2set DB2CODEPAGE=1208 command from the DB2® instance user again, because the value is registered for the DB2® instance user. The root user cannot run the command because the root user might not have sufficient permission.
2. To verify the setting, type the following command and confirm that the output is 1208:
  $ db2set DB2CODEPAGE
3. To confirm that the DB2CODEPAGE setting works for the root user, type the following command on the $CAMPAIGN_HOME/bin directory and confirm that the output is 1208:
  # . ./setenv.sh
  # db2set DB2CODEPAGE
4. Run the following command to start the Unica Campaign listener:
  ./rc.unica_ac start

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.