On Cloud Computing, Integration Technology, Mobility, RFID, ERP etc...
Sr, Program Manager at Microsoft and MBA from UNC Chapel Hill.My small world includes my beautiful wife Swati and our awesome twin boyz Arni and Abhi.
We at Microsoft feel Community and its involvement is key to success of any product. We recently released more BizTalk Server 2006 R2(http://msdn2.microsoft.com/en-us/library/aa548004.aspx) and BizTalk RFID(http://msdn2.microsoft.com/en-us/library/bb749758.aspx) documentation to MSDN library online with community Content(Wiki) feature enabled.
This feature allows anyone registered with MSDN online using a passport account to contribute to the content of the documentation. So please provide your feedback and help us improve a great product.
Microsoft launched its RFID platform in September 2007. BizTalk RFID has many features and I will post many of these in over next few weeks on this blog. Today I want to focus on 3 pillars of Microsoft RFID Platform.
When any organization think about deploying RFID solutions there are 3 areas to think about RFID application, RFID Infrastructure and Integrations with existing systems. Therefore our 3 pillars map to these 3 areas.
Imagine all this for a price starting at 1.8K $ in production(Buy Here) and less than 500$ for developer license(Buy Here). Our goal is to make RFID a mass adoption technology and we do not want price to be the blocking factor in that goal. :)
There is 4th pillar that we are working on but more on that later. Keep tuned for more information on each pillar.
Upgrading from Beta 2 or RC to RTM is a bit tricky. I hope this upgrade is not very painful for lot of you guys. I would like to assure you all we will keep this much simpler in future releases.
A direct upgrade from Beta 2 / RC version of BizTalk RFID to the RTM version is not supported. Instead users have to follow the procedure given below to upgrade. 1. Export the processes configuration and deleted all processes. The processes may be exported using the Export Processes option from within the RFID Manager. To do this: - Open the RFID Manager. - Right click on Processes -> select Export... - Move the required processes from the "Available Processes" section to the "Selected Processes" section. - Ensure that the "Export Bindings" option is selected to retain the Process Properties and the Device Binding information. - Specify a suitable filename and location where the information should be exported. - Click on Start Export. Alternatively, the processes can be exported using the RfidClientConsole utility with the ExportAllProcesses or ExportProcesses switch. 2. Export the Devices configuration and delete all devices. This step is required only if you have devices with username/password authentication. The devices may be exported using the Export Devices option from within the RFID Manager. To do this: - Open the RFID Manager. - Right click on Devices -> select Export... - Move the required devices from the "Available Devices" section to the "Selected Devices" section. - Ensure that the "All device properties" option is selected under Export Options in order to export the device information along with device properties. Note: For this option to work, the respective devices must be online during the Export. - Specify a suitable filename and location where the information should be exported. - Click on Start Export. Alternatively, the devices can be exported using the RfidClientConsole utility with the ExportAllDevices or ExportDevices switch. 3. Uninstall the current version of BizTalk RFID. 4. From BizTalk RFID RC onwards, the minimum SQL Server requirements for BizTalk. RFID have been changed to reflect the latest service packs: - SQL Server 2005 SP2: SQL Server 2005 Service Pack 2 ---> Version: 2005.90.3042 - SQL Server 2000 SP4: SQL Server 2000 SP4 ---> Version: 2000.8.00.2039 If users are upgrading from BizTalk RFID Beta 2 to RTM, the latest Service Pack for SQL must be applied before BizTalk RFID RTM may be installed. 5. Install the RTM version of BizTalk RFID using the same installation parameters as the previous installation. IMPORTANT: Make sure that you DO NOT overwrite the RFID Store. 6. If the Provider(s) version has changed, copy the new provider binaries into the Provider app base folder. This should be located at %RFIDDataDir%\Providers\<Your Provider>\bin. 7. Edit the exported process XML file to change version number of Microsoft.Rfid.OobComponents.dll from 184.108.40.206 to 220.127.116.11, and also references to any other binaries, the version of which may have changed. 8. Import the exported Devices by using RFID Manager. For imported devices that have username/password authentication, re-enter the username and password using RFID Manager. 9. Import the exported Processes from xml and re-enter the Process Bindings that are of type SecureString. 10. If users have any Process components built on the Beta 2 / RC builds, these must be replaced with the latest binaries compiled against the RTM build. (Version of RFID assemblies have been bumped up from 3.0 to 3.6. Hence Beta2/RC assemblies will require a re-compile to be used in RTM.) The public components can be found in the GAC, whereas the private components can be found at the location %RFIDDataDir%\Processes\<Your Process>\bin. [Note: The sink database that was used in Beta2 / RC (in case any process has a Sink Event Handler), can be used in RTM directly without requiring any migration steps]
Anush has posted a great summary of AMR report focusing on BizTalk RFID. In short AMR says BizTalk RFID is going to make RFID available for everyone. It is an amazing read. I will highly encourage everyone to take a look. Microsoft is really changing the dynamics in RFID implementation. Take a look at the post at http://blogs.msdn.com/biztalkrfid