Archive for the ‘ebXML’ Tag

The Global Justice Reference Architecture (JRA) ebXML Messaging Service Interaction Profile Version 1.0

The purpose of this document is to establish a SERVICE INTERACTION PROFILE (SIP) based on the ebXML family of technology standards.

A Service Interaction Profile is a concept identified in the Global Justice Reference Architecture ([JRA2]). This concept defines an approach to meeting the basic requirements necessary for interaction between SERVICE CONSUMERS and SERVICES. The approach utilizes a cohesive or natural grouping of technologies, standards, or techniques in meeting those basic interaction requirements. A profile establishes a basis for interoperability between service consumer systems and services that agree to utilize that profile for interaction. A Service Interaction Profile guides the definition of SERVICE INTERFACES.

In an SOA environment, every service interface shared between two or more information systems should conform to exactly one Service Interaction Profile. Service consumers who interact with an interface should likewise conform to that interface’s profile. The profile discussed in this document is based on the ebXML family of technology standards, defined as follows:

  • OASIS ebXML Messaging Services, Version 3.0: Part 1, Core Features, 2007 [ebMS3]
  • OASIS ebXML ―Conformance Profiles Gateway RX V3 or RX V2/3 for e-Business and e-Government applications [ebMS3-PROFILES]
  • OASIS ebXML Business Process Specification Schema v2.0.4 [ebBP]
  • OASIS ebXML Collaboration-Protocol Profile and Agreement Specification Version 2.0 [ebCPPA v2]
  • The Web Services Interoperability Organization (WS-I) Basic Profile, Version 1.1, dated April 10, 2006 (noted in this document as [WS-I BP]), ebXML Messaging Services v3 is conformant with Section 3 MESSAGES and Section 6 SECURITY and all standards that those sections reference. Section 4 of WS-I Basic Profile does NOT APPLY to ebXML. ebXML does not specify WSDL for service descriptions and service bindings.
  • The WS-I Attachments Profile ([WS-I AP]), Version 1.0, and all standards that it references
  • The WS-I Basic Security Profile Version 1.0 (dated March 30, 2007, 37 noted in this document as [WS-I BSP]), all current Token Profiles, and all standards that they reference.

For more information please visit:


OASIS solicits feedback on proposed ebXML Core charter

OASIS members are asked to review and comment on a draft charter to establish the OASIS ebXML Core (ebCore) Technical Committee. The group plans to serve as the maintenance body for ebXML specifications that are completed or transitioned to the TC. It will manage clarifications, modifications, and enhancements for the specifications. The ebCore TC may also produce new conformance profiles and adjunct documents complementing existing specifications. It will explore synergies with UN/CEFACT, WS-* specifications and SOA best practices.Proposers include representatives of OASIS Sponsor members, Axway Software, Boeing, and Fujitsu, and Contributor members, British Telecommunications and Sonnenglanz Consulting. The comment period for the charter closes 25 Feb 2008.

Read the complete announcement from OASIS.

Process Component Models: The Next Generation In Workflow ?

Tom Baeyens, founder of JBoss jBPM gives his view of the state of the BPM / workflow market and introduces a new type of workflow technology called process component models.

This article arguments that the gap between the analysis and the implementation of business processes is far bigger then the marketing of today’s workflow tools might suggest. Also it will propose a much more realistic way of dealing with this situation. The current standards and initiatives will be explained with enough depth so that you can see how they relate to the movements and why.

At the end, a new type of workflow technology is introduced called process component model. This type of framework can handle multiple process languages and it can support process languages that better support the transition from analysis process diagrams to executable processes.

This article is orgnised as follows:

– What is BPEL
     – Thoughts and comments on BPEL
     – BPEL extensions
     – What is BPMN
     – Analysis versus execution
     – Process development process
     – Modelling details
     – Mappings and mismatches
– Other BPM technologies
     – XPDL
     – BPDM
     – jPDL
– Choreography
– Process component models
– Implications of this new approach

Read full article …

2007: A Marquee Year for ebXML

The adoption and use of ebXML has finished 2007 stronger and deeper with significant new product and project wins achieved.  The plans for 2008 already hold out expansion on what 2007 has accomplished and particularly in Asia an ambitious programme with several governments contributing to projects taking advantage of what ebXML V3 offers to implement lower cost extended cross-boundary communications solutions.   Europe too is seeing expanding use through adoption in EU funded projects.  Meanwhile the US is broadening use more especially in the government healthcare sector. The adoption by HL7 of the new ebXML V3 messaging will be key in 2008 and especially when combined with SOA techniques and technology needs.

New Tools and Capabilities

Three standout milestones in new software were delivered in 2007.  First Oracle shipped ebXML messaging and CPA support in their Oracle A/S suite and used this for a key project in the agricultural chemical industry in the USA (see Helena Chemicals project report in resources below).

Next IBM provided ebXML messaging and CPA support in their Web Sphere 6.1 product release, primarily to support customers in the medical services industry interfacing with the DHS/CDC PHIN nationwide health reporting system in the USA.

