The OASIS ebXML Messaging Services TC has approved OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features, 19 May 2011, as a Committee Specification 01.
Archive
OASIS ebMS Version 3.0: Part 2, Advanced Features is an OASIS Committee Specification
News: Submitted by Pim on Sat, 2011-06-11 09:17.
ebXML Message Service Adapter enhances medical data transfer at Helse Vest, Norway
Resource: Submitted by Pim on Wed, 2011-06-01 15:27.
According to a press release by Covast, the Covast ebXML Message Service Adapter for Microsoft BizTalk Server has been adopted by Helse Vest IKT AS, the ICT management center for healthcare institutions in western Norway. The Norwegian healthcare sector adopted ebXML as the communication standard of choice. With the Covast ebXML Message Service Adapter, Helse Vest can exchange ebXML messages from within BizTalk Server. The whole working experience has also been improved by a new user-friendly graphic interface together with a CPA/CPP editing functionality.
ebXML and NBN Gateway Services: bas2eServices
Service: Submitted by arthur on Sat, 2011-05-28 05:30. Last updated on Mon, 2017-08-28 00:35.
NBN Gateway Overview
The Base2Services NBN Gateway is an enterprise grade scalable solution that meets all specification requirement under ebMS 2.0, providing trading partner management, non-repudiation, secured, signed, encrypted, and guaranteed delivery.
Jentrata
Product: Submitted by arthur on Sat, 2011-05-28 05:26.
Jentrata is an Open Source B2B Gateway that uses the Hermes code as a baseline. Jentrata has taken the Hermes Gateway, extended it and provided enhancements to it that improve its performance, configurability and maintainability.
Key amongst these improvements is the operational stability, and the provision for Jentrata to integrate directly with an ESB or other messaging backbone.
Question on handling multiple CPA's
Forum topic: Submitted by reema.kakodker on Tue, 2011-05-24 08:26.
Hello,
I would like to know if multiple CPA's can be handled between the same 2 partners. For example, I have created partner A and B using details provided in CPA1 with CPAID1, would it be correct if I receive a CPA2 with CPAID2 for the same partners A and B? How is this to be handled then? Should it over-write existing configuration for partners A and B or add on to the existing configuration?
Also what would be then the CPAID present in the EBMS message header for any Ebxml document being sent out?
I would like to know if multiple CPA's can be handled between the same 2 partners. For example, I have created partner A and B using details provided in CPA1 with CPAID1, would it be correct if I receive a CPA2 with CPAID2 for the same partners A and B? How is this to be handled then? Should it over-write existing configuration for partners A and B or add on to the existing configuration?
Also what would be then the CPAID present in the EBMS message header for any Ebxml document being sent out?
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
Navigation
Currently online: 2 guests and 0 users:
