HCL® Opportunity Detect enables you to look for specified customer behaviors and patterns in your customer data. You define the transactions and patterns that Opportunity Detect looks for, and you specify the data that is written to the database or web servlet when those criteria are met.

The permissions assigned to users in Opportunity Detect determine what areas of the application they can access and the actions they can perform.

Opportunity Detect offers three data source connectors for processing transactions as soon as they are received.

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.

You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

The Queue data source connector allows Opportunity Detect to operate with a supported queue server.

You can use a Web Service Connector for incoming transaction data, for Outcome data, or for both.

Opportunity Detect provides a monitoring tool for deployments running on Streams.

The Opportunity Detect command line utility, RemoteControlCLI (CLI), allows you to automate the management of deployment configurations and batch runs. You can use the CLI to perform the same actions you can perform on the Deployment & Batch Run tab of a workspace.

Use the export/import utility to transfer Opportunity Detect workspace logic from one environment to another.

The conversion utility enables you to convert workspaces in Unica Detect format (that is, in versions earlier than 9.1.1) to Opportunity Detect format.

Some suggestions for resolving issues with Opportunity Detect are listed in this section, along with workarounds or solutions.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.

The following table describes permissions that you can assign to roles in Opportunity Detect.

Four built-in roles are included with Opportunity Detect.

Opportunity Detect offers three data source connectors for processing transactions as soon as they are received.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

The Queue data source connector allows Opportunity Detect to operate with a supported queue server.

You can use a Web Service Connector for incoming transaction data, for Outcome data, or for both.

If you are unsure of how to complete the fields on the Server Groups page, use the information provided here.

You can use a Web Service Connector for incoming transaction data, for Outcome data, or for both.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

Before you can run a workspace to process data, you create a deployment configuration for it and then deploy it.

The Queue data source connector allows Opportunity Detect to operate with a supported queue server.

You can use a Web Service Connector for incoming transaction data, for Outcome data, or for both.

If you are unsure of how to complete the fields on the Server Groups page, use the information provided here.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

Use this procedure to define server groups and connect them to data sources you have configured.

If you are unsure of how to complete the fields on the Server Groups page, use the information provided here.

Audience codes represent the various audience levels defined in your data. Opportunity Detect groups data sources based on the audience code associated with them.

Use this procedure to specify audience level codes in Opportunity Detect.

On the Deployment tab of a workspace, you can create deployment configurations for workspaces, map data source connectors within the deployment configuration, deploy the configurations, stop and restart deployments, and view deployment history.

On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.

On the Batch History tab, you can see details about past runs, filtered by deployment and a date range.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

Data source connectors can be mapped to different data sources in each deployment configuration, which provides flexibility for testing and ramp-up operations.

On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.

On the Batch History tab, you can see details about past runs, filtered by deployment and a date range.

Use this procedure to create and deploy a deployment configuration.

Use this procedure to run a workspace for test or production purposes.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

Use this procedure to run a workspace for test or production purposes.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

When the Expanded Outcome data source connector is used for Outcome data, the system writes the data in a form that can be used by HCL® Campaign or an external system.

The Opportunity Detect engine can run batch files when it completes a run. You can use these files to issue different notifications for each successful and failed engine run.

Properties in this category are used to configure the Marketing Platform to send emails to users for system alerts and notifications.

Properties in this category control system behavior for notifications that HCL® Marketing Software products can send to users.

Follow this procedure to configure the Marketing Platform to send system alert and notification emails to users. You must have an email server set up before you start.

Follow these steps to configure notifications for the Opportunity Detect monitoring service.

Follow this procedure to configure the Marketing Platform to send system alert and notification emails to users. You must have an email server set up before you start.

You use JConsole to connect to the monitoring service as a remote client. Optionally, you can set configuration properties to configure the polling interval and the length of time that monitoring data is retained, logging levels, and the port that the tool uses.

Properties in this category specify values that affect the monitoring tool.

The Opportunity Detect monitoring tool runs as a JConsole service. To view the monitoring data, you must have the Java Development Kit (JDK) installed.

The Attributes fields in the monitoring tool provide details that can help you to determine the health of the Opportunity Detect runs being executed on your Streams servers.

