Export (0) Print
Expand All
1 out of 2 rated this helpful - Rate this topic

Installing and Running BizTalk Server 2009 RFID in a Windows Server 2008 Cluster

This document provides step-by-step instructions for installing and running Microsoft® BizTalk® Server 2009 RFID in a Microsoft Windows Server® 2008 cluster.

Microsoft Corporation

Published: September 2009

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, BizTalk, SQL Server, and Windows Server are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

This document provides step-by-step instructions for installing and running Microsoft® BizTalk® Server 2009 RFID in a Microsoft Windows Server® 2008 cluster. We make the following assumptions about the deployment scenario:

  • A four-node cluster using the Cluster service is already set up as follows:

    • Nodes 1-4 run the service that needs to be failed over.

    • The domain controller is outside of this cluster.

    • A computer with Microsoft SQL Server® is outside of the cluster (SQL Server may also be clustered).

  • A client computer has access to the cluster, and is available in the network.

  • The administrator is already familiar with clustering concepts and the use of the Cluster service, specifically the concepts of resource types such as Generic Service, Application resource, and Script resource.

Ee470805.Important(en-US,BTS.10).gifImportant
Setting up Microsoft BizTalk Server RFID on a cluster with SQL Server as a dependent resource in the cluster group is not supported. SQL Server should be on a computer that is not part of the cluster.

BizTalk Server RFID must be installed on a cluster and then tested to verify if the deployment is running successfully.

Deploying BizTalk Server RFID in a clustered environment requires the following actions:

  1. Creating a cluster group and assigning the required resources to the group

  2. Installing and configuring BizTalk Server RFID on each node in the cluster

  3. Configuring the cluster group through Failover Cluster Manager

Testing BizTalk Server RFID in a cluster configuration requires the following actions:

  1. Installing and configuring BizTalk Server RFID on a client computer

  2. Using the client computer to test and verify the cluster group setup (optional)

Deploying BizTalk Server RFID in a Cluster Setup

To create a cluster group and assign resources to it
  1. Using the Failover Cluster Manager tool, create a new cluster group for BizTalk Server RFID (say, BizTalk Server RFID Cluster) in the cluster.

  2. Add IP Address, Network Name, and Physical Disk resources to the group (or make sure that the group contains these resources).

    Ee470805.Important(en-US,BTS.10).gifImportant
    While adding and configuring resources, select the Enable Kerberos Authentication check box. This is applicable only for Microsoft Windows Server 2003 systems.

  3. Enable clustering of MSDTC and Message Queuing (also known as MSMQ) within this cluster group.

    1. Add the “Message Queuing” resource to the group.

    2. Add the “Distributed Transaction Coordinator” resource to the group.

To install and configure BizTalk Server RFID on the cluster nodes
  1. Bring a node online.

  2. On the Choose Setup Type page:

    Ee470805.b9b02e48-49e6-415e-a537-b319a876fa48(en-US,BTS.10).gif
    1. Select the Complete option for installing BizTalk Server RFID.

    2. Specify a Data path for a directory that will contain process, provider, log, and configuration-related folders and files on the Physical Disk resource. Note the directory name. This directory will be used for the other nodes.

  3. On the Database System and RFID Configuration Database Information page:

    Ee470805.d516581a-c98f-4270-8201-8a5bc9145d0c(en-US,BTS.10).gif
    1. Enter the name of the SQL Server computer that this cluster will use. Because the SQL Server computer will be remote, there are specific steps that you need to perform after BizTalk Server RFID installation is complete. These steps are described in the Installation Guide in the section “Preparing to Set Up a Remote RFIDSINK Database.”

    2. To start with a fresh installation of BizTalk Server RFID, select Overwrite contents of Rfid Configuration Database. If you want to preserve the process and device configuration from a previous installation of BizTalk Server RFID, clear Overwrite contents of Rfid Configuration Database (by default, the Overwrite contents of Rfid Configuration Database check box is cleared).

    3. For the SQL Server authentication type, select Windows authentication.

  4. On the Set up the RFID Service and RFID Process Accounts page:

    Ee470805.a3bea2dc-5063-44b3-9966-d30c62e0ac4a(en-US,BTS.10).gif
    1. Select the Specify user name and password option for the RFID Service Account.

    2. For User name, you must enter a domain account. This domain account should be different from the account that is currently running the installation.

    Considerations for the Service Account

    The Service Account for the MSBizTalkRFID service must:

    Considerations for the Worker Process Account

    The Worker Process Account specified must:

    • Be an administrator on the node. The account is required to be a domain account, but a roaming profile is not needed. This account should also have necessary security permissions on SQL Server to access the rfidsink database.

  5. Register Web service proxies on each node.

    On all nodes:

    • Stop the Microsoft BizTalk RFID service (MSBizTalkRFID service).

    • Stop the World Wide Web Publishing service.

    • Register the Microsoft.Rfid.ManagementWebServiceProxies.dll for COM interop. (This is required for the clusrfid.vbs script to communicate with the service.) To register the DLL, open a command prompt and execute the command:

      %windir%\Microsoft.Net\Framework\v2.0.50727\regasm.exe /tlb:rfid.tlb %rfidinstalldir%bin\Microsoft.Rfid.ManagementWebServiceProxies.dll
      
  6. Repeat steps 1 through 5 for each node in the cluster group. For each node, fail over the cluster resource group owner to it before installation.

