455. An Enterprise Messaging System (EMS) is a set of published Enterprise-wide standards that allows sending of semantically precise messages between computer systems. EMS systems promote loosely coupled architectures that allow changes in the formats of messages to have minimum impact on message subscribers. EMS systems are facilitated by the use of XML messaging, SOAP and Web services.

456. An Enterprise Service Bus (ESB) generally provides an abstraction layer on top of an implementation of an enterprise messaging system, which allows integration architects to exploit the value of messaging without writing code. Contrary to the more classical enterprise application integration (EAI) approach of a monolithic stack in a hub and spoke architecture, the foundation of an enterprise service bus is built of base functions broken up into their constituent parts, with distributed deployment where needed, working in harmony as necessary.

457. The following figure shows a layer model for the "Enterprise Messaging System (EMS) / Enterprise Service Bus (ESB)" based on the chapter: "Web Service Fundamentals".

458. Based on the Standards (signed in an ESB / EMS Profile) every Client and Server can be integrated into the ESB system.

459. WS-I Basic Profilee

460. The WS-I Basic Profile V1.0 specifies a set of usage scenarios and Web services standards that can be used to integrate systems. It focuses on the core foundation technologies upon which Web services are based. Basic Profile V1.0 was approved unanimously on July 22, 2003, by the WS-I board of directors and members.

461. The WS-I Basic Profile V1.0 – Profile Specification consists of the following non-proprietary Web services related specifications:

462. UPDATE: A combined claim of conformance to the WS-I Basic Profile 1.1 and the Simple SOAP Binding Profile 1.0 is roughly equivalent to a claim of conformance to the WS-I Basic Profile 1.0 plus published errata.

463. Additional there are many successful implementations of the basic Web services standards, particularly SOAP and WSDL but many aspects of service interaction and integration are not directly supported by those basic standards, such as security, transactional, delivery assurance, and process modelling – for example WS-Security, WS-Trust, WS-Privacy, and WS-Policy. It also accommodated existing security technologies such as Kerberos, XML Digital Signatures, and XML Encryption.

464. Because of this an "ESB / EMS Profile" proposal is defined on the next page.

465. ESB / EMS Profile proposal:

466. A proposal for an ESB / EMS Profile could be based on the WS-I profiles:

467. With the following parts of the WS-I profiles:

468. And with the following additional parts included in the ADaP-34 NISP-Vol2-v2 Draft, but not in the WS-I profiles:

469. And with the following additional parts (not in the WS-I profiles and not in the ADaP-34 NISP-Vol2-v2 Draft):