Hi,
In the
CPA there is a defaultMSHchannelID for sending MSH level messages.
Yes, on the PartyInfo element. This means it has scope over all
the
CollaborationRole elements and is the same throughout the CPA for each side
CollaborationRole elements and is the same throughout the CPA for each side
Since the sender channel does not have the
endPoints, how can I
identify the endpoint of the trading partner so that the MSH level message can
be sent to the right place?
Well, assuming that
syncReplyMode values are not involved (asynchronous for everything), then
if a response and MSH
acks (for example) go different
places, both sides will know where to send their acks, because each
will look at
the attribute on the other sides's
PartyInfo and use the URL found in that delivery channel... Both sender
and
receiver will have PartyInfo
elements, so look under the defaultMSHchannelId attibutes, chase down to
Transport/Endpoint
and you are
done.
The story can get more complex if
specific packaging modes and synch packaging are involved. But I hope that
helps
us get
started.
Do the transport protocol,
version and access authentication have to be the same between transport sender
and receiver in a bi-direction
transport?
Not required. The Request can go out HTTP, and the
Response can come back
SMTP!
Same
regarding transport security? Is the bi-directional delivery channel established
only for synchronous message exchange?
For synch, only one endpoint is required (if synchReplyMode
is signalsAndResponse) For split modes some
parts
come back synch, and others asynch. Gets a little
complicated but that is what people said they
wanted!
Thanks in advance for your
help.
Xiaoming Ding
RAD
404 E. Huntington Drive
Monrovia, CA 91016
ph: (626)471-6000 *6421
xding@SeeBeyond.com