Interact | Cache Managers | EHCache | Parameter Data

The configuration properties in this category control how the EHCache cache management system works to improve the performance of Unica Interact.

cacheType

Description: You can configure the Unica Interact runtime servers in a server group to use a multicast address for sharing cache data. This is referred to as a distributed cache. The cacheType parameter specifies whether you are using the built-in EHCache caching mechanism in local (stand-alone) mode or distributed (as with a runtime server group).
Note:
If you select Distributed for the cacheType, all of the servers sharing the cache must be part of the same, single server group. You must also enable multicast to work between all members of a server group.

From version 12.1.2 onwards, support to ‘Distributed’ EHCache is stopped. Ignite Distributed is used in place of EHCache Distributed. If you find ‘Distributed’ EHCache configured while upgrading from previous versions of Interact to 12.1.2 to higher versions, you are required to change Cache Manager from ‘Distributed EHCache’ to ‘Distributed Ignite’. Once the cache manager is changed from ‘Distributed EHCache’ to ‘Distributed Ignite’,all the compatible settings (for example: multicastPort, multicastIPAddress, overflowToDisk, etc.) are copied from EHCache to Ignite Cache. Distributed option is removed from EHCache dropdown. So, there would not be ‘Distributed’ option after upgrading to 12.1.2 or higher versions as well as for clean installatons. For any reason, if Distributed EHCache is used for caching, it will log an error message stating -"Invalid cache configuration. Switch to either local EHCache or Distributed Ignite cache." After logging error message it will shutdown Interact RT. So, in order to make Interact RT up and running, users must switch to either ‘local EHCache’ or to ‘Distributed Ignite’ cache. After logging error message Interact RT initialization status would be set to ‘INITIALIZATION_FAILED’. So, in order to initialize Interact RT successfully again, users require to switch to either ‘local EHCache’ or to ‘Distributed Ignite’ cache.
Default value: Local
Valid Values: Local

multicastIPAddress

Description

If you specify that the cacheType parameter is "distributed," you are configuring the cache to operate via multicast between all members of an Unica Interact runtime server group. The multicastIPAddress value is the IP address that all the Unica Interact servers for the server group use for listening.

The IP address must be unique across your server groups.

Default value

230.0.0.1

multicastPort

Description: If you specify that the cacheType parameter is "distributed," the multicastPort parameter indicates the port that all of the Unica Interact servers for the server group use for listening.
Default value: 6363

overflowToDisk

Description

The EHCache cache manager manages the session information using available memory. For environments where the session size is large due to a large profile, the number of sessions to be supported in memory may not be large enough to support the customer scenario. For situations where this is the case, EHCache has an optional feature to allow cache information greater than the amount that can be kept in memory to be written temporarily to the hard drive instead.

If you set the overflowToDisk property to "yes," each Java™ virtual machine (JVM) can handle more concurrent sessions than the memory alone would have allowed.

Default value

Valid Values

No | Yes

diskStore

Description: When the configuration property overflowToDisk is set to Yes, this configuration property specifies the disk directory that will hold the cache entries that are overflowed from memory. If this configuration property does not exist or its value is not valid, the disk directory is automatically created in the operating system's default temporary directory.
Default value: None
Valid Values: A directory to which the web application hosting Unica Interact run time has write privileges.

(Parameter)

Description

A template that you can use to create a custom parameter to be used with the cache manager. You can set up any parameter name, and the value it must have.

To create a custom parameter, click (Parameter) and complete the name and the value you want to assign to that parameter. When you click Save Changes, the parameter you have created is added to the list in the Parameter Data category.

Default value

None