CDD Cluster Tab and Cache OM Settings Reference

The CDD Cluster tab is used for setting up the cache OM.

Note: TIBCO BusinessEvents Express: This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.

For the related procedure, see Cluster Discovery and Internal Communication.

CDD Cluster Tab Cache OM Settings
Property Global Variables Notes
Provider No Select the cache provider:

TIBCO: Uses the provided TIBCO BusinessEvents DataGrid component. See DataGrid Discover URL and DataGrid Listen URL for more details.

ORACLE: Uses a supported version of Oracle Coherence, for which you have a license that is appropriate for your usage. Requires additional configuration. See Enabling Use of Oracle Coherence as the Cache Provider and Oracle Coherence Cluster Discovery for details.

Cache Agent Quorum Yes Specifies a minimum number (quorum) of storage-enabled nodes that must be active in the cluster when the system starts up before the following occur:
  • Data is preloaded from the backing store, if a backing store is configured and preloading is configured .
  • The other agents in the cluster become fully active.

The property does not affect the running of the deployed application after startup (though a message is written to the log file if the number of cache agents running falls below the number specified in this property). As a guideline, set to the number of cache agents configured.

Default is 1.

Number of Backup Copies Yes The number of backup copies (also known as the backup count) specifies the number of members of the distributed cache service that hold the backup data for each unit of storage in the cache. Recommended values are 0, 1, or 2.

Value of 0 means that in the case of abnormal termination, some portion of the data in the cache will be lost. Value of N means that if up to N cluster nodes terminate at once, the cache data will be preserved. A backup count of 1 means one server plus one backup are needed, that is, two cache agents (or storage enabled nodes if cache agents are not used).

To maintain the partitioned cache of size M, the total memory usage in the cluster does not depend on the number of cluster nodes and will be in the order of M*(N+1).

See Synchronous and Asynchronous Replication of Cache Objects for details on replication behavior and options for TIBCO BusinessEvents DataGrid.

Default is 1.

Entity Cache Size Yes Specifies the size of the limited cache, in number of cache entries for each object type. The setting is per processing unit. See Configuring a Limited (or Unlimited) Cache .

Default is 10000 (entries per object type)

Object Table Cache Size Yes Specifies the maximum size of the object table cache, in number of entries. Used with limited cache only.

See The Role of the Object Table in TIBCO BusinessEvents Architect’s Guide for more details about the object table.

Also see Configuring a Limited (or Unlimited) Cache .

Default is 100000 entries

TIBCO BusinessEvents DataGrid
Discovery URL Yes Specifies how an engine (node) listens for discovery requests from nodes attempting to join the cluster. PGM protocol is supposed for multicast discovery. TCP Protocol is supported for unicast discovery
ListenUrl Yes The discovery mechanism is based on pure TCP. All the designated well known metaspace members are identified by an IP address and a port number.
Remote Listen URL Yes Specifies on which IP address and TCP port this proxy metaspace member will be listening for the remote client connections.
Protocol Timeout Yes Indicates the protocol timeout value for space. The protocol can be unicast or multicast.

Default value is -1 (forever).

Read Timeout Yes Indicates the read timeout value for the space, if a read timeout has been set. It specifies the read timeout value for a specified SpaceDef. The read timeout value applies to Get operations.

Default value is 60000 (ms).

Write Timeout Yes Indicates the write timeout value for the space, if a write timeout has been set. Specifies the write timeout value that is set for the space. The write timeout value applies to Put, Take, Lock, and Unlock operations.

Default value is 60000 (ms).

Lock Timeout Yes For a space that is locked, it specifies how long a member process will wait for it to become unlocked.

The default is -1 (forever). Other valid values are 0 or any positive value.

Shutdown wait Yes Indicates the shutdown wait value for the space.

Default value is 8500 (ms).

Worker Thread Count Yes Indicates the thread count specified for the space.

Default value is 4.

Store Properties as Individual Fields No Enabling this property sets the property be.engine.cluster.as.tuple.explicit to true.
Security Enabled No Enables Transport level security for the DataGrid when selected.

The following fields are displayed only if the Security Enabled checkbox is selected:

  • Policy File
  • Policy File Identity Password
  • Token File
  • Token File Identity Password
  • LDAP Identity File
  • Domain
  • Username
  • Password
Policy File Yes Absolute path to the policy file which contains the security settings that the controller node enforces. It is generated using the as-admin utility.
Policy File Identity Password Yes The password for the identity key in the security policy file.
Token File Yes Absolute path to the token file which is used by requestor to connect to a metaspace whose security is defined in the policy file.
Token File Identity Password Yes The password for the identity key in the security token file.
LDAP Identity File Yes The absolute path for a file containing the key to use for LDAP with the certificate based authentication.
Domain Yes Optional. Domain name for system based user authentication.
Username Yes User name for LDAP and system based authentication.
Password Yes Password for LDAP and system based authentication. In case authentication type in the policy file is "x509" then this is the password is for the private key in the LDAP Identity File.