Web Services and Peer-to-Peer Technologies for the Grid ICCS Amsterdam April 24 2002 PTLIU Laboratory for Community Grids Geoffrey Fox Computer Science, Informatics, Physics Indiana University,

Download Report

Transcript Web Services and Peer-to-Peer Technologies for the Grid ICCS Amsterdam April 24 2002 PTLIU Laboratory for Community Grids Geoffrey Fox Computer Science, Informatics, Physics Indiana University,

Web Services and Peer-to-Peer
Technologies for the Grid
ICCS Amsterdam April 24 2002
PTLIU Laboratory for Community Grids
Geoffrey Fox
Computer Science, Informatics, Physics
Indiana University, Bloomington IN 47404
http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02
[email protected]
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupag
es/presentations/iccsapril02"
email="[email protected]"
1
The Application Service Model






There are generic Grid system services: security, collaboration,
persistent storage, universal access
• OGSA (Open Grid Service Architecture) is implementing these as
extended Web Services
An Application Web Service is a capability used either by another
service or by a user
• It has input and output ports – fed by devices or other services
A service “is a component” and is a replacement for a library in case
where performance allows
Services (components) are a sustainable model of software development
– each service has documented capability with standards compliant
interfaces
• XML defines interfaces at several levels
• WSDL at Service interface level and XSIL or equivalent for scientific
data format
A service can be written as Perl, Python, Java Servlet, Enterprise
Javabean, CORBA (C++ or Fortran) Object …
Communication protocol can be RMI (Java), IIOP (CORBA) or SOAP
(HTTP, XML) ……
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
2
What is a Web Service I


A web service is a computer program running on either the local
or remote machine with a set of well defined interfaces (ports)
specified in XML (WSDL)
In principle, computer program can be in any language (Fortran
.. Java .. Perl .. Python) and the interfaces can be implemented in
any way what so ever
• Interfaces can be method calls, Java RMI Messages, CGI Web
invocations, totally compiled away (inlining) but



The simplest implementations involve XML messages (SOAP)
and programs written in net friendly languages like Java and
Python
Web Services separate the meaning of a port (message) interface
from its implementation
Enhances/Enables Re-usable component model of ANY
electronic resource
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
3
Raw
Resources
Raw Data
Raw Data
(Virtual) XML Data Interface
Web Service (WS)
WS
WS
WS
etc.
XML WS to WS Interfaces
WS
WS
WS
WS
WS
(Virtual) XML Knowledge (User) Interface
Render to XML Display Format
Clients
11/6/2015
(Virtual) XML
Rendering Interface
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
4
Classic Grid Architecture
Resources
Database
Database
Composition
Content Access
Netsolve
Security
Collaboration
Middle Tier
Brokers
Service Providers
Computing
Middle Tier becomes Web Services
11/6/2015
Clients
Users and Devices
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
5
What is a Web Service II



Web Services have important implication that ALL
interfaces are XML messages based. In contrast
Most Windows programs have interfaces defined as
interrupts due to user inputs (see WSIA and W3C
DOM)
Most software have interfaces defined as methods which
might be implemented as a message but this is often
NOT explicit
WSDL interfaces
Security
11/6/2015
Payment
Credit Card
Catalog
Warehouse
shipping
WSDL interfaces
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02"
email="[email protected]"
6
What is a Web Service III





This is a server NOT a client model
“Everything electronic” is a
resource (= distributed object or = service)
• Computers; Programs; People
• Data (from sensors to this presentation to email to
databases)
All resources have interfaces which are defined in XML for
both properties (data-structure) and methods (service,
function, subroutine)
• We can assume that a data-structure property has
getproperty() and setproperty(value) methods to act as
interface
All resources are linked by messages with structure, which
must be specifiable in XML
All resources have a URI such as unique://a/b/c …….
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
7
WSDL Abstractions


WSDL abstracts a program as an entity that does
something given one or more inputs with its results
defined by streams on one or more outputs.
Functions are defined by method name and
parameters
methodname(parm1,parm2, … parmN)
• Where parameters are “Input” “Output” or both

In WSDL, we will have a Web Service which like a
(Java or CORBA Program) can be thought of as a
(distributed) object with many methods
• Instead of a function call, the “calling routine” sends an
XML message to the Web Service specifying methodname
and values of the parameters
• Note name of function is just another parameter
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
8
Details of WSDL Protocol Stack







