JDBC on 10.1B

[RhymeAndReason]

Hi all!

I'm a complete Progress newbie, I have a million questions, and I feel terrible for just dropping in here and dumping them on you... but I have spent a lot of time trying to find the answers myself, and so far, no dice... so here goes.

I am trying to connect using the JDBC driver from a Windows box. I am running Progress/OE 10.1B on RedHat. I copied the drivers off the linux box and they appear to be working fine - ie - I know that my connect requests are reaching Progress.

So my questions:

1. What port should I be connecting too for JDBC, and how do I find that out? (I've looked in the ubroker.properties and hit all of those ports, and also hit the port shown under the showcfg)
2. Is there a special "broker" or some sort of daemon that I need to start specifically for JDBC connectivity? (or a start parameter when starting progress?)
2B. If there is a special daemon that is needed (or start parameter), how would I know if it is running or not?
3. Do I need to have the Progress Network Client installed on my Windows machine for this all to work? Or just the various .jars? (I haven't been able to install the network client, I don't know where it exists if there is a copy on the HD, and I haven't been able to get decent support from Progress as our vendor registered the OE licenses WE bought to themselves... arrrg)

I tried connecting with sqlexp using the same info and also couldn't connect. Same errors/ports as I saw using the JDBC driver.

On the port that I know agents are being brokered, I get this message back when I try to connect:

sqlexp -db dev -S 3095 -user xxxx -password xxxx
OpenEdge Release 10.1B as of Wed Jan 10 12:21:31 EST 2007
Connecting user "xxxx" to URL "jdbc:datadirectpenedge://localhost:3095;databaseName=dev"... (8920)
Error: [DataDirect][OpenEdge JDBC Driver]A server crash is likely.. (8933)

Thanks for any help you can offer... I really appreciate it.

 

[Casper]

Ok I just tested the following (used 10.1B03 on RH EL 4):



Copied from linux machine to local windows (vista SP2) directory:

1. $DLC/java/openedge.jar
2. $DLC/java/util.jar
3. $DLC/jave/base.jar

Setup driver for test purposes with Squirrel (http://squirrel-sql.sourceforge.net/#installation):

• Drivername: Progress 10.1B driver
• Example URL: jdbc:datadirectpenedge://hostort;databaseName=db_name;
• added to classpath:
• path-to-copied-jar/openedge.jar
• path-to-copied-jar/util.jar
• path-to-copied-jar/base.jar
• Class Name: com.ddtek.jdbc.openedge.OpenEdgeDriver

I used this driver to connect to a Progress database and everything worked out fine.



You need to make sure that the vendor has made the database enabled for SQL access this includes:

• setting up a secondary broker which accepts only SQL connections
• security (only access to certain users with certain priviliges)
• running dbtool on a regular basis
• running update statistics periodically.

Anyway, I can confirm that it is possible to use the linux driver on windows (as expected, since the drivers are type 4 and therefore all java).

It is hard to tell what actually goes wrong with you, but reading your story I think the part where your vendor needs to do stuff isn't done yet.

I hope this helps (so far).
Feel free to ask more questions.

Regards,

Casper.

 

[RhymeAndReason]

Casper,

Amazingly quick reply, thanks!

So I don't have to install else on the client besides the drivers - good. Glad to know the Linux drivers do in fact work.

I figured it was a configuration thing on the server side.

Hopefully I can get that side setup soon...