Forum Replies Created
-
AuthorPosts
-
Ok, if I got this right ..
1] Message has itinerary attached to it.
2] Biztalk ESB contains “x” number of components/orchestrations to handle every step in the itinerary
3] Each component does his job and only “routes” to next but not “executes” the next.
This routing would be as simple as removing the current step or marking the current as complete.
4] As each component does the work corresponding to only 1 step in the itinerary it doesn’t care what the next step is. It finishes its work and hands it back to the central Database
5] The next component simply retreives the message from the central database , executes the step as per the itinerary and lets go..
and so on ..You’re confusing things. I didn’t say that the components knew exactly what to execute. I meant the ESB dispatcher components know how to interpret the itinerary, look up a service and execute it; that’s what the ESB components are for. Of course that part is dynamic, and the esb components know how to handle all of that; it’s not something you have to do by hand for each itinerary.
As for orchestrations, those are not used in the way you thing. It is true that an itinerary can configure a service to run in an orchestration context, but it’s not like a regular biztalk orchestration… it’s an orchestration that needs to be coded in a specific way, registered a certain way with biztalk and the ESB toolkit and a bunch of other things. The ESB toolkit does come with 2 predefined orchestrations to execute routing and transformation services, but that’s it.
Ok,
If we really want to be loosely coupled one service/ESB component should not even know the other exists.
Im a little confused .. If 1 orchestration executes all the steps in the itinerary , then it would also need to know “how ” to execute all the steps.
So if the itinerary is altered for a message the same orchestration would need to understand the exact way to communicate with the newly introduced steps etc.
How is this dynamic if I need to add a new step to a few of the itineraries and also modify the corresponding orchestrations which are affected ?You can’t really disassociate the two things: You execute the *next* stage in the itinerary and then *advance* it to the next state. There’s really nothing fancy there. For example, the ESB dispatcher component in a receive pipeline will simply execute all stages in the itinerary until it reaches one that is not set to execute in the port’s receive handler and then simply let’s biztalk carry that message forward as usual. It doesn’t really need to do anything else other than update the itinerary state in the message context and any associated properties.
Thanks for the reply..I will be a bit a more specific …
[quote user="tomasr"]The way the ESB toolkit does is that the itinerary (and the state of execution of it) is attached to each message in a special context property. That’s how the various ESB components/pipelines/orchestrations know how to handle the message and what the next step in the itinerary is. If you change the itinerary definition, normally this will just be picked up by messages that arrive after that, not by running itineraries.
[/quote]
I understood the part about itinerary is attached to the message and the itinerary attached to a message cannot be altered mid way.
You just mentioned that the various ESB components, piplelines and orchestrations know how to handle the next stap based on the itinerary.
I think this is where my questions are …
1] If there is an orchestration A (for service A), orchestration B (for WCF service B), C (for service C) and D (Http post) etc
2] I create itinerary1 which says A–>B–>C
3] I create a new itinerary2 which says A–>D–>B–>CNow the orcehstrations A, B,C and D will be responsible for :
1] Just executing the corresponding service
OR
2] [Executing the corrersponding sercvice in the itinerary] + [routing to next step in the itinerary]Which of these 2 options is the responsibility ?
To what extent does one orchestration/ESB component corresponding to a service take the responsiblity of executing an itinerary ?
Lets assume Im not a Biztalk developer and Im not concerned with the exact technical detail of how the Biztal code runs..Im just looking for an overview of how this is done in Biztalk ? [:)]
How will Biztalk habdle the itinerary1 and itinerary2 dynamically ?I can simply put in other words as will 1 orchestration/pipleine/ESB component in Biztalk handle all the steps in the itinerary or will each component be responsible for only 1 step in the itinerary.. Seems from your reply its 1 orchestration which will doo all the steps in the itinerary…
Please correct me if Im wrong ?The way the ESB toolkit does is that the itinerary (and the state of execution of it) is attached to each message in a special context property. That’s how the various ESB components/pipelines/orchestrations know how to handle the message and what the next step in the itinerary is. If you change the itinerary definition, normally this will just be picked up by messages that arrive after that, not by running itineraries.
In your second example, however, you’re talking more about handling request/response, two-way scenarios, which are also supported by the ESB toolkit. In this case, you need to make sure that the two-way send ports use are using the right send/receive pipelines provided by the ESB toolkit, which use the ESB Itinerary Cache pipeline components so that when the response message is received, the itinerary state/definition left by the request message is attached to the response message so that it can continue to execute. That’s actually covered in the ESB toolkit docs, by the way.
Thanks for the reply!!
This may be more of “Itinerary/routing slip” design pattern type of a query ..just to understand the overall concept of Itinerary.
Iv’e understood the concept that the Itinerary pattern is used to decouple and allow the message to be routed across services by simply altering the items in the Itinerary.
So instead of going from A–>B–>C
I introduce another step and say it should go from A–>D–>B–>C
Now if this Itinerary pattern is to be succesfull ideally I should just modify the “Itinerary” and rest should be automatically handled.As explained above if the “services are set to execute in the same location” or in the dispatcher pipeline one after the other how does the Itinerary pattern work ?
If the code (either in the receive/send handler or the dispatcher pipeline) was set to execute A–>B–>C and If I introduced another step “D” ; will it handle this change ? will I have to go and modify this if I alter the Itinerary ?
Assuming “B” was a WCF (SOAP) type of a call and now “D” is an Http post how does the code know how to handle the call made after “A”If I have to go and alter the code related to “A” to make it understand that it has to go to D instead of B then whats the purpose of an Itinerary ?
Its like “hard coding” the logic into the service/container to allow it to route/call the next step in the chain…Thanks for your reply. It was running in standalone app. Anyway I have resolved this using the seachroot with Directory seacher.
Best regards,
Nandika
It really depends on where you’ve set the services to execute. Most of the time, several services are set to execute in the same location like the receive handler or send handler of a port, in which case the esb dispatcher pipeline component will execute all the services one after the other according to the itinerary scheduled. In those cases, routing isn’t really an issue.
When routing is needed because you’re switching locations (say, you’ve got one service set in the receive handler of the receive port, then move to an off-ramp or to a service in an orchestration), then standard BizTalk Pub/Sub handles it based on the message properties and the subscriptions that ESB on/off-ramps and special orchestrations have in place.
August 23, 2009 at 11:31 AM in reply to: Help needed to start biztalk EDI application development #23094Hi Ram,
BizTalk and EDI are two different subjects to learn and master, each with its own domain of difficulty and complexity.
I would suggest that you start with BizTalk, then, once you have a good basic knowledge of that, move on to EDI.
I suggest that you go to this website for BizTalk training:
http://www.biztalk-training.com/news.php
They have good tutorials on BizTalk 2006 and they charge a reasonable fee for online learning.
As for EDI knowledge, here are a few links that you can read through to gain more understanding, the first two are from MSDN dealing with EDI Interface Developer Tutorial and EDI Solution Architecture, and the last two are blogs dealing with the concepts of Party resolution and Role links:
http://msdn.microsoft.com/en-us/library/bb226541(BTS.10).aspx
http://msdn.microsoft.com/en-us/library/bb246106(BTS.10).aspx
http://blog.biztalk-info.com/archive/2006/10/25/BizTalk_Role_Links_explained.aspx
One piece of advice with regards to BizTalk training: over the course of your training, you should always try to apply the knowledge that you have gained, by doing coding in BizTalk (orchestrations, maps, schemas, port settings, pipelines, XLANGs, XPath, etc.), as I found out that was the best way of understanding how BizTalk works and its numerous intricacies, and retaining the knowledge.
Best of luck!
Daniel.
Ok, so I unpromoted the date element in question and now that data propagates just fine. Very interesting but still problematic as I think I need that field to be a property. >:(
August 22, 2009 at 10:49 AM in reply to: Message Type not available in Transform Destination drop down menu #23089Is everything part of the same project? Try importing your webservice reference into a separate project, marking everything there as public and then using a project reference to make them visible where you will be using them. This seems to be necessary with the WCF adapter in 2009 sometimes, so maybe it’s the same bug…
Can you please send me sample project for that. it’s relay help for me.
Thanks,
Oyash
August 21, 2009 at 8:47 PM in reply to: What the Limitations of BizTalk on Integrating Legacy System Like AS400 #23087Hi,
It would help others answer your questions if you could be more specific about what you are looking to achieve in trying to integrate AS/400 with BizTalk. The limitations that you are seeking are not officially documented and would only be encountered when trying to implement such an integration scenario.
Indeed. In the meantime, I can achieve the same with send/receive ports (a send port on which you can update subcriptions that sends to a place where it is picked up by a receive port bound to the orchestration, but I find that cumbersome).
-
AuthorPosts