To configure the cluster group through Failover Cluster Manager
  1. In Failover Cluster Manager, add the MSBizTalkRFID service as a generic service to the BizTalk Server RFID Cluster group. Make the MSBizTalkRFID service dependent on all other resources in the group. Select the Use the cluster name as the network name check box.

  2. In Failover Cluster Manager, add a generic script resource to the BizTalk Server RFID cluster. The file to be used for the script resource is located at %RFIDINSTALLDIR%\bin\clusrfid.vbs.

  3. Set up the Discovery feature by performing the steps in the following procedure, “To set up the Discovery feature in a cluster environment.”

  4. Use Failover Cluster Manager to bring the BizTalk Server RFID Cluster group online.

  5. On any node, open a Command Prompt window, browse to the directory %RFIDINSTALLDIR%\Samples\Device Service Provider\Contoso\ContosoEndtoEnd, and then run Contososetup.cmd. This installs a test provider and a test process used in the verification procedure described below. From RFID Manager browse to the SQLServerSink component bindings for ContosoTestProcess and provide the remote SQL Server name for the ServerName property.

To set up the Discovery feature in a cluster environment
  1. On each computer, find the correct network adapter (the network adapter with the description Microsoft Failover Cluster Virtual Adapter) and the associated GUID for the NIC, as follows:

    1. On each node, in a Command Prompt window, run the command ipconfig/all.

    2. In the output, inspect the description of each adapter. Search for the adapter with the description Microsoft Failover Cluster Virtual Adapter.

    3. Make a note of the adapter that has the description Microsoft Failover Cluster Virtual Adapter. The following image illustrates how the adapter name is displayed on a cluster node. The adapter in this example is Ethernet adapter Local Area Connection* 12.

      Ee470805.580a5721-36cb-4324-89f1-a2756629e87f(en-US,BTS.10).gif
    4. At a command prompt, run the command %RFIDINSTALLDIR%\bin\ListMulticastNics.exe. This will generate a file, PickNic.xml, and is available in the current working directory. This XML file lists all available adapters and associated GUIDs.

    5. Open the PickNic.xml file, and locate the entry for the adapter identified in step c. The Id value associated with the adapter is the required GUID. Note the value of the GUID. The contents of PickNic.xml files from two nodes are displayed in the following images. In both these cases, the adapter is Ethernet adapter Local Area Connection* 12.

      Ee470805.8ad2ee9e-65fe-4839-926f-853d61f410f7(en-US,BTS.10).gif

      PickNic.xml from Node1

      Ee470805.f689393d-7e68-4508-9b2a-f2b08c531bfc(en-US,BTS.10).gif

      PickNic.xml from Node2

    6. Repeat steps a through e for each node in the cluster.

    When this step is complete, you must have as many GUIDs as there are nodes in your cluster.

  2. Select the PicNic.xml file from the active node and open the file to edit it.

  3. In the PickNic.xml file, create a <selectedAdapterId> XML node for each node available in the cluster. In each <selectedAdapterId> node, enter the GUIDs that you noted in step 1. When this step is complete, you will have as many <selectedAdapterId> XML nodes as there are nodes in the cluster. For example, in the following image, there are two <selectedAdapterId> XML nodes, one for each of the two nodes in the cluster.

    Ee470805.88977c96-397a-4690-a386-8699676f08a3(en-US,BTS.10).gif

    PickNic.xml after adding GUIDs from Node1 and Node2

  4. Save and close the PickNic.xml file. Copy the file to the %RFIDDATADIR%\Providers\<ProviderName>\ folder of the active node. For example, you must copy the PickNic.xml file to the %RFIDDATADIR%\Providers\LLRP\ folder on the active node.

Testing the BizTalk Server RFID Cluster Configuration

The following procedure assumes that BizTalk Server RFID has already been set up in a cluster configuration by following the steps in the preceding section. To complete this process of verification, you must connect to the cluster by using a client computer.

Considerations for the client computer:

  • The client computer must have network access to the cluster.

  • The client computer must be able to address physical servers (nodes) in the cluster by using the IP address of the cluster.

