We follow the Teradata Studio Express (TSE) wizard trying to connect to JBoss Dev. Studio 7.1.1.GA (Teiid Runtime ver. 8.4.1-redhat-7) using Teiid's jdbc driver but although the jdbc URL and the rest of the paremeters get setup correctly and the connectivity test comes back succesfull, we get a couple of Eclipse errors and the connection fails.
We experimented with 2 TSE editions, namely, ver 14.10.01 and 15.00.02 and other Teiid jdbc drivers, just in case we get a quick solution to the problem but no luck.
We can't use another 3rd party JDBC/ODBC query tool per customer's request so it must be some edition of TSE.
Any ideas how to either resolve or circumvent this problem will be greatly appreciated.
The errors we get come into a window titled "Multiple problems have occurred".
Two errors reported:
Stavros, As JBoss Teiid is not one of our supported database servers, I have not tried connecting. Have you followed the steps in thie JBoss guide at http://docs.jboss.org/teiid/7.0.0/client-developers-guide/en-US/html/teiid_connection.html#connectio...
You will need to create a New Driver Definition on the New Connection Profile page. In the Name/Type tab, give it a unique Driver Name. In the JAR List tab, specifiy the location of the Teiid JDBC library. In the Properties tab, specify the URL for teiid:
Specify the Driver Class name. You can use the elipse to choose the class file from the Jar. Specify the User ID and Database Name and any other properties needed.
First of all I'd like to thank you for replying to our request.
The steps as you described them are exactly the process we followed to setup a connection to Teiid from TSE. The only available option for a JDBC Driver was the 'New Generic JDBC' driver which we use to setup the driver definition using Teiid's jdbc driver and then a connection profile that although it had a successfull connectivity ping, there was nothing coming back from Teiid, only the 2 errors we mentioned up above.
Thanks to Redhat tech. support and a lady engineer who tried the following that worked perfectly fine. All credit goes to her.
The way to workaround the TSE Generic JDBC issue is to create an "Oracle" connection as a new connection profile, add a new driver, for which you need to select "Other Driver", and set all the correct driver classes and URL. That'll allow TSE to connect to a JBoss Data Virtualization virtual Database.
The connection profile properties showed as follows for us:
Drivers: Other Driver
user name: preferredUserName
driver class can be specified manually as org.teiid.jdbc.TeiidDriver
We hope this helps some one else out there.