Configure trigger 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 trigger resources for server clusters
Click Start, point to All Programs, point to Administrative Tools, and then click Cluster Administrator.
To create a Message Queuing Triggers 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.)
In the console tree, right-click the cluster group to which you want the Message Queuing Triggers resource to belong (console tree location is: *ClusterName/*Groups/YourGroup).
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 Triggers in the Resource type list box, and then click Next.
On the Possible Owners page, select the set of possible owners to match that of the Message Queuing resource in the same group, and then click Next.
On the Dependencies page, in Available resources, select the name of the Message Queuing resource in the group, and then click Add.
Select the name of the Network Name resource in the group, click Add, and 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 depend:
Bring the Network Name resource offline as follows: In the console tree for the cluster group, right-click the Network Name resource 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. The default setting is that Kerberos authentication is not enabled.
Bring the Network Name resource online as follows: 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 Triggers resource online, in the console tree, click the Resources folder. In the details pane, click the Message Queuing Triggers resource. On the File menu, click Bring Online.
To manage the Message Queuing Triggers 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 Triggers 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 Triggers 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 Triggers 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, has Message Queuing with Triggers already installed, and has a Message Queuing resource already configured.
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.
Once created, do not rename resources for Message Queuing Triggers.
The trigger and rule definitions for the cluster resource created are stored in subkeys in the local Windows registry under a special key. The Message Queuing Triggers resource is checkpointed with this registry key and the subkeys under it so that when the resource is moved to a new node (during failover, for example), the required keys are propagated to the local registry on the new node. After failover, the Triggers service can thus continue to process the incoming messages in each monitored queue and invoke the applicable stand-alone executable or COM component according to the rules defined.
You can use the Generic Application resource created with a dependency on the Message Queuing resource to manage Triggers in the applicable resource group from a local Computer Management snap-in. For more information on these resources, see Related Topics.
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
Configure Message Queuing resources for server clusters
Installing Message Queuing in a server cluster
Message Queuing servers
Installing Message Queuing triggers
Working with MMC console files