What's New In BizTalk Server RFID

This section contains information about the enhancements and new features in BizTalk Server RFID.

.NET Framework Support

BizTalk RFID supports building provider and mobile applications on .NET Framework 4.5.

In .NET Framework 4.5, you can reuse the application DLLs which have been built for .NET Framework 4.

Launches MMC from All Programs Only

In BizTalk Server, you can launch the RFID Manager console only from Start > All Programs > Microsoft BizTalk RFID 20xx > RFID Manager.

When you launch RFIDManager.msc from %RFIDINSTALLDIR%bin, you are not able to load providers/event handlers which are built against .NET Framework 4.5 runtime.

New Event Handlers

BizTalk Server RFID introduces six new event handlers. The new event handlers can be categorized into three categories:

  • Event handlers for event filtering

  • Event handlers for event delivery

  • Other event handlers

This section provides more information for event handlers in these categories.

Event Handlers for Event Filtering

RFID environments generate large volumes of data that may or may not be required by an RFID application. Usually, RFID applications include the logic to filter unwanted events. BizTalk Server RFID provides out-of-box event handlers that handle common filtering scenarios, such as duplicate events. RFID application developers can use the following event handlers to help the filter events.

  • DuplicateEliminationFilter – When RFID readers are constantly reading tags, there is a high probability of reading the same tag multiple times. The same tag can also be read by multiple readers/antennae if the tag happens to be in their field of view. The DuplicateEliminationFilter event handler eliminates duplicate events from the incoming event stream. It considers any new tag with the same tag ID and within a specified time, as a duplicate tag and eliminates it. For more information on this event handler see How to Eliminate a Duplicate Tag.

  • Epc Filter – The EPC Filter event handler filters events on the basis of the type of EPC (Electronic Product Code) encoding and the values of the various fields in the encoding. It filters out a tag if a corresponding encoding type is not selected by the user, or if the values specified for the various fields do not match. For more information on this event handler see How to Filter Events by EPC Code.

  • VisibilityFilter – Some applications require information about the unique occurrence of events and any change in the visibility of that event. For example, a truck parked in front of a reader for several hours would be generating continuous stream of the same set of events, while the application is interested in only knowing when the truck is pulled in and pulled out. The VisibilityFilter event handler handles such scenarios by reporting events only when a tag is read for the first time and when a tag is no longer read. For more information on this event handler see How to Use the Visibility Event Filter.

Event Handlers for Event Delivery

The event delivery event handlers aim at providing out-of-box solutions to deliver RFID events asynchronously to the consuming RFID applications. The event delivery event handlers enable delivery of events for the following scenarios:

  • Event delivery to an EPCIS service

  • Event delivery to BizTalk Server

  • Event delivery to a .NET application

To help with these scenarios, BizTalk Server RFID provides two event handlers: EpcisEventForwarder and EventForwarder.

  • EpcisEventForwarder – This event handler forwards the EPCIS events to an EPCIS Capture Service endpoint.

    In a typical scenario, RFID application developers would use the EpcisTransformHandler and EpcisEventForwarder in conjunction. The EpcisTransformHandler would transform the RFID events to EPCIS events and the EpcisEventForwarder would forward the EPCIS events to an EPCIS service. For more information on the EpcisEventForwarder event handler see How to Forward EPCIS Events to a EPCIS Capture Service Endpoint.

  • EventForwarder – The EventForwarder event handler can be used to forward events to a WCF endpoint. The same event handler can be used to forward events to a BizTalk Server application or a .NET application.

    • For BizTalk Server Applications – The EventForwarder event handler posts the events to MSMQ and the WCF-NetMSMQ/WCF-Custom adapter is configured in BizTalk Server to read the events from MSMQ.

    • For .NET Applications – The EventForwarder event handler posts the event to MSMQ and RFID application developers can write a .NET application to read the events from MSMQ.

    For more information on the EventForwarder event handler see How to Forward Events to a WCF Endpoint.

    BizTalk Server RFID provides a sample “EventReceiver” class library to demonstrate how to use the events from MSMQ from a .NET application. The “EventReceiver” class library is available under the “Samples” folder on the installation CD.

Other Event Handlers

  • EpcisTransformHandler - This event handler transforms TagReadEvents and TagListEvents into corresponding EPCIS events. After you have transformed the event using the EpcisTransformHandler, you can use the EpcisEventForwarder event handler to forward the event to an EPCIS service. For more information on this event handler see How to Use the EPCIS Transform Handler.

See Also

Other Resources

Getting Started