Mick Badran – BizTalk MVP Training and Integration Specialist Breeze SOA314

Session Agenda BizTalk RFID Mobile Architecture RFID Mobile Prerequisites Getting Started with BizTalk RFID Mobile Major Components and Code Snippets (Demo) Summary

BizTalk RFID Mobile Architecture

BizTalk RFID Mobile applications: Are a standard Windows Mobile Application typically built out of VS.NET2005/2008+ (x86/x64). RFID Mobile extensions are.NETCF assemblies. Same RFID classes exist in RFID Mobile as in RFID Server (cut-down though) *Difference* - no RFID Processes exist in RFID Mobile. Your application is the Process space Can run in Standalone Mode – no need for Server connectivity. E.g. building maintenance inventory tracking. Can forward events back to RFID Server through a durable store/forward technique. Can read Tags in Sync/Async mode (Provider dependant) RFID Mobile can use Storage Cards for Database locations.

BizTalk RFID Mobile Architecture… BizTalk RFID Mobile Framework: Installed onto the Device (approx 2MB) under \Program Files\BizTalkRfidMobile Allows for Provider/Device Metadata Management through a Configuration DB (SqlCe) Logging. Main functional areas: RFID Mobile Management – Stop/Start Providers/Devices Custom Provider creation Sync/Async Tag Commands – gettags()… Tag Data Translation(TDT) – EPC standards based library allowing for manipulation of TagIDs and their data. Local Event Storage or Store/Forward back to RFID Server.

BizTalk RFID Mobile Architecture… If you are building your own Mobile Provider: BizTalk RFID Mobile comes with its own Mobile Provider Certification Tool (PCT) Installs onto the Windows Mobile Device and executed from there. PCT runs a set of comprehensive tests on your custom Provider. E.g Property/Metadata management, Tag Reads, No Tag Reads, Exception handling etc. Produces a report which can be analyzed. Great troubleshooting tool enabling more robust Provider Development.

BizTalk RFID Prerequistes O/S - Windows CE 5.0+.NETCF 2.0+ (on most newer devices tends to be in firmware) SqlCe 3.5 sp1 for Event Storage. SqlCe has 3 main components: SqlCe Runtime – required SqlCe Developer lib – Query Analyzer & Detailed Error Messages SqlCe Replication lib – SqlCe Merge Replication

BizTalk RFID Prerequistes RFID Mobile.NETCF Framework – approx 2MB Destkop Install – BizTalk RFID Mobile Installation extracts out the required files to be deployed down to the device. No desktop/server applications installed...\BizTalk RFID Mobile\x86 (or x64)\Setup.exe After Desktop Install RFID Mobile Files can be found here: C:\Program Files\Microsoft BizTalk RFID\SDK\Mobile\v1.1..\Bin – assemblies to reference in VS.NET..\Bin\WCE500 – mobile runtime, runtime with extra pieces e.g. sample tag read application, custom Provider...\Documentation – Handy

Getting Started Steps 1. Create a SmartDevice Windows Application Project in Visual Studio.NET 2. Reference the BizTalk RFID Mobile dlls from: C:\Program Files\Microsoft BizTalk RFID\SDK\Mobile\v1.1\bin 3. Reference the appropriate Mobile Provider dlls 4. Build Out your application 5. Attach (& cradle) your Physical Windows Mobile Device – if youre using one. 6. Deploy your compiled application to either the Windows Mobile Emulator or Physical Device 7. Test/Debug as appropriate.

Major Components 1. ProviderManagerProxy 2. DeviceConnection 3. Tag Data Translation (TDT) Library 4. NotificationStorage 5. RfidServerConnector

Major Components and Code 1. ProviderManagerProxy – used to Stop/Start/Register/Unregister Providers + Discover Devices.

Major Components and Code -II 1. DeviceConnection – used to the Device to Set/Get Properties; Read/Write Tags

Major Components and Code -III 1. Tag Data Translation (TDT) – library used for easy manipulation of Tags and their data. E.g. look a the Sgtin96Encoding section

Major Components and Code -IV 1. NotificationStorage – used for storing Tag Reads locally. Will automatically create the SqlCe DB + Schema if needed. Can be used with existing Application DBs too.

Major Components and Code -V 1. RfidServerConnector – Store/Forward used for sending Tag Reads back to the RFID Server. Uses a local DB if the device is not connected and will automatically send Tags when connected.

Summary BizTalk RFID Mobile allows for greater flexibility within systems, while reducing infrastructure setup costs. Can build RFID capabilities into an existing application. Easy transition for existing.NET Developers. Tag Events can still be processed centrally Monitoring and Management of Mobile Devices is done centrally through System Center.

Building your first RFID Mobile Application

Summary BizTalk RFID Mobile is exposed as.NETCF assemblies. Mobile DSPI Provider Model structure. Easy skill up for.NET Developer. Apps can be standalone. Apps can be tightly integrated with BizTalk RFID Server. Easily integrate into *your* applications.

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Additional Resources – BizTalk Light and Easy Webcast Series

Sessions On-Demand & Community Resources for IT Professionals Resources for Developers Microsoft Certification & Training Resources Resources Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online.

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Required Slide