Netezza Resource Configuration
Source System Properties
This configuration can be setup by creating a new connection on Admin UI / Connections tab or editing an existing connection in Admin UI / Connections / Databases / Netezza /specific connection. New connection can also be created via Manta Orchestration API.
Granularity of the IBM Automatic Data Lineage connection for Netezza is one Netezza server. Use filter on databases and schemas to limit the scope of analysis as needed. Use of multiple connections against a single Netezza server may lead to within-system lineage not be connected properly.
| Property name | Description | Example |
|---|---|---|
| netezza.dictionary.id | Name of a resource representing this Netezza server known as the dictionary ID, used as an output subdirectory name for extracted DDL files and the database dictionary | NZ |
| netezza.url | JDBC connection string for the Netezza database; use any extracted database for the <database> part. When receiving: Cannot create JDBC driver of class '{jdbc driver name}' for connect URL 'jdbc:netezza://<host>:<port>/database;' No suitable driver message, ensure that JDBC parameters are correct before troubleshooting the given JDBC driver |
jdbc:netezza://<host>:<port>/<database>; |
| netezza.username | Name of the user with the specified privileges needed for extraction | manta_user |
| netezza.password | Password of the user with the specified privileges | manta_password |
| netezza.extractedDbsSchemas | List of databases and schemas to extract, separated by commas, which are to be provided in the format database/schema; each part is evaluated as a regular expression | database1/sch1,database2/sch2,database3 |
| netezza.excludedDbsSchemas | List of databases and schemas to exclude from extraction, separated by commas | database3/sch3,database3/sch4 |
| netezza.extraction.method | Set to Agent:default when the desired extraction method is the default Manta Extractor Agent, set to Agent:{remote_agent_name} when a remote Agent is the desired extraction method, set to Git:{git.dictionary.id} when the Git ingest method is the desired extraction method. For more information on setting up a remote extractor Agent please refer to the Manta Flow Agent Configuration for Extraction documentation. For additional details on configuring a Git ingest method, please refer to the Manta Flow Agent Configuration for Extraction:Git Source documentation. | default / Git / agent |
| netezza.ddl.encoding | Encoding of automatically extracted Netezza DDL scripts. See Encodings for applicable values. | utf8 |
| netezza.script.encoding | Encoding of manually provided NZPLSQL scripts performed on this Netezza database instance. See Encodings for applicable values. | utf8 |
| netezza.defaultPath | Default PATH variable used during the lookup of any unqualified procedures; the value has the same syntax as the value in the SET PATH = ... command, but supports only database or schema objects, no variables | database1.schema1, database2.schema2 |
| netezza.hostName | User-set host name. Leave blank, to use the automatically extracted server name. Set to a custom unique server name to override the automatically extracted server name. For example, when the Netezza database experiences a failover, the hostname extracted from the database changes. | NETEZZA |
Common Scanner Properties
This configuration is common for all Netezza source systems and for all Netezza scenarios, and is configure in Admin UI / Configuration / CLI / Netezza / Netezza Common. It can be overridden on individual connection level.
|
Property name |
Description |
Example |
|---|---|---|
|
netezza.dictionary.dir |
Directory with data dictionaries extracted from Netezza |
${manta.dir.temp}/netezza |
|
filepath.lowercase |
Whether paths to files should be lowercase (false for case-sensitive file systems, true otherwise) |
false |
|
netezza.dll.output |
Directory for automatically extracted Netezza DDL scripts (for the extraction phase) |
${manta.dir.temp}/netezza/ |
|
netezza.ddl.input |
Directory with automatically extracted Netezza DDL scripts (for the analysis phase) |
${netezza.dll.output} |
|
netezza.script.input |
Directory with manually provided NZPLSQL scripts which are performed on this Netezza database instance (for the analysis phase) |
${manta.dir.input}/netezza/ |
|
netezza.script.replace |
Path to the CSV file with the replacements to be applied to the provided NZPLSQL scripts; see Placeholder Replacement in Input Scripts for details about the replacement file format |
${manta.dir.input}/netezza/${netezza.dictionary.id}/replace.csv |
|
netezza.script.replace.regex |
Flag specifying whether replacements for NZPLSQL scripts in the provided CSV file specified in |
false |
|
netezza.analyze.parallelCount |
Number of parallel threads which will analyze DDL and NZPLSQL |
4 |
|
netezza.dictionary.mappingFile |
Path to automatically generated mappings for Netezza databases |
${manta.dir.temp}/netezza/ netezzaDictionaryMantaMapping.csv |
|
netezza.dictionary.mappingManualFile |
Path to mappings provided manually for Netezza databases |
${manta.dir.scenario}/conf/ netezzaDictionaryMantaMappingManual.csv |
|
netezza.sqlextensions.enabled |
Whether built-in functions from Netezza SQLExtensions should be included in the extraction/analysis |
true |
|
netezza.sqlextensions.database |
Database under which SQL extensions are installed; only applies if |
TOOLKIT |
|
netezza.sqlextensions.schema |
Schema under which SQL extensions are installed; only applies if |
SQLEXT |
|
netezza.analyze.retainUnusedResultSetColumns |
Flag specifying whether the data lineage should include sub-query resultset columns that do not have any downstream lineage By default, set to false |
false |
|
netezza.expressionDescriptions.enabled.ddl |
Enables or disables building transformation logic descriptions from SQL code in DDL scripts |
false |
|
netezza.expressionDescriptions.enabled.nzplsql |
Enables or disables building transformation logic descriptions from SQL code in SQL scripts |
false |
|
netezza.expressionDescriptions.enabled.queryService |
Enables or disables building transformation logic descriptions from Netezza SQL code defined in other technologies |
false |
Manual Mapping Properties
It is possible to manually configure mappings for Netezza databases in the file ${netezza.dictionary.mappingManualFile}listed in the table above. This is necessary for non-extracted schemas in the Automatic Data Lineage extraction phase.
In order to configure manual mapping, copy a relevant line from the automatically generated file ${netezza.dictionary.mappingFile} and modify the Connection ID column with the external connection identifier.
Each mapping has its own row with the following parts separated by semicolons.
|
Property name |
Description |
Example |
|---|---|---|
|
Dictionary ID |
Name of a resource representing this Netezza server known as the dictionary ID, used as an output subdirectory name for extracted DDL files and the database dictionary |
NETEZZA |
|
Host name |
Name of the host where the database is running |
localhost |
|
Host port |
Port on which the database listens |
5480 |
|
Connection ID |
External Netezza connection ID in third-party tools; for example, as it appears in the Informatica PowerCenter connection string, etc., or it can be left empty if it is the same as the host name |
NETEZZA |
|
Include filter |
List of databases and schemas to extract, separated by commas, which are to be provided in the format database/schema; each part is evaluated as a regular expression |
database1/sch1,database2/sch2,database3 |
|
Exclude filter |
List of databases and schemas to exclude from extraction, separated by commas |
database3/sch3,database3/sch4 |