Teiid is relational data integration engine that can combine the data from multiple heterogeneous sources.
This is a Reference guide for Teiid Spring Boot, for general Teiid Reference Guide consult link:http://teiid.github.io/teiid-documents/master/content/
Please read the User Guide to understand the problem this library is solving, this guide is more about description of the annotations in play.
Most of the Teiid specific functionality is hidden in the set of Annotations provided by this framework. Annotations are used on a Entity class. If you are familiar with regular Teiid, consider that creating an Entity is equivalent creating a View. Using the annotations, this system gathers metadata about the View, similar to what you may have done using Teiid Designer or using DDL. Most of these annotations still require the user to define the DDL underneath as is in previous tools. But at the same time this library makes use of JPA annotations to define Entity structure. So, consider the below are extensions to JPA annotations that bring virtualization capabilities to a JPA based application without all the jargon of Teiid or a separate independent virtualization server.
The below are list of annotations that are part of the library, please refer to the JavaDoc of the annotation for detailed explanation and possibly code examples.
This probably is MOST important and MUST have annotation on any Entity classes that is being defined to read data or join data from two different sources. This defines the transformation query of the view. Take look at Javadoc for usage.
If your entity is joining the data from multiple sources, this annotation will provide a hook for a procedure where you can define the "insert" behavior. You can completely control which sources you want to update internally when a "insert" on Entity comes in from user. Take look at Javadoc for usage.
If your entity is joining the data from multiple sources, this annotation will provide a hook for a procedure where you can define the "update" behavior. You can completely control which sources you want to update internally when a "update" on Entity comes in from user. Take look at Javadoc for usage.
If your entity is joining the data from multiple sources, this annotation will provide a hook for a procedure where you can define the "delete" behavior. You can completely control which sources you want to update internally when a "delete" on Entity comes in from user. Take look at Javadoc for usage.
Unlike other annotations this annotation is used to read a CSV or fixed format text file. The Entity on which it is defined will behave exactly as if data were defined in a Database in like JPA to the user. Take look at Javadoc for usage.
This annotation is similar to @TextTable, but provides a way to read a JSON payload into an Entity class. You can read the payload from a web resource or read from file location. Take look at Javadoc for usage. Also find find more complex example in samples.
This annotation is to read a Excel file into an Entity from a file location. See Excel translator in Teiid for more information Microsoft Excel Translator
If you want to use a source specific function (like SOUNDX in Oracle) that is not already defined by Teiid, then you can define this annotation on a Java Method that mimics the signature of the function in the source database. Then you can use this function in any of your queries. This Java method needs to be defined on a class that is annotated with @UserDefinedFunctions. The evalution of this functions will be pushed to source. Take look at Javadoc for usage. For more information see in Teiid documentation Source Supported Functions
If you want to define a user defined function (UDF) based on java code, that you can use in your Teiid queries, then you can define this annotation on a Java Method and supply the implementation of the method in Java. This Java method needs to be defined on a class that is annotated with @UserDefinedFunctions. Take look at Javadoc for usage. For more information see in Teiid documentation Support for User-Defined Functions (Non-Pushdown)
| Property | Description | Default Value |
|---|---|---|
spring.teiid.model.package |
This property defines the package name, where the @Entity classes are defined in the application. This will be used to scan the classes and generate necessary metadata. In absence of this property whole classpath will be scanned which can lead very slow start up |
* (all classpath) |
logging.level.org.teiid.{context} |
Defines the logging level for Teiid specific code. "spring" is context where spring boot specific log messages are defined. example: logging.level.org.teiid.spring=DEBUG |
n/a |
spring.teiid.file.parent-directory |
When using the "file" based resources such as @TextTable, @ExcelTable this property defines a parent directory where files exist. |
${user.dir} system property. |
For configuring the JDBC data sources please see Data Access
| Property | Description | Default Value |
|---|---|---|
spring.datasource.{dsname}.platfrom |
Name of the platform, where when init SQL queries for the database are provided this will be used ad postfix. See rdbms-file-example for example. |
n/a |
| Property | Description | Default Value |
|---|---|---|
spring.teiid.odata.xxx |
Any connection properties. ex:batch-size,skiptoken-cache-time, |
n/a |
spring.teiid.odata.alt.paths |
Comma separated context paths that should be redirected from OData context handler. This will be useful when user wants handle custom paths in addition to OData. ex: /api,/foo where when a request comes for these paths they will redirected to registered servlet. To Register a servlet see https://www.baeldung.com/register-servlet |
n/a |
| Property | Description | Default Value |
|---|---|---|
teiid.jdbc-enable |
Enable the non-secure Teiid JDBC transport. By default login and other secure traffic will be encrypted with an ssl like protocol based upon 128 AES encryption based upon a DH key exchange. |
false |
teiid.jdbc-port |
Teiid JDBC port |
31000 |
teiid.jdbc-secure-enable |
Enable the SSL Teiid JDBC transport. See the SSL properties for more. |
false |
teiid.jdbc-secure-port |
Teiid JDBC secure port |
31443 |
teiid.pg-enable |
Enable the non-secure PG transport. Currently only cleartext username/password authentication is supported, so you should consider instead using the secure pg transport |
false |
teiid.pg-port |
PG port |
35432 |
teiid.pg-secure-enable |
Enable the SSL PG transport. See the SSL properties for more. |
false |
teiid.pg-secure-port |
PG secure port |
35443 |
By default a secure transport will use the system options (javax.ssl…) to create secure sockets. If you cannot utilize the system properties, you may use a Teiid specific SSL configuration, which is shared by both PG and Teiid JDBC secure transports.
Property |
Description |
Default Value |
teiid.ssl.ssl-protocol |
The SSL/TLS protocol |
TLSv1.2 |
teiid.ssl.enabled-cipher-suites |
A comma separated list of cipher suites that are allowed |
teiid.ssl.keystore-password |
The keystore password |
teiid.ssl.keystore-type |
The keystore type |
JKS |
teiid.ssl.keystore-key-alias |
The keystore key alias |
teiid.ssl.keystore-key-password |
The keystore key password |
teiid.ssl.keymanagement-algorithm |
The key management factory algorithm |
System default |
teiid.ssl.authentication-mode |
1-way or 2-way, 2-way requires the system truststore or a configured truststore to authenticate the client certificate |
1-way |
teiid.ssl.truststore-filename |
The truststore file name |
teiid.ssl.truststore-password |
The truststore password |
teiid.ssl.truststore-check-expired |
If client certificates should be checked for expiration |
false |