Setting up a connection to a Netezza data source (Watson Knowledge Catalog)

With the Netezza connector, Watson Knowledge Catalog tools can connect to a Netezza database, import database metadata, and access data in the database.

Before you can run automated discovery on Netezza databases, complete the following setup:

• Configure access to the Netezza databases.
• Add an import area for the Netezza database.

To complete these steps, you must be an administrator of the project (namespace) where Watson Knowledge Catalog is deployed.

Configuring access to Netezza databases

To configure access to Netezza databases, you must install the client libraries and add connection details to the .odbcinst.ini file.

1. Download the ips-linuxclient-v11.0.6.1.tar.gz package from IBM Fix Central. You can use this link or search for the package as follows:
   1. On Fix Central, click Select product. Then, pick the following values:
      • Product group: WebSphere
      • Select from WepShere: IBM Cloud Pak for Data System
      • Installed version: IPS_11.0
      • Platform: Linux Click Continue.
   2. On the Identify fixes page, select Individual fix IDs, enter the fix ID 11.0.6.1-WS-ICPDS-IPS-fp126015, and click Continue.
2. Copy the ips-linuxclient-v11.0.6.1.tar.gz package to the /root directory of the primary node. Use a secure copy tool such as WinSCP.
3. Move the package to a temporary directory:

   # scp /root/ips-linuxclient-v11.0.6.1.tar.gz <primary_node>:/tmp/
   

4. Move the package from the temporary directory to the conductor pod:

   # oc cp /tmp/ips-linuxclient-v11.0.6.1.tar.gz zen/is-en-conductor-0:/mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/ips-linuxclient-v11.0.6.1.tar.gz
   

5. Enter the pod:

   # oc -n zen exec -it is-en-conductor-0 bash
   [dsadm@is-en-conductor-0 /]$ cd /mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/
   

6. Unpack the files:

   [dsadm@is-en-conductor-0 EngineClients]$ tar -xvf ips-linuxclient-v11.0.6.1.tar.gz
   datadirect.package.tar.z
   linux/
   linux/unpack
   linux/npsclient.11.0.6.1.tar.gz
   linux64/
   linux64/unpack
   linux64/npsclient.11.0.6.1.tar.gz
   webadmin/
   webadmin/unpack
   webadmin/npswebclient.11.0.6.1.tar
   

7. Unpack the linux64 package. Use /mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/nz as the path.

   [dsadm@is-en-conductor-0 EngineClients]$ cd linux64
   [dsadm@is-en-conductor-0 linux64]$ ./unpack
   
   IBM IPS -- NPS Linux Client 11.0.6.1
   (C) Copyright IBM Corp. 2002, 2020 All Rights Reserved.
   Validating package checksum ... ok
   Where should the NPS Linux Client be unpacked? [/usr/local/nz] /mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/nz
   Directory '/mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/nz' does not exist; create it (y/n)? [y] y
   0% 25% 50% 75% 100%
   |||||||||||||||||||||||||||||||||||||||||||||||||||
   Unpacking complete.
   

8. Set connector-specific environment variables:
   1. Edit the dsenv file.

      cd $DSHOME
      vi dsenv
      

   2. Add the following entries at the end of the file:

      NZClientDir=/mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/nz
      LIBPATH=$LIBPATH:$NZClientDir/lib64
      export LIBPATH
      PATH=$PATH:$NZClientDir/bin64
      export PATH
      NZ_ODBC_INI_PATH=$DSHOME
      export NZ_ODBC_INI_PATH
      

9. Edit the .odbc.ini configuration file and add connection details:

   vi $DSHOME/.odbc.ini
   

   1. Locate the [ODBC Data Source] section and add the following entry:

      NPS=Netezza
      

   2. At the end of the file, add the following content replacing the values in <> with the proper values for your system:

      [NPS]
      Driver=/mnt/dedicated_vol/Engine/is-en-conductor-0/EngineClients/nz/lib64/libnzodbc.so
      Description=Netezza database
      Servername=<your_server>
      Port=5480
      Database=<your_database>
      ReadOnly=false
      FastSelect=false
      ShowSystemTables=false
      LegacySQLTables=false
      LoginTimeout=0
      QueryTimeout=0
      DateFormat=1
      NumericAsChar=false
      SQLBitOneZero=false
      StripCRLF=false
      securityLevel=preferredUnSecured
      caCertFile=
      ;loadMaxErrors=1
      ;loadRoundFraction=0
      

   3. Save the .odbc.ini file.
10. Restart the servers:

    cd $DSHOME/bin
    ./uv -admin -stop
    ./uv -admin -start
    cd /opt/IBM/InformationServer/ASBNode/bin
    . ./NodeAgents_env_DS.sh
    ./NodeAgents.sh stopAgent
    ./NodeAgents.sh start
    

Adding an import area for the Netezza database

To make the connection available for use in automated discovery jobs, add an import area for the Netezza connection:

1. Go to Catalogs > Metadata import.
2. Select Import and click New Import Area.
3. Name the import area, select IBM Netezza Connector from the list of bridges and connectors and click Next.
4. Click the magnifying glass icon next to the Data connection field to open the list of data connections. Then, click New Data Connection.
   NPS should be displayed in the Data source field.
5. Provide all other required information, such as credentials and the Netezza database name, and test the connection. Then, click OK.
6. On the Identity Parameters page, specify IS-EN-CONDUCTOR as the hostname and IADB as the database. Skip the DBMS server instance name and click Next.
7. Select to run an express import and click Import.

After the import is complete, the connection is ready for use. For more information, see Importing assets to the staging area.

Parent topic: Metadata import connectors