Create stock webservice using WSDL, java and BPEL
$30-250 USD
Paid on delivery
1. Overview
The coursework of the module involves the design of an online Investment Brokering System (IBS). IBS
offers its clients the capability of making investment decisions and executing relevant transactions, including
the purchase and selling of shares through it, online. To provide these capabilities, IBS uses a number of
third party services including
• A Portfolio service for storing information about client transactions and their overall share portfolios.
• Services providing different types of financial information related to investment decisions including
live stock prices (LiveStockPrice service) and press headlines for different companies listed in stock
exchanges (StockHeadlines service), and
• Services enabling the execution of stock purchase and selling requests through the systems of
different stock exchanges that are accessible through IDS (StockExchange services).
IBS is to be realised as an executable BPEL process, deployed using a BPEL process execution engine
(e.g., the Apache Orchestration Director Engine (ODE) [1]). The BPEL process realising IBS should enable
the user to
• Create a portfolio of stocks through the Portfolio service (the portfolio may be empty when it is
initially created) [Functionality F1].
• Retrieve information from his/her portfolio through the Portfolio service. More specifically, it should
be possible for the user to retrieve at least all the transactions that he/has made for a given stock
over a given period of time, the total current value of his/her portfolio, and statistics regarding
transactions of a given type (i.e., sell/buy) for a given stock (e.g., min, max, average “sell” and “buy”
values for a given stock) [Functionality F2].
• Purchase shares through the StockExchange service [Functionality F3].
• Sell shares through the StockExchange service [Functionality F4].
• Retrieve press headlines for specific companies listed in stock exchanges through the
StockHeadlines service [Functionality F5].
• Contact the LiveStockPrice service to obtain live data for stocks of interest [Functionality F6].
2. Tasks
To do the above coursework you will need to complete the following tasks:
(i) Develop suitable web services in order to cover the functionalities F1 – F6 above. In the case of the
LifeStockPrice service you may wish to search for possible suitable services over the Internet and
use one of them to cover the required functionality. The services that you will develop should have a
realistic interface (i.e., sufficient set of operations and realistic data types). From a behavioral point
of view, however, it will be sufficient to have a simple implementation that can accept exemplar
inputs and provide exemplar outputs without needing to provide a full implementation that a realistic
web service of the same kind would normally have. For example, if you decide to develop your own
LiveStockPrice service, this service should be able to accept a stock identifier (stock exchange
listing symbol) and provide some fictitious live price data for this stock.
(ii) Specify the interfaces of all the services identified for IBS in WSDL. The WSDL specifications of
these services should include the portTypes, operations, messages and data types required in order
to realise the functionality expected by each service.
(iii) Specify a BPEL process in order to realise the functionality of IBS as described above. You are free
to make your own assumptions about the exact realisation of the functionality of IBS in cases where
the above description provides scope for different alternative realisations.
(iv) Deploy your BPEL process in a BPEL process execution engine, preferably the Apache
Orchestration Director Engine (ODE) and test it to ensure that it provides the above functionality and
interacts correctly with the external web services (including the client).
(v) Develop a simple Java client to enable an end user to interact with the BPEL proces
INM381: Service Oriented Architectures
Coursework 2012
1. Overview
The coursework of the module involves the design of an online Investment Brokering System (IBS). IBS offers its clients the capability of making investment decisions and executing relevant transactions, including the purchase and selling of shares through it, online. To provide these capabilities, IBS uses a number of third party services including
• A Portfolio service for storing information about client transactions and their overall share portfolios.
• Services providing different types of financial information related to investment decisions including
live stock prices (LiveStockPrice service) and press headlines for different companies listed in stock exchanges (StockHeadlines service), and
• Services enabling the execution of stock purchase and selling requests through the systems of different stock exchanges that are accessible through IDS (StockExchange services).
IBS is to be realised as an executable BPEL process, deployed using a BPEL process execution engine (e.g., the Apache Orchestration Director Engine (ODE) [1]). The BPEL process realising IBS should enable the user to
• Create a portfolio of stocks through the Portfolio service (the portfolio may be empty when it is initially created) [Functionality F1].
• Retrieve information from his/her portfolio through the Portfolio service. More specifically, it should be possible for the user to retrieve at least all the transactions that he/has made for a given stock over a given period of time, the total current value of his/her portfolio, and statistics regarding transactions of a given type (i.e., sell/buy) for a given stock (e.g., min, max, average “sell” and “buy” values for a given stock) [Functionality F2].
• Purchase shares through the StockExchange service [Functionality F3].
• Sell shares through the StockExchange service [Functionality F4].
• Retrieve press headlines for specific companies listed in stock exchanges through the
StockHeadlines service [Functionality F5].
• Contact the LiveStockPrice service to obtain live data for stocks of interest [Functionality F6].
2. Tasks
To do the above coursework you will need to complete the following tasks:
(i) Develop suitable web services in order to cover the functionalities F1 – F6 above. In the case of the LifeStockPrice service you may wish to search for possible suitable services over the Internet and use one of them to cover the required functionality. The services that you will develop should have a realistic interface (i.e., sufficient set of operations and realistic data types). From a behavioral point of view, however, it will be sufficient to have a simple implementation that can accept exemplar inputs and provide exemplar outputs without needing to provide a full implementation that a realistic web service of the same kind would normally have. For example, if you decide to develop your own LiveStockPrice service, this service should be able to accept a stock identifier (stock exchange listing symbol) and provide some fictitious live price data for this stock. (ii) Specify the interfaces of all the services identified for IBS in WSDL. The WSDL specifications of these services should include the portTypes, operations, messages and data types required in order to realise the functionality expected by each service. (iii) Specify a BPEL process in order to realise the functionality of IBS as described above. You are free to make your own assumptions about the exact realisation of the functionality of IBS in cases where the above description provides scope for different alternative realisations. (iv) Deploy your BPEL process in a BPEL process execution engine, preferably the Apache Orchestration Director Engine (ODE) and test it to ensure that it provides the above functionality and interacts correctly with the external web services (including the client). (v) Develop a simple Java client to enable an end user to interact with the BPEL pr
Project ID: #1590779
About the project
4 freelancers are bidding on average $150 for this job
Hi, I'm a trainer w/ wide exposure to Webservices and bpel,among other technologies. I create these kinds of projects regularly as part of my course materials. I should be able to deliver the entire project from sta More