D3.22 Mission Control Room Prototype (v2.0) Nesat Efendioglu Robert Woitsch Wilfrid Utz Benjamin Knoke

Transcription

1 D3.22 Mission Control Room Prototype (v2.0) Nesat Efendioglu Robert Woitsch Wilfrid Utz Benjamin Knoke Co- funded by the European Commission, contract n FP7- ICT Co- funded by the European Commission, contract n FP7- ICT

2

3 Document type Document version Deliverable : Final Submission Date : 16/09/2014 Dissemination Level : Public Author(s) : Nesat Efendioglu (BOC), Robert Woitsch (BOC), Wilfrid Utz (BOC), Benjamin Knoke (BIBA) File Name : D3.22 Mission Control Room Prototype (v2.0).pdf Grant Agreement n. : FP7-ICT IST Project Number : Project Title : Business Innovation in Virtual Enterprise Environments Project Duration Website 40 months : Co- funded by the European Commission, contract n FP7- ICT

4 CHANGE HISTORY Version Date Status Author (Partner) Description STARTING Nesat Efendioglu (BOC) Initial Table of Content WORKING Nesat Efendioglu, Robert Woitsch (BOC) Initial Contribution to each chapter WORKING Nesat Efendioglu, Wilfrid Utz(BOC) WORKING Nesat Efendioglu (BOC) WORKING Nesat Efendioglu (BOC) Further Contribution to chapter New Features Further Contribution to chapter Adaptation of Existing Features Contribution to Chapter User Requirements WORKING Nesat Efendioglu (BOC) Contribution Chapter Introduction Deployment to and DRAFT Nesat Efendioglu Executive Summary and Formating DRAFT Benjamin Knoke (BIBA) DRAFT Nesat Efendioglu (BOC) Detailing of User Requirements (Section 2) Further Contribution to all chapters and consolidation Internal Release Nesat Efendioglu (BOC) Executive Summary and Introduction Update. Formatig Final Nesat Efendioglu (BOC) Improvements based on internal review reports Page 4 of 36

5 EXECUTIVE SUMMARY This document reports realization of Mission Control Room Prototype v2.0 (MCR 2.0) that is enhanced and updated version of Mission Control Room prototype v1.0 (MCR 1.0). MCR 2.0 aims to fulfil end- user requirements and shortcomings, which arose during the evaluation of MCR 1.0. Besides end- user requirements, the MCR 2.0 aims also to fulfil technical requirements that arose because of changes on other BIVEE Components and migration of MCR into new ADOxx release. This report complements the report D3.21 [1] by reporting new features added, adaptations made on the existing features according to requirements and shortcomings mentioned above. Hence, the report has nature of delta report that refers to design considerations described in [1]. First of all, the aforementioned requirements and shortcomings are shortly revisited and listed. The requirements and short comings are classified in two groups; (1) end- user requirements, which are reported by end- users or by consortium during plenary meetings, evaluation of MCR 1.0, the Second Monitoring Campaign and as well as the requirements that are reported in second iteration of user requirement analysis report [2], (2) technical- user requirements. The technical requirements differentiates in three groups; (a) technical requirements in order to utilize services provided by BIVEE Platform (b) technical requirements that are occurred due to changes in some service description of other BIVEE components, (c) technical requirements that are occurred due to migration into the new ADOxx release. Afterwards, the new features; (1) Multi Language Support, (2) Single- Sing- On, (3) New Start Page, (4) New Look & Feel Package and (5) Copy & Paste Feature are introduced, short overview on realization of the features is given and how they can be used is shortly described. After that, required adaptations on existing features according to requirements are reported. It is shortly reported, that what on which layer of MCR Component has been changed, why it has been changed and how it is working now. Although the overall deployment scenario of MCR v2.0 does not have any significant difference between deployment scenario of MCR v1.0, the deployment scenario, hardware and software environment and accessing into MCR v2.0 are introduced to ensure completeness of the report. The report is finalized with a conclusion and outlook on future work. Page 5 of 36

