Configuring a Sybase PowerDesigner Resource in Metadata Manager 9.0 2010 Informatica
Abstract This article shows how to create and configure a Sybase PowerDesigner resource in Metadata Manager 9.0 to extract metadata from Sybase PowerDesigner 12.5. Supported Versions Metadata Manager 9.0 Table of Contents Sybase PowerDesigner.... 2 Configuring Sybase PowerDesigner.... 2 Install the Metadata Manager Agent.... 3 Export Models to Metadata Files.... 3 Creating a Sybase PowerDesigner Resource.... 3 Reference for Data Modeling Resources.... 4 Datatypes.... 4 Validation Rules.... 5 Relationships.... 5 View Associations.... 5 Schema and Owners.... 6 Name and Properties.... 6 Multiple Models in the Same Repository.... 6 Objects Not Extracted.... 6 Domain-to-Validation Rule Association.... 6 Sybase PowerDesigner Sybase PowerDesigner is a data modeling tool used to create and maintain data models. You can create and configure a Sybase PowerDesigner resource to extract Sybase PowerDesigner metadata. Before you create a Sybase PowerDesigner resource, you export Sybase PowerDesigner models to metadata files. When you create the resource, you specify the metadata file. Metadata Manager extracts the Sybase PowerDesigner models from the metadata file. Configuring Sybase PowerDesigner Before you create a Sybase PowerDesigner 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. To configure Sybase PowerDesigner, complete the following tasks: Install the Metadata Manager Agent. Export models to metadata files. 2
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 nodes where the Metadata Manager Service runs. If the Metadata Manager Service runs on UNIX, you must install the Metadata Manager Agent separately on a Windows machine. The Metadata Manager Agent does not run on UNIX. Export Models to Metadata Files To extract metadata from Sybase PowerDesigner, you export models from Sybase PowerDesigner to metadata files. Use the Sybase PowerDesigner client tool to save the model to a.pdm file in XML format. Metadata Manager extracts Sybase PowerDesigner models from the exported metadata files. Creating a Sybase PowerDesigner Resource Before you create a Sybase PowerDesigner resource, export the Sybase PowerDesigner models to metadata files. To create a Sybase PowerDesigner resource: 1. On the Load tab, click Actions > New Resource. The Resource Selection window appears. 2. Click Data Modeling > PowerDesigner. 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 1 through 256 characters. It cannot include the following characters: / \ : * '? " < > [ ] for the resource. cannot exceed 4,000 characters. 5. Click Next. The Configuration page appears. 6. Configure the following resource properties: Property Agent URL Source system version Always use latest source files Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine. Name and version of the metadata source. You cannot edit this field. Metadata Manager uses the metadata source file in the location you provide each time you load the resource. If you enable this option, the path to the file must include an absolute path that is accessible from the Metadata Manager Agent machine. If you disable this option, Metadata Manager copies the metadata source file to the Metadata Manager application directory when you finish configuring the resource. Each time you load the resource, Metadata Manager uses the copied metadata source file in the Metadata Manager application directory. 3
Property Encoding Auto Assign Connections Code page for the PDM file that you exported from Sybase PowerDesigner. Metadata Manager configures connection assignments to relational database resource types during the resource load. If you disable this option, you must configure connection assignments in the resource properties after you create the resource. 7. To add a metadata source file, click Add. If you configured Metadata Manager to use the latest source files, include an absolute path to the file that is accessible from the Metadata Manager Agent machine. If you did not configure Metadata Manager to use the latest source files, select a file and click OK. Configure the following property for the source file: Property Refresh Updates the metadata in the Metadata Manager warehouse with the metadata from the source file. Metadata Manager extracts the metadata from the source file and converts it to IME files. Select one of the following options: - True. Refresh the metadata in the warehouse using the metadata in the source file. - False. Use the metadata in the previously generated IME files. If you configure Metadata Manager to use the latest source files, this option must be true for at least one of the source files. 8. To add more files, click Add, enter the file name in the Source File box, and enter the user name and password. 9. To remove a file you added, select the file and click Delete. You must configure at least one file for the resource. 10. Click Test Connection to validate the source file configuration. Metadata Manager validates the Metadata Manager Agent URL. If you configured Metadata Manager to use the latest source file, Metadata Manager also validates that the source file exists in the specified path. If Metadata Manager cannot validate the source file configuration, an error message appears. Correct any error and test the connection again. 11. Click Next. The Schedules page appears. 12. 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. 13. Click Finish. The resource appears in the Resources panel on the Load tab. Reference for Data Modeling Resources After you create and load a data modeling resource, you can view and run data lineage on the metadata objects that Metadata Manager extracted. The following information applies to all data modeling tool resources. Datatypes Metadata Manager extracts datatypes and change the names based on the datatypes used by Metadata Manager. Metadata Manager stores the datatypes in the Metadata Manager warehouse. 4
Names of Datatypes Metadata Manager extracts the datatypes for objects in the Domains and Column classes and stores them as properties of the objects. While extracting the datatypes, Metadata Manager changes the names of the datatypes to the names used by Metadata Manager. For example, if Metadata Manager extracts a datatype named integer in the data modeling tool, Metadata Manager converts this to name to SQL_integer. You may not see a match between the datatype name in the data modeling tool and the corresponding name in the metadata catalog. Datatypes for Columns Using Domains Data modeling tools store datatypes for domains and most columns, all of which Metadata Manager extracts and stores in the Metadata Manager warehouse. Since data modeling tools do not store datatypes for columns using domains, Metadata Manager cannot extract or store the datatypes for these columns. To help you determine the datatype of columns using domains, Metadata Manager stores the datatypes of all domains and establishes an association between columns and their corresponding domains. To determine the datatype of a column using a domain, determine the domain associated with the column, and then determine the datatype of the domain. Validation Rules You can define validation rules in data modeling tools and reuse the rules. Metadata Manager stores one instance of the validation rule for each column or domain that uses the rule. In data modeling tools, there is a one-to-many relationship between validation rules and columns or domains. To identify each validation rule for each column or domain, Metadata Manager renames each validation rule based on the column or domain name. The following table shows a validation rule VR1 that is used by columns X and Y and the domain DOM: Validation Rule in Data Modeling Tool VR1 Validation Rule in Metadata Manager X Y DOM Metadata Manager renames validation rule, VR1, to the column and domain names, X, Y, and DOM. Metadata Manager extracts validation rules that are used in columns or domains. Relationships Metadata Manager does not extract relationships named Subtype. View Associations Metadata Manager does not parse the SQL to determine the associations between views and tables and between views and columns. To load view-to-table and view-to-column associations, the data modeling tool must provide this information to Metadata Manager. 5
Schema and Owners You can specify an owner when you create an object in a data modeling tool. Metadata Manager extracts distinct owners of objects, assigns the owners as the schema names in the Metadata Manager warehouse, and creates the associations between the objects and the schema. If you did not assign an owner to the object in the data modeling tool, Metadata Manager assigns Undefined schema as the schema name and associates the object with this schema name. Name and Properties Metadata Manager maps the physical name of an object to the Name property and the logical name to the Label property. If a logical name does not exist in the data modeling tool, Metadata Manager assigns the physical name of the object to the Name and Label properties. Metadata Manager maps comments about the object to the Usage property and descriptions or definitions to the property. Note: Name, Label, Usage, and are properties of model classes. Multiple Models in the Same Repository You can load multiple models into the same data modeling tool resource. The metadata catalog shows these models under the same instance of a data modeling tool resource. Objects Not Extracted Metadata Manager does not extract the following object types: Tablespaces Rollback segments Synonyms Sequences Database packages Materialized views Domain-to-Validation Rule Association Data modeling tools can use the following validation rules: MinMax. Makes sure that each value of a column is not below a predefined minimum value or above a predefined maximum value. ListConstraint. Makes sure that each value of a column is valid based on a predefined set of possible values. RuleConstraint. Makes sure that each value of a column is valid using user-defined logic or expression. Although domains can be associated with any of these rules, Metadata Manager extracts associations between a domain and the MinMax or ListConstraint rule. Author Alison Taylor Technical Writer 6