Difference between revisions of "Spicy-stonehenge"

From Scube-casestudies
Jump to: navigation, search
Line 1: Line 1:
==Description==
 
 
 
Spicy Stonehenge is an implementation of Apache Stonehenge [1] built on top of the Turmeric SOA platform [2]. Our goal with this project is to create a use case that researchers can use to validate their research and compare results by using a common platform.
 
Spicy Stonehenge is an implementation of Apache Stonehenge [1] built on top of the Turmeric SOA platform [2]. Our goal with this project is to create a use case that researchers can use to validate their research and compare results by using a common platform.
  
==Quick Overview==
+
== Quick Overview==
  
 
The Stonehenge system is composed of 5 web services, 1 web application and 2 databases.
 
The Stonehenge system is composed of 5 web services, 1 web application and 2 databases.
Line 9: Line 7:
 
The services are described as follows:
 
The services are described as follows:
  
* Business Service - Provides the business logic required for the web application to operate.
+
* '''Business Service''' - Provides the business logic required for the web application to operate.
* Configuration Service - Acts as a directory where references to all the instances of the web services are kept. Whenever the trader client wants to perform an action, it must first ask the configuration service for an endpoint.
+
* '''Configuration Service''' - Acts as a directory where references to all the instances of the web services are kept. Whenever the trader client wants to perform an action, it must first ask the configuration service for an endpoint.
* Order Processor Service - Whenever a buy or sell order is made, the business service will interact with the Order Processing Service to make the order final.
+
* '''Order Processor Service''' - Whenever a buy or sell order is made, the business service will interact with the Order Processing Service to make the order final.
* Exchange Service - If a purchase is made in a currency different from that of the wallet used, it gets converted by the Exchange Service which uses real currency data from Google.
+
* '''Exchange Service''' - If a purchase is made in a currency different from that of the wallet used, it gets converted by the Exchange Service which uses real currency data from Google.
* Quote Service - The quote service provides live quote information from Yahoo Finance. This service can be used directly to query the price of a certain stock symbol. It is also used indirectly whenever an order is placed as the Order Processing Service queries it to find the right price at which to place the order.
+
* '''Quote Service''' - The quote service provides live quote information from Yahoo Finance. This service can be used directly to query the price of a certain stock symbol. It is also used indirectly whenever an order is placed as the Order Processing Service queries it to find the right price at which to place the order.
  
 
In this project, it’s common to see the abbreviations BS and OPS, these refer to the Business and Order Processing services respectively.
 
In this project, it’s common to see the abbreviations BS and OPS, these refer to the Business and Order Processing services respectively.
Line 21: Line 19:
 
The web application is built using PHP and most of the code is reused from the original project. Some minor changes have been made to accommodate the new, Turmeric-powered web services.
 
The web application is built using PHP and most of the code is reused from the original project. Some minor changes have been made to accommodate the new, Turmeric-powered web services.
  
==Business Goals and Domain Assumptions==
+
== Basic technology ==
 +
 
 +
E.g., WSDL, BPEL, UML, Data
  
Business Goals and the Domain Assumptions for the current case study.
+
== How to install ==
  
=== Business Goals ===
+
If applicable, please give a clear procedure for installing the artifact
  
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
+
== How to use ==
|+ Table BG1. Business Goal ID<br>
 
|-
 
! Field
 
! Description
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID
 
| ID
 
|- style="background:white; color:black"
 
! Short Name
 
| Spicy-stonehenge
 
|- style="background:white; color:black"
 
! Type
 
| Stock Trader.
 
|- style="background:white; color:black"
 
! Description
 
| To buy and sell stocks
 
|- style="background:white; color:black"
 
! Rationale
 
| <br>
 
|- style="background:white; color:black"
 
! Involved Stakeholders
 
| <br>
 
|- style="background:white; color:black"
 
! Priority of accomplishment
 
| <br>
 
|}
 
  
== Domain Analysis ==
+
If applicable, describe how to interact with the artifact
  
=== Strategic Dependency Model and Context Diagram ===
+
== Download ==
  
=== Domain Model===
+
URL where to download the package
  
== Scenarios==
+
== Additional info ==
The scenarios
 
  
 +
Link to papers or technical reports that could be useful to understand and use the artifact
  
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
+
== Related case study ==
|+ Table S1: Scenario ID
 
|-
 
! Field
 
! Description
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID
 
| ID
 
|- style="background:white; color:black"
 
! Short Name
 
| Spicy-stonehenge
 
|- style="background:white; color:black"
 
! Related To
 
| Apache Stonehenge
 
|- style="background:white; color:black"
 
! Involved Actors
 
| <br>
 
|- style="background:white; color:black"
 
! Detailed Operational Description
 
| see the quick overview.
 
|- style="background:white; color:black"
 
! Problems and Challenges
 
|<br>
 
<br>
 
|- style="background:white; color:black"
 
! Additional Material
 
| <br>
 
|}
 
  
== Bibliography ==
+
In case your artifact is directly related to one or more the case studies included in this repository, please put here a link to these case studies. For instance, if the artifact implements the scenario described in the "Automotive Case Study" then add a link to the page http://scube-casestudies.ws.dei.polimi.it/index.php/Automotive_Case_Study
#<div id="1"></div>  http://incubator.apache.org/stonehenge/.
 
#<div id="2"></div>  https://www.ebayopensource.org/index.php/Turmeric/HomePage.
 
#<div id="3"></div> https://www.ebayopensource.org/forum/.
 
#<div id="4"></div> http://ant.apache.org/.
 
#<div id="5"></div> http://wso2.com/products/web-services-framework/php/.
 

Revision as of 10:45, 31 May 2012

Spicy Stonehenge is an implementation of Apache Stonehenge [1] built on top of the Turmeric SOA platform [2]. Our goal with this project is to create a use case that researchers can use to validate their research and compare results by using a common platform.

Quick Overview

The Stonehenge system is composed of 5 web services, 1 web application and 2 databases.

The services are described as follows:

* Business Service - Provides the business logic required for the web application to operate.
* Configuration Service - Acts as a directory where references to all the instances of the web services are kept. Whenever the trader client wants to perform an action, it must first ask the configuration service for an endpoint.
* Order Processor Service - Whenever a buy or sell order is made, the business service will interact with the Order Processing Service to make the order final.
* Exchange Service - If a purchase is made in a currency different from that of the wallet used, it gets converted by the Exchange Service which uses real currency data from Google.
* Quote Service - The quote service provides live quote information from Yahoo Finance. This service can be used directly to query the price of a certain stock symbol. It is also used indirectly whenever an order is placed as the Order Processing Service queries it to find the right price at which to place the order.

In this project, it’s common to see the abbreviations BS and OPS, these refer to the Business and Order Processing services respectively.

The databases run off an Apache Derby server and skeletons for them are also provided as part of this project. This database was not available as part of the original project and was built from scratch.

The web application is built using PHP and most of the code is reused from the original project. Some minor changes have been made to accommodate the new, Turmeric-powered web services.

Basic technology

E.g., WSDL, BPEL, UML, Data

How to install

If applicable, please give a clear procedure for installing the artifact

How to use

If applicable, describe how to interact with the artifact

Download

URL where to download the package

Additional info

Link to papers or technical reports that could be useful to understand and use the artifact

Related case study

In case your artifact is directly related to one or more the case studies included in this repository, please put here a link to these case studies. For instance, if the artifact implements the scenario described in the "Automotive Case Study" then add a link to the page http://scube-casestudies.ws.dei.polimi.it/index.php/Automotive_Case_Study