|
Home > Archive > BizTalk Server General > February 2004 > Preprocessor sample code for MQSeries?
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 |
Preprocessor sample code for MQSeries?
|
|
|
| I am trying to implement a process that will receive two positional
flat files of different format on the same queue (MQSeries), the
problem is that there is no common header or source tag identifier I
can use to self-route the documents. So I am looking to use a
preprocessor (VB.Net) in the receive function. Basically the
preprocess will add a common header for these two flat files so I can
specify a source tag identifier. Does anyone have code sample of
preprocessor for MQSeries receive function? The sample code in the SDK
is for the file receive function. Or maybe there is a better way to
handle this? Any help is greatly appreciated.
Thanks,
Bin
| |
| Jan Eliasen 2004-02-08, 8:38 am |
| On 21 Jan 2004 08:41:52 -0800, bfxue@comcast.net (Bin) wrote:
>I am trying to implement a process that will receive two positional
>flat files of different format on the same queue (MQSeries), the
>problem is that there is no common header or source tag identifier I
>can use to self-route the documents. So I am looking to use a
>preprocessor (VB.Net) in the receive function. Basically the
>preprocess will add a common header for these two flat files so I can
>specify a source tag identifier. Does anyone have code sample of
>preprocessor for MQSeries receive function? The sample code in the SDK
>is for the file receive function. Or maybe there is a better way to
>handle this? Any help is greatly appreciated.
Forgive me, if I am wrong here, but to me it sounds like to have mixed
up some concepts.
The source tag identifier is used on a per record-basis to identify
that particular record. It is not used to identify an organization
that can be used to route the document.
Do you really need to route the document? If yes, then you have two
options;
1. Have the sender of the document add the necessary fields to let you
route the document
2. Whatever logic you want your prprocessor to use, try implementing
it in pure BizTalk instead. Your preprocessor would have to add fields
based on what it reads in the document, right? Maybe the "Filter" on
the channels could do it for you? Or perhaps the identifiers on a
organization can do what you want?
Anyway, to best solve this, we'd need more knowledge of your setup,
such as;
1. How many different organizations do you deal with?
2. How would your preprocessor know how to route the document?
3. Do you really need to route the documents? Often it isn't
necessary.
--
Jan Eliasen, representing himself and not the company he works for.
MCP in Microsoft BizTalk Server
| |
|
| Jan Eliasen <spam@eliasen.dk> wrote in message news:<j7vu00de6mmvm93ss0b7ncfnghtfso59tl@4ax.com>...
> On 21 Jan 2004 08:41:52 -0800, bfxue@comcast.net (Bin) wrote:
>
> Forgive me, if I am wrong here, but to me it sounds like to have mixed
> up some concepts.
>
> The source tag identifier is used on a per record-basis to identify
> that particular record. It is not used to identify an organization
> that can be used to route the document.
>
> Do you really need to route the document? If yes, then you have two
> options;
>
> 1. Have the sender of the document add the necessary fields to let you
> route the document
>
> 2. Whatever logic you want your prprocessor to use, try implementing
> it in pure BizTalk instead. Your preprocessor would have to add fields
> based on what it reads in the document, right? Maybe the "Filter" on
> the channels could do it for you? Or perhaps the identifiers on a
> organization can do what you want?
>
> Anyway, to best solve this, we'd need more knowledge of your setup,
> such as;
>
> 1. How many different organizations do you deal with?
> 2. How would your preprocessor know how to route the document?
> 3. Do you really need to route the documents? Often it isn't
> necessary.
Thanks Jan. I found a way to resolve the issue with specifying a
dictionary item then use the filter and qualifier in the port/channel.
|
|
|
|
|