•After you have copied the NetezzaSQL driver JAR file, restart the Data Integration Service.
•Create endpoint catalog sources for connection assignment.
•Optionally, if you want to identify pairs of similar columns and relationships between tables within a catalog source, import a relationship inference model.
Verify permissions
To extract metadata and to configure other capabilities that a catalog source might include, you need account access and permissions on the source system. The permissions required might vary depending on the capability.
Permissions for metadata extraction
To extract IBM Netezza metadata, you need account access and permissions to the IBM Netezza source system.
Verify that the administrator grants the View Definition permission to perform the following operations on the IBM Netezza database:
•select on _V_OBJECTS
•select on _V_PROCEDURE
•select on _V_SCHEMA
•select on _V_SEQUENCE
•select on _V_SYNONYM
•select on _V_VIEW
•select on _V_RELATION_COLUMN
•select on _V_RELATION_KEYDATA
•select on _V_DATABASE
•select on _V_JDBC_COLUMNS1
Permissions to run data profiles
You can run profiles with the permissions required to perform metadata extraction.
Permissions to run data classification
You can perform data classification with the permissions required to perform metadata extraction.
Permissions to run relationship discovery
You can perform relationship discovery with the permissions required to perform metadata extraction.
Permissions to run glossary association
You can perform glossary association with the permissions required to perform metadata extraction.
Create a connection
Create a Netezza connection object in Administrator with the connection details of the IBM Netezza source system.
Before you can use Netezza Connector, install the Netezza client on Windows or Linux. Ensure that you have access to the Secure Agent directory that contains the success and error files. This directory path must be the same on each Secure Agent machine in the runtime environment selected for your connection. Before you create a Netezza connection, be sure to configure the Netezza ODBC and JDBC drivers.
1In Administrator, select Connections.
2Click New Connection.
3Enter the following basic connection details:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
Netezza.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
The name of the runtime environment where you want to run tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
Database
The name of the Netezza database.
Schemaname
The schema used for the Netezza source or target.
Schema name is case sensitive.
Servername
The Netezza database host name.
Port
Network port number used to connect to the database server.
Default is 1521.
Username
Database user name with the appropriate read and write database permissions to access the database.
Password
Password for the database user name.
4Enter the following advanced connection details:
Property
Description
Driver
The Netezza ODBC driver name that is used to connect to the Netezza database.
The Netezza ODBC driver name is NetezzaSQL.
Runtime Additional Connection Configuration
Additional runtime attributes required to fetch data.
For example, securityLevel=preferredUnSecured;caCertFile =
Metadata Additional Connection Configuration
The values to set the optional properties of the JDBC driver to fetch the metadata.
5Click Test Connection.
6Click Save.
Create endpoint catalog sources for connection assignment
An endpoint catalog source represents a source system that the catalog source references. Before you perform connection assignment, create endpoint catalog sources and run the catalog source jobs.
You can then perform connection assignment to reference source systems to view complete lineage with source system objects.
Import a relationship inference model
Import a relationship inference model if you want to configure the relationship discovery capability. You can either import a predefined relationship inference model, or import a model file from your local machine.
1In Metadata Command Center, click Explore on the navigation panel.
2Expand the menu and select Relationship Inference Model. The following image shows the Explore page with the Relationship Inference Model menu:
3Select one of the following options:
- Import Predefined Content. Imports a predefined relationship inference model called Column Similarity Model v1.0.
- Import. Imports the predefined relationship inference model from your local machine. Select this if you previously imported predefined content into your local machine and the inference model is stored on the machine.
To import a file, click Choose File in the Import Relationship Inference Model window and navigate to the model file on your local machine. You can also drag and drop the file.
The imported models appear in the list of relationship inference models on the Relationship Discovery tab.