Then Hong Kong University CECID (Center for E-Commerce Infrastructure Development) shipped their new H2O “Hermes V2” ebXML messaging system as an entirely new replacement for their original Hermes system.  As an open source project this not only achieved huge momentum being deployed in over 40 countries worldwide but more importantly it rapidly evolved into a very stable and capable solution with the code base working in a wide variety of environments with solid support for core ebXML functionality.

The Supporting Cast

Added to this was the release of two more very capable and stable messaging open source solutions – the NexusE2E used originally in the chemical industry and the OrionSMG (Secure Messaging Gateway) from healthcare.

Further more the ebXML Registry V3.0 was formally completed and Webswell Inc. combined this with Hermes H2O to make provide a whole B2B-enabled orchestration system for SOA deployments.

Then OASIS approved the Content Assembly Mechanism (CAM) standard and this allows development of content templates to simplify transaction exchange between ebXML systems using the jCAM open source rule engine.  The OrionSMG comes with this capability built-in.  CAM delivers on five years of work that started in ebXML and UN/CEFACT as the BRIM requirements for message exchange definitions in business processes.

Standout Projects in 2007

Of particular note in 2007 was the continued expansion of use of ebXML in the UK NHS “Connecting for Health” system.  This system is the world�s largest e-Business system and the underpinning for this is ebXML messaging.  Electronic transmission of prescriptions message exchange volume reached five hundred messages per second in 2007 and is projected to reach up to seven hundred.   That is over 2,000,000 messages an hour.

Another area in healthcare is the US IHE/XDS secure document exchange project where ebXML Registry is the foundation technology.  This project involves over twenty key providers in the healthcare services industry being able to exchange patient documents between their product offerings and is being coordinated by NIST.

In Asia Axway have implemented a large scale deployment of ebXML messaging for the exchange of customs documents between Thailand and the Philippines;  via service providers, this link connects many thousands of exporting and importing companies.

Better Standards Coordination for 2008

OASIS is launching the new OASIS CORE technical work that will provide better coordination and support for ebXML technology standards in 2008.  Also UN/CEFACT is completing initiatives defining the requirements for context driven support for core component based transaction exchanges and design.  This will make semantically more capable XML transactions possible using technologies such as OASIS CAM templates and W3C schema.

Leading Forward in 2008

Fujitsu and Axway are both leading into 2008 with new ebXML V3 service offerings.  These will be particularly important to their projects in enabling SOA integration between legacy systems, B2B systems and web service WSDL exchanges.  The ebXML V3 specifications are addressing the extended and expanded interchange requirements that today’s distributed national and international level systems require.

The available capabilities in Oracle and IBM solution suites combined with open source lightweight ebXML message solutions can now provide plug-and-play opportunities between existing ERP systems and extended networks of suppliers systems.

The opportunity for ebXML use in 2008 at all levels will continue to accelerate delivery of solutions based around the proven open standards that ebXML provides.

By David Webber

IBM Websphere adds native support for ebXML Messaging and CPA

The latest release of IBM Websphere Partner Gateway has added native support for ebXML Messaging and CPA. The following excerpt is from What’s new in V6.1 – Detail: ebXML Messaging Service (ebMS) 2.0 used in Canada, Europe, and Asia, and in healthcare and auto industries, and support for the ebMS 2.0 Basic Profile
ebMS 2.0 XML Encryption Profile, designed to test message-based encryption. The technical details of this profile are based on requirements and methods originally defined by the CDC (Centers for Disease Control and Prevention), which uses ebMS in its Public Health Information Network applications
ebMS 2.0 Automotive Retail Profile, based upon requirements and recommendations from the STAR consortium (Standards for Technology in Automotive Retail), which includes testing of gzip-based compression
ebXML Collaboration Protocol Profile and Agreement (CPPA), which supports the import of CPPAs to automate the exchange and implementation of structured trading partner agreements

ebMS 3.0 and support for SOA

OASIS, the international open standards consortium, announced October 16th that its members have approved ebXML Messaging Services (ebMS) version 3.0 as an OASIS Standard.

The V3.0 specification provides a raft of new features that enable extended B2B interchanges and support for SOA message transport layer services.

ebMS V3.0 is designed to be used either with or without any of the other ebXML standards.

V3.0 now includes capability to use WS-Security, WS-Reliability, and the WS-ReliableMessaging OASIS Standards with ebMS. It can also be used with business process technology including OASIS ebXML BPSS V2.0.4 and OASIS BPEL systems.

Several industry domains have declared their support for the new ebMS V3.0 including AIAG automotive group, Fujitsu and the HL7 healthcare standards community.

“This new version of ebMS will address a broader array of users including SMEs with limited connectivity and little IT management resources. The adoption of Web services standards for security and reliability will facilitate implementations over existing platforms. We believe ebMS 3.0 will become an effective and versatile B2B complement to enterprise systems and SOA deployments,” said Yasushi Ishida, Exective Architect of Software Unit, Fujitsu Limited.

For more information see