Home
Administrator Guide
Unica Interact provides documentation and help for users, administrators, and developers.
Interact runtime environment configuration properties
This section describes all the configuration properties for the Unica Interact runtime environment.
Interact | cacheManagement
This set of configuration properties defines settings for selecting and configuring each of the supported cache managers that you can use to improve the performance of Unica Interact, such as EHCache or Ignite, which is built-in to your Unica Interact installation. Use the Unica Interact | cacheManagement | Cache Managers configuration properties to configure the cache manager you want to use. Use the Unica Interact | cacheManagement | caches configuration properties to specify which cache manager Unica Interact should use to improve performance.
Interact | caches
Use this set of configuration properties to specify which supported cache manager you want to use to improve the performance of Unica Interact, such as Ehcache or Ignite caching, and to configure specific cache properties for the runtime server you are configuring.
Interact | Caches | Interact Cache | Ignite
A cache manager "Ignite" is added under Cache Manager node. The cache Unica Interact Cache and PatternStateCache can use either EHCache or Ignite independently of each other. The following parameters are available for configuration:

Administrator Guide
Unica Interact provides documentation and help for users, administrators, and developers.
- Administering Interact
  When you administer Unica Interact you configure and maintain users and roles, data sources, and optional product features. You also monitor and maintain the design and runtime environments. Product-specific application programming interfaces (APIs) are available for you to use.
- Security Management
  Access to the Unica Interact runtime User Interface requires authentication. Only the Login IDs defined in Unica Platform and having Unica Interact admin role can access the pages.
- Configuring users
  Unica Interact requires you to configure two sets of users, runtime environment users and design environment users.
- Managing Unica Interact data sources
  Unica Interact requires several data sources to function properly. Some data sources contain the information Unica Interact requires to function, other data sources contain your data.
- Offer serving
  You can configure Unica Interact in many ways to enhance how it selects offers to present. The following sections describe these optional features in detail.
- Understanding the Interact API
  Unica Interact serves offers dynamically to a wide variety of touchpoints. For example, you can configure the runtime environment and your touchpoint to send messages to your call center employees informing them of the best up sell or cross sell prospects for a customer who has called with a specific type of service inquiry. You can also configure the runtime environment and your touchpoint to provide tailored offers to a customer (visitor) who has entered a particular area of your Web site.
- Managing the Unica Interact API
  Whenever you use the startSession method, you create a Unica Interact runtime session on the runtime server. You can use configuration properties to manage the sessions on a runtime server.
- Classes and methods for the Unica Interact API
  The following sections list requirements and other details you should know before you work with the Unica Interact API.
- Classes and methods for the Interact JavaScript API
  The following sections list requirements and other details you should know before you work with the Unica Interact JavaScript API.
- About the ExternalCallout API
  Unica Interact offers an extensible macro, EXTERNALCALLOUT, for use with your interactive flowcharts. This macro enables you to perform custom logic to communicate with external systems during flowchart runs. For example, if you want to calculate the credit score of a customer during a flowchart run, you can create a Java™ class (a callout) to do so and then use the EXTERNALCALLOUT macro in a Select process in your interactive flowchart to get the credit score from your callout.
- Unica Interact utilities
  This section describes the administrative utilities available with Unica Interact.
- About the Learning API
  Unica Interact offers a learning module which uses a naive-bayesian algorithm to monitor visitor actions and propose optimal offers (in terms of acceptance). You can implement the same Java™ interface with your own algorithms using the Learning API to create your own learning module.
- Interact WSDL
  The Unica Interact installation includes two WDSL (Web Services Description Language) XML files that describe the available web services and how to access them. You can view these files in your Unica Interact home directory, and an example is shown here.