6 TABLE OF CONTENTS CHANGE HISTORY... 4 EXECUTIVE SUMMARY... 5 TABLE OF CONTENTS... 6 LIST OF ABBREVIATIONS... 8 LIST OF FIGURES... 9 LIST OF TABLES INTRODUCTION USER REQUIREMENTS AND SHORTCOMINGS OF FIRST PROTOTYPE NEW FEATURES Multi Language Support New Language Context into Generic User Interface New Language Context in Meta- model New Language Context in MFBs Usage Single- Sing- On Usage New Start Page New Look & Feel Package Copy & Paste Feature Usage ADAPTATIONS ON EXISTING FEATURES Adaptations on Mission Control Room Modeller User Interaction layer Functional Layer Adaptations on Mission Control Room Assistant Functional layer Adaptation on Mission Control Room Monitoring User Interaction Layer Functional Layer Adaptation on SMK and Component API DEPLOYMENT OF MISSION CONTROL ROOM Page 6 of 36

7 5.1 Deployment Scenario Hardware and software Environment How to Access into Mission Control Room CONCLUSION AND OUTLOOK REFERENCES Page 7 of 36

8 LIST OF ABBREVIATIONS AJAX API AServer BIS CSS DTD Interref JSP KPI MCR MFB PIKR SMK SOAP SSO VE VEMF VIF VPS Asynchronous JavaScript and XML Application Programming Interface ADOxx Application Server Business Innovation Space Cascading Style Sheets Document Type Definition Inter reference to reference model objects from different models or model objects with models Java Servlet Pages Key Performance Indicator Mission Control Room Method and Functionality Building Block Production and Innovation Knowledge Repository Semantic Modelling Kernel Simple Object Access Protocol Single- sign- on Virtual Enterprise Virtual Enterprise Modelling Framework Virtual Innovation Factory Value Production Space Page 8 of 36

9 LIST OF FIGURES Figure 1: Spanish Language Context in User Interface Samples Figure 2: Spanish Language Context in Meta model Sample Figure 3: Spanish Language Context in MCR Start page MFB Figure 4: Spanish Language Context in MCR Modeller MFB Figure 5: Spanish Language Context in MCR Assistant MFB Figure 6: Spanish Language Context in MCR Monitor MFB Figure 7: Selection of Language Context in MCR Figure 8: Interactions between Web Browser, BIVEE SSO Service and MCR during the Login Process Figure 9: Sequence of Login from User's Point of View Figure 10: New Start Page Figure 11: Alignment of Look & Feel between BIVEE Platform and MCR Figure 12: Copy & Paste Model Content Figure 13: New Preferences and Date Pick Panel in MCR Modeller for KPI Models Figure 14: Resizable and Decoupled Notebook Figure 15: New Approach to set Interref Figure 16: KPI Model Selection Panel and Date Pick Panel in MCR Monitoring Figure 17: Deployment Diagram of the MCR Page 9 of 36

10 LIST OF TABLES Table 1 Details of Translation Package for Generic User interface Table 2: Details of Translation for Package for Meta- model Table 3: Details of Translation for Package for MFBs Page 10 of 36

11 1 INTRODUCTION This is the short report of delivered second prototype Mission Control Room by deploying on BOC servers and allowing online access. This report has a nature of delta report, since this report is the complementary of report D3.21 [1], which reports new features that are added, adaptations made on the existing features due to requirements arose during the evaluation of first prototype of Mission Control Room (MCR). After short introduction, in chapter 2, the requirements that arose during the evaluation of the first prototype are revisited and summarized within two categories; (1) End- User requirements and (2) Technical- User requirements. In chapter 3, new features (1) Multi Language Support, (2) Single- Sign- On, (3) New Start Page, (4) New Look & Feel and (5) Copy & Paste are introduced, their realization and usage are shortly described. In chapter 4, adaptations made on existing features are introduced by classifying them according to MCR components; (1) MCR Modeller, (2) MCR Assistant, (3) MCR Monitoring and (4) SMK and Component APIs. Then in chapter 5, the deployment of second prototype of MCR is introduced with giving overview of (1) deployment scenario,(2) hardware and software environment and (3) accessing into second prototype with new login scenario and BIVEE Central Authentication System. And finally, in chapter 6, short conclusion and overview of future work are given. Page 11 of 36

