Installed applications use data sources as resources to
obtain connection to relational databases. To create these connections
between an application and a relational database, WebSphere® Application
Server uses the driver implementation classes that are encapsulated
by the JDBC provider, which is an object that represents vendor-specific
JDBC driver classes to WebSphere Application Server.
For access to a relational databases, applications use the JDBC drivers
and data sources that you configure for WebSphere Application
Server.
Procedure
- Start the WebSphere Application Server
administrative console.
- Click Security -> Global security.
- On the Configuration panel, under Authentication,
expand Java™ Authentication and Authorization Service
and click J2C authentication data.
- Click New and enter the Alias, User ID and Password.
- Click Ok.
- On the WebSphere Application Server
administrative console, expand Resources. Expand JDBC then
click JDBC Providers.
- In the Scope section, choose the Node level from
the drop-down list.
- Click New to create a new JDBC driver.
- Select, in this order, the Database type, Provider type,
Implementation type and Name.
The Name automatically fills
based on the implementation type you choose.
- Click Next and configure the database class path.
Click Next.
- On the Summary page, click Finish.
- Click Save to save your selections.
The
JDBC providers page then appears.
- On the WebSphere Application Server
administrative console, click Data sources.
- Click New to create a new data source.
Enter
the Data source name and the JNDI name, and choose the authentication
alias from the drop-down list in Component-managed authentication
alias. The JNDI name should match the datasourceName value set in
wimconfig.xml.
By default, it is
jdbc/wimDS.
Note: For Apache Derby v10.2
embedded databases, leave the Component-managed authentication alias
field set to NONE.
- Click Next.
- Enter the Database name and deselect the checkbox, Use
this data source in container managed persistence (CMP). Click Next.
- On the Summary page, click Finish.
- The Data sources page displays. Click Save, and
then select the check box for the authentication alias previously
created. Click Test Connection.
The message should
indicate that the connection is successful. Ignore any warnings, and
then click Next.
-
Set the following custom property on the newly created data source:
webSphereDefaultIsolationLevel = 2
- Click .
- In the Scope section, select Cell from
the drop-down list.
- Click New to create a variable.
- In the Name field, enter VMM_JDBC_CLASSPATH.
- In the Value field, enter the complete
path to the JDBC driver library files separated by a colon (:)
for UNIX or Linux or a semicolon (;) for Windows.
For example, the path to Linux or UNIX is as follows: /opt/IBM/SQLLIB/java/db2jcc.jar:/opt/IBM/SQLLIB/java/db2jcc_license_cu.jar.
- Click OK. Additionally, copy the
specified JDBC driver library files in the ${WAS_HOME}/lib directory
of each installed WebSphere Application Server node.
- Save the configurations, and restart WebSphere Application
Server.
Note: In a clustered environment, you must also
stop and restart the Deployment manager and the node agents.