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. MX Views Reference
  17. PowerCenter Reports Reference

Repository Guide

Repository Guide

Copying Object Types

Copying Object Types

Consider the relationships between objects in the deployment group and objects in the target repository when you copy the following types of objects:
  • Parts of composite objects.
    When you create a deployment group, you can choose to copy all or part of composite objects. If you choose to deploy part of a composite object, you must ensure that dependent objects exist in the target folder.
  • Local and global shortcuts.
    When you copy a deployment group, you can reestablish local shortcuts to objects in shared folders. The wizard does not allow you to reestablish global shortcuts. As a result, you must ensure that the shared folders and global shortcuts exist in the target repository.
  • Objects with different or conflicting names in the deployment group and target repository.
    An object in the target repository can be a copy of the object in the deployment group but have a different name. In this situation, the wizard replaces the copy of the object with the object in the deployment group.
    An object in the target repository may also have the same name as an object in the deployment group, but may not be a copy of the deployment group object. If this naming conflict occurs, the wizard cannot copy the deployment group object.
  • Objects with different statuses in the deployment group and target repository.
    The status of an object in a deployment group may change after the copy operation, depending on the status of the object before deployment.

0 COMMENTS

We’d like to hear from you!