- 1. Data Sources Summary
- 2. JDBC Connections
- 2.1. DB2 Connection Profiles
- 2.2. Derby Connection Profile
- 2.3. DB2 Connection Profile
- 2.4. Informix Connection Profile
- 2.5. Ingres Connection Profile
- 2.6. MaxDB Connection Profile
- 2.7. Modeshape Connection Profile
- 2.8. MySQL Connection Profile
- 2.9. Oracle Connection Profile
- 2.10. PostgreSQL Connection Profile
- 2.11. SQLite Connection Profile
- 2.12. SQL Server Connection Profile
- 2.13. Sybase Connection Profiles
- 2.14. Teiid Connection Profile
- 2.15.
Teiid Designer provides the ability to model, federate, virtualize, test and access your various and disparate data sources. These data sources come in many forms and formats. This references guide documents the data sources supported by Teiid and describes how each data source connection should be created and managed in Teiid Designer.
The matrix below indicates for a given data source how a model can be created (Designer Import Option) and how the data source is integrated (Translator) for data access.
Note
The DDL Import option is an available option to build a source model for any data source. Note there are some data source types where no specific importer is available.
Table 1.1. Teiid Designer Supported Data Sources
| Data Source | Translator Type | Designer Import Option |
|---|---|---|
| Apache Derby | JDBC - derby | JDBC Importer |
| Files | file | File Importer |
| General JDBC | JDBC - jdbc-simple | JDBC Importer |
| HDFS (Hadoop) | hive | use DDL importer or perform modeling manually |
| HSQL | JDBC - hsql | JDBC Importer |
| H2 | JDBC - h2 | JDBC Importer |
| Ingres |
| JDBC Importer |
| IBM DB2 | JDBC - db2 | JDBC Importer |
| Informix | JDBC - informix | JDBC Importer |
| LDAP/ActiveDirectory | ldap | LDAP Importer |
| LoopBack | JDBC - loopback | use DDL importer or perform modeling manually |
| MetaMatrix | JDBC - metamatrix | JDBC Importer |
| ModeShape/JCR | JDBC - modeshape | JDBC Importer |
| MongoDB | mongodb | model manually |
| Mondrian | olap | use DDL importer or perform modeling manually |
| MS Access | JDBC - access | JDBC Importer |
| MS Excel | JDBC - excel-odbc | JDBC Importer |
| MS SQL Server | JDBC - sqlserver | JDBC Importer |
| MySQL | JDBC - mysql5 (mysql) | JDBC Importer |
| Netezza | JDBC – netezza | JDBC Importer |
| Oracle | JDBC - oracle | JDBC Importer |
| PostgreSQL | JDBC - postgresql | JDBC Importer |
| Salesforce.com | salesforce | SalesForce Importer |
| SAP Gateway | ws | File Source (XML) Importer |
| SAP R/3 | ws | |
| SAP Services Registry | ws | WSDL Importer |
| Sybase ASE | JDBC - sybase | JDBC Importer |
| Teradata | JDBC - teradata | JDBC Importer |
| Teiid | JDBC - teiid | JDBC Importer |
| Web Services (SOAP/WSDL) | ws | WSDL or URL Importer |
| Web Services (Rest/OData) | ws | File Source (XML) Importer |
The driving factor for connectivity from the Teiid runtime is based on the concept of translators. Translators represent deployed runtime code that performs the function of communicating with the actual data source and transforming the data from it's native structures and properties into common Teiid-defined metadata. The translators available in Teiid 8.4 release are:
Cassandra
Delegating
File
Google Spreadsheet
JDBC
JPA
LDAP
Loopback
MongoDB
Object
OData
Salesforce
SAP Netweaver Gateway
SimpleDB
Web Services
JDBC Connections
Connections pertaining to the JDBC (Java DataBase Connectivity) API see: Chapter 2, JDBC Connections
Open Data Access (ODA) Connections
Connections adhering to the ODA spec such as MongoDB, Flat File (CSV) etc.
Custom Teiid Connections
Connections defined for Teiid-specific translators not covered via JDBC or ODA
In Teiid Designer, the following ODA Connection Profiles options are available:
BIRT Hive
BIRT JDBC
BIRT POJO
BIRT Sample DB
Excel
Flat File - Local File System
The file system flat file data source is designed to represent one of 2 file structures.
Folder containing multiple delimited files containing data representing identical column data for single table definition. For this case, the usage pattern will involve using a file definition in your view SQL consisting of a "*" wildcard.
Folder containing multiple delimited files containing data for multiple table definitions. For this case, each file will be modeled separately and each view will contain SQL specific to the file name (table) that it represents.
The primary wizard page contains inputs for home folder or file URI. There are also options for setting:
Character Set
Flat File Style includes:
CSV formatting (Comma ',' separated values)
SSV formatting (Space ' 'separated values)
PSV formatting (Pipe '|' separated values)
TSV formatting (Tab separated values)
Additional properties can be set including:
Use first line as colmumn name
Use second line as datatype
Use trailing null columns
MongoDB
Web Services - WSDL
XML Data
- 2.1. DB2 Connection Profiles
- 2.2. Derby Connection Profile
- 2.3. DB2 Connection Profile
- 2.4. Informix Connection Profile
- 2.5. Ingres Connection Profile
- 2.6. MaxDB Connection Profile
- 2.7. Modeshape Connection Profile
- 2.8. MySQL Connection Profile
- 2.9. Oracle Connection Profile
- 2.10. PostgreSQL Connection Profile
- 2.11. SQLite Connection Profile
- 2.12. SQL Server Connection Profile
- 2.13. Sybase Connection Profiles
- 2.14. Teiid Connection Profile
- 2.15.
Teiid Designer utilizes the Eclipse Data Tools JDBC connection profile definitions. The following is a comprehensive definition of the available JDBC connection profiles.
TBD.
