Defining the JDBC driver path

Defining the JDBC driver path is a necessary step if you want to configure horizontal clustering.

About this task

The following information applies to clustering with horizontal cluster members only.

Ensure that the JDBC provider is configured properly within your clustered environment. The JDBC provider software is included with the database client software that you installed on each node. Each WebSphere Commerce node that has servers that are part of the cluster must have the JDBC provider information defined. When WebSphere Commerce creates an instance, the JDBC provider information is defined at the node level. When you configure a cluster, each node that has a new cluster member must be configured to reference the appropriate JDBC provider. To define your JDBC provider information, complete the following steps:

Note: You are not required to complete these steps on the node where you originally installed WebSphere Commerce.


  1. Start the node agent on each system that is managed by WebSphere Application Server Network Deployment.
    LinuxAIXNote: Ensure that you start each node agent as the WebSphere Commerce non-root user.
  2. Start the Deployment Manager.
  3. Open the WebSphere Application Server Deployment Manager administrative console. For more information, see Launching the WebSphere Application Server Administrative Console.
  4. In the Navigation area, expand Environment and then select WebSphere Variables.
  5. Select Browse Nodes, and choose the node that you want to configure. You must configure all nodes that run WebSphere Commerce. Click OK.
  6. Click the link for the variable that represents your database type. The following values are the default values:
  7. In the Value field, enter the path to the appropriate JDBC provider. Do not enter the name of the .jar file in this field. This value needs the directory path only.
    For example,
    • DB2DB2_installdir/java
    • OracleOracle_installdir/jdbc/lib
  8. Click OK.
  9. Click Review to save your changes.
  10. Select Synchronize changes with Nodes to ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes.
  11. Click Save.
  12. Click OK.