Use of net driver in java application - V7.2 -> V8.1 
Author Message
 Use of net driver in java application - V7.2 -> V8.1

Hi,

We have just been trying to change a java program to use the net
driver rather than the app driver, and this has raised some questions.

Scenario:
V7.2 Client -> V8.1 Server

if we change the java code to use the client's V7.2 net driver we
get an error - CLI0621
CLI0621E Unsupported JDBC Server configuration.

Explanation:

The target JDBC Server configuration is not supported.  If you
are running the Control Center, the target JDBC Server must be a
standalone db2jd process (started via db2jstrt) and not a 2-tier
native JDBC Server.

User Response:

Reconfigure the JDBC Server using db2jstrt on the port targeted
by the Control Center.

If we copy the java .zip files from the server(V8.1) to the client,
and put them in the CLASSPATH instead of the V7.2 ones, it works fine.

So this has raised the following questions?

1. Is V7.2 net driver to V8.1 supported?
   - we notice net driver os depracated in V8.1?

2. Is there a way to have the Java Application 'load' the net driver
from
the server on the fly, i.e like it is down for an applet running on a
client
without a DB2 client at all?

3. If we upgraded the client to V8.1, and used the type4 driver, would
we
need to catalog the databases on the client?  

The reason we were trying this in the first place was that we didn't
want to have to have db catalog info on the client for this particular
application.

Thanks.

Paul.



Sun, 17 Jul 2005 22:15:53 GMT
 Use of net driver in java application - V7.2 -> V8.1

   Hi, Paul.

   Yes, V7-to-V8 is a supported configuration, though I believe there may be
some exceptions which are not java-specific.

   No, I don't believe there is a way to load the driver from the server on
the fly.  To eliminate the need for installing the DB2 Client code, you
would need a Type 4 JDBC driver (the ".net" driver is a Type 3 driver, which
means it needs the DB2 Client layer on the client system).

   Yes, I believe you can use the JCC Type 4 JDBC driver, which as an added
benefit means you would not need to install the DB2 Client on the client
system... just the JDBC driver.
--
Larry Menard
IBM Workstation Database (DB2) Performance Team
Defender of Geese and of All Things Natural


Quote:
> Hi,

> We have just been trying to change a java program to use the net
> driver rather than the app driver, and this has raised some questions.

> Scenario:
> V7.2 Client -> V8.1 Server

> if we change the java code to use the client's V7.2 net driver we
> get an error - CLI0621
> CLI0621E Unsupported JDBC Server configuration.

> Explanation:

> The target JDBC Server configuration is not supported.  If you
> are running the Control Center, the target JDBC Server must be a
> standalone db2jd process (started via db2jstrt) and not a 2-tier
> native JDBC Server.

> User Response:

> Reconfigure the JDBC Server using db2jstrt on the port targeted
> by the Control Center.

> If we copy the java .zip files from the server(V8.1) to the client,
> and put them in the CLASSPATH instead of the V7.2 ones, it works fine.

> So this has raised the following questions?

> 1. Is V7.2 net driver to V8.1 supported?
>    - we notice net driver os depracated in V8.1?

> 2. Is there a way to have the Java Application 'load' the net driver
> from
> the server on the fly, i.e like it is down for an applet running on a
> client
> without a DB2 client at all?

> 3. If we upgraded the client to V8.1, and used the type4 driver, would
> we
> need to catalog the databases on the client?

> The reason we were trying this in the first place was that we didn't
> want to have to have db catalog info on the client for this particular
> application.

> Thanks.

> Paul.



Sun, 17 Jul 2005 22:59:31 GMT
 Use of net driver in java application - V7.2 -> V8.1
You might check these links regarding JDBC Type 4:

http://www-3.ibm.com/software/data/db2/udb/ad/v8/java/
http://www-3.ibm.com/software/data/db2/udb/ad/v8/client/db2a1426.htm
http://www7b.software.ibm.com/dmdd/library/techarticle/0209hutchison/...

You don't need to catalog the database if you use the
Type 4 driver. Hostname and port have to be specified
during the getConnection() method.
However the JDBC Type 4 driver will not work against
DB2 V7.x or V6.x on unix/linux/windows and is missing
some essential features like connection pooling and
distributed transactions.

Just one more area where IBM tries to catch up
with the wonderful Informix world....

Best regards

