Some remarks on Portals and Web Services NCSA All Hands May 9 2002 PTLIU Laboratory for Community Grids Geoffrey Fox Computer Science, Informatics, Physics Indiana University, Bloomington IN 47404 http://grids.ucs.indiana.edu/ptliupages/presentations gcf@indiana.edu 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Web Services in a Nutshell Application or Content source WSDL Web Service Ports: Messages to and from other web services, resources or users Web Services codify a clear process for deploying distributed software components representing Data and Information Sources (Sensors, Databases) Computers Application Software System services (OGSA Open Grid Service Architecture) Distributed Message Passing Model We should be in some process of dividing applications into components and giving them an XML “skin” defining input and output ports (data, remote procedure calls) WSDL Web Service Definition Language 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Example of Application Web Services Note Service model integrates sensors, sensor analysis, simulations and people An Application Web Service is a capability used either by another service or by a user It has input and output ports – data is from users, sensors or other services Big services built hierarchically from “basic” services Sensor Data as a Web service (WS) Data Analysis WS Sensor Management WS Visualization WS Simulation WS Data Management WS 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Application Web Services Filter1 WS Filter2 WS Filter3 WS Build as multiple Filter Web Services Prog1 WS Prog2 WS Build as multiple interdisciplinary Programs Data Analysis WS Simulation WS Visualization WS Note Service model integrates sensors, sensor analysis, simulations and people An Application Web Service is a capability used either by another service or by a user It has input and output ports – data is from users, sensors or other services Big services built hierarchically from “basic” services Sensor Data as a Web service (WS) Data Analysis WS Sensor Management WS Visualization WS Simulation WS Data Management WS 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

XML Specified Resources connected by XML Specified messages XML Skin XML Skin Message Or Event Based Inter Connection Soft ware Resource Soft ware Resource Data base XML Specified Resources connected by XML Specified messages Implementation of resource and connection may or may not be XML 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Web Services as a Portlet Each Web Service naturally has a user interface specified as “just another port” Customizable for universal access This gives each Web Service a Portlet view specified (in XML as always) by WSRP (Web services for Remote Portals) So component model for resources “automatically” gives a component model for user interfaces When you build your application, you define portlet at same time Application or Content source WSDL Web Service S R W P Application as a WS General Application Ports Interface with other Web Services User Face of Web Service WSRP Ports define WS as a Portlet WSRP is Web Services for Remote Portals 1st Meeting OASIS March 18 2002 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Integration of Portlets Portals integrate Portlets into a complete user interface Apache Jetspeed seems good open source technology supporting this model Application as a WS General Application Ports Interface with other Web Services Client Render Application or Content source WSDL Web Service Portal User Profile Aggregate UI Fragments S R W P Integrate Multiple Portlets User Customization at either Portal or if complicated at WS User Face of Web Service WSRP Ports define WS as a Portlet 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Online Knowledge Center built from Portlets A set of UI Components Web Services provide a component model for the middleware (see large “common component architecture” effort in Dept. of Energy) Should match each WSDL component with a corresponding user interface component Thus one “must use” a component model for the portal with again an XML specification (portalML) of portal component 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Jetspeed Computing Portal: Choose Portlets 4 available portlets linking to Web Services I choose two 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Choose Portlet Layout Choose 1-column Layout Original 2-column Layout 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

Two Computing Portlets 11/11/2018 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"