Embed Size (px)
Citation preview
Deliverable D300.12
Final Scenario Executions
WP 300
Project Acronym & Number: FIspace – 604 123
Project Title: FIspace: Future Internet Business Collaboration Networks in Agri-Food, Transport and Logistics
Funding Scheme: Collaborative Project - Large-scale Integrated Project (IP)
Date of latest version of Annex 1: 17.03.2015
Start date of the project: 01.04.2013
Duration: 30
Status: Final
Authors: Eliezer Dekel
Contributors: Carmen Perea Escribano, Fabiana Fournier, Seyhun Mehmet Futacı, Aggelos Groumas, Dany Moshkovitz , Philip Reimer, Havier Romero, Vasileios Sarris,
Document Identifier: FIspace D300.12
Date: 30.09.2015
Revision: 02
Project website address: http://www.FIspace.eu
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 2 of 20
The FIspace Project
Leveraging on outcomes of two complementary Phase 1 use case projects (FInest & SmartAgriFood), aim of FIspace is to pioneer towards fundamental changes on how collaborative business networks will work in future. FIspace will develop a multi-domain Business Collaboration Space (short: FIspace) that employs FI technologies for enabling seamless collaboration in open, cross-organizational business net-works, establish eight working Experimentation Sites in Europe where Pilot Applications are tested in Early Trials for Agri-Food, Transport & Logistics and prepare for industrial uptake by engaging with play-ers & associations from relevant industry sectors and IT industry.
Project Summary
As a use case project in Phase 2 of the FI PPP, FIspace aims at developing and validating novel Future-Internet-enabled solutions to address the pressing challenges arising in collaborative business networks, focussing on use cases from the Agri-Food, Transport and Logistics industries. FIspace will focus on ex-ploiting, incorporating and validating the Generic Enablers provided by the FI PPP Core Platform with the aim of realising an extensible collaboration service for business networks together with a set of innovative test applications that allow for radical improvements in how networked businesses can work in the future. Those solutions will be demonstrated and tested through early trials on experimentation sites across Eu-rope. The project results will be open to the FI PPP program and the general public, and the pro-active engagement of larger user communities and external solution providers will foster innovation and indus-trial uptake planned for Phase 3 of the FI PPP.
Project Consortium
DLO; Netherlands Kühne + Nagel; Switzerland
ATB Bremen; Germany University Duisburg Essen; Germany
IBM; Israel ATOS; Spain
KocSistem; Turkey The Open Group; United Kingdom
Aston University; United Kingdom CentMa; Germany
ENoLL; Belgium iMinds; Belgium
KTBL; Germany Marintek; Norway
NKUA; Greece University Politecnica Madrid; Spain
Wageningen University; Netherlands Arcelik; Turkey
PlusFresc; Spain EuroPoolSystem; Germany
FloriCode; Netherlands GS1 Germany; Germany
Kverneland; Netherlands Mieloo & Alexander; Netherlands
North Sea Container Line; Norway OPEKEPE; Greece
LimeTri; Netherlands Innovators; Greece
BO-MO; Slovenia CIT; Spain
MOBICS; Greece SDZ; Germany
Fraunhofer IML; Germany Snoopmedia; Germany
Q-ray; Netherlands EECC; Germany
FINCONS; Italy CBT; Spain
More Information
Harald Sundmaeker (deputy coordinator) e-mail: [email protected]
ATB Bremen GmbH phone: +49 421 220920
FIspace website: www.FIspace.eu
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 3 of 20
Dissemination Level
PU Public
PP Restricted to other programme participants (including the Commission Services)
RE Restricted to a group specified by the consortium (including the Commission Services)
CO Confidential, only for members of the consortium (including the Commission Services)
Change History
Version Notes Date
01 Creation of the document 25.09.2015
02 Refinement with partner input 30.09.2015
Document Summary
In this report we discuss the execution of the use cases as defined in WP400 and in collaboration with business partners. It also includes analysis of the usefulness of the platform. It relates to Subtasks 342 and 343 of WP300.
The document provides a general overview of running an experiment on FIspace as well as actual exe-cution description of the different steps of the use case trials and the analysis of the outcomes. We have established a knowledge base (WIKI) for sharing knowledge regarding experience in defining and execut-ing experiments and to understand what can be done and used to demonstrate usefulness of new ser-vices and/or applications. The document points out the relevant places in the FIspace Wiki for developers and Business Architects who intend to test their applications/scenarios on the experimentation Environ-ment
This document is compiling all the related specifications and agreements to use the results of the FIspace project. It is intended for developers and business architects who want to use FIspace, especially FI-WARE phase 3 accelerators that are funding a large number of application developers also in the agri-food domain.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 4 of 20
Abbreviations
App Software Application
D Deliverable
DoW Description of Work
EC European Commission
e.g. Exempli gratia = for example
EU European Union
FIA Future Internet Assembly
FI PPP Future Internet Public Private Partnership
FP7 Framework Programme 7
GA Grant Agreement
ICT Information and Communication Technology
i.e. id est = that is to say
IP Intellectual Property
IPR Intellectual Property Rights
KPI Key Performance Indicator
M Month
RTD Research and Technological Development
SME Small and Medium Sized Enter-prise
ST Sub-Task
T Task
WP Work Package
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 5 of 20
Table of Contents
1 Introduction ....................................................................................................................................... 7
1.1 Content and Purpose ................................................................................................................ 7
2 Experimentation Environment ......................................................................................................... 7
2.1 EE Objectives ........................................................................................................................... 7
2.2 EE Documentation .................................................................................................................... 7
2.3 EE Procedures ......................................................................................................................... 7
2.4 Related information and documents: ........................................................................................ 8
3 Generic guide for implementing scenarios using the EE core .................................................... 9
3.1 Create and run experiments using the FIspace platform. ........................................................ 9
3.1.1 Implement a Backend Simulator component relevant to the scenario and connect it with the FIspace platform ....................................................................................................................... 9
3.1.2 Define-run the experiments .................................................................................................... 10
3.2 Demo of test scenario ............................................................................................................. 13
4 Product Information Exchange Scenario Using Experimentation Environment ..................... 14
4.1 Introduction ............................................................................................................................. 14
4.2 Product Information Exchange Scenario ................................................................................ 14
4.2.1 Description .............................................................................................................................. 14
4.3 Backend Simulator ................................................................................................................. 15
4.4 Experiments ............................................................................................................................ 15
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 6 of 20
List of Figures
Figure 1: Backend Simulator ................................................................................................................... 9
Figure 2: Search for farmers experiment ............................................................................................... 11
Figure 3: Search for farmer’s results experiment .................................................................................. 12
Figure 4: Experiment logs ...................................................................................................................... 13
Figure 5: Message Sequence Chart for Product Information Exchange ............................................... 14
Figure 6: Provide Shipment Details ....................................................................................................... 16
Figure 7: Execution results .................................................................................................................... 17
Figure 8: Another experiment setup ...................................................................................................... 18
Figure 9: Execution results for the experiment in Figure 8. ................................................................... 19
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 7 of 20
1 Introduction
1.1 Content and Purpose
There are three main parts to this deliverable. In the first part we provide a general overview of what is available in FIspace for Developers and Business Architects who want to experiment with the platform. The related information section might be the most useful part for the reader as it maps out the knowledge base that we have accumulated running the trials of this project. The second part is a step by step gen-eral “how to” run an experiment summary. The third and last part goes into a detailed example. Another example, the Greenhouse Scenario, is available in the ownCloud. See the related information and docu-ments section.
2 Experimentation Environment
This chapter summarizes FIspace Experimentation Environment (EE) objectives, documentation, and procedures for supporting new application developers and users including the Phase 3 community.
2.1 EE Objectives
FIspace Experimentation Environment (EE) aims at providing a means via different stakeholders will be able to explore, interact with, and understand how FIspace platform works in practice. Specifically the EE provides a controlled environment in which developers and business architects can test new collaborative scenarios before these processes are released for use by “end users”. Developers can gain some confi-dence in understanding the services provided by FIspace and check how their application interact with these services and with their own backend. This allows them use FIspace in a conroled environment, and can start to see the benefits of using it. From September 2015 until September 2016 the role of the EE is to support phase 3 developers and business architects in the creation of new apps and business pro-cesses.
2.2 EE Documentation
The following WIKI page https://bitbucket.org/fispace/experimentation-environment/wiki/Experiments%20definition%20and%20execution%20in%20EE-core presents how to create and run experiments in the EE along with some examples. The documentation in the Wiki should complement the FIspace documentation for developers and business architects. The stress in the EE wiki will be on how to use the platform, less on technical details which are more suitable for the FIspace plat-form developers.
2.3 EE Procedures
Two different roles are involved in the deployment of new apps and business processes in the platform: business architects and developers.
The deployment of a new app by a developer includes the following steps (technical details on the de-ployment can be found in FIspace platform documentation):
1. Creation of the messages and capabilities by the developer
2. Review and approval of these messages by the FIspace review committee. This step can be iter-ated if errors or corrections are necessary by the business developer. Each review cycle currently takes a week.
3. Request for the upload of the app
4. Deployment to the EE
The deployment of a new business process/collaboration by a business architect requires the following steps:
1. Creation of the messages and capabilities by the developer
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 8 of 20
2. Review and approval of these messages by the FIspace review committee. This step can be iterated if errors or corrections are necessary by the business developer. Each review cycle takes a week.
3. Creation of the business process and rule patterns
4. Request for the upload of the business process
5. Deployment to the EE
2.4 Related information and documents:
The experimentation environment Wiki should be consulted to find out the current version de-
ployed: https://bitbucket.org/fispace/experimentation-
environment/wiki/Experiments%20definition%20and%20execution%20in%20EE-
core
If the application requires new messages (we believe that most applications can do with the existing defined set).
o Frequency of updates in the EE. This includes frequency of updates in:
New messages – We recommend at the beginning once a week. This can be less once the accelerators projects finish their development.
New business processes – once in two weeks?
Bug fixing- once a week?
o Review committee – Who will take care of this? Today done by Javier Hitado and Paco.
Deliverable 400.5
FIspace Results & Offering document
EE_last_prototype description - Information regarding defining and executing experiments in the latest deliverable of EE core in. This document focuses on the Greenhouse Scenario: https://www.atb-bre-men.de/owncloud/index.php/apps/files/ajax/download.php?dir=%2FShared%2FFIspace%2FDeliverables%2FD300.11-EEfinalRelease&files=EE_last_prototype_description.docx
Video having as a testcase Marketplace operations service experiments here: https://www.atb-bre-men.de/owncloud/index.php/apps/files?dir=%2FShared%2FFIspace%2FWPs%2FWP300%2FT350-Facilities%2FT352%20-%20Experimentation%20Environment%20Core%2Fdemo_with_sdi%2Fmos_testcase
Another demo video about the EE: https://www.atb-
bre-
men.de/owncloud/index.php/apps/files/?dir=%2FShared%2FFIspace%2FWPs%2FW
P300%2FT350-Facilities%2FT352%20-
%20Experimentation%20Environment%20Core%2Flatest_demo_status
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 9 of 20
3 Generic guide for implementing scenarios using the EE core
3.1 Create and run experiments using the FIspace platform.
The experimentation environment is in general responsible for the creation/modification of FIspace exper-iments and their execution. These experiments are a set of several steps relative to a specific scenario (e.g. greenhouse, logistics, flowers etc. and the FIspace platform) .Each step has specific description, parameters and a script/jar/executable/REST that is responsible for executing the specific scenario’s functionality for this step.
The steps for having such scenarios are the following:
1. Implement a Backend Simulator component relevant to the scenario and connect it with the FIspace platform.
a. Choose messages from FIspace API to communicate with the platform
b. Define security application for secure connection with FIspace
2. Define-run the experiments
a. Define the steps of the experiment scenario
b. Define KPIs that can be measured by the experimenter to show the results of the experi-ment execution.
c. Execute the experiment
d. Check the logs
e. Calculate KPIs through the reports
3.1.1 Implement a Backend Simulator component relevant to the scenario and connect it with the FIspace platform
At first a Backend Simulator has to be defined. A Backend Simulator is a component that imitates a FIspace backend service. In other words it provides a capability through the EE SDI so that it can be used in experiments defined through EE core. So for each scenario a Backend simulator implementation is needed.
BackendSimulator
-InitializeConfiguration()
-utilizeCapability()
Figure 1: Backend Simulator
The initialization method will do the following:
Get a token from Keycloak to be authenticated in EE SDI using an application id, secret
Search for the capability type that is wanted to be used for sending and receiving messages in this mock service.
Register a business process template
Register the capabilities that will be offered by the Backend simulator
There can be capabilities offering information or receiving information according to messages defined in the capability types.
Register a business process for these capabilities
An example Backend Simulator implementation imitating a sensor values provider capability is available Here
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 10 of 20
The utilizeCapability method is exposed in the REST interfaces implemented by the Backend Simulator. The REST interfaces will use the capability type messages so as to be able to exchange messages with the EE SDI.
The Backend Simulator can have simplified REST APIs that will do queries and communicate with SDI for fetching information after interacting with the capability. Or it can be used as any service that FIspace offers.
3.1.2 Define-run the experiments
After having implemented a scenario specific Backend Simulator we are ready to define experiments that will use it and measure performance, capture logs and calculate KPIs for reports.
a. Define the steps of the experiment scenario
The steps for each scenario are specific to it and cannot be generalized. We will show an example for a scenario where we have created a Backend simulator that is offering the EE FIspace platform a search for farmers’ capability. In other words it offers a service where someone can search through the SDI and connection to our searchForFarmers Backend Simulator for farmers according to simple criteria.
Also the number of experiments is case specific. In order to evaluate a scenario many experiments may need to be implemented or a single one with many steps.
So in this case we need to define 2 experiments.
A first one, searching for farmers:
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 11 of 20
Figure 2: Search for farmers experiment
In this scenario, we are searching for farmers with VAT ID = 2 and we have one step with a link that is querying the corresponding capability.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 12 of 20
A second experiment is set for getting the results of SDI-capability communication.
Figure 3: Search for farmer’s results experiment
A one step experiment for fetching all results of executing the real experiment in the first case is created.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 13 of 20
3.1.2.1 Define KPIs that can be measured by the experimenter to show the results of the experiment execution.
At this point there have to be implemented specific KPICalculator Implementations that will measure KPIS relevant to the scenario.
For example for a search for farmers scenario there can be defined KPIs that will measure farmers found per query, total farmers in the database, time elapsed to search farmers etc.
This will have to parse the Experiment execution logs and do the processing.
By default we have the following KPIs
a) Response time for the whole execution b) Step execution time c) Validity of response time d) Success rate of steps
3.1.2.2 Execute the experiment, check the logs
Figure 4: Experiment logs
After executing the experiments we can see the logs of the experiment taking place.
3.1.2.3 Calculate KPIs through the reports
After executing the experiment a report can be created by choosing the appropriate KPIs and calculating it.
3.2 Demo of test scenario
In mos scenario (available in owncloud) the video of the execution is available and it can be seen along-side with a message capturing facility to show what messages are exchanged in the EE core, the Backend simulator and the EE SDI.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 14 of 20
4 Product Information Exchange Scenario Using Experimentation Environment
4.1 Introduction
The Experimentation Environment Core is in general responsible for the creation/modification of FIspace experiments and their execution. These experiments are a set of several steps relative to a specific sce-nario (e.g. greenhouse, logistics, flowers etc. and the FIspace platform). Each step has specific descrip-tion, parameters and a script/jar/executable/REST that is responsible for executing the specific scenario’s functionality for this step.
A relatively new module of the Experimentation Environment is the backend simulator module that in-tends to help developers with simulating backends needed in order to execute their scenarios end-to-end against the Fispace platform. In this chapter we provide a step by step walk through for the FIspace Product Information Exchange scenario.
4.2 Product Information Exchange Scenario
4.2.1 Description
In this scenario, product information (i.e. product quality-related information) shall be exchanged between FIspace users/companies (i.e.apps of these users/companies). Therefore we focus in the first part on 2 apps and more (at least 2 more) in further parts:
1. Communication between Initial Apps: Connection between multiple PIA (Product Information App) instances as well as forwarding product information from PIA towards TIC (Tailored Information for Consumers app) Instances both of the same FIspace user/company
2. Involvement of Open Call Apps: Forwarding of packaging information from PIA towards Boxman (Box Management app) instances both of the same FIspace user/company as well as providing of product information on demand from PIA towards Riskman (Risk Management app) instances both of the same FIspace user/company
The purpose of the PIA is to enable stakeholders of a food supply chain to exchange quality-related prod-uct information across the company IT system boundaries of the individual stakeholders including hori-zontal collaboration with service providers, laboratories, etc. Products are exchanged between actors in the food supply chain in the form of shipments; in parallel with the flow of physical goods, the stakehold-ers need to forward the associated quality-related product information. Therefore, the shipment has been identified as the business entity exchanged between actors, and the PIA deals with the virtualisation of shipments between supply-chain actors using FIspace. In these virtualised deliveries, process and prod-uct related information is included. Below find the message sequence chart for this scenario.
Figure 5: Message Sequence Chart for Product Information Exchange
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 15 of 20
More information about the Product information Exchange scenario can be found in the FIspace wiki page [1]
4.3 Backend Simulator
Following the backend simulator guide [2] that can be found in the Experimentation Environment wiki, we are simulating the customer PIA backend and the BOXMAN backend. Please note that there is no need to create separate backend simulators in order to simulate different backends, as a single backend simu-lator can implement all the required capabilities for a scenario.
Initilalization:First we create the initialization resource class, named “CapsInitResource” that is used to register everything that is needed for the execution of the scenario, on the FIspace side. This includes the registration of a Business Process Template, Business Roles, a Business process, and the needed Ca-pabilities.
Capabilities Implementation: The needed capabilities are implemented in classes “CapabilityResource” and “CapsUsageResource”.
The web application is packaged as a .war file and then deployed in a Jetty web server that has an exter-nal IP address. This is needed so that FIspace can reach back the simulator.
The backend simulator code is published as a sub-module of the Experimentation Environment, any in-terested readers in developing a simulator are advised to review it so they can see a concrete example [3].
4.4 Experiments
In order to do some testing we define some experiments against the backend. So we go ahead and test the “provide_shipment_details” capability, by providing an id for the shipment we are interested in. A sim-ple experiment with a single step will suffice.
The definition of such an experiment is shown in the screenshot below.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 16 of 20
Figure 6: Provide Shipment Details
By executing the experiment and requesting the logs we can see that the response is a ProvideShip-mentDetailsResponseMessage mashalled in XML format. The logs do not show completely as the re-sponse is too big.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 17 of 20
Figure 7: Execution results
Now let’s perform another experiment with the initialization of the backend.
The definition of the experiment is depicted below:
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 18 of 20
Figure 8: Another experiment setup
Executing the experiment we can see that no logs are produced in this case.
FIspace 30.09.2015
FIspace-D300.12-FinalScenarioExecutions-V02.docx Page 19 of 20
Figure 9: Execution results for the experiment in Figure 8.
References:
[1] https://bitbucket.org/fispace/core/wiki/productInformationExchangeScenario
[2] https://bitbucket.org/fispace/experimentation-environment/wiki/BackendSimHowTo
[3] https://bitbucket.org/fispace/experimentation-environment/src/fefeca852b9ffe6d21b1ac57f328b3e1777349b2/PiaBackendSimulator/?at=default
