Communication Management 

Purpose

This system is responsible for managing client connections to the cluster and for managing the communication between the cluster elements.

Features

The communication management system uses several J2EE Engine managers to complete its functions.

Cluster Manager

This manager is responsible for managing the communication between the elements in the cluster. It updates information about the status of each cluster element and the services running on it. The information that is kept concerns the communication status. For more information about the different communication mechanisms offered by the Cluster Manager, see Cluster Communication.

For more information about configuring the different communication mechanisms, see:

·        Configuring the Message Server Communication

·        Configuring the Session Communication

·        Configuring the Lazy Communication

Ports Manager

This manager is a non-distributed system that manages ports on which sockets are opened. It stores information about the mapping of a port and the service that uses it, collects data about all Sockets and ServerSockets, and registers listeners on the TCP port. The TCP ServerSockets are then opened and wait for user requests. When a client request comes, a socket is created (the client socket type depends on the type of the ServerSocket.) For more information, see Ports Management.

Connections Manipulator Manager

This manager provides options for managing client connections to the cluster. The client access to the cluster is available through the dispatcher only. Therefore, this module runs solely on dispatchers.

Each connection is associated with a particular socket (TCP/IP), through which the data transfer is completed and is connected to a specific service. This connection comprises two buffers – one for client data and another for the data from the server to the dispatcher. For more information, see Connections Manipulation.

 

See also:

Cluster Communication in the Architecture Manual