Fabric supports creating a new custom interface type based on a JDBC driver's specifications or overriding existing database types without the need for product enhancement. Once saved, the database type appears in the Interface type list and can be selected when creating a new Interface.
A new database type can be created from a template to customize a built-in database type or when a new database type is very similar to an existing type. When creating a database type from a template based on an existing database type (e.g. Oracle), make sure to save it according to your needs: either with the same name (Oracle) in order to override default configurations, or with a different name, which will be handled as a new database type, alongside the original. You can also create a new database type, from start, which is not based on a template.
To create a new custom interface type/database type based on a template, do the following:
oracle.jdbc.ReadTimeout=10000
oracle.jdbc.ReadTimeout=10000
To create a new custom interface type/database type from start, do the following:
&abc=[useSSL]
abc=false
When introducing a new database type, the JDBC driver is saved under: [Fabric Project's Directory]/[Project Name]/lib/[new database type]. Each database type is kept in a separate folder in order to avoid overlapping or conflicts with other drivers (dynamically loaded). When creating a new custom interface type, such folder is automtically created, so that you just need to drop there the driver files. Note that since Fabric 8.0 the JDBC drivers are part of the Fabric Deployment process.
Fabric supports creating a new custom interface type based on a JDBC driver's specifications or overriding existing database types without the need for product enhancement. Once saved, the database type appears in the Interface type list and can be selected when creating a new Interface.
A new database type can be created from a template to customize a built-in database type or when a new database type is very similar to an existing type. When creating a database type from a template based on an existing database type (e.g. Oracle), make sure to save it according to your needs: either with the same name (Oracle) in order to override default configurations, or with a different name, which will be handled as a new database type, alongside the original. You can also create a new database type, from start, which is not based on a template.
To create a new custom interface type/database type based on a template, do the following:
oracle.jdbc.ReadTimeout=10000
oracle.jdbc.ReadTimeout=10000
To create a new custom interface type/database type from start, do the following:
&abc=[useSSL]
abc=false
When introducing a new database type, the JDBC driver is saved under: [Fabric Project's Directory]/[Project Name]/lib/[new database type]. Each database type is kept in a separate folder in order to avoid overlapping or conflicts with other drivers (dynamically loaded). When creating a new custom interface type, such folder is automtically created, so that you just need to drop there the driver files. Note that since Fabric 8.0 the JDBC drivers are part of the Fabric Deployment process.