1. HMA 26-27 January 2011 – Slide 1 Daniele Marchionni TELESPAZIO HMA Follow On Task 4 - Order AR 26-27 January 2011

2. HMA 26-27 January 2011 – Slide 2 Task 4 – Acceptance Review – Agenda  Task 4 Activities Status: Deliverables Order SWG Activities Reference Order Server – OPGW ETS (con terra presentation)

3. HMA 26-27 January 2011 – Slide 3 Task 4 – Activities Status - Deliverables  Deliverables for AR Configuration Item Data List (CIDL): DIL in the SDP document Non Conformance Reports (NCRs): none HMA Ordering ICD (including ATS):  Ordering Services for Earth Observation Products OGC 06-141r5 V0.9.8 10/01/2011 Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – (Technical Note)  Already delivered at MTR Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – (CTL Scripts)  To be provided at Delta AR ETS Execution Report  To be provided at Delta AR

4. HMA 26-27 January 2011 – Slide 4 Task 4 – Activities Status - Deliverables  Deliverables for AR OPGW Software Installation Document:  OPGW SID V1.1 28/01/2011 OPGW Software Design Document:  OPGW SDD V1.2 28/01/2011 OPGW Software Validation Testing Specification:  OPGW SVS V1.1 28/01/2011 OPGW Acceptance Test Reports:  OPGW ATR V1.0 28/01/2011 Order Server Installation Plan:  To be provided at Delta AR OPGW SW:  OPGW V5.0 28/01/2011

5. HMA 26-27 January 2011 – Slide 5 Task 4 – Activities Status - SWG  Ordering Services for Earth Observation Products SWG Several updates to the ICD have been prepared since MTR:  OGC 06-141r4 V0.9.6, 03/09/2010  OGC 06-141r4 V0.9.7, 29/11/2010  OGC 06-141r5 V0.9.8, 10/01/2011

6. HMA 26-27 January 2011 – Slide 6 Task 4 – Activities Status - SWG  OGC 06-141r4 V0.9.6, 03/09/2010  A number of issues have been fixed: Clarified asynchronous operations behaviour, WS-addressing and statusNotification element. Updated ATS OGC Issue Tracker Issue 441: To align with OWS 2.0 OGC Issue Tracker Issue 559: Make GetStatus Mandatory operation OGC Issue Tracker Issue 553: To specify capabilities at collection level OGC Issue Tracker Issue 556: To use HTTP URIs OGC Issue Tracker Issue 557: To align XML Schema to OGC 06-135r9  This version has been successfully voted by SWG for public comments

7. HMA 26-27 January 2011 – Slide 7 Task 4 – Activities Status - SWG  OGC 06-141r4 V0.9.7, 29/11/2010  Major update due to the OAB review (mainly John R. Herring comments): The review focussed on the ATS part and also on requirements, most critical points:  Conformance Classes, Conformance Tests were not in line with OAB expectations;  Conformance Classes and Requirements were not in line with OAB expectations;  Mapping between requirements and tests to be improved;  Traceability Matrix to be included No comments on interfaces instead

8. HMA OGC 06-141r4 V0.9.7, 29/11/2010  A teleconf has been held with OAB on 4/11/2011 for discussing these points  Then Requirements, Conformance Classes, Conformance Tests have been rewritten ending up with plenty of Conformance Classes and Requirements. 26-27 January 2011 – Slide 8

9. HMA OSEO Requirement Classes  OSEO allows submitting different type of requests (product orders, subscriptions, tasking orders) with different delivery method (media, on-line), with different scene and processing options.  Therefore different Requirement Classes have been defined specifying the requirements for implementing the ordering process for each of the identified order types.  Additional classes have been defined for optional functions that might be implemented by Order Server having extended functionality. 26-27 January 2011 – Slide 9

10. HMA OSEO Requirement Classes  List of Requirements Classes : ProductOrder  SceneSelection SubscriptionOrder TaskingOrder OnlineDataAccess OnlineDataDelivery MediaDelivery Cancellation  Async Cancellation AsyncSubmit 26-27 January 2011 – Slide 10

