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

Team-Based Development with Versioned Objects Overview

Team-Based Development with Versioned Objects Overview

If you have the team-based development option, you can configure the repository to store multiple versions of objects. You can configure a repository for versioning when you create it, or you can upgrade an existing repository to support versioned objects. With object versioning, you can store copies of previous versions of objects in development, track changes to those objects, and prepare them for deployment to a production environment.
A versioned repository assigns multiple version numbers to versions of the same object. Each time you check in an object, the repository increments the version number by one and stores a new version of the object in the repository database. A repository enabled for versioning can store multiple versions of the following objects:
  • Sources
  • Targets
  • Transformations
  • Mappings
  • Mapplets
  • Sessions
  • Tasks
  • Workflows
  • Worklets
  • User-defined functions
  • Session configurations
  • Schedulers
  • Cubes
  • Dimensions
You can complete the following tasks when you work with a versioned object:
  • View object version properties.
    Each versioned object has a set of version properties and a status. You can also configure the status of a folder to freeze all objects it contains or make them active for editing.
  • Track changes to an object.
    You can view a history that includes all versions of a given object, and compare any version of the object in the history to any other version. With the history, you can determine changes made to an object over time.
  • Check out or check in the versioned object.
    You can check out an object to reserve it while you edit the object. When you check in an object, the repository saves a new version of the object, and you can add comments to the version. You can also find objects checked out by yourself and other users.
  • View multiple versions of an object in the workspace.
    You can view multiple versions of an object in the workspace of the Designer and Workflow Manager.
  • Apply labels to objects
    . You can create labels to associate with any versioned object or group of versioned objects in a repository. Use labels to track versioned objects during development, improve query results, and associate groups of objects for deployment or import and export.
  • Group objects for deployment
    . You can create groups of versioned objects to deploy to another repository or folder. Use the result set from an object query to group objects for deployment. Or, you can create a static group of objects for deployment.
  • Delete or purge the object version.
    You can delete an object from view and continue to store it in the repository. You can recover, or undelete, deleted objects. If you want to permanently remove an object version, you can purge it from the repository.
You can perform these tasks in the Repository Manager, Designer, and Workflow Manager.

0 COMMENTS

We’d like to hear from you!