Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference
  17. Appendix B: PowerCenter Reports Reference

Repository Guide

Repository Guide

Creating Reusable Metadata Extensions

Creating Reusable Metadata Extensions

You can create reusable metadata extensions for repository objects using the Repository Manager.
When you create a reusable metadata extension for any type of repository object, the metadata extension becomes part of the properties of that type of object. For example, you create a reusable metadata extension for source definitions called SourceCreator. When you create or edit any source definition in the Designer, the SourceCreator extension appears on the Metadata Extensions tab. Anyone who creates or edits a source can enter the name of the person that created the source into this field.
To create a reusable metadata extension:
  1. In the Repository Manager, connect to the appropriate repository.
  2. Choose Edit > Metadata Extensions.
    The Edit Metadata Extensions dialog box opens.
    This dialog box lists the existing user-defined and vendor-defined metadata extensions. User-defined metadata extensions appear in the User Defined Metadata Domain. If vendor-defined metadata extensions exist, they appear in their own domains.
  3. Open the User Defined Metadata Domain.
  4. Click Add.
    The Add Metadata Extensions dialog box opens.
  5. Enter the metadata extension information.
    The following table describes the options available in the Add Metadata Extension dialog box:
    Field
    Description
    Extension Name
    Name of the metadata extension. Metadata extension names must be unique for each type of object in a domain.
    Metadata extension names cannot contain any special character except underscore, and they cannot begin with a number.
    Object Type
    Type of repository object to which the metadata extension is associated. This can be a source definition, target definition, transformation, mapping, mapplet, session, workflow, worklet, or all of these objects.
    You associate metadata extensions with specific types of transformations. For example, if you create a metadata extension for Expression transformations, it is available for Expression transformations.
    Database Type
    Database type. The database type is required for source and target definition objects. You can select a single database type or all database types. Required for source and target definition objects.
    Datatype
    Datatype: numeric (integer), string, or boolean.
    Default Value
    An optional default value.
    For a numeric metadata extension, the value must be an integer between -2,147,483,647 and 2,147,483,647.
    For a boolean metadata extension, choose true or false.
    For a string metadata extension, you can enter a default value of more than one line, up to 2,147,483,647 bytes.
    Maximum Length
    Maximum length for string metadata extensions. Required for string objects.
    Client Visible
    Specifies whether the metadata extension is visible in PowerCenter.
    Client Editable
    Specifies whether the value of the metadata extension is editable in PowerCenter. If you select this option, the Repository Manager grants Client Visible permission as well.
    Share Read
    Specifies whether the metadata extension is visible in vendor domains.
    Share Write
    Specifies whether the value of the metadata extension is editable across vendor domains. If you enable Share Write permission, the Repository Manager grants Share Read permission as well.
    Private
    Specifies whether the metadata extension is private to the domain in which it is created. The Repository Manager enables this option when third-party application vendors create vendor-defined metadata extensions.
    Description
    Optional description of the metadata extension.
  6. Click Create.

0 COMMENTS

We’d like to hear from you!