SEO

#1 (**permalink**) 02-27-2008, 02:47 AM

Hello, everyone.

Our developers are wondering if their swing Java-based application
connecting to a DB2 server through JDBC requires the DB2 client access
license (CAL) per user.
They've got the Java app installed on PCs connecting a DB2 server.

They believe that the above scenario does not requires DB2 CALs.

I think as long as an application connects to a DB2 server requires a
DB2 CAL whethere it is a ODBC or JDBC connection.
Furthermore, there are also web-based connections to the DB2 via Tomcat
from the same PCs where the swing-based apps are.
Is my belief wrong?
Can some licensing experts give their opinions please?

Thanks.

#2 (**permalink**) 02-27-2008, 02:47 AM

"DB2" <pineme@yahoo.com> wrote in message
news:1107217217.279068.33010@c13g2000cwb.googlegro ups.com...
> Hello, everyone.
>
> Our developers are wondering if their swing Java-based application
> connecting to a DB2 server through JDBC requires the DB2 client access
> license (CAL) per user.
> They've got the Java app installed on PCs connecting a DB2 server.
>
> They believe that the above scenario does not requires DB2 CALs.
>
> I think as long as an application connects to a DB2 server requires a
> DB2 CAL whethere it is a ODBC or JDBC connection.
> Furthermore, there are also web-based connections to the DB2 via Tomcat
> from the same PCs where the swing-based apps are.
> Is my belief wrong?
> Can some licensing experts give their opinions please?
>
> Thanks.
>
If you are connecting to DB2 server on Linux, UNIX, or Windows, you do not
need any license. You can connect directly without a client with a type 2
driver (and some 3rd party drivers).

If you are connecting to DB2 on mainframe or AS/400 you need a license for
DB2 Connect.

Please mention your OS and DB2 release of your DB server in future posts.

#3 (**permalink**) 02-27-2008, 02:47 AM

Thanks for your quick reply.
The OS platform will be strictly Windows-based.
New deployments will be using DB2 v 8.x. There might be some existing
DB2 v.7.x

So why a ODBC connection requires a CAL while a JDBC does not?

Thanks.

#4 (**permalink**) 02-27-2008, 02:47 AM

"DB2" <pineme@yahoo.com> wrote in message
news:1107218675.649835.131800@c13g2000cwb.googlegr oups.com...
> Thanks for your quick reply.
> The OS platform will be strictly Windows-based.
> New deployments will be using DB2 v 8.x. There might be some existing
> DB2 v.7.x
>
> So why a ODBC connection requires a CAL while a JDBC does not?
>
> Thanks.
>
I don't know what a CAL is (my ignorance). DB2 clients are free. The type 2
driver is just another type of DB2 client.

#5 (**permalink**) 02-27-2008, 02:47 AM

To clarify, you can use ODBC, JDBC, JDBC type-4 if you wish to access
DB2 on Linux, UNIX, Windows. There are, however, two different types of
server licenses: Enterprise Standard Edition and Workgroup Edition. ESE
is licensed on a processor basis ... and processors on that server must
be licensed for ESE ... no matter how many client connections you have.
WE is different, however, as it has a per-user license option. If you
have that option, then you must license each DB2 client connection that
comes into that server.

Hope this helps.

Larry Edelstein

DB2 wrote:
> Thanks for your quick reply.
> The OS platform will be strictly Windows-based.
> New deployments will be using DB2 v 8.x. There might be some existing
> DB2 v.7.x
>
> So why a ODBC connection requires a CAL while a JDBC does not?
>
> Thanks.
>

#6 (**permalink**) 02-27-2008, 02:47 AM

"Larry" <larry@nospam.net> wrote in message
news:PtBLd.58638$n06.14978@fe09.lga...
> To clarify, you can use ODBC, JDBC, JDBC type-4 if you wish to access
> DB2 on Linux, UNIX, Windows. There are, however, two different types of
> server licenses: Enterprise Standard Edition and Workgroup Edition. ESE
> is licensed on a processor basis ... and processors on that server must
> be licensed for ESE ... no matter how many client connections you have.
> WE is different, however, as it has a per-user license option. If you
> have that option, then you must license each DB2 client connection that
> comes into that server.
>
> Hope this helps.
>
> Larry Edelstein
>
But you can use connection pooling to limit the number of simultaneous
connections, without worrying about how many clients think they are
connected.

Right?

#7 (**permalink**) 02-27-2008, 02:47 AM

Mark,

I think you must still license the # of clients that connect into the
db. If you have 100 clients and pool them into 50 connections, you pay
for 100 clients.

Larry Edelstein

Mark A wrote:

> "Larry" <larry@nospam.net> wrote in message
> news:PtBLd.58638$n06.14978@fe09.lga...
>
>>To clarify, you can use ODBC, JDBC, JDBC type-4 if you wish to access
>>DB2 on Linux, UNIX, Windows. There are, however, two different types of
>>server licenses: Enterprise Standard Edition and Workgroup Edition. ESE
>>is licensed on a processor basis ... and processors on that server must
>>be licensed for ESE ... no matter how many client connections you have.
>>WE is different, however, as it has a per-user license option. If you
>>have that option, then you must license each DB2 client connection that
>>comes into that server.
>>
>>Hope this helps.
>>
>>Larry Edelstein
>>
>
> But you can use connection pooling to limit the number of simultaneous
> connections, without worrying about how many clients think they are
> connected.
>
> Right?
>
>

#8 (**permalink**) 02-27-2008, 02:47 AM

"Larry" <larry@nospam.net> wrote in message
news:ZwDLd.58647$jr7.22675@fe09.lga...
> Mark,
>
> I think you must still license the # of clients that connect into the
> db. If you have 100 clients and pool them into 50 connections, you pay
> for 100 clients.
>
> Larry Edelstein
>
Hmmm. I may have to bet you an Anthony's Pizza on that one.

#9 (**permalink**) 02-27-2008, 02:47 AM

There is also a Workgroup Edition unlimited users version. If you have more than about 20 users this is the way to go. It is a per processor license with a maximum number of processors.(4 I think)

Jeff

>>> Mark A<nobody@nowhere.com> 01/02/2005 12:35:23 am >>>
"Larry" <larry@nospam.net> wrote in message
news:ZwDLd.58647$jr7.22675@fe09.lga...
> Mark,
>
> I think you must still license the # of clients that connect into the
> db. If you have 100 clients and pool them into 50 connections, you pay
> for 100 clients.
>
> Larry Edelstein
>
Hmmm. I may have to bet you an Anthony's Pizza on that one.

#10 (**permalink**) 02-27-2008, 02:48 AM

Thank you everyone.

I really appreciate everyone's input.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

DB2 Client Access Licensing Question