content_image/984016.jpg
6. The installation path of IBM App Connect in a container in IBM Cloud Pak for Integration platform is /opt/ibm/ace-11/ . Therefore, modify the odbc.ini file as shown in Example 7-4 below to reflect the correct path of the odbc driver in IBM App Connect container. Make the similar change to the InstallDir  path under mandatory [ODBC] stanza. 

[USERDB] Driver=/opt/ibm/ace-11/server/ODBC/drivers/lib/UKora95.so ;########################################## ;###### Mandatory information stanza ###### ;########################################## [ODBC] InstallDir=/opt/ibm/ace-11/server/ODBC/drivers UseCursorLib=0 IANAAppCodePage=4 UNICODE=UTF-8 

Note:  Only a partial snippet of odbc.ini file configuration is shown in the preceding example. Refer to the product Knowledge Center for the complete DSN stanza for respective database providers. 

7. In the Downloaded configuration package, you will find a file named setdbparms.txt. Associate your DSN with the user ID and password as shown in Example 7-5 . 

#<Resource Name> <Userid> <Password> USERDB user1 passwd1 

This is equivalent to running mqsisetdbparms  command for an on-premises integration server. 

8. Create the Kubernetes secret by using the generateSecret.sh script, which is available in the downloaded configuration package. The syntax and considerations for running generateSecret.sh is already described in previous section. 

$ generateSecret.sh myodbcsecret icp4i 

9. In the helm chart, specify this secret in the field for integration server secret configuration as shown in Figure 7-78. 

<img src='content_image/984016.jpg'>

10.After the helm chart is deployed successfully verify the database operations by processing a message through the flow. 

## Connecting via JDBC interface 

You might include a DatabaseRetrieve, DatabaseRoute, JavaCompute, Mapping, or Java user-defined node in a message flow, and interact with a database in that node. In this case, 

