Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
98 Copyright © 2012 Open Geospatial Consortium
Table 7-28 - Operation request encoding
7.4.3 Asynchronous requests and replies
Regarding the asynchronous requests and replies the WS-addressing [NR10] SOAP header extensions have been used:
– In the SOAP header of GetQuotation, Submit and Cancel operations request messages the following
tags have to be included wsa is the namespace of WS-addressing definitions
http:www.w3.org200508addressing:
wsa:ReplyTo wsa:Address order service URI of the client wsa:Address
wsa:ReplyTo wsa:MessageID unique identifier of the request wsa:MessageID
In case the reply address is set to:
http:www.w3.org200508addressinganonymous
it means that the client does not have to be notified. It is useful for standard clients not having server capabilities. In this case the client has to ask the status of asynchronous requests calling dedicated
operations e.g. GetStatus for checking the status Submit and Cancel operations.
– In the SOAP header of GetQuotationResponse SubmitResponse CancelResponse operations
request messages the following tags have to be included wsa is the namespace of WS-addressing definitions:
wsa:RelatesTo RelationshipType=wsa:Response Identifier of the GetQuotation, Submit or Cancel previously submitted
requests wsa:RelatesTo
The following sequence diagram explains the usage scenario of Submit, Cancel and GetQuotation operations:
Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
99 Copyright © 2012 Open Geospatial Consortium
wsa:ReplyTo=client RI,
wsa:MessageI =request 1
Client Client
Server Server
3: Submit 4: SubmitResponse
5: SubmitResponse
: Cancel 7: CancelResponse
8: CancelResponse wsa:RelatesTo=request
1
wsa:ReplyTo=client RI,
wsa:MessageI =request wsa:RelatesTo=request
wsa:RelatesTo=request wsa:RelatesTo=request
1 1: GetQuotation
wsa:ReplyTo=client RI,
wsa:MessageI =request 2: GetQuotationResponse
wsa:RelatesTo=request
Figure 7-16 - Asynchronous requests scenario.
The previous figure explains the sequence of requests and responses for asynchronous operations Cancel, Submit, GetQuotation. The asynchronous interaction is performed in 2 steps:
Step1. The client sends a SOAP request to the server and receives an acknoweledge from it.
– Submit: o Client request: Submit;
o Server response: SubmitAck. – Cancel:
o Client request: Cancel; o Server response: CancelAck.
– GetQuotation: o Client request: GetQuotation;
o Server response: GetQuotationAck.
Step2. The server sends the SOAP notification to the client i.e. it calls an operation implemented by the
client and receives an acknoweledge from it.
Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
100 Copyright © 2012 Open Geospatial Consortium
– Submit: o Server Notification i.e. it issues a SubmitResponse request and Client Response
SubmitResponseAck. – Cancel:
o Server Notification i.e. it issues a CancelResponse request and Client Response CancelResponseAck.
– GetQuotation: o Server Notification i.e. it issues a GetQuotationResponse request and Client Response
GetQuotationResponseAck. This mechanism is not the only one supported by this specification for notifying the clients. In fact it is
also supported the WS-notification standard See clause 7.5.
7.4.4 statusNotification element
