Re: Advice
From: Scott Woodgate \(MS\) (replyto_at_newsgroup)
Date: 10/30/04
- Next message: Scott Woodgate \(MS\): "Re: BizTalk 2004 or pure .Net components for request/reply via API:s?"
- Previous message: Paul Johansen: "FTP Receive Adapter in BTS Group"
- In reply to: Andrew: "Advice"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 30 Oct 2004 08:04:34 -0700
This depends on "what type of rules" if they are publish and subscribe rules
to determine source and destination as you describe below and you promote
the properties for the total set they will ever want in advance (which will
be the tricky thing to figure out; or maybe there is just a static set) then
you can provide a simple UI that sits on top of the explorerOM and
programmatically modify/create send/receive ports subscriptions on demand in
a manner you describe below.
If it were business logic rules I'd suggest the rules engine but its routing
rules.
"Andrew" <andrew@nospam.com> wrote in message
news:OCZYKjfvEHA.3276@TK2MSFTNGP15.phx.gbl...
> I have the requirement to route messages in BizTalk to known systems based
> on some field elements within that message. My client would like the
ability
> to easily change the routing without developer intervention. For example,
if
> I have System A and System B, a combination of field elements within the
> message will determine that's it's supposed to go to System A. My client
> wants the ability to change that rule so in future messages with the same
> field elements, it will go to System B. What is the easiest approach to
take
> in providing this functionality? Some of my thoughts are:
>
> 1. Just let them go into BizTalk and change the orchestration. Provide the
> client with deployment scripts to automate the deployment process. (This
> could get messy if they have lots of routing rules)
>
> 2. Store 'routing rules' within a table in SQL Server. BizTalk would call
a
> stored procedure, passing in the appropriate field elements that determine
> routing. The stored procedure would subsequently return the destination
> system. Using this alternative, we could create a simple interface for
them
> to change routing rules.
>
> 3. Any other ideas?
>
> Thank you in advance for your assistance,
> Andrew
>
>
- Next message: Scott Woodgate \(MS\): "Re: BizTalk 2004 or pure .Net components for request/reply via API:s?"
- Previous message: Paul Johansen: "FTP Receive Adapter in BTS Group"
- In reply to: Andrew: "Advice"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
