Data source setup in Opportunity Detect

To set up data sources for HCL® Opportunity Detect, you configure them in the user interface, including setting up connections to the databases that hold run detail, State History, and Outcome data.

To develop data feeds, you must identify the operational systems, databases, and tables that hold the feed data you want to use. If you plan to use flat files, you must extract this data into flat files in the required format, with the required file names.

The following table describes the input and output data you set up in Opportunity Detect.

Note: All of your database tables must be of the same type. If you use DB2 for your system tables, Oracle is not supported for profile or lookup tables. If you use Oracle for your system tables, DB2 is not supported for profile or lookup tables.
Table 1. Types and formats of data used in Opportunity Detect
Type Description Allowed formats
Input data

Your profile and transaction files must be accessible from the machine on which the Opportunity Detect run time component is installed.
Transaction data Customer activities, obtained from your organization's operational system. At least one transaction data source is required to run a workspace.
  • Flat file
  • A message from a queue server
  • A message from the HCL Opportunity Detect web service
Profile data Customer attributes. Examples of profile data are age, home address, and telephone number. Optional.
  • Flat file
  • Database tables

If a queue or the Web Service data source connector is used for transaction data, the associated profile data must be in a database table.
Lookup data An auxiliary table that holds static data, and is used to look up values.
  • Database tables
Output data (system tables)
State History Data needed for component processing. You can share State History tables with multiple workspaces for development and test purposes, and set up one or more State History tables for exclusive use by the production environment.
  • Database tables
Outcomes Data produced by trigger systems, for use by external systems. You can share Outcome tables with multiple workspaces for development and test purposes, and set up one or more State History tables for exclusive use by the production environment.
  • Database tables
  • A message from a queue server
  • A message from the HCL Opportunity Detect web service
Run detail Data produced by the engine, containing information about workspace runs. The table is created in the run time database automatically during installation. When you set up data sources, you define a database connection for the run time database and associate it with the server group.
  • Database tables