1 / 29

SSE Evolutions

SSE Evolutions. SSE Service Providers Workshop Frascati, 2-3 October 2007 Yves Coene, Marc Gilles SPACEBEL. SSE Evolutions. Service Registration Wizard Order Information Access Improvement Restricted Access Services Next SSE ICD . Why a Registration Wizard ?.

regina
Download Presentation

SSE Evolutions

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. SSE Evolutions SSE Service Providers Workshop Frascati, 2-3 October 2007 Yves Coene, Marc Gilles SPACEBEL

  2. SSE Evolutions • Service Registration Wizard • Order Information Access Improvement • Restricted Access Services • Next SSE ICD

  3. Why a Registration Wizard ? • Current registration procedure requires: • Creation of a service schema • Creation of a service stylesheet • Creation of service WSDL file • Design of workflow or reuse of template

  4. Why a Registration Wizard ? • Problems • Schema and stylesheet files may be difficult to create. • Workflows are not so easy to define. • Default workflows exist but customization is limited (SOAP location) • Principle • Reduce the effort needed to integrate services on the SSE for some standards protocols of interest.

  5. Service Registration Wizard • Administrators defines ICDs in server’s directory • Each ICD contains a conf.xml file and templates for schema, wsdl and stylesheet filesand workflow for each defined operation.

  6. Service Registration Wizard • ICD Properties • ICDs are rescanned during the service registration, administrators can dynamically add ICD. • ICDs’ configuration file (conf.xml) is checked on runtime. • Templates files • Options are selected from the web interface. • A template engine does replacement in template file and copies the result on the server.

  7. Registration Wizard Usage

  8. Registration Wizard Usage • Service common configuration

  9. Registration Wizard Usage • AOI Configuration

  10. Registration Wizard Usage • Interface and Operation Selection

  11. Registration Wizard Usage • Operations’ configuration

  12. Service Usage

  13. Registration Wizard Supported ICDs • EOLI Catalogue 2.4 • CSW 2.0.1 ISO Metadata Application Profile OGC 04-038r4 • HMA Defined Catalogues ICDs for EO Products: • CSW 2.0 EO Application Profile OGC 06-079r2 • CSW 2.0 EO Ext. package for ebRIM Appl. ProfileOGC 06-131r2 version 0.1.4 • HMA Defined ICD for EO Products Ordering: • OGC 06-141 v1.0.4 • Online data through various OGC protocols: • WFS 1.0.0, WFS 1.1.0 • WMS 1.1.0, WMS 1.1.1 • WCS

  14. Registration Wizard Conclusion • Generalization use of « default » workflows approach for services stylesheet, wsdl, workflows • Only applicable for some protocols to specify some parameters like server location, collections names and define the support for some optional parameters. • Can not be used for services based on the SSE ICD where the messages definitions are not fixed.

  15. Order Management • Optimize the order information access • Add a filter by service in the order list • Possibility for the service provider to remove orders in any state. • While ordering a service through the different steps RFQ, ORDER possibility to skip the order list in order to display the order information or the order preparation • More precise status in the order list (Failed status).

  16. Order Management

  17. Order Management • Direct link on the confirmation page to skip the order list

  18. Restricted Access Service • Purpose: • Service Providers can decide to which user they want to give access to their services • Users require once the access to the service • Service Provider receives an e-mail and allows or denies the access to their service for this user. • User receives Service Provider decision by e-mail. • User can check the request status on the portal.

  19. Restricted Access Service • Service Registration

  20. Restricted Access Service

  21. Restricted Access Service • Request Access User Confirmation

  22. Restricted Access Service • User Service Access Requests

  23. Restricted Access Service • Access request e-mail to the Service Provider

  24. Restricted Access Service • E-mail link • Login • Automatic redirection to the SP Service Access Page

  25. Restricted Access Service • Access Allowed E-mail to the user

  26. Restricted Access Service • E-mail link: automatic redirection to the service page after login.

  27. Restricted Access Service • User access to services request status

  28. Automatic Redirection • After a login, the SSE will redirect the user to the last page he was browsing before logging in when he was on one of the following pages: • Service category/subcategory Page, • Service description Page • Organisation category/subcategory Page • Organisation description Page, • Software Page, • Documents Page

  29. SSE ICD 1.6 • Update of the SSE schemas structure to allow Service Provider to import the version of GML he wants to support (GML2.1.2 or GML3.1.1) at the service schema level. • Publication of a stub for the AreaOfInterest element to avoid to upload the GML schemas at the toolbox level. • Support for additional format as results files: • WCSURL (OGC Web Coverage Service) • CoverageFileURL (GeoTIFF file of limited size)

More Related