Abstract
This deliverable describes how components of SPIKE Portal, SPIKE Semantic Bus and Security subsystems developed in the previous tasks were finally integrated into the SPIKE system. First release of the integrated system was prepared for the Trial 2, and then it was gradually revised during the Trial 2 testing towards the second final release. The main part of the report deals with the integration of user interface and external applications in SPIKE portal, integration of Human Task Environment, integration of security subsystem and integration of Semantic Manager.
Executive Summary
This deliverable is the last document in the list of D4.x, D5.x, D7.x deliverables, which all describe development process from the specification of the system, through the implementation of components to the last phase – software integration described in this deliverable.
The document gives a short and high-level overview of the major changes during the integration phase. It serves as a written report, mainly accompanying the first release of the SPIKE integrated system prepared for Trial 2 (D8.1a) and second release with updates/bug fixes prepared after the Trial 2 testing (D8.1b). More consolidated documentation with the description of the overall SPIKE architecture is provided in [D8.2a] deliverable.
During the integration phase of the software development, the main goal was to integrate components of all SPIKE subsystems (i.e. SPIKE Portal described in D4.x reports, SPIKE Service Bus described in D5.x reports and Security sub-system described in D7.x reports) into the integrated software. The main contributions of this deliverable are therefore:
-Integration of user interface in the SPIKE portal, which consists of the Alliance Manager portlet, Human Task Environment portlets and a set of dedicated portlets for integration of external applications using various protocols
-Integration of SPIKE portal with the SPIKE service bus through the integration between service and portal part of the Human Task Environment (HTE)
of security mechanism for services not accessible by URL
-Integration of Semantic Manager with Alliance Manager in order to support discovery of services relevant for the creation of new alliances
-Integration of Content Manager with Alliance Manager in order to persist alliances and their contracts for usage of services by alliance member organizations
Download
You can download a short version of this document here:
In order to obtain the full content of this document, please use the contact form below:
