Known limitations

This section describes the known limitations in the 11.0.1 version of Opportunity Detect.

Unexpected results for Forward Inactivity components in multiple deployments using the same State History table Enhancement 202780, APAR 202786 If two deployments of different workspaces run against the same state history table, if there are Forward Inactivity components in either of the workspaces, then these components must be placed in both deployments. If not, then the deployment that does not have the Forward Inactivity interferes with the inactivity processing for the other deployment.
Deployments fail when multiple workspaces are deployed simultaneously Defects 200534, 201851 Attempting to deploy multiple workspaces simultaneously causes a conflict with a shared resource. There is a high probability that at least one of the deployments will fail. To avoid the issue, limit deployments to one workspace at a time.
The database password is not updated when you install Interact Advanced Patterns over Opportunity Detect Defect 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

The Action component does not fire for some workspaces when the Outcome is mapped to a Web Service connector Defect 198305 When the Outcome data source is mapped to the Web Service connector, and if the trigger system contains only one Action component that is listening for a Forward Looking or negative Pattern component, no outcome message is sent. In this case, you need a second Action component that is listening for another type of component; then all outcome messages will be sent.
The XML file for the command line utility is not updated when the Run Time component is installed on a different machine from the Design Time component Defect 199632 When you do not install the Run Time component on the same machine as the Design Time component, the RemoteControlCLI.xml file is not updated with the host and port of the Streams Remote Control service. This file must be configured if you want to use the RemoteControlCLI utility.

To work around this issue, update the file manually to replace [RCS_SERVER] and [RCS_PORT] with the host and port of the Streams Remote Control Service.

The RemoteControlCLI.xml file is located in the clidirectory under your Opportunity Detect design time installation.
The monitoring tool shows the same number of total transactions for all workspaces or a null pointer exception occurs Defect 219989, Defect 219002 In some cases, the monitoring tool can have either of the following issues.
  • The same number of total transactions is shown for all workspaces.
  • A null pointer exception occurs.
These issues can occur when Streams instances are not shut down gracefully. To resolve the issue, do the following.
  • In the Opportunity Detect user interface, stop all deployments.
  • Stop the Streams server.
  • On the runtime server, manually remove all job id files under $DETECT_HOME/apps/RealTimeProxy/ .

    The name format of these files is rtp.jobid.streams-instance-name.host. For example: rtp.jobid.streams1@streamsadmin.myHost.

  • Restart the Streams server