We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
D.2.3.2 FI-WARE Architecture WP4 contribution front page - FIWARE Forge Wiki

D.2.3.2 FI-WARE Architecture WP4 contribution front page

From FIWARE Forge Wiki

Jump to: navigation, search

Private Public Partnership Project (PPP)
Large-scale Integrated Project (IP)


D.2.3.2: FI-WARE Architecture

Project acronym: FI-WARE
Project full title: Future Internet Core Platform
Contract No.: 285248
Strategic Objective: FI.ICT-2011.1.7 Technology foundation: Future Internet Core Platform
Project Document Number: ICT-2011-FI-285248-WP4-D.2.3.2
Project Document Date: 2013-03-29
Deliverable Type and Security: Public
Author: FI-WARE Consortium
Contributors: FI-WARE Consortium

Executive Summary

This version of the deliverable "FI-WARE Architecture" outlines updated information for the FI-WARE project in the Second Release.

A description of the Reference Architecture linked to the different chapters of FI-WARE is given in detail. A description of FI-WARE Generic Enablers (GEs) being supported in each chapter is provided, including the description of the APIs that each FI-WARE Generic Enabler (GE) exposes to application developers or it uses to connect to another FI-WARE GEs.

The given content was improved significantly and additional information requested by the reviewers were adhere to. Parts of this document is being reused within the Open Specifications and help to distribute the information on detailed design and architecture to the general public and make the Open Specifications more self-contained.

About This Document

The FI-WARE Architecture describes the GEs of FI-WARE being implemented, interfaces between them and properties of both. It also brings a description of the architecture of components linked to the implementation of each of the FI-WARE GEs being developed within the FI-WARE project.

Application developers reading contents of this document should be able to understand how applications are programmed using APIs exposed by FI-WARE GEs (i.e., what is the programming model). They will learn what are the names, basic description of arguments, behavior and responses of the main operations in those APIs.

However, the detailed specification of FI-WARE APIs are outlined in the FI-WARE GE Open Specifications and related deliverables.

Intended Audience

The architecture description of components is given with new developers in mind, who join the development team linked to that component to make it effectively. Additionally service providers can learn about capabilities and functionality the FI-WARE platform provides. Thirdly use case projects and related colleagues might use the provided information to understand FI-WARE design and adapt their own architecture or adopt certain parts of the system.

Chapter Context WP2 Global Technical Activities

Due to the complexity and scope of FI-WARE‘s vision and objectives project-level coordination and direction of some key technical activities is critical for the success of the project. The transversal work package (WP2) "Global Technical Activities" focuses on global technical activities such as analysis and consolidation of requirements requested by FI-WARE's stakeholders, high level architecture, Core Platform roadmap, open calls coordination.

All these technical coordination activities will be performed in close cooperation with all the research and development work packages (WP3-WP8). Specific WP2 resources assigned to representatives of the research and development WPs (WP3-WP8) will allow the execution of these coordination activities and the generation of the global consolidated results, both driving and drawing upon the expertise and resources of the development WPs.

Requirements specification will be a key activity in constructing the FI-WARE platform and revision/refinement of requirement specifications will take place continuously through all the sprints planned during development of reference implementations of FI-WARE Generic Enablers (GEs).

The realization of the FI-WARE vision and objectives through the concept of Generic Enablers will require a carefully designed global architecture where the role of each GE and the interfaces between GEs as well as the interfaces exported by GEs to the users of FI-WARE are properly defined.

In order to fulfil the FI-WARE promise all Generic Enablers will be accompanied by Open Specifications that will facilitate usage and integration in any FI-WARE Instance as well as the development of compliant implementations of GEs by third parties. While GE Specifications themselves will be done inside WP3-WP10, overall coordination and consolidation of these specifications is part of this work package.

Structure of this Document

The document is generated out of a set of documents provided in the public FI-WARE wiki. For the current version of the documents, please visit the public wiki at http://wiki.fi-ware.eu/

The following resources were used to generate this document:

D.2.3.2 FI-WARE Architecture WP4 contribution front page
Cloud Hosting Architecture

Typographical Conventions

Starting with October 2012 the FI-WARE project improved the quality and streamlined the submission process for deliverables, generated out of our wikis. The project is currently working on the migration of as many deliverables as possible towards the new system.

This document is rendered with semi-automatic scripts out of a MediaWiki system operated by the FI-WARE consortium.

Links within this document

The links within this document point towards the wiki where the content was rendered from. You can browse these links in order to find the "current" status of the particular content.

Due to technical reasons part of the links contained in the deliverables generated from wiki pages cannot be rendered to fully working links. This happens for instance when a wiki page references a section within the same wiki page (but there are other cases). In such scenarios we preserve a link for readability purposes but this points to an explanatory page, not the original target page.

In such cases where you find links that do not actually point to the original location, we encourage you to visit the source pages to get all the source information in its original form. Most of the links are however correct and this impacts a small fraction of those in our deliverables.


Figures are mainly inserted within the wiki as the following one:


Only if the wiki-page uses this format, the related caption is applied on the printed document. As currently this format is not used consistently within the wiki, please understand that the rendered pages have different caption layouts and different caption formats in general. Due to technical reasons the caption can't be numbered automatically.

Sample software code

Sample API-calls may be inserted like the following one.



The current document has been elaborated using a number of collaborative tools, with the participation of Working Package Leaders and Architects as well as those partners in their teams they have decided to involve.

Keyword list

FI-WARE, PPP, Architecture Board, Living Lab, OIL, Steering Board, Roadmap, Reference Architecture, Generic Enabler, Open Specifications, I2ND, Cloud, IoT, Data/Context Management, Applications/Services Ecosystem, Delivery Framework , Security, Developers Community and Tools, ICT, es.Internet, Latin American Platforms, Cloud Edge, Cloud Proxy.

Changes History

Release Major changes description Date Editor
v1 First draft of deliverable structure 2013-03-03 TID
v2 First consolidated review draft 2013-03-10 IBM
v3 Updated following first peer review 2013-03-24 IBM
v4 Updated following second peer review 2013-04-16 IBM

Table of Contents

FIWARE WIKI editorial remark:
In the final deliverable, somebody would include the TOC here
Personal tools
Create a book