How to set up WebSphere Application Server V5.0 to connect to DB2 for OS/390 using the Type 4 DB2 Universal JDBC Driver
 Technote (troubleshooting)
 
Problem(Abstract)
To set up WebSphere Application Server V5.0.2 or higher to connect to a DB2® for OS/390® database using the Type-4 DB2 Universal JDBC Driver, follow these instructions.
 
Resolving the problem
DB2 for OS/390:
On DB2 for OS/390 V7:
Please ensure that PTFs PQ72453 and PQ62695 are applied.

Run the DB2 Universal JDBC Driver binder utility DB2binder if it has not been run against the databases on OS/390.

Details about the DB2binder utility:
On DB2 UDB for UNIX and Windows version 8, prerequisite JDBC/CLI packages are preinstalled. On DB2 for OS/390 version 7, these packages must be bound manually to the server with the supplied DB2binder utility. The DB2binder utility is used to add the standard IBM JDBC packages to a target database URL. The latest version of the IBM JDBC packageset will be bound to the server.

The DB2binder utility is invoked from the command line as "java com.ibm.db2.jcc.DB2Binder" with arguments as described below.
java com.ibm.db2.jcc.DB2Binder -url jdbc:db2://<server_name>:<port_number>/<database_name> -user <username>  -password <password>

-url
Specifies the data source at which the JCC packages are to be bound. The variable parts of the -url value are:

server
The domain name or IP address of the MVS system on which the DB2 subsystem resides.
port
The TCP/IP server port number that is assigned to the DB2 subsystem. The default is 446.
database
The location name for the DB2 subsystem, as defined in the SYSIBM.LOCATIONS catalog table.

-user
Specifes the user ID under which the packages are to be bound. This 4 user must have BIND authority on the packages.

-size
Specifies the number of DB2 packages that DB2binder binds for each of the four DB2 isolation levels and each of the two holdability values. The DB2 Universal JDBC Driver uses these packages to process dynamic SQL. In addition, the DB2binder binds a single package that the DB2 Universal JDBC Driver uses for static SQL. Therefore, the total number of packages that DB2binder binds is:
4*2*integer+1
The default value for integer is 3.

-collection
Specifies the collection ID for the packages that are used by an instance of the DB2 Universal JDBC Driver. The default is NULLID. DB2binder translates this value to uppercase.
You can create multiple instances of the JCC package set at a single location by running com.ibm.db2.jcc.DB2Binder multiple times, and specifying a different value for -collection each time. At run time, you select a copy of the DB2 Universal JDBC Driver by setting the currentPackageSet property to a value that matches a -collection value. See Properties for the DB2 Universal JDBC Driver for information on the currentPackageSet property.

-tracelevel
Specifies what to trace while DB2binder runs. See the explanation of the traceLevel property in Properties for the DB2 Universal JDBC Driver for the options that are available.

Notes:
  • Only one version of the IBM JDBC packageset exists. So the current syntax does not allow for adding or dropping specific versions of the JDBC packageset.
  • If the latest version of the JDBC packageset is already bound to the server, then this operation is ignored, and the bind request will be rejected by the following DB2 target servers: DB2 for OS/390 version 7, DB2 UDB for UNIX and Windows version 8.
  • If the latest JDBC packageset is already bound to the server, the bind request will be accepted by a DB2 UDB for UNIX and Windows V7 server, but the pre-existing JDBC packageset of the same version will be replaced.

For WebSphere Application Server:

1. Start WebSphere and launch the Admin Console.

2. Create a new J2C Authentication Alias (Expand Security --> JAAS Configuration --> J2C Authentication Data) to specify the userid and password to be used to connect to the DB2 for OS/390 database.

3. Edit the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable (Expand Environment --> Manage WebSphere Variables) to specify the fully qualified path for the directory that contains the db2jcc.jar, db2jcc_license_cisuz.jar, and db2jcc_license_cu.jar files.

4. Create a new JDBC Provider (Expand Resources --> JDBC Providers, and click New). Select DB2 Universal JDBC Driver Provider from the drop-down list and accept the defaults on the next page.

5. Save the configuration and navigate back to the new JDBC Provider. Select the new JDBC Provider and then select Data Sources under Additional Properties. A new data source is created. Enter a Name, JNDI Name, Component-managed Authentication Alias, and Container-managed Authentication Alias. Select the check box for Container Managed Persistence if the data source is to be used for CMP entity beans. Click OK and then select Custom Properties under Additional Properties in the data source configuration. The following properties are required:

databaseName <OS/390 sub-system name, case sensitive>
enableSQLJ   true(default value)
portNumber   <specify the port number on OS/390, the default is 447>
serverName   <OS/390 machine name>

6. Save the configuration, and click the Test Connection button in the data source configuration to see if the data source is now set up successfully to connect to the DB2 for OS/390 database.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1139465
IBM Group: Software Group
Modified date: Dec 27, 2005