File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes Setting up Teradata DataSource in WSAD 5.1.2 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Setting up Teradata DataSource in WSAD 5.1.2" Watch "Setting up Teradata DataSource in WSAD 5.1.2" New topic

Setting up Teradata DataSource in WSAD 5.1.2

Stacey Roach

Joined: Jun 21, 2004
Posts: 5
Has anyone had any luck?

I need to setup a 5.0 data source with connection pooling to Teradata.

I established a Teradata JDBC provider pointing it at the com.ncr.teradata.TeraConnectionPoolDataSource class in the terajdbc4.jar file from NCR.

I then added a 5.0 data source, but I don't have or know of a Data Source Helper class for Teradata.

The options listed are:
But none of those seem to work for Teradata.

I then set up the properties:
DSName, user, and password each with a type of java.lang.String

Ultimately I am getting an issue in the javax.naming.InitialContext.lookup when its trying to open the JNDI reference.
[ November 05, 2004: Message edited by: Stacey Roach ]
Stacey Roach

Joined: Jun 21, 2004
Posts: 5
In case anyone needs a tutorial on this, here is what I did.

I downloaded and installed the latest JDBC drivers from Teradata/NCR (version

I edited my local hosts file (c:\\WINNT\\system32\\drivers\\etc\\hosts) and added two aliases to the server. example1 example1cop1

I then created a JDBC provider within the Data Source tab of the .wsi screen for WebSphere. I pointed the implementation class at com.ncr.teradata.TeraConnectionPoolDataSource and added both jar files within the class path.

Then I created a JNDI 5.0 data source and used as the Data Source Helper Class.

Then I added three properties, each of type java.lang.String: DSName, user, and password. DSName points to the entry in the hosts file. When I didn't do this, I kept getting an error about "default transaction mode" which I found a KB article about. Apparantly the cop1 entry is mandatory or something.

Now I had all of this setup for a few hours and still couldn't get it to would fail on the executeQuery statements with a null pointer exception. This was a problem with a version of the driver (fixed in 3.01.03 (reference: DR84904)) which seemed to be a problem I was causing myself (multiple copies of different jars loaded at once while trying to debug).
I agree. Here's the link:
subject: Setting up Teradata DataSource in WSAD 5.1.2
It's not a secret anymore!