12 2 USER REQUIREMENTS AND SHORTCOMINGS OF FIRST PROTOTYPE In this chapter user- requirements (end- and technical- user requirements) and shortcomings that have been discussed and agreed in Plenary Meetings in Valencia between th of September 2013, in Rome between th of January 2014, the requirements and shortcomings that are reported by s, during webinars, by monthly reports within the Second Monitoring Campaign, of which results have been collected in deliverable [2] are revisited and shortly described. Moreover, the requirements reported in deliverable [3] and pilot application cases in [4] have been revisited again. Addition to that, technical requirements in order to utilize BIVEE services that are reported in [5] and technical requirements caused by changes in services from other components have been also revisited and described in separated category. All requirements from end- users and technical- users, which are considered during the development of MCR 2.0 are as following. End- user Requirements: Spanish language context in MCR: It has been a specific request of AIDIMA to provide a Spanish language pack for the MCR, because a considerable share of the members of AIDIMA s business environment are not used to English language. This requirement has been communicated during the BIVEE General Assembly in Valencia during 17-18th September of Single- sign- on (SSO): in order to improve the usability of all BIVEE tools, a central au- thentication service has been defined as a requirement. A complete implementation of a SSO would allow to use central authentication system, which means users do not have to create accounts for each component of BIVEE or give their information to each system, but to just one central system or even with binding their user repositories with this central system. And also users want to switch between the BIVEE Components without re- entering login details and may thereby shorten the time to access. This re- quirement has been described in [6], section UC1.4 Login. Intuitive navigation: The navigation within the MCR is supposed to be largely self- explaining by using a navigation that can be used as similar as possible to current state- of- the- art operational systems. Among this general requirement, scenario based content, copy & paste functions and selection of values rather than entering them manually have been described specifically. This requirement has been communicated during the BIVEE General Assembly in Valencia during th September of Page 12 of 36

13 Graphical User Interface (GUI): following the requirements of an intuitive navigation and multi- language support, the interface should rather be based on graphics than on numbers and text to allow easy access. This especially applies to the graphical visuali- sation of numeric data. This requirement has been described in [6], section UC6.3.3 Presentation, and improvement request made during the evaluation period and reported during BIVEE General Assembly in Rome during th January of Tutorial scenarios: in order to make the BIVEE tools more appealing to new VE mem- bers and potential new users, generic tutorial scenarios shall be used to explain func- tionalities. For the MCR, this user- guide should specifically cover the Virtual Enter- prise Design and Virtual Enterprise Monitoring in the MCR. This requirement be- came apparent and was communicated during the Review Meeting in Ancona during 9-10 th of October 2013 and specified concretely during the Second Monitoring Cam- paign. in. BIVEE Look & Feel Alignment: The BIVEE platform is supposed to provide a consistent look & feel. The design and functionalities of the MCR therefore need to be consistent with the VIF. This requirement has been agreed during the BIVEE Integration Work- shop in Rome during 4-5 th of July Technical- user Requirements Integration of BIVEE SSO into MCR. As MCR utilizes central authentication system pro- vided by BIVEE Platform, technical requirements reported in [6] need to be consid- ered. Adaptation requirements that are caused by changes in PIKR service description. In order to integrate Spanish- language context into MCR and enable SSO MCR should be migrated into new ADOxx release which caused following requirements Re- implementation of SMK and Component APIs Refactoring of source code of MFBs, which provide functionalities of MCR Page 13 of 36