11. HMA OSEO Requirement Classes Quotation: it specifies the requirements for supporting order quotation.  QuotationSync, which specifies the requirements for a server providing order quotation in real time;  QuotationMonitoring, which specifies the requirements for a server providing order quotation by monitoring;  QuotationAsync, which specifies the requirements for a server providing order quotation by asynchronous notification;  QuotationOffLine, which specifies the requirements for a server providing order quotation by mail / e-mail; Notification: it specifies the requirements for supporting notification about the order status via WS-notification protocol.  Every OSEO implementation is expected to comply with at least one of ProductOrder, SubscriptionOrder, TaskingOrder and optionally with one of the other classes. 26-27 January 2011 – Slide 11

12. HMA OSEO Requirement Classes 26-27 January 2011 – Slide 12

13. HMA OSEO Requirement Classes 26-27 January 2011 – Slide 13 Requirement Class Requirement Class URI Dependency AsyncCancellation http://www.opengis.net/spec/OSEO/1.0/req/AsyncCancellation Cancellation AsyncSubmit http://www.opengis.net/spec/OSEO/1.0/req/AsyncSubmit Core Cancellation http://www.opengis.net/spec/OSEO/1.0/req/Cancellation Core http://www.opengis.net/spec/OSEO/1.0/req/Core MediaDelivery http://www.opengis.net/spec/OSEO/1.0/req/MediaDelivery Core Notification http://www.opengis.net/spec/OSEO/1.0/req/Notification Core OnlineDataAccess http://www.opengis.net/spec/OSEO/1.0/req/OnlineDataAccess Core OnlineDataDelivery http://www.opengis.net/spec/OSEO/1.0/req/OnlineDataDelivery Core ProductOrder http://www.opengis.net/spec/OSEO/1.0/req/ProductOrder Core Quotation http://www.opengis.net/spec/OSEO/1.0/req/Quotation Core QuotationAsync http://www.opengis.net/spec/OSEO/1.0/req/QuotationAsync Quotation QuotationMonitoring http://www.opengis.net/spec/OSEO/1.0/req/QuotationMonitoring Quotation QuotationOffLine http://www.opengis.net/spec/OSEO/1.0/req/QuotationOffLine Quotation QuotationSync http://www.opengis.net/spec/OSEO/1.0/req/QuotationSync Quotation SceneSelection http://www.opengis.net/spec/OSEO/1.0/req/SceneSelection ProductOrder SubscriptionOrder http://www.opengis.net/spec/OSEO/1.0/req/SubscriptionOrder Core TaskingOrder http://www.opengis.net/spec/OSEO/1.0/req/TaskingOrder Core

14. HMA OSEO Requirements  For each OSEO operation a table has been included reporting the requirements, divided by classes, a server has to comply with for claiming the conformance with respect to that class.  e.g. (from GetOptions): 26-27 January 2011 – Slide 14

15. HMA OSEO Requirements 26-27 January 2011 – Slide 15 OperationNumber of requirements GetCapabilities16 GetOptions20 GetQuotation17 Submit22 GetStatus20 DescribeResultAccess9 Cancel15 TOTAL119  Statistics:

16. HMA OSEO Conformance Classes  1:1 mapping between Conformance Classes and Requirements Classes (as required by OGC policies): 26-27 January 2011 – Slide 16

17. HMA OSEO Conformance Classes  Each Conformance Class is composed of a set of tests, each verifying one or more requirements of the corresponding Requirements Class.  Each Conformance Class covers all requirements of the corresponding Requirements Class.  It has to be noted that the tests reported in the Conformance classes have “temporal dependencies”: in fact for running one test another specific test might be needed (e.g. to test order status at least one order needs to be created in the Order Server by Submitting an order). Then: The tests specified in a Conformance Class must be executed in the order they are specified in the document; The tests of a Conformance Class can be started only if the tests of the parent class have been completed. 26-27 January 2011 – Slide 17

18. HMA OSEO Conformance Classes  Provided that the full compliance is very difficult to achieve, possible examples of compliance : An Order Server supporting product ordering for scientific users should comply with:  Core  MediaDelivery  ProductOrder  SceneSelection  Optionally it should support also on-line delivery: –OnlineDataAccess –OnlineDataDelivery 26-27 January 2011 – Slide 18

19. HMA OSEO Conformance Classes An Order Server supporting product ordering for commercial users should comply with:  Core  MediaDelivery  ProductOrder  SceneSelection  Quotation, and at least one of: –QuotationAsync –QuotationMonitoring –QuotationOffLine –QuotationSync  Optionally it should support also on-line delivery: –OnlineDataAccess –OnlineDataDelivery 26-27 January 2011 – Slide 19