Eric
--
IT-Consulting Herber
WWW:   http://www.herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************

Quote:

> Hi,

> We have just been trying to change a java program to use the net
> driver rather than the app driver, and this has raised some questions.

> Scenario:
> V7.2 Client -> V8.1 Server

> if we change the java code to use the client's V7.2 net driver we
> get an error - CLI0621
> CLI0621E Unsupported JDBC Server configuration.

> Explanation:

> The target JDBC Server configuration is not supported.  If you
> are running the Control Center, the target JDBC Server must be a
> standalone db2jd process (started via db2jstrt) and not a 2-tier
> native JDBC Server.

> User Response:

> Reconfigure the JDBC Server using db2jstrt on the port targeted
> by the Control Center.

> If we copy the java .zip files from the server(V8.1) to the client,
> and put them in the CLASSPATH instead of the V7.2 ones, it works fine.

> So this has raised the following questions?

> 1. Is V7.2 net driver to V8.1 supported?
>    - we notice net driver os depracated in V8.1?

> 2. Is there a way to have the Java Application 'load' the net driver
> from
> the server on the fly, i.e like it is down for an applet running on a
> client
> without a DB2 client at all?

> 3. If we upgraded the client to V8.1, and used the type4 driver, would
> we
> need to catalog the databases on the client?  

> The reason we were trying this in the first place was that we didn't
> want to have to have db catalog info on the client for this particular
> application.

> Thanks.

> Paul.



Sun, 17 Jul 2005 22:29:18 GMT
 Use of net driver in java application - V7.2 -> V8.1
The .net driver should normally not need the DB2 Client layer on
the client system, otherwise it would not be a Type 3 driver.

AFAIK the .net driver needs the DB2 Client layer on the machine
where the db2jd listener is running.

Best regards

Eric
--
IT-Consulting Herber
WWW:   http://www.herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************

Quote:

>    Hi, Paul.

>    Yes, V7-to-V8 is a supported configuration, though I believe there may be
> some exceptions which are not java-specific.

>    No, I don't believe there is a way to load the driver from the server on
> the fly.  To eliminate the need for installing the DB2 Client code, you
> would need a Type 4 JDBC driver (the ".net" driver is a Type 3 driver, which
> means it needs the DB2 Client layer on the client system).

>    Yes, I believe you can use the JCC Type 4 JDBC driver, which as an added
> benefit means you would not need to install the DB2 Client on the client
> system... just the JDBC driver.
> --
> Larry Menard
> IBM Workstation Database (DB2) Performance Team
> Defender of Geese and of All Things Natural



>>Hi,

>>We have just been trying to change a java program to use the net
>>driver rather than the app driver, and this has raised some questions.

>>Scenario:
>>V7.2 Client -> V8.1 Server

>>if we change the java code to use the client's V7.2 net driver we
>>get an error - CLI0621
>>CLI0621E Unsupported JDBC Server configuration.

>>Explanation:

>>The target JDBC Server configuration is not supported.  If you
>>are running the Control Center, the target JDBC Server must be a
>>standalone db2jd process (started via db2jstrt) and not a 2-tier
>>native JDBC Server.

>>User Response:

>>Reconfigure the JDBC Server using db2jstrt on the port targeted
>>by the Control Center.

>>If we copy the java .zip files from the server(V8.1) to the client,
>>and put them in the CLASSPATH instead of the V7.2 ones, it works fine.

>>So this has raised the following questions?

>>1. Is V7.2 net driver to V8.1 supported?
>>   - we notice net driver os depracated in V8.1?

>>2. Is there a way to have the Java Application 'load' the net driver
>>from
>>the server on the fly, i.e like it is down for an applet running on a
>>client
>>without a DB2 client at all?

>>3. If we upgraded the client to V8.1, and used the type4 driver, would
>>we
>>need to catalog the databases on the client?

>>The reason we were trying this in the first place was that we didn't
>>want to have to have db catalog info on the client for this particular
>>application.

>>Thanks.

>>Paul.



Sun, 17 Jul 2005 22:36:12 GMT
 Use of net driver in java application - V7.2 -> V8.1
   Eric corrected me... Type 3 drivers do NOT need the DB2 Client installed
on the client either.  My bad.  Thanks, Eric.

--
Larry Menard
IBM Workstation Database (DB2) Performance Team
Defender of Geese and of All Things Natural