14 3 NEW FEATURES According to aforementioned requirements, MCR has been enhanced with new features like (1)Multi- Language Support, (2)Single- Sign- On,(3)New Start page, (4) New Look & Feel package, and (5) Copy & paste feature. In following section these new features, their realization and usage are introduced. 3.1 Multi Language Support During the evaluation of first prototype, Spanish users requested to able to use Mission Control Room in their native language. Although fulfilment of this requirement was not obligated by DoW [7], It is decided by the consortium that requirement has higher priority and it should be fulfilled, since language support will bring highly valuable advantages to end- users while using Mission Control Room. Since fulfilment of this requirement requires significant effort, we have decided not to spend whole effort only integration of just one language context but to use a generic framework and regarding mechanisms that make possible integration of not just Spanish language context but also other language contexts upon request. Hence, we decided to migrate MCR onto new ADOxx release, since it allows such a framework. Possible scenarios and requirements in order to provide Multi Language Support have been analyzed and we have decided for following three- phase- scenario; 1. Add new language context into generic UI 2. Add new language context into meta- model 3. Add new language context into MFBs, which provides functions of the MCR components For each phase individual translation packages have been prepared, on what language packages can be build. Following sub- section introduces package and process followed in each phase New Language Context into Generic User Interface With Generic User Interface, the generic user interface of ADOxx is ment, which consist of standard user interface items, information-, warning- and error- messages, etc. For this phase a package with regarding property and DTD files are prepared, which consist of strings that should be translated by the following translation guide provided in the package. Package Nature Translation Package for Generic User Interface Content Source Language Required Skills 12 Property Files, 3 DTD Files and Translation Guide English English Language- and Target Language- Page 14 of 36

15 Knowledge Table 1 Details of Translation Package for Generic User interface AIDIMA provided required skills and translated the files in Spanish- Language Package. Samples of Spanish language context on the generic user interface can be seen on Figure 1. Figure 1: Spanish Language Context in User Interface Samples New Language Context in Meta- model The most complicated part of the integration of new language context into MCR is integration of new language Context into Meta- model, which means integration of new language context into syntax, semantics and notation of modelling language of VPS Modelling Method. Due to facts mentioned above, this phase requires a package, which consists of files that can be translated with minimum skills and without knowledge of VPS meta model but still able to integrate new language context in the meta- model. Therefore, a mechanism has been utilized, which is able to prepare the meta- model- translation file in XML format, exports the file and then imports translated file and integrates new language context in the meta- model accordingly. A package that consists of the meta- model- translation file and related translation guide has been prepared. Package Nature Content Source Language Translation Package for Meta- model 1 XML file and Translation Guide English Required Skills English Language-, Target Language- Knowledge and XML Basics Page 15 of 36

16 Table 2: Details of Translation for Package for Meta- model AIDIMA provided required skills and translated the files and delivered Spanish- Language Package. The Figure 2 depicts the notebook of the class Process and its attributes from VPS Meta- model, which gives an idea about Spanish language context in the meta- model. Figure 2: Spanish Language Context in Meta model Sample New Language Context in MFBs As matter of course, the VPS specific mechanisms of the modelling method are highly depended to the syntax and semantics of the modelling language. After integration of new language context into the meta- model the mechanisms, which are placed in MFBs should be decoupled from natural- language context. For that issue, first of all, source code in MFBs have been refactored, so they do not have natural- language- context dependency and they can work with each language- context in the meta- model. Secondly, user interface items; (such as menu items, info-, warning- and error messages) refactored, so they can reflect strings in each natural- language- context. A similar translation package like the package in the first phase has been prepared. Page 16 of 36

17 Package Nature Content Source Language Translation Package for MFBs 3 Property Files and a Translation Guide English Required Skills English Language-, Target Language- Knowledge. Table 3: Details of Translation for Package for MFBs AIDIMA provided required skills and translated the files and delivered Spanish- Language Package. Samples of Spanish language context on MCR Start Page, MCR Modeller, MCR Assistant and MCR Monitoring, which are the components implemented by regarding MFBs, can be seen in Figure 3, Figure 4, Figure 5 and Figure 6 respectively. Figure 3: Spanish Language Context in MCR Start page MFB Page 17 of 36

