By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,496 Members | 1,489 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,496 IT Pros & Developers. It's quick & easy.

Oracle Net VS DB2 Connect

P: n/a
Hello,
Is it right to tell that DB2 Connect has the same function that Oracle
Net ?
If I have an ODBC application is it also right to tell that I have 2
possibilities on my client workstation to acces a remote UDB database
on a Sun machine :
a) with a run-time client
b) with DB2 Connect Personnal Edition

Thank you
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Kona" <ko*******@yahoo.fr> wrote in message
news:a1**************************@posting.google.c om...
Hello,
Is it right to tell that DB2 Connect has the same function that Oracle
Net ?
If I have an ODBC application is it also right to tell that I have 2
possibilities on my client workstation to acces a remote UDB database
on a Sun machine :
a) with a run-time client
b) with DB2 Connect Personnal Edition

Thank you


You need DB2 connect to remotely access DB2 on the mainframe, but you don't
need it for DB2 on Unix. The run-time client is free, and DB2 Connect is not
free.

But if you want to set up a gateway machine, so that all clients go through
the gateway instead of directly connecting to the DB2 server, then DB2
Connect does provide that on functionality.
Nov 12 '05 #2

P: n/a
Kona wrote:
Hello,
Is it right to tell that DB2 Connect has the same function that Oracle
Net ?
If I have an ODBC application is it also right to tell that I have 2
possibilities on my client workstation to acces a remote UDB database
on a Sun machine :
a) with a run-time client
b) with DB2 Connect Personnal Edition

Thank you


1. I don't know what functions Oracle.Net has - therefore I am unable to
comment on this. DB2 Connect enables customers to connect to DRDA host
(DB2 VSE/VM, DB2/400, DB2/xOS) - ither from local workstation only (DB2
Connect PE) - or acting as Gateway server (DB2 Connect EE).

2. Any of DB2 products have RunTime clients; therefore you have several
posibilities on the requester workstation:

DB2 Run-Time Client
DB2 Development Client
DB2 Administration Client
DB2 Personal Edition (on Windows and Linux)
DB2 Workgroup Server Edition
DB2 Enterprise Server Edition
DB2 Connect Personal Edition (on Windows and Linux)
DB2 Connect Enterprize Edition

depending on additional capabilities you may want to use/explore.

Jan M. Nelken
Nov 12 '05 #3

P: n/a
Thank you for your informations.
But if you want to set up a gateway machine, so that all clients go throughthe gateway instead of directly connecting to the DB2 server, then DB2Connect does provide that on functionality


If we setup a gateway machine for the clients, is it also possible to
access my UDB database on my Sun machine directly ?
I ask you that because we would like to enable the access to the UBD
only from authorized clients. We would like to prevent UDB access from
unauthorized clients workstations that have setup an ODBC and access
the DB using a foreign tool like MS Query.

Thank in advance (a db2connect newbie)
Nov 12 '05 #4

P: n/a
Kona wrote:

If we setup a gateway machine for the clients, is it also possible to
access my UDB database on my Sun machine directly ?
I ask you that because we would like to enable the access to the UBD
only from authorized clients. We would like to prevent UDB access from
unauthorized clients workstations that have setup an ODBC and access
the DB using a foreign tool like MS Query.


You most likely would like to control access (by GRANTing CONNECT
priviledge to users or group) at UDB server.
There is nothing like "authorised" versus "unauthorised" workstation in
native UDB. Remember that for ODBC access you have to have as a minimum
the DB2 UDB Run-Time client installed on the workstation.

so the matrix looks like:
RT Client -------------------------------------------> UDB Server
(or other clients)

or

RT Client -----------> DB2 Connect Gateway ------------> DRDA HOST
(or other clients)

or

DB2 Connect Personal Edition --------------------------> DRDA HOST

There are several other possibilities as well (Federated Database
Support) to consider - so perhaps reviewing DB2 Books may help you a bit
more.

As a rule - DB2 Connect is used when ultimate destination is DRDA Host
(DB2 for VSE/VM, DB2/400 or DB2/zOS).
Jan M. Nelken
Nov 12 '05 #5

P: n/a
"Jan M. Nelken" <Un**********@Invalid.Domain> wrote in message news:<40********@news1.prserv.net>...
Kona wrote:

If we setup a gateway machine for the clients, is it also possible to
access my UDB database on my Sun machine directly ?
I ask you that because we would like to enable the access to the UBD
only from authorized clients. We would like to prevent UDB access from
unauthorized clients workstations that have setup an ODBC and access
the DB using a foreign tool like MS Query.
You most likely would like to control access (by GRANTing CONNECT
priviledge to users or group) at UDB server.
There is nothing like "authorised" versus "unauthorised" workstation in
native UDB. Remember that for ODBC access you have to have as a minimum
the DB2 UDB Run-Time client installed on the workstation.

so the matrix looks like:
RT Client -------------------------------------------> UDB Server
(or other clients)

or

RT Client -----------> DB2 Connect Gateway ------------> DRDA HOST
(or other clients)

or

DB2 Connect Personal Edition --------------------------> DRDA HOST

There are several other possibilities as well (Federated Database
Support) to consider - so perhaps reviewing DB2 Books may help you a bit
more.

As a rule - DB2 Connect is used when ultimate destination is DRDA Host
(DB2 for VSE/VM, DB2/400 or DB2/zOS).
Jan M. Nelken


Hello Jan,
Remember that for ODBC access you have to have as a minimum
the DB2 UDB Run-Time client installed on the workstation.


Case 1 : normal user on agreed workstation

Application
-------------------
IBM DB2 ODBC DRIVER
-------------------
Run-Time DB2 ----------DB2 Gateway------------- UDB Unix
server
-------------------
All security rules are set by the application.
Case 3 : normal user on agreed workstation

Application / MSQUERY
-------------------
IBM DB2 ODBC DRIVER
-------------------
Run-Time DB2 ----------DB2 Gateway------------- UDB Unix
server
-------------------

In this case the user could use MSQUERY to by-pass security rules set
by the Application.

Case 4 : Hacker

MSQUERY
-------------------
IBM DB2 ODBC DRIVER
-------------------
Run-Time DB2 --------------------------------- UDB Unix
server
-------------------

We suppose that the hacker knowns all informations like
username/pasword and DSN configuration.
But he access the UDB directly, no DB2 Gateway.
In this case is it possible to tell that the UDB server only accept
connexions from DB2 Gateway ?
I thing that SSL is not supported by DB2connect, an other way ?

Thank you
Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.