Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "STP/IM Component/Sample scenario involving the intermediate meta-model"
(→Defining a basic process) |
(→Defining a basic process) |
||
| Line 9: | Line 9: | ||
== Defining a basic process == | == Defining a basic process == | ||
| − | Using a "process editor" such as a BPMN or BPEL editor, the | + | Using a "process editor" such as a BPMN or BPEL editor, the business analyst defines a simple travel agency scenario, reserving a hotel. The reservation process involves booking a room, obtaining the weather forecast for the trip dates and sending a confirmation email to the customer. |
[[Image:travel_process.png]] | [[Image:travel_process.png]] | ||
| − | The "process editor" saves the representation of its diagram into the intermediate model. The model now | + | The "process editor" saves the representation of its diagram into the intermediate model. The model now contains the following instances: |
[[Image:initial-steps.png]] | [[Image:initial-steps.png]] | ||
| + | |||
| + | == Opening the SCA Editor == | ||
| + | In order to start defining the architecture for the travel reservation system, the architect opens up the STP's own SCA Editor. Since the editor is linked with the internal model, it provides an automatic "import" of its elements and creates empty placeholders for services corresponding to the identified processes. This placeholders would later be refined to either implement the required services or to link to external services. | ||
| + | |||
| + | Since the intermediate model contains one process, the SCA Editor interprets this as a request for an orchestration service and creates one. It is this newly created orchestration service that will provide the process functionality. The services involved in the orchestration are placed inside a generated composite that will expose the process service's interface. The figure below shows a rendering of the composite. | ||
| + | [[Image:initial-composite.png]] | ||
Revision as of 18:18, 26 August 2007
This page presents a possible scenario for creating a sample SOA architecture using several Eclipse STP editors. The scenario greatly simplifies the description of each step in order to keep the presentation focused on the representation of artefacts in the internal meta-model. In addition, the representation of the resulting internal model is kept to a minimum, ignoring some elements of the meta-model completely for the purpose of reducing visual clutter. Some of the elements that are ignored are:
- Owner
- Transition
- TransitionUnderCondition
- ObservableAttribute
Each of the following steps in creating the architecture for a [highly original] sample travel service involves the usage of an editor. Each section of this page shows one such step, highlighting the simplified output of the editor as well as the resulting intermediate model.
Defining a basic process
Using a "process editor" such as a BPMN or BPEL editor, the business analyst defines a simple travel agency scenario, reserving a hotel. The reservation process involves booking a room, obtaining the weather forecast for the trip dates and sending a confirmation email to the customer.
The "process editor" saves the representation of its diagram into the intermediate model. The model now contains the following instances:
Opening the SCA Editor
In order to start defining the architecture for the travel reservation system, the architect opens up the STP's own SCA Editor. Since the editor is linked with the internal model, it provides an automatic "import" of its elements and creates empty placeholders for services corresponding to the identified processes. This placeholders would later be refined to either implement the required services or to link to external services.
Since the intermediate model contains one process, the SCA Editor interprets this as a request for an orchestration service and creates one. It is this newly created orchestration service that will provide the process functionality. The services involved in the orchestration are placed inside a generated composite that will expose the process service's interface. The figure below shows a rendering of the composite.
