|
Home > Archive > BizTalk Server General > July 2005 > one message type = one receive location = one orchestration ?
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 |
one message type = one receive location = one orchestration ?
|
|
| Ravi Shankar 2005-06-09, 5:51 pm |
| Hi,
Sorry for posting these newbie questions in this group but the newbie UG is
not accessible over the web interface..
I have another design dilema. We have identified a single process that would
need to be invoked for different message types. The different message types
would be 45-50. So...
Can a single receive port handle multiple message types ? (I read some
previous posts stating that by disabling schema verification this is possible
but it is not a nice thing to do or I mis-understood ?)
The other option of creating one receive location per message format and
tying it down to a single orchestartion sound equally horrific. Creating a
sperate copy of the same orchestartion with a different name (deployment
binary) and attaching it to separate ports which handle specific message
sound very horrific..
I get the feeling I've missed a very basic step in my learning..
Thanks for your patience and understanding.
--
Ravi Shankar
| |
| Stephen W. Thomas 2005-06-09, 5:51 pm |
| Hello.
Yes, a single port and even a single receive location can handle multiple
message types.
Depending on the message type and mapping requirements you might have to
break them out.
Disabling schema verification is only required if each schema is not
deployed or if you have two messages deployed with the same message type
(namespace # root node name).
Do you need to map each message on the Receive Port? If so, as long as two
schemas do not have the same message type you should not have a problem.
Receive ports can support multiple maps. If you need to map two schema that
look the same to BizTalk, then those will have to be placed under different
ports.
If you need to receive different schemas into your Orchestration, you can
use untyped messages. You can get more info on that on my blog. Basically,
your receive messages as XmlDocuments.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"Ravi Shankar" wrote:
> Hi,
>
> Sorry for posting these newbie questions in this group but the newbie UG is
> not accessible over the web interface..
>
> I have another design dilema. We have identified a single process that would
> need to be invoked for different message types. The different message types
> would be 45-50. So...
>
> Can a single receive port handle multiple message types ? (I read some
> previous posts stating that by disabling schema verification this is possible
> but it is not a nice thing to do or I mis-understood ?)
>
> The other option of creating one receive location per message format and
> tying it down to a single orchestartion sound equally horrific. Creating a
> sperate copy of the same orchestartion with a different name (deployment
> binary) and attaching it to separate ports which handle specific message
> sound very horrific..
>
> I get the feeling I've missed a very basic step in my learning..
>
> Thanks for your patience and understanding.
> --
> Ravi Shankar
| |
| Ravi Shankar 2005-06-10, 7:47 am |
| Thank you Stephen for the quick response.
Messages conforming to a standard e.g. SWIFT would have the same namespace.
Unless and until the message type gets translated into an appropriate root
node like only if the SWIFT MT 100 message has the root node as MT100 there
would not be a problem ?
I shall also go through your blog.
"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> Yes, a single port and even a single receive location can handle multiple
> message types.
> Depending on the message type and mapping requirements you might have to
> break them out.
>
> Disabling schema verification is only required if each schema is not
> deployed or if you have two messages deployed with the same message type
> (namespace # root node name).
>
> Do you need to map each message on the Receive Port? If so, as long as two
> schemas do not have the same message type you should not have a problem.
> Receive ports can support multiple maps. If you need to map two schema that
> look the same to BizTalk, then those will have to be placed under different
> ports.
>
> If you need to receive different schemas into your Orchestration, you can
> use untyped messages. You can get more info on that on my blog. Basically,
> your receive messages as XmlDocuments.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "Ravi Shankar" wrote:
>
| |
| Stephen W. Thomas 2005-06-12, 2:47 am |
| Hello.
I have not worked with SWIFT so I do not know the schema structure.
As a rule of thumb, as long as none of your messages have the exact same
message type (i.e. Namespace and root node name) your life is much easier.
I know when working with Microsoft Great Plains and Siebel, they call all
the integration messages the exact same thing.. thus causing problems if you
want to use the same receive location to receive the messages and have to do
mapping on the receive port.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"Ravi Shankar" wrote:
[vbcol=seagreen]
> Thank you Stephen for the quick response.
>
> Messages conforming to a standard e.g. SWIFT would have the same namespace.
> Unless and until the message type gets translated into an appropriate root
> node like only if the SWIFT MT 100 message has the root node as MT100 there
> would not be a problem ?
>
> I shall also go through your blog.
>
> "Stephen W. Thomas" wrote:
>
| |
| Ravi Shankar 2005-06-13, 2:47 am |
| Thanks Stephen.
"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> I have not worked with SWIFT so I do not know the schema structure.
>
> As a rule of thumb, as long as none of your messages have the exact same
> message type (i.e. Namespace and root node name) your life is much easier.
>
> I know when working with Microsoft Great Plains and Siebel, they call all
> the integration messages the exact same thing.. thus causing problems if you
> want to use the same receive location to receive the messages and have to do
> mapping on the receive port.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "Ravi Shankar" wrote:
>
| |
| Sukesh Shetty 2005-07-30, 5:49 pm |
| How do I do the same thing for flat file schemas. For flat file schema at the
receive pipeline I need to give the receiving message schema name. Is there a
way to have a recevie location pickup mulitple flat file formats??
Thanks,
Sukesh.
"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> I have not worked with SWIFT so I do not know the schema structure.
>
> As a rule of thumb, as long as none of your messages have the exact same
> message type (i.e. Namespace and root node name) your life is much easier.
>
> I know when working with Microsoft Great Plains and Siebel, they call all
> the integration messages the exact same thing.. thus causing problems if you
> want to use the same receive location to receive the messages and have to do
> mapping on the receive port.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "Ravi Shankar" wrote:
>
|
|
|
|
|