Chapter 3. WebSphere - DB2 environment 57
In the right columns of the display a contextual explanation is given for all properties.
Click Apply again.
The new JDBC provider is now defined for this server, but the definition is not saved yet. It is
good practice to save the changes at this time (by clicking the Save button). After the save,
we return to the JDBC Provider list in which the new provider should be present now
Figure 3-8 JDBC new provider list
3.5.2 Defining Data Sources under this provider
Now that the new driver is available from the JDBC provider list, select the DB2 Universal
JDBC Driver Provider by clicking on the link (in blue).
On the bottom of the next window, under the provider characteristics, a frame called
Additional Properties (Figure 3-9) is presented. Within this frame we can define Data Sources
(V5 and V4).
Figure 3-9 Additional properties of the DB2 Universal JDBC Driver Provider
As we want to define a WAS V5 Data Source, select Data Sources. This takes us to the
window shown in Figure 3-10 on page 58.
58 DB2 for z/OS and WebSphere: The Perfect Couple
Figure 3-10 New Data Source
No Data Source has been defined at this point. Click New for a new Data Source.
In the next windows, Figure 3-11, Figure 3-12 on page 59, and Figure 3-13 on page 60, we
define the properties of the (new) Data Source. In the right column contextual information is
provided about the meaning of each of the properties.
Figure 3-11 General Properties 1
Some properties are marked as mandatory (with a red asterisk). We provide information for
the following fields:
Name (display) This is a label; specify a name that is as meaningful as
Chapter 3. WebSphere - DB2 environment 59
JNDIName By convention this should start with “jdbc/”; we should
use a name that expresses as close as possible the
addressed DB2 and driver type.
jdbc/T2DBD8 (DBD8 on Local via type2)
The JNDIName will have to be set in the Deployment
Descriptors of the Web Applications and EJBs, or if the
name defined in the descriptors is not a defined JNDI
name of a Data Source, it will have to be overridden in
the deployment dialog.
Container managed persistence Check this box if CMP EJBs will make use of this Data
Figure 3-12 General Properties 2
Statement Cache Size This parameter influences the performance
of JDBC. SQLJ has been prepared in
advance. JDBC statements that are used
repetitively are prepared the first time and
can been cached afterwards in prepared
Component-managed Authentication Alias This is the user ID/password that will be
used to access DB2 with component
managed security. The alias has to be
Container-managed Authentication Alias This is the user ID/password that will be
used to access DB2 with container managed
security. The alias has to be defined