[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-dev] Is this an MSH?
Hi,
I am not clear about what an MSH is. The
Message Service Spec doc
lists down the functions provided by the MSH,
namely, header processing,
header parsing, message packaging, transport
binding, etc. Supposing
I have a front-end that envelopes/de-envelopes a
message in an ebXML
Message Package and
connects to a message provider that does the actual
routing to the receiving party's MSH; is my front-end considered an MSH
node?
And supposing the recipient party connects and
retrieves the ebXML-packaged
messages from the same message provider and uses
another instance of
the same front-end app; how many MSH nodes are
there?
Is it 1?
Party A ----------> shared MSH of both
parties ----------> Party B
Is it 2?
Party A ----------> MSH of Party A / MSH of
Party B----------> Party B
Is it 4?
Party A / MSH at client side ----------> MSH of
Party A at server side / MSH of Party B at server side ----------> MSH at
client side / Party B
Is it 3?
Party A / MSH at client side ----------> shared
MSH of both parties ----------> MSH at client side / Party B
Tnx for any help.
Regards,
art sombrito
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC