1. Ordering Services for EO Products SWG ATS / ETS
Sponsored and hosted by
ESA/ESRIN
Ordering Services for EO Products SWG ATS / ETS
Uwe Voges, con terra GmbH
HMA FO MTR, July 6, 2010
© 2010 Open Geospatial Consortium, Inc.

2. © 2010 Open Geospatial Consortium, Inc.
General Order Model
EO Order Service General UML model
EOOrderService class associated with 5 classes, each with one or more operations
each real instance of the EO-OrderService must implement two or more associated classes
EOOrderCore type is abstract class from which three concrete classes are derived handling concrete order types
Associated classes are mandatory or optional
A compliant OrderServer shall implement OGCService and EOOrderCore and can implement additional classes
© 2010 Open Geospatial Consortium, Inc.

3. ATS – Conformance Classes © 2010 Open Geospatial Consortium, Inc.
Each concrete type has one or more Conformance Classes (CC) associated (green/grey)
Dark green CCs address core set of synchronous operations for one OrderType: Supporting one or more of these CCs is mandatory
The light green / grey conformance classes test additional opt. behaviour:
EOOrderCore Asynch (PO|Sub|SPS): support for asynchronous Submit requests
EOOrderResultAccess: covers support for the DescribeResultAccess operation
EOOrderCancel[Asynch]: covers the (asynchronous) Cancel support
© 2010 Open Geospatial Consortium, Inc.

4. ATS – Conformance Classes © 2010 Open Geospatial Consortium, Inc.
Large number of CC result from the combinatoric of three different attributes
Operations: a set of mandatory (Core) operations (GetCapabilities, GetOptions, Submit and GetStatus) can be combined with the three optional operations (GetQuotation, Cancel, DescribeResultAccess)
OrderType: ProductOrder(PO), Subscription (Sub), Tasking (SPS)
Processing type: synchronous, asynchronous with notification
CC are defined within the ATS
Every has assigned one or more Abstract Test Cases (ATC)
© 2010 Open Geospatial Consortium, Inc. 4

