This is a working document of the OASIS WSBPEL Technical Committee. It maintains a list of both approved and potential use cases for the BPEL4WS specification . When a potential use case is approved, its entry is moved from the Pending section to the In Process section. Use cases that are reviewed and approved by the TC are moved to the Approved section of this document.
This is a living document, frequently updated as additional use cases are identified and voted upon by the TC.
The WSBPEL TC. utilizes use cases to identify and clarify the role of BPEL to solve a specific issue. Use Cases can be informal, such as simple narrative descriptions, or very formal, such as those used in designing and building large, complex systems. The WSBPEL TC employs Use Cases to help clarify capture information about the context, activity and requirements involved in an area of specification development.
Use Cases are grouped into the following categories:
While most of the Use Cases have been developed by the WSBPEL Use Case subgroup, others may have been donated by individuals or organizations external to the WSBPEL TC. Please contact us if you are interested in contributing a WSBPEL Use Case.
- Technical Use Cases (clarifying the specification)
- Industry-specific Use Cases (BPEL for vertical industries)
- Other (Based upon external submissions)
Please use the template when submitting a Use Case. Note that while the templates are fairly detailed, only the following fields are required:
- Contact Name and Email
- Publishing preferences (e.g. making your Use Case public/removing your email address and/or organization's name and references)
- Organization Name/Abbreviation-Index, where index is the number of the use case you are submitting. e.g. MS-01.
- Title - a brief (short sentence) title for the use case.
- Assumptions - A description of what if anything is assumed to have happened before the activities described in the use case description.
- Description - A narrative description of the use case or usage scenario. For example, "John designed a PO process" is a usage scenario while "Analyst designs a business process" is a generalized Use Case.
- Exceptions - Short description of error situations that may arise.
- Optional Artifacts - Additional artifacts may include sample BPEL and sample WSDL. Note, however, that these artifacts are not required to submit a Use Case to the WSBPEL TC. The goal of the Use Cases are to describe scenarios in which BPEL can be utilized. Depending on the Use Case, a sample BPEL representation may not be required. For example, while a BPEL example may not be needed to describe the use of BPEL in a supply chain, a BPEL example is probably necessary to clarify targeted sections of the specification. Please be sure to include any additional artifacts when submitting your Use Case.
Please send your Use Case submissions to email@example.com.
|Nuperus-01||Multi- party message transformation in application integration (AI)|
|Description||This is a general use case for an application integration effort using the BPEL as WSDL definitions in XML. A Sales Force Automation application (SFA) needs to interact with a Customer Relation Management (CRM) application as part of a business operation of an enterprise. A BPEL-based execution environment (engine + platform) is used for application integration (AI).|
Simpl-eb is a business led approach to business communication focused on simplifying the underlying communication of the trading process. It is the smallest electronic component of the business messaging architecture. Simpl-eb enables users to trade information more efficiently by eliminating unnecessary information in the exchange of business messages. Simpl-eb is based upon the core commercial business processes used in the trade of products and services, which enable application to any industry. The data used for Simpl-eb assumes item synchronization or alignment occurs prior to the commercial collaborative business processes. It is maintained as changes to data take place in accordance with industry guidelines and rules. Simpl-eb utilizes a Global Data Dictionary to use a common definition of industry standard attributes provided in a globally-accepted set of common terms.
Simpl-eb is a sequence of messages that can be expanded to account for additional scenarios for various contexts (e.g., industries, geographic regions, business practises). The seller identifies party data and sends the party message to the buyer or third party to map the party data and integrate it to complete the initial align data activities. Alignment of item information follows, permitting subsequent activities such as the purchase order, despatch advice, and request for payment (invoice).
|BCF-01||UN/CEFACT Business Collaboration Framework|
Mapping UN/CEFACT's Business Collaboration Framework to BPEL.
|CAM-001||eBusiness Transaction binding with external service – Validation.|
|Category||Other: external submission from the OASIS CAM TC|
|Description||The OASIS CAM TC team has created a specification and toolset that can act as an external service. A WSDL definition of a CAM process can provide the linkage between the CAM process and the BPEL. The BPEL will need to package the XML content that requires validation and pass that to the CAM process. The CAM process will return to the BPEL process the outcome from the external validation service.|
|CAM-002||eBusiness Transaction binding with external service - Transaction Assembly|
|Category||Other: external submission from the OASIS CAM TC|
|Description||The OASIS CAM TC team has created a specification and toolset that can act as an external service. The CAM process will return to the BPEL process the outcome from the external assembly service, along with either a completed transaction document, or a delivery result status.|
|MS-02||Automated Shipping Service|
|Category||Other - simple example of what could be an Industry-specific Use Case|
|Description||Example of a firm providing BPEL representations of
their interfaces to trading partners. A more complex
scenario might include a “Wal-Mart like” store and its
A shipping company provides services
to product firms, enabling them to ship products to their
customers using an automated shipping service.
|Category||Industry-specific Use Case|
|Description||The scenario relates to a reseller of PC’s selling configure-to-order PC’s in an instance when a consumer ,who buys through this reseller, wants to change the configuration of the PC he has ordered by say, upgrading the disk drive.
This results in a change request made by the reseller on the manufacturer. The reseller places a request to change the product configuration information, which is to upgrade the disk drive for the PC of a previously placed order.
The manufacturer’s process for order change, which follows the RosettaNet PIP for an order change, has various process steps and decision points. The first process step is the receipt of order change request from the reseller.
|MS-01||BPEL Data Manipulation Options|
|Description||This is a Technical Use Case designed to illustrate
various options for manipulating data with BPEL. Technical
Use Cases are designed to clarify the BPEL specification and
do not necessarily have workflows associated with them.|
The following options are illustrated: Variable initialization, Assignment of string, numeric, boolean and date values, Assignment of variables by copying other variable’s values, Sample XPath calculations, Working with array structures
The sample BPEL markup appears in the Abstract BPEL section of the document.