Known issues

This section describes the known issues in the 9.1.1 version of Opportunity Detect.

When a Batch run is performed in Recovery mode, duplicate outcomes are sometimes generated RTC 95405 If a batch run is performed in Recovery mode, duplicate outcomes are sometimes generated for Pattern components and multiple audience feed data. You should wait at least three minutes before attempting to re-start the run, to ensure that the automatic save has time to complete.
No warning is displayed when you change the type of data source connector RTC 164287 No warning is displayed when you change the type of data source connector within a deployment configuration. When you change the type of the data source connector used by a data source, you must re-deploy any deployment configuration that uses the changed data source before you run the deployment.
Forward Inactivity components do not fire after the specified time span following the incoming event when transactions use the Web Service data source connector RTC 175922 When transactions use the Web Service data source connector, and if a valid incoming event occurs for a Forward Inactivity component, the component does not fire as soon as specified time span has elapsed. Instead, the Forward Inactivity component fires when a new set of transactions is processed.
An undefined error occurs during deployment RTC 176388 When your system is integrated with Tivoli Access Manager (TAM), you might see an undefined error when you deploy a deployment configuration.

Deployment time can vary due to the capacity of the machine on which it is running, and also the number of concurrent applications that run on the same machine. TAM, authenticates, authorizes, forwards requests to the Opportunity Detect server and forwards the server response to clients. TAM interprets a response that is received outside its timeout interval as a failure from the Opportunity Detect server, and sends a failure response.

However, the deployment is successful despite the undefined error message.

To correct this issue, perform the following procedure in TAM configuration to extend the TAM timeout.

  1. Update the webseald-default.conf file with the following parameters.

    Because deployment time varies, you should modify the values shown below to reflect your environment. Observe your deployment time and add 2 minutes as the timeout interval in your TAM settings.

    • http-timeout = 600
    • https-timeout = 600
    • client-connect-timeout = 600
    • intra-connection-timeout = 600
  2. Restart TAM.

    For example: pdweb restart
The database password is not updated when you install Interact Advanced Patterns over Opportunity Detect RTC 177556 If you install Interact Advanced Patterns over Opportunity Detect, and you select the manual option, you must manually update the password attribute of the properties tag in the server.xml file. This file is located in the InteractService/wlp/usr/servers/InteractService directory under your Opportunity Detect installation.

You can use the securityUtility located under the InteractService/wlp/bin directory under your Opportunity Detect installation to encrypt the password. For example:

./securityUtility encode your_password

An error occurs when referenced Container components in the same workspace have the same name RTC 178235 When you are building triggers, it is a common practice to copy component references from multiple test workspaces into the same production workspace. If two Container components from two different workspaces have the same name, the Streams log shows the following error, and Outcomes are produced for only one of the Containers.

The table definition already exists: Container

To avoid this issue, give your Container components names that are unique across all workspaces.
When you use the Internet Explorer browser you can not add output functions on Select fields used in a Container component RTC 178313 When you use the Internet Explorer browser to work with a Container component that uses fields from a Select component, when you try to apply a function that changes the output data type, the page refreshes intermittently and you can not select a function on any field. The drop down select box is not available and there are no values in the field. The workaround is to use the Chrome browser, where this issue does not occur.