OSIRIS Middleware

1
OSIRIS Middleware ISIS ApplicationDELOS All
Tasks Meeting

Heiko Schuldt University of Basel,
SwitzerlandUMIT, Austria
2
What is OSIRIS?

• OSIRIS Open Service Infrastructure for Reliable
  and Integrated process Management
• Middleware supporting the combination of services
  (Programming in the Large)
• Reliable process execution (advanced transaction
  model)
• High degree of scalability (peer-to-peer process
  execution)
• Development started at ETH Zürich, now jointly
  continued at UMIT and Univ. of Basel
• OSIRIS does per se not provide any application
  functionality (it is a middleware)

3
What is ISIS?

• ISIS Interactive SImilarity Search
• Set of DL services (content-based image
  similarity, relevance feedback, audio retrieval,
  etc.)
• Which are combined by means of processes
• Execution of ISIS DL processes by OSIRIS

4
OSIRIS Architecture
Services
Services
Services
Services
5
OSIRIS Architecture

• Architecture consists of two parts
• Local OSIRIS layer, attached to each service
  provider
• Hosts application services (life cycle
  management, transactional guarantees, etc.)
• Global repositories
• They host global data on processes, service
  providers, etc
• Relevant parts of the information of these
  repositories is replicated to the local OSIRIS
  layers

6
Services in OSIRIS

• System services
• provided by the global repositories and local
  OSIRIS layers
• Ship with the system
• Process execution (including compensation,
  failure handling) replication, load balancing,
• Application services
• Provided by third parties
• Used inside processes

7
ISIS Services and Processes
8
DEMO Search in ISIS
9
DEMO Search in ISIS
10
OSIRIS Details

• Providers register the service they offer
  (subscription)
• Relevant information on processes is replicated
  at each node
• Sufficient to locally drive process execution in
  a P2P style

11
Load Balancing
subscription

• Workload balancing select the least loaded
  service provider
• Exploit workload information to route a service
  invocation
• Workload information must be locally available
• Subscription for significant changes of provider
  workload
• Publication in case of local changes

12
Failure Handling
?

• Service execution may fail
• Choose another provider (according to load
  information)
• Alternative execution (in process model)
• Compensation (undo effects of previous services
  if available)

?
?
13
How to Make Use of Your Services

• Application services can be
• Tightly-coupled
• Follow the OSIRIS component model
• Service is invoked locally from the OSIRIS layer
• Service life cycle (on demand deployment, ) and
• Compensation / transactional guarantees available
• Loosely-coupled
• Just provide a standard Web service interface
  (UDDI / SOAP)

14
How to Make Use of Your Services
Core System Services
Local OSIRIS Layers
OSIRIS Layer
OSIRIS Layer
OSIRIS Layer
...
IntegrationGateway
Services
Services
Service Providers
A
B
WSDLSOAP
K
15
How to Make Use of Your Services

• Definition of processes with the OGRAPE tool
  (Osiris GRAphical Process Editor)

16
Demo, Part II

• OGrape
• Relevance Feedback
• (Search with URL given)

17
Summary

• The DELOS Call for Services
• Integration activity
• Combine existing services of DELOS partners by
  using OSIRIS
• Send a description of your service(s) to Prof.
  H.-J. Schek (UMIT) hans-hjoerg.schek_at_umit.at

18
Demo, Part III

• Music Retrieval