Monthly Archives: January 2009

BizTalk RFID 2009 – PhidgetRFID

1
Filed under BPI
Tagged as , ,

    Below are the steps I used to get my BizTalk RFID up and running with respect to PhidgetRFID. You have to use 3.6.0.0 for BizTalk Server 2006 R2, and 3.7.0.0 for BizTalk Server 2009 Beta

    Make sure the Microsoft BizTalk RFID Service is running!

    Download Phidget software (http://www.phidgets.com/downloads.php?os_id=1)

    Copy the Phidget21.NET.dll to the GAC

    Start RFID-full.exe and check if your Reader is working. If not, make sure it is connected to your computer (or Virtual Machine). You don’t need to install this device. Windows will recognize it and installs it as a Human Interface Device.

Download “”BizTalk RFID Device Provider (DSPI) for Phidget Devices”. (this version works with the PhidgetRFID): http://blogs.msdn.com/irvingd/pages/biztalk-rfid-device-provider-dspi-for-phidget-devices.aspx

Build Phidget_BizTalkDSPI_src against the right BizTalk.RFID version (3.6.0.0 for BizTalk Server 2006 R2). The original Dll is build against BizTalk Server 2006 R2 Beta (3.0.0.0).

Copy the Dll’s Microsoft.PhidgetDevices.dll and Microsoft.PhidgetDevices.DSPI.dll to the  GAC

Copy these Dll’s also to the folder: PhidgetPackage (where PhidgetProvider_Install.cmd resides)

Change the file PhidgetProvider_Install.cmd

Microsoft.PhidgetsDevices.DSPI  must be Microsoft.PhidgetDevices.DSPI

Run PhidgetProvider_Install.cmd

Install DupElim (Duplicate Eliminator): http://go.microsoft.com/fwlink/?LinkId=99664 (This sample eliminates duplicates from TagReadEvents and TagListEvents)

Change the file FilterProcess.xml. Change 3.0.0.0 to 3.6.0.0

Build: DuplicateTagIdsElimination.csproj (against the BizTalk.RFID assemblies 3.6.0.0)

Run EventHandlerSampleSetup.cmd

Open RFID Manager

The Device Providers must contain a Phidgets Provider

Add your reader to the Devices

Below Processes the DupElim creates a dummy process. Change this one, or Add a new one and use as component besides the SqlSink the DupElim component.

After starting all, your reader will receive events (tags) and put it in SQL Server in the TagsEvent table.

This works for me. If you have still some problems, then you can have a look at:

http://blogs.msdn.com/irvingd/pages/biztalk-rfid-device-provider-dspi-for-phidget-devices.aspx
http://blogs.objectsharp.com/cs/blogs/matt/archive/2007/06/09/biztalk-r2-rfid-and-working-with-a-real-reader-device-phidget.aspx

If you use custom accounts for the Service and the Worker Process, then make sure these accounts are added in SQL Server. The Service account must have access to the RFIDSTORE. The Worker Process must have access to the ‘rfidsink’ database.

As I blogged earlier I had problems with BizTalk RFID 2009 (Beta, 3.7.0.0). But after following the steps above I managed to get BizTalk RFID up and running (use .Net Framework 2.0). I had only 1 small problem ;-) my database ‘rfidsink’ was not created. This database is installed with BizTalk RFID, but something went wrong or it is really a beta product. Finally I took the rfidsink database from BizTalk Server 2006 R2. And as I can see now, it works all fine :’-) Now I can focus on the real process.

I you have any suggestions or questions let me know.

Vincent: thanks for your support

  • Share/Bookmark

BizTalk RFID Phidgets Provider

0
Filed under BPI
Tagged as ,

I was playing around this week with this technology and finally past the Provider configuration in RFID Manager. It is very important that you build the “PhidgetDSPI” against your .Net Framework and BizTalk RFID components (3.6.0.0 for BizTalk Server R2 / RFID). Make also sure that you install/copy the assembly Microsoft.PhidgetDevices.DSPI.dll and Microsoft.PhidgetDevices.dll to the GAC (else it will complain).

