IBM G210-1784-00 manual Defining the JDBC data sources, Create the J2C Authentication Data Entries

Defining the JDBC provider for a SQL Server database

1.Install SQL Server 2000 Driver for JDBC Service Pack 2 on the WAS node(s) that will host the LMM and DS. If you don't have the MSSQL jars, you can get them from the Microsoft site.

The URL for the SP2 drivers is:

http://www.microsoft.com/downloads/details.aspx?FamilyID=9f1874b6-f8e1-4bd6- 947c-0fc5bf05bf71&DisplayLang=en

2.Access the WAS Admin Console.

3.Navigate to Environment --> Manage WebSphere Variables and set the

MSSQLSERVER_JDBC_DRIVER_PATH variable to the lib directory under the path to which you installed the JDBC drivers.

This is the directory that contains the .jar files of the JDBC driver:

msbase.jar

mssqlserver.jar

msutil.jar

spy.jar ("spy.jar" may be in a different location from the rest of them)

4.Navigate to Resources-->JDBC Providers.

5.Click New and select Microsoft JDBC Driver for MSSQL Server 2000. Do not select the XA version of the driver.

Defining the JDBC data sources

The next step is to define the JDBC data sources. Access to JDBC connections is made via JNDI lookup of a named data source. These data sources have well-known names that are embedded in the Learning Management System

.ear file. Using the WAS admin console, three data sources must be configured: LMM (Default), LSAUDIT (Audit), and DS (Delivery). The following steps provide the instructions for completing these tasks. This section describes the procedure to create data sources and configure DB connections.

Create the J2C Authentication Data Entries

1.Expand Security on the left panel of the WAS console.

2.Expand JAAS Configuration.

3.Click J2C Authentication Data.

4.Click New.

5.Enter your data base information. For example:

•Alias: db_name - This identifier is used to identify the authenticated data entry. When configuring resource adapters or JDBC data sources, the administrator can specify which authentication data to choose for the corresponding alias.

•User ID: your_id - This is the user identity of the intended security domain. For example, if a particular authentication data entry is intended to be used to open a new connection to DB2, this entry would contain a DB2 user identity.

•Password: your_password - This password of the user identity is encoded in the configuration respository.

6.Click Apply. This creates an entry like hostnameManager/db_name.

7.Repeat for the other two databases.

Chapter 11: Configuring JDBC Data Sources 57