Define the JDBC driver path

Defining the JDBC driver path is a required step when configuring horizontal clustering.

This section applies only to clustering with horizontal cluster members.

You must 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 have 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 a new instance this information is defined at the node level. When configuring 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:

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

  1. If they are not started, start the node agent on each system managed by WAS ND. Ensure that you start each node agent as the WebSphere Commerce non-root user.

  2. If it is not started, start the deployment manager. Refer to:

  3. Open the WAS Deployment Manager Administrative Console. For instructions, refer to Launching the WAS Administrative Console.

  4. In the Navigation area, expand Environment. 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 defaults are listed below:

    • (DB2) DB2_JDBC_DRIVER_PATH

    • (Oracle) ORACLE_JDBC_DRIVER_PATH

  7. I5/OS:

    If you are using the WC_OS400_TOOLBOX_JDBC_DRIVER_PATH value...

    1. Click New and enter WC_OS400_TOOLBOX_JDBC_DRIVER_PATH in the Name field.

      The Name field is case sensitive.

  8. 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 requires the directory path only. For example:

    • AIX|Linux|Solaris|Windows:

      (DB2) DB2_installdir/java

    • AIX|Solaris|(Oracle) Oracle_installdir/jdbc/lib

    • I5/OS|${APP_INSTALL_ROOT}/cell/WC_instance.ear/lib


    I5/OS: Do not replace the ${APP_INSTALL_ROOT} section of the path name. where:

    cell

    The name of the cell at the time the application was installed. This cell may change if you have uninstalled and reinstalled WebSphere Commerce multiple times.

    instance

    The name of your WebSphere Commerce instance.

    This path represents the path to your WebSphere Commerce EAR /lib directory. This path may not exist on your machine at this time. When the WAS Deployment Manager distributes the WebSphere Commerce application to this machine, the path will be created.

    If you are defining a JDBC provider for a node where one of your cluster members will reside, but where you have not installed WebSphere Commerce, this path will not exist on that machine.

  9. Click OK.

  10. Click Save in the Administrative Console taskbar.

  11. Click Review to save your changes.

  12. Select Synchronize changes with Nodes to ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes.

  13. Click Save.

  14. Click OK.

  15. Log out of the WAS Deployment Manager Administrative Console.

 

Related Concepts


WAS ND clustering mechanism
WebSphere Commerce federation

 

Related tasks


Cluster with vertical cluster members
Cluster with horizontal cluster members
Prepare additional nodes
Create the WebSphere Commerce cluster
Add additional cluster members
Start or stopping a WebSphere Commerce cluster
Remove a cluster member