ColdFusion 9 / UniVerse database access

[LSH1]

We have recently upgraded to ColdFusion 9 from ColdFusion MX 7, and we cannot get our UniVerse driver (IBM JDBC Driver for UniData and UniVerse, version 10.3) to work with the newer version of ColdFusion.  I have verified that the ColdFusion Class Path settings point to the location of the unijdbc.jar and asjava.zip files, and the datasource settings in ColdFusion 9 are the same as they were in ColdFusion 7:

CF Data Source Name: uvjdbc

JDBC URL: jdbc:ibm-u2://[server IP address]/UVODBC;dmbstype=UniVerse;

Driver Class: com.ibm.u2.jdbc.UniJDBCDriver

Driver Name: uniJDBCDriver

User name: [valid user name]

Password: [valid password]

Where UVODBC is the name of the UV account that the user logs into, in our case UVODBC.

The error I get (immediately, no delay) is:

Connection verification failed for data source: uvjdbc
java.sql.SQLException: Timed out trying to establish connection
The root cause was that: java.sql.SQLException: Timed out trying to establish connection

Are there any other users on ColdFusion 9 connecting to a UniVerse database?  Or does anyone have any theories as to why this would no longer work with ColdFusion 9?

Thanks in advance.

[Adam Cameron.]

Did you get this sorted out?

--

Adam

[LSH1]

Not yet.  I did remove all my classpath settings and found I'm getting the same error, so it seems as though it's never even finding the driver (?)

[Adam Cameron.]

OK. I D/Led and installed UniVerse on the w/end and then decided... hang-on... this issue is quite old maybe they've sorted it and I'm wasting my time.  Fortunately (for me, anyhow 😉 not.

I'll continue having a look at it when I find some time... my actual day job tends to get in the way during the week though...

--

Adam

[Adam Cameron.]

Sigh.

I've installed UniVerse and UniVerse Admin and have now come to connect to the DB.  It wants a user name and a password, which is entirely fair enough, but at no point during the installation did it ask me for default admin a/c info.  So I guess there is a UniVerse version of scott/tiger that I should be using, but I'm buggered if I can find any useful docs on this system on the 'net.  Am I missing something?  Do you know what the default system admin login & pwd is?  Or where I should be expecting to find it out?

--

Adam

[Adam Cameron.]

Aha.  It uses my local Windows login & password.  So I'm in... and fumbling around...

--

Adam

[Adam Cameron.]

OK: I give up.  This UniVerse thing is too arcane for my liking, and I can't work out how to get the admin app to do anything useful like create a DB or tablespace or user or anything that one might want to do with a DB admin tool.  I guess I have been spoilt by the likes of SQL Server, Oracle, MySQL, Access etc in that one can pretty much intuit how to do this stuff via the supplied admin UI.  I also don't think learning this stuff is a particularly useful skill for me to have, so I'm chucking it in.

Sorry.  Tried to help.

--

Adam

[LSH1]

Thanks for your efforts.  UniVerse is not a very common database but in the past I have been able to find other UniVerse/ColdFusion users, so I'm hopeful that I will eventually be able to get this resolved.  For now though the upgrade to CF9 is on hold.

[Bill Brutzman]

I experienced the same problem...

I wrote a little java program based on the sample program in the Rocket Software (IBM) manual,  The command...

  Class.forName("com.u2.ibm.jdbc.UniJDBCDriver");   does not work.

I created a tech support incident with Rocket.  I am hopeful that Rocket will come up with a fix.

[Bill Brutzman]

When the connection string was encapsulated in a try/catch/finally snippet, the code worked.  The tech support rep at Rocket Software (Mike Rajkowski) was glad to be made aware of this finding.

Perhaps there is a direct way to crank this try/catch into the connection string.  Failing that, I expect to contact Adobe Tech Support for help..

[LSH1]

So did you have any luck getting a datasource set up or did you just get it to work in the java program you wrote?   And did you have to actually catch any errors or are you saying just encapsulating it in the try/catch/finally snippet was all it took to get it to work?  At this point we've had to cancel our plans to move forward with CF 9 because running queries against our UniVerse database is so critical.

[Bill Brutzman]

DataSource... not yet... but it is my top priority.

I do not really care about the little Java program except as a crutch to move forward to the DataSource question.

I expect to spend a few minutes trying to use the Java code to establish the connection string.  If I myself cannot get it to work, I hope that Adobe CF Tech Support will be able to address the problem without having to have a UniVerse server handy.

Of course, I expect to follow-up on this forum with the (positive) answer.

[LSH1]

Thanks for the update - I'll be sure and post if I make any breakthroughs as well.

[Bill Brutzman]

Yes... encapsulating the Class.forName in try/catch was all that it took to get the Java code to work.

The sample IBM Java code by itself did not work.  The IBM code had to be encapsulated in try/catch in order to work.

[Bill Brutzman]

Victory... How sweet it is.  I am able to Connect CF9 to our UniVerse 10.1...ok.

It appears that the problem with the settings given in the original post is nothing more than the pesky

     dbms = UniVerse

Please just delete this text and try to connect.

If still problems, in the CF9 admin, go to \\Server Settings \ Java and JVM \ ColdFusion ClassPath

Put in C:\Rocket\unijdbc.jar, c:\Rocket\asjava.zip, %CLASSPATH%

Copy the unijdbc.jar and asjava.zip to the C:\Rocket\ folder.

It is noteworthy that that the path to these files no longer includes ...\UniClient\...

If there are still problems there, please let the forum know and I will dope out all of the fields in a follow-up post.

Good luck and

Regards,

--Bill

[LSH1]

I tried removing that (dbmstype=UniVerse) from the connection string and it didn't seem to change anything.  I already had the unijdbc.jar and asjava.zip files referenced in my ClassPath, so I think those are okay (different directories than yours but I verified that the files are where I'm pointing to).  Would you mind posting your exact datasource settings so I can double-check mine one more time?