Quote:
>    Hi, Paul.

>    Yes, V7-to-V8 is a supported configuration, though I believe there may
be
> some exceptions which are not java-specific.

>    No, I don't believe there is a way to load the driver from the server
on
> the fly.  To eliminate the need for installing the DB2 Client code, you
> would need a Type 4 JDBC driver (the ".net" driver is a Type 3 driver,
which
> means it needs the DB2 Client layer on the client system).

>    Yes, I believe you can use the JCC Type 4 JDBC driver, which as an
added
> benefit means you would not need to install the DB2 Client on the client
> system... just the JDBC driver.
> --
> Larry Menard
> IBM Workstation Database (DB2) Performance Team
> Defender of Geese and of All Things Natural



> > Hi,

> > We have just been trying to change a java program to use the net
> > driver rather than the app driver, and this has raised some questions.

> > Scenario:
> > V7.2 Client -> V8.1 Server

> > if we change the java code to use the client's V7.2 net driver we
> > get an error - CLI0621
> > CLI0621E Unsupported JDBC Server configuration.

> > Explanation:

> > The target JDBC Server configuration is not supported.  If you
> > are running the Control Center, the target JDBC Server must be a
> > standalone db2jd process (started via db2jstrt) and not a 2-tier
> > native JDBC Server.

> > User Response:

> > Reconfigure the JDBC Server using db2jstrt on the port targeted
> > by the Control Center.

> > If we copy the java .zip files from the server(V8.1) to the client,
> > and put them in the CLASSPATH instead of the V7.2 ones, it works fine.

> > So this has raised the following questions?

> > 1. Is V7.2 net driver to V8.1 supported?
> >    - we notice net driver os depracated in V8.1?

> > 2. Is there a way to have the Java Application 'load' the net driver
> > from
> > the server on the fly, i.e like it is down for an applet running on a
> > client
> > without a DB2 client at all?

> > 3. If we upgraded the client to V8.1, and used the type4 driver, would
> > we
> > need to catalog the databases on the client?

> > The reason we were trying this in the first place was that we didn't
> > want to have to have db catalog info on the client for this particular
> > application.

> > Thanks.

> > Paul.



Sun, 17 Jul 2005 23:46:26 GMT
 Use of net driver in java application - V7.2 -> V8.1

Quote:

> You might check these links regarding JDBC Type 4:
> http://www-3.ibm.com/software/data/db2/udb/ad/v8/java/
> http://www-3.ibm.com/software/data/db2/udb/ad/v8/client/db2a1426.htm
> http://www7b.software.ibm.com/dmdd/library/techarticle/0209hutchison/...
...snip...
> Just one more area where IBM tries to catch up
> with the wonderful Informix world....

Its funny you mention this.  A colleague and I were discussing the
differences between DB2 JDBC and Informix JDBC yesterday.  I have
used Informix since Online v5 up to v9.21, and am now going DB2.

We have been using the Informix JDBC driver, which simply
connects directly to the sqlexec port (1527?) on the informix
server, and requires no client s/w.  I guess that makes it type 3.
Or is it type 4?  
That driver apparently speaks the native informix wire protocol,
connecting to the same port that an ESQL or other CLI app would
connect to.  Informix doesn't care what makes the connection.

But now we are implementing a DB2 database.  The DB2 JDBC type 2
driver requires a client layer at the client.  It gives you a faster
connection, but its a pain to install the client s/w everywhere.
The DB2 JDBC type 3 driver does not require client s/w, but does
require that the DB2 instance you are talking to has a db2jd daemon
process running.   This daemon process listens on a port other than
the main connection port (6789?), and I guess translates what it
gets into DB2 wire protocol and redirects it to the connection port
(50000?).

Question:  why can't the DB2 type 3 driver talk directly to the
DB2 connection port?   Why is a daemon required?

I think an informix JDBC URL *always* references the host and port
to connect to, while a DB2 JDBC URL might or might not reference
these things, depending on whether the remote database has been
cataloged with the local client s/w.  Informix has no such
cataloging process.  Why such different approaches?  

Why do you consider the Informix approach better? (not looking for
a fight - just curious)

Cheers

Allen



Mon, 18 Jul 2005 03:47:05 GMT
 Use of net driver in java application - V7.2 -> V8.1

Quote:


