Message Queuing servers

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Message Queuing servers

For the purposes of this documentation, the term Message Queuing server refers to a Windows Server 2003 family computer that has Message Queuing installed on it. The term Message Queuing client can refer to either an independent client, or a dependent client. Both of these terms are used to describe Message Queuing servers that have particular Message Queuing components installed, and such computers are referred to as having independent client functionality, or dependent client functionality.

Message Queuing servers also provide the following features:

  • Directory access for all client computers in the Windows Server 2003 family domain or Windows 2000 domain that are running Message Queuing on Windows NT 4.0, Windows 98, or Windows 95 computers.

  • Support for dependent clients.

  • Routing capabilities.

Directory access

Message Queuing servers enable client computers running MSMQ 1.0 clients running on Windows NT 4.0, Windows 98, or Windows 95 computers, and Message Queuing 2.0 clients running on Windows 2000 computers, to view and change information listed in the Active Directory directory service. To do this, the Message Queuing directory service (Downlevel Client Support) must be installed on a Windows Server 2003 family domain controller. For more information, see Installation requirements and restrictions.

Message Queuing independent clients running on Windows Server 2003 family computers can access Active Directory directly without the aid of a Message Queuing server.

Routing capability

Message Queuing servers installed with routing services enabled provide message routing and intermediate store-and-forward message queuing. Such Message Queuing servers can route messages within a site or between different sites when there is no direct connectivity between client computers. Message Queuing servers that provide message routing functions within the same site are called in-routing servers (InRS) or out-routing servers (OutRS). Intersite connectivity is defined by a routing link. A server through which the message traffic from one site to another can be configured to pass in a routing link is called a site gate. A site gate can belong to either or both of the sites connected by a routing link. A routing link can be configured with any number of site gates or no site gate. For more information, see Routing with Message Queuing servers.

For information on sites, see Deploying in a domain environment.

Dependent client support

Every dependent client in your network needs a supporting server, which can be any Message Queuing server with or without routing enabled. By default, following installation, Message Queuing servers are not enabled to support dependent clients. For instructions on enabling a Message Queuing server to act as a supporting server, see Enable a supporting server.