Forum Replies Created
-
AuthorPosts
-
John,
Can you post an example of the input files and the schema?
Nick.
Hi Guhanath,
Before I dive into a BizTalk answer, I'd probably look at doing this using SSIS packages directly from SQL Server (SSIS are the new DTS) – this might be an easier option and would produce faster results.
If however you're intent on doing this through BizTalk, you'll need to get hold of the DB2 Adapter, available free of charge, which can be found here (it ships as part of the Microsoft BizTalk Adapters for Host Systems).
In terms of the solution, you have two options:
- If you plan on polling the DB2 for changes (and can determine what has changed when you poll DB2), you can use a messaging-only solution: setup a receive port/location using the DB2 adapter to poll once every x seconds/minutes/hours – records will be returned into the MsgBox. Setup a Send Port to subscribe to messages coming from the receive port and map from the DB2 message to a SQL Server Updategram message, squirting the message at your SQL Server instance using the out-of-the-box SQL Adapter. For this solution, you will need a schema representing the DB2 message and SQL Server message and a map between the two.
- If you need to receive a trigger message to kick-off the poll of DB2, you will need to run this in an orchestration: the orchestration will receive the trigger message and initiate a solicit-response call to DB2 (using the DB2 adapter), returning an Xml message representing the records to be inserted into SQL Server. A map can be applied in the orchestration converting the message from a DB2 record into a SQL Server updategram record and a Send Port will then be used to squirt the message at your SQL Server instance using the out-of-the-box SQL Adapter. For this solution, you will need a schema representing the DB2 message (request and response) and SQL Server message (request; response is not necessarily required) and a map between the DB2 response and SQL Server Request; the trigger message can be defined as an XmlDocument as you'll throw it away once received.
Note, that I've just read that the DB2 adapter will return a single message for each record returned – you'll need to check this as the orchestration becomes a little more complicated than that described above. Happy to elaborate if you need anymore advice.
Please bear in mind that this is a brief overview of the two possible solutions, however, the following links should help you with your solution:
- BizTalk Adapter for DB2
How to Create a BizTalk Application Using the DB2 Adapter- Using the SQL Adapter in BizTalk
Hope this helps,
Nick.
Have you made sure that the SQL Agent is running and that you have at least one (and preferably just one) instance of a host that is configured for tracking running?
This is one of the limitations of the built in POP3 adapter. I would think that you would need to write a custom pipeline component to filter. The TopXML adapter supports regular expressions on subject lines. We bought this adapter back in 2005 when supporting BizTalk 2004 so we have continued to use this adapter in BizTalk 2006.
solved by using application/octet-stream.
But wondering how to filter emails to only passthrough specific subject?
The XmlDocument message type can hold any type of message (XML, PDF, Word, etc). If you've got a series of XML messages that may be passed to the other orchestration, XmlDocument's probably the easiest way to go.
Yes, I agree that they could go into more details. "Complete EAI, B2B, and Business Process Management functionality" is definately subject to interpretation
That's too bad. I miss the old Partner Edition. One would think that Microsoft could show a comparison chart anyway, wouldn't you?
October 28, 2007 at 9:53 AM in reply to: What part in BizTalk is responsible for keeping information about all adapters’ properties? #18287Check out BizTalk Documenter – it will provide you with a lot of configuration info for all of your applications and gives you some data on your adapters installed. http://www.codeplex.com/BizTalkDocumenter
From http://www.microsoft.com/biztalk/howtobuy/faq.mspx
"BizTalk Server 2006 R2 Branch Edition (BR) is a specialty version of BizTalk Server designed for hub and spoke deployment scenarios. Branch Edition (as the spoke) is used in conjunction with Enterprise Edition (at the hub) to support the distributed intra-enterprise connectivity needed for RFID scenarios, host gateway connectivity, and hub and spoke deployments. "
This would definately rule out Branch edition for you.
Based on what you provided, I would thinkg that Standard edition would probably be your best bet:
http://www.microsoft.com/biztalk/howtobuy/default.mspx
Ok, but the ONLY thing i need from Biztalk is HWS and Rule Engine. Theese are not included then?
You can use a .net class library includs a methods can readthe dataset , and then you find what you want using pure C# code , and then send the response…
I looked into BizTalk 2008 when our development was discussing the migration to VS2008/SQL2008 and Windows Server 2008. From what I've read there are no discussions about a BizTalk 2008 being released any time soon.
Yes, R2 is available (for developer download as well on MSDN).
Don't bet on anything out in 2008. MAYBE a beta of something, but no full release of the next version.
-
AuthorPosts