Follow the instructions below to configure your Message Router to work in a cluster. The Message Router section contains general information about the message router and its initial set up.

If you are following the active/passive Message Router and active/active Responder Server configurations discussed in Clustering Server 2008 R2, then you will not run the Responder services (Data Services, Archive Services, Prediction Services) on the same machine as the Message Router. This machine will have these services installed, but they should not be running. Run only the Message Router.

Next you will create the resource for the Failover Cluster Manager. These steps make the Responder Message Router work with a cluster.

1. Within the cluster, right-click Services and applications.
2. Select More Actions, then Create Empty Service or Application. A new service is added. For the purposes of this documentation, and to keep instructions succinct, this will be referred to as a Cluster Group.
   
3. Right-click the new cluster group and select Rename. Rename this service for identification purposes (such as MrCG1, for this example, i.e., MessageRouter Cluster Group 1).
4. Right-click MrCG1 and select Add a Resource, then Client Access Point.
   
5. The New Resource Wizard appears and guides you through the process. Enter the network name (we recommend matching the cluster group name: MrCG1) or IP, and click Finish when done.
6. Right-click MrCG1 and select Add storage. Select the unused storage drive.

   Message Router cluster groups require their own storage drive. This must be separate from your Responder cluster group storage device.

   
   
7. Right-click MrCG1 and select Add a Resource, More resources, then Add Message Queuing.
   
8. The MSMQ requires three dependencies. To add these:
   1. Right-click the Message Queue and select Properties.
   2. Select the Dependencies tab.
   3. Add the Storage Resource, Cluster Group Name, and Service IP created in the steps above.
      
   4. Click OK.
      
9. Right-click MrCG1 and select Add a Resource, then Generic Service.
   
10. From the list of services, select Responder (the Message Router process is hosted by the Responder Windows Service). Complete the remaining steps of the wizard. Click Finish.
11. The Responder service requires the MSMQ cluster as a dependency. To add this:
    1. Right-click Responder and select Properties.
       
    2. Select the Dependencies tab.
    3. Add the Message Queue that you created in the steps above and click Apply.
       
    4. On the General tab, ensure the Use Network Name for computer name check box is selected.
    5. Click OK.

    Next, you will need to update the configuration files for the various Responder services to point to the machine running your Message Router. 

    Prior the following, open Miner.Responder.WindowsService.exe.config on the Responder Server, and set the count for all services to zero.

    
    Peform the following steps on these configuration files: Miner.Responder.DataServices.exe.config, Miner.Responder.ArchiveServices.exe.config, Miner.Responder.PredictionServices.exe.config.

    1. Look for the following bit of XML.
       

       	Copy Code
       <channel ref="msmq" isServer="true" />

    2. Add to this tag: router="FormatName:DIRECT=OS:MessageRouterServerName". Replace MessageRouterServerName with the Message Router cluster group name (the name created in step #3 above). So it looks something like this.
       

       	Copy Code
       <channel ref="msmq" isServer="true" router="FormatName:DIRECT=OS:MrCG1" />

    3. Save and close the configuration file. Make this edit in the following configuration files: Miner.Responder.DataServices.exe.config, Miner.Responder.ArchiveServices.exe.config, Miner.Responder.PredictionServices.exe.config.

     

Send Comment to ArcFMdocumentation@schneider-electric.com