Home

D6.32 - bivee

1. eo Bivee xsi type xs string gt Acme Inc saml2 AttributeValue saml2 Attribute lt saml2 Attribute Name BIVEE VirtualOrganization lt saml2 AttributeValue xmlns xs http www w3 0rg 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance xsi type xs string gt Acme Inc saml2 AttributeValue saml2 Attribute saml2 Attribute Name Role saml2 AttributeValue xmlns xs http www w3 org 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance xsi type xs string gt BIVEE User saml2 AttributeValue saml2 AttributeValue xmlns xs http www w3 org 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance xsi type xs string gt PIKR User lt saml2 AttributeValue gt saml2 Attribute saml2 Attribute saml2 AttributeStatement saml2 Assertion SSO Service Installation prerequisites The prerequisites for installing the SSO Service components are JA J2EE servlet container version 6 or later the prototype has been tested on Apache Tomcat 7 The URL of the LSA Service endpoint and the corresponding authority name to identify and configure the related Authentication Handler Installation instructions The SSO Server web application can be downloaded from http bivee eng it 8780 web guest documents document library view 43585 path BIVEE Project Portal Document Library WP6 Architecture IT Platforms federation and s
2. lt LongDescription gt AIDIMA is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt lt Members gt lt MemberName gt Calilac S A lt MemberName gt lt MemberName gt Coala lt MemberName gt lt MemberName gt Ferrocuesta S L lt MemberName gt lt MemberName gt Lasientu lt MemberName gt lt MemberName gt Mazzaro Giulio S R L lt MemberName gt lt MemberName gt Muebles Romero SA lt MemberName gt lt MemberName gt Recubrimientos Vecoal S L lt MemberName gt lt Members gt lt VirtualEnterprise gt lt VirtualEnterprise gt lt Name gt LOCCIONI lt Name gt lt ShortDescription gt ENERGY ENVIRONMENT HOME HUMANCARE amp MOBILITY SOLUTIONS lt ShortDescription gt lt Members gt lt Members gt lt VirtualEnterprise gt lt VirtualEnteprises gt Verb URI Description tr v1 ves ve name retrieve details of given VE Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 ves AIDIMA Output lt VirtualEnteprises gt VirtualEnterprise lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INST
3. Instances Person Data Storage LEV VIRTUALENTERPR SE mee d mte Enn ess LEV ENTERPRISE ACME ACME1 Figure 20 Example of how ontology concept instances are mapped to database records Page 30 of 76 Qo Bog Bivee fem fan an fem i ZA CS f 04 7e d FEIE erm a 40 Lil G 1 ui i N 4 N i N B N B N n B E n E B E 7 Z E TA T r CA Hadda Figure 22 DB schema of the RDH DS Catalogue Page 31 of 76 AO Bivee 4 4 3 RDH WS The RDH module exposes a web API RDH WS used by external systems to load KPI data in RDH DS and by RDH FE to provide KPI data navigation and administration functionality to BIVEE Platform users RDH WS is implemented as a HTTP SOAP web service which exposes a set of operations e Retrieve all the existing KPI definitions e Retrieve all the dimensions and dimension levels for a specific KPI definition e Retrieve all the values stored for a specific KPI e Load update delete values for a specific KPI A formal WSDL based definition of this API is given in Annex D Raw Data Handler Factsheet 4 4 4 RDH FE The RDH module also provides a web based front end UI RDH FE which is an integral part of the BIVEE Platform It enables users to navigate and manage the KPI historical data maintained in RDH DS All the operations provided by RDH WS see 4 4 3 are exposed by RDH FE
4. novating novation BIVEE Environment Prototype v2 0 OG prg Bivee EXECUTIVE SUMMARY The objective of WP6 is to design and build the integrated BIVEE Environment consisting of the BIVEE Platform prototype also in the scope of WP6 and of several BIVEE Application prototypes that are the outcome of WP3 WP4 and WP5 This deliverable is the prototype release of the BIVEE Platform v2 0 and the prototype integration of the Mission Control Room v1 0 D3 21 of the Virtual Innovation Factory v1 0 D4 21 and of the Production amp Innovation Knowledge Repository D5 1 D5 2 D5 3 Section 1 gives a functional overview of the BIVEE Environment and describes the achievements obtained since the previous release of the prototype Section 2 deals with the technical architecture of the BIVEE Environment and with integration of BIVEE Applications and of the BIVEE Platform Section 3 shows the big picture of BIVEE Environment use cases Section 4 describes each single module of the BIVEE Platform in detail from the architectural and technical points of view Section 5 is a user guide providing actual screenshots of the BIVEE Platform and to a minor extent of the linked BIVEE Applications Section 6 lists references to external sources Finally four annexes provide the technical facts links to implementation to source code installation instructions etc for the BIVEE Platform modules that are released as part of this de
5. WEB PORTAL FACTSHEET seeneresnvnnnsenevenesenenenennnnnnnsnnnnsnnnsnnenenenenenenensnnnnnsnnnnsnnnsnnenenenene 57 ANNEX B SINGLE SIGN ON FACTSHEET sese esse sese nnn nenen nenn enen nnn 59 SRI 60 SSO Client c 61 ANNEX C VIRTUAL ENTERPRISE MANAGEMENT FACTSHEET esesronevnnnennnnnnnnnnenenenensnnnsnnnsnnnnnnnnnnnnnnnenene 62 ANNEX D RAW DATA HANDLER FACTSHEET eoonononnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnenenensnnnnnnnnnn nenee 70 Page 5 of 76 OG prg Bivee INDEX OF FIGURES Figure 1 BIVEE Environment Overview sese ee eee eee ee eee eee eee eee eee 8 Figure 2 Example deployment of a BIVEE Environment Instance eee eee ee eee eee eee 10 Figure 3 BIVEE Platform API overview sese ee ee eee 11 Figure 4 Synchronization of PIKRand MCR for Model Annotation esses 12 Figure 5 Partner Search during VE Creation in MCR Modeller sese 13 Figure 6 Document and Knowledge Resource Retrieval in MCR Assistant 14 Figure 7 Synchronization of MCR and PIKR for KPI Visulaisation eese 14 Figure 8 Exposing Conceptual Models to VIF Whiteboard in order to take Comments Suggestions and Annotations excerpt from Gl sss 15 Figure 9 Integrated components from the VIF side 16 Figure 10 PIKR services consumed by
6. pil bared gt pene a Bt rten I ua g P orm dum gi te ua ut M vm e men Reveardtletury Page 40 of 76 OG Bivee Information Society 5 5 7 Sub menu entry Whiteboards Bivee Innovating Innovation 5 5 8 Sub menu entry Admin QO Bivee Innovating Innovation Page 41 of 76 RO Bivee 5 6 Menu entry PIKR This menu entry links to the landing page of the Production and Innovation Knowledge Repository PIKR which runs as a standalone application i e integrated with the SSO Service but not with the Web Portal For this reason no screenshot is provided here see PIKR s own documentation 4 for the user manual In the last release of the BIVEE Environment full Ul integration will be achieved This menu entry is accessible only to users holding any of these roles PIKR User BIVEE_Ecosystem_Admin BIVEE_Admin Page 42 of 76 OG Bivee Information Society lov ete T 5 7 Menu entry KPI This is the entry point for RDH FE i e the web based front end of the Raw Data Handler module RDH FE base functionality read is available to authenticated users having any role while some privileged operation write are enabled only for users having one of these roles BIVEE KPI Admin BIVEE Ecosystem Admin BIVEE Admin The landing page displays the list of KPI definitions for which data exists in the Data Store RDH DS Description HOUUU
7. 76 Q Bivee 2 2 Mission Control Room integration The first prototype of MCR provides a set of web methods in the Component API and Semantic Modelling Kernel SMK in order to enable interactions of the other two BIVEE macro blocks VIF and PIKR the BIVEE Platform itself and the third parties with the MCR see details in 6 Furthermore during the ongoing implementation of the second prototype of MCR within the task T3 2 integration scenarios in following three fields have been concretized in order to realize interaction with BIVEE macro blocks BIVEE Platform and third parties e Integration between MCR and PIKR e Integration between MCR and VIF e Integration between MCR BIVEE Platform and third parties 2 2 1 Integration between MCR and PIKR Integration work between MCR and PIKR concentrates on following scenarios e Synchronization of the PIKR and the MCR for Model Annotation e Partner Search during VE Creation in the MCR Modeller e Document and Knowledge Resource Retrieval in the MCR Assistant e Synchronization of the MCR and the PIKR for the KPI Visualisation Synchronization of the PIKR and the MCR for Model Annotation The idea in this scenario is based on the semantic lifting approach as described in 11 and 12 and its scenarios that have been detailed in 6 The scenario aims to synchronize the domain ontologies as concept lists within the MCR environment for annotation of modelling constructs using domain
8. Apache License Version 2 0 MySQL is distributed under the GPL License Page 69 of 76 Bivee ANNEX D RAW DATA HANDLER FACTSHEET Prototype references Version 1e http bivee sp eng it Availability Source control Mauro Isaja mauro isaja eng it Contact person Prototype technical information hrs Web Application Programming Java Language Development Java SE Development Kit 1 6 or later Framework Additional libraries Spring Framework 4 0 0 Axis 2 1 6 2 Application Server J2EE servlet container tested on Apache Tomcat 7 Database MySQL v5 1 or later RDH WS API documentation The formal WSDL definition of the RDH WS API can be downloaded at bivee sp eng it 8280 RDH WS services RDHService wsdl The RDH WS Web Service exposes the following operations v getAllKpi Input parameters not required Output parameters array of 0 N Dscindicator where DscIndicator is a complex structure Dscindicator definedBy string Name of the person that defined the KPI hasTimeDimension string indicates if the KPI has the TIME dimension Page 70 of 76 svn repo nimbus ware com BIVEE WP6 D6 32 trunk RDH WS RO Bivee indClass string KPI class indDescr string KPI description indName string KPI name rdhNormName string KPI normalized name unitOfMeasure string unit of measure of the KPI v getAllKpiValues Input parameters indicatorName s
9. Businfzs a Innovation n fatal Enterprise Environments 5 Ko 9 E SBusiness oprocess Customer SMission amp SCollaborate Performance v Semantic Management S OM dell Indicators v c VD odelling supplier c gt vOriginality imagination S 9 Problems improvement EE g reg sove INNOVATION 25 Integration Sa Satisfactionog lt BIVEES nv vironment 2 O Progress SIE Success a Virtual ity eposito Standards2 Factory 5 8 Contributelngenuity trols Phases Production ata S lt Waves Inven G AE SEVENTH FRAMEWORK PROGRAMME
10. CL COST AMAF OF DEA ELIS Ser JAN CH INVE MEN Figure 25 RDH FE landing page The user can browse stored data for any KPI by clicking on the x icon of the corresponding row The page will then display the list of all the historical data sequences that are available for the given KPI Innovating Innovation Home Mission Contro Room Virtual In Selected KPI KPI lt P ROLIG ORGANIZATIONDIMENSTON_VINTUALENTERD ORGANIZATIONDIMENSION_ENTERPR 4 ORGANIZATIONDIMENSLON DEPARTMENT ADIMA Fotoeues a SL Lula ADMA P aaun lt SL hrorrskobToul ADIMA Foroeues a S L ADIMA P taw S ADINA Mazzaro Give SAL Anita Massaro i se RAJ zwi pel p Figure 26 RDH FE KPI data Page 43 of 76 OP Bivee Information Society rard From here the user can browse an historical value sequence by clicking on the QI icon of the corresponding row The page will then display the list of all values stored for the given sequence RPL Salectoy Misery Selection KFI 4P RC IG hei Fabro AIDIVA Entererse eToouerta SL Figure 27 RDH FE KPI value sequence On each row any user holding the appropriate rights BIVEE KPI Admin BIVEE Ecosystem Admin or BIVEE Admin role can either delete Xor modify S the corresponding KPI value The same privileged user can from the KPI data page start a totally new KPI value sequence by clicking on the Insert button This displays an input form where the u
11. It has to be configured according to Jasig s instructions by replacing the URL of the CAS Server with the URL of the deployed SSO Server instance Licensing information All third party software is also open source in particular Jasig s CAS Central Authentication Service see http www jasig org cas license Page 61 of 76 20 Bivee ANNEX C VIRTUAL ENTERPRISE MANAGEMENT FACTSHEET Prototype references http bivee sp eng it Availability Gre onto svn repo nimbus ware com BIVEE WP6 D6 32 trunk VER Contact person Mauro Isaja mauro isaja eng it Prototype technical information Nature Web Application Programming Java Language Development Java SE Development Kit 1 6 or later Framework Additional libraries Liferay Community Edition v 6 Vaadin 7 1 0 MyBatis 3 1 1 Application Server J2EE servlet container tested on Apache Tomcat 7 Database MySQL v5 1 or later other relational DBs should work VEM WS API documentation Verb URI Description tr v1 ves retrieve list of all VEs Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 ves Output lt VirtualEnteprises gt lt VirtualEnterprise gt lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INSTITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt Page 62 of 76 AO Bivee
12. VIF will extend the profile of each user to meet specific needs such as e Roles and permissions within the VIF e Detailed skills e Etc 2 4 Production and Innovation Knowledge Repository integration The PIKR implements a collection of interfaces jointly referred to as PIKR Connector see Deliverable D5 2 realizing a bridge on the ontology based structures defined in the PIKR and the data structures adopted by the other BIVEE components In the application scenarios considered so far the PIKR acts mainly as a back end module providing services to the BIVEE front end realized by the VIF and MCR Please refer to Deliverable D5 2 Chapter 5 and 6 fora discussion regarding the approach followed for the ontology based lifting of the informative resources pertaining to both the Business Innovation Space and the Value Production Space The main API implemented by the Connector can be grouped as follows Accessing to the Domain Specific Ontologies in order to retrieve domain concepts and related information to be used for the annotation tagging of resources Management of the Semantic Descriptors in order to operate on the PIKR Knowledge Base for storing modifying retrieving the semantic representation of informative resources e g models created in the MCR documents edited in the VIF Exporting fragments of the PIKR Knowledge base by a suitable conversion or transformation e g retrieve the form for describing a given document e
13. all changes are discarded and the dialog window is closed From the main page the user can create a new VE by clicking on the Insert VE button Page 46 of 76 Information Society Bivee Innovating Innovation ADD NEW VIRTUAL ENTERPRISE Namo CLUICNE Short description kY SMARDNPEN FUME HUMANGARE amp MCEILI Y EULUT UNS Long description Figure 31 VEM FE new VE dialog window The user has to insert a VE name which has to be unique and not exceeding 50 characters in length A short max 255 characters and a long max 1000 characters description may also optionally be provided When done the user has to click on the Save button to insert the new VE in the registry By clicking on the Cancel button the dialog window is closed without any change 5 8 2 Sub menu entry RDH Synchronization The RDH Synchronization functionality is available only to users having the BIVEE Admin role i e BIVEE Platform administrators When the user select this menu item the system will ask for confirmation with a confirm cancel dialog window In case of confirmation the system will execute the RDH Sync program in the background meaning that RDH DS structure and partially contents will be synchronized with the current state of PIKR s KPlOnto ontology without any further user interaction and providing no feedback during the process It is worth noting that this functionality may have adverse effects on existin
14. allows interoperability between different infrastructures software business partners enabling the creation of an application platform based on a single shared authentication process SAML supports the interaction between the following entities e Principal generic person who actively participates in the process of authentication or authorization uniquely identifiable by the system using a profile that collects information about her e Identity Provider also called SAML Authority or Asserting Party keeps track of the credentials of the Principal and provides the associated information In the most general sense a SAML Authority is considered as an entity capable of responding to requests made through the SAML protocol e Service Provider also called Relying Party represents the entity that receives the information on a Principal released by the Identity Provider SAML has mechanisms that allow the service provider to check the validity of this information SAML is based on the concept of assertions An assertion is the reply to a question made by a Service Provider to a SAML Authority The Service Provider requests and obtains an identity 7 SAML http saml xml org Page 23 of 76 eO Bivee assertion from the Identity Provider On the basis of this assertion the Service Provider can make an access control decision in other words it can decide whether or not to service a request from the connected Principal Befor
15. architectural view of the BIVEE Environment Figure 1 BIVEE Environment overview Page 8 of 76 RO Bivee 1 2 Achievements with respect to the previous release This deliverable builds upon the M12 issue D6 31 which released the first version of the BIVEE Platform with no integrated BIVEE Environment at that time the only BIVEE Application released being PIKR D5 1 M8 In order to include MCR VIF and PIKR the Liferay web portal on which the BIVEE Platform is based see section 4 1 was extended with a Single Sign On SSO implementation providing the central authentication and attribute release services required in order to run several distinct web applications together in a seamless way The SSO service was developed from a de facto standard open source implementation Jasig CAS but innovative BIVEE functionality was also added that enable the federation of multiple BIVEE Environment instances into a single business ecosystem without the need for a centralized user administration see section 4 2 for details BIVEE Applications that were released as standalone applications by M22 MCR and VIF were embedded into the web portal Their web front ends were decomposed into functional modules which can be navigated through the common BIVEE Environment menu Moreover they were integrated with the SSO service Finally a first step towards look amp feel harmonization was taken by applying some common BIVEE style elemen
16. as interactive functionalities See the user manual of this sub module section O for screenshots and details 4 4 5 RDH Sync RDH Sync is an utility program that keeps RDH DS schema aligned with KPIOnto leveraging on the PIKR web API to retrieve KPlOnto It has to run once when the BIVEE Platform is installed and then each time KPlOnto is modified RDH Sync tries to avoid the disruption or the loss of stored data whenever possible but there are operations that may generate loss of historical data or that may cause a data integrity violation problem In particular loss of historical data may be caused by e the removal of an existing indicator because of the dropping of the corresponding fact table e the removal of a dimension for an existing indicator because of the removing of the corresponding columns from the fact table e the removal of a level for dimension because of the removing of the corresponding column from all the fact table where the column were present Data integrity violation problems may occur when e adding a new dimension to an existing indicator e removing an existing dimension instance This sub module is activated interactively by the user by means of a menu entry in the RDH FE web UI see section 5 8 Page 32 of 76 eo Bivee Information Society loc etiez 5 BIVEE PLATFORM USER GUIDE 5 1 Login to the Web Portal The user loads the Web Portal URL in her web browser the Portal s ho
17. concepts MCR MODELLER PIKR e g Production Process Model y Ea Domain Ontology ZOMMH LL lt NisAnnotated CreateArtefact Domain Ontology Samantic Trancit Samantic Transit LESS n ri CreateArtefact CreateArtefact in Ontology Figure 4 Synchronization of PIKRand MCR for Model Annotation In order to realize the idea in ongoing implementation of MCR prototype V2 0 within the T3 2 a functionality has been developed which runs every 24 hours as a cron job to compare and synchronize the bases and automatically creates a semantic transit model for each ontology The semantic transit model includes related domain concepts in form of concepts a modelling Page 12 of 76 eo Bivee construct specified for semantic transit model see details in 11 As depicted in Figure 4 the cron job basically utilize the services from PIKR in order to look up the domain ontologies and applies web method createArtefact from the MCR Component API in order to create semantic transit models with related concepts in model repository within the MCR Partner Search during VE Creation in the MCR Modeller The idea is to use PIKR during VE design creation to find and select appropriate partners for the definition of the VE for certain process activities product features based on the annotation with the concepts imported from PIKR as described in
18. file liferay portal 6 1 1 ce ga2 bivee tomcat 7 0 27 webapps ROOT WEB INF classes portal ext properties must be edited changing the following properties appropriately Page 57 of 76 RO Bivee Property name Value jdbc url JDBC URL of MySQL instance including hostname and port on which MySQL is installed as well as database name in the format below jdbc mysql HOSTNAME PORT DB_NAME jdbc username Username of MySQL user with read write access to database jdbc password Password of MySQL user To start the Web Portal launch the startup file which is in the directory tomcat 7 0 27 bin of the folder liferay portal 6 1 1 ce qa2 bivee Licensing information All software developed is open source and under the Apache License Version 2 0 All third party software is also open source in particular Liferay Portal Community Edition is distributed under the GNU Lesser General Public License version 2 1 MySQL is distributed under the GPL License Page 58 of 76 EE Information Society eO Bivee ANNEX B SiNGLE SIGN ON FACTSHEET Prototype references Version 1e http bivee sp eng it Availability svn repo nimbus ware com BIVEE WP6 D6 32 trunk SSO Source control Contact person Mauro Isaja mauro isaja eng it Prototype technical information Nature Web Application Programming Java Language Development Java SE Development Kit 1 6 or lat
19. gt Lasientu lt MemberName gt lt VirtualEnterprises gt lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INSTITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt lt LongDescription gt AIDIMA is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt lt VirtualEnterprises gt lt EnterpriseMember gt lt Members gt Page 65 of 76 Verb URI Description v1 direct members mb namel ves uid username lsame as above without SSO login user amp pwd password credentials registered on property file Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 members Lasientu ves uid user amp pwd password Output lt Members gt lt EnterpriseMember gt lt MemberName gt Lasientu lt MemberName gt lt VirtualEnterprises gt lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INSTITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt lt LongDescription gt AIDIMA is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope
20. is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt lt VirtualEnterprises gt lt EnterpriseMember gt lt Members gt Verb URI Description pur v1 ves ve name create new VE Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 ves LOCCIONI lt VirtualEnterprise gt lt ShortDescription gt ENERGY ENVIRONMENT HOME HUMANCARE amp MOBILITY SOLUTIONS lt ShortDescription gt lt LongDescription gt lt LongDescription gt lt Members gt lt Members gt lt VirtualEnterprise gt Page 66 of 76 OG Bivee Verb URI Description Post v1 ves update given VE descriptions only Input http HOSTNAME PORT VirtualEnterpriseManager_rest rest v1 ves lt VirtualEnterprise gt lt Name gt LOCCIONI lt Name gt lt ShortDescription gt ENERGY ENVIRONMENT HOME HUMANCARE amp MOBILITY SOLUTIONS lt ShortDescription gt lt LongDescription gt lt LongDescription gt lt VirtualEnterprise gt Verb URI Description DELETE v1 ves ve name delete given VE cascade on members Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpr
21. is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt lt VirtualEnterprises gt lt EnterpriseMember gt lt EnterpriseMember gt lt MemberName gt Coala lt MemberName gt lt VirtualEnterprises gt lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INSTITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt lt LongDescription gt AIDIMA is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt Page 64 of 76 AO Bivee lt VirtualEnterprises gt lt Members gt Verb URI Description retrieve list of all VE memberships for GET vi members mb namej ves given Enterprise Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 members Lasientu ves Output Members lt EnterpriseMember gt lt MemberName
22. maintaining a registry for Virtual Enterprises and their Enterprise members VEM WS VEM Web Service sub module of VEM exposing a web API for accessing the VE registry VEM FE VEM Front end sub module of VEM integrated into the BIVEE Platform implementing a web based UI for navigating and managing the VE registry Page 7 of 76 OG Bivee Information Society lov erie 1 BIVEE ENVIRONMENT OVERVIEW 1 1 General Description The BIVEE Environment prototype is the first integrated release of the BIVEE Platform which includes the complete set of BIVEE Applications More specifically the following elements were integrated BIVEE Platform v2 0 D6 32 M24 issue this deliverable Mission Control Room MCR v1 0 D3 21 M22 issue Virtual Innovation Factory VIF v1 0 D4 21 M22 issue Production and Innovation Knowledge Repository PIKR v1 0 D5 1 M8 issue including o Advanced Data Adaptors D5 2 M21 issue o Advanced Interoperability Services D5 3 M21 issue The BIVEE Platform plays the role of integration enabler for BIVEE applications and services in several ways e Web portal and single sign on system e Common back end services VEM WS and RDH WS e Unified storage for raw performance indicator data RDH Data Storage Additionally the BIVEE Platform exposes its own front end for data and environment administration Figure 1 shows how all the above mentioned elements are related See also section 2 for an
23. v Top Level Organizations Delete Figure 43 Add USer Page 53 of 76 Kol EE L Infor mation Society Bivee ge It is then possible to fill the required fields with the desired values New User Back Details User Information No Virtual Organizations defined for this user Birthday Organizations Personal si Title Janay 1 Personal site v 1970 w Save Cancel Screen Name Required a ECTSystemAdministrator Gender Email Address Required Malo i ECTSystemAdministrator Job Title First Name Required ECTSystemAdministrator Middle Name Last Name Suffix Figure 44 New User basic data To associate the User with one or more role she holds inside the Web Portal click on the Roles item in the right column and select the desired Organizations click on Select button User Information Details Password Organizations ite User Groups Roles Personal site Categorization Identification Addresses Phone Numbers A nal Email r Websites Instant Messenger Social Network SMS OpenID Figure 45 User menu Roles Page 54 of 76 Q vi Information Society Bivee md To associate the User with the Organizations in which she is involved click on Organizations item in the right column and select the desired Organizations click on Select button When done click on the Save button to make changes persistent User Information Details Organizations Pe
24. A Service also interacts with Virtual Enterprise Management see section 4 3 Typically there is one single LSA Service instance in place for each BIVEE Platform installation In this very common configuration the LSA Service is a simple wrapper around Liferay s built in user repository Users Enterprises and Roles are those defined in Liferay and the LSA Service added value comes from its capability of merging these data with information from the Virtual Enterprise Management registry assigning Users to Virtual Enterprises as appropriate Regardless of this enhancement the context is still that of the traditional centralized approach to SSO as described in the introduction However the SSO module s distributed architecture also enables the federative paradigm Having multiple LSA Service instances governed by one single SSO Service means that you can configure e one BIVEE Environment with user data stored and managed by several different authorities like corporate users in LDAP or ActiveDirectory services see Figure 15 e multiple federated BIVEE Environments each running its own Liferay web portal e amixofthe above see Figure 16 This wide range of possible SSO configurations reflects on the flexibility of the BIVEE Environment itself which can be adapted to complex setups involving a variety of businesses and of business ecosystems Enterprise is the BIVEE equivalent of Organization in Liferay A User is vir
25. E WP6 D6 32 trunk WebPortal Mauro Isaja mauro isaja eng it Contact person Prototype technical information Nature Web Application Programming Java Language Development Java SE Development Kit 1 6 or later Framework Additional libraries Liferay Community Edition v 6 Application Server J2EE servlet container tested on Apache Tomcat 7 Database MySQL v5 1 or later Installation pre requisites The prerequisites for installing the Web Portal application are An operating system available with no specific constraints The application has been successfully installed and tested on Windows XP Enterprise Edition and Mac OS X A MySQL instance version 5 1 or later the application has been tested using MySQL Database engine however any database with a JDBC driver available should work Installation instructions The Web Portal Server application can be downloaded from http bivee eng it 8780 web guest documents document library view 43585 path BIVEE Project Portal Document Library WP6 Architecture IT Platforms federation and services Deliverables Final D6 32 The package D6 32_BIVEE Environment prototype M24 WebPortal zip must be unzipped it contains the folder iferay portal 6 1 1 ce ga2 bivee and the file bivee portal sql First of all a new database must be created using bivee portal sql which creates the schema with the portal configuration To configure database access the
26. INFORMATION 0050 sccesscsesecsesencesenderconsvessecenusvactnvaccresssndernensueacesenuevecsssctencessndensenseeass 3 TABLE OF CONTENTS fte 4 INDEX OF FIGURES REED EE SVS 6 GLOSSARY OF TERMS sssssssscscscssssessssssovsssssdeaescsssessessssseassssvevsacssdasesevesesencssssesssastecsesssdasesetevedsvedss 7 1 BIVEE ENVIRONMENT OVERVIEW saonnnnnnnnnnnnnnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnene 8 1 1 General Description TTT 8 1 2 Achievements with respect to the previous release ce eee eee 9 2 BIVEE ENVIRONMENT ARCHITECTURE eseserensnnnnnnnnnnnnnennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnenenenensnnnnnnnnnnnnnnnnnnnene 10 2 1 BIVEE Platform integration ccccccccccssssssssscccceeecsssssceseceeeeeessssenseseeeessesssseeseecenesesseenes 11 2 2 Mission Control Room Integration sese eee eee 12 2 2 1 Integration between MCR and PIR sss eee 12 2 2 2 Integration between MCR and VIE sese eee 15 2 2 3 Integration between MCR BIVEE Service Platform and Third Parties 15 2 3 Virtual Innovation Factory Integration eee eee eee eee 16 PME I HM 16 232 MCR T A 17 2 3 3 BIVEE PLATFORM P m 17 2 4 Production and Innovation Knowledge Repository Integration sese eee 18 3 BIVEE ENVIRONMEN
27. ITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt lt LongDescription gt AIDIMA is the Technology Institute on Furniture Wood Packaging and related industries It is a non for profit association and its scope is both national and international Although it was founded in November 1984 AIDIMA modified its statutes on July 1994 to open its membership and general assembly to packaging and transport companies lt LongDescription gt lt Members gt lt MemberName gt Calilac S A lt MemberName gt Page 63 of 76 lt MemberName gt Coala lt MemberName gt lt MemberName gt Ferrocuesta S L lt MemberName gt lt MemberName gt Lasientu lt MemberName gt lt MemberName gt Mazzaro Giulio S R L lt MemberName gt lt MemberName gt Muebles Romero SA lt MemberName gt lt MemberName gt Recubrimientos Vecoal S L lt MemberName gt lt Members gt lt VirtualEnterprise gt lt VirtualEnteprises gt Verb URI Description er v1 members retrieve list of all registered Enterprises Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 members Output Members EnterpriseMember lt MemberName gt Calilac S A lt MemberName gt lt VirtualEnterprises gt lt Name gt AIDIMA lt Name gt lt ShortDescription gt TECHNOLOGY INSTITUTE FURNITURE WOOD AND PACKAGING lt ShortDescription gt lt LongDescription gt AIDIMA
28. T USE CASES eerenennnnnnnnnnnnnnnnnenanensnenenansnnnnsnnnnnnnnnnnnenenensnenennnsnnnnnnnnnnnnnnnnnene 20 4 BIVEE PLATFORM MODULES s sssssza 21 4 1 Idcm HE 21 4 2 Sinple Sign OM 225 35 I 21 42 1 IEP O AUCTION ees E serte wernt lngten 21 4 2 2 Open technologies er dtt ete er Tere Use eV E vete Quee VEU NE eke 22 4 2 3 Architecture of the SSO module sees 24 4 2 4 SSO Service sub module sess enne 24 4 2 5 ESA Service sub module 5 iet EF a de el ee 25 4 2 6 BIVEE standard SSO attributes and roles sese eee eee eee eee 26 4 3 Virtual Enterprise Management sese eee eee eee eee eee 27 4 4 Raw Data Handler c 28 4 4 T Introduction aceti REOR sents Rue EUR ER eR TEES Pee SURE eue EE ree UE verae 29 RU R R 29 4 43 B c 32 uabslgdpeu dued 32 Page 4 of 76 QO LS Bivee KHU D a EN 32 5 BIVEE PLATFORM USER GUIDE sccsccicseccessscsessscsssctsessevseecisseccecsssaessssssecssesiveseectssecsessssasssssssecsses 33 S 1 Login to the Web Portal neni ten eee k aene EY M DDR EX eu e XN AER OE EY UA ER RR GR 33 3 2 BIVEE Platform mie Ur eios trit re oe nene Ent un SE eee ERR AERE veta HERR AERE Ax tiss 34 5 3 Menu entry HOME sausen ots caet se dncens coa e
29. VIE sese 17 Figure 11 MCR VIF whiteboard integration sese eee eee 17 Figure 12 Bivee Environment use case diagram sese esse eee eee 20 Figure 13 CAS authentication process ccsssccccccsssssssssseccccesessssssaeeeecesssesssaseeeeceessessseseeeseeess 23 Figure 14 SSO login sequence ccccccccccesssssssseeeccesssssssseeeeecesseseeaaeeeeeesseessaaaseeeeeesssessaaseeeeeeeess 24 Figure 15 Multiple LSA Services under a single SSO master sese eee 26 Figure 16 BIVEE Environment federation sese 26 Figure 17 Relationship of the RDH module with BIVEE components esee 28 Figure 18 Example of Dimension in KPlOnto sese eee eee 29 Figure 19 Example of how ontology concepts are mapped to database tables 30 Figure 20 Example of how ontology concept instances are mapped to database records 30 Figure 21 Example of DB schema involving two KPI fact tables seseeeeeeee 31 Figure 22 DB schema of the RDH DS Catalogue eee eee 31 Figure 23 Web Portal home page sees sees eee 33 Figure 24 Sign In Button 33 Figure 25 RDH FE landing page sse esse eee 43 Figure 26 RDH FE KPI data sese 43 Figure 27 RDH FE KPI value sequence sss eee eee eee eee 44 Figure 28 RDH FE insert KPI Value sese see eee 44 Figure 29 VEM FE landing page sse esse eee eee 45 Figure 30 VEM FE VE Details dialog window sss eee eee 46 Figure 31 VEM FE new VE dialog wi
30. a session timeout or a faked token the user is redirected to the CAS login page o If validation is successful the user finally receives the requested resource When a different web application is accessed by the same user the handshake sequence is started again but this time when the user reaches the CAS server she is recognized as authenticated she owns an active session on CAS so she does not go through the login form and is immediately directed back with a new authentication token From the user point of view this second handshake is totally transparent 7 http www jasig org cas Page 22 of 76 CAS Server AUTHENTICATION PROCESS 1 CLIENT REQUEST gt gt 2 AUTHENTICATION REDIRECT 3 TICKET FORWARDING 4 TICKET VALIDATION Web Browser TRANSMITTED DATA ICKET s ervice io gt c ooxie cas sso Application Server A UTHENTICATED ID Figure 13 CAS authentication process Security Assertion Markup Language Security Assertion Markup Language SAML is an open standard based on XML for the exchange of information between different entities during authentication and authorization operations It was developed by SSTC Security Services Technical Committee which belongs to OASIS Organization for the Advancement of Structured Information Standards The purpose of SAML is to provide a standard XML syntax to represent security assertions made by an IT system The SAML standard
31. are instances of the Indicator ontology class The other semantic concepts of relevance are the Dimension class and its sub classes These together with their concrete instances i e dimension members represent a standardized machine readable model of the real world from which KPI data originates Using this model as KPI meta data it is then possible to achieve a unified view of KPIs regardless of their original source and structure For instance a KPI may be defined in KPIOnto as supporting OrganizationDimension see Figure 18 which means that each single KPI value collected by the BIVEE system will have meta data attached describing how that value relates with standard BIVEE entities like Enterprise Department ProjectTeam etc Enterprise VirualEnt M ur iunc css istanceOf partOf Figure 18 Example of Dimension in KPlOnto This use of meta data is an example of semantic annotation In the RDH context it is implemented by storing KPI data collected from heterogeneous systems in ad hoc structures which can be easily matched back with concepts of the reference ontology This responsibility is on the Data Storage sub module RDH DS 4 4 2 RDH DS The RDH DS sub module is a relational database management system RDBMS with a specific schema in which KPI data is stored This data schema is actually auto generated by the RDH Sync utility see section 0 using KPlOnto as a blueprint so that his
32. as they are the foundation on which the BIVEE SSO solution is built Central Authentication Service Central Authentication Service CAS is an open source authentication system developed by Yale University Jasig which manages all authentication requests by means of a centralized server This solution is characterized by the following features Security o Passwords are never transmitted to applications o All tickets exchanged are encrypted Simple integration and portability o Several clients are available for free including libraries for Java Microsoft Net PHP Perl Apache Liferay Open source codebase The CAS authentication protocol is illustrated in Figure 13 and is briefly described here When the user first reaches a web application she is redirected to the CAS login page on a secure connection where she enters her username and password When user credentials are submitted CAS verifies them o If authentication fails the user receives an error page o f authentication is successful the user is redirected again to the originating web application this time carrying an authentication token from this point on CAS maintains an active user session to remember that this user has been authenticated The web application receives again the same user request but this time with an authentication token attached before granting access it validates the token with the CAS service o If validation fails the problem might be
33. atform is a web based portal assembling together an array of web based BIVEE Applications which leverage different technologies and may run on different nodes of the hosting network The unifying elements are a centralized or federated see section 4 2 3 authentication and attribute release system a standard user profiling schema a portal like container a set of Platform level services and to a lesser extent a common look amp feel across user interfaces Given this fabric and the stateless nature of all back end services in the BIVEE Environment both Platform level and Application level cloud deployment is a viable option with a minimum of extra effort any Application which is part of the Environment as well as the Platform itself can be virtualized and installed on high availability clusters The following deployment diagram illustrates this design with an example where each subsystem runs on its own node More complex cloud oriented setups are possible with the introduction of system level facilities like load balancers ad database clusters however these scenarios are out of the scope of this document lt exe u io1 environment gt Application Server 2 x xexecuton environment gt gt lt lt executon ewironment gt Database Server Application Server 1 x amp exezurion environment gt Application Server 3 xxexecttien snvironment gt gt Application Server 5 lt lt exe u 1017 environment gt Ap
34. dividuals of a given class KPI Key Performance Indicator numerical indicator used to express a performance measurement that is key to assess some process KPIOnto specific reference ontology which defines KPIs and their related concepts dimensions levels and entities level members in the scope of a given BIVEE Environment MCR Mission Control Room the BIVEE Application VIF Virtual Innovation Factory the BIVEE Application SSO Single Sign On general purpose authentication pattern where a centralized trusted service performs user authentication on behalf of one or more trusting applications LSA Local Security Authority specific BIVEE Environment concept denoting any system internal or external to the Environment which provides a credential verification service to the centralized SSO system RDH Raw Data Handler core module of the BIVEE Platform dealing with the collection of KPI data RDH DS RDH Data Storage sub module of RDH in charge of the storage of normalized KPI data RDH WS RDH Web Service sub module of RDH exposing a web API for accessing stored KPI data RDH FE RDH Front end sub module of RDH integrated into the BIVEE Platform implementing a web based UI for navigating and managing stored KPI data VE Virtual Enterprise temporary and dynamic association of Enterprises for the achievement of common business goals VEM Virtual Enterprise Management core module of the BIVEE Platform
35. e delivering the identity assertion to the Service Provider the Identity Provider may in turn request some information from the Principal such as a user name and a password in order to authenticate its identity In SAML one Identity Provider may provide SAML assertions to many Service Providers Conversely one Service Providers may rely on and trust assertions from many independent Identity Providers 4 2 3 Architecture of the SSO module The BIVEE SSO module is designed on top of CAS and SAML technologies BIVEE SSO introduces some new extension elements in the standard CAS architecture e The notion of VE and Enterprise as properties of the authenticated user which in the BIVEE context implies the integration with the VEM component see section 4 3 e An attribute release feature a SAML based way of passing additional user information to SSO clients e ABIVEE model for standard user attributes and roles see section 4 2 6 This architecture in implemented in two sub modules the SSO Service and the LSA Service which are described below from the functional point of view See Annex B Single Sign On Factsheet for detailed technical information 4 2 4 SSO Service sub module The SSO Service is a CAS instance customized to delegate user authentication and attribute release to a Local Security Authority LSA Service chosen from a registry The target LSA Service is identified from the credentials presented by users as demonstrated by
36. e it first To deactivate an User select it and press the Deactivate button or click on the Action button and then on Deactivate item Deactivate rime a Last Screen Job ij Ed gt Permissions O Giovanni T 9 Manage Pages 4 P Actions Showing 1 result amp Impersonate User Deactivate Figure 40 Deactivate User It is possible to get back a deactivated User through the search box described before Select the deactivated User you want to delete and press the Delete button or click on the Action button and then on Delete item Delete Restore C FirstName LastName ScreenName JobTitle Organizi Edit O Giovanni Tea _ Permissions 4 P Actions Manage Pages 1 Giorann llovanni S LIS Actions amp Impersonate User D Test Test test g Activate JH Actions Figure 41 Delete User Page 52 of 76 e Bivee Information Society rad 5 10 Add a new Organization Click on the Add menu item and then on Regular Organization View All Q Add Y R Export All Users User E Regular Organization Location v Top Level Jl Organizations Delete Figure 42 Add Organization Enter the Organization name in the form that is displayed when done click on the Save button to make changes persistent 5 11 Add a new User Click on the Add menu item and then on User View Al Add v Export All Users Regular Organization Location
37. er Framework Additional libraries Jasig CAS v3 1 OpenSAML 1 1b OpenSAML 2 5 JBoss RESTEasy 2 3 5 or later Application Server J2EE servlet container tested on Apache Tomcat 7 Database ne Example of SAML response issued by LSA Service lt xml version 1 0 encoding UTF 8 gt lt saml2 Assertion xmlns saml2 urn oasis names tc SAML 2 0 assertion Version 2 0 IssueInstant 2012 12 27T16 20 22 664Z gt lt saml2 Issuer gt http lsa mydomain com lsaservice lt saml2 Issuer gt lt saml2 Subject gt saml2 NameID Format urn oasis names tc SAML 1 1 nameid format unspecified NameQualifier BIVEE gt myuserid lt saml2 NameID gt lt saml2 Subject gt lt saml2 Conditions gt saml2 0neTimeUse saml2 Conditions saml2 AttributeStatement saml2 Attribute Name BIVEE_Name gt saml2 AttributeValue xmlns xs http www w3 org 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance xsi type xs string John Doe lt saml2 AttributeValue gt saml2 Attribute lt saml2 Attribute Name BIVEE Email gt lt saml2 AttributeValue xmlns xs http www w3 0rg 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance xsi type xs string gt jdoe acme com lt saml2 AttributeValue gt saml2 Attribute saml2 Attribute Name BIVEE Organization saml2 AttributeValue xmlns xs http www w3 org 2001 XMLSchema xmlns xsi http www w3 org 2001 XMLSchema instance Page 59 of 76
38. erprise Management VEM is a simple module which enables the management of Virtual Enterprises VE in the BIVEE Environment The operations supported are the following e Create modify and delete VE entities in the BIVEE Environment e Add and remove Enterprises as VE members VEM is integrated with the BIVEE Environment at several levels e VEM web UI VEM FE is part of the BIVEE Platform front end e VEM web API VEM WS is part of the BIVEE Platform common services e VEM is exploited by the BIVEE Platform s SSO module the notion of VE membership is attached as an attribute to authenticated users form there it propagates to all BIVEE Applications Page 27 of 76 Q Bivee All supported operations can be performed both by BIVEE Platform administrators through the VEM FE and by BIVEE Applications using VEM WS which is implemented as a set of REST calls See the user manual section 5 8 for screenshots and details about VEM FE and Annex C Virtual Enterprise Management Factsheet for technical documentation on VEM WS API 4 4 Raw Data Handler The Raw Data Handler RDH module and mainly its Data Storage sub module RDH DS address the need of collecting Key Performance Indicator KPI data from BIVEE ecosystem members and publish them to consumer applications such as the Mission Control Room MCR for monitoring and analysis The most relevant feature of RDH RDH DS is its integration with the Production and Innovat
39. ervices Deliverables Final D6 32 The package D6 32 BIVEE Environment prototype M24 SSO zip contains the file sso war that must be deployed on the application server deployerConfigContext xml must be edited configuring the specific AuthenticationHandlers invoked for authentication Add the following beans e inthe list of property name credentialsToPrincipalResolvers bean class gt name of the specific Authentication Handler class gt property name URI set the URL of the LSA Service endpoint e Inthe map of property name authenticationHandlers entry key gt name of the specific authority gt bean class name of the specific Authentication Handler class gt property name URI set the URL of the LSA Service endpoint Licensing information All software developed is open source and under the Apache License Version 2 0 All third party software is also open source in particular Jasig s CAS Central Authentication Service see http www jasig org cas license Page 60 of 76 RO Bivee OpenSAML is distributed under the Apache License Version 2 0 JBoss RESTEasy is distributed under the Apache License Version 2 0 SSO Client Installation pre requisites The prerequisites for installing the SSO Client are a NET framework or a PHP environment or a Java Virtual Machine Installation instructions The standard version of the CAS Client can be downloaded at the address
40. g KPI data stored in RDH DS so it is advisable to use it with caution Page 47 of 76 e Bivee Information Society Woe ondnge 5 9 User and Enterprise management This section explains how Users and Enterprises can be managed on the BIVEE Platform Organizations are the Web Portal abstraction that is used to represent Enterprises In this section we will then refer to Enterprises as Organizations Users with the Ecosystem Administrator or the System Administrator role can access the Go to gt Control Panel menu item as shown by the following picture w Control Panel QO KR 1 My Public Pages Public b yr S V Q My Private Pages Private Innnvatin Innnvatinn Goo Figure 32 Go To menu While in the Control Panel open the Portal menu located in the left column and click on the Users and Organizations item Backto Bivee Control Panel Marketplace o g Please select a tool from the left n AL Portal Administrator o o o Bivee Y T Portal Users and Organizations Sites E Site Templates Page Templates fft User Groups roles ig Password Policies Kg Portal Settings Eg Custom Fields fft Monitoring 4g Plugins Configuration Mobile Device Rules B Server o Figure 33 Control Panel menu Page 48 of 76 OG Bivee Two tables are displayed LS Information Society Woe bondage e Top Level Organizations this table lists all the Organizat
41. ion Knowledge Repository PIKR which defines a reference ontology for BIVEE KPIs KPIOnto By virtue of this integration KPI data can be collected from heterogeneous sources typically Enterprise IT systems belonging to different organizations and still be presented and analyzed in a homogeneous way This ontology driven approach to data interoperability is commonly called semantic lifting Note that RDH RDH DS are just two elements of a complex multi layered solution see Figure 17 having WP5 as the main contributor More specifically the prototype deliverable D5 3 Advanced Interoperability Services 8 released by M21 had the objective of providing advanced services to achieve full interoperability among the different activities and services taking place in the business ecosystem which may speak different languages and are not natively able to exchange data and knowledge among each other 9 In the scope of the T5 3 task RDH and RDH DS were extensively redesigned in order to support the new Data Interoperability Services WP5 artefact The complete reference documentation of this design is available in the D5 3 deliverable in this D6 32 deliverable where the actual prototype implementation of RDH and RDH DS is done we just provide some highlights Raw Data Handler Figure 17 Relationship of the RDH module with BIVEE components Page 28 of 76 Q Bivee 4 4 1 Introduction In KPIOnto KPI definitions
42. ion instructions The Raw Data Handler Service and the relative database schema can be downloaded from http bivee eng it 8780 web guest documents document library view 43585 path BIVEE Project Portal Document Library WP6 Architecture IT Platforms federation and services Deliverables Final D6 32 The package D6 32 BIVEE Environment prototype M24 RawDataHandler zip contains the files RDH WS war and bivee rdh sql First of all a new database must be created The database schema for MySQL is provided in bivee rdh sql which creates the schema and inserts the domains data To configure database access the file Spring Module xml must be edited changing the following properties appropriately Property name Value url JDBC URL of MySQL instance including hostname and port on which MySQL is installed as well as database name in the format below jdbc mysql HOSTNAME PORT DB NAME username Username of MySQL user with read write access to database password Password of MySQL user The file RDH WS war must be deployed on the application server Licensing information All software developed is open source and under the Apache License Version 2 0 All third party software is also open source in particular Spring Framework is distributed under the Apache License Version 2 0 Axis2 is distributed under the Apache License Version 2 0 Page 74 of 76 e Bivee Page 75 of 76
43. ions registered with the Web Portal e Users Without an Organization this table contains Users not associated with any Organization Marketplace Portal Administrator Bivee Y t4 Portal Users and Organizations Users are individuals who perform tasks using the portal Administrators can create new users or deactivate existing users Users can join sites be placed into organization hierarchies be delegated permissions in roles or be collected into user as sites or roles User groups may also be used to customize personal site templates for members o groups User groups can cross organizational boundaries and can be used to assign all members to other collections such Users and Organizations View All 9 Add Y 3 Export All Users Ejsites Site Templates Page Templates fh User Groups Roles Ti Password Policies Kg Portal Settings ig Custom Fields PR Monitoring 4g Plugins Configuration Mobile Device Rules l Server Search v Top Level Organizations Search Al Organizations Delete Name Type 8 Users M o s r LOCCIONI 7 Users o v Users Without an Organization Search All Users Deactivate D ren am m ed Organizations D Giovanni 1iovanr Figure 34 Users and Organizations page if Actions if Actions User Groups gt Actions Page 49 of 76 Q Bivee Through the web link Search All Organizations it is possible to open a search box to perf
44. iseManager rest rest v1 ves AIDIMA Output n a Verb URI Description pos v1 ves ve_name members add new member to given VE Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager_rest rest v1 ves AIDIMA members lt Members gt lt MemberName gt Recubrimientos Vecoal S L lt MemberName gt lt Members gt Page 67 of 76 Output n a Verb URI Description remove given Enterprise from member DELETEv1 ves ve name members mb name list of given VE Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest v1 ves AIDIMA members Coal a Output n a Verb URI Description petere v1 ves ve_name members clear member list of given VE Normal Response Code ok 200 Error Response Code error 500 Example Input http HOSTNAME PORT VirtualEnterpriseManager rest rest vi ves AIDIMA members Output n a Installation pre requisites The prerequisites for installing the VEM Web Application are A Liferay portal where Vaadin version 7 is installed A MySQL instance version 5 1 or later the application has been tested using MySQL Database engine however any database with a JDBC driver available should work Installation instructions The VEM web application and the relative database schema can be do
45. ities exist The second level of the menu is hidden by default you can reach it by clicking on a top level entry which is then expanded showing all its children Individual menu entries regardless of their level are also selectively hidden to reflect the actual access rights of the current user Profiling is done by user role see section 4 2 6 for details on the standard roles supported in the BIVEE Environment The complete list of entries in the BIVEE Platform menu follows For each of them the list of enabling roles is also given i e the user must hold at least one of them to have access e Home public e Mission Control Room MCR User BIVEE Ecosystem Admin BIVEE Admin e Virtual Innovation Factory VIR User BIVEE Ecosystem Admin BIVEE Admin Dashboard same as top level entry o New Idea same as top level entry o Posted Ideas same as top level entry o Challenges same as top level entry o Observatory same as top level entry Store same as top level entry o Whiteboard same as top level entry 9 Admin same as top level entry e PIKR PIKR_User BIVEE Ecosystem Admin BIVEE Admin e KPI BIVEE User BIVEE KPI Admin BIVEE Ecosystem Admin BIVEE Admin e Admin BIVEE Ecosystem Admin BIVEE Admin o Virtual Enterprises BIVEE Ecosystem Admin BIVEE Admin RDH Synchronization BIVEE Admin Details on each entry are given in individual sections below Page 34 of 76 eo Bivee 5 3 Menu ent
46. le is based on the Liferay Community Edition CE product Liferay CE is a JSR 168 compliant web portal working on top of the Apache Tomcat web application server Both Liferay CE and Apache Tomcat are free open source and Java based software and can run on any computing platform which supports the Java Runtime Environment In the BIVEE Platform the base Liferay implementation is enriched with custom extensions The most notable example of such extensions is the Liferay based implementation of Single Sign On see section 4 2 which enables BIVEE Applications to integrate with Liferay s authentication authorization system In particular the BIVEE Platform inherits from Liferay the concepts of user organization and role and the functionalities for their management In the BIVEE context the mapping of users and roles is straightforward while organizations are mapped to Enterprises in the BIVEE business ecosystem BIVEE web applications that are compatible with the JSR 168 standard are directly integrated as portlets in the web portal This is the case of the VEM and of the RDH front end Uls Technical details on this module are given in Annex A Web Portal Factsheet 4 2 Single Sign On 4 2 1 Introduction Generally speaking Single Sign On SSO provides a central authentication point for users of complex distributed multi tier web applications and services users authenticate themselves once and then are granted access to the en
47. liverable Page 2 of 76 QO Bivee DOCUMENT INFORMATION IST Project Number Full title Project URL EU Project officer Deliverable Work package Date of delivery Status Nature Abstract for dissemination Keywords Authors Partner Responsible Author 285746 Acronym BIVEE Business Innovation and Virtual Enterprise Environments http www bivee eu Danuta Seredynska Number D6 32 Title BIVEE Environment prototype v2 0 Number WP6 Title Architecture IT Platforms federation and services Errore L origine riferimento non e stata trovata Version 1 0 dated 30 09 2013 final x Report Demonstrator x Other This document provides technical details and user manual for the BIVEE Environment v2 0 prototype BIVEE prototype manual platform Mauro Isaja ENG Maria Carla Mantuano ENG Fabrizio Smith CNR IASI Nesat Efendioglu BOC Francisco Calle Moreno ATOS Mauro Isaja Email mauro isajaGeng it Partner ENG Phone 39 05771887100 This work is licensed under the Creative Commons Attribution 3 0 License To view a copy of this license visit http creativecommons org licenses by 3 0 or send a letter to Creative Commons 171 Second Street Suite 300 San Francisco California 94105 USA This work is partially funded by EU under the grant of 285746 SEVENTH FRAMEWORK PROGRAMME Page 3 of 76 RO prg Bivee TABLE OF CONTENTS EXECUTIVE SUMMARY 2 DOCUMENT
48. me page is displayed Only the Home entry is showing up in the first level of the Platform s menu as the user is still navigating as a guest anonymous user 5Bivee Innovating Innovation LS AIDIIM A FURNITURE WOOD AND PACKAGING TECHNOLOGY INSTITUTE LOCCIONI ZX osos BN Figure 23 Web Portal home page To access the full set of functionalities available through the Web Portal the user clicks on the Sign In button Figure 24 Sign In button Ask the URL of your BIVEE Platform installation to your IT contact Page 33 of 76 The user is redirected to the login form The user types her username and password as provided by the Web Portal administrator in the corresponding fields of the login form Then she clicks on the Confirm button If the credentials are valid the Web Portal home page is again displayed this time with a set of menu options according to the user s profile see section 5 3 For the sake of completeness from now on we assume that the user holds full administrative rights so that the entire set of menu options is available 5 2 BIVEE Platform menu The menu of the BIVEE Platform is structured on two levels The first one lists areas of interest within the BIVEE Environment e g a BIVEE Applications or a group of related functionalities in the BIVEE Platform These top level entries may have child entries as well where multiple entry points or different functional
49. ment value required precision scale 19 6 factDate date Date of measurement required vEnt string Virtual Enterprise required must be valid registered in RDH ent string Enterprise optional if provided must be valid registered in RDH as member of vEnt dimData array of O N DimElement instances One entry for each reference to a dimension level all entries must be valid and uniquely named levName and DimElement is a complex structure too DimElement levName string Name of dimension level required must be valid supported by the current KPI levRef string Reference to a dimension level member required must be valid registered in RDH Output parameters A boolean true if the operation ended successfully false otherwise Y getLevelValues Input parameters levelName string normalized name of the dimension level required must be valid registered in RDH Output parameters array of O N DscLevelValue where DscLevelValue is a complex structure DscLevelValue name string instance of dimension level partOf string indicates the parent of the member in the dimension hierarchy Page 73 of 76 OG Bivee Installation pre requisites The prerequisites for installing the Raw Data Handler Service are A Java servlet container version 6 or later the prototype has been tested on Apache Tomcat 7 A MySQL instance version 5 1 or later Installat
50. n RDH factRecord FactRecord data of the record to delete where FactRecord is a complex structure FactRecord factVal decimal Measurement value required precision scale 19 6 factDate date Date of measurement required vEnt string Virtual Enterprise required must be valid registered in RDH ent string Enterprise optional if provided must be valid registered in RDH as member of vEnt dimData array of O N DimElement instances One entry for each reference to a dimension level all entries must be valid and uniquely named levName and DimElement is a complex structure too DimElement levName string Name of dimension level required must be valid supported by the current KPI levRef string Reference to a dimension level member required must be valid registered in RDH Output parameters A boolean true if the operation ended successfully false otherwise Y putData Input parameters PutDatalnput sender string identity of the sender required must be valid Page 72 of 76 AO Bivee simLoad string If value is 1 data sent with the call will go through validation but will not be committed into Data Storage factName string normalized name of the KPI for which to put data required must be valid registered in RDH factData array of 1 N FactRecord instances where FactRecord is a complex structure FactRecord factVal decimal Measure
51. ncoded according to a data structure processable by the VIF the list of the dimensions to be provided in order to compute a given KPI In addition the reasoning facilities provided by the PIKR Service Library see Deliverable D5 1 are made available through the interface exposed by the Service Manager The main API that can be accessed by the VIF and the MCR through the Service Manager interface are Semantic search which allows exploiting semantics enabled search services The search_request is an expression containing an ontology based feature vector describing the criteria for the selection of the resources of interest The function returns a list of ranked results in terms of resource URIs by applying semantic similarity techniques Query evaluation which allows posing queries to the PIKR knowledge base compiling queries into the underlining inference engine and collecting the result of the evaluation Besides the query service described in D5 1 a pure SPARQL end pointhas been deployed Compliance verification which allows verifying the consistency between the semantic descriptors and the business rules both formalized and stored in the PIKR KPI definition management which supports the management of KPIOnto by allowing the introduction of new KPIs and their mathematical formulas their update and their deletion Page 18 of 76 RO Bivee These functions are capable to check if the new KPI is consistent with respect
52. ndow sss sese eee eee 47 Figure 32 Go TO MENU er e a en ra e Yeates ds Ld n vede n ds kDa Eq Ra ede dan EUR 48 Figure 33 Control Panel Menu sss ee eee ee eee 48 Figure 34 Users and Organizations Dage eee eee ee eee 49 Figure 35 Organizations basic Search 50 Figure 36 Organizations advanced search sss 50 Figure 37 Users basic Tea Cte a REI EHE IEEE IOR EC EN Naas 51 Figure 38 Users advanced search ue reser a E Aa EE EEEa DARREN 51 Figure 39 Delete Organizatlori eite ot eR REEEE oldie Pee ER EE RECEN ERE RIDE Re La PUN 52 Figure 40 Deactivate User uice iine esce LU Te RHEINE FARE TURN EE R RET TRR E RR QRR ARE TRAN ERA 52 Figure 41 Delete User um edite Rott Ret I E TUER E TERRE UE RE CRECEN TERRE 52 Figure 42 Add Organization ERE teken ideen eee 53 Figure 43 Add USET ERES See EHE H ERI e Neae Poet e eiet eitt 53 Figure 44 New User basic data eere tee tesis tei deni Meee eds 54 Figure 45 User menu Roles eR eR ves i E nee eie i He cuu e esci diet 54 Figure 46 User menu Organizations sese eee eee 55 Figure 47 New User Organization Ist eee 55 Page 6 of 76 GLOSSARY OF TERMS PIKR Production and Innovation Knowledge Repository the BIVEE Application which is responsible for maintaining the Knowledge Base of a given BIVEE Environment PIKR KB PIKR Knowledge Base the reference ontologies of a given BIVEE Environment each composed by concepts classes and attributes and real world entities in
53. onent API in order to allow interactions with MCR 2 Single Sing On SSO integration and 3 look amp feel Currently 56 web methods in the MCR Component API have been implemented The SSO integration using CAS and style adaptations in order to have common look amp feel are under development Page 15 of 76 2p Bivee 2 3 Virtual Innovation Factory integration The Virtual Innovation Factory VIF is one of the components integrated within the BIVEE environment This is done through the use of web services consumed exposed The integrated components are e PIKR e MCR e BIVEE platform services This is the main picture of the integrated components BIVEE PLATFROM Figure 9 Integrated components from the VIF side The VIF also partially exposes its own database information using a CRUD system based on REST web services There s also read only specific services that are expose those one needed to obtain the information in the KPI calculation processes 2 3 1 PIKR PIKR offer the VIF semantic support through SOAP based web services While SOAP it is heavily used in other technological frameworks it is of no common use in javascript environments Thus the VIF has implemented a component to enable such kind of connections Consumed services by the VIF from are e Element tags Concepts from the PIKR e Document annotation e Semantic search Page 16 of 76 T 2 Information Society Bivee TAGS Concept
54. orm the search action over all registered Organizations This search box is available in two flavours e Basic e Advanced Organizations arch uw Advanced Figure 35 Organizations basic search Match All w ofthe following fields Name Street City Type Country Region v v v Postal Code Search Figure 36 Organizations advanced search Page 50 of 76 QC Bivee Through the web link Search All Users it is possible to open a search box to perform the search action over all registered Users This search box is available in two flavours e Basic e Advanced Users Search Advanced Figure 37 Users basic search Match All v ofthe following fields First Name Middle Name Last Name Screen Name Email Address Status Active Search Figure 38 Users advanced search Page 51 of 76 e Bivee Eve Information Society Ine ette To delete an Organization select it and press the Delete button or click on the Action button and then on Delete item v Top Level Organizations Search All Organizations Delete Name Type o s r AIDIMA N x Regular Organizatio Edi ctions 2 8 Users regular Organizatio la Edit E Assign Organization Roles a rp Reqular Organizatior Actions amp Assign Users amp Add User Add Regular Organization Add Location amp Delete Figure 39 Delete Organization To delete an User it is necessary to deactivat
55. plementation of MCR prototype V2 0 within the Task T3 2 a method updateKPI has been implemented which serializes a query for each KPI in question to XML complying XML schema provided by the PIKR and saves the returning XML stream in XML file for further processing as depicted in Figure 7 Page 14 of 76 Q Bivee 2 2 2 Integration between MCR and VIF Effort to establish integration between MCR and VIF is focused on the scenario defined in 6 The idea is to expose conceptual models modelled with the MCR Modeller to the Whiteboard in VIF open them for a discussion and get them back enriched with comments in order to improve VE VIF WHITEBOARD MCR APIs comment v J gt 8 E comment O comment comment MCR APIs comment Expert Modeller Figure 8 Exposing Conceptual Models to VIF Whiteboard in order to take Comments Suggestions and Annotations excerpt from 6 In order to realize the idea the approach specified in 6 has been taken as basis In order to realize that approach the web methods GetTOC GetModelNameByld GetModelldByNameAndType GetModelAsXML GetModellmage are provided within the MCR Component API and they are currently inbeing tested in the WP4 2 2 3 Integration between MCR BIVEE Service Platform and Third Parties Effort to establish integration between MCR BIVEE Platform and third parties gathers around three subjects 1 Implementation of web methods in the MCR Comp
56. plication Server 4 Figure 2 Example deployment of a BIVEE Environment instance In a distributed architecture such as the BIVEE Environment where several different BIVEE Applications need to cooperate in a seamless way integration issues are of paramount importance The following subsections give an overview of how this objective was achieved with a focus on cross application communications Page 10 of 76 OD Bivee Information Society lov erie 2 1 BIVEE Platform integration The BIVEE Platform exposes a set of APIs for BIVEE Applications to consume and in turn consumes some APIs exposed by BIVEE Applications The following component diagram identifies these endpoints 550 API RDH API VEM API PIKR API Figure 3 BIVEE Platform API overview The SSO API provides means for BIVEE Applications to verify user authentication tokens and to obtain relevant information about the current web user user attributes See section 4 2 4 for more details and also section 4 2 6 for information about user attributes The RDH API enables BIVEE Applications to read and modify KPI data stored in RDH WS See section 4 4 3 for more details The VEM API enables BIVEE Applications to read and modify Virtual Enterprise data stored in VEM See section 4 3 for more details Finally the RDH Sync sub module depends on the PIKR API for reading the KPlOnto ontology See the PIKR documentation 8 for more details Page 11 of
57. plications even if not as an attribute this is standard information provided by the base SSO protocol BIVEE Applications can and should use the security related attributes Organization Virtual Organization and Role for applying their own user profiling logic In the BIVEE Environment there is a standard set of Roles defined for this purpose BIVEE User basic access to non public areas of the BIVEE Platform PIKR User access to the PIKR application VIF User access to the VIF application MCR User access to the MCR application BIVEE KPI Admin access to KPI data management capabilities BIVEE Ecosystem Admin access to VEM and to web portal user administration BIVEE Admin no restrictions in the BIVEE Environment full admin control on web portal Note about PIKR User VIF User and MCR User these are coarse grained roles that enable a first level user profiling who can access which BIVEE Application Each BIVEE Application may also add its own user profiling layer on top e g enable disable some of its features on the basis of user identity The management of this kind of local profiling is in charge to each single application and is not covered by this document Attributes are released to applications in SAML format see section 4 2 2 Technical details of the attribute release feature including an example of SAML are given in Annex B Single Sign On Factsheet 4 3 Virtual Enterprise Management Virtual Ent
58. previous scenario MCR MODELLER PIKR e g Production Process Model ao 0 INPUT Process Information Concepts annotated findPartner Partner OUTPUT List of potential Partner B partners for human Expert aki interpretation Modeller Figure 5 Partner Search during VE Creation in MCR Modeller For the realization of the proposed scenario in the ongoing implementation of second prototype of MCR a specific method has been implemented which as depicted in Figure 5 sends information about process activity product feature and annotated concepts to the PIKR service and displays returning proposed partners in a list within the MCR Modeller and allows users to select one partner from the list Although the first interaction has been established in the context of this scenario the scenario is still under development within the T3 2 Document and Knowledge Resource Retrieval in the MCR Assistant This scenario is set around the idea to make related documents knowledge resources available to the user of the MCR Assistant based on the annotation of the flow object by using concepts imported from the PIKR The documents knowledge resources are not hard linked but derived according to the annotation Page 13 of 76 O65 Bivee MCR ASSISTANT PIKR EMI oo o fe ua uu 7 S INPUT Process Activity a c Information Concepts annotated c c findKno
59. rsonal site Save Cancel Figure 46 User menu Organizations New User Organizations Name Type Roles ECT System Regular Organization d Remove Figure 47 New User Organization list Page 55 of 76 QO Bivee 6 REFERENCES 1 2 3 4 5 6 7 8 9 10 11 12 Camarinha Matos Afsarmanesh Galeano Molina Collaborative networked organisations Concepts and practice in manufacturing enterprises Elsevier 2008 BIVEE deliverable D6 20 Service Platform Specifications BIVEE deliverable D6 31 BIVEE Environment prototype v1 0 BIVEE deliverable D5 1 Production and Innovation Knowledge Repository BIVEE deliverable D4 1 State of the Art amp Virtual Innovation Factory Design BIVEE deliverable D3 21 Mission Control Room Prototype v1 0 BIVEE deliverable D4 21 Virtual Innovation Factory Prototype v1 0 BIVEE deliverable D5 3 Advanced Interoperability Services BIVEE Description of Work document http www liferay com BIVEE deliverable D3 1 State of the Art and Mission Control Room Specification Hrgovcic V Karagiannis D Woitsch R Conceptual Modeling of the Organisational Aspects for Distributed Applications The Semantic Lifting Approach IEEE conference COMPSAC 2013 2013 Kyoto Japan Page 56 of 76 ANNEX WEB PORTAL FACTSHEET Prototype references 2 0 http bivee sp eng it Version Availability Source tontfol svn repo nimbus ware com BIVE
60. ry Home This is the default page of the BIVEE Platform portal It is accessible to any user The screenshot below shows the appearance of the home page to a user holding full admin rights Innovating Innovation 5 AIDIMA FURNITURE WOOD AND PACKAGING TECHNOLOGY INSTITUTE LOCCIONI ENGINEERING Ed Page 35 of 76 RO Bivee 5 4 Menu entry Mission Control Room This menu entry links to the landing page of the Mission Control Room MCR which runs as a standalone application i e integrated with the SSO Service but not with the Web Portal For this reason no screenshot is provided here see MCR s own documentation 6 for the user manual In the last release of the BIVEE Environment full Ul integration will be achieved This menu entry is accessible only to users holding any of these roles MCR_User BIVEE_Ecosystem_Admin BIVEE_Admin Page 36 of 76 Q Bivee 5 5 Menu entry Virtual Innovation Factory This is the landing page of the Virtual Innovation Factory VIF whose Ul if fully integrated with the Web Portal This as well as the inner pages which compose the VIF front end see following sub sections are accessible only to users holding any of these roles VIF User BIVEE Ecosystem Admin BIVEE Admin The following is a screenshot of VIF s landing page 25 Bi EN 2 v Bivee 8 A second level menu deploys under the VIF main entry each entry corresponding to a VIF module Each of
61. s Search results VIF Documents Annotated docs physical files Annotated document no physical file Figure 10 PIKR services consumed by VIF 2 3 2 MCR There are two kinds of integrations between MCR and VIF First one the already explained in the MCR section 2 2 2 between the MCR and the VIF whiteboard This integration allows the models to be annotated not semantically but with notes This integration is started from the MCR and ends in it Y i send model to the whiteboard i l experts annotate model send annotated model perform changes if any PED Figure 11 MCR VIF whiteboard integration The second one yet to be implemented will happen when the Innovation Project is finished This will be a web service based communication protocol allowing the Production Space to implement the outcomes of a concrete Innovation Project 2 3 3 BIVEE PLATFORM The VIF uses these services from the BIVEE platform e sso e User profiles next release e Notifications next release Page 17 of 76 AO Bivee The SSO is performed using an specific module developed as part of the VIF Again as it happens with the SOAP based services since they are not of common use the CAS is not heavily expanded within the javascript community User profiles are to be extended by each component VIF MCR and PIKR but the user and its general profile are common to each component Therefor the
62. s capable to rewrite the request by 1 performing drill down of some dimensions in order to obtain the required information by aggregation of lower level data e g aggregation of KPI data about months January 2013 June 2013 to evaluate KPI data about the first semester 2013 or 2 by decomposing the KPI formula in its components e g A B C computing the required information for each of the component e g B and C separately and then evaluating the required value through the formula e g A Page 19 of 76 BO Bivee 3 BIVEE ENVIRONMENT USE CASES Figure 12 is a use case diagram showing the pig picture of the BIVEE Environment from the functional point of view Only those use cases which are directly supported by the BIVEE Platform are described in detail in the User Guide see section 5 For information on the others which are related with specific BIVEE Applications see the relevant documentation released as part of other BIVEE deliverables 4 6 7 Oo T pom EE 4 Manage Knowledge Base gt Ontology Engineer gr x Em baa SEE Cou e r aa Manage Organizations gt esse taii Mp CORE Oe pe C Browse KPI Data gt P 2 e mete xs p C Manage KPI Data gt S Po Access Ecosystem Administrator p d Pl ae cara lem eaten yy ae p E o m I Manage Innovation Space gt S Qo KPI Data Administrator T 9 e niii Bu
63. ser may determine name attributes and value of a new record by selecting from option lists The list of available KPIs of the relevant attributes dimension levels and of their legal values are all sourced from PIKR s KPlOnto When done the user commits the new KPI value to RDH DS by clicking on the Save button ORGANIZATIOMDIMENSION Terl VARN ZAI ONUIFENSIDY CE KN 9 Vahe saeersecanz Development TIMEDIMENSION Level VES Figure 28 RDH FE insert KPI value Page 44 of 76 Q vi Information Society rad Bivee 5 8 Menu entry Admin Administration is not an entry point by itself it collects admin related functionality as second level items as detailed in the following sub sections 5 8 1 Sub menu entry Virtual Enterprises This is the entry point for VEM FE i e the web based front end of the Virtual Enterprise Management module VEM FE functionality is available only to users having the BIVEE Ecosystem Admin or the BIVEE Admin role i e to ecosystem or web portal administrators The landing page displays the list of Virtual Enterprises VE registered in the VEM ET SOR EN Mission Control Room Short description AMA TETANC 039 INST AE SHINE LURE WOON AND EACKAG NG Xj AJ UCOICN N gt YY ENVIHCNMEN I HUME HUMANCAFE amp MUBILITY SOLU ICNS X ul Figure 29 VEM FE landing page The user can delete any VE by clicking on the x icon of
64. siness Innovation Space Administrator Q a Ecosystem user T o uod A EEE B siness Innovation Space Engineer Manage Innovation Process gt nen EEG Business Innovation Space User __ wd Pana C Execute Innovation Process Qo Value Production Space User C Monitor Value Production Space 2 E gin e RIZ C Improve Value Production Space BE Value Production Space Engineer lt Model Value Production Space LENS ON PE Q Value Production Space Administrator eS in na CL Manage Production Space gt Figure 12 Bivee Environment use case diagram Regarding the diagram in Figure 12 it is worth noting that the Actor names and their relationships represent a logical responsibility network and do not necessarily correspond to the physical user roles assigned by the BIVEE Platform s Single Sign On system see section 4 2 6 In the current version of the BIVEE Environment roles that are application specific are still managed internally by the applications themselves e g Value Production Space User Value Production Space Engineer and Value Production Space Administrator are all roles belonging to the Mission Control Room application which is in charge of mapping them to the users as appropriate Page 20 of 76 RO Bivee 4 BIVEE PLATFORM MODULES 4 1 Web Portal The BIVEE Platform web portal modu
65. the corresponding row the system will ask the user for confirmation When a VE is removed from the registry all membership information i e the notion of which Enterprises are part of the given VE is lost Page 45 of 76 Q Bivee Information Society lrchondequ The user can navigate to the details of any VE by clicking on the a icon of the corresponding row a dialog window is displayed VE DETAILS Name Short description TECFROLOGY INSTITUTE FURNITURE V COD AND PACKAG NG Long description ADIMA R ths Technology A E c Fut re Wooc Pazkagirg 70 obed ncua es It 3 3 non fo pratt 95300830 ard ka scope is both atoral Ard R Mer 1 Aeg 0 was to det n Novemcer 1882 AIDIMA madti ts tat des oc Jury 1883 to pen its KK and DANAA assemct VE Members Enterprises Mazao G ulb SRL Manian Inmac EA Ram n D a Machol CV dos Veco S L Ss Canes Figure 30 VEM FE VE Details dialog window The user can modify the short max 255 characters and long max 1000 characters descriptions of the VE The user can also edit the member list of the VE e add a member by selecting it in the Enterprises list and by clicking on 27 e remove a member by selecting it in the VE Members list and by clicking on e remove all members by clicking on s add all non members by clicking on To make changes permanent the user has to click on the Save button By clicking on the Cancel button
66. the following sequence diagram User Web Browser BIVEE Web App HTTP GET protectedEesource HTTP REDIRECT loginForm HTTP GET loginForm HITP PUST uid pwd Find LSA Service endpoint Verify response userData Figure 14 SSO login sequence Page 24 of 76 RO Bivee 4 2 5 LSA Service sub module All users in a BIVEE Ecosystem are registered with some Local Security Authority LSA which is an abstraction for a user repository exposed as a service The LSA Service sub module is a two faced object On one side it exposes a public endpoint for user credential validation and user attribute release on the other it connects with some pluggable user data repository e The public endpoint is a RESTful service that accepts HTTP GET requests issued on a secure channel with username and password parameters the response body is a SAML document stating the authenticated identity of the user and a set of standard attributes see section 4 2 6 e The user repository connector is a plug in module chosen from a library of off the shelf e g for LDAP or JDBC based integration or custom built adapters As the LSA Service sub module is binary compatible with the AuthenticationManager architecture of CAS the entire library of connectors from the CAS standard distribution is available for reuse In order to retrieve Virtual Enterprise membership information and populate the attribute set of an authenticated user the LS
67. the sub sections that follow provides a relevant screenshot See VIF s own documentation 7 for the user manual Page 37 of 76 20 as Bivee 5 5 1 Sub menu entry Dashboard QO Bivee Innovating Innovation pode mot n cape y ce rad eld arm dr Mot Page 38 of 76 Qo HE Bivee 5 5 3 Sub menu entry Posted Ideas T QO Bivee Innovating Innovation QO Bivee Innovating Innovation een Quem i ut omm ode KA OF vof h omm Veme t rer quus tco Mt rmt certes ster A ant event oe rent rhum bnt M owt most Kra Of ver 5 e m wer 460 V rrt Y Jr epson UC en al mean QA rm chon oa c BOOS V v eq nen deb NR DA RA Fut K A RPT CRIT PE r A itn t pel hom paw Tare at act been prod ost ve Qua ica femen nell grind ov abe um ope 0004 V Qon G LRH nop 4 DL E ict oos damer aeos v UKA nm OO trk DA KN FOT Or a Ae o matet vet over ce rere me tna Me ras Leie eer verse neder natem bet OND Y Pa OD et vel ys Oe aem tO WOOT P intet hope pine t eun ad nm mam oA Ord rater ares MOOR Ue OG 0108 vett EC Jet LR me BG operere gn on nme Gr mere pa SQUE KMR ere Confer vt mene ches re f KK rv Ye N Kret P r d vel wr koe Partepents ca Page 39 of 76 eo Bivee 5 5 5 Sub menu entry Observatory EU Iv o lt Innovating Innovation Innovating Innovation Mighited item Qucm det op Peta ien tnt Mee seeti e 2 s TL ae nw
68. tire environment without repeating annoying login operations Furthermore the overall security level of the environment is enhanced with respect to application based sign on as user credentials remain invisible to applications There are two basic approaches at implementing SSO e Centralized All users and their credentials are registered in a single repository This approach is most effective when used to centralize the management of security policies e g within a single company Each organization tends to keep an internal centralized repository of users and groups often provided by a LDAP server in order to control access to corporate resources e Federative Users and credentials are stored in local systems or nodes which are grouped in a federation Accessing one of the federated nodes grants also access to all the others This approach is particularly useful when different organizations want to keep control over their own security policies In the BIVEE context both approaches are feasible with different configurations of the SSO module see section 4 2 5 T Lightweight Directory Access Protocol Page 21 of 76 RO Bivee 4 2 2 Open technologies Several open technologies and standards have been developed in the last years to address authentication and authorization issues in distributes systems Here we present two of them Central Authentication Service CAS and Security Assertion Markup Language SAML
69. to all the other formulas to avoid incoherencies and redundancies KPI reasoning for VE setup which allows for the extraction of those indicators that are in common among a set of enterprises and that can be used to monitor and compare their performances Such functionalities are useful during the setup phase to determine the sets of information that have to be provided by enterprises in order to calculate the requested KPI or on the other hand to recognize which kind of indicators can be derived given the available information at enterprise level Finally the Semantic Data Handler SDH is the module of the PIKR that allows the other BIVEE components to access KPI data by providing a uniform view over them independently of their original data sources see Deliverable D5 3 The main functionality is Multidimensional Query which accepts a request for the computation of a certain KPI with respect to levels of some dimensions e g ROI for the enterprise ACME evaluated for the first semester of 2013 for the countries Italy and Spain Terms are expressed through the VE common reference that is the KPIOnto The approach described in details in D5 3 exploits reasoning over the KPIOnto in order to determine if the KPI specified in the request can be actually computed starting from the data in the RDH If so the request is translated into a Data Storage compliant query and then passed to the RDH for retrieving the actual data Otherwise it i
70. torical KPI data are kept in normalized form that is in a relational format that is highly compatible with the logical structure modelled by KPlOnto The main value of data normalization is that application queries expressed in KPlOnto terms can be then translated by the Semantic Data Handler into equivalent RDH DS queries SQL which will perform very fast Basically KPlOnto classes derived from the Dimension class are translated into domain tables see Figure 19 and are populated with records corresponding to concrete instances see Figure 20 each Indicator instance becomes a fact table by its own connected with the relevant domains see Figure 21 The resulting schema is described in the RDH DS Catalogue and from there entities can be easily mapped back to KPlOnto concepts see Figure 22 The RDH DS sub module is a private back end component in that its functionality is made available externally i e to applications which are not integrated into the BIVEE Environment only by means of another module RDH WS implementing the RDH web API layer see section Page 29 of 76 RO EE Information Society oe henda Bivee s 4 4 3 Internally RDH DS is accessible through a direct low level channel a Java Database Connectivity JDBC driver rmn abstract classes KPlOnto Dimension concrete classes Indicator S instances Organization PERSON REF DCPARTMENT RET abstract classes Dimension conzrele classes KPIOnto
71. tring normalized name of the KPI required must be valid registered in RDH Output parameters array of O N FactRecord where FactRecord is a complex structure FactRecord factVal decimal Measurement value factDate date Date of measurement vEnt string Virtual Enterprise ent string Enterprise dimData array of O N DimElement instances One entry for each reference to a dimension level and DimElement is a complex structure too DimElement levName string Name of dimension level levRef string Reference to a dimension level member v getKpiLevels Input parameters indicatorName string normalized name of the KPI required must be valid registered in RDH Output parameters array of O N DscindicatorLevel where DscIndicatorLevel is a complex structure DscindicatorLevel dimNormName string normalized name of the KPI dimension Page 71 of 76 RO Bivee dimensionClass string class of the dimension indName string KPI name isMandatory string indicates if the dimension is mandatory levelClass string class of the level levelNormName string normalized name of the dimension level levelPriority int indicates the position of the level in the dimension hierarchy Y deleteKpiValue Input parameters indicatorName string normalized name of the KPI for which delete a record required must be valid registered i
72. ts as defined in the portal stylesheet The PIKR web front end due to its nature of separate administration tool is linked from the BIVEE Environment menu and is integrated with SSO but still remains a standalone application A new component was added to the BIVEE Platform the Virtual Enterprise Management VEM see section 4 3 This component enables Virtual Enterprise VE management at the base BIVEE Platform level and is also integrated with the SSO service such that VE membership is attached as an attribute to authenticated users The VEM comes with its own web Ul but also exposes a web API for BIVEE Applications to use VEM WS The existing Raw Data Handler RDH component in charge of acquiring performance indicator data and of navigating the repository was entirely redesigned in the scope of WP5 in order to support the D5 3 deliverable Advanced Interoperability Services released by M21 the new design was then implemented in the scope of this deliverable More specifically the Data Storage RDH DS was re engineered and the RDH WS web API was extensively modified enabling the integration between the end user IT systems and the BIVEE semantic knowledge base that was the objective of D5 3 On top of that an enhanced web Ul for data navigation and administration was also developed Page 9 of 76 O65 Bivee 2 BIVEE ENVIRONMENT ARCHITECTURE The BIVEE Environment is an inherently distributed architecture the BIVEE Pl
73. tually member to a given VE if at least one of the Enterprises she belongs to as defined by Liferay s mappings is actually member of that VE as per VER s mappings Page 25 of 76 QO Information Society Bivee T I User Repository N Connectors Active Directory LDAP 7 LIFERAY Figure 15 Multiple LSA Services under a single SSO master Public Internet SSO Service BIVEE BIVEE Environment A Environment B LSA VEM LSA VEM U Figure 16 BIVEE Environment federation 4 2 6 BIVEE standard SSO attributes and roles In the BIVEE Environment the SSO module is responsible not only for user authentication but also defines a standard schema for user data As previously mentioned see section 4 2 3 the BIVEE implementation of SSO adds the attribute release feature which means that BIVEE Applications will obtain a standard set of attributes attached to each authenticated user Page 26 of 76 Attributes are basically a name value pair where the name is one of the following BIVEE Name 1 occurrence Screen name of the user BIVEE Email 0 1 occurrence Email address of the user BIVEE Organization 0 occurrences List of Enterprises the user belongs to BIVEE VirtualOrganization 0 occurrences List of Virtual Enterprises VEs the user is member of BIVEE Role 0 occurrences List of BIVEE Roles assigned to the user The unique ID of the user i e the login name is also exposed to ap
74. wledgeResources Resource A Resource B R 6 SESQUIGE gt OUTPUT List of Knowledge Resource D Resources as URL List Assistant User Figure 6 Document and Knowledge Resource Retrieval in MCR Assistant In order to realize the idea in ongoing implementation of MCR prototype V2 0 within the Task T3 2 an appropriate approach has been specified which is currently being implemented According to approach as depicted in Figure 6 the MCR sends information about process activity and annotated concepts to PIKR service and receives related list of URLs of related documents knowledge resources and displays them in the MCR Assistant Synchronization of the MCR and the PIKR for KPI Visualisation The idea in this scenario is to feed the sensors related with KPIs in the MCR by data retrieved from PIKR The MCR controls the KPI update and calculation frequency and then visualizes the KPI data on MCR Monitor according to predetermined parameters MCR MONITOR PIKR 2 Query for each KPI LI 3 Response for each KPI as XML Stream 6 Retum updated KPI values 4 for dvery Sensor if answer is error free save temporary 5 For every Sensor read data from temp file Server side file system ume Seo c APR Temporary XML files Figure 7 Synchronization of MCR and PIKR for KPI Visulaisation In order to realize the idea in addition to on going im
75. wnloaded from Page 68 of 76 http bivee eng it 8780 web guest documents document library view 43585 path BIVEE Project Portal Document Library WP6 Architecture IT Platforms federation and services Deliverables Final D6 32 The package D6 32 BIVEE Environment prototype M24 VirtualEnterpriseManager zip contains the files VirtualEnterpriseManager war and ver sql First of all a new database must be created A sample schema for MySQL is provided in ver sgl which creates a basic schema and inserts some test data for users The file VirtualEnterpriseManager war must be deployed on the Liferay portal To configure database access the file jdbc properties must be edited changing the following properties appropriately Property name Value jdbc url JDBC URL of MySQL instance including hostname and port on which MySQL is installed as well as database name in the format below jdbc mysql HOSTNAME PORT DB_NAME jdbc username Username of MySQL user with read write access to database jdbc password Password of MySQL user Licensing information All software developed is open source and under the Apache License Version 2 0 All third party software is also open source in particular Liferay Portal Community Edition is distributed under the GNU Lesser General Public License version 2 1 Vaadin is distributed under the Apache License Version 2 0 MyBatis is distributed under the
76. xuta cu esa casae epu Dk esu Ra exa Du Du esu cR ene Duca besta 35 5 4 Menu entry Mission Control ROOM sese eee eee eee 36 5 5 Menu entry Virtual Innovation Factory sees 37 5 5 1 Sub menu entry Dashboard sss eee eee eee 38 5 5 2 Sub menu entry New ldea eese eene enne nennen eene nennen 38 5 5 3 Sub menu entry Posted Ideas cccesscccessssececesneeceesseecesssnececssaeeeeseeanecessnaueeesenanes 39 5 5 4 Sub menu entry Challenges sees enne nnne nnne 39 5 5 5 SUB MENU entry Observatory sese eee 40 5 5 6 SUb menurentryr StOFe e etuer ener re oni ni eter ain aie ieee 40 5 5 7 Sub menu entry Whiteboards rrmrrrrnrvvnnrrnvvvrrennvvnnsennrrnnsernrrnrsennrrnssennrrnssennrsnssennresne 41 5 5 8 SUB MENU entry Admin rsnrrersrnnrvernrnnrrnrsrsnrenssernrrnssernrrnssssnrnnsssnnvenssennrsnsssnnrsnsssnnrsnee 41 5 6 Menu entty PIKR oes dices erede rir eoe hr ee ea EY Sega goo E SYN MEER FLYER YA SEE o Tolg e XY ORE Y RC NE sand 42 Ki TE e Ta T M 43 5 8 Menu entry AGM Nemera AT A agere sanere 45 5 8 1 Sub menu entry Virtual Enterprises eene eene 45 5 8 2 Sub menu entry RDH Synchronization sese eee eee eee 47 5 9 User and Enterprise management esses eene nennen enne ener 48 5 10 Add a new Organization sse eee eee eee 53 SIT Add new WSO ies sinnene ae enka era badene eddik 53 G REFERENCES n HE 56 ANNEX

D6.32 - bivee

Contents

Download Pdf Manuals

Related Search

Related Contents