- Interact runtime environment configuration properties
  This section describes all the configuration properties for the Unica Interact runtime environment.
  - Interact | general
    These configuration properties define general settings for your runtime environment environment, including the default logging level and the locale setting.
  - Interact | flowchart
    This section defines configuration settings for interactive flowcharts.
  - Interact | monitoring
    This set of configuration properties enables you to define JMX monitoring settings. You need to configure these properties only if you are using JMX monitoring. There are separate JMX monitoring properties to define for the contact and response history module in the configuration properties for Unica Interact design environment.
  - Interact | profile
    This set of configuration properties control several of the optional offer serving features, including offer suppression and score override.
  - Interact | offerserving
    These configuration properties define the generic learning configuration properties. If you are using built-in learning, to tune your learning implementation, use the configuration properties for the design environment.
  - Interact | services
    The configuration properties in this category define settings for all the services which manage collecting contact and response history data and statistics for reporting and writing to the runtime environment system tables.
  - Interact | cacheManagement
    This set of configuration properties defines settings for selecting and configuring each of the supported cache managers that you can use to improve the performance of Unica Interact, such as EHCache or Ignite, which is built-in to your Unica Interact installation. Use the Unica Interact | cacheManagement | Cache Managers configuration properties to configure the cache manager you want to use. Use the Unica Interact | cacheManagement | caches configuration properties to specify which cache manager Unica Interact should use to improve performance.
    - Interact | cacheManagement | Cache Managers
      The Cache Managers category specifies the parameters for the cache management solutions you plan to use with Unica Interact.
    - Interact | caches
      Use this set of configuration properties to specify which supported cache manager you want to use to improve the performance of Unica Interact, such as Ehcache or Ignite caching, and to configure specific cache properties for the runtime server you are configuring.
      - Interact | cacheManagement | caches | InteractCache
        The InteractCache category configures the caching for all session objects, including the profile data, segmentation results, most recently delivered treatments, parameters passed through API methods, and other objects used by the Unica Interact run time.
      - Interact | Caches | Interact Cache | Ignite
        A cache manager "Ignite" is added under Cache Manager node. The cache Unica Interact Cache and PatternStateCache can use either EHCache or Ignite independently of each other. The following parameters are available for configuration:
      - Interact | Caches | Interact Cache | Parameter Data
        The configuration properties in this category control the Interact Cache that is automatically used by your Unica Interact installation. These settings must be configured individually for each Unica Interact run time server.
      - Interact | cacheManagement | caches | PatternStateCache
        The PatternStateCache category is used to host the states of event patterns and real time offer suppression rules. By default, this cache is configured as a read-through and write-through cache, so that Unica Interact attempts to use the cache first event pattern and offer suppression data. If the requested entry does not exist in the cache, the cache implementation loads it from the data source, through either the JNDI configuration or directly using a JDBC connection.
  - Interact | triggeredMessages
    The configuration properties in this category define settings for all triggered messages and offer channel delivery.
  - Interact | activityOrchestrator
    The activity orchestrator category specifies the receivers and gateways for your Unica Interact inbound gateway activity.
  - Interact | ETL | patternStateETL
    The configuration properties in this category define the settings for the ETL process.
- Unica Interact Simulator
  This section describes all the configuration properties for the Unica Interact simulator.
- Interact design environment configuration properties
  This section describes all the configuration properties for Unica Interact design environment.
- Real-time offer personalization on the client side
  There may be situations where you want to provide real-time offer personalization without implementing low-level Java™ code or SOAP calls to the Unica Interact server. For example, when a visitor initially loads a web page where Javascript content is your only extended programming available, or when a visitor opens an email message where only HTML content is possible. Unica Interact provides several connectors that provide real-time offer management in situations where you have control only over the web content that is loaded on the client side, or where you want to simplify your interface to Unica Interact.
- JVM parameters
- Unica Interact and Digital Recommendations integration
  Unica Interact can integrate with IBM Digital Recommendations to provide Unica Interact-driven product recommendations. Both products can provide product recommendations for offers, but using different methods. Digital Recommendations uses a visitor's web behavior (collaborative filter) to build correlations between visitors and recommended offers. Unica Interact is based on customer's past behavior, attributes, history, and less on view-level offers, learning which offers best match a customer's behavior profile (based on demographics and other information about the customer). Offer acceptance rates help to build a predictive model through self-learning. Using the best of both products, Unica Interact can use a personal profile to define offers that will pass a category ID to Digital Recommendations and retrieve recommended products based on popularity (the "wisdom of the crowds") for display to the visitor as part of the selected offers. This can provide better recommendations for customers that will result in more click-throughs and better outcomes than either product acting alone.
- Interact and DDX integration
  With Digital Data Exchange, your website can link to Unica Interact to provide a powerful omni-channel execution engine that delivers the best offers to the optimum channels and evolves (learns) from the offer feedback to continuously increase marketing effectiveness.
- Unica Interact and Unica Journey integration
- Unica Interact and Unica Deliver integration
- Configure gateways
  Use triggered message gateways to send offer information from outbound channels.

Interact | Caches | Interact Cache | Ignite

A cache manager "Ignite" is added under Cache Manager node. The cache Unica Interact Cache and PatternStateCache can use either EHCache or Ignite independently of each other. The following parameters are available for configuration:

cacheType

Description: When "Local" is selected, each node runs independently of each other. When "Distributed" is selected, all the nodes form a grid and the data are distributed across the grid, which is the default.
Default value: When "Distributed" is selected, all the nodes form a grid and the data are distributed across the grid, which is the default.

discoveryIPAddresses

Description: The comma separated list of nodes' addresses in the format of <IP>:<port> for the nodes to communicate with each other. If one of these addresses is a multicast address, multicast discovery is used. Otherwise, the static IP discovery is used, and in this case, at least one of them has to be active at any moment. This is required when "Distributed" is selected as the cache type. The default value 230.0.0.1:6363 is a multicast.
Default value: 230.0.0.1:6363

localPort

The port each node will use for communicating with other nodes. If not specified, an open port in the range between 47500 and 47509 will be used. It is suggested to configure this setting if static IP discovery is used. This value can be overridden by using JVM property -Dinteract.ignitePort=<valid port>.

numberOfBackups

This is the backup copies of data are saved in the grid. Higher value will have better failover support and better read performance with the cost of lower write performance. When cache type is Distributed set numberofBackups value to 1.

overflowToDisk

Whether persist data into a temporary file on disk.

Note: Requests for the same session on different instances may fail if an instance stops and no backup is configured. This implies, API call fails on two different RTs when cache type is Ignite, in a case.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.