The monitoring tool displays the health of the Streams jobs running for the various deployments.

You edit the RemoteControlCLI.xml file to enable the CLI to connect with the Opportunity Detect design time database.

The values you enter in the RemoteControlCLI.xml file enable the CLI to connect with your Opportunity Detect design time database.

Use this procedure to set up to export Opportunity Detect workspace logic from your source environment.

Use this procedure to set up to import Opportunity Detect workspace logic to your target environment.

The export/import utility supports the following commands and options.

The values you enter in the export/import XML file enable the export/import utility to connect with your Opportunity Detect design time database.

Use the export/import utility to transfer Opportunity Detect workspace logic from one environment to another.

If changes were made to the target environment between two export/import cycles, then the following conflict resolution rules are applied during the import.

Follow these guidelines when exporting and importing workspace logic.

Use the export/import utility to transfer Opportunity Detect workspace logic from one environment to another.

The conversion utility enables you to convert workspaces in Unica Detect format (that is, in versions earlier than 9.1.1) to Opportunity Detect format.

You can integrate Opportunity Detect with HCL® Campaign.

To create your business logic, you configure sets of components called trigger systems. Some components send events that activate other components, while others perform operations on data and make the results available to other components.

As you learn to work with Opportunity Detect, it is helpful to have a basic understanding of the way the application processes transactions.

Components in a trigger system can be said to have ancestor and descendent relationships with each other. Ancestor and descendent relationships affect many aspects of component behavior.

The transaction and profile data you feed into a trigger system is processed one record at a time. For batch file processing using the File type of data source connector, the system requires specific fields, field order, and sort order in your transaction and profile files.

Enable cookies in your browser to take advantage of all of the features provided in the Opportunity Detect user interface.

The permissions assigned to users in Opportunity Detect determine what areas of the application they can access and the actions they can perform.

You build trigger systems in workspaces. This procedure provides the basic steps for setting up workspaces. Details on adding and using components are provided elsewhere in this guide.

There are three ways to add components to workspaces: by creating a component from the Component Palette, by copying a component within a workspace, and by using a component reference to share a component across workspaces.

You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

Components are the basic building blocks for trigger systems in Opportunity Detect.

You build expressions and configure incoming events and time spans when you work with several types of components. In addition, all component editors have a left panel where you configure or view basic attributes. Read this section to understand these commonly used component attributes.

The Expression Builder is used throughout Opportunity Detect to compare strings and numbers, perform math operations, and apply database functions.

In Opportunity Detect, you use regular expressions in two situations.

Expression components evaluate customer data and return a value that can be used by other components. You can create similar logic by using inline expressions within components, but creating an expression component for frequently used calculations allows you to re-use this logic.

Trigger systems in HCL® Opportunity Detect all have Simple components as their basic building block. Simple is the only component type that is triggered by incoming transactions in the transaction data feed, and not by an event produced by another component. This is why every trigger system requires at least one Simple component.

The purpose of an Action component is to send a notification that a specified behavior has occurred by writing data to a database or sending the data to a web service. Like all event components, an Action component fires and writes its outcome when it receives an incoming event from another event component.

Select components perform operations that are similar to the SQL SELECT database query with optional WHERE clauses. A Select component holds a set of records that you define, and on which you can perform further operations.

Container components store data that you define for a specified length of time. Container components depend on Container Manipulator components to feed them the data that they store.

You can use Pattern components to test whether one or more events for a given customer occur over a period of time. A Pattern component collects events that match its criteria and stores these events in the customer's state history. When the specified pattern of events is met, the pattern drops those events from state history and fires a positive event.

You use a Backward Inactivity component when you want to verify that some event did not occur within a specified period of time prior to an incoming event. You use a Forward Inactivity component to set a timer when it receives an incoming event, and optionally to specify another event that turns off the timer.

Trend components detect changes in activity measured over defined periods of time. Before you can create a trend component, your trigger system must include a Container or Select component that the trend can use as a data source.

An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.

Components in a trigger system can be said to have ancestor and descendent relationships with each other. Ancestor and descendent relationships affect many aspects of component behavior.