Note: if you use PhidgetProvider_Install.cmd, then search on Microsoft.PhidgetsDevices.DSPI and change to Microsoft.PhidgetDevices.DSPI. Note: manual works also…

  • Share/Bookmark

BizTalk Software Factory – installation error

0
Filed under BPI
Tagged as , ,

When you receive the next message: Unable to get installer types in the C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\BizTalk Software FactoryInstaller.dll assembly. –> Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

clip-image002-thumb1

Then make sure you installed the GuidanceAutomationToolkitForVS2005 !!!

  • Share/Bookmark

Installing Microsoft ESB Guidance 2.0 CTP2

0
Filed under BPI
Tagged as ,

BizTalk Server 2009

1.

Because of the problems with the first version, I followed the Installation Instruction (yeah, we sometimes do this ;-) . I installed all pre-requisites (Powershell is a feature
of Windows Server 2008). But during installation I get the next error message:

Error while importing "C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 – January 2009\Microsoft.Practices.ESB.CORE.msi".
Change requests failed for some resources.
Unable to process create change request for BizTalk binding "BindingInfo.xml". Import bindings (overwrite) failed.
Failed to update binding information.
Cannot update send port "ALL.Exceptions".
Cannot update transport information (address "SQL://(local)/EsbExceptionDb/").
The following items could not be matched up to hosts due to name and/or trust level mismatches:
Item: ‘SQL’ Host: ‘BizTalkServerApplication’ Trust level: ‘Untrusted’
You must do one of the following:
1) Create hosts with these names and trust levels and try again
2) Re-export the MSI without the binding files and have a post import script apply a suitable binding file.

You would think that I didn’t configure my BizTalkServerApplication properly, but I did. So probably there is an error in the binding file. If you install the Msi straight away you can find the binding file in the 49th Cab file (ITEM~49.CAB). I changed the binding file so it matches my Hosts (Trusted="true" instead of Trusted="false"). After
installing the Msi ‘Microsoft.Practices.ESB.CORE_NOBINDING.msi’ in BizTalk I imported the Binding file manually. And this works.

A pity this workaround (or question during installation) is not described.

2.

Don’t forget the EntLib 4.0 Dll’s must be in the GAC. Because else you will get an error in the ESB Configuration Tool when you try to configure the Itinerary Database.

I didn’t configure the Optional Components yet or did dive into this new ESB Guidance, so stay tuned…

  • Share/Bookmark

BizTalk Server Clustering

0
Filed under BPI
Tagged as , ,

There are people/customers who are talking about a BizTalk Server cluster, but they actually mean a BizTalk Server group (when they use BizTalk Server 2006 R2 or older). With SQL Server you can cluster.

And new within BizTalk Server 2009: you can make also a cluster: “By taking advantage of Windows Server 2008 clustering, BizTalk Server is now able to be deployed in multi-site cluster scenarios, where cluster nodes could reside on separate IP subnets and avoid complicated VLANs.” (see: http://www.microsoft.com/biztalk/en/us/roadmap.aspx)

  • Share/Bookmark

BizTalk Server 2009 and the good old HAT

0
Filed under BPI
Tagged as , ,

As you maybe have noticed in BizTalk Server 2009 the good old HAT is not there anymore. Actually, it is still there, but not for the queries. It seems that its only purpose is for the Orchestration Debugger (and Message Flow etc), which still isn’t integrated in Visual Studio (maybe the final release?).

Anyhow: what I am missing are the predefined queries from the HAT. You can create your own queries. If you compare the query builder with BizTalk Server 2006 R2, then you can see that you have more predefined possibilities, so that it is not that hard to retrieve the information you want. For example:

image

When you right click an Orchestration you can select the Orchestration Debugger:

image1

As you can see: the old stuff (but it still works)

  • Share/Bookmark

Testing with BizTalk Server 2009

0
Filed under BPI
Tagged as , ,

Have a look at the blog: http://geekswithblogs.net/michaelstephenson/archive/2008/12/12/127828.aspx

This one contains some links to some test features in BizTalk Server 2009.

  • Share/Bookmark