Many people who have implemented the ESB 2.0 BizTalk 2009
solution would have come to notice that there is a need where the endpoint
takes up a request to a synchronous system, and the system reverts back with a
response. There is a scenario wherein the response is required to be routed
back not to the initiator but other different endpoints according to the
complicated rules and processes.
This may not be a big thing for the reason that the BizTalk
can deal with such types of designs without any difficulty by means of the
static send ports with special filter expressions, simple orchestrations and
also those orchestrations with the Microsoft dynamics AX send ports. Complex
rules, logic and processes can be employed within the custom components, or the
Business Rules Engine (BRE) inside the pipeline components or the
orchestrations.
The means for building the flow process is what is called
for that first accepts the message initiated by the initiator, and after that,
taking note of the rules, dynamically settles on the 2 way service, takes back
the response. In the next step, based on the set of rules, it dynamically
routes back the response from an endpoint that is different from the initiator.
These capabilities are the Itineraries model of ESB. The BizTalk messaging BRE applies the complex logic and rules. The ESB
Resolvers are there for breaking such logic and the address of the endpoint
addresses and the final endpoint to transmit the responses to. By modeling an
itinerary of the ESB 2.0 of BizTalk 2009 server and incorporating the Itinerary
designer which will accept the message from the initiator and then route back
request to a 2-way Synchronous Endpoint, which then obstructs and finally sends
the Response to an endpoint other than the initiator depending on a Business
rule.
You may also like:
No comments:
Post a Comment