The Data Dependencies panel contains a read-only list of transaction data sources that are allowed and used in this component and the audience level associated with these data sources. The fields update as you configure a component.

You can share a component in multiple workspaces by using component references.

Use this procedure to delete components from workspaces in Opportunity Detect.

When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.

To create your business logic, you configure sets of components called trigger systems. Some components send events that activate other components, while others perform operations on data and make the results available to other components.

You can share a component in multiple workspaces by using component references.

Time spans are used throughout Opportunity Detect to specify time periods.

You can set either a calendar or rolling time span in Forward Inactivity components.

You can set either a calendar or rolling time span in Forward Inactivity components.

You specify the calendar time span for the pattern using the Time Span section of the component editor.

You specify the rolling time span for the pattern using the Time Span section of the component editor.

When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.

Fields where you set a limit on how often an event component produces its event. Optional.

Time spans are used throughout Opportunity Detect to specify time periods.

Fields where you can set a start and end date during which an event component is active. Optional.

An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.

When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.

Fields where you can set a start and end date during which an event component is active. Optional.

Fields where you set a limit on how often an event component produces its event. Optional.

You can set either a calendar or rolling time span in Forward Inactivity components.

You can set either a calendar or rolling time span in Forward Inactivity components.

You build trigger systems in workspaces. This procedure provides the basic steps for setting up workspaces. Details on adding and using components are provided elsewhere in this guide.

Use this procedure to add components to workspaces from the Component Palette in Opportunity Detect.

Use this procedure to share a component across workspaces.

Use this procedure to add a component within a workspace by saving a copy of a component using a new name.

In the Workspace List, you can create, delete, and modify the basic properties of workspaces.

Use this procedure to run a workspace for test or production purposes.

You can share a component in multiple workspaces by using component references.

Use this procedure to share a component across workspaces.

To create your business logic, you configure sets of components called trigger systems. Some components send events that activate other components, while others perform operations on data and make the results available to other components.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

Use this procedure to run a workspace for test or production purposes.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

When the Expanded Outcome data source connector is used for Outcome data, the system writes the data in a form that can be used by HCL® Campaign or an external system.

The Opportunity Detect engine can run batch files when it completes a run. You can use these files to issue different notifications for each successful and failed engine run.

On the Deployment tab of a workspace, you can create deployment configurations for workspaces, map data source connectors within the deployment configuration, deploy the configurations, stop and restart deployments, and view deployment history.

On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.

On the Batch History tab, you can see details about past runs, filtered by deployment and a date range.

Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.

Data source connectors can be mapped to different data sources in each deployment configuration, which provides flexibility for testing and ramp-up operations.

The input mode that you select determines what data source connectors are allowed for the data sources used in the workspace. The Input mode field is located on the Properties tab of a deployment configuration.

On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.

On the Batch History tab, you can see details about past runs, filtered by deployment and a date range.

On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.

An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.

You build trigger systems in workspaces. This procedure provides the basic steps for setting up workspaces. Details on adding and using components are provided elsewhere in this guide.

You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.

Use this procedure to create and deploy a deployment configuration.

Use this procedure to run a workspace for test or production purposes.

Functions perform some additional processing on a record set returned by a Container or Select component. Functions allow you to apply commonly used database functions to the records.

The IsMemberOf (IMO) function provides an efficient method for identifying and acting on large quantities of lookup table data to determine which records contain a specified value.

Container components provide a way to create a data structure similar to a database table in your trigger systems. You use the Container to define the table that holds the data inserted by a Container Manipulator.

Select components perform operations that are similar to the SQL SELECT database query with optional WHERE clauses. A Select component holds a set of records that you define, and on which you can perform further operations.

When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.

When a customer withdraws $10,000 from her account, you might want to determine whether she has made any other withdrawals larger than $5,000 within the past two months. For this, you would use a Backward Inactivity component.

You can set either a calendar or rolling time span in Forward Inactivity components.

You can set either a calendar or rolling time span in Forward Inactivity components.

Expression components evaluate customer data and return a value that can be used by other components. You can create similar logic by using inline expressions within components, but creating an expression component for frequently used calculations allows you to re-use this logic.

