1 / 11

Some remarks on Portals and Web Services

NCSA All Hands May 9 2002. Some remarks on Portals and Web Services. 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. WSDL.

lbeaman
Télécharger la présentation

Some remarks on Portals and Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. WSDL Application orContent source Web Service Web Services in a Nutshell • 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 Ports: Messages to and fromother web services, resourcesor users uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  3. Data Analysis WS Sensor Data as a Webservice (WS) Simulation WS Visualization WS Sensor ManagementWS 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 Data Management WS uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  4. Prog1WS Prog2WS Filter1WS Filter2WS Filter3WS Build as multiple interdisciplinaryPrograms Build as multiple Filter Web Services Data Analysis WS Data Analysis WS Sensor Data as a Webservice (WS) Simulation WS Simulation WS Visualization WS Visualization WS Sensor ManagementWS 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 Data Management WS uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  5. XMLSkin XMLSkin Data base XML Specified Resourcesconnected by XML Specified messages Message Or Event Based InterConnection Software Resource Software Resource Implementation of resource and connection may or may not be XML uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  6. Application as a WSGeneral Application PortsInterface with other WebServices WSDL W S Application orContent source R P Web Service User Face ofWeb ServiceWSRP Ports define WS as a Portlet 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 portletat same time WSRP isWeb Services for Remote Portals1st Meeting OASIS March 18 2002 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  7. WSDL W S Application orContent source R P ClientRender Web Service Integration of Portlets • Portals integrate Portlets into a complete user interface • Apache Jetspeed seems good open source technology supporting this model Application as a WSGeneral Application PortsInterface with other WebServices PortalUser ProfileAggregateUI Fragments Integrate Multiple Portlets User Customizationat either Portal or if complicated at WS User Face ofWeb ServiceWSRP Ports define WS as a Portlet uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  8. Online Knowledge Center built from Portlets A set of UIComponents • 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 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

  9. 4 available portletslinking to Web ServicesI choose two Jetspeed Computing Portal: Choose Portlets uri="http://grids.ucs.indiana.edu/ptliupages/presentations/" email="gcf@indiana.edu"

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

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

More Related