JDBC Metadata Explorer | X4Documentation

The adapter connects to a JDBC-compliant database and determines metadata about the database, tables and columns, and stored primary and foreign keys. The adapter expects an input XML document with adapter-specific structures to query the desired metadata.

Properties

Operation

Describes which operation the adapter performs.

Possible values: execute: Runs the adapter

Parameters

JndiName	JNDI name of the DataSource If the connection is made using the JNDI name, the `connectionURL` parameter must not be filled in. Possible values: Valid JNDI name (e.g. `java:/DefaultDS`)
ColumnCase	Controls how the column names are transferred to the result. Since databases have different behavior regarding the case of column names, it is possible to make further processing of the result independent of the database behavior. Possible values: `NO_CHANGE`: Does not change the column names, i.e. the notation in the result is exactly as supplied by the database (default) `TO_LOWER`: Changes the column names to lowercase `TO_UPPER`: Changes the column names to uppercase characters Column names that do not represent valid element names (`NCNAME`) are replaced by `_<number>` (e.g. `_2` ), where `<number>` is the index of the column.
connectionURL	Connection URL for the JDBC database If the connection is made using the connection URL, the `JndiName` parameter must not be filled in. Possible values: The type of setup depends on the database to which you want to connect. Example of sqlite: `jdbc:sqlite:C:/temp/mydatabase.db`
user	User name used for authenticatation when using the `connectionURL` parameter
password	Password used for authentication when using the `connectionURL` parameter

Status values

`1`	The operation was successful.
`0`	The operation was executed successfully, but without results.
`-1`	The operation failed due to a technical error.

Input

The JDBC Metadata Explorer expects specific input XML structures that can contain one or more of the metadata queries described below, as needed. These input XML structures can be dynamically generated via XSL mappings depending on the data processed.