You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> Note the two extra keywords **Security** and **SSLServerCertificate** used in connection string. `SSLServerCertificate` should point to the SSL Certificate from server or an CA signed certificate. Also, `PORT` must be `SSL` port and not the TCPI/IP port. Make sure Db2 server is configured to accept connection on SSL port else `ibm_db` will throw SQL30081N error.
111
111
112
+
> `ibm_db` uses IBM ODBC/CLI Driver for connectivity and it do not support a certificate generated in `jks` format.
113
+
`ibm_db` do not work with a `keystore.jks` file or any certificate generated for Java application. `ibm_db` works
114
+
with a certificate generate for non-Java application that can get processed by GSKit tool. If you have a `*.jks` file,
115
+
please get a SSL Certificate meant for non-Java application. If you have downloaded `IBMCertTrustStore` from IBM site,
116
+
ibm_db will not work with it; you need to download `Secure Connection Certificates.zip` file that comes for IBM
117
+
DB2 Command line tool(CLP).
118
+
119
+
> `ibm_db` supports only ODBC/CLI Driver keywords in connection string: https://www.ibm.com/docs/en/db2/11.5?topic=odbc-cliodbc-configuration-keywords
120
+
121
+
> Do not use keyworkds like `sslConnection=true` in connection string as it is a JDBC connection keyword and ibm_db
122
+
ignores it. Corresponding ibm_db connection keyword for `sslConnection` is `Security` hence, use `Security=SSL;` in
123
+
connection string instead.
124
+
112
125
To connect to dashDB in IBM Cloud, use below connection string:
> Value of `SSLServerCertificate` keyword must be full path of a certificate generated for non-Java application on
137
+
Db2 Server. It normally has `*.arm` or `*.cert` or `*.pem` extension. `ibm_db` do not support `jks` format
138
+
certificate file.
139
+
118
140
You can also create a KeyStore DB using GSKit command line tool and use it in connection string along with other keywords as documented in [DB2 Infocenter](http://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.sec.doc/doc/t0053518.html).
119
141
142
+
If you have created a KeyStore DB using GSKit using password or you have got *.kdb file with *.sth file, use
**Note:** You can also create keystoredb using GSKit and add certificate file to keystoredb to use as documented in [DB2 Infocenter](http://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.sec.doc/doc/t0053518.html).
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ Async APIs return promises if callback function is not used. Async APIs supports
11
11
12
12
-**SQL1598N Error** - It is expected in absence of valid db2connect license. Please click [here](#sql1598n) and read instructions.
13
13
14
+
-**GSKit Error** - Check instructions as documented [here](https://github.com/ibmdb/node-ibm_db/blob/master/APIDocumentation.md#SSLConnection).
15
+
14
16
## API Documentation
15
17
16
18
- For complete list of ibm_db APIs and example, please check [APIDocumentation.md](https://github.com/ibmdb/node-ibm_db/blob/master/APIDocumentation.md)
@@ -32,6 +34,9 @@ Install a newer compiler or upgrade older one.
32
34
33
35
-**For Docker Linux Container:** make sure you have installed **make, gcc, g++(gcc-c++), python3.9 and node** before installing `ibm_db`. For `root` user, use `npm install --unsafe-perm ibm_db` to install `ibm_db`.
34
36
37
+
- While installing `ibm_db` under a container, if you get libcrypt error, add a line in your scrip to install `libcrypt` and `libcrypt-compat` as this library is not present in most of the container OS. f.e. add a line like below in docker script:
-**For Windows Subsystem for Linux (WSL):** Install `build-essentials` package before installing `ibm_db`.
36
41
37
42
-**For MacOS:** Install XCode from appstore before installing `ibm_db`. Also, gcc@8 and `make` is required.
@@ -373,6 +378,8 @@ To suppress this error, Db2 server must be activated with db2connectactivate uti
373
378
374
379
- Client side db2connect license is a `db2con*.lic` file that must be copied under `clidriver\license` directory.
375
380
381
+
- User running application must have write permission for`clidriver\cfgcache` and `clidriver\license` directories as clidriver need to create binary files to store licensing infoin these directories at runtime. Lack of permission to create file too causes SQL1598N error.
382
+
376
383
- If you have a `db2jcc_license_cisuz.jar` file, it will not work for ibm_db. `db2jcc_license_cisuz.jar` is a db2connect license file for Java Driver. For non-Java Driver, client side db2connect license comes as a file name `db2con*.lic`.
377
384
378
385
- If environment variable `IBM_DB_HOME` or `IBM_DB_INSTALLER_URL` is not set, `ibm_db` automatically downloads [open source driver specific clidriver](https://public.dhe.ibm.com/ibmdl/export/pub/software/data/db2/drivers/odbc_cli/) from https://public.dhe.ibm.com/ibmdl/export/pub/software/data/db2/drivers/odbc_cli and save as `node_modules\ibm_db\installer\clidriver`. Ignores any other installation.
0 commit comments