Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3
  • All Products

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

Repository Manager Guide

Repository Manager Guide

Back Next

Importing Design Objects from a CWM File

Importing Design Objects from a CWM File

This section describes how to import design objects from CWM file in the
Repository Manager
.
Before you import from a CWM file, back up the target repository according to the instructions in Exporting a Repository.
To import from CWM file into a repository, perform the following steps:
  1. In
    Repository Manager
    , click the
    Import from CWM file
     tab.
  2. Load the CWM file for import.
    1. Click the
      Load CWM File
       button.
      The
      Repository Manager
       displays the Open dialog.
    2. Navigate to the
      .cwm
       file that you must import, select the CWM file, and click
      Open
      .
      Repository Manager
       loads and validates the selected CWM file.
    3. Review the loaded source repository, which
      Repository Manager
       displays as a design object hierarchy.
  3. Select design objects to import.
    • To select a design object, click the check box next to the design object.
      When a design object is selected, all associated design objects are automatically selected. For example, if a package is selected, then all tables and queries on which the package is based are automatically selected (checked). Likewise, if a query is removed (unselected), then packages based on that query are also removed. You can individually remove (unselect) any objects that you want to exclude from import.
    • To select all design objects of a particular object type, select the check box next to the object type.
      Repository Manager
       automatically selects all design objects of that type.
    • To select all design objects in the source repository, select the check box next to the repository at the top of the hierarchy.
    In general, consider importing an entire collection of design objects at once, rather than importing subsets separately, so that required design objects are not inadvertently omitted. For example, rather than importing landing tables, staging tables, mappings, and packages separately, consider importing the entire base object so that the collection of dependent design objects is complete.
  4. Import selected design objects.
    1. Click the
      Apply Change List
       button.
      Repository Manager
       displays an Open Repository dialog with a database repository list.
  5. Select the target repository for import.
    1. Select a target repository from the database repository list and click
      OK
      .
    2. Repository Manager
       prompts you to select a rollback strategy in the event of a failure during the import process.
      Select one of the following options:
      Option
      Description
      Full rollback
      Rolls back all of the changes attempted during the import process.
      Rollback to last change
      Rolls back to the last successful change prior to the interruption of the import process. For example, if base object columns A and B were successfully imported, but the import process failed before column C was successfully created in the target repository, then changes are rolled back to column B.
      Use this option if you are importing many design objects and want to retain successfully-applied changes in the event of a failure.
    3. Click
      OK
      .
      If the target repository is currently registered with a proxy user,
      Repository Manager
       prompts you to enter the owner password for the repository.
    4. If prompted to enter the password, enter the password of the ORS schema owner.
      Repository Manager
       displays a progress bar. When the import process is complete,
      Repository Manager
       displays a message indicating whether the import process succeeded.
  6. Save changes in a comparison change list XML file.
    1. Click the
      Save
       button.
      Repository Manager
       displays the Save Change List dialog.
    2. Navigate to the target directory where you need to save the change list XML file.
    3. In the File name field, enter the name of the change list file to be saved.
      Repository Manager
       adds an extension to the file (
      *.change.xml
      ).
    4. Click
      Save
      .
      Repository Manager
       saves the specified
      change.xml
       file, displaying a progress bar while writing to the target location.
You can open the change XML file in an editor to review its contents.
0 COMMENTS
We’d like to hear from you!