Configuring PeopleSoft MCF Clusters

An MCF cluster is a group of multiple MCF-enabled application server domains in which all queue servers and log servers communicate with the same REN server cluster. Only one queue server and one log server in an MCF cluster are active at any one time. These are called the masters. The rest are dormant and redundant, and are called the slaves. If a master drops out of the cluster for any reason, the slaves elect a new master to take its place.

This section provides an overview of MCF cluster configuration and discusses how to configure MCF clusters.

Each MCF cluster includes a minimum of one queue server and one log server communicating with one REN server. An MCF cluster is typically identified by the ID of the REN server cluster serving it. No configuration limit is placed on the maximum number of queue servers in an MCF cluster.

In MCF architecture, a chat client initiates contact with an agent through the designated external (browser) URL for a REN server. This URL can point to a load balancer, switch, reverse proxy server, or other hardware or software directing requests through a firewall. The external URL is also known as the browser URL because it supports the MCF browser windows (agent chat, customer chat, and MultiChannel Console).

For communication of queue servers, log servers, and application servers with REN servers, for example, handling email requests behind a firewall, you can use an internal URL. Specify both internal (cluster) and external (browser) REN server URLs during MCF cluster configuration.

Note: If no security is implemented, the browser and cluster URLs may be the same.

Access the UQ Cluster page using the following navigation path:

PeopleTools > MultiChannel Framework > Universal Queue > Configuration > Cluster (MCF_UQCLUSTER)

Image: UQ Cluster Page

This example illustrates the fields and controls on the UQ Cluster page. You can find definitions for the fields and controls later on this page.

The UQ Cluster page showing the MCF Cluster ID and having the following editable fields: Description, MCF Cluster URL, MCF Browser URL, Queue Server ID, Application Server Domain, Host Machine, and Description

Field or Control


MCF Cluster ID

Displays the MCF cluster ID.

MCF Cluster URL

Displays the URL for the REN server that serves this cluster. This is the URL that is used by internal processes. If the MCF cluster is served by a REN server cluster, the cluster URL is that of the switch or load balancer in front of the clustered REN servers.

Buffer Test

Click to initiate a test of the REN server's ability to break up and send a large file using multiple internal buffers.

The buffer test does not depend on specified domain names, so you can use it to verify that RENSRV is running on the network.

MCF Browser URL

Displays the URL for a REN server cluster that serves this MCF cluster for external clients and for agent chat. The browser URL may be different from the cluster URL, which should not have to go through any firewall, reverse proxy server, or other outward-facing security barrier.

Ping Test

Click to initiate a test of the REN server that is specified in the URL fields. Failure may indicate that a URL is incorrectly specified.


Click to delete the entire MCF cluster. No active agents or tasks should be on the cluster.

Note: If the cluster's queue server configuration is changed, changes to the actual application server domains must be made manually using PSADMIN. For example, if a cluster member (queue server) is removed, the affected application server domain must be shut down and reconfigured (set the MCF Servers field to No) using PSADMIN. If the cluster URL is changed, all associated queue server domains must be shut down and rebooted.

Queue Server

An MCF cluster can consist of a primary queue server and any number of backup servers.

Each cluster requires a minimum of one queue server. The primary queue server is the first queue server started, and the remaining queue servers are backups. If the primary queue server fails, the system determines the subsequent primary queue server among the backups.

You can add a queue server to a cluster by adding a new row. Before removing a queue server, ensure that it is not the master, and then shut down its domain. Then click Delete (the minus sign).

If a domain is started with a queue server that does not belong to a cluster, the universal queue server and MCF log server poll the MCF configuration tables indefinitely until the queue server is assigned to a cluster.

Field or Control


Queue Server ID

Enter a unique identifier for each queue server to identify its entries in the database control tables.

The log server process that is paired with this queue server uses this same ID to identify its entry in the log cluster table.

Application Server Domain

Enter the application server domain of which this queue server is a member.

Host Machine

Enter the name of the application server host machine.

Note: In some cases, the name of the server may be the fully qualified host name.