Geeks With Blogs

News
Stuart Brierley Integration Management - BizTalk and More

I have previously talked about the installation of the Community ODBC adapter and also using the ODBC adapter to generate schemas.  But what about creating a receive location?

An ODBC receive location will periodically poll the configured database using the stored procedure or SQL string defined in your request schema.

If you need to, begin by adding a new receive port to your BizTalk configuration.

BizTalk 2009 ODBC Adapter Receive Location - Port

Create a new receive location and select to use the ODBC adapter and click Address.

BizTalk 2009 ODBC Adapter Receive Location - Location Properties

You will now be shown the ODBC Community Adapter Transport properties window.  Select connection string and you will be shown the Choose data Source window.  If you have already created the Test Database source when generating a schema from ODBC this will be shown (if not go and take a look in my previous post to see how this is done).

BizTalk 2009 ODBC Adapter Receive Location - Transport properties
 

BizTalk 2009 ODBC Adapter Receive Location - Data Source

You will then need to choose the SQL command that will be run by the recieve port.  In this case I have deployed the Test Mapping schemas that I created previously and selected the Request schema.

BizTalk 2009 ODBC Adapter Receive Location - Request Schema

You should now have populated the appropriate properties for the ODBC Com Adapter.

BizTalk 2009 ODBC Adapter Receive Location - Updated Transport Properties

Finally set the standard receive location properties and your ODBC receive location is now ready.

Next: Creating a Send Port

Posted on Wednesday, June 9, 2010 2:25 PM BizTalk Administration and Troubleshooting , BizTalk Adapters | Back to top


Comments on this post: BizTalk 2009 - The Community ODBC Adapter: Receive Location

# re: BizTalk 2009 - The Community ODBC Adapter: Receive Location
Requesting Gravatar...
I am not able to select the assembly and the schema. I was able to connect using odbc. The error is " An error has occured connecting the BizTalk configuration system.
Left by murtaza on Dec 21, 2010 6:56 PM

# re: BizTalk 2009 - The Community ODBC Adapter: Receive Location
Requesting Gravatar...
I followed the steps above for the BizTalk 2010 Adapter. I running BizTalk 2010 on Window 7 64 bit. I Copied the assemblies to the "C:\Program Files (x86)\Microsoft BizTalk Server 2010\" folder, then installed into the GAC (4.0). I generated a schema through the Add Adapter Wizard, which works fine. When I deploy the schema to my BizTalk application, set up the receive port and location, and enable the port, I receive the following error in the event log:

The Messaging Engine failed to create the receive adapter "ODBC Cummunity Adapter".
InboundAssemblyPath: "NULL"
InboundTypeName: "Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCReceiveAdapter.ODBCReceiver, ODBCAdapterManagement, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL"
Exception Details: "Could not load type 'Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCReceiveAdapter.ODBCReceiver' from assembly 'ODBCAdapterManagement, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL'."

Left by Kerchal on Jun 08, 2011 3:33 PM

# re: BizTalk 2009 - The Community ODBC Adapter: Receive Location
Requesting Gravatar...
I had this same issue:
The Messaging Engine failed to create the receive adapter "ODBC Cummunity Adapter".
InboundAssemblyPath: "NULL"
InboundTypeName: "Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCReceiveAdapter.ODBCReceiver, ODBCAdapterManagement, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL"
Exception Details: "Could not load type 'Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCReceiveAdapter.ODBCReceiver' from assembly 'ODBCAdapterManagement, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL'."

I think the InboundTypeName and OutboundTypName may be misconfigured in the BizTalkMgmtDb database table
dbo.adm_Adapter - not sure why at the moment...

I updated them to the following:
InboundTypeName:
Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCReceiveAdapter.ODBCReceiver, ODBCReceiveAdapter, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL
and
OutboundTypeName:
Microsoft.BizTalk.Adapters.ODBC.RunTime.ODBCTransmitAdapter.ODBCTransmitter, ODBCTransmitAdapter, Version=1.2.0.0, Culture=neutral, PublicKeyToken=0ad1f077efbaab97, processorArchitecture=MSIL

(Note the assembly name change from ODBCAdapterManagement)
After restarting the host instance this worked for me testing against an MSAccess database.

Left by dawa on Jun 21, 2011 11:00 AM

Your comment:
 (will show your gravatar)


Copyright © Stuart Brierley | Powered by: GeeksWithBlogs.net