šŸ”„šŸ”„ Donā€™t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

šŸ”
BS ISO 15000-1:2021

BS ISO 15000-1:2021

$215.11

Electronic business eXtensible Markup Language (ebXML) – Messaging service core specification

Published By Publication Date Number of Pages
BSI 2021 128
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. Weā€™re here to assist you 24/7.
Email:[email protected]

This document provides a communication-protocol neutral method for exchanging electronic business messages. It defines specific enveloping constructs supporting reliable, secure delivery of business information. Furthermore, this document defines a flexible enveloping technique, permitting messages to contain payloads of any format type.

It specifies each of the following:

  • Messaging model

  • Message pulling and partitioning

  • Processing modes

  • Message packaging

  • Error handling

  • Security module

  • Reliable messaging module

This document is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations) that exchange documents or data electronically using messaging.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Contents
9 Foreword
11 Introduction
13 1. Scope
2. Normative references
15 3. Terms and definitions
18 4. Relevant messaging concepts
4.1. Web services and their role in an eBusiness messaging framework
19 4.2. Caveats and assumptions
4.3. XML notation
4.4. Namespace prefixes
20 4.5. Example domains
5. Messaging model
5.1. Model components
5.1.1. Components of the model
21 5.1.2. Messaging roles
22 5.1.3. Abstract messaging operations
5.2. Message exchange patterns
5.2.1. Rationale
23 5.2.2. General definition
5.2.3. MEP bindings
25 5.2.4. Relationship to SOAP MEPs
5.2.5. The One-Way/Push MEP
26 5.2.6. The One-Way/Pull MEP
27 5.2.7. The Two-Way/Sync MEP
28 5.2.8. Other transport-channel-bound MEPs
29 6. Message pulling and partitioning
6.1. Objectives
6.2. Supporting message pulling
31 6.3. Combining pulling with security and reliability
32 6.4. Message partition channels
6.4.1. Concept and purpose
34 6.4.2. Some use cases
35 6.4.3. Definition and usage requirements
36 7. Processing modes
7.1. General
37 7.2. Messaging service processing model
38 7.3. Processing mode features
39 7.4. Default features for processing mode
40 8. Message packaging
8.1. Message envelope and message parts
8.1.1. MIME structure and SOAP profile
43 8.1.2. MIME and XML considerations
8.1.2.1. Additional MIME parameters
8.1.2.2. Reporting MIME errors
8.1.2.3. XML prolog
8.1.2.4. XML declaration
8.1.2.5. Encoding declaration
44 8.1.3. ebXML SOAP envelope extension
8.1.3.1. General
8.1.3.2. namespace pseudo attribute
8.1.3.3. xsi:schemaLocation attribute
45 8.1.3.4. SOAP header element
8.1.3.5. SOAP body element
8.1.3.6. ebXML SOAP extensions
8.1.4. ebMS header
46 8.1.5. Payload containers
47 8.2. The eb:Messaging container element
8.2.1. General
48 8.2.2. eb:Messaging element specification
49 8.2.3. eb:Messaging/eb:UserMessage
8.2.3.1. General
8.2.3.2. eb:Messaging/eb:UserMessage/eb:MessageInfo
50 8.2.3.3. eb:Messaging/eb:UserMessage/eb:PartyInfo
8.2.3.4. eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From
8.2.3.5. eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From/eb:PartyId
51 8.2.3.6. eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:To
8.2.3.7. eb:Messaging/eb:UserMessage/eb:CollaborationInfo
8.2.3.8. eb:Messaging/eb:UserMessage/eb:CollaborationInfo/eb:AgreementRef
52 8.2.3.9. eb:Messaging/eb:UserMessage/eb:CollaborationInfo/eb:Service
53 8.2.3.10. eb:Messaging/eb:UserMessage/eb:CollaborationInfo/eb:Action
8.2.3.11. eb:Messaging/eb:UserMessage/eb:CollaborationInfo/eb:ConversationId
8.2.3.12. eb:Messaging/eb:UserMessage/eb:MessageProperties
54 8.2.3.13. eb:Messaging/eb:UserMessage/eb:PayloadInfo
8.2.3.14. eb:Messaging/eb:UserMessage/eb:PayloadInfo/eb:PartInfo
55 8.2.4. eb:Messaging/eb:SignalMessage
8.2.4.1. General
56 8.2.4.2. eb:Messaging/eb:SignalMessage/eb:PullRequest
8.2.4.3. eb:Messaging/eb:SignalMessage/eb:Error
8.2.4.4. eb:Messaging/eb:SignalMessage/eb:Receipt
8.2.5. Message unit bundling
57 8.3. Examples of ebMS messages (informative)
8.3.1. General
8.3.2. UserMessage example
59 8.3.3. PullRequest message example
8.3.4. Error message example
60 8.3.5. Receipt message example
8.3.6. “Bundled” message example
62 9. Error handling
9.1. General
9.2. Packaging of ebMS errors
9.2.1. eb:Error element
9.2.2. eb:Error/@origin
63 9.2.3. eb:Error/@category
9.2.4. eb:Error/@errorCode
9.2.5. eb:Error/@severity
9.2.6. eb:Error/@refToMessageInError
9.2.7. eb:Error/@shortDescription
9.2.8. eb:Error/Description
9.2.9. eb:Error/ErrorDetail
9.3. ebMS Error message
64 9.4. Extensibility of the eb:Error element
9.4.1. Adding new ebMS errors
9.5. Generating ebMS errors
9.6. Error reporting
65 9.7. Standard ebMS errors
9.7.1. General
9.7.2. ebMS processing errors
66 9.7.3. Security processing errors
67 9.7.4. Reliable messaging errors
10. Security module
10.1. General
10.2. Security element
68 10.3. Signing messages
10.4. Signing SOAP with attachments messages
69 10.5. Encrypting messages
10.6. Encrypting SOAP with attachments messages
10.7. Signing and encrypting messages
10.8. Security token authentication
10.9. Security policy errors
70 10.10. Secured message examples
10.10.1. Digitally signed and encrypted ebXML message
72 10.10.2. Digitally signed and encrypted ebXML SOAP with attachments message
74 10.10.3. Digitally signed receipt signal message
75 10.11. Message authorization
77 10.12. Securing the PullRequest signal
10.12.1. Authentication
10.12.2. Authorization
10.12.3. Preventing replay attacks
10.13. Countermeasure technologies
10.13.1. Persistent digital signature
78 10.13.2. Persistent signed receipt
10.13.3. Non-persistent authentication
10.13.4. Non-persistent integrity
10.13.5. Persistent confidentiality
10.13.6. Non-persistent confidentiality
10.13.7. Persistent authorization
10.13.8. Non-persistent authorization
10.14. Security considerations
80 11. Reliable messaging module
11.1. The reliable messaging model
11.1.1. General
11.1.2. Message processing
11.1.3. The reliable messaging processor in the MSH
83 11.2. Reliable delivery of ebMS messages
11.2.1. General
11.2.2. Reliability contracts for the RMP
84 11.2.3. Reliability contracts for the MSH
85 11.2.4. Reliability for signal messages
11.2.5. Handling of delivery failures
86 11.3. Reliability of ebMS MEPs
11.3.1. General
87 11.3.2. Reliability of the One-Way/Push MEP
88 11.3.3. Reliability of the One-Way/Pull MEP
89 11.3.4. Reliability of the Two-Way/Sync MEP
90 11.3.5. Reliability of other transport-channel-bound MEPs
91 Annex A. (informative) The ebXML SOAP extension element schema
95 Annex B. (informative) Reliable messaging bindings
B.1. General
B.2. WS-Reliability binding
B.2.1. Operations and contracts binding
B.2.2. Complement to the reliability of the One-Way/Push MEP
96 B.2.3. Complement to the reliability of the One-Way/Pull MEP
97 B.2.4. Complement to the reliability of the Two-Way/Sync MEP
98 B.3. WS-ReliableMessaging binding
B.3.1. Operations and contracts binding
100 B.3.2. Complement to the reliability of the One-Way/Push MEP
B.3.3. Complement to the reliability of the One-Way/Pull MEP
101 B.3.4. Complement to the reliability of the Two-Way/Sync MEP
102 Annex C. (informative) SOAP format and bindings
C.1. General
C.2. Using SwA with SOAP-1.1
103 C.3. Using SwA with SOAP-1.2
105 C.4. SMTP binding
106 Annex D. (informative) Processing modes
D.1. Objectives and usage
107 D.2. Model for processing modes
D.2.1. General
108 D.2.2. Notation
109 D.3. Processing mode parameters
D.3.1. General
D.3.2. General P-Mode parameters
110 D.3.3. PMode[1].Protocol
D.3.4. PMode[1].BusinessInfo
111 D.3.5. PMode[1].ErrorHandling
112 D.3.6. PMode[1].Reliability
113 D.3.7. PMode[1].Security
115 Annex E. (informative) P-Mode values and ebMS MEP bindings
E.1. General
E.2. P-Mode Values and the One-Way/Push MEP
116 E.3. P-Mode Values and the One-Way/Pull MEP
E.4. P-Mode Values and the Two-Way/Sync MEP
118 Annex F. (informative) Compatibility mapping to ebMS 2.0
F.1. Objectives and approach
F.2. Compatibility mapping rules
F.2.1. General
119 F.2.2. (CM1) Header mapping rules
F.2.2.1. General
F.2.2.2. Rule CM1-a: Mapping general message information
F.2.2.3. Rule CM1-b: Mapping party information
F.2.2.4. Rule CM1-c: Mapping collaboration information
F.2.2.5. Rule CM1-d: Mapping agreement reference
120 F.2.3. Rule CM2-a: mapping attachments
F.2.4. (CM3) Reliability mapping rules
F.2.4.1. General
F.2.4.2. Rule CM3-a: acknowledgments
F.2.4.3. Rule CM3-b: reliability contracts
121 F.2.4.4. Rule CM3-c: duplicate elimination
F.2.4.5. Rule CM3-d: Use of sequences and sequence numbers
F.2.4.6. Rule CM3-e: message ordering
F.2.4.7. Rule CM3-f: expiration timeout
F.2.5. (CM4) MEP mapping rules
F.2.5.1. General
122 F.2.5.2. Rule CM4-a: One-Way/Push with no signals
F.2.5.3. Rule CM4-b: One-Way/Push with signals
F.2.5.4. Rule CM4-c: Two-Way/Sync with no signals
F.2.5.5. Rule CM4-d: Two-Way/Sync with signals
F.2.5.6. Rule CM4-e: Two-Way/Push-and-Push
123 F.2.6. (CM5) Signal mapping rules
F.2.6.1. Rule CM5-a: Error metadata mapping
F.2.6.2. Rule CM5-b: Error value mapping
124 F.2.6.3. Rule CM5-c: ping and pong services
125 F.2.7. (CM6) Processing mode mapping rules
126 Annex G. (informative) Conformance
127 Bibliography

Related products

BS ISO 15000-1:2021
$215.11