UDDI finds where programs are
• remote( (distributed) programs are
just Web Services
WSFL links programs together
(under revision?)
WSDL defines interface (methods,
parameters, data formats)
SOAP defines structure of message
including serialization of information
HTTP is negotiation/transport
protocol
TCP/IP is layers 3-4 of OSI
Physical Network is layer 1 of OSI
11/6/2015
UDDI or WSIL
WSFL
WSDL
SOAP or RMI
HTTP or SMTP
or IIOP or RMTP
TCP/IP
Physical Network
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
9
Examples of Web Services I




OGSA (Open Grid Service Architecture)
• Integrate Web Service and Grid Concepts and allows Globus
to be implemented as Web Services
Audio-Video Conferencing as a Web Service
• Integrates H323, SIP, JXTA (etc.) protocols by mapping to
single XML Interface
• Provides VRVS reflector model from Messaging Web Service
Messaging or Event Web Service provides intelligent routing and
buffering of messages
Computing as a Web service
• Job submittal, status, composition, data services, visualization
• Performance WS allows access to distributed monitoring
data, analysis, models, and final benchmarks with
interoperable XML interfaces
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
10
Examples of Web Services II

Education as a Web Service
• One of easiest to do as object standards well defined (IMS)
and little performance issues
• Grading, Homework submission, registration, assessment etc.

Universal Access and Web Services
• As Web Services allow multiple implementation of a
particular interface, one can adjust to needs of particular
clients (PDA v. versus, impaired sight etc.). See WSRP
• Can build custom implementations of certain web services for
particular communities but re-use others

Collaborative Web Services
• As interfaces all message based, much easier to share Web
Services than other applications (PowerPoint interface is
NOT message based and harder to share than server app)
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
11
Education as a Web Service














Can link to Science as a Web Service and substitute educational
modules
“Learning Object” XML standards already exist from IMS/ADL
http://www.adlnet.org – need to update architecture
Web Services for virtual university include:
Registration
Performance (grading)
Authoring of Curriculum
Online laboratories for real and virtual instruments
Homework submission
Quizzes of various types (multiple choice, random parameters)
Assessment data access and analysis
Synchronous Delivery of Curricula
Scheduling of courses and mentoring sessions
Asynchronous access, data-mining and knowledge discovery
Learning Plan agents to guide students and teachers
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
12
XML
Skin
Message
Or Event
Soft
Soft
Based
ware
ware
Inter
Connection
Resource
XML
Skin
Resource
Data
base
e-Science is XML Specified Resources
connected by XML specified messages
Implementation of resource and
connection may or may not be XML
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
13
Biased History of Computing




In almost the beginning, there was Fortran and formats
(6I5, 5F10.4) for data
…………………………..
1993-1997: HTML came along for Web Pages
1998-…: XML was developed to define information in
documents while HTML defining rendering
• But soon it became used for specifying all data and their
format


2001: Web Services allowed XML to specify methods
(subroutines) as well as data
Java, C++, Python, Perl, .. Fortran are now “just” the
insides of XML specified programs
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
14
How do we organize all this



As everything is a resource implemented as a Web
Service, we need a common description framework for
• back end supercomputers and a petabyte data
• Microsoft PowerPoint and this file
Grids tend to organize large back end resources but
peer to peer (P2P) technology more natural for the
digital equivalent of the scraps of information in each
of the multiple sub-communities in a “virtual
organization”
Grids and P2P approaches can be integrated by
building both in terms of Web Services with different
implementations of core services such as discovery, and
event or message transport/filter …..
• Use JXTA as “typical” P2P technology as architecture clear

Gives a Peer-to-Peer Grid
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
15
JXTA
Database
Database
Web Service Interfaces
Event/
Message
Brokers
Integrate P2P
and Grid/WS
Event/
Message
Brokers
Peer to Peer Grid
Web Service Interfaces
JXTA
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02"
email="[email protected]"
16
A
democratic
organization
Peer
to Peer Grid
Broker Network
For message/events service
Broker
(P2P) Community
Broker
(P2P) Community
Resource
Broker
Broker
(P2P) Community
Data
base
Broker
Software multicast
Broker
(P2P) Community
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
17
Event Web Service
Destination
Source Matching
Routing
Web
Service 1
WSDL
Ports




(Virtual)
Queue
Broker
Filter
workflow
Web
Service 2
WSDL
Ports
Filter is mapping to PDA or slow communication channel
(universal access) – see our PDA adaptor
Workflow natural as all messages “intercepted” by Event Web
Service
Routing illustrated by JXTA
Destination-Source matching illustrated by JMS
• Publish-subscribe
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
18
Messaging/Events as a Web Service

We can implement messaging subsystem (between
WSDL resources) with either direct messages or by a
queued system where you publish messages to queues
and subscribe as receiver to particular queues
• events are time stamped messages

There are many different publish/subscribe models
• JMS is a classic Grid-like cluster of central servers
• JXTA is a very dynamic Peer to Peer model where pipes are
queues and topics (metadata) are service advertisements


JXTA naturally supports local dynamic structure but
JMS is long distance “carrier” between JXTA peers and
supports global relatively static resources
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
19
Narada P2P Grid Event Service





http://grids.ucs.indiana.edu/ptliupages/projects/narada/
Is a network of event brokers which can reliably deliver XML
specified events with UDP or TCP/IP
Using openJMS selection module, becomes a distributed or
conventional Java Message Service
Linking selected JXTA
rendezvous’s, it also
supports multiple
JXTA communities
Think of JXTA JMS and
Narada as different
bindings for a
event/messaging
web service
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
20
e-Science is just a pile of XML

Each leaf is a piece of XML either defining a nugget of
information or a Service and/or containing links to other XML or
“raw resources”
Database
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
21
XML (RSS) Specification of Information Nuggets













<item rdf:about="http://xml.com/pub/2000/08/09/xslt/xslt.html">
<title> Processing Inclusions with XSLT </title>
<link> http://xml.com/pub/2000/08/09/xslt/xslt.html </link>
<description>
Processing document inclusions with general XML tools can be
problematic. </description>
</item>
<item
rdf:about="http://xml.com/pub/2000/08/09/rdfdb/index.html">
<title> Putting RDF to Work </title>
<link> http://xml.com/pub/2000/08/09/rdfdb/index.html </link>
<description>
Tool and API support for the Resource Description Framework
is slowly coming of age. </description>
</item>
Example of XML meta-data in the “pile”
</rdf:RDF>
pointing to other (outside) resources
11/6/2015
Links are essential as much meta-data will
NOT be co-located with resource
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02"
email="[email protected]"
22
Distributed Information
Actually the XML is distributed
all around in a dynamic Grid
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
23
Tree Structured Information

Roughly current organization of Web (Grid)
escience://root/one/two/bottom
Note XML specifies
root both internal and
external nodes of tree
one
two
bottom
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
24
Unstructured and Structured XML


Peer to Peer natural for unstructured “mess” (local broadcast)
Get a Grid of P2P organized communities
root
escience://root/one/two/mess
one
two
mess
11/6/2015
“mess” can be multiple levels of tree
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
25
Database
Database
MP Group
Grid Middleware
M
P
G
r
o
u
p
M
P
Grid
Middleware
Grid
Middleware
Grid Middleware
G
r
o
u
p
MP Group
MP=Middleware Peer
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
26
Audio Video Conferencing as a Web Service







We can use openh323 as core of a web service for audio video
conferencing
We have designed XGSP as a common XML session protocol
including SIP and H323 capabilities
We add additional commands to extend web service to
support heterogeneous clients and new fault tolerance and
audio mixing options
Will support traditional (H323, SIP) or new generation
clients with native XML (JXTA)
Event Service must support UDP and Real-time constraints
WSDL must “bind” to RTP transport used in A/V field
Include Internet Audio (NetMeeting, HearMe SIP ….),
Polycom (H323), Voice over IP Phones, and Access Grid
(MBONE)
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
27
New Tech
XGSP
A/V Conferencing
Web Services
JXTA
Gateway
Setup
Session
JXTA
SIP
Media
Server
Event/
Message
Service
Mix
Audio
Convert
Codec
SIP
Gateway
H323
Gateway
H323
AG
Gateway
Access
Grid
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
28
XML General Session Protocol I
<xs:complexType name="SessionDes">
<xs:sequence>
<xs:element name="SessionName" type="xs:string"/>
<xs:element name="SessionID" type="SessionID"/>
<xs:element name="SessionCreator" type="UserURL"/>
<xs:element name="SessionInfo" type="xs:string"/>
<xs:element name="SessionTime">
<xs:complexType>
<xs:sequence>
<xs:element name="StartTime" type="xs:dateTime"/>
<xs:element name="EndTime" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="SessionURI" type="xs:anyURI"/>
<xs:element name="SessionParticipants" maxOccurs="unbounded">
<xs:complexType>
<xs:complexContent>
<xs:extension base="UserURL"/>
“random”
</xs:complexContent>
</xs:complexType>
fragment
</xs:element>
<xs:element name="ContactInfo" type="UserURL"/>
</xs:sequence>
</xs:complexType>
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
29
XML General Session Protocol II
<xs:complexType>
<xs:sequence>
<xs:element name="MediaCodec" type="xs:string"/>
<xs:element name="CodecParam">
<xs:complexType>
<xs:choice>
<xs:element name="H.261" type="xs:H.261"/>
<xs:element name="H.263" type="xs:H.263"/>
<xs:element name="G.711" type="xs:G.711"/>
<xs:element name="G.722" type="xs:G.722"/>
<xs:element name="G.723" type="xs:G.723"/>
<xs:element name="G.728" type="xs:G.728 "/>
<xs:element name="G.729" type="xs:G.729"/>
<xs:element name="GSM" type="xs:GSM"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
30
A Typical SIP Message


REGISTER sip:registrar.biloxi.com
Via: SIP/2.0/UDP 10.4.1.4:5060
To: Bob (sip:[email protected])
From: Bob (sip:[email protected]);tag=456248
Call-ID: [email protected]
CSeq: 1826 REGISTER
Contact: (sip:[email protected])
Expires: 7200
Contact-Length: 0
Initially build a wrapper that accepts such messages
and converts to XGSP
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
31
Portals and Web Services




Web Services allow us to build a component model (see
CCA) for resources.
Each resource naturally has a user interface (which
might be customized for user) specified in WSRP/WSIA
from OASIS
Web Service <--> Portlet
Natural to use a component model for portal building
displayed web page from collection of portlets
• So can customize each portlet and customize which portlets
you want

Apache Jetspeed seems good open source technology
supporting this model
• JSP model is better than say a client-side Java integration in
that also message based so this is “Portal as a Web Service”
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
32
WSRP Structure of a Portlet


When one has multiple components in the UI one must extend
Web Service picture to include Portal and Portlets
WSRP and indeed WSDL details unimportant. Need basic
architecture with message based middleware
Application as a WS
General Application Ports
Interface with other Web
Services
WSDL
W
Application or
Content source
Web Service
11/6/2015
P
WSRP is
Web Services for Remote Portals
1st Meeting OASIS March 18 2002
S
R
Portal
User Profile
Aggregate
UI Fragments
User Face of
Integrate Multiple Portlets
Web Service
User Customization
WSRP Ports define
at either Portal or if
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02"
WS
as a Portlet
complicated atemail="[email protected]"
WS
Client
33
Online Knowledge Center built from Portlets



A set of UI
forComponents
the
Web Services provide a component model
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/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
34
Jetspeed Computing Portal: Choose Portlets
4 available portlets
linking to Web Services
I choose two
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
35
Choose Portlet Layout
Choose 1-column Layout
Original 2-column Layout
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
36
Two Computing
Portlets
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
37
Portal Shell

Our Gateway portal supports many methods or Sub
Web Services
• Over 80 is a lot to agree on – need to breal up into Services
with a few parts (methods)

Think of as a Portal Shell invoking many specific other
services such as
• run myws, ls, cd, cat mwsarchive, visualize ….


Both Shell and sub services could have separate UI
components
Services like ls could be instantaneous or updated as
needed
• If instantaneous, need to archive results as portlet lasts a
different length of time from transient ls
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
38
Transient or “Permanent”
or
WSDL
W
Application or
Portal WS
Web Service
WSDL
Factory WS
Web Service
WSDL
Archive
Persistent
Content WS
S
P
WSDL
R
WSRP
User Face of
Web Service
WSRP Ports define
WS as a Portlet
Integrate
Multiple Portlets
User Customization
at either Portal or if
complicated at WS
Portal
WSDL
W
Portal Shell
11/6/2015
Web Service
P
S
R
User Profile
Aggregate
UI Fragments
Client
Render
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
39
myWSarchive.wsdl I
WordWS
Factory
fred.doc




File
I/O
WS
Word
as a
WS
Portal
User
I/O
Please imagine that Microsoft Word becomes a Web Service …..
We are familiar with a file like fred.doc on our PC where .doc indicates the
appropriate handler for file
• fred.doc will be mix of XML (meta)data and perhaps binary attachments
Several web services (Word, StarOffice ..) can produce fred.doc
• They all support same Word.wsdl interface
Even more web services can process (handle) fred.doc
• Word, StarOffice, Notepad (XML dump), Copy are WordWS handlers
• These correspond to different ports specified directly (as XML) or
indirectly (as URI) in fred.doc
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
40
myWSarchive.wsdl II

We build our environments in terms of Web Services which can
be transient as well as persistent Web Service documents
analogous to fred.doc
myWS.wsdl can be
multiple files with
XML wrapper
defining action
of handlers
myWS
(handler)
Factory
myWS.wsdl
11/6/2015
File
I/O
WS
Job Portal
Shell
User
I/O
Portal
Transient for
length of job
File
I/O
WS
myWS
myWS
Handler
Portal
Persistent
myWS.wsdl
User
I/O
Transient for length
of user portal session
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02"
email="[email protected]"
41
Collaborative Web Services



First note that there are two distinct concepts
Collaboration as a Web Service
• Such as “Audio-Video Conferencing” as a Web Service or
“Text Chat as a Web Service”
Collaborative Web Services
• Here we view a Web Service as specifying a (distributed)
object and wish to share an object
• Object could be a Web page, a Job status form, a scientific
visualization, a PowerPoint slide etc. (not all of these are Web
Services but all should be)
• There is an overall framework (part of collaboration as a web
service) specifying such items as members of collaborative
session and their preferences. There is a mechanism to make
Web services collaborative within this framework
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
42
Why Web Services for Collaboration


Well everything is meant to be a Web Service but also:
Web Services are MUCH EASIER to make
collaborative than other objects because all input and
output is defined by uniform XML messages
• You need to teach your message service about collaboration!
• Note local applications are NOT Web Services – input is
things like “user mouse click” represented by “method
events” (UI program interrupts) not “XML message events”

The elegance of collaborative web services suggest that
it could be easiest to make object X (such as
PowerPoint or SVG) collaborative not by traditional
direct methods but by converting to a Web Service
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
43
Key Types of Collaboration



Shared Display: here one shares the rendering of a Web
Service. No modification is needed of the web service.
Rather this is handled by the portal controlling the user
interface
Collaborative Replicated Web Services: here one
replicates several instances of a web service and the
task is to keep these copies consistent. This
synchronizes inputs to multiple Web Services
Collaborative Web Service Access: here one has
multiple clients accessing a single instance of a web
service and obtaining consistent views. This multicasts
output of a single Web service to multiple clients
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
44
Collaboration: Shared Display

Sharing can be done at any point on “object” pipeline
Shared
Web Service
Shared Export
Shared
Event
Object
Shared
Display
Object’
Object
Viewer
Object’’
Object
Display
Master
Shared Display shares
framebuffer with events
corresponding to changed
pixels in master client.
Event
(Message)
Service
In these and following diagrams, we have
three collaborating clients;
is master
while
and
are non-masters
11/6/2015
Object
Display
Object
Display
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
45
Collaborative Web Service Access

Web Service either supports collaboration directly or uses event service
Web Service Interceptor
Providing General Services
Set Collaboration Mode
Master
Web
Service
Object
Web Service has a port
on which collaborative
modes set
Web Service can be
“front-end” (in middle
tier) to complex
back-end object
11/6/2015
Object
Viewer
Object
Display
Object
Viewer
Object
Display
Object
Viewer
Object
Display
Event
(Message)
Service
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
46
Web Service Interceptor


Collaborative Web Services are implemented “just” by
replicating the messages that are output by the Web service
This replication is provided by the event service which needs
both client and service dependent information
• The service specific message function is provided by an interceptor or an
adaptor which takes care of issues like security, collaboration,
management, service information, which message service to use
• The client specific function specifies the client profile telling event service
how to filter events for each client

Depending on system implementation, the interceptor is either
built into web service or a wrapper provided by event service
• The latter implies that all messages between clients and (all) web services
are handled by event service

There are ports on the interceptor allowing specification of
Collaboration Session and giving event service access to
information needed for appropriate filtered (as per profile)
message delivery to clients
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
47
Collaborative Portlets II

Collaboration is gotten by extending the WSRP
Interface
Interceptor
WSDL
W
Application or
Content source
Web Service
P
S
R
Workflow
Filter
Pub-Sub
11/6/2015
Control
Collaboration
as a Web
Service
Portal
User Profile
Aggregate
UI Fragments
Client
Event
(Message)
Service
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
48
Collaborative Replicated Web Services I

This uses event multicast to support replicated web services
Web Service Interceptor
Providing General Services
Set Collaboration Mode
Master
Object
Event
(Message)
Service
Web
Service
Object
Viewer
Object
Display
Web
Service
Object
Viewer
Object
Display
Object
Viewer
Object
Display
Web
Service
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
49
Collaborative Replicated Web Services II


The event service now replicates the messages INPUT
to the master web service (In Collaborative Web
Service Access we replicated messages OUTPUT to the
client)
Again we use a special “collaboration” port on the Web
Service to set up links between clients
• Note publish/subscribe mechanism in the events service
supports the late joiners (in other collaboration models as
well)

The event service can also handle messages between
Web services and clients and provide the user
customization service but this is not shown on previous
foil
11/6/2015
uri="http://grids.ucs.indiana.edu/ptliupages/presentations/iccsapril02" email="[email protected]"
50