Creating and populating the Interact system tables

If you have not created and populated the system tables during the installation process, use your database client to run the Interact SQL scripts against the appropriate database or to create and populate the Interact runtime environment, design time environment, learning, user profile, and contact and response tracking data sources.

Design time environment tables

Before you can enable the Interact design time environment in Campaign, you must add some tables to your Campaign system table database.

The SQL scripts are in the Interact_HOME/interactDT/ddl directory under your Interact design time environment installation.

If your Campaign system tables are configured for Unicode, use the appropriate script that is in the Interact_HOME/interactDT/ddl directory in your Interact design time environment. There are no Unicode equivalent scripts for the aci_populate_systab scripts that are used to populate the design time environment tables.

Use the scripts in the following table to create the Interact design time environment tables:

Table 1. Scripts for creating design time environment tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL® DB2®	aci_systab_db2.sql The user table space and system temporary table space where the Campaign system tables exist must each have a page size of 32K or greater.
Microsoft™ SQL Server	aci_systab_sqlsvr.sql
Oracle	aci_systab_ora.sql

Use the scripts in the following table to populate the Interact design time environment tables:

Table 2. Scripts for populating design time environment tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL DB2	aci_populate_systab_db2.sql
Microsoft SQL Server	aci_populate_systab_sqlsvr.sql
Oracle	aci_populate_systab_ora.sql

Runtime environment tables

The SQL scripts are in the <Interact_HOME>/ddl directory under your Interact installation.

If your Interact runtime tables are configured for Unicode, use the appropriate script that is in the <Interact_HOME>/ddl/Unicode directory to create the runtime tables. There are no Unicode equivalent scripts for the aci_populate_runtab scripts that are used to populate the runtime tables.

You must run the SQL scripts once for each server group data source.

Use the scripts in the following table to create the Interact runtime tables:

Table 3. Scripts for creating runtime environment tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL DB2	aci_runtab_db2.sql The user table space and system temporary table space where the Interact runtime environment tables exist must each have a page size of 32K or greater.
Microsoft SQL Server	aci_runtab_sqlsvr.sql
Oracle	aci_runtab_ora.sql

Use the scripts in the following table to populate the Interact runtime tables:

Table 4. Scripts for populating runtime environment tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL DB2	aci_populate_runtab_db2.sql You must use the following command when you run the script: db2 +c -td@ -vf aci_populate_runtab_db2.sql
Microsoft SQL Server	aci_populate_runtab_sqlsvr.sql
Oracle	aci_populate_runtab_ora.sql

Note: You should alter the size of the UACI_EligStat.offerName column from 64 to 130 (or 390 for Unicode tables) to preserve compatibility with Campaign. Use the following sample SQL statements for this modification.

Non-Unicode
DB2: ALTER table UACI_EligStat ALTER COLUMN OfferName SET DATA TYPE varchar(130);
ORACLE: ALTER TABLE UACI_EligStat MODIFY OfferName varchar2(130);
SQLSVR: ALTER TABLE UACI_EligStat alter column OfferName varchar(130) not null;

Unicode
DB2: ALTER table UACI_EligStat ALTER COLUMN OfferName SET DATA TYPE varchar(390);
ORACLE: ALTER TABLE UACI_EligStat MODIFY OfferName varchar2(390);
SQLSVR: ALTER TABLE UACI_EligStat alter column OfferName nvarchar(390) not null;

Learning tables

You can use SQL scripts to create and populate tables for optional features such as learning, global offers, score override, and contact and response history tracking.

All the SQL scripts are in the <Interact_HOME>/ddl directory.

Note: The built-in learning module requires a separate data source from the Interact runtime environment tables. For the built-in learning module, you must create a data source to hold all the learning data. The separate data source can communicate with all server groups, which means you can learn from your different touchpoints at the same time.

If your Interact runtime tables are configured for Unicode, use the appropriate script that is in the <Interact_HOME>/ddl/Unicode directory to create the learning tables.

Use the scripts in the following table to create the Interact learning tables:

Table 5. Scripts for creating learning tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL DB2	aci_lrntab_db2.sql
Microsoft SQL Server	aci_lrntab_sqlsvr.sql
Oracle	aci_lrntab_ora.sql

Contact and response history tables

You must run SQL scripts against the contact history tables if you want to use cross-session response tracking or the advanced learning feature.

All the SQL scripts are in the Interact installation directory.

Note: Using contact and response history features requires a separate data source from the Interact runtime environment tables. To use the contact and response history features, you must create a data source to reference contact and response data. The separate data source can communicate with all server groups.

If your contact history tables are configured for Unicode, use the appropriate script that is in the Unicode directory under the same location as the standard script to create the learning tables.

Use the scripts in the following table to create the Interact contact and response history tables:

Table 6. Scripts for creating contact history tables
This two-columned table provides information about the data source type in one column, and the script name in the second column.
Data source type	Script name
HCL DB2	aci_crhtab_db2.sql in the `<Interact_HOME>`/ddl/ directory. The script impacts the Interact runtime tables. aci_lrnfeature_db2.sql in the `<Interact_HOME>`/interactDT/ddl/acifeatures/ directory. The script impacts the Campaign design time tables.
Microsoft SQL Server	aci_crhtab_sqlsvr.sql in the `<Interact_HOME>`/ddl/ directory. aci_lrnfeature_sqlsvr.sql in the `<Interact_HOME>`/interactDT/ddl/ directory.
Oracle	aci_crhtab_ora.sql in the `<Interact_HOME>`/ddl/ directory. aci_lrnfeature_ora.sql in the `<Interact_HOME>`/interactDT/ddl/ directory.