eMessage requires that you create additional system tables in the Campaign schema and then populate them with initial data. These tables are used only by eMessage.

The Campaign installer automatically creates and populates the eMessage system tables in the Campaign schema if you select the option to create system tables automatically. However, if you do not select this option, you must create and populate the eMessage system tables manually.

Use your database client to run the appropriate script against the Campaign database. See the following tables to determine the scripts appropriate for your installation. The scripts that you must run depend on the type of database that hosts the Campaign schema and on whether the Campaign tables are configured for Unicode.

IBM® provides the ace_op_systab scripts for creating the eMessage tables in your local environment.

If your Campaign system tables are configured for Unicode, find the appropriate script in the ddl/unicode directory under your eMessage installation.

If your Campaign system tables are not configured for Unicode, use the non-Unicode scripts in the ddl directory under your eMessage installation.

IBM® provides the ace_op_populate_systab scripts for populating the eMessage tables in your local environment.

Locate the populate scripts in the ddl directory of your eMessage installation. IBM® provides only one version of the populate scripts because you can use them for either Unicode or non-Unicode tables.