Deployment Profile Templates v1.1
For OASIS ebXML 2.0 Specifications
Public Review Draft 01, 04 December 2006
Artifact identifier:
ebXML_DPT-v1.1-Intro-wp-pr-01
Location:
http://www.oasis-open.org/committees/documents.php?wg_abbrev=ebxml-iic
Artifact Type:
White Paper
Technical Committee:
OASIS ebXML Implementation, Interoperability and Conformance (IIC) TC
Chair:
Jacques Durand, Fujitsu <jdurand@us.fujitsu.com>
Editor:
Monica Martin, Sun Microsystems <monica.martin@sun.com>
Contributors:
Jacques Durand, Fujitsu <jdurand@us.fujitsu.com>
Pete Wenzel, Sun Microsystems <pete.wenzel@sun.com>
Abstract:
Introduction to the set of Deployment Profile Templates produced by this Technical Committee for use with the ebXML 2.0 specifications.
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 2006. 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.
The heterogeneous nature of eBusiness transactions requires a flexible infrastructure/framework that supports simple service calls and complex document exchange. To support that goal, the Electronic Business (eBusiness) eXtensible Markup Language (XML) [ebXML] set of specifications was developed to enable electronic trading relationships between business partners and integrate new technologies.
Communicate data in common terms (Core Components)
Register and provide eBusiness artifacts and services (ebXML Registry Services and Registry Information Model)
Configure technical contract between business partners (Collaboration Protocol Profile and Agreements)
Provide secure and reliable transport (ebXML Messaging Service)
Enable business processes (ebXML Business Process Specification Schema)
In the realm of eBusiness, key integration patterns and technology has been realized and will realize SOA benefits in a pragmatic iterative manner. To promote use of independent yet aligned technologies, the ebXML IIC has created deployment profile templates to enable user communities to specify their use of these specifications. Each Deployment Profile Template created thus far is based on a template outline.
Three Deployment Profile Template have been created:
Deployment Profile Template for ebMS 2.0
Deployment Profile Template for CPPA 2.0
Deployment Profile Template for ebBP 2.0
A user community may use any of these templates to derive a Deployment Guide from it (or Deployment Profile Guide), that is specific to this community and that defines practical details on how this community is intending to apply the corresponding ebXML specification to do business.
More precisely, each one of the above templates allows user communities to effectively understand key functionality and tailor the use of each specification based on their technical requirements. It also identifies operational and business aspects that may impact the specification usage or further profile their business practices. For example, in a Deployment Guide derived from an above Template, a user community may require use of specific optional features, prohibit the use of other options, profile the content of some message headers, identifies the process for validating new artifacts such as message payloads, etc. These templates were developed to foster interoperability on multiple levels between participants, enable runtime collaboration, and document conventions associated with business processes and content.
OASIS
ebXML Messaging Services (ebMS) Technical
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-msg
OASIS
ebXML Collaboration Protocol Profile and Agreements (ebCPPA)
Technical
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-cppa
ebXML
Business Process Specification Schema (BPSS or ebBP) Technical
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-bp
Metadata
for Deployment Profile
Templates:
http://www.oasis-open.org/committees/download.php/19253/ebxml-iic-Deployment_Profile_Template-CD.doc
The
current versions of all ebXML Deployment Profile Templates may be
found on the OASIS ebXML Implementation, Interoperability and
Conformance (IIC) Technical Committee web
site:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-iic
More
information on each of these specifications may be found at their
respective web sites above, as well as in a white paper published by
the OASIS ebXML Joint Committee, available
at:
http://www.oasis-open.org/committees/download.php/17817/ebxmljc-WhitePaper-wd-r02-en.pdf
In addition to editors or direct contributors, the following individuals were members of the committee during the development of this specification or of a previous version of it:
|
Rev |
Date |
By Whom |
What |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ebXML_DPT-v1.1-Intro-wp-pr-01 04 December 2006
Copyright
© OASIS Open 2006. All Rights Reserved. Page