18 Figure 4: Spanish Language Context in MCR Modeller MFB Figure 5: Spanish Language Context in MCR Assistant MFB Page 18 of 36

19 Figure 6: Spanish Language Context in MCR Monitor MFB Usage The MCR supports at the moment two language context fully (1) English, (2) Spanish and one language context partially (3) German. In order to change language context of MCR- as depicted in Figure 7 - users need to click on settings button, select menu item Language ( Idioma in Spanish, Sprache in German) and then select one of three languages. Figure 7: Selection of Language Context in MCR Page 19 of 36

20 3.2 Single- Sing- On Based on requirement to have central authentication, a service so- called BIVEE- Single- Sign- On service has been implemented in WP6. Technical requirements, in order to utilize this service by BIVEE Components (MCR, VIF and PIKR), has been listed in [6]. In order to fulfil those technical requirements following actions have been taken in the MCR; MCR has been migrated into new ADOxx Release. Since the new ADOxx release allows SSO scenarios, MCR has been migrated into new ADOxx release. A new login scenario has been implemented. Since Central Authentication Service by JA- SIG (CAS) login scenario was not complying with MCR s login scenario, we have implemented new login scenario complying with CAS requirements. The new login scenario consists of, implementation of a valve based on valve provided by ADOxx, servlet and regarding java servlet pages. CAS Client has been integrated into MCR. In order to enable required interaction between BIVEE CAS Server and MCR, regarding CAS Client for Java 3.1 [8] has been integrated into MCR MCR has been re- configured. In order to allow interaction between MCR and BIVEE CAS Server, MCR has been re- configured according to configuration requirements of BIVEE CAS Server. For the configuration of MCR both configuration requirements that are described by JA- SIG[9] and described in [5]. The interaction as depicted in Figure 8 has been established. As the user sends request to the MCR, MCR redirects the user to login form of the BIVEE SSO Service and user enters her/his user id and password. BIVEE SSO service redirects user to MCR with an authentication token, MCR requests verification of the token from BIVEE SSO Service, BIVEE SSO Service verifies the token and sends to MCR a verification response and the user data. MCR communicates with user management component on the application server side and request to open a valid session for the user, MCR User Management Component opens a valid session and sends a response. MCR opens this valid session for the user.after that point user is allowed to access protected resources of MCR. Page 20 of 36

21 Figure 8: Interactions between Web Browser, BIVEE SSO Service and MCR during the Login Process Usage The usage of SSO Service and regarding sequence from users point of view is depicted in Figure 9. Firstly, after request made to log into MCR by user, the user receives login page from BIVEE SSO service. Secondly, after user enters her/his credentials, she/he will receive a notification that she/he is being forwarded to the MCR and in third step she/he lands on the MCR with valid session. Page 21 of 36

22 3.3 New Start Page Figure 9: Sequence of Login from User's Point of View Based on the requirement of more intuitive, easier navigation among to scenarios a new start page with more intuitive concepts, which aims to ease the usage of MCR and understand the scenarios Design of Virtual Enterprise, Execution of Virtual Enterprise and Monitoring of Virtual Enterprise, has been implemented. The new start page has been designed as minimalist as possible and to give feeling of a desktop. As depicted in Figure 10 the new start page consists of three scenario portlets and toolbar consists of menu items reserved for each scenario. Those three scenario portlets consist of relevant functionality to each scenario have been integrated. As one of the scenarios is selected by clicking either on scenario portlet or regarding menu item on the tool bar, the start page smoothly slides to the scenario page with main panel and a tool bar consists of functionalities with regard to the selected scenario. Page 22 of 36

