Setting up an IBM i database in a cluster | HCL Digital Experience
To communicate with a database, servers that run IBM i can use either of two JDBC drivers: the IBM Toolbox for Java JDBC driver or the IBM Developer Kit for Java JDBC driver (also referred to as the native JDBC driver). Which JDBC driver you must use depends on how you are setting up your clustered environment.
db2_iseries.DbDriver
property
in the wkplc_dbtype.properties file,
which is in thewp_profile_root/ConfigEngine/properties directory. You can specify the
value by editing the file manually or by selecting the appropriate
value by using the Configuration Wizard.- Native JDBC driver:
com.ibm.db2.jdbc.app.DB2Driver
- IBM Toolbox for Java JDBC driver:
com.ibm.as400.access.AS400JDBCDriver
Scaling topology considerations
Scaling topology | JDBC driver considerations |
---|---|
Vertical scaling | When you sett up a vertical cluster, you can install the
database locally on the same machine as your portal or remotely on
a separate machine. Use the appropriate JDBC driver, depending on
where the database is installed.
|
Horizontal scaling | When you set up a horizontal cluster, you must use the IBM Toolbox for Java JDBC driver. The typical configuration is to use a remote database for primary and secondary nodes in the cluster. If you choose, you can use a local database for the primary node and configure the secondary nodes to use that database, just as you would any other remote database. However, regardless of whether you choose to include a local database in your environment, you must use the IBM Toolbox for Java JDBC driver with your horizontal cluster. |
Using a local database in an IBM® i horizontal cluster
- wkplc_dbtype.properties
-
- Specify the JDBC driver in the
db2_iseries.DbDriver
property. For example:db2_iseries.DbDriver=com.ibm.as400.access.AS400JDBCDriver
- Specify the database location as remote in the
db2_iseries.DbDriverType
property. For example:db2_iseries.DbDriverType=4
- Specify the JDBC driver in the
- wkplc_dbdomain.properties
-
- Specify the primary node's host name for the
domain.DbName
properties. For example: release.DbName=primary_host_name/wpsdb - Specify the primary node's host name in the
domain.DbUrl
properties. For example: release.DbUrl=jdbc:as400:primary_host_name/wpsdb
- Specify the primary node's host name for the
Complete all other configuration as described. When you configure secondary nodes in this scenario, do your database configuration as you would for any remote database, by using the primary node's host name for the database transfer.