Overview of the IBM® Interact Fix Pack 2

The IBM® Interact 9.1.0 Fix Pack 2 provides a number of improvements over the base 9.1.0 installation, including fixed defects and improved results when you process event pattern data. This guide describes the features added to Interact by this fix pack.

In Interact, all event pattern data for a given AudienceID is stored as a single collection in the runtime database tables. To perform any SQL queries or reporting based on event patterns, this new ETL process is required to break up the collection of event pattern data into tables in a target database. To accomplish this, the stand-alone ETL process takes event pattern data from the Interact runtime database tables, processes it on the schedule you specify, and stores it in the target database where it is available for SQL queries or additional reporting.

The stand-alone event pattern ETL process stores the processed event pattern data in a target database for further use in SQL queries or reporting. The target database must be updated with four new tables that are required to store the data. These tables are documented here for reference in retrieving the data in your own reporting process.

Using the Interact application programming interface (API), two API calls deliver offers: getOffers and getOffersForMultipleInteractionPoints. getOffersForMultipleInteractionPoints can prevent the return of duplicate offers at the OfferID level, but cannot deduplicate offers across offer category. So, for example, for Interact to return only one offer from each offer category, a workaround was previously required. With the introduction of two parameters to the startSession API call, offer deduplication across offer attributes, such as category, is now possible.