Configuring a JDBC Resource for IBM DB2/ iseries in Metadata Manager HotFix 2

Transcription

1 Configuring a JDBC Resource for IBM DB2/ iseries in Metadata Manager HotFix Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners.

2 Abstract You can use a JDBC resource to extract metadata from any relational database to which you can connect through JDBC. This article describes how to create and configure a JDBC resource in Metadata Manager to extract metadata from IBM DB2/iSeries. Note: This article describes how to create and configure a JDBC resource in Metadata Manager HotFix 2 to extract metadata from IBM DB2/iSeries. For Metadata Manager versions HotFix 1 and earlier, see the H2L article Configuring a JDBC Resource for IBM DB2/iSeries in Metadata Manager ( Supported Versions Metadata Manager HotFix 2 Table of Contents Overview JDBC Metadata Source Configuration Install the Metadata Manager Agent Configure Permissions Creating a JDBC Resource JDBC Configuration Properties Connection Assignment Troubleshooting Resource Loads Objects Extracted and Not Extracted Overview You can create and configure a JDBC resource to extract metadata from any relational database management system that is accessible through JDBC. For relational databases that support JDBC, you can create and configure a JDBC resource instead of creating and configuring a custom resource. It is easier to manage linking between objects in connected resources with JDBC resources. You can create a JDBC resource for any relational database that supports JDBC. Informatica has tested the JDBC resource for IBM DB2/iSeries. You cannot connect to relational databases through ODBC. Informatica recommends that you use the existing database resource types specific to that relational database instead of the JDBC resource whenever possible. The database-specific resource types perform better and extract more metadata aspects. For example, to load metadata from an Oracle database, create an Oracle resource instead of creating a JDBC resource. JDBC Metadata Source Configuration Before you create a JDBC resource, you must configure the metadata source. If you do not correctly configure the metadata source, the metadata load can fail or the metadata can be incorrectly loaded in the Metadata Manager warehouse. Install the Metadata Manager Agent. Configure the permissions for the database user account that you use to connect to the database. Make sure that the user has access to the system tables rather than the data tables. Install and configure required database drivers. For example, to configure a JDBC resource to use IBM DB2/iSeries, you can use the data drivers that are available to you when you install PowerCenter. Make sure that the JDBC driver JAR files are available on the same host as the Metadata Manager Agent. 2

3 To test the connection settings to the data source, use any available interface to connect to it through JDBC. For example, you use the database development perspective in Eclipse to test the connection settings. After connecting to the data source, verify that you can access the catalog, schema, or tables that you want to import. Use these connection settings when you configure a JDBC resource for that data source. Install the Metadata Manager Agent The Metadata Manager Agent is a program that Metadata Manager uses to access metadata sources and extract source metadata. By default, the Metadata Manager Agent runs on the Windows node where the Metadata Manager Service runs. You can also install the Metadata Manager Agent on another Windows machine. The Metadata Manager Agent does not run on UNIX. If the Metadata Manager Service runs on UNIX, you must install the Metadata Manager Agent separately on a Windows machine. For more information about installing the Metadata Manager Agent, see the Metadata Manager Administrator Guide. Configure Permissions To enable access to system objects in a relational database, you must configure the appropriate permissions. Creating a JDBC Resource Before you create a JDBC resource, configure the JDBC metadata source. 1. On the Load tab, click Actions > New Resource. The Resource Selection window appears. 2. Click Database Management > JDBC. 3. Click Next. The Properties page appears. 4. Enter the following information: Property Name Name for the resource. The resource appears in the Resources panel with this name. The name must be unique and have from one through 256 characters. It cannot include the following characters: / \ : * '? " < > [ ] for the resource. cannot exceed 4000 characters. 5. Click Next. The Configuration page appears. 6. Enter the configuration properties. 7. Click Test Connection to test the connection to the source system. If Metadata Manager cannot connect to the source system, an error message appears. Correct any error and test the connection again. 8. Click Next. The Schedules window appears. 9. To add a schedule, select Attach a Schedule and select a schedule in the Schedule list. If you have not created a schedule, you can assign a schedule to a resource after you create the resource. 3

4 10. Click Finish. The resource appears in the Resources panel on the Load tab. JDBC Configuration Properties Update the configuration properties when you create or edit a JDBC resource. The following table describes the JDBC configuration properties: Property Agent URL Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine. For example: Source system version Driver class Name and version of the metadata source. Name of the Java class that implements the JDBC driver interface. Specify the full name including the package name. For example: com.informatica.jdbc.db2.db2driver Driver path URL Path to the JDBC driver JAR file. Separate multiple values with a semicolon (;). If required, copy the JAR file to the Windows machine on which the Metadata Manager Agent is installed. The driver path is relative to the Metadata Manager Agent location. If you specify the file name without specifying the path, verify that the JAR file is in the classpath of the machine that runs the Metadata Manager Agent. For example, the data driver for IBM DB2/iSeries is in the following directory: <Informatica installation directory>\services\metadatamanagerservice\utilities \mmcmd\lib JDBC URL to connect to the database. Metadata Manager uses this URL to verify connection information to the database. The value that you specify depends on the database and the driver that you use. For example: jdbc:informatica:db2://<host name>:<port>;locationname=<location name>;packagecollection=<package collection> The default port number of the IBM DB2/iSeries server is 446. User name Password Catalog Name of the user account used to connect to the database. Password for the user account used to connect to the database. Catalog name that Metadata Manager uses to filter metadata. The catalog is a container for schemas and global objects. IBM DB2/iSeries does not use a catalog. Schema Schema name that Metadata Manager uses to filter metadata. Separate multiple values with a semicolon (;). If you do not specify a schema name, Metadata Manager loads the first schema in the list of available schemas sorted in ascending alphabetical order. 4

5 Property View definition extracting SQL Database-specific SQL query to extract the view definitions. The query must return results with a single column that contains the view definition text. If you do not enter a query, Metadata Manager does not build data lineage between views and their source tables. Enter the following query for IBM DB2/iSeries: SELECT TABLE_SCHEMA, TABLE_NAME, VIEW_DEFINITION FROM QSYS2.SYSVIEWS WHERE TABLE_SCHEMA IN (?) Synonym lineage SQL Database-specific SQL query to extract the synonym information for tables and views. Note: This property is reserved for future use. Connection Assignment You can use a JDBC resource as the target for connection assignments after you load the resource. For example, you can create connections from a PowerCenter resource to a JDBC resource that represents the IBM DB2/ iseries database schema. Troubleshooting Resource Loads You can monitor a resource load run to determine whether it is successful. If a resource load fails, troubleshoot the failure and load the resource again. Load fails for a JDBC resource when driver details are not properly configured. When you specify the driver details during resource configuration, complete the following tasks: For the driver class, specify the full name including the package name. For the driver path, verify that the JAR file is in the same host as the Metadata Manager Agent. Load fails for a JDBC resource when the source is IBM DB2/iSeries version V6R1. Assign the ALLOBJ privilege to the user, and then reload the resource. Objects Extracted and Not Extracted After you create and load a JDBC resource, you can view and run data lineage on the metadata objects that Metadata Manager extracted. To view lineage between views and tables, specify a database-specific SQL query to extract the view definitions when you create or edit a JDBC resource. Metadata Manager uses the view definitions text to build lineage between views and tables. Objects Extracted Metadata Manager extracts the following objects from a JDBC resource: Schema name Table name, Comments Column name, Nullable, Position, Length, Scale, Comments, Data type Data type is a generic equivalent of the proprietary datatype. 5

6 View name, View definition Metadata Manager extracts view definitions when you specify the view definition extraction SQL during resource configuration. Objects Not Extracted Metadata Manager does not extract the following objects from a JDBC resource: Catalog name Synonyms of tables and views Indexes Stored procedures Triggers Primary key and foreign key information Profiling information Author Lori Troy Senior Technical Writer Acknowledgements The authors would like to thank Rashmi Mani, Lead Software Engineer QA, for her technical assistance. 6