5. © 2010 Open Geospatial Consortium, Inc.
ATS – Test “Scenario”
Some test cases within a CC are dependant on the results / procedure of other test cases within the same CC
CC can be seen as a Scenario
UML state diagrams in ATS visualize scenarios as transitions (from the servers point of view)
transitions of core CC EOOrderCore(PO|Sub|SPS: lines coloured green in the state diagram
Transitions of EOOrderCancel CC visualized with pink lines
Transitions of the EOOrderResultAccess CC visualized with red lines
EOOrderQuotation: separate diagram (not included here)
© 2010 Open Geospatial Consortium, Inc.

6. © 2010 Open Geospatial Consortium, Inc.
ATS – Test Cases
Every Test Case represents the execution of a service call and the testing of the service results
Some Test Cases are dependant from others
Scenario has to wait for a specific status before proceeding with next Test Case
As definition of Test Classes would result in massive replications of Test Cases a concept of sliding-in or replacing Test Cases was defined
A Test Case looks like:
© 2010 Open Geospatial Consortium, Inc.

7. © 2010 Open Geospatial Consortium, Inc.
ETS - Approach
Executable Test Suite (ETS): „Implements“ ATC of ATS
includes most important test cases which will be supported by OPGW (+Cancel)
GetCapabilities
GetOptions (for predefined Coll/PO/Sub/SPS)
Submit
GetStatus
DescribeResultAccess
Submit / GetStatus / DescribeResultAccess tested within Scenario
No communication with Catalogues or SPS (Product-ID must a priori be known)
GetStatus used within an Order Scenario following a Submit request
DescribeResultAccess (optionally) follows GetStatus test cases
Cancel (although not supported by OPGW) tested within Scenario
case differentiation to distinguish version 0.9.5r3 / (for EUMETSAT)
„outsourced“ functions for requesting parts of the Capabilities document
Currently testing on EUMETSAT implementation
© 2010 Open Geospatial Consortium, Inc. 7

8. © 2010 Open Geospatial Consortium, Inc.
ETS - Approach
GetStatus within Scenarios following Submit- and Cancel-requests
with repeat-test, to test within a timeframe if status = successful
Example:
© 2010 Open Geospatial Consortium, Inc. 8

9. © 2010 Open Geospatial Consortium, Inc.
ETS - Approach
© 2010 Open Geospatial Consortium, Inc. 9

10. © 2010 Open Geospatial Consortium, Inc.
ETS - Approach
© 2010 Open Geospatial Consortium, Inc. 10

11. © 2010 Open Geospatial Consortium, Inc.
ETS - CTL-Scripts
The following figure describes the structure of the .ctl-scripts:
call-test
main.ctl
call-function
Implements test case
CC_EOOrderCore.ctl
EOOrderCoreGetCapabilities.ctl
ATS A.3.1.1
EOOrderCoreGetOptions.ctl
ATS A.3.1.2, A.3.1.3
EOOrderCoreSubmitGetStatusDescResult.ctl
ATS A > A.3.1.9
EOOrderCoreGetStatus.ctl
ATS A > A
EOOrderDescribeResultAccess.ctl
ATS A.3.3.1
CC_EOOrderCancel.ctl
ATS A A.3.4.2
Java_functions.ctl
© 2010 Open Geospatial Consortium, Inc. 11

12. © 2010 Open Geospatial Consortium, Inc.
ETS - CTL-Scripts
the requests are outsourced in separate “request-message-files”
load file
© 2010 Open Geospatial Consortium, Inc. 12

13. © 2010 Open Geospatial Consortium, Inc.
ETS - Limitations
Because of limited resources and unavailability of required features within TEAMEngine the current ETS has different limitations:
Concentrate on test cases to be tested against OPGW (+Cancel)
Skip GetQuotation
Use of predefined Orders instead of automatically generated requests
No inclusion of UserManagement
Testing with „command-line based“ TEAMEngine
No testing of asynchronous operations
Currently call-backs are not supported by TEAMEngine
Chuck Morris (OGC): „We are planning to add support for "asynchronous operation” to TEAM Engine. The code isn't complete, but I have just completed drafting the changes to CTL. Take a look at the new create-monitor and examine-monitor instructions…“
© 2010 Open Geospatial Consortium, Inc. 13

14. ETS / Test-Environment File-Directory
“ETS”-directory: CTL scripts
“messages”-directory: requests used by TEAMEngine
Sub-directory which includes the EUMETSAT requests
Sub-directory which includes the future ESA / OPGW 0.9.5r3 requests
the “responses”-directory includes the response XML docs from tests
Sub-directories “schema_0.9.4” / “schema_0_9_5r3”: order xml schemas used for validation of requests / responses
© 2010 Open Geospatial Consortium, Inc. 14

15. © 2010 Open Geospatial Consortium, Inc.
Deliverables - ATS
ATS as separate document (Technical Note) delivered by conterra on 25/01/2010, under consortium review
ATS integrated into Order Spec on 24/02/2010
Update ATS 28/06/2010
© 2010 Open Geospatial Consortium, Inc.

16. © 2010 Open Geospatial Consortium, Inc.
Deliverables - ETS
Executable Test Suite (ETS) for the Ordering Spec delivered by conterra on 28/06/2010
ETS Technical Note delivered by conterra on 28/06/2010
© 2010 Open Geospatial Consortium, Inc.

17. Deliverables – Ordering ICD © 2010 Open Geospatial Consortium, Inc.
Setup Issue Tracker
Included Items
Reviewed Order Spec with inputs into Issue Tracker
Lots of input for Order ICD
Provision to RFC and Order SWG setup
© 2010 Open Geospatial Consortium, Inc.

18. © 2010 Open Geospatial Consortium, Inc.
Results – Other
Meetings (+ preparation):
OGC TC Darmstadt
Frascati (OGC TC + MTR)
Telecons
© 2010 Open Geospatial Consortium, Inc.

19. © 2010 Open Geospatial Consortium, Inc.
Issues
Elaboration of complicated ATS and ETS concepts (stateful scenarios, repeat-tests,..) and lots of inputs into Order ICD, Issue Tracker, Order SWG resulted in major consumation of Resources than expected
Budget nearly finished: 4 man days left!!
Allows only to help Datamat testing OPGW (when available): Order Server Acceptance Testing (next slide)
This was foreseen by con terra -> therefore we restricted in our proposal the amount of test cases to (depending on resources left) -> we implemented > 25
Consequences
not all ATS Test-Cases can be covered by ETS
Ordering ICD has several async operations, but the TEAM engine at the moment does not support these operations (see before)
Test-case for SubmitResponse (part of the asynchronous operation "submit").
This means that after calling "submit" the server notifies the client (here the TEAMEngine) by calling "SubmitResponse" when the whole order has been completed (or on a changed order status).
The client must set <wsa:ReplyTo> of the Submit message to> the address where the client is listening...
© 2010 Open Geospatial Consortium, Inc.

20. © 2010 Open Geospatial Consortium, Inc.
Issues
Support to Order Server Acceptance Testing
After the ETS preparation is accomplished, the scripts will be preliminary executed by the CITE TEAM Engine against a web-accessible version of the OPGW, the reference order server set-up by Elsag Datamat. Formally the ETS has to be prepared in the WP and executed against the OPGW in WP , then it would imply that the ETS is delivered to OPGW team without having performed any verification against a “live” server. For avoiding this risk, a preliminary but functional version of the OPGW will be set-up on public INTERNET for allowing some remote test sessions from the developer of the ETS. The results of these preliminary tests will be reported for taking the needed actions: either to fix the CTL, or the test message or the OPGW software.
Test plan has to be defined.
The CTL scripts have to be executed by the TEAM Engine against the Reference Server
The test results have to be documented.
What do we need from Datamat:
GetCapabilities endpoint
a valid collection ID for testing GetOptions
a valid Submit->orderSpecification Structure (one with and one without sceneSelection)
© 2010 Open Geospatial Consortium, Inc.