Extend user interfaces with new portlets Marco Fargetta - marco.Fargetta@ct.infn.it Riccardo Bruno - riccardo.Bruno@ct.infn.it RIA-653549 Uso del software INDIGO-DataCloud in ambito scientifico Bari, 21 July 2017

Extend user interfaces with new portlets INDIGO User Interface The FutureGateway framework makes easier to create user interfaces for the INDIGO-DataCloude services Web User Interface is based on Liferay Application Portal Framework A Java portal supporting OSGi specifications It is possible to create portals with other technologies Some use cases/applications have their own user interface to maintain Literacy components cannot be re-used Toolkit for desktop/mobile application available 21/07/2017 Extend user interfaces with new portlets

Create a portal: Liferay Plugins A collection of Liferay plugins released in INDIGO Integrate in Liferay the following features: IAM token management FG management Customisable application portlet Source: https://github.com/indigo-dc/LiferayPlugIns Binary: http://repo.indigo-datacloud.eu/repository/indigo/2/centos7/x86_64/tgz/LiferayPlugins-binary-2.0.2.tgz Consist of 6 modules 21/07/2017 Extend user interfaces with new portlets

IAM Authentication modules Provide authentication with IAM Allow token access to other components Access possible at server and client side Provide token information for the FG backend By several APIs the FG can use to verify the token validity 21/07/2017 Extend user interfaces with new portlets

IAM Authentication - configuration 21/07/2017 Extend user interfaces with new portlets

IAM Authentication - authentication 21/07/2017 Extend user interfaces with new portlets

IAM Authentication - Token 21/07/2017 Extend user interfaces with new portlets

IAM Authentication - API 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets FG management Show user activities Provide a view on user tasks Currently no actions are supported against user operations Edit applications/infrastructures configured in the FG back-end Allow to configure the applications used in the portal 21/07/2017 Extend user interfaces with new portlets

FG management - Monitoring 21/07/2017 Extend user interfaces with new portlets

FG management - Monitoring 21/07/2017 Extend user interfaces with new portlets

FG management - Editing 21/07/2017 Extend user interfaces with new portlets

Customisable application portlet Customisable portlet to support many different applications Administrator has to provide an interface description Integrate with the FG TOSCA based deployment supported Other infrastructures not fully supported yet 21/07/2017 Extend user interfaces with new portlets

Customisable application portlet - Interface 21/07/2017 Extend user interfaces with new portlets

Customisable application portlet - Customisation 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets Authorisations Liferay manage groups and roles Groups are associated with IAM groups Customisation and management can be delegated by the administrator to a group of users Create specific roles enabling these activities and assign the users Some actions could require special configuration in the backend FG services 21/07/2017 Extend user interfaces with new portlets

How to develop a new portlet Some applications could require a more complex interface An ad-hoc portlet has to be develop A portlet can be developed from scratch following Liferay indications The main code can be client side, server side or both Server side portlets are in Java and have to follow OSGi specifications Client side can exploit any JS framework but the integration could be difficult The tooling is based on Gradle For details: https://dev.liferay.com/develop/tutorials Components and services can be shared among portlets Token management Interaction with FG services 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets Other interfaces The PSNC is developing A mobile toolkit for iOS and Android A Kepler module for workflow The mobile toolkit has been tested with a use case ENES climate change Kepler modules allow to integrate processing steps on INDIGO platform inside a workflow Component developed to interact with the FG Available in INDIGO-DataCloud release 21/07/2017 Extend user interfaces with new portlets

Other interfaces - Mobile Indigo OMT is a set of libraries to give mobile programmers easier start to implement mobile applications based on INDIGO DataCloud API. Basing on the existing FG API, library for Android and a sample applications which helps to show the features. New iOS library and sample applications Current version of the library handles exposed FG operations. The sample app shows these operations as well. Example - ENES app using the OMT https://youtu.be/fexYm74kjRs https://youtu.be/g1NdJUheTfY 21/07/2017 Extend user interfaces with new portlets

Other interfaces - Kepler 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets Questions? 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets A Liferay portlet A portlet provide a fragment in a web page Has its own lifecycle It is rendered every time a is loaded After an action is performed in one of the portlet available Many kind of portlet available Differences are mainly in the development Internal frameworks, tools, etc… 21/07/2017 Extend user interfaces with new portlets

Extend user interfaces with new portlets A Liferay MVC portlet @Component( immediate = true, property = { "com.liferay.portlet.display-category=category.sample", "com.liferay.portlet.instanceable=true", "javax.portlet.display-name=Liferay MVC Portlet", "javax.portlet.init-param.template-path=/", "javax.portlet.init-param.view-template=/view.jsp", "javax.portlet.resource-bundle=content.Language", "javax.portlet.security-role-ref=power-user,user" }, service = Portlet.class ) public class LiferayMVCPortlet extends MVCPortlet { } 21/07/2017 Extend user interfaces with new portlets

Portlet commands – action example @Component( immediate = true, property = { "javax.portlet.name=MyTestPortlet", "mvc.command.name=/port/edit_entry" }, service = MVCActionCommand.class ) public class EditEntryMVCActionCommand extends BaseMVCActionCommand { // the app's edit blog entry action implementation } <portlet:actionURL name="/port/edit_entry" var="editEntryURL" /> JSP link to the action Action class 21/07/2017 Extend user interfaces with new portlets