The XML WebServices Connection has to deal with more than just a data retrieval method when collecting the result of a data retrieval call or a key retrieval call through a HTTP request. It also has to know the structure of the HTTP request in which the data retrieval/key retrieval is send to the HTTP server. When data is returned to ITP the XML WebServices Connection has to know the location of the result data in the returned XML tree.
The structure of the HTTP message can be specified in templates, the location of the result data in the XML tree can be specified at the key RESULT_PATH at the entry in the DID.
HTTP Request
A HTTP request is composed from a HTTP Header and HTTP Content. The HTTP header and the HTTP Content are separated by an empty line.
One can specify a template for both the HTTP Content as well as for the HTTP header
HTTP Content of a HTTP request
The content of a HTTP message can be anything (is dependent on the structure the HTTP server expects). Therefore a content template must be specified in which the structure of the HTTP Content is specified.
HTTP header of a HTTP request
To support special custom headers and not supported standard headers, it is possible to specify a header template for the header.
HTTP response
A HTTP response is also composed from a HTTP Header and HTTP Content. The HTTP header and the HTTP Content are separated by an empty line.
HTTP Content of a HTTP response
The HTTP Content of the Response message has to be some XML structure. The key RESULT_PATH at the entry definition in the DID document specifies where in this returned XML tree the result of the KEY_RETRIEVAL and DATA_RETRIEVAL are located.
HTTP header of a HTTP response
All standard headers for the Response message are supported. Headers that are not supported are ignored by the XML WebServices Connection.