Deployment Profile Template
v1.1
For OASIS ebXML Message Service 2.0 Standard
Public Review Draft 01, 04
December 2006
Artifact identifier:
ebXML_DPT-v1.1-ebMS2-template-pr-01
Location:
http://www.oasis-open.org/committees/documents.php?wg_abbrev=ebxml-iic
Artifact Type:
template
Technical Committee:
OASIS ebXML Implementation, Interoperability and Conformance (IIC) TC
Chair:
Jacques Durand, Fujitsu <jdurand@us.fujitsu.com>
Editors:
Pete Wenzel, SeeBeyond <pete@seebeyond.com>
Jacques Durand, Fujitsu <jdurand@us.fujitsu.com>
Contributors:
Sacha Schlegel, CycloneCommerce <sschlegel@cyclonecommerce.com>
Pim van der Eijk, OASIS
Monica Martin, Sun Microsystems <Monica.Martin@sun.com>
SHIMAMURA Masayoshi, Fujitsu Limited <shima.masa@jp.fujitsu.com>
Thomas Bikeev, EAN International <bikeev@ean-int.org>
Abstract:
(Refer to Section 1.1, Purpose.)
Status:
This document was last revised or approved by the OASIS ebXML IIC TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/ebxml-iic.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/ebxml-iic/ipr.php).
Notices
OASIS takes no position regarding the validity or scope of
any intellectual property or other rights that might be claimed to pertain to
the implementation or use of the technology described in this document or the
extent to which any license under such rights might or might not be available;
neither does it represent that it has made any effort to identify any such
rights. Information on OASIS's procedures with respect to rights in OASIS
specifications can be found at the OASIS website. Copies of claims of rights
made available for publication and any assurances of licenses to be made
available, or the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or users of
this specification, can be obtained from the OASIS Executive Director.
OASIS invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to implement this
specification. Please address the information to the OASIS Executive Director.
Copyright © OASIS Open 2005. All Rights Reserved.
This document and translations of it may be copied and
furnished to others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, provided
that the above copyright notice and this paragraph are included on all such
copies and derivative works. However, this document itself may not be modified
in any way, such as by removing the copyright notice or references to OASIS,
except as needed for the purpose of developing OASIS specifications, in which
case the procedures for copyrights defined in the OASIS Intellectual Property
Rights document must be followed, or as required to translate it into languages
other than English.
The limited permissions granted above are perpetual and will
not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is
provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1.3
How to Use the Deployment Profile Template
2 Profiling the Modules of ebMS 2.0
2.3
Communication Protocol Bindings
2.3.1
Profile Requirement Item: Transport Protocol
3 Profile Requirements Details
3.1
Module: Core Extension Elements
3.1.1
Profile Requirement Item: PartyId
3.1.2
Profile Requirement Item: Role
3.1.3
Profile Requirement Item: CPAId
3.1.4
Profile Requirement Item: ConversationId
3.1.5
Profile Requirement Item: MessageId
3.1.6
Profile Requirement Item: Service
3.1.7
Profile Requirement Item: Action
3.1.8
Profile Requirement Item: Timestamp
3.1.9
Profile Requirement Item: Description.
3.1.10
Profile Requirement Item: Manifest
3.1.11
Profile Requirement Item: Reference
3.1.12
Profile Requirement Item: Reference/Schema
3.1.13
Profile Requirement Item: Reference/Description
3.2.1
Profile Requirement Item: Signature generation
3.2.2
Profile Requirement Item: Persistent Signed Receipt
3.2.3
Profile Requirement Item: Non Persistent Authentication
3.2.4
Profile Requirement Item: Non Persistent Integrity
3.2.5
Profile Requirement Item: Persistent Confidentiality
3.2.6
Profile Requirement Item: Non Persistent Confidentiality
3.2.7
Profile Requirement Item: Persistent Authorization
3.2.8
Profile Requirement Item: Non Persistent Authorization
3.2.9
Profile Requirement Item: Trusted Timestamp
3.3.1
Profile Requirement Item:
3.4.1
Profile Requirement Item: SyncReply
3.5
Module : Reliable Messaging
3.5.1
Profile Requirement Item: SOAP Actor attribute
3.5.2
Profile Requirement Item: Signed attribute
3.5.3
Profile Requirement Item: DuplicateElimination
3.5.4
Profile Requirement Item: Retries and RetryInterval
3.5.5
Profile Requirement Item: PersistDuration
3.5.6
Profile Requirement Item: Reliability Protocol
3.6.1
Profile Requirement Item: Status Request message
3.6.2
Profile Requirement Item: Status Response message
3.7.1
Profile Requirement Item: Ping-Pong Security
3.8.1
Profile Requirement Item: Use of intermediaries