Describes the configuration for a VDB
An imported VDB is reused in the context of this VDB.
A model defines the alias for the Schema the data being integrated. In the Designer
built VDB, the Schema for this model is defined by external index files. In the "Dynamic VDB"
this defines the importer properties along with "source" information the Schema
is generated at deploy time.
A source defines access to physical data source with its connection-jndi-name.
translator-name defines a translator. Translator is a layer between Teiid engine and data source
that knows how to convert and execute commands native to source. Teiid offers various
pre-built translators.
Schema metadata (tables, views, stored procedures, functions)
definitions of the model. If this defined on source model, it becomes source metadata,
on virtual model it become view metadata where user can define the logical layer
When Schema files for model defined by Designer, the validation-errors define
any errors in the schema. This is not applicable in the Dynamic VDB scenario.
When the pre-built translator's behavior need to be altered, this optional element need to
be used to override them.
This defines a data role. The "resource-name" element defines fully qualified
name for a Schema, Table, Procedure, etc. The "allows-*" elements define the security access, which are applied to the resource
and all child resources. The "mapped-role-name" defines the "role" name that user must have before they have access to this data.
The "role" name matches to the JAAS based role that user has.
With Designer based VDBs, this element is used to define extra files that are
defined inside the VDB archive. Not applicable for Dynamic VDBs
property