20. HMA OSEO Conformance Classes 5-6 July 2010 – Slide 20 Conformance ClassNumber of tests Core13 ProductOrder5 SceneSelection2 SubscriptionOrder4 TaskingOrder4 AsyncSubmit5 Quotation5 QuotationSync1 QuotationMonitoring2 QuotationAsync2 QuotationOffLine1 OnlineDataAccess6 OnlineDataDelivery2 MediaDelivery2 Cancellation4 AsyncCancellation4 Notification1 TOTAL63  Statistics:

21. HMA OGC 06-141r5 V0.9.8, 10/01/2011  Changes due to OGC NA: Definition of URI for Order Options e.g.:  http://www.opengis.net/def/order/OGC-EO/0/QualityOfService http://www.opengis.net/def/order/OGC-EO/0/QualityOfService  http://www.opengis.net/def/order/OGC-EO/0/ProcessingLevel Definition of URI for Scene Selection Options e.g.:  http://www.opengis.net/def/scene/OGC-EO/0/SceneType http://www.opengis.net/def/scene/OGC-EO/0/SceneType  http://www.opengis.net/def/scene/OGC-EO/0/RowsExtraction Update of namespace:  http://www.opengis.net/oseo/1.0 http://www.opengis.net/oseo/1.0 Some edits from Carl Reed 26-27 January 2011 – Slide 21

22. HMA 26-27 January 2011 – Slide 22 Task 4 – Activities Status - SWG  OGC 06-141r5 V0.9.8 has been put on the OGC Web Site (24/01/2011) for public comments: http://www.opengeospatial.org/pressroom/pressrelease s/1346  Next activities: To include schema and WSDL updates done during the implementation of OPGW. Waiting for the expiration of the comments period (23 February 2011), gathering comments and then preparation of the final version.

23. HMA Reference Order Server - Overview  A reference order server, OPGW, has been implemented with the following objectives: Demonstrate the updated specification; Support the implementation of ordering clients; Support the implementation of ordering servers.  Since ordering process implies processing, formatting and delivering to the user of the required products, then a fully functional order server would mean a complete order handling system for EO products.  OPGW is in stead a gateway that translates the incoming requests in equivalent calls (EOLI XML Order) to the ESA Order Handling System. 26-27 January 2011 – Slide 23

24. HMA Reference Order Server - Architecture 26-27 January 2011 – Slide 24

25. HMA Reference Order Server - Architecture  External Entities: HMA Client: TEAM Engine, SSE EOLI XML Order Server (MMOHS via M2EOS)  The input HMA Order is translated in the corresponding EOLI XML Order for being actually executed OPGW Operator  Provides the order options configuration and some ESA GS users External OGC 06-131 Catalogue  This is the OGC Catalogue storing the EO Product metadata to be queried and ordered from the HMA Client. 26-27 January 2011 – Slide 25

26. HMA Reference Order Server - Architecture  OPGW Sub Components: OPGW Check Order:  Command line Java application in charge of updating the status of orders with async notification (SubmitResponse) to the async client. The status of order is updated by sending a monitor request to the configured EOLI XML order server.  Based on AXIS 2 for sending SOAP requests.  HSQLDB V2.0 JDBC Driver for connecting to the OPGW Orders Database.  XMLBEANS V2.4 for producing and reading XML messages OPGW Common:  Java library including all functions needed to the other OPGW components e.g.: Database access functions, EOLI XML and OSEO SOAP Clients functions, EOLI XML to OSEO and vice-versa functions 26-27 January 2011 – Slide 26

27. HMA Reference Order Server - Architecture  OPGW Sub Components: OPGW Import Users:  Command line Java application in charge of reading Users.xml file (from MMOHS components) and loading the needed ESA user’s profile info in the OPGW User Database.  HSQLDB V2.0 JDBC Driver for connecting to the OPGW Users Database.  Based on XML Beans 2.4 for reading the XML files. OPGW OSEO Axis Service:  Web Service implementing the OSEO operations (GetCapabilities, GetOptions, GetQuotation, Submit, GetStatus, Cancel, DescribeResultAccess) generated using: –AXIS2 Service of Netbeans 6.9.1 from WSDL –The service is deployed into Apache Tomcat 6.0.26  Due to the complexity of schema files (basically the GML ones included by SWE and then by OSEO) the only way for generating the service was Netbeans 6.9.1 + AXIS 2 Services + no data binding; the other ways (AXIS 2 + any data binding or METRO (JAX-WS + JAXB) were not able to parse the WSDL and schemas). 26-27 January 2011 – Slide 27

