Overview: MCS Agents and Agent Clusters

Some clients make use of the MCS agent, also referred to as the MCS service agent, to communicate with MCS; others communicate directly. Products and components (clients) that implement the MCS agent use the agent to communicate with MCS and make use of its management services, such as event logging.

In most cases, if an agent does not already exist on the client computer, it is installed at the same time as the client itself is installed. If an existing agent is detected during client installation, it is used instead. You can also install the agent separately if necessary.

Communication Between MCS and MCS Agents

The agent communicates with MCS through an assigned server in the MCS server cluster. If that server goes down, the agent finds another server in the cluster and directs future communication through it.

Note Some Attachmate designer components do not use the MCS agent. If any of these attempt to communicate with an MCS server that is not running, the connection will fail unless there is a third-party load balancing solution in place.

Using MCS Agent Clusters

An agent cluster is a logical grouping of one or more computers on which MCS agents are installed. These groups might be based on business functionality, location, or any other logical arrangement. For information about how your product uses MCS agent clusters, see the product guide for your product.

Related Topics
Bullet MCS Server Clustering, Overview
Bullet Adding an Agent Cluster
Bullet Changing the MCS Server Address for an Agent
Bullet Viewing Agent Cluster Information
Bullet Management & Control Services, Overview
  Attachmate