23 Figure 10: New Start Page The new start page is implemented with following new framework by ADOxx. The new framework allows us to add and remove scenario- portlets. 3.4 New Look & Feel Package According to requirement Alignment of Look & Feel of all BIVEE Components made by consortium following actions have been taken in the MCR; ExtJS Theming Package has been implemented. Since ADOxx follows ExtJS framework by Sencha [10] for GUI implementation, base GUI components of MCR are based on that framework. Within this framework each theming requires its own theming packages following theming framework by Sencha as described in [11]. Due to fact that, an ExtJS theming package for base GUI complying with style definition made by WP6 has been implemented on the Sencha Development environment. Style definitions of MFBs have been adapted. The MFBs consists of additional style definitions independent from ExtJS theming package. These style definitions have been adapted again according to style definition variables by WP6. As a sample of look & feel alignment between BIVEE Platform and MCR in Figure 11 home page of BIVEE Platform and Start page of MCR are depicted. Page 23 of 36

24 Figure 11: Alignment of Look & Feel between BIVEE Platform and MCR 3.5 Copy & Paste Feature End- users reported that during the modelling to able select and copy some parts of model content into another model will significantly accelerate and ease their job. Copy & Paste mechanism allows copying part of model content or whole model content with mouse and short cuts. The copying model content means, copying objects, all attribute values of objects, references, and connectors between objects. Before pasting, a mechanism decides, if copied types of objects belong to model type of the model, where the objects shall be paste in. With other words if the object types are included in the meta- model part of given model type, user will be allowed to paste the copied objects in the model from given model type, otherwise not. Page 24 of 36

25 3.5.1 Usage Figure 12: Copy & Paste Model Content The usage of Copy & Paste mechanism is self- evident and allows using same shorts cuts as users are used to use on well- known application. The user can copy the model content with using short cut CTRL+A to select all content, or selecting with mouse partial content and with CTRL+C copy the content, then with CTRL+V paste the content in the model, which has the same model type as model, where the content has been copied from. Page 25 of 36

26 4 ADAPTATIONS ON EXISTING FEATURES Migration of MCR into ADOxx new release brought additional requirements of updating and refactoring of (1) Meta- model and (2) Implementation of all functionalities covered by MFBs. Meta- model has been adapted according to changes in the meta²- model of ADOxx, which arose additional adaptation on the functionalities. Although the meta model has been adapted, it is still correspond to specification described in [12]. Since MFB framework has been updated in the ADOxx new release, MFBs of MCR have been aligned with the new framework, which required refactoring source code. Besides abovementioned adaptations, following adaptations have been made particular to each component of MCR as reported shortly in next sections. 4.1 Adaptations on Mission Control Room Modeller User Interaction layer According to requirement Intuitive navigation date pick up panels (as depicted in Figure 13) has been implemented complying with ExtJS 4. These panels can be used with the different language context, which are included into MCR. Figure 13: New Preferences and Date Pick Panel in MCR Modeller for KPI Models Instead of a fixed coupled panel, new Notebook panel (as depicted in Figure 14) is a decoupled panel from modelling area panel, it can be minimized, maximized, moved and resized, which ease modelling experience. Page 26 of 36

27 4.1.2 Functional Layer Figure 14: Resizable and Decoupled Notebook In MCR 2.0 setting of interref, from object to model, from object to object, and from model to object have been made easier. In MCR 2.0 user need to click + button, and a mechanism will check all repository and make list of concepts, which are appropriate to context. The user selects corresponding concept from the list and the mechanisms sets reference between concepts as aforementioned. Page 27 of 36

28 Figure 15: New Approach to set Interref Moreover, since the service description of some of PIKR Services has been changed, the MCR Modeller functions that are interacting with those services have been adapted accordingly. 4.2 Adaptations on Mission Control Room Assistant Functional layer Based on the changes in the new ADOxx release, the mechanism that builds Table of Content with models from appropriate model types has been re- implemented Moreover, MCR Assistant functions that utilize PIKR services have been adapted according to changes made on service description. As a result of migration into new ADOxx release, we had to drop out image map on the right panel of the MCR Assistant. Page 28 of 36

