Configuring DataDirect Test
- Last Updated: August 6, 2018
- 1 minute read
- DataDirect Connectors
- JDBC
- Aha! 6.0
- Amazon Redshift 6.0
- Apache Cassandra 6.0
- Apache Hive 6.0
- Apache Spark SQL 6.0
- Atlassian Jira 6.0
- Autonomous REST Connector 6.0
- Cloudera Impala 5.1
- + 24
The default DataDirect Test configuration file is:
install_dir/testforjdbc/Config.txt
where:
- install_dir
- is your product installation directory.
The DataDirect Test configuration file can be edited as appropriate for your environment using any text editor. All parameters are configurable, but the most commonly configured parameters are:
| Drivers | A list of colon-separated JDBC driver classes. |
| DefaultDriver | The default JDBC driver that appears in the Get Driver URL window. |
| Databases | A list of comma-separated JDBC URLs. The first item in the list appears as the default in the Database Selection window. You can use one of these URLs as a template when you make a JDBC connection. The default Config.txt file contains example URLs for most databases. |
| InitialContextFactory | Set to com.sun.jndi.fscontext.RefFSContextFactory if you are using file system
data sources, or com.sun.jndi.ldap.LdapCtxFactory
if you are using LDAP. |
| ContextProviderURL | The location of the .bindings file if you are using file system data sources, or your LDAP Provider URL if you are using LDAP. |
| Datasources | A list of comma-separated JDBC data sources. The first item in the list appears as the default in the Data Source Selection window. |
To connect using a data source, DataDirect Test needs to access a JNDI data store to persist the data source information. By default, DataDirect Test is configured to use the JNDI File System Service Provider to persist the data source. You can download the JNDI File System Service Provider from the Oracle Java Platform Technology Downloads page.
Make sure that the fscontext.jar and providerutil.jar files from the download are on your classpath.