This extract is used to read data from XML files and Web Services in a tabular form. An XmlFile, REST, or SOAP connection is needed.
The extract definition uses XPath language, which is a standard query language for selecting nodes from an XML document. You can find more information on XPath at www.w3schools.com/xml/xpath_intro.asp.
Note: REST connections with HTTP mode POST can no longer be used in XML/JSON extracts in Jedox 2019.3. They have to be used as connection in a XML/JSON load instead. To get the XML/JSON response for a REST connection with HTTP mode POST, a Groovy job must be used.
|XPath loop expression||
Drop-down list of reasonable XPath expressions that specify the root or anchor elements of the XML document that will be looped through. The number of elements applying to this expression gives the number of output rows.
Expressions can also be entered manually.
Drop-down list of expressions that define a column of the extract output or the xpath from the XMLloop expression. For each column, a name and a default value can be defined. All space, multiple space, or null values will be mapped to this default value.
XML documents may contain namespaces. The declaration of these namespaces in the XML extract is optional; it can be omitted if the XML structure has no naming collisions without namespaces. To declare a namespace, a prefix has to be defined for the URI of the namespace. This prefix is then used in the XPath expressions to identify the correct XML nodes.
If caching is activated, the complete output of the extract is temporarily stored during the first call of the extract, using an internal H2 database. Subsequent calls of the extract read directly from the cache without connecting to the underlying source system of the extract. If the extract or the underlying connection contain variables, a separate cache is build for different values of these variables.
See Caching in Extracts for more information.