>>You might check these links regarding JDBC Type 4:
>>http://www-3.ibm.com/software/data/db2/udb/ad/v8/java/
>>http://www-3.ibm.com/software/data/db2/udb/ad/v8/client/db2a1426.htm
>>http://www7b.software.ibm.com/dmdd/library/techarticle/0209hutchison/...

> ...snip...

>>Just one more area where IBM tries to catch up
>>with the wonderful Informix world....

> Its funny you mention this.  A colleague and I were discussing the
> differences between DB2 JDBC and Informix JDBC yesterday.  I have
> used Informix since Online v5 up to v9.21, and am now going DB2.

> We have been using the Informix JDBC driver, which simply
> connects directly to the sqlexec port (1527?) on the informix
> server, and requires no client s/w.  I guess that makes it type 3.
> Or is it type 4?  
> That driver apparently speaks the native informix wire protocol,
> connecting to the same port that an ESQL or other CLI app would
> connect to.  Informix doesn't care what makes the connection.

> But now we are implementing a DB2 database.  The DB2 JDBC type 2
> driver requires a client layer at the client.  It gives you a faster
> connection, but its a pain to install the client s/w everywhere.
> The DB2 JDBC type 3 driver does not require client s/w, but does
> require that the DB2 instance you are talking to has a db2jd daemon
> process running.   This daemon process listens on a port other than
> the main connection port (6789?), and I guess translates what it
> gets into DB2 wire protocol and redirects it to the connection port
> (50000?).

> Question:  why can't the DB2 type 3 driver talk directly to the
> DB2 connection port?   Why is a daemon required?

> I think an informix JDBC URL *always* references the host and port
> to connect to, while a DB2 JDBC URL might or might not reference
> these things, depending on whether the remote database has been
> cataloged with the local client s/w.  Informix has no such
> cataloging process.  Why such different approaches?  

> Why do you consider the Informix approach better? (not looking for
> a fight - just curious)

> Cheers

> Allen

The Informix JDBC Driver is Type 4 not 3. Informix has been bought by
IBM in 2001, so this might the reason for the different approaches
taken.

Anyway, if you don't use JDBC, you have also to catalog the remote
node in Informix (adding an entry to your sqlhosts file). So this
is not that different from DB2.

The new JDBC Type 4 Driver for DB2 allows also a direct connection
without any prior catalog steps to do and you don't need to install
the DB2 Runtime Client.
I think it is quite curious that a company like IBM, which recommends
Java technology, did not have a JDBC Type 4 driver until yet.

There are many things that IBM could learn from Informix technology,
like the wonderful fragmentation possibilities, the sysmaster-interface,
the powerful onstat-commands, the scalable thread-based architecture,
the alter-table-in-place feature, the easy migrations and REVERSIONS
from one version to another (without having to restore a previous taken
archive), a high performance loader and UNLOADER, ease of setup and
configuration, dynamic logical logs (on raw devices !!), dynamic locks
(without lock escalation !!), how to take an
online-backup without logretention logging enabled, stored procedures
that need no c-compiler, a powerful and performant replication
technology, a hot-standby-server (without copying logs via userexit or
such worse things),.......

Ok, enough said, I'm quite confident that IBM has recognized the power
of the Informix technology and will transfer those features that make
sense to DB2.

Best regards

Eric
--
IT-Consulting Herber
WWW:   http://www.herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************



Mon, 18 Jul 2005 03:26:35 GMT
 
 [ 7 post ] 

 Relevant Pages 

1. after upgrade v7->v8, CREATE FUNCTION fails on 2 of 3 databases, same server

2. Oracle v7.3 Application with Oracle v8 Client and Server

3. real memory v7 -> v8

4. Oracle v7.3 Application with Oracle v8 Client and Server

5. db2 v8 ADO driver on db2 v7.2 servers

6. migrationpath from v7 -> v8

7. 32Bit ODBC Drivers for Progress V7 and V8

8. US-MA-Progress v7 GUI->v8-WSI

9. Migrating from v7.3.4 to v8.0 or v8.1 series

10. Migrating from v7.3.4 to v8.0 or v8.1 series

11. >>> TECH FORCE Toronto Progress V7 and V8 Positions...>>>

12. >>> TECH FORCE Toronto Progress V7 and V8 Positions...>>>


 
Powered by phpBB® Forum Software