Connecting Information Server to an IBM Db2 Big SQL instance

Using the InfoSphere Metadata Asset Manager, you can use the Db2 connector on the computer designated as a metadata interchange server to import implemented data resources, including database schemas and tables, from Db2 Big SQL.


The Db2 connector uses the Db2 client to connect to your databases. The following example illustrates how you can catalog a remote Db2 Big SQL server and database on the metadata interchange server node, and then use the InfoSphere Metadata Asset Manager to import data from the Db2 Big SQL instance.

  1. Start by cataloging the bigsql database on a Db2 Big SQL cluster. Run the following commands as the db2inst1 user to catalog the bigsql database of a Db2 Big SQL server with the head node running on FQDN/IP-Address port 32051. In this example, the cataloged node and database use biwin as the local name for the machine hosting the database, as well as the alias for the database, respectively.
    db2 catalog tcpip node biwin remote <FQDN/IP-Address> server 32051
    db2 catalog db bigsql as biwin at node biwin
    db2 terminate
  2. Restart the InfoSphere Information Server.

The InfoSphere Metadata Asset Manager (IMAM) can be used to import the metadata that represents schemas, tables, views, nicknames, and columns in Db2 Big SQL. The imported metadata is saved in the metadata repository.

  1. Open the IBM Information Server launchpad, from which you can access the various IIS governance tools.
    IIS user interface showing the available governance tools
  2. Open the Metadata Asset Manager and click New Import Area.
    IMAM interface: New Import Area button
  3. Specify a name, description and the interchange server for the import area, and select IBM InfoSphere DB2 Connector as the connector type.
    Create New Import Area dialog: import area name, description, server, and connector type
  4. Click on the icon beside the Data connection field to specify the connector details.
    Create New Import Area dialog: Data connection field and button
  5. Click the New Data Connection button.
    Select a Data Connection dialog: New Data Connection button
  6. Specify the name, description, location, and credentials for the connection.
    New Data Connection dialog
  7. Click Test Connection to verify the settings.
    New Data Connection dialog: Test Connection button
  8. If the settings are correct the connection test should be reported as successful.
    New Data Connection dialog: The connection test was successful.
  9. Provide a description for the import event and click the Express Import radio button if it is not already selected.
    Create New Import Area dialog: Import description and Express Import
  10. The new import area should be created successfully.
    Create New Import Area dialog: results successful
  11. The imported database and metadata is now visible in IMAM under Import > Shared Imports.
    DemoImportArea with database metadata
  12. Under the Import tab you can see the name, description, timestamp, and other details for the new, completed import.
    Import Areas dialog with details for each import
  13. You can also see the detailed database metadata and connection information.
    Details for database Bank

What to do next

To capture ongoing changes to the Db2 Big SQL database and reflect updates, the Information Governance Catalog (IGC) repository imports can be repeated periodically to a staging area and the relevant assets can be updated selectively.

For more details about using the IMAM see Importing metadata by using InfoSphere Metadata Asset Manager in the InfoSphere Information Server Knowledge Center.