|
Home > Archive > BizTalk Server Framework > January 2005 > receive location name
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
receive location name
|
|
| eXavier 2005-01-18, 5:50 pm |
| Is it possible to get receive location name in pipeline ? It seems that it
is not in message context....
Can I get the receive location name from within custom adpater code ? If
yes, how? Then I could set it to message context at least in my custom
adapters.
I have special component in receive pipeline handling messages specifically
based on receive channel (e.g. specific per queue in MQ). I have a single
receive port for given MQ with several locations - each receiving data from
its dedicated queue. There must be different (per queue) rules applied on
received data. I can get InboundTransportLocation, which is in fact
location's URI. Because rules application has to be configurable, currently
I need to specify whole URI into config file, but if e.g. MQ port number
(which is part of URI) changed, also the configuration would have to change.
It is not very flexible, it would be much better to have possibly invariant
identifier of location, e.g. location's name.
Thanks,
eXavier
| |
| Stephen W. Thomas 2005-01-18, 8:50 pm |
| Hello.
Have you look at the BTS. InboundTransportLocation and
BTS.InboundTransportType?
They should be available in the receive pipeline.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"eXavier" wrote:
> Is it possible to get receive location name in pipeline ? It seems that it
> is not in message context....
> Can I get the receive location name from within custom adpater code ? If
> yes, how? Then I could set it to message context at least in my custom
> adapters.
>
> I have special component in receive pipeline handling messages specifically
> based on receive channel (e.g. specific per queue in MQ). I have a single
> receive port for given MQ with several locations - each receiving data from
> its dedicated queue. There must be different (per queue) rules applied on
> received data. I can get InboundTransportLocation, which is in fact
> location's URI. Because rules application has to be configurable, currently
> I need to specify whole URI into config file, but if e.g. MQ port number
> (which is part of URI) changed, also the configuration would have to change.
> It is not very flexible, it would be much better to have possibly invariant
> identifier of location, e.g. location's name.
>
> Thanks,
> eXavier
>
>
>
| |
| eXavier 2005-01-24, 5:50 pm |
| This is what I wrote - InboundTransportLocation contains location's URI (not
location's name). URI is too dependent on current net configuration, it can
change easily (e.g. port or IP address). I'd rather use some alias, like
Customer1Invoices. Then it would be possible to define specific dissambling
rules per customer in application configuration and if I change location's
URI (e.g. from testing data source to productive) I could not change the
configuration.
eXavier
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:94EEB6B0-05B2-4083-A085-8460B900B646@microsoft.com...[vbcol=seagreen]
> Hello.
>
> Have you look at the BTS. InboundTransportLocation and
> BTS.InboundTransportType?
>
> They should be available in the receive pipeline.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "eXavier" wrote:
>
it[vbcol=seagreen]
specifically[vbcol=seagreen]
single[vbcol=seagreen]
from[vbcol=seagreen]
on[vbcol=seagreen]
currently[vbcol=seagreen]
change.[vbcol=seagreen]
invariant[vbcol=seagreen]
| |
| Stephen W. Thomas 2005-01-24, 8:47 pm |
| Hello.
If you want to be more focused on a per customer driven process, maybe
defining them as parties would help. This way, you can check the party
inside the pipeline? Or, possibly make is as simple as a different receive
port for each customer and then check ReceivePort name?
Just some other idea to think about if you have not already.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"eXavier" wrote:
> This is what I wrote - InboundTransportLocation contains location's URI (not
> location's name). URI is too dependent on current net configuration, it can
> change easily (e.g. port or IP address). I'd rather use some alias, like
> Customer1Invoices. Then it would be possible to define specific dissambling
> rules per customer in application configuration and if I change location's
> URI (e.g. from testing data source to productive) I could not change the
> configuration.
>
> eXavier
>
>
> "Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
> message news:94EEB6B0-05B2-4083-A085-8460B900B646@microsoft.com...
> it
> specifically
> single
> from
> on
> currently
> change.
> invariant
>
>
>
|
|
|
|
|