News Feed
Forgot your password?
New user?
WP8 Trusted Application Infrastructure
TAS3_D8p1_v1p0.pdf
Software Documentation System: Repository services - Accepted by European Commission in June 2009. Executive Summary: This document provides the description of ‘Repository Services’ – a component of the TAS3 Trusted Application Infrastructure. Repositories are needed in TAS3 to store personal identifying information. Moreover, they need to be able to also store so called ‘Sticky Policies’ with those data items. The TAS3 Trusted Application Infrastructure is the application dependent part of the TAS3 infrastructure. Its purpose is to provide the services needed to realize the pilots of WP9 in the fields of employability and eHealth. The TAS3 Trusted Application Infrastructure depends on the requirements collected in WP1, the architecture design provided by WP2 and the business process models developed in WP3. It allows the application independent services developed in WP4, WP5 and WP7 to be used in the WP9 pilots. Most of the concrete technical solutions in this deliverable are inherited from deliverable 4.2. [1], which has a more generic view on Repositories. Within the TAS3 Trusted Application Infrastructure the ‘Repository Services’ component serves to store, protect and deliver PII1 (Asset Banks). This document describes • The Conceptual model - the assumptions on which the development of ‘Repository Services’ is based. • An evaluation of existing Open Source repositories and a description for a chosen TAS3 reference repository. • The services provided by ‘Repository Services’ and a description of its architecture. • Plans for the further development of the services in the next phase of the TAS3 project. NOTE: The software components produced in WP 8 implement application specific adaptors that are required to use the application independent TAS3 infrastructure in the TAS3 pilots in eHealth and eEmployability. The overall architecture, semantically enriched executable business process models with an XForms user interface and the design of the core TAS3 services are the pre-requisites for WP8. The TAS3 architecture has been finalized only recently (see D2.1). While all our results are consistent with and usable for the current TAS3 architecture it cannot be a surprise that some alignments and refinements will be required. Moreover new service needs, for example the request for a service bus, are emerging from the architecture document, which still need to be detailed before they can be implemented and documented in any of the deliverables of WP8. Technical Note: All produced components (web services, libraries and clients) of Deliverables D8.1., D8.2. and D8.3. can be found in a binary version at this location: http://citrix.uni-koblenz.de:9000/homepage/tas3/default.aspx Readers Guide To help the reader of this document to better understand its contents together with the other two deliverables of WP8 (especially Deliverable D8.2.), we provide this readers guide. Deliverables D8.2. is based on this deliverable D8.1. D8.1. has many references to D8.2., because D8.2. describes services that extend the repository services described in this document. Section 2 in D8.1. is the section that contains the conceptual model for TAS3 repositories. This conceptual model is then filled with flesh by section 4 and 5 from this document and section 2 in deliverable D8.2. The reader can use section 2 in D8.1. as a starting point for reading deliverable D8.1. and D8.2. Section 6 (applied software engineering methods) in this deliverable is optional and in an initial state, but we decided to leave it in the document, because this document is a software documentation and we have to document our applied software engineering methods.
TAS3_D8p2_v1p0.pdf
Software Documentation System: Back Office Services - Accepted by European Commission in June 2009. Executive Summary: This document provides the description of the back office services These services neither store person related data nor serve the user directly. They provide ontologies and metadata, perform search and aggregation operations and transform data into specific formats. Task T8.3 contributes to this deliverable. The back office services are a component of the TAS3 Trusted Application Infrastructure but not of the core TAS3 Trust and Security Infrastructure. This document describes in particular • The Generic Data Format used to store data in TAS3 repositories • Services to transform data from the IMS ePortfolio format to the Generic Data Format and from the Generic Data Format to the Europass CV Data Format. • Aggregation Service and Policy Aggregation • A Request Logger Service to store information on requests issued and responses received by TAS3 web services for rapid prototyping and debugging purposes The TAS3 Trusted Application Infrastructure is the application dependent part of the TAS3 infrastructure. Its purpose is to provide the services needed to guide the implementation of the pilots of WP9 in the fields of employability and eHealth. The TAS3 Trusted Application Infrastructure depends on the requirements collected in WP1, the architecture design provided by WP2 and the business process models developed in WP3. It allows the application independent services developed in WP4, WP5 and WP7 to be used in the WP9 pilots. Within the TAS3 Trusted Application Infrastructure the back office components serve as parts of the Application Dependent Policy Enforcement Points of service providers and service requesters or as stand-alone components. This document describes • the assumptions on which the development of back office services is based • the services provided • the high level architecture of the services • installation and usage of the services • limitations and known issues • plans for the further development of the back office services in the next phase of the TAS3 project.
TAS3_D8p3_v1p2.pdf
Client / Intalio Service Requester ADPEP - Accepted by European Commission in June 2009. Executive Summary: This document provides the description of the client side of the TAS3 Trusted Architecture for Securely Shared Services and its connection to the core components of the infrastructure (the TAS3 stack). The client side is also called the ServiceRequester side and the connection from the client to the TAS3 stack is called the ServiceRequester ADPEP (Application Dependent Policy Enforcement Point). As well as the general concepts for a ServiceRequester ADPEP also the first implementation of a ServiceRequester ADPEP specific adapted for Intalio|BPMS (Intalio ServiceRequester ADPEP) is presented. By using the ServiceRequester ADPEP the Intalio|BPMS and the connected web browser provide the functionality of a TAS3-client for uploading and retrieving data from a TAS3 ServiceProvider. Actually the ServiceRequester ADPEP and the Intalio ServiceRequester ADPEP do not cover security functions. The ServiceRequester ADPEP in general is the application dependent part of the TAS3 infrastructure on the “ServiceRequester side”. Its purpose is to provide functions to connect the client-application to the TAS3 infrastructure for uploading and retrieving data. These functions are needed to realize the pilots of WP9 (Employability and Healthcare Demonstration) in the fields of employability and eHealth. The TAS3 Trusted Application Infrastructure depends on the requirements collected in WP1 (Requirements Analysis), the architecture design provided by WP2 (Framework, Architecture and Semantics) and the secured business process models developed in WP3 (Securely Adaptable Business Processes) in conjunction with WP9. It allows the application independent services developed in WP4 (Information Protection), WP5 (Trust Policy Management) and WP7 (IDIJ Authentication Authorization) to be used in the WP9 pilots. As technical basis for the demonstrators the Intalio|Designer and Intalio|BPMS from the project partner Intalio is used. Therefore the first implementation of a ServiceRequester ADPEP is created for the Intalio|BPMS and is called the ‘Intalio ServiceRequester ADPEP’. A short description of the Intalio|Designer and the Intalio|BPMS is provided in the deliverable D3.1. Within the TAS3 trusted application infrastructure the ADPEP-components provide the application dependent connection from the ServiceRequester and the ServiceProvider to the core components of the TAS3-infrastructure. Therefore two different types of ADPEPs were designed: the ServiceRequester ADPEP (described in this document) at the ServiceRequester side and the ServiceResponder ADPEP (described in the deliverable D8.1) at the ServiceProvider side. Later on in this document the term ADPEP is used for the ServiceRequester ADPEP. This document describes: • the assumptions on which the development of the ServiceRequester ADPEPcomponent is based • the functions provided by ServiceRequester ADPEP • the architecture of ServiceRequester ADEP • the first implementation of a ServiceRequester ADPEP for Intalio|BPMS (Intalio ServiceRequester ADPEP) • limitations and known issues • Roadmap for future releases of the component (ServiceRequester ADPEP / Intalio ServiceRequester ADPEP / Intalio|BPMS, Clients) in the next phases of the TAS3 project.
