EPES Service Generator Module (SGM)

Service Generator Module (SGM) The Service Generator Module (SGM) supports the user in creating, updating and deploying application-specific life-cycle services. The user has the possibility to define new services with a template from scratch, to adjust configurations of deployed services, to reflect changing conditions and to deploy the changed configurations. Within the SGM the user can analyze contextual information and previously taken decisions in order to update an existing configuration. Latter can be used to reconfigure a particular deployed application-specific service. The SGM has the following functionalities: • To provide a service runtime infrastructure for EPES, by acting as an intermediary and aggregator for the functionality offered by the SM and DMM • To enable the creation and update of configuration for deployed services. The configurations can be managed (storage/retrieval) by using the provided persistence services (persisting objects to the DB or files to the Cloud or to the VCN repository through the Content Management Interoperability Services (CMIS)) The SGM’s functionality is transparent to the human user, who interacts with the SGM through the so-called Cockpit, which is the Graphical User Interface Component of the SGM. The Cockpit is a Web-based GUI which acts as support for both major roles of the SGM: it aggregates the UIs of the other EPES modules into a common workspace, and it presents a view for changing the values of the parameters in services’ configurations. The SGM functionalities are accessible either through the Cockpit or through exposed RESTful public Web Services. The API can be utilized by other EPES modules and external systems. The provided functionalities include: • Configuration component, which enables configuration and deployment of existing services • Persistence related component, which provides CRUD type of functionalities for managing data in selected Cloud services, the VCN content repository by utilizing the CMIS interfaces or in a conventional DBMS • Interfaces to services provided by other EPES modules, e.g. the VCN Repository data storage services, optimization and simulation services provided by DMM and SM • Security component: The SGM handles the authentication services in EPES by providing a single point of authentication. Every request made through the web services or the GUI has to possess a valid authentication ticket. If no valid ticket is provided, the user must obtain a valid ticket by (re)authenticating The SGM takes into account the user context to refine Business Case-specific elements, such as KPI suggestions. The user context can be detected by the Context services bundled with the SGM.