- This topic has 4 replies, 1 voice, and was last updated 9 years, 6 months ago by
.
-
Posts
-
-
I am writing an application in BTS2006 that has around 10 stored procedure calls, each returning differently formatted data. Rather than creating 10 ports and all the related binding, I am looking for a solution that would be a single sql adapter that I could set the prerequisite rootnames etc. At this point they would all be using the same database. Has anyone seen an example of this or a commercial adapter that would handle this?
Thanks,
Doug
-
I don’t really know of anything.
But could you wrap all of your calls into a single SP and then call that using the SQL Adapter?
Just a thought.
-
Now that is an interesting idea, the adapter only determines the response root and ns, so it might handle different content structure. However, the generated port linkage in the orchestration requires a defined message. Maybe you can assign multiple sql ports to the same adapter or visa vesa. I still get confused which is the port and which is the adapter. Otherwise you would have to use an <any> element and map it back to specific results. Several procedural questions in that but I may give it a try.
It just occurred to me that if you used that same namespace and root element name you may be able to link all 'logical' ports to the same 'physical' port. This may be an easier solution.
Right now I have built an orchestration that calls a .net class that mimics the sql adapter. It does handle errors and retries, but I am sure it is missing aspects of an adapter I have not discovered.
Thanks, Doug
-
"It just occurred to me that if you used that same namespace and root element name you may be able to link all 'logical' ports to the same 'physical' port. This may be an easier solution." if you run like this you will get Runtime XLANG issue, Schema Compatabulity.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.