Service Support Environment - PowerPoint PPT Presentation

1 / 34
About This Presentation
Title:

Service Support Environment

Description:

Expose functionality in modular fashion. Avoids duplication. Reduces total number of processes ... discovery from 'BPEL Designer' Alternatives: UDDI and OGC ... – PowerPoint PPT presentation

Number of Views:35
Avg rating:3.0/5.0
Slides: 35
Provided by: yco9
Category:

less

Transcript and Presenter's Notes

Title: Service Support Environment


1
Service Support Environment
Yves Coene, SPACEBEL Simone Gianfranceschi,
Intecs Steven Smolders, GIM
2
Table of Contents
  • Overview
  • Tools
  • Standards
  • Future work

3
SSE Objectives
  • Orchestrate synchronous and asynchronous EO
    Services for online and offline processes
  • Provide an overarching infrastructure, neutrally
    managed by ESA
  • Empower service providers through abusiness
    process management (BPM) platform
  • Easily deploy and deliver services to users from
    own infrastructure
  • Minimize service providers upfront investments
  • Open standards to facilitate adoption and
    evolution

4
Service Oriented Architecture
  • SOA
  • Approach to develop reusable services
  • Loosly coupled
  • Expose functionality in modular fashion
  • Avoids duplication
  • Reduces total number of processes
  • Combine services according to a business process
    "orchestration".
  • SOA implemented using Web services

5
SSE Toolbox
6
Table of Contents
  • Overview
  • Tools
  • Standards
  • Future work

7
Service Publishing Steps
  • Publish service as Web service
  • SSE Toolbox
  • Orchestrate services
  • BPEL Designer creating workflows
  • or use default workflows
  • Register service on SSE Portal
  • Fill out Web form and configure AOI component
  • Monitor service processes "in-flight"
  • BPEL Console

8
Step 1 Toolbox
  • Allows easy Web service publishing
  • Provides a generic gateway towards service
    providers infrastructure (e.g. DBMS, File
    System, API)
  • Supports also services with NO infrastructure
    behind
  • Interface towards the Service Provider
    infrastructure based on widely accepted IT
    standards
  • Permits to translate local terms into SSE ones
    (no need to change Service Provider
    infrastructure)

9
Step 2 Service Orchestration
  • Workflow editor to chain services ...

10
Step 3 Service Definition Panel
11
Step 4 Service Monitoring
Workflow console to monitor service instances
12
Table of Contents
  • Overview
  • Tools
  • Standards
  • Future work

13
  • WSDL (W3C)
  • WSDL file for each service, generated by SSE
    Toolbox
  • Defines available service operations
  • Each operation has parameters. Types defined in
    XML Schema (W3C)
  • Operations have (mainly) SOAP bindings
  • Apache WSIF (WS Invocation Framework) allows
    using WSDL for other bindings such as XML/HTTP
    (OGC WMS, WFS, WCS), email, etc.

14
Interaction Model
  • Predefined "basic" operations per service
  • Search returns matching catalogue entries
  • Present retrieves all available "metadata".
  • Request Quotation returns information about the
    service, e.g. feasibility, pricing, alternatives
    etc.
  • Order activate the service.
  • Customised operations
  • Can be mapped to a workflow
  • Workflow can call any Web service

15
Interaction Model
  • WS-Interoperability (ws-i.org)
  • Request/Response (synchronous)
  • Basic callback (asynchronous)

16
  • ws-addressing (W3C)
  • asynchronous communication correlation of
    messages.
  • SOAP (W3C)
  • message-based (i.e. document-style)
  • Over HTTP, firewall-friendly, platform neutral
  • Optional use of HTTPS / SSL
  • De-facto standard J2EE and Microsoft .NET
  • Interface is formalised using WSDL

17
  • BPEL (OASIS)
  • Standard to orchestrate Web services into process
    flows
  • Invoke Web services synchronous / asynchronous
  • Manipulate XML documents (XPath, XSLT)
  • Rich language if / while / parallel, exceptions,
    events etc.
  • Expose process flow as Web service
  • Many implementations SeeBeyond, IBM, Oracle,
    Intersystems etc.

18
Orchestration Example
Spot Vegetation Sensor S10
User needs
Carbon flux over Belgium in GeoTIFF format
(Kyoto Protocol verification)
Format Conversion
GeoTIFF
HDF
Data Provider
Value Adder
Automation of Business Process
Data Provider
Service Provider
Net Flux of Carbon Map (HDF)
Clipping
Europe
Belgium
19
  • ws-inspection
  • Service discovery from "BPEL Designer"
  • Alternatives UDDI and OGC catalogue

20
Catalogue Access
  • Currently ESA EOLI-XML ICD (SOAP) Search/Present
  • OGC Catalog 2.0 (Catalogue Services for the Web)
    being investigated.
  • EOLI-XML may become OGC Profile (Harmony Project
    with OGCE)

21
  • Data distribution mechanisms
  • SOAP data included in SOAP payload
  • FTP/HTTP URL passed in SOAP payload
  • WFS - to publish service results (vector data)
  • WCS - to publish service results (raster data)
  • ESA DDS data delivery via satellite

22
  • OGC Standards
  • WMS - superimpose layers and service results
  • Layers can be results of workflows

ERS SAR catalogue
Envisat ASAR catalogue
RadarSat catalogue

Wave height direction model
Ship detection
processor
ERS SAR online data access
O il spill detection
processor
ERS SAR online data access
23
  • OGC Standards
  • WMS Catalogue search results can be shown on map
  • Web Map Context allow to save/load context

24
  • OGC Standards
  • GML for AOI encoding
  • GML for service results


25
  • Gazetteer (Alexandria) - to select rectangular AOI

26
  • Gazetteer (Alexandria) to select circular AOI

27
Table of Contents
  • Overview
  • Tools
  • Standards
  • Future Work

28
OGC Standards
  • Better support for Service Result Symbology
    OGC s Styled Layer Descriptor Language (SLD)

ltStyledLayerDescriptorgt . ltRulegt
ltPointSymbolizergt . lt/
PointSymbolizergt lt/Rulegt
. lt/StyledLayerDescriptorgt

29
OGC Standards
  • OGC WFS
  • Vector data
  • Client-side or Portrayal service rendering
  • OGC WCS
  • Raster data
  • Client-side or Portrayal service rendering
  • Can be combined with coordinate transformation

30
Manual Service Steps
  • Supports 100 manual service via task list
  • Service provider can enters service result as
    text (e.g. URL)
  • Also manual services can be "chained"

31
Data Distribution via DDS
  • Send "data" via ESA DDS as last "step" in any SSE
    service workflow.
  • Uses Eutelsat C-band

32
Data Distribution via DDS
  • DDS is additional way to disseminate service
    results, e.g. in Africa.

NPPService VITO
Format Conversion Service GIM
AOI selection(SSE)
Data Dissemination System
NPP-Africa-GeoTIFF
NPP-Africa-GeoTIFF
NPP-Africa-HDF
NPP input AOI description required format
33
Data Distribution via DDS
  • SSE as front-end of product distribution for
    service providers.

FTP Server
Product upload
destination selection(SSE)
OGC Web Coverage Server
Data Dissemination System
34
More info
  • 3 afternoon sessions
  • SSE CD-ROM
  • Flash presentation
  • SSE and BPEL White Papers
  • SSE User Manuals
  • Software Toolbox, Eclipse, BPEL Designer
  • http//services.eoportal.org (Documents section)

Thank you !
Write a Comment
User Comments (0)
About PowerShow.com