Thanks!

Connection verification failed for data source: uvjdbc
java.sql.SQLException: Timed out trying to establish connection
The root cause was that: java.sql.SQLException: Timed out trying to establish connection

[Bill Brutzman]

Yes... will do... it will take a few minutes.

[Bill Brutzman]

CF DSN: Gull.Shipping

JDBC URL: jdbc:ibm-u2://192.168.0.102/SHIPPING

Driver Class: com.ibm.u2.jdbc.UniJDBCDriver

Driver Name uniJDBCDriver

User name: ups

password: xxx

[Bill Brutzman]

If still problems, I believe that there is an update patch for CF9.  I have not applied it yet.

[LSH1]

Well still no luck for me but knowing that you have it working has given me hope.  My datasource settings are identical to yours, and as far as I can tell my classpath settings should be fine, but I think somehow that's where my problem lies.  I do wonder if you have a different version of the driver, since yours installed to C:\Rocket (mine is still going to C:\IBM by default). Unless you just changed your install path to Rocket during the installation.  Do you know if you're using the IBM JDBC Driver for UniData and UniVerse, version 10.3?

Thanks for keeping me updated on your progress - I'm glad it's working for you.

[Bill Brutzman · Accepted solution]

1.  While this forum is great, I do not know how to cut and paste text to the screen.  Thus..

2.  Feel free to contact me... the best way is Brutzy@gMail.com as this will forward to two other eMail addresses.

4.  If I had your real eMail I could send over the Java program... it is maybe 50 lines of code.

5.  When changing Java and JVM settings on the CF9 admin... it forces the operator to do a reStart of the main CF9 Service in WIndows Server.

6.  I believe that I am using the 10.3 classpath files.

7.  My asjava.zip is 113KB   115,661 bytes

8.  My unijdbc.jar is 158kb    161,304 bytes

9.  Consider unzipping asjava.zip

10.  When I changed the Java and JVM settings on the CF9 admin screen, I did not bother to update the ClassPath on the environment variable on the Windows server.  Thus, I expect that the Java and JVM settings in CF9 overRide or augment with environment's classpath settings.

11. Consider obtaining fresh copies of the classpath files.

12. Ben Forta of CF fame encourages CF developers to install CF on their local machine for development as well as the production server.  While the production server is of course the main event, consider installing CF on the local machine.

13. Consider using forward slashes in the Java and JVM settings on CF9.  My settings use both.

14. If I had your eMail, I could do screen shots.

15. Consider renaming a copy of asjava.zip to asjava.jar.  This is an interesting trick I just picked up.

16. Consider reInstalling CF9.

Regards,

--Bill