Table of Contents

Search

  1. Preface
  2. Introduction
  3. Getting Started with Repository Manager
  4. Validating Metadata
  5. Promoting Changes Between Repositories
  6. Importing Design Objects
  7. Exporting Repositories
  8. Common Warehouse Model Support
  9. Design Objects Reference
  10. Change List Reference
  11. MetCommand Reference

Exporting a Repository

Exporting a Repository

To export a repository as a creation change list:
  1. Start the
    Repository Manager
    tool.
  2. Click the
    Export
    tab, if it is not already selected.
  3. Select a repository to export from the drop-down list.
    Repository Manager
    allows you to use a repository only after it has been validated and found to be free of Errors, and FATAL issues.
  4. Click the
    Save
    button.
    Repository Manager
    displays the Export Repository dialog.
  5. Navigate to the target directory where you will save the change list XML file.
  6. Specify the following information about the repository.
    Field
    Description
    Name
    Logical name for this change list file. This value will be stored in the <name> tag of the change list XML file.
    Description
    Description of this change list file. This value will be stored in the <description> tag of the change list XML file.
    File Name
    Name of the change list file to save.
    Repository Manager
    will add an extension to this file (*.change.xml).
  7. Click
    Export
    .
    The
    Repository Manager
    saves the specified change list file, displaying a progress bar while writing to the target location.
  8. You can open the change list XML file in an editor to review its contents.
    The specific name and description, along with a time stamp, file name, and other information, is saved as attributes to the <changelist> element.
    After you have created an export file and before using the file for import or promotion operations, you can edit the file, rename design objects, delete extraneous sections, and make other changes as needed. However, Informatica is not responsible for any consequences resulting from XML files that you have modified in this way.

0 COMMENTS

We’d like to hear from you!