Sending ebMS 3.0 UserMessage to multiple destinations (multicast pattern)
Hello everybody,
I am rather new to ebMS and ebXML, but I'm looking if it can be used to work out a project of us. One of the patterns we have to support is to have MessageProducers sending a message that needs to be routed by the MSH to one or more MessageReceivers (something like a multicast).
We want to avoid putting the work on the producers to send multiple messages with one Party, but instead want to have them sending one message with multiple PartyId elements in the eb:To. The XML schema allows for this, but if I look in the technical spec, I can see the following statement:
eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From/eb:PartyId
The REQUIRED PartyId element occurs one or more times. If it occurs multiple times, each instance MUST identify the same organization.
Does this mean we cannot have one-to-many message communication, using ebMS3.0?
Search
Recent Content
- TelCOMM – tool designed for B2B exchange of documents using AS4
3 years ago - Drummond Certifies AS4 and ebMS-based Software Applications in 2021’s 1st Quarter Interoperability Event
3 years ago - ISO Approves OASIS ebMS3 and AS4 as International Standards for Messaging
3 years ago - Use Python and Domibus for eDelivery Message Exchange
3 years ago - ebXML Messaging Protocol Binding for RegRep v1.0 approved as a Committee Specification
3 years ago - Collaboration Protocol Profile and Agreement v3.0 from ebCore TC approved as a Committee Specification
3 years ago
Subscribe
Submit vs Send
You are talking about the Submit() operation whereas the specification is focussed on the communication between MSHs. The Submit() operation is only defined in an abstract way, as it is dependent on product or middleware. Some product could perhaps provide a SubmitMulti() operation that allows the Producer to submit a single submitted user message that is to be sent to multiple destinations. But those submitted user messages would map to distinct user messages, all of which could have their own message identifier, would individually succeed or fail etc.