29 4.3 Adaptation on Mission Control Room Monitoring User Interaction Layer As mentioned in sub- subsection 4.1.1, a again according to requirement Intuitive navigation date pick up panels (as depicted in Figure 16) has been implemented complying with ExtJS 4. These panels can be used with the language context, which are included into MCR. Moreover, it is requested and classified as major-issue by end-users, to solve issue of "Texting KPI model names manually in MCR Monitoring". With regard to that, a mechanism has been implemented, which retrieves regarding models from model repository and prepares for selection by users. For selection on the user interaction layer a combo box complying with ExtJS 4 has been implemented. Users can select a KPI model from a combo box. # Figure 16: KPI Model Selection Panel and Date Pick Panel in MCR Monitoring Functional Layer Because of new security policy complying with cloud application security standards, new ADOxx release does not allow to use Get method of HTTP protocol. Hence, web methods that allow GET method calls based on SOAP standards have been refactored, so they accept PUT method calls of HTTP protocols. Accordingly, AJAX calls on the web client side have been refactored from GET to PUT method. 4.4 Adaptation on SMK and Component API All APIs in SMK and Component API had been implemented with using GET method from HTTP protocol and was allowing communication with the web methods of MCR without authentication. As mentioned before the new ADOxx release does not allow GET Methods of HTTP protocol, and does not allow calling web methods on server side without authentication. Page 29 of 36

30 In order to solve this issue, it has been decided to re- implement all APIs as RESTful services. Therefore, a framework to create and register RESTful services provided by new ADOxx release has been utilized. And then all APIs have been re- factored as RESTful services. Page 30 of 36

31 5 DEPLOYMENT OF MISSION CONTROL ROOM 5.1 Deployment Scenario The aserver (ADOxx Application Server), component of the ADOxx meta- modelling platform accesses the ADOxx database on a dedicated database server. The ADOxx application server contains the functionality for the web scenario. In addition, a web server is needed which takes over the communication between the client computers and the application server. On the server side, the Administration Toolkit contains the functionality for user management, database management and repository management. Figure 17 depicts the setting and deployment environment of MCR in a deployment diagram. Page 31 of 36

32 Figure 17: Deployment Diagram of the MCR 5.2 Hardware and software Environment The client workstation requires a web browser. The best results are obtained when using Mozilla Firefox version 25.0 or later, Mozilla Firefox ESR version or later, Microsoft Internet Explorer 9.0 or later, respectively Google Chrome 25.0 or later. The web server, accessible over the internet, has a Linux operating system (Ubuntu Linux version ) installed. On the Linux operating system, an Apache HTTP Server version 2.2 and an Apache Tomcat Server version are installed. MCR web application is deployed to Page 32 of 36

33 the Apache Tomcat Server. In the configuration file of the MCR web application, the IP address and port of the aserver have to be provided to establish communication between web application and certain aserver. MCR Administration Toolkit and components of the MCR are running on MS windows based operating system installed server. The recommended hardware requirements for installing the ADOxx platform, that MCR developed on, include Pentium 4 or similar processor with a speed of 1.4 GHz or better, 2048MB of RAM, 2500 MB of hard- disk space. The database server runs on a MS windows based operating system where a Microsoft SQL Server 2008 is installed. The MCR database has been initialized using the ADOxx Database Administration Tool, part of the ADOxx platform. 5.3 How to Access into Mission Control Room In order to login into MCR 2.0 with new login scenario please use following link; As described in section 3.2 MCR 2.0 utilizes BIVEE SSO. Therefore, the users, who want to login into MCR has to be authenticated by BIVEE SSO and hence need to be a registered user in one of user repositories, with which BIVEE SSO interacts. Page 33 of 36

