Access level: read, write
With XMLFile connection, an XML-structured file can be specified.
PGP encryption and decryption are supported for file-based connections, such as
Connection settings
| Type | The following file locations are supported: |
| File / Directory settings | File:file name is the path to the file.
The syntax of the file name is location-specific. Directory: directory name is the path to the directory containing the files. For root, use "/". File pattern (optional) is a regular expression on the filenames for the selection of files in the directory. Select the option Recursive to include all subdirectories within the chosen directory. |
| Decryption method | Decryption method is only relevant when extracting data from an encrypted file. For PGP decryption, enter the passphrase that was set during key creation. The key will be a private / secret key. See for details. Directory connections will only work if the same passphrase can be used for all files (either the files use keys without passphrase, or the keys for the files have the same passphrase). |
| Encryption method |
For PGP encryption, a public key ID is required; this can be obtained from the "name" column in the Keys & Secrets section of the Cloud Console. |
| Encoding | The most common character encodings are UTF-8 (default), ASCII, and latin1 (Windows standard).
A list of all character codes can be found at http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html From this list you can also enter manually a character code into the field ‘Encoding’. Note that this connection only supports file encodings as provided by the Java Runtime Environment. |
| XSD schema file | If set, the XML file is validated against the XSD Schema. For extracts, this is done for the existing XML file; for loads, this is done against the created XML file.
The XSD file is taken from either
|
| XSD validation | Defines the behavior in case of a validation error against the XSD Schema:
|
Updated September 12, 2025