Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Configuring Apache Ignite as the Cluster Provider

TIBCO BusinessEvents provides Apache Ignite as a built-in and open-source clustering option. Apache Ignite is a well-suited option for applications with smaller cluster sizes.

Before you begin Ensure that a CDD file is added to your project, see Adding a CDD File to the Project.

Procedure
1. In the TIBCO BusinessEvents Studio, open the CDD file for editing.
2. On the Cluster tab, select Cluster Management and `Apache Ignite` as the Cluster Provider.
3. Configure the following cluster properties.

Apache Ignite Cluster Properties
Property | Description
--- | ---
Discovery URL | Specify a set of IP addresses and ports for node discovery. For fault tolerant discoveries, specify multiple IP addresses with port ranges as comma separated values. Example: IP1:47500..47510[,IP2:PORTS]
Listen Port | Port to listen on for discovery of nodes in a cluster.
Communication Port | Specify the port or range of ports used by the Ignite Communication SPI.
Socket Write Timeout | Specify the socket write timeout for the TCP connection.
Connect Timeout | Specify the connection timeout used for establishing the connection with remote nodes.
Join Timeout | Specify the join timeout. If a non-shared IP finder is used and a node fails to connect to any address from the IP finder, the node keeps trying to join within this timeout. If all addresses are unresponsive after the timeout, an exception is generated and node start up fails.
Network Timeout | Specify the maximum network timeout for network operations.
Failure Detection Timeout | Specify the failure detection timeout. The failure detection timeout is used to determine how long the communication or discovery SPIs must wait before considering that a remote connection has failed.
Enable Hostaware | Select the checkbox to enable the host-aware replication. By default, the checkbox is selected. When host-aware replication is enabled, if the cache nodes are deployed on multiple machines to satisfy replication by the host, then replication does not happen on the same node (or happens only according to the number of hosts available). If cache nodes within the cluster are on the same machine, then host-aware replication needs to be disabled to honor Number of Backup Copies. When host based replication is disabled then data is replicated on neighbor cache nodes on same machine.
Hostaware Hostname | Hostnames that are used in identifying members (and therefore naming Shared nothing file and folders), are generated from underlying OS. If you would like to assign hostnames manually instead, for reasons such as hostname/machine changes and testing, then provide hostnames in the CDD by using this field.
\

4. (Optional) To enable secure Apache Ignite connection among all nodes, select the Security Enabled checkbox, and fill values for the following fields:

   Field | Description
   --- | ---
   Trusted Folder Path | When using a secure connection, provide the path to the base folder location containing the trust certificate files.
   Identity | Path to the keystore identity file when using the two-way SSL.
   Trust Store Password | Specify a password for the trust store.

5. Save the CDD file.

What to do nextConfigure Apache Ignite as the cache provider. See Configuring Apache Ignite as a Cache Provider for more information.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.