Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

Configuring Clustered Servers

TeamConnect's clustering feature allows transparent failover and recovery for end users. In the event of a node's failure, each session on that node is transferred to another node, preserving even the uncommitted edits in the session's browser.

In the case of a recovered session, all work is saved except the uncommitted edits in the browser of the expired session.

Each application server vendor implements clustering and cache synchronization in a different way. This section does not discuss details of a specific vendor's implementation, but describes properties of TeamConnect that are common across all implementations.

Configure your application servers for session replication across all nodes. All nodes must run exactly the same version of TeamConnect.

Editing teamconnect.properties

The TeamConnect installer makes many changes to teamconnect.properties when it runs but to configure clustering you will need to make additional manual edits. Each node in a cluster runs an identical copy of TeamConnect, so the properties file needs to be edited only once per cluster.

Here are the properties that require editing, with their definitions:

Clustering Properties

Property Name

Definition

Suggested or example value

sync.enabled

A YES or NO value that determines whether TeamConnect attempts to do cache synchronization YES

sync.channel

Use a unique character string of your choice. The purpose of this property is to avoid the situation where multiple clusters of application servers are running on the same network, and one cluster attempts to synchronize cache with a different cluster Each cluster should have a different value in this property.

Spend Management

sync.rmi.port

This port provide a single numerical value representing the desired port number for the RMI registry or server to listen on and will be used by all nodes in the cluster. The RMI registry is started in-process by TeamConnect. 

2258

sync.multicastGroupAdd ress

This parameter specifies the multicast group address to be used for communication within the cluster. The multicast group address acts as a virtual destination for messages sent within the cluster. It is Optional. By default, it is 226.10.12.64.

226.10.12.64

sync.multicastPort

This parameter defines the port number associated with the multicast communication. By specifying the multicast port, the nodes in the cluster can listen on that port to receive multicast messages related to cluster synchronization. It is Optional. By default, port number is 3121.

3121

Additional Information

Importance of sync.multicastGroupAddress and sync.multicastPort fields

sync.multicastGroupAddress and sync.multicastPort are configuration parameters that determine the multicast group address and port used for inter-node communication in a cluster. These settings enable efficient and coordinated information exchange among the cluster nodes, facilitating synchronization and ensuring consistent states across the distributed system.

Is sync.rmi.port should be a numerical value or a numerical range value?

RMI (Remote Method Invocation) is a Java API that allows objects to invoke methods on remote objects in a distributed system. The sync.rmi.port parameter is used to configure the port number on which the RMI registry or RMI server listens for incoming RMI requests. So when configuring the sync.rmi.port, you should provide a single numerical value representing the desired port number for the RMI registry or server to listen on.

Special Considerations for IMAP

If you are using IMAP to integrate with an Exchange server, you must configure TCP/IP load balancing. IMAP does not use the failover or recovery capabilities of the main TeamConnect clustering feature.

  • Was this article helpful?