Aug 18, 2009 3:52 PM
EGL data access to DB2 on IBM i doesn't work, jt400.jar might be old
Hi folks, I have seen this happen now a couple of times so I thought I append this info here, so people might be able to find this tip.
If you have DB2 for Windows installed on your workstation there is the following scenario.
When you use the EGL data access application wizard and create a connection to IBM i, the data source is automatically created with this wizard and the class location for the jt400 driver is created pointing to the DB2 directory SQLLIB\tools . The problem is that this jar is totally outdated, it is from 2004. When you try to connect to IBM i with this old jar you will get a connection refused message in the app server console.
You can fix this by copying a newer version of the jt400.jar into the SQLLIB\tools directory, or by pointing to another location that contains a newer jar.
If you go to the properties for the project that contains the EGL data access application and look at the EGL Runtime Data Source property and select the generated data source. You can see the class location that has been generated.
This seems to be behavior that got introduced with RBD V7.5.1, I don't think I have seen this before. Check the data source jt400.jar file when in doubt why a connection doesn't work.
Claus