The behaviour under normal conditions:
- for sdd-wfs service, the Data Consumer sends the WFS or WFS-TE SOAP request and expects the corresponding SOAP response; the details of accepted requests are covered by SDD XML Primer section 2.3.6.2.
- for SDDDownloadWebService, the Data Consumer requests via the EAD Service Desk the creation of parameter sets in order to define WHAT DATA should be downloaded and WHEN the download should be performed.
You can find guidance on how to build parameter sets in the Operational User Handbook - Data User, which can be found in EAD Knowledgebase.
For download jobs, using AIMSL file distribution, the user will be provided with functionality that:
* Enables an AIMSL publish/subscribe topic for every subscribed user
* Notifies subscribed users about any download job status changes and errors via the created AIMSL topic
* Creates download and log files
* Provides a SOAP endpoint, registered as AIMSL Proxy, which accepts a download identifier and returns the log and download file matching the given identifier.
* Cleans up the created files and topics after the download.
The details of accepted requests are covered by SDD XML Primer section 2.3.6.2.