WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Configuring a JDBC provider for a clustered environment

Use these steps to define a data source on multiple nodes that comprise a cluster.

Before you begin

Be aware that all members of your cluster must run at least Version 6.0 of WebSphere Application Server to use a cluster-scoped JDBC provider. See Administrative console scope settings for more information about scope settings in general.

About this task

The cluster scope has precedence over the node and cell scopes. Create a JDBC provider for a cluster if you want the associated data source to:

Procedure

  1. Open the administrative console.
  2. Click Resources > JDBC Providers. In the Scope section, note that the default scope setting is at the node level.
  3. Click Browse Clusters. The JDBC providers > Select a Cluster Scope panel is displayed.
  4. Select the cluster for which you want to define a data source, and click OK. The JDBC providers panel is displayed again.
  5. Click Apply.
  6. Click New to create a new JDBC provider at the cluster level. The class path for your new JDBC provider is already filled in; part of that class path is specified using a symbolic variable, for example: ${DB2390_JDBC_DRIVER_PATH}/classes/db2j2classes.zip . Leave it at the default.
  7. Finish creating the JDBC provider.
  8. Click Environment > WebSphere Variables in the administrative console.
  9. For each node in the cluster, select the symbolic variable used in the class path of your JDBC provider, and provide a value that is appropriate for the selected node. For example, if the class path of your JDBC provider uses the symbolic variable ${DB2390_JDBC_DRIVER_PATH}, you might supply the value /usr/lpp/db2 on one node and /usr/lpp/db2710 on another node, depending on where your DB2 390 installation is located.
  10. Click DB2_JDBC_DRIVER_PATH (this already exists by default). Here provide the path (in the value field) where db2java.zip exists on the selected node.
  11. Click Apply and save the changes.
    Note: This variable must be defined on each node within the cluster.

What to do next

You are now ready to configure your data source. For guidance, refer to Configuring a data source using the administrative console .
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tdat_mcrtpds.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)