Release Notes
Abstract
There are new features introduced in Db2Connect 12.1 release.
Below are the new features users needs to consider before the driver upgrade.
Content
JCC license requirement
From Db2 Connect 12.1, to connect to Db2 for z/OS and Db2 for i server, JCC customers will need to download the new JCC license activation kit for 12.1 from PPA (Passport Advantage). This is needed only while moving from one major version of Db2 Connect to another major ver-sion of Db2 Connect (Example: from 11.5 to 12.1). There is no need to download the JCC license activation kit if customer moves from one modpack/fixpack to another modpack/fixpack within the same major version(Example: from 12.1.0.0 to 12.1.1.0).This license requirement is already in place for non-java drivers. With this release, we are making this requirement for JCC as well.
License activation at the client/application side
So far, the JCC license jar that customer gets while downloading the license activation kit from PPA was db2jcc_license_cisuz.jar regardless of the license edition they purchase. With 12.1, the license jar names changed for each license editions. Below are the different Db2 Connect license editions available and the corresponding
So far, the JCC license jar that customer gets while downloading the license activation kit from PPA was db2jcc_license_cisuz.jar regardless of the license edition they purchase. With 12.1, the license jar names changed for each license editions. Below are the different Db2 Connect license editions available and the corresponding
JCC license jars.
DB2 Connect Unlimited Edition for System z - db2jcc_license_consvZS.jar
DB2 Connect Unlimited Edition for System i - db2jcc_license_consvIS.jar
DB2 Connect Application Server Edition - db2jcc_license_consvAS.jar
DB2 Connect Enterprise Edition - db2jcc_license_consvEE.jar
DB2 Connect Advanced Application Server Edition - db2jcc_license_consvAAS.jar
DB2 Connect Advanced Unlimited Edition for System z - db2jcc_license_consvAZS.jar.
DB2 Connect Unlimited Edition for System i - db2jcc_license_consvIS.jar
DB2 Connect Application Server Edition - db2jcc_license_consvAS.jar
DB2 Connect Enterprise Edition - db2jcc_license_consvEE.jar
DB2 Connect Advanced Application Server Edition - db2jcc_license_consvAAS.jar
DB2 Connect Advanced Unlimited Edition for System z - db2jcc_license_consvAZS.jar.
User needs to remove the old license jars and update the Java CLASSPATH with the new license jars while running the java application to use 12.1 JCC driver.
License activation for the Unlimited Edition at the Db2 Server side
Unlimited license edition can be activated at the Db2 Server side or at the client/application. If you activated the unlimited license for the existing Db2 Connect version (Example 11.5) at the Db2 Server, customer now need to download the 12.1 activation kit from PPA and follow the ex-isting license activation procedure to activate the same.
Unlimited license edition can be activated at the Db2 Server side or at the client/application. If you activated the unlimited license for the existing Db2 Connect version (Example 11.5) at the Db2 Server, customer now need to download the 12.1 activation kit from PPA and follow the ex-isting license activation procedure to activate the same.
sslClientHostnameValidation default value change for TLS/SSL connectivity.
Java driver
JCC property sslClientHostnameValidation is “OFF” by default today. From Db2 Connect 12.1 version, sslClientHostnameValidation will be “BASIC” by default. So, Customers who are using TLS/SSL Connection can have an impact if the Db2 Server certificate that is exchanged with the driver do not have the hostname or IP Address of the Db2 Server in the certificate once they move to Db2 Connect 12.1 version. In such cases, customer can set sslClientHostnameValida-tion property to “OFF” explicitly get the same behavior prior to 12.1 release.
JCC property sslClientHostnameValidation is “OFF” by default today. From Db2 Connect 12.1 version, sslClientHostnameValidation will be “BASIC” by default. So, Customers who are using TLS/SSL Connection can have an impact if the Db2 Server certificate that is exchanged with the driver do not have the hostname or IP Address of the Db2 Server in the certificate once they move to Db2 Connect 12.1 version. In such cases, customer can set sslClientHostnameValida-tion property to “OFF” explicitly get the same behavior prior to 12.1 release.
Non-java driver
sslclienthostnamevalidation property value is “OFF” by default today. From Db2 Connect 12.1 version, sslclienthostnamevalidation property value will be “Basic” by default. So, Customers who are using TLS/SSL Connection can have an impact if the Db2 Server certificate that is ex-changed with the driver do not have the hostname or IP Address of the Db2 Server in the certifi-cate once they move to Db2 Connect 12.1 version. In such cases, customer can set sslclien-thostnamevalidation db2dsdriver.cfg property value for CLI to “OFF” explicitly get the same behavior prior to 12.1 release.
sslclienthostnamevalidation property value is “OFF” by default today. From Db2 Connect 12.1 version, sslclienthostnamevalidation property value will be “Basic” by default. So, Customers who are using TLS/SSL Connection can have an impact if the Db2 Server certificate that is ex-changed with the driver do not have the hostname or IP Address of the Db2 Server in the certifi-cate once they move to Db2 Connect 12.1 version. In such cases, customer can set sslclien-thostnamevalidation db2dsdriver.cfg property value for CLI to “OFF” explicitly get the same behavior prior to 12.1 release.
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPDU","label":"Db2 Connect"},"ARM Category":[{"code":"a8m3p000000hBRiAAM","label":"JDBC and SQLJ Connection"},{"code":"a8m3p000000hBRcAAM","label":"ODBC and CLI Connection"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
15 November 2024
UID
ibm17176210