34 6 CONCLUSION AND OUTLOOK As stated before, this report is complementary of the report D3.21[1]. Therefore requirements that considered in that report and design considerations are valid for this report as well. Complementary to features reported in the report D3.21[1], we have presented new additional features and adaptations made on existing features in this report Due to above mentioned facts, the end- user requirements arose during the evaluation of first prototype, and during the Second Monitoring Campaign have been revisited and summarized. Addition to end- user- requirements, requirements from technical- users arose due to integration reasons, changes on the other BIVEE components and migration onto ADOxx new release has been considered and revisited. The new features that have been implemented based on above mentioned requirements have been listed and reported. The usages of these features have been introduced, shortly. Moreover, adaptations made on existing features, which have been made due to end- user- requirements, technical- user- requirements and migration into the new ADOxx release, have been reported. One of the requirements by end- users was a tutorial describing have to use MCR regarding to scenarios Virtual Enterprise Design and Virtual Enterprise Monitoring. Regarding to the description in the DoW[7], it has been decided by partners involved in WP3 and by end- users that this tutorial should be realized in task T3.3. With respect to this issue structure of tutorial with following end- users comments and suggestion have been defined and currently being realized in task T3.3. BOC considers developing a commercial tool out of the MCR prototype, hence the final tool will be a licenced software. In order to disseminate MCR prototype, BOC has two strategies: First the current prototype will be hosted for a reasonable time as a service, enabling interested members to test the tool. With the regards to that, as the first step a landing page ( has been launched, where overview, user- guides and access information of MCR will be found. Second, in order to disseminate the meta model of BIVEE, an open use tool will be provided in the academic framework open models ( or adoxx.org ( Page 34 of 36

35 REFERENCES [1] N. Efendioglu, R. Woitsch, A. Solomon, S. Popescu and F. C. Moreno, Mission Control Room Prototype (v1.0), Deliverable D3.21, BIVEE European Project, [2] V. Basar, A. Sinaci, A. Dogac, C. Cristalli, M. Piersantelli, G. Ward and F. Gigante, Analysis of User Requirements, Deliverable D6.12, BIVEE European Project, [3] A. Sinaci, A. Pacaci, C. Cristalli and D. G. F. Isidori, Results of the Monitoring Campaing (r2.0), Deliverable d7.31, BIVEE European Project, [4] A. Sinaci, V. Basar, C. Cristalli, M. Piersantelli, F. Gigante, A. Roca de Togores, M. Belanche, V. Leon and G. Ward, Analysis of User Requirements, Deliverable D6.11., BIVEE European Project, [5] C. Cristalli, M. Piersantelli, A. Sinaci, V. Basar, F. Gigante, V. Leon, P. Crespi and G. Ward, Definition of BIVEE Pilot Application Validation Cases (r1.0), Deliverable D7.11, BIVEE European Project, [6] M. Isaja, M. C. Mantuano, F. Smith, N. Efendioglu and F. C. Moreno, BIVEE Environment prototype (v2.0), Deliverable D6.32,, BIVEE European Project, [7] BIVEE Project Consortium, BIVEE Project Grant Agreement - Annex- I - Description of Work, [8] JA- SIG, CAS Client for JAva 3.1, [Online]. Available: [Accessed ]. [9] JA- SIG, Configuring the Jasig CAS Client for Java in the web.xml, [Online]. Available: eb.xml. [Accessed ]. [10 ] [11 ] [12 ] [13 ] Secha, Ext JS Sencha Docs, [Online]. Available: [Accessed ]. Sencha, Theming Ext JS, [Online]. Available: [Accessed ]. R. Woitsch, N. Efendioglu, B. Knoke and J. H. Verdu, State of the Art and Mission Control Room Specification, Deliverable D3.1., BIVEE European project, A. Rossi, B. Knoke, N. Efendioglu and R. Woitsch, Specification of business innovation reference frameworks (in the context of the VEMF), Deliverable 2.2., BIVEE European Project, Page 35 of 36

36 Page 36 of 36