Configure Message Queuing resources for server clusters
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To configure Message Queuing resources for server clusters
Click Start, point to All Programs, point to Administrative Tools, and then click Cluster Administrator.
To create a Message Queuing resource:
When the Open Connection to Cluster dialog box appears, in the Cluster or server name list box, select the applicable cluster or server. If you select a server, the name of the cluster to which it belongs will appear in the console tree (console tree location is: ClusterName/Groups/YourGroup).
In the console tree, right-click the cluster group to which you want the Message Queuing resource to belong.
On the File menu, point to New, and then click Resource.
In the New Resource Wizard, type the applicable information in Name and Description, select Message Queuing in the Resource type list box, and then click Next.
On the Possible Owners page, if you want to add nodes to the automatically chosen list under Possible owners, select them from the list under Available nodes, and then click Add. If you want to remove nodes from the automatically chosen list under Possible owners, select them in this list, click Remove, and then click Next.
On the Dependencies page, under Available resources, select the name of the Network Name resource in the group and click Add, and then select the name of the Physical Disk resource in the group and click Add. Then click Finish.
If Message Queuing has the Active Directory Integration component installed, enable Kerberos authentication for the Network Name resource on which the Message Queuing resources depends. This is not enabled by default. To enable, do the following:
To bring the Network Name resource offline, in the console tree for the cluster group, right-click the Network Name resource selected as a dependency in the details pane, and then click Take Offline.
Right-click the Network Name resource again, and then click Properties.
On the Parameters tab, select the Enable Kerberos Authentication check box, to enable authentication.
To bring the Network Name resource online, in the console tree for the cluster group, right-click the Network Name resources in the details pane, and then click Bring Online.
Caution
- Other resources in the group may also depend on the Network Name resource. These will be taken offline automatically when the Network Name resource goes offline. When you bring the Network Name resource online, bring these other resources online too.
To bring the Message Queuing resource online, in the console tree, click the Resources folder. In the details pane, click the Message Queuing resource. On the File menu, click Bring Online.
To manage the Message Queuing resource from Computer Management, create a Generic Application resource in the same cluster group and configure it to launch the Computer Management MMC snap-in:
In the Cluster Administrator console tree, click the cluster group to which the Message Queuing resource belongs.
On the File menu, point to New, and then click Resource. The New Resource Wizard launches.
In the New Resource Wizard, type Computer Management in the Name text box and select Generic Application in the Resource type list box. Then click Next.
On the Possible Owners page, select possible owners to match those selected for the Message Queuing resource. Then click Next.
On the Dependencies page, under Available resources, select the name of the Network Name resource in the group and click Add, and then select the Message Queuing resource previously created and click Add. Then click Next.
On the Generic Application Parameters page, in Command line, type mmc compmgmt.msc.
In Current directory, type %windir%/system32.
Select the Allow application to interact with desktop check box, select the Use Network Name for computer name check box, click Next, and then click Finish.
Bring the resource online using the procedure above. The Computer Management snap-in will appear on the desktop of the computer node that owns the resource.
Notes
This task is performed on a computer that is running Windows Server 2003, Enterprise Edition or Windows Server 2003, Datacenter Edition as part of a server cluster, and has the Message Queuing service already installed.
If you want to use triggers, HTTP messaging, or external transactions in your cluster, before creating a Message Queuing resource in any cluster group hosted on a node of a server cluster, you must configure a Microsoft Distributed Transaction Coordinator (DTC) resource in the cluster. For instructions on creating a cluster, see Create a cluster, in Server Clusters Help.
Errors occurring during the performance of this task are recorded in a Windows event log. For example, a "device not ready" error indicates that Message Queuing was not installed on the node.
All Message Queuing applications that run in the context of a cluster group (whether cluster-aware or not) must depend on the Message Queuing resource in that group, and use the Network Name resource in that group. Repeat the steps stated above for the Computer Management MMC snap-in to properly configure Generic Application resources for "cluster-unaware" applications.
Once created, do not rename resources for Message Queuing.
If the virtual Message Queuing service managed by the Network Name resource will access Active Directory, you must enable Kerberos authentication on the Network Name resource on which the Message Queuing resource depends. Note that this feature is not enabled by default.
You can also enable Kerberos authentication from the command line by typing the following command cluster res "Network_Name_resource_name" /priv RequireKerberos=1:DWORD
When you select the Physical Disk resource in the group, Message Queuing allocates its storage in the MSMQ\STORAGE folder on the shared disk. After storage has been allocated, you cannot modify the folder location.
To uninstall Message Queuing on a computer that is part of a server cluster, the Message Queuing virtual server must be deleted from the node before uninstalling Message Queuing on the physical node. For example, if Message Queuing is installed on NodeA of a server cluster, you need to identify all Message Queuing resources on this cluster, ensure that NodeA does not own any cluster groups containing Message Queuing resources, and remove NodeA from the list of possible owners of each Message Queuing resource. Then you uninstall Message Queuing from NodeA.
Information about functional differences
- Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.
See Also
Concepts
Message Queuing servers
Administering server cluster nodes
Installing Message Queuing in a server cluster