28. HMA Reference Order Server - Architecture  OPGW Sub Components: OPGW Core:  Java library including all functions for implementing OSEO operations.  It is directly called by OPGW OSEO Axis Service.  These functions have not been included into the service itself, because it is generated automatically by Netbeans: every time the WSDL is changed it must be regenerated again with the risk to loose manually written code. OPGW OSEO Axis Async Client:  Web Service implementing the OSEO async operations (GetQuotationResponse, SubmitResponse, CancelResponse)  Generated using: –AXIS2 Service of Netbeans 6.9.1 with the WSDL provided with the OSEO schema. –The service is deployed into Apache Tomcat 6.0.26  To overcome an AXIS problem which was not able to distinguish Submit from SubmitResponse operations, 2 PortTypes have been defined in the WSDL: –One for the actual operations –The other one for the async notifications. 26-27 January 2011 – Slide 28

29. HMA Reference Order Server - Architecture  OPGW Sub Components: OPGW Schema Lib:  It is a Netbeans a project in charge of generating the JAR libraries managing the different schemas handled by OPGW (OSEO 1.0, EOLI XML, EOLI Order, OWS,...)  These libraries are used by all other components OPGW Security Layer:  Java library including functions for reading / writing SAML Tokens with encryption & digital signature HSQLDB V2.0:  Java RDBMS (it is a single JAR file!) used for managing the OPGW Database (Users and Orders). 26-27 January 2011 – Slide 29

30. HMA Reference Order Server - Architecture OPGW TestTool:  Java command line tool implementing the tests defined in the OPGW SVS.  It is a SOAP client that sends the requests specified in the SVS, then receive the response from the server, dump on file, performs schema checks and verify the assertions of the test (i.e. check the received order id or the expected ExceptionReport, etc.) 26-27 January 2011 – Slide 30

31. HMA Reference Order Server – Development Status  Missing functions: Implementation of UM ICD V0.0.6 (V0.0.4 was previously implemented) Call to External SPS EO Server Simulated operations (GetQuotation, Cancel, DescribeResultAccess, which returns fixed responses) 26-27 January 2011 – Slide 31

32. HMA Reference Order Server - Architecture  Implementation Issues: OGC Services cannot be easily handled with common Web Service development tools e.g.:  Only XMLBEANS 2.4 was able to manage the schemas; JAXB and the latest version of XMLBEANS failed instead;  Only AXIS2 without data binding was able to generate the service from the WSDL Switch from AXIS1 to AXIS2 (which supports SOAP 1.2)  Previous versions of OPGW were based on HMA Skeleton, which was based on AXIS 1.x;  The switch to AXIS2 has lead to the rewriting of several parts of the old code (the security part is one of them) and then some further delay 26-27 January 2011 – Slide 32

33. HMA Reference Order Server - Test  Test Environment OPGW relies on an EOLI XML Order back-end to avoid the need of the availability of MMOHS, then a simulator has been implemented: mOHS (Micro Order Handling System). mOHS implements EOLI XML Order protocol:  processAcquisitionOrderRequest  processProductOrderRequest  processOrderMonitorRequest Submitted orders are stored in the HSQLDB and order monitoring is implemented querying the DB. The service has been generated from the WSDL without issues using Netbeans 6.9.1 + Metro (JAXB + JAX-WS) 26-27 January 2011 – Slide 33

34. HMA Reference Order Server – Test Results  TC_010_001: Ordering Service - GetCapabilities 26-27 January 2011 – Slide 34

35. HMA Reference Order Server – Test Results  TC_010_010: Ordering Service - GetOptions 26-27 January 2011 – Slide 35

36. HMA Reference Order Server – Test Results  TC_010_030: Ordering Service - Submit 26-27 January 2011 – Slide 36

37. HMA Reference Order Server – Test Results  TC_010_040: Ordering Service - GetStatus 26-27 January 2011 – Slide 37

38. HMA Reference Order Server – Test Results  TC_010_020: Ordering Service – GetQuotation SKIPPED  TC_010_050: Ordering Service – SubmitResponse: PASSED  TC_010_060: Ordering Service – Cancel: SKIPPED  TC_010_070: Ordering Service – DescribeResultAccess: SKIPPED  TC_020_001: Ordering & Programming Service – Coverage Order: SKIPPED 26-27 January 2011 – Slide 38