XMLNoTemplateUnit

Class name

com.ebd.hub.datawizard.iu.XMLNoTemplateUnit


This Integration Unit creates an XML file from the target tree without using a template file like the XMLTemplateParserUnit and the XMLMemSaveTemplateParserUnit do, so you should preferably use this Integration Unit here. The target structure must be constructed according to some rules, though, that are mentioned below.

Parameters


Parameter

Allowed values

Default value

Description

Add certificate information

true, false

false

If true, the public certificate (i.e. without a private key) is added to the signature.

Certificate-ID for signing



If this parameter is filled with a valid ID of a local certificate (i.e. private key available), the XML file will be signed. The ID can simply be copied from the detail view of a certificate.

Force Carriage Return (\r -> \r\n)

true, false

false

\n stays \n, but a \r becomes \r\n and therefore #&xD\n; (only for data part).

Example: <Text1\r\nText2> becomes

&lt;Text1&#xD;

Text2&gt;

Insert this DOCTYPE declaration



The DOCTYPE declaration to be added after the generation of the XML file. The DOCTYPE cannot be part of the template since the underlying XML generator would abort the generation in that case. Note: If you want to use an XML header other than the default header <?xml version="1.0" encoding="UTF-8"?>, you can specify it here. If you do, also use parameter Without XML-Header=true to remove the default XML header.

Mem save swap threshold


1000

If Use mem save method = true the threshold is set here. It specifies the number of elements after which data is swapped to the file system.

Pretty format

true, false

true

true creates a formatting with indentations (2 spaces). With false there are no indentations. Note: If parameter Write xml in a single line is set to true , the setting here has no effect.

RSA signing algorithm

SHA-1 (RSA, DSA, ECDSA),
SHA-224
(RSA, ECDSA),
SHA-224-MGF1
(RSA),
SHA3-224-MGF1
(RSA),
SHA-256
(RSA, DSA, ECDSA),
SHA-256-MGF1
(RSA),
SHA3-256-MGF1
(RSA),
SHA-384
(RSA, ECDSA),
SHA-384-MGF1
(RSA),
SHA3-384-MGF1
(RSA),
SHA-512
(RSA, ECDSA),
SHA-512-MGF1
(RSA),
SHA3-512-MGF1
(RSA)

SHA-1

Algorithm for signing (see parameter Certificate-ID for signing). The digest algorithm adapts to the signing algorithm.

Remove given prefix from field or node name



Cuts off any custom-defined prefix. Note: This action is performed before the one described in the following parameter.

Replace D-_... and F_-... to _...


false

Replace field names D-_... and F-_... with _... (cuts off D- and F- from field name).

Root node name



The node of the target structure that becomes the root node of the XML (mandatory). Important node: If the root node uses a namespace, the parameter Use mem save method must be set to true.

Text mode (…)

normalize, preserve, trim, trim-full-white

trim-full-white

Configures the way, values are written into the XML file.

preserve - No changes will be made to the text. All whitespaces (leading, trailing, …) will remain in the XML file.

trim-full-white - Same as preserve with the exception that a text, containing only whitespaces, will be replaced by an empty text.

trim - All leading and trailing whitespaces of a text will be removed.

normalize - Same as trim with the addition, that 'inner' whitespaces are reduced to a single space (..1..2.. → 1.2, a dot represents a whitespace).

Type of signature

Enveloped, Enveloping

Enveloped

The type of the signature.

Use XML short form for empty fields

true, false

false

If true, use XML short form for empty fields (<element/> instead of <element></element>).

Use mem save method

true, false

true

If true, elements will be swapped to the file system if a certain threshold is reached. This is the preferred method for large volumes of data.

Use namespace Inheritance

true, false

false

If true, namespaces will be inherited.

With empty fields

true, false

false

If true, empty elements (_attr and _val empty) will be created in the XML file. Note: If this option is set to true, 'hidden values' (see the corresponding section in the explanations for the Empty Flag) are also written into the output file (e.g. default date values for unsuccessfully parsed values for source structure date fields).

Without XML-Header

true, false

false

If true, no XML header (e.g. <?xml version="1.0" encoding="UTF-8"?>) will be created.

Write mandatory empty fields

true, false

false

If true, elements for mandatory empty fields will be created in the XML file.

Write values containing white spaces only

true, false

false

If true, fields which only contain whitespaces will not be treated as 'empty'.

Write xml in a single line

true, false

false

If true, the entire XML will be written in a single line.

end of line


\n

Defines the line delimiter.

file encoding


UTF-8

The name of the character set to be written into the header of the XML file. Note: The encoding in the Response (phase 6) of the profile must be set to the same value to actually save the data with this character set. Otherwise parsing errors on the reading side will most likely occur (mandatory).

Control elements in the target structure for the XML creation


See section Control Elements in the Target Structure for the XML Creation.

Unique field names and reserved field names


See section Unique Names, Reserved Names (XML).

Procedure


  • Create the target structure. See section XML to XSD (to structure).

  • Select the Integration Unit and set parameter "Root node name". All other settings are optional.

  • Set the "Content" in a Response "File" to "Output of IU".