To verify a BizTalk Server RFID cluster configuration
  1. Start BizTalk Server RFID Setup on a client computer (for example, client01).

  2. On the Custom Setup page, choose to install only the RFID Tools and Client Connector and the RFID SDK.

    Ee470805.a9cb39a3-89de-4263-98f3-bf933f2bea72(en-US,BTS.10).gif
  3. Using Failover Cluster Manager, make the first node in the BizTalk Server RFID cluster group the active node.

  4. On the computer client01, open a Command Prompt window and browse to the directory %RFIDINSTALLDIR%\Samples\Device Service Provider\Contoso\ContosoEndtoEnd\ContosoDeviceSimulator.

    1. Use Notepad to edit the notification configuration XML file (ContosoSimulatorconfig.xml). Change the IPAddress value to the IP address of the cluster as shown:

      <section name="DeviceInformation_1">
      <entry name="DeviceName">ContosoTestDevice</entry>
      <entry name="ConnectionType">TCPIP</entry>
      <entry name="IpAddress">0.0.0.0</entry> INVALID USE OF SYMBOLS CHANGE IPADDRESS 
      VALUE TO CLUSTER IP ADDRESS 
      
      
    2. At the command prompt type runContososimulator.cmd, and then press ENTER.

  5. Start RFID Manager on the client computer, right-click the RFID Services Administration node, and then click Connect. In RFID Manager, provide the name or the IP Address of the cluster to connect to. When connected to the cluster, select the ContosoTestProcess process, and check if the process is receiving tags by opening the View Tags dialog box.

  6. In Failover Cluster Manager, note the owner of the cluster group named BizTalk Server RFID Cluster.

    The owner of the cluster group should be Node1, and all the resources associated with the group must be online.

  7. Using RFID Manager, stop the MSBizTalkRFID service. This will cause BizTalk Server RFID to fail over to the next available node in the cluster group. Wait for a few minutes to enable BizTalk Server RFID to be started on another node.

  8. Using RFID Manager, disconnect from the cluster, and then reconnect to the cluster by using the IP Address or name of the cluster.

  9. You should now be connected to Node2. When connected to the cluster, select the ContosoTestProcess process, and check if the process is receiving tags. If the process is receiving tags, this verifies that BizTalk Server RFID failed over to the next available node in the cluster.

You may need to perform administrative tasks for BizTalk Server RFID.

Adding a Provider or Process

In a clustered environment, any one node will be the active node.

To add a provider or process to BizTalk Server RFID in a clustered environment
  1. Use Failover Cluster Manager to check which node is the currently active node for BizTalk Server RFID.

  2. Log on to the computer that is the active node in the cluster. You may choose to log on to the active node from a remote computer.

  3. Start RFID Manager.

  4. Add a process or provider, as required.

Starting, Stopping, or Restarting the Microsoft BizTalk RFID Service

You may need to stop or restart the MSBizTalkRFID service.

To start, stop, or restart the MSBizTalkRFID service in a cluster, use Failover Cluster Manager. The use of RFID Manager or any other tool/console may interfere with the management of the MSBizTalkRFID service by the cluster, and may cause undesirable results.

This section provides information about some errors you may encounter while configuring BizTalk Server RFID to work in a clustered setup.

Cluster service fails to start

For troubleshooting information when the Cluster service fails to start, see:

MSMQ service resource fails to come online on a node

Check if Kerberos Authentication has been enabled in the properties for Network Name.

BizTalk Server RFID failover does not occur

In addition to failover not occurring, the following message is obtained from the event log:

Service cannot be started. Microsoft.SensorServices.Rfid.StartupFailedException: The Microsoft BizTalk RFID service failed to start because of exception Key not valid for use in specified state.. Resolve the issue that is causing the exception, and then try restarting the service. ---> System.Security.Cryptography.CryptographicException: Key not valid for use in specified state.

This error occurs when BizTalk Server RFID accounts have been incorrectly configured. To troubleshoot the issue:

  • Check if the domain account used as the Microsoft BizTalk RFID service account has a roaming profile.

  • Modify the profile, and then check the profile type again. If the type continues to be local, then use the account credentials to log on, and then log off the computer.

  • If the issue still persists, clear the locally cached profiles (browse to %appdata% folder for that particular profile, and then delete all the files in the folder).

  • Run BizTalk Server RFID Setup, choose to repair the current installation, click Next to go to the Database System and RFID Store Information page, select the Overwrite contents of Rfid Configuration Database check box, and then complete the installation process.

WinSock errors occur

Restart the computer on which the error occurs.

While uninstalling BizTalk Server RFID, an error message is displayed: “Providers is not a valid short file name”

While uninstalling BizTalk Server RFID, this error occurs if the node computer does not have access to the shared disk (resource that hosts the data directory). Before uninstalling BizTalk Server RFID, ensure that the computer is the active node.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.