An XML via HTTP step is defined for an HTTP-XML system connection and defines a URL called by the Agentry Server and also defines how the XML data returned from this call is mapped to the data members of the mobile application. This step includes two child definitions that encapsulate the arguments passed by the Server to the defined URL, and the mapping of return values to the data members of the application. An XML via HTTP step is defined for a specific definition type within the same module.
The first information entered for an XML via HTTP step is the definition for which it is defined, which may be an object, transaction, or fetch. This information is needed by the step definition for use in its child definitions, which must have access to the property values of the selected data definition as a part of their behaviors.
Within this step type is the HTTP request. This portion of the step defines the URL called by the Agentry Server and the HTTP request method. This may be one of GET, HEAD, POST, or PUT.
The child definitions to an XML via HTTP step include its request arguments and response mappings. Request arguments provide access to the property values and other data values in scope for the step to be passed to the URL defined by the step. Included in this definition is the type of argument the data represents.
Response mappings extract data from the structured XML data or document returned from the request. They may use of XPaths to locate and retrieve these values from the XML and define to which property or other data member of the application the XML contents will be mapped. Response mappings may be used to extract a specific XML element’s contents, or a parent element may be specified with a second, child element within that parent of which there may be multiple instances.