Use these steps to create a Responder Windows Service for each group in your server cluster and to create the resource that allows Responder to work with a server cluster.

1. Create a batch script that creates a Responder Windows Service for each virtual server. You may cut and paste the code below to create a batch script. The portion that begins "sc" and ends with the DisplayName value must be repeated in the batch script for each virtual server. The sample below is for two virtual servers: Responder0 and Responder1. Your script may include additional servers. There are two values in this section that must be edited for each virtual server:

   Responder Windows Service: The first highlighted area in the sample below is the name of the Responder Windows Service. The Service Name for each virtual server must be unique. Make note of these names as they will be necessary when creating a resource in later steps.

   DisplayName: The second highlighted area is the name that will appear in the Services window (Computer Management). To avoid confusion, create a DisplayName that is similar to the Service Name.

   @echo off set RXWS_INSTALL_DIR=%ProgramFiles%\Miner and Miner\Responder\Server sc create responder0 binPath= "%RXWS_INSTALL_DIR%\Miner.Responder.WindowsService.exe" type= own start= demand error= normal depend= msmq obj= "NT AUTHORITY\NetworkService" DisplayName= "Responder 0" sc create responder1 binPath= "%RXWS_INSTALL_DIR%\Miner.Responder.WindowsService.exe" type= own start= demand error= normal depend= msmq obj= "NT AUTHORITY\NetworkService" DisplayName= "Responder 1" pause

2. Run the batch script on every node (physical server) in the server cluster. This places a Responder Windows Service on each node in the server cluster for all virtual servers that could failover to that node.
3. Using the Cluster Administrator, create an active/active server cluster (see Additional Resources section on the Server Clustering page to obtain information).
4. Create a group for each active node (e.g., Responder Server configuration) participating in the server cluster.
5. Create the following resources for each group.
   • Physical Disk
   • IP Address
   • Network Name
   • Message Queuing

Next you will create the resource for the Responder Windows Service using the Cluster Administrator. Perform these steps for each group. These steps make the Responder server work with a cluster.

6. With the group selected, right click in the window at the right and select New | Resource.
7. In the New Resource window, give the resource a name. This is the name that will be displayed in the Cluster Administrator and may be anything you like.
8. In the Resource Type field, select Generic Service.
9. Choose the group to which you're adding the resource. By default, this will be the selected group. Click Next.

   

10. The Possible Owners screen shows all nodes (i.e., servers) that participate in the server cluster. The Possible Owners list shows all servers onto which the current group may failover. By default, all nodes in the server cluster are selected. Click Next to continue.

    All possible owners should be included in ALL resources within a group. For example, if you create three possible owners in the Responder resource, then those same three owners must also exist in the other resources (e.g., Physical Disk, IP Address, Network Name, Message Queuing) within the same group.

11. On the Dependencies screen, select the resource that represents MSMQ and add it to the Resource Dependencies column. Click Next to continue.
12. In the Generic Service Parameters window, enter the Service Name. You specified this name using the batch script created in step 1. Indicate the Responder Windows Service name that corresponds to the group for which you're creating the resource.
13. Select the "Use Network Name for computer name" checkbox. Click Next to continue.

     

14. You are not required to enter a value on the Registry Replication screen. Click Finish.
15. The resource is added to the group and displayed in the right-hand window when the group is selected on the left. You may right-click the resource and select Properties to view the properties you just configured.
16. Open Miner.Responder.WindowsService.exe.config. By default this file is installed here: Program Files\Miner and Miner\Responder\Server\.
17. Look for the following line of XML:

<WebServer Enabled="true" Port="7997" VirtualPath="/" AllowRemoteRequests="false"/>

18. Add a FallbackPorts attribute to this tag. The FallbackPorts value supports deliminated values (7998 7999 8000), ranges (7998-8000), and a combination of both (7999 8500-8550 9000). The Responder Windows Service web page uses this value. Your finished tag may look like this:

         <WebServer Enabled="true" Port="7997" FallbackPorts="7998 8200-8300 9000 9340" VirtualPath="/" AllowRemoteRequests="false"/>
    

    Responder looks first for the Port value. If that port is not available, it looks for those listed in the FallbackPorts attribute.

19. Save and close Miner.Responder.WindowService.exe.config.

Optional steps for Query Services users

1. Browse to and open Miner.Responder.QueryWindowsService.exe.config. You can use a text editor (e.g., Notepad) to edit this file. 

   Do not use a word processing program such as WordPad or Microsoft Word to edit XML files because they can corrupt your configuration file.

2. Edit the <wellknown> tag defined inside the <client> tag to point Query Services to Data Services. By default, the url attribute of the <wellknown> tag points to the localhost using a period (.). Replace this period with the cluster name ({ComputerName} replaces the period in the following example).
   

   Edit wellknown tag	Copy Code
   <client> <wellknown type="Miner.Responder.Shared.IDataServices, Miner.Responder.Shared" url="msmq://FormatName:DIRECT=OS:{ComputerName}\private$\rxserver/DataServices.rem" /> </client>

Send Comment to ArcFMdocumentation@schneider-electric.com