The Expression Builder is used throughout Opportunity Detect to compare strings and numbers, perform math operations, and apply database functions.

You specify the calendar time span for the pattern using the Time Span section of the component editor.

You can set either a calendar or rolling time span in Forward Inactivity components.

When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.

By default, a Pattern fires a positive event when its criteria are met, but it does not fire a negative event when the aging out of an event creates a negative condition. However, you can configure the behavior to include negative events.

Pattern behavior options allow you to enable the pattern to fire a negative event (by default patterns fire only positive events). They also allow you to delay firing the negative event.

Container components provide a way to create a data structure similar to a database table in your trigger systems. You use the Container to define the table that holds the data inserted by a Container Manipulator.

You use Container Manipulator components to add and delete data in Container components.

An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.

On the Deployment tab of a workspace, you can create deployment configurations for workspaces, map data source connectors within the deployment configuration, deploy the configurations, stop and restart deployments, and view deployment history.

The integration between HCL® Interact and HCL Interact Advanced Patterns provides advanced pattern recognition capabilities for your Interact implementation.

An installation of Opportunity Detect or Interact Advanced Patterns is complete when you install, configure, and deploy the product.

When you plan your Opportunity Detect and Attribution Modeler installation, you must ensure that you have set up your system correctly, and that you have configured your environment to deal with any failures.

The Opportunity Detect runtime environment uses data sources to store user and interaction data.

You must run the HCL® Marketing Software installer to start the installation of Opportunity Detect. The HCL Marketing Software installer starts the Opportunity Detect installer during the installation process. Make sure that the HCL Marketing Software installer and the product installer are saved at the same location.

If you select manual database set up when you install Opportunity Detect, you must complete the tasks in this section after you run the HCL® Marketing Software and the Opportunity Detect installer.

To deploy Opportunity Detect, you must deploy Opportunity Detect Design Time using an EAR or WAR file.

After you deploy Opportunity Detect, perform the additional configuration tasks described in this chapter.

Opportunity Detect can be installed and deployed in a cluster.

Run the Opportunity Detect and Attribution Modeler uninstallers to uninstall Opportunity Detect. When you run the Opportunity Detect uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.

The properties and values on the Configuration page are stored in the Marketing Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.

You must set the configuration properties for Opportunity Detect or Interact Advanced Patterns.

Properties in this category specify values that are used internally to navigate among HCL® Marketing Software products.

The property in this category specifies the URL for the HCL® InfoSphere Streams remote control web service. Opportunity Detect Design Time communicates with Opportunity Detect Run Time over this service.

The property in this category specifies the URL for the web service used when Interact is integrated with Interact Advanced Patterns or when the Web Service connector is used for input data.

The property in this category specifies the URL for the web service that allows Interact to automatically create and deploy advanced patterns when Interact is integrated with Interact Advanced Patterns.

The property in this category specifies the location of the Opportunity Detect log file.

An upgrade of Opportunity Detect is complete when you upgrade, configure, and deployupgrade and configure Opportunity Detect. The Opportunity Detect Upgrade Guide provides detailed information about upgrading, configuring, and deployingupgrading and configuring Opportunity Detect.

You can upgrade your current version of Opportunity Detect to bring it up-to-date with the latest features.

Perform these steps before you run the upgrade installer.

Automatic migration allows the installer to run the SQL scripts and insert the configuration properties that are required to upgrade your Marketing Platform system tables. If your company policy does not allow automated updates to your system table database, you must use manual migration, described elsewhere in this guide.

The Opportunity Detect upgrade installer can perform all of the data migration that is required for an upgrade automatically. However, if the policy of your organization does not allow automatic migration, you must complete the migration procedure to upgrade Opportunity Detect manually.

To deploy Opportunity Detect, you must deploy Opportunity Detect Design Time using an EAR or WAR file.

After you deploy Opportunity Detect, perform the additional configuration tasks described in this chapter.

Run the Opportunity Detect and Attribution Modeler uninstallers to uninstall Opportunity Detect. When you run the Opportunity Detect uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.

The properties and values on the Configuration page are stored in the Marketing Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.