P. 1
Repository Guide

Repository Guide

|Views: 47|Likes:
Published by praj761

More info:

Published by: praj761 on Aug 27, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/24/2012

pdf

text

original

Sections

  • Overview
  • Repository Architecture
  • Repository Connectivity
  • Figure 1-1. PowerCenter Repository Connectivity
  • Repository Server Notifications
  • Receiving Notifications in the Designer
  • Receiving Notifications in the Repository Manager
  • Receiving Notifications in the Workflow Manager
  • Receiving Notifications in the Workflow Monitor
  • PowerCenter Server Notifications
  • User-Created Notifications
  • Understanding Metadata
  • Administering Repositories
  • Creating the Repository
  • Creating Folders
  • Security
  • PowerCenter Domains
  • Building the Domain
  • Reusing Metadata
  • Reusing Data
  • Version Control
  • Repository Manager Windows
  • Figure 2-1. Repository Manager Components
  • Progress Indicator
  • Displaying Windows
  • Navigator Window
  • Figure 2-2. Repository Manager Navigator
  • Main Window
  • Sorting and Organizing
  • Figure 2-3. Source Definition Object Properties
  • Table 2-1. Object Details Displayed in Repository Main Window
  • Dependency Window
  • Output Window
  • Figure 2-5. Output Window
  • Adding and Removing a Repository
  • Adding a Repository
  • Removing a Repository
  • Working with Repository Connections
  • Connecting to a Repository
  • Connecting to Multiple Repositories
  • Exporting/Importing Repository Connection Information
  • Searching for Repository Objects
  • Performing Keyword Searches
  • Searching All Repository Objects
  • Viewing Object Dependencies
  • Table 2-2. Viewing Object Dependencies
  • Figure 2-6. Dependencies Dialog Box
  • Table 2-3. Dependencies Options
  • Figure 2-7. View Dependencies Window
  • Table 2-4. Object Properties for View Dependencies Window
  • Validating Multiple Objects
  • Figure 2-9. Validate Objects Results
  • Table 2-5. Validate Objects Properties
  • Comparing Repository Objects
  • Truncating Workflow and Session Log Entries
  • Permissions and Privileges
  • Repository Code Pages
  • Navigating the Administration Console
  • Console Tree
  • Figure 3-1. Administration Console
  • Repository Server Name Node Details
  • Table 3-1. Repository Servers Node Details
  • Table 3-2. Repositories Node Details
  • Figure 3-2. Repository Details
  • Table 3-3. Repository Details
  • Table 3-4. HTML Links for Performing Repository Tasks
  • Registering and Connecting to the Repository Server
  • Registering a Repository Server
  • Connecting to the Repository Server
  • Disconnecting from the Repository Server
  • Tuning Repository Performance
  • Updating Repository Statistics
  • Increasing Repository Copy, Backup, and Restore Performance
  • Copying a Repository
  • Deleting a Repository
  • Backing Up and Restoring a Repository
  • Backing Up a Repository
  • Restoring a Repository
  • Starting and Stopping the Repository
  • 5.Start the repository
  • Enabling the Repository
  • Starting the Repository
  • Stopping the Repository
  • Disabling the Repository
  • Sending Repository Notifications
  • Registering a PowerCenter Repository
  • Migrating the Repository to a Different Repository Server
  • Propagating Repository Domain Connection Information
  • Viewing User Connections and Locks
  • Viewing User Connections
  • Table 3-5. Repository User Connection Details
  • Viewing Locks
  • Table 3-6. Object Lock Properties
  • Closing User Connections and Locks
  • Closing Connections in the Repository Manager
  • Closing Connections in the Administration Console
  • Registering and Unregistering Repository Plug-ins
  • Registering a Repository Plug-in
  • Unregistering a Repository Plug-in
  • Registering and Unregistering LDAP Security Modules
  • Registering an LDAP Security Module
  • Table 3-7. Register Security Module Options
  • Table 3-8. LDAP Server Configuration Options
  • Table 3-9. LDAP Login Properties Options
  • Unregistering an LDAP Security Module
  • Table 3-10. LDAP Login Properties Options
  • Reading the Repository Log Files
  • Log File Codes
  • Process Identification
  • Table 3-11. Repository Log Codes
  • Repository Server Log
  • Repository Agent Log File
  • Figure 3-4. Event Viewer Application Log Message
  • Figure 3-5. Application Log Message Detail
  • Adding a Repository Configuration
  • Table 4-1. New Repository - General Tab
  • Table 4-2. New Repository - Database Connection Tab
  • Table 4-3. New Repository - Network Tab
  • Table 4-4. New Repository - Configuration Tab
  • Editing a Repository Configuration
  • 3.Edit the repository configuration
  • Removing a Repository Configuration
  • Exporting and Importing Repository Configurations
  • Exporting a Repository Configuration
  • Importing a Repository Configuration
  • Creating or Promoting a Repository
  • Creating a Repository
  • Promoting a PowerCenter Repository
  • Enabling Version Control
  • Working with PowerCenter Licenses
  • License Key Types
  • License Key Repository Types
  • License File Types
  • Table 4-5. Converting Special Characters in Repository License File Names
  • Managing License Files
  • Table 4-6. License File Compatibility Requirements
  • Rules and Guidelines
  • User Groups
  • Default Groups
  • User Groups and Folder Permissions
  • Creating a User Group
  • Editing a User Group
  • Deleting a User Group
  • User Authentication
  • Using Default Authentication
  • Using LDAP Authentication
  • Figure 5-1. Repository User Names and External Login Names
  • Switching Between Default and External User Authentication
  • Creating and Editing Repository Users
  • Editing a User Password
  • Creating a Repository User Under an External Directory Service
  • Editing a User
  • Enabling a User
  • Disabling a User
  • Removing a Repository User
  • Repository Privileges
  • Default Privileges
  • Table 5-1. Default Repository Privileges
  • Extended Privileges
  • Table 5-2. Extended Repository Privileges
  • Assigning and Revoking a Privilege
  • Permissions
  • Configuring Folder Permissions
  • Table 5-3. Folder Object Security Levels
  • Configuring Versioning Object Permissions
  • Table 5-4. Versioning Object Security Levels
  • Managing User Connections
  • Table 5-5. Repository Connection Properties
  • Handling User Connections
  • Creating an Audit Trail
  • Repository Locks
  • Locking the Same Object
  • Table 5-6. Repository Locks
  • Locking Within Objects
  • Locking with Cubes and Dimensions
  • Locking Business Components
  • Handling Locks
  • Table 5-7. Object Lock Properties
  • Releasing Locks
  • Tips
  • Troubleshooting
  • Using Folders in the Repository Manager
  • Using Folders in the Designer
  • Using Folders in the Workflow Manager
  • Organizing Folders
  • Folder Properties
  • Folder Owner and Owner's Group
  • Shared Folders
  • Table 6-1. Folder Permissions
  • Configuring a Folder
  • Creating a Folder
  • Editing a Folder
  • Deleting a Folder
  • Comparing Folders
  • Compared Attributes and Object Differentiation
  • Table 6-2. Compared Object Types and Attributes
  • Table 6-3. Compared Objects in Compare
  • One-Way and Two-Way Comparisons
  • Editing and Saving Results Files
  • Steps for Comparing Folders
  • Figure 6-1. One-Way and Two-Way Comparisons
  • Shortcuts Versus Copies
  • Understanding Shortcut Properties
  • Default Shortcut Name
  • Describing the Object and the Shortcut
  • Locating the Referenced Object
  • Figure 7-1. Object and Shortcut Description
  • Figure 7-2. Referenced Shortcut Object
  • Creating a Local Shortcut
  • Figure 7-3. Transformation Shortcut Icon
  • Creating a Global Shortcut
  • Figure 7-4. Create a Global Shortcut
  • Configuring the Global Shortcut Environment
  • Working with Shortcuts
  • Refreshing Shortcut Properties
  • Copying a Shortcut
  • Renaming Source Qualifiers to Shortcut Sources
  • Table 7-1. Copying Global or Local Shortcuts
  • Working with Versioned Objects
  • Sample Scenario
  • Viewing Results View Windows
  • Figure 8-1. Results View Windows List
  • Working with Version Properties
  • Viewing Version Properties
  • Object Properties
  • Version Properties
  • Figure 8-2. Object Properties
  • Figure 8-3. Version Properties
  • Labels Properties
  • Object Status Properties
  • Figure 8-4. Labels Properties
  • Changing Object Status
  • Figure 8-5. Object Status Properties
  • Changing Folder Status
  • Tracking Changes to Versioned Objects
  • Viewing Object History
  • Figure 8-6. View History Window
  • Table 8-1. Tasks Available in View History Window
  • Comparing Versions
  • Checking Out and Checking In Objects
  • Checking Out Objects
  • Viewing Checked Out Objects
  • Table 8-2. Tasks Available in View Checkouts Window
  • Undoing a Checkout
  • Checking In Objects
  • Deleting and Purging Versioned Objects
  • Deleting a Versioned Object
  • Recovering a Deleted Object
  • Purging a Version
  • Working with Labels
  • Creating and Editing Labels
  • Figure 9-1. Label Browser
  • Figure 9-2. Label Editor Options
  • Applying Labels
  • Figure 9-3. Apply Label Dialog Box
  • Table 9-1. Label Options and Description
  • Figure 9-4. Apply Label Wizard
  • Working with Object Queries
  • Figure 9-5. Query Browser
  • Configuring Query Conditions
  • Figure 9-6. Query Editor
  • Table 9-2. Query Parameters and Values
  • Validating and Saving a Query
  • Running a Query
  • Figure 9-8. Sample Query Results
  • Table 9-3. Tasks Available in Query Results Window
  • Viewing Query Results
  • Sample Queries
  • Working with Deployment Groups
  • Figure 9-9. Deployment Group Browser
  • Creating and Editing a Deployment Group
  • Viewing Deployment History
  • Figure 9-10. Deployment Group Editor
  • Rolling Back a Deployment
  • Figure 9-11. Deployment Group History
  • Working with Static Deployment Groups
  • Figure 9-12. Dependency for Deployment Group Dialog Box
  • Working with Dynamic Deployment Groups
  • PowerCenter Server Processing
  • Using the Copy Wizards
  • Copy Modes
  • Registered PowerCenter Servers
  • Connections
  • Copying Plug-in Application Information
  • Copying or Replacing a Folder
  • Naming
  • Locking and Checkouts
  • Shortcuts
  • Copying Within a Repository
  • Copying From Local Repositories
  • Steps for Copying or Replacing a Folder
  • Table 10-1. Copy Folder Wizard Prompts (Copying a Folder)
  • Copying a Deployment Group
  • Copying Composite Objects
  • Copying Shortcuts
  • Object Naming
  • Object Status
  • Steps for Copying a Deployment Group
  • Table 10-2. Change In Object Status After Copying Deployment Group Objects
  • Table 10-3. Copy Deployment Group Wizard Prompts
  • Working with Objects and Object Types
  • Working with Different Repository Versions
  • Code Pages
  • Table 11-1. Exporting and Importing Objects Permissions and Privileges
  • The XML and DTD Files
  • CRCVALUE Codes
  • Figure 11-1. CRCVALUE Code in an Exported XML File
  • Exporting and Importing Multiple Objects and Object Types
  • Table 11-2. Options for Exporting and Importing Multiple Objects
  • Working with Dependent Objects
  • Table 11-3. Dependent Objects Exported
  • Exporting and Importing Parent Objects
  • Figure 11-2. Export Options Dialog Box
  • Table 11-4. Options for Exporting Objects
  • Working with Object Versions
  • Shortcut Types
  • Importing Shortcuts to Sources
  • Exporting Objects
  • Modifying an Exported XML File
  • Modifiable Objects
  • Table 11-5. Modifiable Repository Objects
  • Importing Objects
  • Validating XML Files Against the DTD
  • Validating Objects
  • Resolving Object Conflicts
  • Figure 11-3. Import Wizard - Resolve General Object Conflicts
  • Table 11-6. Resolving General Conflicts During Import
  • Figure 11-5. Conflict Resolution Wizard
  • Steps for Exporting Objects
  • Steps for Importing Objects
  • Figure 12-1. The Copy Wizard
  • Table 12-1. Copy Wizard Areas
  • Resolving Copy Conflicts
  • Table 12-2. Copy Wizard Resolutions
  • Figure 12-2. Copy Wizard Resolutions
  • Steps for Copying Objects
  • Figure 12-3. Copy Wizard Mapping Conflicts
  • Copying Workflow Manager Objects
  • Copying Workflows and Worklets
  • Copying Sessions
  • Database Connection Conflicts
  • Mapping Variables
  • Copying Workflow Segments
  • Copying Designer Objects
  • Copying Mapping and Mapplets Segments
  • Steps for Exporting Metadata
  • Steps for Importing Metadata
  • Table 13-1. Metadata Import Wizard - PowerCenter Options
  • Working with Metadata Extensions
  • Creating Reusable Metadata Extensions
  • Table 14-1. Options for Creating Reusable Metadata Extensions
  • Editing Reusable Metadata Extensions
  • Deleting Reusable Metadata Extensions
  • Viewing the Repository Metadata
  • MX View Categories
  • Table 15-1. MX View Categories
  • Using PowerCenter Metadata Reporter
  • SQL Definition of Views
  • Table 15-2. SQL Script to Create MX Views
  • Table 15-3. SQL Script to Drop MX Views
  • Integrating MX Views with Third-Party Software
  • Database Definition View
  • REP_DATABASE_DEFS
  • Table 15-4. REP_DATABASE_DEFS MX View
  • Source Views
  • REP_ALL_SOURCES
  • Table 15-5. Source Views
  • Table 15-6. REP_ALL_SOURCES MX View
  • REP_ALL_SOURCE_FLDS
  • Table 15-7. REP_ALL_SOURCE_FLDS MX View
  • REP_SRC_FILES
  • Table 15-8. REP_SRC_FILES MX View
  • REP_SRC_TBLS
  • Table 15-9. REP_SRC_TBLS MX View
  • REP_SRC_FILE_FLDS and REP_SEG_FLDS
  • Table 15-10. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views
  • REP_SRC_TBL_FLDS
  • Table 15-11. REP_SRC_TBL_FLDS MX Views
  • Target Views
  • REP_ALL_TARGETS
  • Table 15-12. Target Views
  • Table 15-13. REP_ALL_TARGETS MX View
  • REP_ALL_TARGET_FIELDS
  • Table 15-14. REP_ALL_TARGET_FIELDS MX View
  • REP_TARG_TBLS
  • REP_TARG_TBL_COLS
  • Table 15-15. REP_TARG_TBLS MX View
  • Table 15-16. REP_TARG_TBL_COLS MX View
  • Mapping and Mapplet Views
  • Table 15-17. Mapping and Mapplet Views
  • REP_ALL_MAPPINGS
  • Table 15-18. REP_ALL_MAPPINGS MX View
  • REP_ALL_MAPPLETS
  • Table 15-19. REP_ALL_MAPPLETS MX View
  • REP_TARG_MAPPING
  • Table 15-20. REP_TARG_MAPPING MX View
  • REP_TARG_FLD_MAP
  • Table 15-21. REP_TARG_FLD_MAP MX View
  • REP_FLD_MAPPING
  • Table 15-22. REP_FLD_MAPPING MX View
  • REP_SRC_MAPPING
  • REP_SRC_FLD_MAP
  • Table 15-23. REP_SRC_MAPPING MX View
  • Table 15-24. Mapping Source Fields
  • REP_TBL_MAPPING
  • Table 15-25. REP_TBL_MAPPING MX View
  • REP_TARG_TBL_JOINS
  • Table 15-26. REP_TARG_TBL_JOINS MX View
  • REP_MAPPING_UNCONN_PORTS
  • Table 15-27. REP_MAPPING_UNCONN_PORTS MX View
  • REP_MAPPING_PORT_CONN
  • Table 15-28. REP_MAPPING_PORT_CONN MX View
  • Metadata Extension Views
  • REP_METADATA_EXTNS
  • Table 15-29. Metadata Extension Views
  • Table 15-30. REP_METADATA_EXTNS MX View
  • REP_METADATA_EXTN_DEFINES
  • Table 15-31. REP_METADATA_EXTN_DEFINES MX View
  • Transformation Views
  • REP_ALL_TRANSFORMS
  • Table 15-32. Transformation Views
  • Table 15-33. REP_ALL_TRANSFORMS MX View
  • REP_WIDGET_INST
  • REP_WIDGET_DEP
  • Table 15-34. REP_WIDGET_INST MX View
  • Table 15-35. REP_WIDGET_DEP MX View
  • REP_WIDGET_ATTR
  • REP_WIDGET_FIELD
  • Table 15-36. REP_EIDGET_ATTR MX View
  • Table 15-37. REP_WIDGET_FIELD MX View
  • Workflow, Worklet, and Task Views
  • REP_WORKFLOWS
  • Table 15-39. REP_WORKFLOWS MX View
  • REP_ALL_TASKS
  • REP_ALL_SCHEDULERS
  • Table 15-40. REP_ALL_TASKS MX View
  • Table 15-41. REP_ALL_SCHEDULERS MX View
  • REP_WFLOW_VAR
  • Table 15-42. REP_WFLOW_VAR MX View
  • REP_EVENT
  • Table 15-43. REP_EVENT MX View
  • REP_TASK_INST
  • REP_WORKFLOW_DEP
  • Table 15-44. REP_TASK_INST MX View
  • Table 15-45. REP_WORKFLOW_DEP MX View
  • REP_TASK_INST_RUN
  • Table 15-46. REP_TASK_INST_RUN MX View
  • REP_WFLOW_RUN
  • Table 15-47. REP_WFLOW_RUN MX View
  • REP_LOAD_SESSIONS
  • Table 15-48. REP_LOAD_SESSIONS MX View
  • REP_SESSION_CNXS
  • REP_SESSION_INSTANCES
  • Table 15-49. REP_SESSION_CNXS MX View
  • REP_SESSION_FILES
  • Table 15-50. REP_SESSION_INSTANCES MX View
  • Table 15-51. REP_SESSION_FILES MX View
  • REP_SESSION_INSTANCE_FILES
  • REP_SESS_WIDGET_CNXS
  • Table 15-52. REP_SESSION_INSTANCE_FILES MX View
  • Table 15-53. REP_SESS_WIDGET_CNXS MX View
  • REP_COMPONENT
  • Table 15-54. REP_COMPONENT MX View
  • REP_SESS_PARTITION_DEF
  • REP_SESS_CONFIG_PARM
  • Table 15-55. REP_SESS_PARTITION_DEF MX View
  • Table 15-56. REP_SESS_CONFIG_PARM MX View
  • REP_TASK_ATTR
  • Table 15-57. REP_TASK_ATTR MX View
  • REP_SESS_LOG
  • Table 15-58. REP_SESS_LOG MX View
  • REP_SESS_TBL_LOG
  • Table 15-59. REP_SESS_TBL_LOG MX View
  • Security Views
  • REP_USERS
  • Table 15-60. Security Views
  • Table 15-61. REP_USERS MX View
  • REP_USER_GROUPS
  • REP_GROUPS
  • Table 15-62. REP_USER_GROUPS MX View
  • Table 15-63. REP_GROUPS MX View
  • Deployment Views
  • REP_DEPLOY_GROUP
  • Table 15-64. Deployment Views
  • Table 15-65. REP_DEPLOY_GROUP MX View
  • REP_DEPLOY_GROUP_DETAIL
  • Table 15-66. REP_DEPLOY_GROUP_DETAIL MX View
  • Repository View
  • REP_REPOSIT_INFO
  • Table 15-67. REP_REPOSIT_INFO MX View
  • PowerCenter Server Views
  • REP_SERVER_INFO
  • Table 15-68. PowerCenter Server Views
  • Table 15-69. REP_SERVER_INFO MX View
  • REP_SERVER_NET
  • REP_SERVER_NET_REF
  • Table 15-70. REP_SERVER_NET MX View
  • Table 15-71. REP_SERVER_NET_REF MX View
  • Change Management Views
  • REP_VERSION_PROPS
  • Table 15-72. Change Management Views
  • Table 15-73. REP_VERSION_PROPS MX View
  • REP_CM_LABEL
  • REP_CM_LABEL_REF
  • Table 15-74. REP_CM_LABEL MX View
  • Table 15-75. REP_CM_LABEL_REF MX View
  • Folder View
  • REP_SUBJECT
  • Table 15-76. REP_SUBJECT MX View
  • Using pmrep
  • Using pmrepagent
  • Using Native Connect Strings
  • Table 16-1. Native Connect String Syntax
  • Running Commands
  • Running Commands in Command Line Mode
  • Running Commands in Interactive Mode
  • Specifying Options and Arguments
  • Using Password Environment Variables
  • Configuring Repository Passwords on UNIX
  • Configuring Repository Passwords on Windows
  • pmrep System Commands
  • Connecting to a Repository (Connect)
  • Table 16-2. pmrep System Commands
  • Table 16-3. Connect Options and Arguments (pmrep)
  • Getting Help (Help)
  • Cleaning up Persistent Resources (Cleanup)
  • Exiting pmrep (Exit)
  • pmrep Repository Commands
  • Table 16-4. pmrep Repository Commands
  • Adding a Server (Addserver)
  • Adding Repository Configurations (Addrepository)
  • Table 16-5. Addserver Options and Arguments (pmrep)
  • Table 16-6. Addrepository Options and Arguments (pmrep)
  • Backing up a Repository (Backup)
  • Table 16-7. Backup Options and Arguments (pmrep)
  • Creating a Relational Connection (CreateConnection)
  • Table 16-8. CreateConnection Options and Arguments (pmrep)
  • Table 16-9. Database Type Strings
  • Table 16-10. Code Page ID by Name (pmrep)
  • Deleting a Connection (Deleteconnection)
  • Deleting a Server (Deleteserver)
  • Disabling a Repository (Disablerepository)
  • Table 16-11. Deleteconnection Options and Arguments (pmrep)
  • Table 16-12. Deleteserver Options and Arguments (pmrep)
  • Enabling a Repository (Enablerepository)
  • Table 16-13. Disablerepository Options and Arguments (pmrep)
  • Table 16-14. Enablerepository Options and Arguments (pmrep)
  • Listing Repository Objects (ListObjects)
  • Table 16-15. ListObjects Options and Arguments (pmrep)
  • Table 16-16. Transformation and Task Types to Use with pmrep
  • Listing Tables by Session (Listtablesbysess)
  • Table 16-17. Listtablesbysess Options and Arguments (pmrep)
  • Listing Object Dependencies (ListObjectDependencies)
  • Table 16-18. ListObjectDependencies Options and Arguments (pmrep)
  • Sending Notification Messages (Notify)
  • Table 16-19. Notify Options and Arguments (pmrep)
  • Exporting Objects (ObjectExport)
  • Importing Objects (ObjectImport)
  • Table 16-20. ObjectExport Options and Arguments (pmrep)
  • Registering Local Repositories (Register)
  • Table 16-21. ObjectImport Options and Arguments (pmrep)
  • Table 16-22. Register Options and Arguments (pmrep)
  • Removing Repositories From the Cache (Removerepository)
  • Table 16-23. Removerepository Options and Arguments (pmrep)
  • Running Script Files (Run)
  • Table 16-24. Run Options and Arguments (pmrep)
  • Showing Connection Information (ShowConnectioninfo)
  • Stopping a Repository (StopRepository)
  • Changing the Connection Name (SwitchConnection)
  • Table 16-25. StopRepository Option and Argument (pmrep)
  • Truncating Workflow and Session Logs (Truncatelog)
  • Table 16-26. SwitchConnection Options and Arguments (pmrep)
  • Table 16-27. Truncatelog Options and Arguments (pmrep)
  • Unregistering Local Repositories (Unregister)
  • Table 16-28. Unregister Options and Arguments (pmrep)
  • Updating a Database Connection (UpdateConnection)
  • Updating the Notification Email Addresses (Updateemailaddr)
  • Table 16-29. UpdateConnection Options and Arguments (pmrep)
  • Updating Server Details (Updateserver)
  • Table 16-30. Updateemailaddr Options and Arguments (pmrep)
  • Table 16-31. Updateserver Options and Arguments (pmrep)
  • Updating Sequence Generator Transformations (Updateseqgenvals)
  • Table 16-32. Updateseqgenvals Options and Arguments (pmrep)
  • Updating the Source Table Owner Name (Updatesrcprefix)
  • Updating Server Variables (Updatesrvvar)
  • Table 16-33. Updatesrcprefix Options and Arguments (pmrep)
  • Updating Repository Statistics (UpdateStatistics)
  • Updating the Target Table Name Prefix (Updatetargprefix)
  • Table 16-34. Updatesrvvar Options and Arguments (pmrep)
  • Table 16-35. Updatestatistics Options and Arguments (pmrep)
  • Table 16-36. Updatetargprefix Options and Arguments (pmrep)
  • pmrep Security Commands
  • Table 16-37. pmrep Security Commands
  • Adding a Privilege (Addprivilege)
  • Adding a User to a Group (Addusertogroup)
  • Changing the Repository Password (Changepasswd)
  • Table 16-38. Addprivilege Options and Arguments (pmrep)
  • Table 16-39. Addusertogroup Options and Arguments (pmrep)
  • Creating a Folder (CreateFolder)
  • Table 16-40. Changepasswd Options and Arguments (pmrep)
  • Table 16-41. CreateFolder Options and Arguments (pmrep)
  • Creating a Group (Creategroup)
  • Creating a User (Createuser)
  • Table 16-42. Creategroup Options and Arguments (pmrep)
  • Deleting a Folder (DeleteFolder)
  • Table 16-43. Createuser Options and Arguments (pmrep)
  • Table 16-44. DeleteFolder Options and Arguments (pmrep)
  • Editing a User (Edituser)
  • Table 16-45. Edituser Options and Arguments (pmrep)
  • Listing All Groups (Listallgroups)
  • Listing All Privileges (Listallprivileges)
  • Listing All Users (Listallusers)
  • Modify Folder Properties (ModifyFolder)
  • Table 16-46. ModifyFolder Option and Argument (pmrep)
  • Registering a User (Registeruser)
  • Removing a Group (Rmgroup)
  • Table 16-47. Registeruser Option and Argument (pmrep)
  • Removing a Privilege (Rmprivilege)
  • Removing a User (Rmuser)
  • Table 16-48. Rmgroup Option and Argument (pmrep)
  • Table 16-49. Rmprivilege Options and Arguments (pmrep)
  • Removing a User from a Group (Rmuserfromgroup)
  • Table 16-50. Rmuser Option and Argument (pmrep)
  • Table 16-51. Rmuserfromgroup Options and Arguments (pmrep)
  • pmrep Change Management Commands
  • Table 16-52. pmrep Change Management Commands
  • Adding to a Deployment Group (AddToDeploymentGroup)
  • Table 16-53. AddToDeploymentGroup Options and Arguments (pmrep)
  • Labeling (ApplyLabel)
  • Table 16-54. ApplyLabel Options and Arguments (pmrep)
  • Checking In Objects (Checkin)
  • Table 16-55. Checkin Options and Arguments (pmrep)
  • Clearing a Deployment Group (ClearDeploymentGroup)
  • Creating a Deployment Group (CreateDeploymentGroup)
  • Table 16-56. ClearDeploymentGroup Options and Arguments (pmrep)
  • Table 16-57. CreateDeploymentGroup Options and Arguments (pmrep)
  • Creating a Label (CreateLabel)
  • Deleting a Deployment Group (DeleteDeploymentGroup)
  • Table 16-58. CreateLabel Options and Arguments (pmrep)
  • Deleting a Label (DeleteLabel)
  • Deploying a Deployment Group (DeployDeploymentGroup)
  • Table 16-59. DeleteDeploymentGroup Options and Arguments (pmrep)
  • Table 16-60. DeleteLabel Options and Arguments (pmrep)
  • Table 16-61. DeployDeploymentGroup Options and Arguments (pmrep)
  • Deploying a Folder (DeployFolder)
  • Table 16-62. DeployFolder Options and Arguments (pmrep)
  • Executing a Query (ExecuteQuery)
  • Table 16-63. ExecuteQuery Options and Arguments (pmrep)
  • Listing Checked Out Items (FindCheckout)
  • Table 16-64. FindCheckout Options and Arguments (pmrep)
  • Undoing a Checkout (UndoCheckout)
  • Validating Objects (Validate)
  • Table 16-65. UndoCheckout Options and Arguments (pmrep)
  • Table 16-66. Validate Options and Arguments (pmrep)
  • pmrepagent Commands
  • Table 16-67. pmrepagent Commands
  • Backup Backs up a repository. See “Backing up a Repository (Backup)” on page477
  • Table 16-68. Backup Options and Arguments (pmrepagent)
  • Restoring Teradata Repositories using Fastload (Bulkrestore)
  • Table 16-69. Bulkrestore Options and Arguments (pmrepagent)
  • Creating a Repository (Create)
  • Table 16-70. Create Options and Arguments (pmrepagent)
  • Deleting a Repository (Delete)
  • Table 16-71. Delete Options and Arguments (pmrepagent)
  • Registering a Plug-in (Registerplugin)
  • Table 16-72. Registerplugin Options and Arguments (pmrepagent)
  • Restoring a Repository (Restore)
  • Table 16-73. Restore Options and Arguments (pmrepagent)
  • Unregistering Plug-ins (Unregisterplugin)
  • Table 16-74. Unregisterplugin Options and Arguments (pmrepagent)
  • Upgrading a Repository (Upgrade)
  • Table 16-75. Upgrade Options and Arguments (pmrepagent)
  • Scripting pmrep and pmrepagent Commands
  • Using the Persistent Input File
  • Creating a Persistent Input File with pmrep
  • Creating a Persistent Input File Manually
  • Using the Object Import Control File
  • Object Import Control File Parameters
  • Table A-1. Object Import Control File Elements and Attributes (pmrep)
  • Example
  • Sample Import XML File
  • Using the Deployment Control File
  • Deployment Control File Parameters
  • Table A-2. Deployment Control File Elements and Attributes (pmrep)
  • Designer Tasks
  • Table B-1. Required Privileges and Permissions for Designer Tasks
  • Workflow Manager Tasks
  • Table B-2. Required Privileges and Permissions for Workflow Manager Tasks
  • Workflow Monitor Tasks
  • Table B-3. Required Privileges and Permissions for Workflow Monitor Tasks
  • Table B-4. Required Privileges and Permissions for pmcmd Tasks
  • Repository Manager Tasks
  • Table B-5. Required Permissions and Privileges for Repository Manager Tasks
  • Table B-6. Required Permissions and Privileges for pmrep Tasks

Repository Guide

Informatica PowerCenter®
(Version 7.1.1)

Informatica PowerCenter Repository Guide Version 7.1.1 August 2004 Copyright (c) 1998–2004 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free. Informatica, PowerMart, PowerCenter, PowerChannel, PowerCenter Connect, MX, and SuperGlue are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software are copyrighted by DataDirect Technologies, 1999-2002. Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved. Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2004 The Apache Software Foundation. All rights reserved. DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi PowerCenter 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . xxxviii Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix

Chapter 1: Understanding the Repository . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Repository Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Repository Manager . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Workflow Manager . . . . . . . . . . . . . . . . . . 7 Receiving Notifications in the Workflow Monitor . . . . . . . . . . . . . . . . . . 7 PowerCenter Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 User-Created Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Understanding Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Administering Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

i

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerCenter Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Building the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2: Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . 19
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Displaying Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Adding and Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Working with Repository Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to Multiple Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Exporting/Importing Repository Connection Information . . . . . . . . . . . 32 Searching for Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Performing Keyword Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Searching All Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Validating Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Comparing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Truncating Workflow and Session Log Entries . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3: Managing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Repository Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Navigating the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

ii

Table of Contents

Console Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Registering and Connecting to the Repository Server . . . . . . . . . . . . . . . . . . 58 Registering a Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Connecting to the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Disconnecting from the Repository Server . . . . . . . . . . . . . . . . . . . . . . 59 Tuning Repository Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Updating Repository Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Increasing Repository Copy, Backup, and Restore Performance . . . . . . . 60 Copying a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Deleting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Backing Up and Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Backing Up a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Starting and Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Enabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Starting the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Disabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Sending Repository Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Registering a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Migrating the Repository to a Different Repository Server . . . . . . . . . . . . . . 77 Propagating Repository Domain Connection Information . . . . . . . . . . . . . . 78 Viewing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Closing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Repository Manager . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Administration Console . . . . . . . . . . . . . . . 84 Registering and Unregistering Repository Plug-ins . . . . . . . . . . . . . . . . . . . 85 Registering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Unregistering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Registering and Unregistering LDAP Security Modules . . . . . . . . . . . . . . . . 88 Registering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . . . 88 Unregistering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . 95 Reading the Repository Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Log File Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Process Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table of Contents iii

Repository Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Repository Agent Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 4: Configuring the Repository . . . . . . . . . . . . . . . . . . . . . . 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Adding a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Editing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Removing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Exporting and Importing Repository Configurations . . . . . . . . . . . . . . . . . 115 Exporting a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Importing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating or Promoting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Promoting a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . 117 Enabling Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Working with PowerCenter Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Repository Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Managing License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 5: Repository Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Default Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 User Groups and Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Creating a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Editing a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using Default Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Switching Between Default and External User Authentication . . . . . . . 133 Creating and Editing Repository Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Editing a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Creating a Repository User Under an External Directory Service . . . . . 137

iv

Table of Contents

Editing a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Removing a Repository User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Default Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Extended Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Assigning and Revoking a Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Versioning Object Permissions . . . . . . . . . . . . . . . . . . . . 149 Managing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Handling User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Creating an Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Repository Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking the Same Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking Within Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking with Cubes and Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking Business Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Handling Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Releasing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 6: Working with Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . 166 Organizing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Folder Owner and Owner's Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Shared Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configuring a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table of Contents

v

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Editing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Compared Attributes and Object Differentiation . . . . . . . . . . . . . . . . . 174 One-Way and Two-Way Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 176 Editing and Saving Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Steps for Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 7: Local and Global Shortcuts . . . . . . . . . . . . . . . . . . . . . . 181
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Shortcuts Versus Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Understanding Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Default Shortcut Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Describing the Object and the Shortcut . . . . . . . . . . . . . . . . . . . . . . . 184 Locating the Referenced Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Creating a Local Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Creating a Global Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring the Global Shortcut Environment . . . . . . . . . . . . . . . . . . 192 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Refreshing Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Copying a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Renaming Source Qualifiers to Shortcut Sources . . . . . . . . . . . . . . . . . 196 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Chapter 8: Working with Versioned Objects . . . . . . . . . . . . . . . . . . 199
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Viewing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Working with Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Viewing Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Object Status Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Changing Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

vi

Table of Contents

Changing Folder Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Tracking Changes to Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Viewing Object History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Comparing Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Checking Out and Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Checking Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Viewing Checked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Undoing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Deleting and Purging Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Deleting a Versioned Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Recovering a Deleted Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Purging a Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 9: Grouping Versioned Objects . . . . . . . . . . . . . . . . . . . . . 217
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Working with Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Creating and Editing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Applying Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Working with Object Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Configuring Query Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Validating and Saving a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Running a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Viewing Query Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Working with Deployment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Creating and Editing a Deployment Group . . . . . . . . . . . . . . . . . . . . . 237 Viewing Deployment History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Rolling Back a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Working with Static Deployment Groups . . . . . . . . . . . . . . . . . . . . . . 239 Working with Dynamic Deployment Groups . . . . . . . . . . . . . . . . . . . 240

Chapter 10: Copying Folders and Deployment Groups . . . . . . . . . . 241
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 PowerCenter Server Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Using the Copy Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Copy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Table of Contents

vii

Registered PowerCenter Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Copying Plug-in Application Information . . . . . . . . . . . . . . . . . . . . . . 247 Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Copying Within a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Copying From Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Steps for Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . 250 Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Copying Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Copying Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Steps for Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 11: Exporting and Importing Objects . . . . . . . . . . . . . . . . . 263
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Working with Objects and Object Types . . . . . . . . . . . . . . . . . . . . . . . 265 Working with Different Repository Versions . . . . . . . . . . . . . . . . . . . . 265 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 The XML and DTD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 CRCVALUE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Exporting and Importing Multiple Objects and Object Types . . . . . . . . . . . 269 Working with Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Exporting and Importing Parent Objects . . . . . . . . . . . . . . . . . . . . . . . 271 Working with Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Shortcut Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Importing Shortcuts to Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Modifying an Exported XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Modifiable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

viii

Table of Contents

Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Validating XML Files Against the DTD . . . . . . . . . . . . . . . . . . . . . . . 280 Validating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Resolving Object Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Steps for Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Steps for Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Chapter 12: Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Resolving Copy Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Steps for Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Copying Workflow Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflows and Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflow Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Copying Designer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Copying Mapping and Mapplets Segments . . . . . . . . . . . . . . . . . . . . . 310

Chapter 13: Exchanging Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Steps for Exporting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Steps for Importing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Chapter 14: Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Creating Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Editing Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Deleting Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Chapter 15: Using Metadata Exchange (MX) Views . . . . . . . . . . . . . 333
Viewing the Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Using PowerCenter Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . 335
Table of Contents ix

. . . 368 REP_WIDGET_DEP . . . . . 371 x Table of Contents . . . . . . . . . . . . . . . . . 359 REP_SRC_FLD_MAP . . . . . . . . . . . . . . . . . . . . 339 REP_ALL_SOURCE_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Transformation Views . . . . . . . 347 REP_ALL_TARGET_FIELDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 REP_WIDGET_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 REP_WIDGET_INST . . . . . . . . . . . . . . . . . . 364 REP_METADATA_EXTNS . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Integrating MX Views with Third-Party Software . . . . . . . . . . . . . . . . . . . . 344 REP_SRC_FILE_FLDS and REP_SEG_FLDS . . 356 REP_TARG_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 REP_TARG_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Target Views . . . . . . . . . . . . . Worklet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 REP_SRC_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Workflow. . . . . . . . . . . . . . . 345 REP_SRC_TBL_FLDS . . . . . . . . . . . . . . . . . . . . 359 REP_TBL_MAPPING . . . . . . . . . . 347 REP_ALL_TARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Database Definition View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 REP_ALL_MAPPINGS . . . . . 366 REP_ALL_TRANSFORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 REP_MAPPING_UNCONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 REP_SRC_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 REP_FLD_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . 341 REP_SRC_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 REP_ALL_SOURCES . . . . and Task Views . . . 369 REP_WIDGET_FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_TARG_TBL_COLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 REP_TARG_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 REP_ALL_MAPPLETS . . . . . . 364 REP_METADATA_EXTN_DEFINES . . . . . . . . . . . . . 338 REP_DATABASE_DEFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .SQL Definition of Views . . . . 362 REP_MAPPING_PORT_CONN . . . . . . . . . . . . . . . . 360 REP_TARG_TBL_JOINS . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 REP_VERSION_PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 REP_ALL_SCHEDULERS . . . . . . . . . . 390 REP_USER_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 REP_SESS_CONFIG_PARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 REP_REPOSIT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 REP_USERS . . . . . . . . . . . . . . 381 REP_SESSION_FILES . . . . . . . . . . . . . . . . . . . . . . . . 383 REP_SESS_WIDGET_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 REP_TASK_INST . 396 REP_SERVER_INFO . . . . . . . . . . . . . . . . 382 REP_SESSION_INSTANCE_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Change Management Views . . . . . . . . . . . . 377 REP_TASK_INST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 REP_WFLOW_RUN . . . . . . . . . . 380 REP_SESSION_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 REP_SERVER_NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 REP_SERVER_NET_REF . 398 REP_CM_LABEL . . . . . 374 REP_WFLOW_VAR . . . . . . . . . . . . . . 383 REP_COMPONENT . . . . 399 Table of Contents xi . . . . . . . . . . . 372 REP_ALL_TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 REP_WORKFLOW_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 REP_EVENT . . . . . . . . . . . . . . . 387 REP_SESS_TBL_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 REP_LOAD_SESSIONS . . 392 REP_DEPLOY_GROUP_DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .REP_WORKFLOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 REP_TASK_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 REP_CM_LABEL_REF . . . . 393 Repository View . . . . . . . . . . . . . . . . . . . . . . . 384 REP_SESS_PARTITION_DEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 REP_DEPLOY_GROUP . . . . . . . . . 391 REP_GROUPS . . . 388 Security Views . . . . . . . . . . . 386 REP_SESS_LOG . 381 REP_SESSION_INSTANCES . . . . . . . . . . 395 PowerCenter Server Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Running Commands in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . 404 Using Native Connect Strings . . . . . . . . 411 Exiting pmrep (Exit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Disabling a Repository (Disablerepository) . . . . . . . . . . . . . . . . . . . . . . 403 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Configuring Repository Passwords on UNIX . . . . . . . . . . . . 432 Importing Objects (ObjectImport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Removing Repositories From the Cache (Removerepository) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Creating a Relational Connection (CreateConnection) . . . . . . . . . . . . . 435 xii Table of Contents . . . . . . . . . . . . . . . . . . . . . . 423 Listing Tables by Session (Listtablesbysess) . . . . . 413 Adding Repository Configurations (Addrepository) . . . . . . . . . . . . . 429 Sending Notification Messages (Notify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 REP_SUBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . .Folder View . . . . . . . . . . . . 407 Using Password Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Specifying Options and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 Adding a Server (Addserver) . . 420 Deleting a Server (Deleteserver) . 404 Using pmrepagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Getting Help (Help) . . . . . . . . . . 433 Registering Local Repositories (Register) . . . . . . . . . . . . . . . . . . . 404 Using pmrep . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Configuring Repository Passwords on Windows . . . . . . 414 Backing up a Repository (Backup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Enabling a Repository (Enablerepository) . . . . . . . . . . . . . . . . . 431 Exporting Objects (ObjectExport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Listing Object Dependencies (ListObjectDependencies) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Cleaning up Persistent Resources (Cleanup) . . . . . . . . . . . . . . . 406 Running Commands in Command Line Mode . . . . . . . . 417 Deleting a Connection (Deleteconnection) . . . . . . . . . . . . . . . . . 411 pmrep Repository Commands . . . . . 404 Running Commands . . . . . . . . . . . . . . . . . . . . . . . . 410 Connecting to a Repository (Connect) . . . . . . . . . 409 pmrep System Commands . . . . . . . . . . . 401 Chapter 16: Using pmrep and pmrepagent . . . . . . 422 Listing Repository Objects (ListObjects) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . 450 Adding a User to a Group (Addusertogroup) . . . . . . . . . 443 Updating Sequence Generator Transformations (Updateseqgenvals) . . . . . . . . . . . . . . . . . . 455 Modify Folder Properties (ModifyFolder) . . . . . 461 Labeling (ApplyLabel) . . . . . . . . . . . . . . . . . . . . . . 447 Updating the Target Table Name Prefix (Updatetargprefix) . . . . . . . . . . . . . . . . . . . . . . . 456 Registering a User (Registeruser) . 462 Checking In Objects (Checkin) . . . . . . . . . . . . . 452 Deleting a Folder (DeleteFolder) . . . . . . . . . . . . . . . . . . 436 Showing Connection Information (ShowConnectioninfo) . . . . . . . . . 439 Unregistering Local Repositories (Unregister) . . . . . . . 451 Creating a Group (Creategroup) . . . 450 Creating a Folder (CreateFolder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Updating the Source Table Owner Name (Updatesrcprefix) . . . . . . . . . . . . . . . . . . . . . . 457 Removing a Group (Rmgroup) . . . . . . . . . . . . . . . . . . . . . . 464 Clearing a Deployment Group (ClearDeploymentGroup) . . . . . 454 Listing All Groups (Listallgroups) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Updating Server Variables (Updatesrvvar) . . . . 452 Creating a User (Createuser) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Changing the Repository Password (Changepasswd) . . . 437 Stopping a Repository (StopRepository) . . . . . . . . . . . . . . . . . . . 455 Listing All Privileges (Listallprivileges) . . . . . . 441 Updating the Notification Email Addresses (Updateemailaddr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 Listing All Users (Listallusers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Creating a Deployment Group (CreateDeploymentGroup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 Truncating Workflow and Session Logs (Truncatelog) . . . . . . . . . . . . . . . 440 Updating a Database Connection (UpdateConnection) . . . . . . . . . . . . . 458 Removing a User (Rmuser) . . . . . . . . . . . 457 Removing a Privilege (Rmprivilege) . 459 pmrep Change Management Commands . 442 Updating Server Details (Updateserver) . . 449 Adding a Privilege (Addprivilege) . 465 Table of Contents xiii . . .Running Script Files (Run) . 437 Changing the Connection Name (SwitchConnection) . . . . . . . . . . . . . . . . . . . 460 Adding to a Deployment Group (AddToDeploymentGroup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Updating Repository Statistics (UpdateStatistics) . . . . . . . . . 447 pmrep Security Commands . . . . . . 453 Editing a User (Edituser) . . . . 458 Removing a User from a Group (Rmuserfromgroup) . . .

. . . . . . . 481 Registering a Plug-in (Registerplugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Creating a Persistent Input File with pmrep .Creating a Label (CreateLabel) . . . . . 506 Scripting pmrep and pmrepagent Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Restoring a Repository (Restore) . 477 Restoring Teradata Repositories using Fastload (Bulkrestore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 . 498 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Validating Objects (Validate) . . . 500 Sample Import XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 xiv Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Deploying a Deployment Group (DeployDeploymentGroup) Executing a Query (ExecuteQuery) Deploying a Folder (DeployFolder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Undoing a Checkout (UndoCheckout) . . . . . . . . . . . . . . . . . . . . . . . . 509 Designer Tasks . . 507 Appendix B: Permissions and Privileges by Task . . 492 Appendix A: Working with pmrep Files . . . . . 470 Listing Checked Out Items (FindCheckout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Using the Object Import Control File . . . . . . 474 pmrepagent Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Deleting a Deployment Group (DeleteDeploymentGroup) Deleting a Label (DeleteLabel) . . . . 469 . 500 Using the Deployment Control File . . . . . . . . . . . . . . . . . . . . . . . . . 467 . . . . 493 Using the Persistent Input File . . . . . . 491 Tips . . . . . . . . . . 477 Backing up a Repository (Backup) . . . . . . . 480 Deleting a Repository (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Object Import Control File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 Workflow Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Creating a Persistent Input File Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Scripting pmrep and pmrepagent Commands . . . . . . . . . . . . . . . . . . . . . . . . . 504 Deployment Control File Parameters . . . . . . . . . . . . . 485 Unregistering Plug-ins (Unregisterplugin) . 479 Creating a Repository (Create) . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Upgrading a Repository (Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 Repository Manager Tasks . . . . . . . . . . . . . 519 pmrepagent Tasks . . . . . 521 Table of Contents xv . . . . . . . . . . . . 513 pmcmd Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 Index . . . . . . . . . . . . . . . . . 516 pmrep Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Workflow Monitor Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi Table of Contents .

9-10. .. . . . .. . . . . . . . . . . . . . . . . . . . .. . . . .. . . ... .. .. . .. . . .... .. . . . .. . . . Repository Manager Components . . Labels Properties .. . . .. .. . . 7-3. . . . .. . . . . .. . . Query Browser . .. . . Deployment Group Editor .. . .. . . . . . . . . .. . . .. .. . . . . .... . . . . . . . . . .. . . . . ... . . . . . .. . .. . .. . . . . . .. . .. . . . . . . . .. .. . . . .. 22 . . .. . . . . Referenced Shortcut Object . . Dependency for Deployment Group Dialog Box . . . . . . .. . . . . 40 . . . . . . . . . . . . . . . . . 7-1. . . . . . . . . . . . . . . . . .. . . . . . . PowerCenter Repository Connectivity . . . . . ... .. . . . 55 . CRCVALUE Code in an Exported XML File . . 56 100 100 132 177 185 186 187 190 202 204 204 205 206 209 220 220 221 223 224 225 226 232 236 237 238 239 268 List of Figures xv . . . . . .. . . 2-1. . . . . . . . 9-9. . . . . . . . . . . . .. . . . .. . . . . . . . View History Window . . . . . . . .. . . . .. . . . .. .. . . Sample Query Results .. . . . . . .. . .. . . . . . . . . . . 27 .. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . . . . . . . . . . .. . . . . 24 . . .. . Deployment Group Browser . . .. . . . . . . . . . . . 9-12. . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . .. . .. . 9-8.. . . . . . . . . . ... Apply Label Dialog Box .. . .. . . . . . . ... 2-2. . . . . . . . . . .. . . . 7-2. . . . . . . One-Way and Two-Way Comparisons . . . . .. 25 . . . .. . . .List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1-1.. . . . . . .. . . . ... . . . . . . . . . . . . Repository User Names and External Login Names 6-1. . . . . . . ... .. . . . . . . . . . . .. 9-2. .. . . . . . . . . . . . . . . . . . . 9-4. . ... . . . .. . . Label Editor Options . . . .. . . .. . . . . . . . . . . . . . .. 2-9. . 2-5. . . ... . . . ... . Object Properties . . .. .. . .. Results View Windows List . .. . ... . . . . . .. . . . . . . .. . . . . . . . .. . . . . . 9-1. . . . . . Object and Shortcut Description . . . .. . . . . . . .. . . . . . .. . . . .. . . . . .. . . . . . .. . . . . . 2-8. . .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11.. . . . . ... .. . . . . . . . . . . . .. . .. . .. . . . . . . . . . . . . . . . . . . . . . . ... . . .. . . Activity Log Window . . . . . . . . . . 2-6.. . . . Create a Global Shortcut .. . . Query Editor . . . Repository Manager Navigator . . . . . . .. .. . ... . 8-2.. . . Event Viewer Application Log Message . .. 9-3. . . . . . . . . . ... . . . . . . . Query with Multiple Conditions . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . 8-5. .. . . . .. . . . . ... . . .. .. . . . 7-4.. . . . . .. . .. . Transformation Shortcut Icon . .. . . . . . . . . ... . . . . . ... . . . .. . View Dependencies Window . . . . Object Status Properties .. . ... . . . .. . . . . . .. . . . .. . ... . . . . . . . . .. .. .. . . . . . . . .. .. . . . . . . . . . ... . . . . . .. . . . .. . . . .. . ... . . .. Label Browser . . .. . . . . . . . Repository Details . . . . . . .. . .. . . . . .. . . . . . . .. . Validate Objects Results .. . . . . . . . . . . Version Properties . . . 41 . . . . .. . . . Deployment Group History . . . . . . . . . . Output Window . . . . Apply Label Wizard . . . . . .. . . .. . . ... .. . . . .. . . . . . ... . . . . . . Application Log Message Detail . . . . . . . .... .. . . 39 . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 2-3. . .. . . . . . . .. . . . . . . . .. . .. . . . . . . . . . . . . . . . .. . .. 2-4. . . . . . .. 3-2. .. . . . . . . Administration Console . ... . . . . 9-5. . . . . . ... . . . . . . . . . . . 52 . . . . ... .. .. . . .. . . . . . .. ... . . . . . . .. . . . .. . . 5-1. . . . . . . . . . 11-1. .. . . . .. . .. . . . . . .. . . 8-4. . . . . . . . . . . . . . . . . . . . . .. . .. . . . . 43 . . . .. . . . . 28 . . . .. .. . . . . . . .. .. . . . . . . . . . .. . . . . . . . . . . . . . . 3-4. . .. . . .. . . .. . . . . . . . . . . . . . . .. . . . . . 8-3. . . . 8-1. . . .. . . 4 . . . . . . . .. . . . . . . . . . . . . . . . ..... 2-7. . . . . . 9-7. . . . 8-6. . . . . . 3-5. Source Definition Object Properties . Object Dependencies Saved as HTML . . 3-1. . ... . . .. . . .. Dependencies Dialog Box .. . . . Dependency Window . . . 9-6. . . . . . . . 3-3. . . .. . .

. . . . . . . . .. . . . . . . . . . . . . ..282 . . . . . . . . ..... .. . . . .. .303 xvi List of Figures . . . . . .. . . . Import Wizard .. . . . .301 . .. . . . . 11-4. . . . . . . . . .. . . . . Export Options Dialog Box . .. ... . . . . . . .. .Figure Figure Figure Figure Figure Figure Figure 11-2.283 . . The Copy Wizard . . . .. . .Resolve Specific Object Conflicts Conflict Resolution Wizard . . . . . ... 11-3. . .. . . .. ..271 . . . . ...Resolve General Object Conflicts Import Wizard . .. .. .. .. .. . . . .. . ..284 . . . . . Copy Wizard Mapping Conflicts . . . . . . . 12-2.. . . . . .. .. .. . . . . . 12-1. . 11-5. . . . . . . . . . . . . . . . . . . .. . . . .. . . .. ..298 .. . . . . . .. . .. . . . . . . Copy Wizard Resolutions . . ... 12-3. . . . .. . . .. . .. . . .

. . . . . . 43 . . . . . .. . 5-7. . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 10-2. . . . . . . . 10-1. . . . .. . . . . . . . Folder Permissions . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . Object Lock Properties . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . 79 . . .. Viewing Object Dependencies . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks Available in View Checkouts Window . . . . 55 . . . 3-8. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 8-1.. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repository Servers Node Details .. 55 . . . . . Repository Locks . LDAP Server Configuration Options . . . . . . .. . . . . . . . . . . .. . . . . .. . . . . 40 . . Versioning Object Security Levels . . . . . . . . . . . .. . . . .. . . . . . . . . . . . . . . . . . 5-2. . . . . . . . . . .. . .. . . . . .. . . . . . . .. . . . . 26 . 6-3. . . . . . . . . . . . . . . . . . . . Compared Objects in Compare . . . . .. HTML Links for Performing Repository Tasks . . . 2-4. . . . . . . . . . . .. . . . . 3-3. Query Parameters and Values . . . . . 9-2. . . . . . . . . . .. . . . . . . . . . . . . New Repository .. . . . . . . Tasks Available in Query Results Window . 4-5. . . . . . . . . . . . .. 4-1. . 8-2. . . . . . . . . . 3-5. 91 . .. . . . . . . . . . . 37 . . . . . . . . . . . Default Repository Privileges . . . . . . . . . . . . . . . . . . . 4-3. . . . . . . . . . . . . . ... 3-1. . . . . . . . . . . . . Converting Special Characters in Repository License File Names . . . . . . . . . . . . . . . 94 . . 3-4. . . . . . . . . . . .. . . . . . . . . . . . Folder Object Security Levels . . . . . .. . . 2-5. . . . . . . . . . . . . . . . . . . . . . . . .. . . Extended Repository Privileges . . .. . . . . . . . . . . . . 6-2. . . . . . . 3-2. .. . . . . . . New Repository . . . . .. . . . . . 5-4. . . . . . . . . . . . . . . 54 . . . . . . . 54 . . . Repository Details .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3.. . . . . . . . . . . . . . . . Label Options and Description . . . . . . . . . . . . . . . . . .. 9-1. . . . . 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Properties for View Dependencies Window . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 2-3. . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . 5-1. . . . . . . . . . . .. . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . .. . . 97 106 107 108 109 120 122 143 145 148 149 151 154 157 169 174 175 196 209 212 222 227 232 251 258 List of Tables xvii . . . . . . . .. . . . . . . . . . LDAP Login Properties Options .. . . . . . . . . . . . .. 4-6. . . . . . .. . . . License File Compatibility Requirements . . LDAP Login Properties Options . . . . . . Object Details Displayed in Repository Main Window . . . .. . . .. . .. . . . . . . . . Repository Connection Properties . . .. . . . . . . . . . . 3-9. 3-7. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . Repositories Node Details . . . . . . 81 . . . . . 93 . . 3-6. . . . . Register Security Module Options. . 7-1. . . . . .. . . . .. . . .. . . . . . . . . . . New Repository . 9-3. . . . . . . .. New Repository . .. . . . . . . . . . . .. . . Repository User Connection Details . . .Configuration Tab . . .. . . . .. . . . . . . . . . Change In Object Status After Copying Deployment Group Objects . . . . . . . . . 2-2. . . . .. .. .. . . . . . . . . . . . . . 6-1. . .. . . Validate Objects Properties. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..General Tab . . . 3-10. .. . . .List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 2-1. . . . . . . . 96 . . . . . Tasks Available in View History Window . . . . . . . . . . . . . .. Compared Object Types and Attributes . . . 4-4. . . . . .. . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . Object Lock Properties . . . 3-11. . . . . . . . . . . . . . 4-2. . Dependencies Options . . Copying Global or Local Shortcuts . . . . Repository Log Codes . . . . . . . . . . . . . . . .. . . . . . 5-6. . . . . . . . . . . . . . . . Copy Folder Wizard Prompts (Copying a Folder) . . . . .Network Tab . .Database Connection Tab . . . . . . . . . 5-5.. . . .

. .. ... . . . . . . .. .. .334 . . . . .. . . . .. . . . . . . . Target Views . . . . . . . . . . . . . . . . . . .358 . . . . . . . . . . . . . . . . . . 15-3. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . .341 . . . . . . . . . . . . . . . . . . .. Modifiable Repository Objects .. . . . Source Views . . . . . . . . . .. .. . . .. . . 15-10.266 .. . . . . . . .365 . . REP_TARG_TBL_JOINS MX View . . . . . . . . . . .. . . .329 . . . . . . .. . REP_ALL_MAPPLETS MX View .. 15-11. .336 . . . . . . . . .. . . . .. . . . .. . . . . ... . . . . . . . . . . . . . . . . . . . . . . REP_TARG_TBLS MX View . . . . .. . . . . . . . 11-3. . . . . . . . . . . . . . ..364 . . . . . .. . . . . . . . . 15-2. . . . . . . . . . .. . . . . .. . . REP_SRC_TBL_FLDS MX Views ... . . . . .. 15-6. . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . .299 . . . . . . . .. .. . . . . . .343 . . . . . . . . . . . . . . . 15-26. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .269 . . .. . . . . . . . .356 . . . . . . . . . . . . . . . . . . . . . . . 15-1. . . . . . . .366 xviii List of Tables .. . . . . . .. . . . .. . REP_ALL_SOURCES MX View . . . .336 . . . . . . . . . . . . Dependent Objects Exported . . . . .271 . . . . . . . . . REP_DATABASE_DEFS MX View .. . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . REP_SRC_MAPPING MX View . . . . .. . . . . ... . . .. .. .354 .338 . . . . . . REP_TARG_FLD_MAP MX View . 11-5. . . . .. . Transformation Views . . . . . . . . . .. . . . . . . . . . . Options for Exporting and Importing Multiple Objects .. . . . . . . . . .270 . .. . . . 15-17. . .. 11-6. . . . .349 . . .. . 12-1. . . . . REP_ALL_TARGET_FIELDS MX View . .. . . . . . . .300 . . . . .347 . 15-18. . . . . . . . . .. . . . . . . . . . . . . REP_MAPPING_UNCONN_PORTS MX View .. . . . . .. . .. ..278 . .. . . . .353 . . . . . REP_SRC_TBLS MX View . . . . . . . . . . . . . Mapping and Mapplet Views .. . . 11-4. . . .. . . . . . 15-15. . . .. . .. . . . . .. .. .. . . . REP_MAPPING_PORT_CONN MX View . . . . . REP_ALL_MAPPINGS MX View . . . . . . 15-28. . .. . . . . . . . . .. . . . .362 .. .. .. . .. . . .. . . . . .. . . . . . 14-1. . . 15-8. . . . . . . . . . . . . 15-24. . . . . . . . ... .. . . . . . . .. . . . . . . . . . . . 15-25. . . . . 15-23. .259 . . . . . .. REP_TARG_MAPPING MX View . .. . .. 15-20. . . . . .. . . . . . . Options for Creating Reusable Metadata Extensions . . . SQL Script to Drop MX Views . . . REP_TBL_MAPPING MX View . Copy Wizard Areas . . ..321 . . . . . . . . REP_ALL_SOURCE_FLDS MX View .346 .. Copy Wizard Resolutions . .. . . . . . . . . . . . . . ..355 . .. . . 15-16. . . . . . . . .. . . ... . . . . ..282 . . . REP_METADATA_EXTNS MX View . .. . 15-5. .. . .. . . . REP_FLD_MAPPING MX View . . . .. . . . . . . . . . . . . . . Resolving General Conflicts During Import. . .364 . . . . .. . . . . . . . . . .359 .. . . . . . .359 . ... . .339 . . 15-31. . .. . . . . .. 13-1.. ... .. . . . . . . . . . .345 . . . . . . . . . . . . . .344 . . . . . .363 . . REP_ALL_TARGETS MX View . . . . . . . . . . .. . . . .. . . 11-1. . . 15-32. . . ... . Metadata Extension Views . . . 15-29. . . . . . . . . .. .. . . . . . . . . . . . .. 15-4. .. . . . . . .. 15-7. . . .. . . . . .. . . . . . 15-19. .. . . . . . . . . . . . . . . 12-2. . . .. . .. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views . . . 15-13. . . . REP_TARG_TBL_COLS MX View . . . . . REP_METADATA_EXTN_DEFINES MX View .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 10-3... . . .357 . ... . Mapping Source Fields . . .351 . 15-14. . . ... . . . MX View Categories . . . . . . . . . . . . . . .. .. . . . . . . . . . Metadata Import Wizard . . 15-22. .. . . . . .. .. . . . .. . . . . . ... .. . .. . . . . . . 15-30. . . . . . . . ... . . . . . . .. . ... . . . . . . . . ... . . . .. . . ...339 . . . ... . . .... .. . .. . . . . . .. .360 . . Copy Deployment Group Wizard Prompts . .. . . . . .. .. . . . . . . . . . . . . . . 15-21. . . . . . 15-12. . ... .. . . .347 . . . SQL Script to Create MX Views . . . . . . . . .PowerCenter Options . . . . . . . . . . . Options for Exporting Objects . . .. . . . . . . . .. . . . . . ... . . REP_SRC_FILES MX View . . . . . . . . . . . .351 . . . .. . .361 . Exporting and Importing Objects Permissions and Privileges 11-2. . . . . . . . . . . . . . 15-9. . . ... . . . . . . . . . . . .. 15-27. . .. . . . . . . . . . . . . .. . . . .

. . ... . . . . . . . . . 15-53. . . . . . . .. . . . ... .. .. . . . . . . . .. .. . . .. . . .. . .. . . . . . . . . . . . . REP_CM_LABEL MX View . . . . . . REP_WFLOW_VAR MX View . . . . and Task Views . . .... .. . . . . . .. . .. ... . . . . .. . . . REP_GROUPS MX View . . . . .. . .. . . . . . .. . . .. . . . . . . 15-65. . . . .. .. . . .. .. REP_TASK_INST_RUN MX View . . . . . 15-71. 15-66... . REP_SERVER_INFO MX View . . . .. 15-73. . . .. . . .. . .. . . . . . . . .. . . . . .. . . . . . . REP_SESS_TBL_LOG MX View . . . . REP_DEPLOY_GROUP_DETAIL MX View . . . . Deployment Views . . .. . . . . . . . . . . . . . 15-45. . . .. . .. REP_USERS MX View . . . . . . . 15-49.. . ... . . .. .. . .. . ... .. . .. REP_SERVER_NET MX View . . . . . . . .. . . .. . . . . . .. ... 15-61. . ... .. . . . . .. . . . .. .. . PowerCenter Server Views . . .. ... . . .. . . . .. .. . .. . . . . . . . . .. . . . . . . .. .. .. . . . ... . . 15-56. . . .. . . . . . . ... . . . . . 15-64. . .. . . REP_WIDGET_DEP MX View . . . . . .. . . .. .. . . . . . . . ... . . . .. . . . . . . . . . . . . . . . . . REP_WORKFLOW_DEP MX View . ... . . . . . . . . .. . . . . . . . . .. .. . . . . . . . . . .. . REP_WORKFLOWS MX View . . . . ... . . . .. . . . .. . .. . . 15-51. . 366 368 368 369 369 371 372 374 374 375 376 377 377 378 379 380 381 382 382 383 383 384 385 385 386 387 388 390 390 391 391 392 392 393 395 396 396 397 397 398 398 399 399 List of Tables xix . .. ... . . REP_COMPONENT MX View . . . . .. . . .. . . .. . . . . . . REP_TASK_INST MX View . . REP_USER_GROUPS MX View . . . 15-59. . . . . . . . . .. . . . ... . . . . . . . . . . . . . . . . . . . . .. . .. . .. .. . 15-35. . . . . . . . . . . . . . . . .. . .. . . . . . 15-69. . . . . . REP_SESS_LOG MX View . .. . . .. .. REP_SESS_PARTITION_DEF MX View . . .. . . . . . . . ... . . .. . 15-54... . . . . .. . . . Worklet. .. . . . . . . . . . . . . .. . . . .. . . . . . ... . . Security Views .. .... . . .. . . . . . . . .. .. .. . . . . . .. . . . .. . . . . .. . . . . . . .. . . . . .. ... . . . 15-55. . .. . . . . . . .. . . . . . .. . . . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 15-33. . . . . 15-52. . . .. . ... . . . . . . . . .. .. . . . . . . . . . . . . . . . .. . . . .. . .. REP_SESSION_INSTANCE_FILES MX View REP_SESS_WIDGET_CNXS MX View . . . . . . . . . . . . . .. . .. REP_CM_LABEL_REF MX View . . .. . . . . .. . . . . .. . ... .. . . . .. . . . . . . . . . . REP_WIDGET_FIELD MX View . . REP_ALL_TRANSFORMS MX View ... . .. .. . REP_SESS_CONFIG_PARM MX View . . . . .. . . 15-47. .. . .. . . . . . .. 15-68. 15-74. . . . .. . . .. .. ... . . . . . . . . .. ... . . . . Workflow.. . . . . . . . .. . . . 15-42. . . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . ... . .. . ... . . . .. . . .. . . 15-58. . .. . ... . . REP_WIDGET_INST MX View . . . .. . .. . REP_TASK_ATTR MX View .. .. .. . . . .. . . . REP_SESSION_CNXS MX View . .. . . .. . . .. . . . . . . ... . . . . . . . . ... .. . . . . .. . . . . . . . . . . . . . . . . REP_WFLOW_RUN MX View ... . . ... . . . 15-50. . . . .. .. . . . . . .. .... . . . 15-34. . . . . . . . . 15-46. . . REP_REPOSIT_INFO MX View . . . . . . . . . .. . . . .. . . .... .. .. . . . ... 15-39. .. . 15-44. . . .. 15-41. . . .. . . . . .. . . 15-38. . . . . . . . . . 15-40. .... . .. . 15-75. 15-70. . . . .. . .. .. . . . .. .. . . . . . . . . .. . ... . . . . .. . . . . .. . .. .. . . . 15-63. . . .. REP_SESSION_INSTANCES MX View . . . . . . . . . . .. . . . . 15-37. . . . . . . .. . REP_VERSION_PROPS MX View .. . . .. . .. . . . . . . . . .. . . . . . . .. . ... . . .. . . . .. . . . . . . .... . . . . . . .. . . . REP_EVENT MX View . . .. . . . . . 15-72.. . 15-60. . . . . . . .. REP_ALL_SCHEDULERS MX View .... . . . . .. .... .. .. . . . REP_SERVER_NET_REF MX View. . . ... 15-48. .. . . . . . . . .. .. . . . . . .. REP_ALL_TASKS MX View . REP_EIDGET_ATTR MX View . . . . . . .. . . . . . . ... . ... ... . . . . ... REP_LOAD_SESSIONS MX View . .. ... .. . . .. . . .. . . . . . REP_SESSION_FILES MX View . . . . . . ... . . 15-36. . . . 15-67. . . .. 15-43. . .. REP_DEPLOY_GROUP MX View . .. . . Change Management Views .. . . . . .. 15-57. . . . . . . . . . . . .. 15-62. . . . . . . . .

.. . .. . . . . . . . . . . Deleteserver Options and Arguments (pmrep) .. .. . pmrep System Commands . . . . . . . . . . . .. . . . . . . . . . .. .. . .. . . . . ObjectExport Options and Arguments (pmrep) . . . . .. . . .. .. .410 . . . . . . 16-23. . . .446 . .. . . . . .. . . ... 16-29. pmrep Repository Commands . . . . .. .. . . . . . .. . . 16-18. . . . . . . .. . .. .. . . . .401 . . Truncatelog Options and Arguments (pmrep) .436 . . . . . . .. . . . . 16-30. Disablerepository Options and Arguments (pmrep) . Updatesrvvar Options and Arguments (pmrep) . . . 16-31. 16-32. . . . . . . .442 . . 16-12. . . . . . . . 16-37. .. . Notify Options and Arguments (pmrep) .. ... . . Updateseqgenvals Options and Arguments (pmrep) . . . . . . ... .443 . . . . . . . . . . ... . 16-17. . . . . .. . . .433 . ... . . . . . . .. . . . .. . . .. Listtablesbysess Options and Arguments (pmrep) . 16-36. . .. . . .. Removerepository Options and Arguments (pmrep) .. . . . . . . . . . . . . .438 . . . .. . . . . . . . . . . . 16-39. . . 16-13. . . .417 .. . . . . . .. . . . . . . . . . . . . . . . . . . . .439 . . . . . . . . ... . . . Addrepository Options and Arguments (pmrep) . . . .. . 16-8. . . . . . . . . . .. .. .. . . . . . .... .. pmrep Security Commands . .. . Creategroup Options and Arguments (pmrep) . .. .. . . . Updatetargprefix Options and Arguments (pmrep) .450 . . . .452 xx List of Tables . . .447 . . . . . . . . . . .448 . . . .414 . SwitchConnection Options and Arguments (pmrep) . . . . . Changepasswd Options and Arguments (pmrep) . . . . . . . .451 . . . 16-26. . . . . . . . . . . . .. . . . . . . . . .. . 16-27. . . . . . . . . 16-28. . . . . . . . .444 . . . . . . . . ListObjects Options and Arguments (pmrep) . . .. . . . . . . . . . . ... .435 . .. . . 16-21. . . . . . 16-14.. . . .. . . . . . . . .. . .. .. . . . . . . . . . . . . ... . . .. . Transformation and Task Types to Use with pmrep . . . . . . . . . . . . . . . . . . . .. . . .. .422 .. . ... . . . . . . .422 . . .434 . . . . . .. . .... . . .. .. . . . . . . . . . . . . . Deleteconnection Options and Arguments (pmrep) . . . . . . . .. . . 16-24.. . . . . . . . Updatestatistics Options and Arguments (pmrep) . . . .. . . . . ... .. . .. . . . . . . . .. . . . . . . . . . . . . 16-10. . . 16-42. . . . .439 . .. . Addprivilege Options and Arguments (pmrep) . . . .. . . . .. StopRepository Option and Argument (pmrep) . . . . . 16-9. . .425 . . . . .. ....418 . . . . . . . . .. . . 16-15. . . 16-7.410 . ....447 . . . . . . .. . . . . . . . 16-41. . .. . .. ... . . . .416 . .. 16-11. . Connect Options and Arguments (pmrep) . 16-33. . .421 . . . . . . . . . . . .. . . . . . .428 . . . . . . Updatesrcprefix Options and Arguments (pmrep) . Addusertogroup Options and Arguments (pmrep) . . .434 . . . Addserver Options and Arguments (pmrep) . . . . . . . . . . . Enablerepository Options and Arguments (pmrep) . . . . . . ... . . .450 .. . . . . . . . .. 16-6. . . . . . . . . . . . 16-40. . .. . ..443 . . . . . . .419 . . . . . . . .. . . ..... 16-38.. . . . . . . 16-25.. . .. Updateemailaddr Options and Arguments (pmrep) . . . 16-4. 16-2. .. .. ..412 . . . . . . . . . . . 16-34. ... . . . . . ListObjectDependencies Options and Arguments (pmrep) . .. . . .451 .. . . . . . . .. . . . . . . 16-16.421 . 16-5. . ... .. . . . . . Unregister Options and Arguments (pmrep) . .. .449 .. . . . . .. . REP_SUBJECT MX View . ... . Backup Options and Arguments (pmrep) .415 . . . . . . .426 . . 16-1. .. .. . . . . ObjectImport Options and Arguments (pmrep) . . . . . . . . . . . . . . . . . . . . . .. 16-19. . 16-20. . . . .. . . . . . .. .430 . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 15-76. .. . . . . . . . . . . . . . . ... . . Updateserver Options and Arguments (pmrep) .... UpdateConnection Options and Arguments (pmrep) . .. . . .. .. . . . .. . . . . . . . . .. . . . . . . .. . . . . . . . . . 16-22. . CreateConnection Options and Arguments (pmrep) . . . . . .. . . . . . . . . .405 . .. . . .. CreateFolder Options and Arguments (pmrep) . . . . Database Type Strings . . .440 . . . . . .. . . . .. . . . . . . . Code Page ID by Name (pmrep) . .. . Run Options and Arguments (pmrep) . . .. . . Native Connect String Syntax . . . . . .. . . . .. . . . .. . . . . . 16-35. . . . .. . . . .. . . .. ... . . . . . .. ... Register Options and Arguments (pmrep) .431 . . . . . . . . . .. . 16-3. . .

. . .. . . . . .. . . . . . . .. . . . . . . . .. . .. . . . .. . . . . . . . . . . . .. . .. .. . .. . 16-65. . . . .. . . . . . . . . . . .. . . . . 16-57. . . . 16-67. . . . . . . . Createuser Options and Arguments (pmrep) . .. . Backup Options and Arguments (pmrepagent) . . . . . .. . . . .. . . . . . . .. . . . .. . . . . . . .. . . . . . . . . . . . . . . .. . . . UndoCheckout Options and Arguments (pmrep) . . . . 16-68. 16-55. Registerplugin Options and Arguments (pmrepagent) . . . . B-3. . . . . . .. . . . 16-46.. . . . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 16-43. . ... . .. . . . 16-47.. . . . . . Delete Options and Arguments (pmrepagent) . . ... . . . . . 16-56. . . . . . . .. . . . . . . . . . . . . . . . FindCheckout Options and Arguments (pmrep) . . . . .. ... . . . . . . . Required Permissions and Privileges for pmrep Tasks. . . . . . . . . . . . .. B-5. . . .. . . . 16-58. . . . . . . . . .. . . . . ... .. . AddToDeploymentGroup Options and Arguments (pmrep) . . . .. . . . . . . . . DeleteDeploymentGroup Options and Arguments (pmrep) . .. .. . . 16-50.. . .. . . . . . . . . . . . . . Required Privileges and Permissions for Designer Tasks . . . . . . . . . . Upgrade Options and Arguments (pmrepagent) . . . . . 16-70. . . . . . .. . . . . Rmuserfromgroup Options and Arguments (pmrep) . . . . . . . . . .. . .. . . . ... . . . . . .. . . . . . . . . . . . .. . ... . . . . . .. . . Rmgroup Option and Argument (pmrep). . . . Unregisterplugin Options and Arguments (pmrepagent) . . . . . . . .. .. 16-48.. . . . . Deployment Control File Elements and Attributes (pmrep) . . . . . 16-69. . .. . . . . . .. . . . . . .. 16-64. . . . . . . . . . . .. . . . . . . 16-63. 16-59.. . . .. . . . . . B-2. . . Required Privileges and Permissions for Workflow Manager Tasks . . . Required Privileges and Permissions for Workflow Monitor Tasks . . . . . . . DeleteFolder Options and Arguments (pmrep) .. . . . 16-44.. 453 453 454 456 457 458 458 459 459 460 461 463 464 465 465 466 467 467 468 469 470 472 474 475 477 478 479 480 481 482 485 488 490 498 505 510 511 513 515 516 519 List of Tables xxi . . . . . . . . . . . Rmprivilege Options and Arguments (pmrep) .. . .. . pmrepagent Commands . . . Object Import Control File Elements and Attributes (pmrep) ... . . .. . . A-1. . . . . . . . .. .. . . . . . .. . . . . . . . . . . . . Edituser Options and Arguments (pmrep) . . 16-74. . . . Checkin Options and Arguments (pmrep) . DeployDeploymentGroup Options and Arguments (pmrep) . . . . . . . . . . .. . . . .. .. . . . . . . . . Validate Options and Arguments (pmrep) . ... . . .... . .. 16-73. . . . . . . . . . . . . . . . . ApplyLabel Options and Arguments (pmrep) . .. . 16-49. DeleteLabel Options and Arguments (pmrep) . 16-61. . . ModifyFolder Option and Argument (pmrep) .. .. . .. .. . . . . . . . . .. . . . . . . . . . . . . . 16-54. . . . 16-62. . . . . . . . . 16-71. 16-45. . . . . . .. . . . . . .. . . . . . . . Restore Options and Arguments (pmrepagent) . .. . . B-1. . . . . . . . .. . .. . . . . . . .. . . ClearDeploymentGroup Options and Arguments (pmrep) . . . . .. . . . CreateDeploymentGroup Options and Arguments (pmrep) . . . . .. .. . . . . . . . . .. . . . . .. . . . 16-53. . . . . . . . . . . Rmuser Option and Argument (pmrep) . . . . . . 16-75. . Registeruser Option and Argument (pmrep) . . . DeployFolder Options and Arguments (pmrep) . . . .. . . . . . . . . . .. . . . . .. CreateLabel Options and Arguments (pmrep) . .. . A-2. ... . . . .. ExecuteQuery Options and Arguments (pmrep) . . . . 16-66. . . . . Create Options and Arguments (pmrepagent) . .. . pmrep Change Management Commands . . . . . . . . . . . . Required Privileges and Permissions for pmcmd Tasks . ... . . . . . . . . . . . . . .. .. . . . .. . . . . .. Required Permissions and Privileges for Repository Manager Tasks B-6. . . Bulkrestore Options and Arguments (pmrepagent) . . . . . . .. . . .. .. . . 16-72. . . .. . . . . . 16-51. . .. .. . . . . . . 16-60. .. . . . . . .. . . . . . .. . . .. . . . . . . . . 16-52. . B-4. . .. . . . . . . . .. . . .

xxii List of Tables .

handle complex transformations on the data.Preface Welcome to PowerCenter. xxiii . data synchronization. PowerCenter can simplify and accelerate the process of moving data warehouses from development to test to production. and information hubs. usable. The PowerCenter Server can extract large volumes of data from multiple platforms. loading. The PowerCenter metadata repository coordinates and drives a variety of core functions. data migration. transforming. Informatica’s software product that delivers an open. and managing data. and efficient manner. scalable data integration solution addressing the complete life cycle for all data integration projects including data warehouses and data marts. and support high-speed loads. including extracting. PowerCenter combines the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely.

1. or the rows that do not meet the business rule. You can define default mapping. sessions. 7. You can configure the Data Profiling Wizard to filter the Domain Inference function results.1. Domain Inference function tuning. You can view a profile from a random sample of data. Profile mapping display in the Designer. PowerCenter 7. You can create a data profile for a sample of source data instead of the entire source. or you may want to widen the scope of patterns returned to view exception data. JEF-kana. xxiv Preface . Flat file partitioning. a specified percentage of data. You may want to narrow the scope of patterns returned to view only the primary domains.0. Row Uniqueness function. and 7. You can save sessions that you create from the Profile Manager to the repository.New Features and Enhancements This section describes new features and enhancements to PowerCenter 7. and MELCOM-kana. You can determine unique rows for a source based on a selection of columns for the specified source. Define mapping. pmcmd passes variables and values in the file to the PowerCenter Server. pmcmd. PowerCenter supports additional Japanese language code pages. you can configure the session to create multiple threads to read the flat file source. and workflow prefixes. When you use a local parameter file. and workflow prefixes for the mappings. Data Profiling ♦ Data sampling. The PowerCenter Server can write all rows. You can specify the type of verbose data you want the PowerCenter Server to write to the Data Profiling warehouse. and workflows generated when you create a data profile. session. ♦ ♦ ♦ ♦ ♦ ♦ PowerCenter Server ♦ ♦ ♦ Code page.1. You can configure a maximum number of patterns and a minimum pattern frequency.1. Session enhancement. You can use parameter files that reside on a local machine with the Startworkflow command in the pmcmd program. such as JIPSEkana. Verbose data enhancements. session.1.1 This section describes new features and enhancements to PowerCenter 7.1. the rows that meet the business rule. When you create multiple partitions for a flat file source session. or for a specified number of rows starting with the first row. The Designer displays profile mappings under a profile mappings node in the Navigator.

you can connect to IBM. You can export or import multiple objects at a time. Reserved word support. Oracle. The Repository Server runs on SuSE Linux. PowerCenter uses Oracle OS Authentication when the user name for an Oracle connection is PmNullUser. GIF. JPEG. Enable enhanced security when you create a relational source or target connection in the repository. Oracle. When you load to Teradata using an external loader. or lookup table name or column name contains a database reserved word. You can now use Oracle OS Authentication to authenticate database users. Update a connection attribute value when you update the connection. and work table names by specifying different tables on the same or different Teradata database. and Sybase repositories. You do not need to know a database user name and password. Repository Server ♦ pmrep. target. When you export metadata. If any source. and Sybase sources. You can exchange source and target metadata with other BI or data modeling tools. you can pass attachments through the requests or responses in a service session. Preface xxv . the PowerCenter Client creates a file format recognized by the target tool. ♦ SuSE Linux support. you can also override the error.txt.♦ SuSE Linux support. targets. DB2. On SuSE Linux. DB2. When the PowerCenter Server initializes a session.txt in the PowerCenter Server installation directory. Depending on the loader you use. you can connect to IBM. The document type you can attach is based on the mime content of the WSDL file. the PowerCenter Server places quotes around matching reserved words when it executes SQL against the database. Web Services Provider ♦ Attachment support. you can create and maintain a file. If the file exists. and repositories using native drivers. such as Business Objects Designer. or PDF. Use ODBC drivers to access other sources and targets. you can now override the control file. ♦ ♦ Repository ♦ Exchange metadata with other tools. log. reswords. Oracle OS Authentication allows you to log on to an Oracle database if you have a logon to the operating system. Teradata external loader. Security ♦ Oracle OS Authentication. When you import web service definitions with attachment groups. containing reserved words. You can use pmrep to perform the following functions: − − − Remove repositories from the Repository Server cache entry list. You can attach document types such as XML. it searches for reswords. The PowerCenter Server runs on SuSE Linux. On SuSE Linux.

You can create multiple partitions in a session containing web service source and target definitions. You can also pivot the view row. and options. Data Profiling ♦ ♦ Data Profiling for VSAM sources. ♦ ♦ ♦ ♦ ♦ ♦ Documentation ♦ ♦ Web Services Provider Guide. This book consolidates XML information previously documented in the Designer Guide. Auto profiles now include the Aggregator function. It also includes information from the version 7. resize columns in a report.0 Web Services Hub Guide. You can now select the columns or groups you want to include in an auto profile and enable verbose mode for the Distinct Value Count function. Workflow Administration Guide. connectivity. Informatica provides licenses for product. Aggregator function in auto profiles.1. and partitions in the session. Source View in the Profile Manager. XML ♦ Multi-level pivoting. You can now view data profiles by source definition in the Profile Manager. Creating auto profile enhancements. You can now create a data profile for VSAM sources. XML User Guide. You can now create data profiles with source-level functions and write data to the Data Profiling warehouse in verbose mode. PowerCenter 7. Purging data from the Data Profiling warehouse. Prepackaged domains. Informatica provides a set of prepackaged domains that you can include in a Domain Validation function in a data profile.♦ Pipeline partitioning. targets. Licensing Informatica provides licenses for each CPU and each repository rather than for each installation. You can now purge data from the Data Profiling warehouse. You can now pivot more than one multiple-occurring element in an XML view. You can now view PowerCenter Data Profiling reports in a separate browser window.1 This section describes new features and enhancements to PowerCenter 7. This is a new book that describes the functionality of Real-time Web Services. PowerCenter Data Profiling report enhancements. and view verbose data for Distinct Value Count functions. You store xxvi Preface . Support for verbose mode for source-level functions. and Transformation Guide. The PowerCenter Server creates a connection to the Web Services Hub based on the number of sources.

and the command line program. ♦ ♦ Repository ♦ Exchange metadata with business intelligence tools. You can compare objects in an XML file to objects in the target repository when you import objects. You can now read and write CLOB/BLOB datatypes. You can export metadata to and import metadata from other business intelligence tools. pmlic. Increased repository performance.the license keys in a license key file. You can also use pmrep to create. Partitioning enhancements. The PowerCenter Server now reads a block of rows at a time. such as Cognos Report Net and Business Objects.1 MX views in its schema. and deploy group history. This improves performance when PowerCenter accesses the repository. REP_VERSION_PROPS allows you to see the version history of all objects in a PowerCenter repository. or enable a repository. You can now run 64-bit PowerCenter Servers on AIX and HP-UX (Itanium). PowerCenter Metadata Reporter PowerCenter Metadata Reporter modified some report names and uses the PowerCenter 7. disable. PowerCenter Server processing enhancements. This improves processing performance for most sessions. truncate log files. and delete a folder. back up. ♦ ♦ Preface xxvii . You can choose to skip MX data. MX views. PowerCenter now identifies and updates statistics for all repository tables and indexes when you copy. If you have the Partitioning option. delete a relational connection from a repository. the PowerCenter Server Setup. pmrep. you can define up to 64 partitions at any partition point in a pipeline that supports multiple partitions. or restore a repository. and restore repositories. REP_SERVER_NET and REP_SERVER_NET_REF views allow you to see information about server grids. PowerCenter Server ♦ ♦ ♦ ♦ 64-bit support. Object import and export enhancements. MX views have been added to help you analyze metadata stored in the repository. and run multiple pmrep commands sequentially. You can increase repository performance by skipping information when you copy. You can use pmrep to back up. workflow and session log history. modify. upgrade. Repository Server ♦ Updating repository statistics. delete repository details. CLOB/BLOB datatype support. You can manage the license files using the Repository Server Administration Console.

the Designer invokes the Flat File Wizard. or a collection of all older versions of objects. The query can return local objects that are checked out. You can now create an XML Parser transformation or an XML Generator transformation to parse or generate XML inside a pipeline.Transformations ♦ Flat file lookup. When you use a dynamic lookup cache. you can choose whether the PowerCenter Server outputs old or new values from the lookup/output ports when it updates a row. Midstream XML transformations. Real-time Web Services allows you to create services using the Workflow Manager and make them available to web service clients through the Web Services Hub. ♦ xxviii Preface . When you create a Lookup transformation using a flat file as a lookup source. The quality of printed workspace has improved. The PowerCenter Server can perform parallel processing of both requestresponse and one-way services. The XML transformations enable you to extract XML data stored in relational tables. such as TIBCO or IBM MQSeries. ♦ ♦ ♦ ♦ Usability ♦ ♦ Viewing active folders. Custom transformation API enhancements. The Designer and the Workflow Manager highlight the active folder in the Navigator. Also. You can use the Union transformation to merge multiple sources into a single pipeline. You can install the Web Services Hub on a JBoss application server. Enhanced printing. Web Services Hub. the PowerCenter Server can ignore some ports when it compares values in lookup and input ports before it updates a row in the cache. Dynamic lookup cache enhancements. Use these functions to take advantage of the PowerCenter Server processing enhancements. The Custom transformation API includes new array-based functions that allow you to create procedure code that receives and outputs a block of rows at a time. The Union transformation is similar to using the UNION ALL SQL statement to combine the results from two or more SQL statements. You can also run object queries based on the latest status of an object. You can also extract data from messaging systems. You might want to output old values from lookup/output ports when you use the Lookup transformation in a mapping that updates slowly changing dimension tables. You can now perform lookups on flat files. Union transformation. the latest version of checked in objects. Web Services Provider ♦ Real-time Web Services. Version Control You can run object queries that return shortcut objects. You can also use a lookup file parameter if you want to change the name or location of a lookup between session runs. The Web Services Hub now hosts Real-time Web Services in addition to Metadata Web Services and Batch Web Services. such as data stored in a CLOB column.

Midstream XML transformations. Synchronizing XML definitions. Workflow Monitor The Workflow Monitor includes the following performance and usability enhancements: ♦ ♦ ♦ ♦ ♦ ♦ When you connect to the PowerCenter Server. You can open multiple instances of the Workflow Monitor on one machine. In a view with hierarchy relationships. You can use XML schemas that contain simple and complex datatypes. You can simultaneously monitor multiple PowerCenter Servers registered to the same repository. Additional options for XML definitions. When you import XML definitions. the Designer creates separate entities for references and multiple-occurring elements. You can create views. XML files. DTD files. The Workflow Monitor includes improved options for filtering tasks by start and end time. XML Support PowerCenter XML support now includes the following features: ♦ ♦ Enhanced datatype support. You can also extract data from messaging systems. When you create views with entity relationships. you can choose how you want the Designer to represent the metadata associated with the imported files. The XML transformations enable you to extract XML data stored in relational tables. see PowerCenter Connect for Web Services User and Administrator Guide. For more informations. The Workflow Monitor displays workflow runs in Task view chronologically with the most recent run at the top. You can synchronize an XML definition with any repository definition or file used to create the XML definition. targets. you no longer distinguish between online or offline mode. ♦ ♦ ♦ Preface xxix . the Designer expands each element and reference under its parent element. add or delete columns from views. You can edit XML views and relationships between views in the workspace. You can synchronize one or more XML definition when the underlying schema changes. You can remove the Navigator and Output window. or schema files. You can now create an XML Parser transformation or an XML Generator transformation to parse or generate XML inside a pipeline. including relational sources or targets. and transformations to call web services hosted by other providers. such as data stored in a CLOB column. such as TIBCO or IBM MQSeries. XML workspace. It displays folders alphabetically. You can choose to generate XML views using hierarchy or entity relationships.Note: PowerCenter Connect for Web Services allows you to create sources. and define relationships between views.

♦ Support for circular references. You can output XML data to multiple XML targets. and evaluate join criteria. DTD files. If the size of the tree exceeds the cache size. you can determine implicit data type. The PowerCenter Client provides a Profile Manager and a Profile Wizard to complete these tasks. the XML data spills to disk in order to free up memory. User-defined commits. and XML schemas that use circular definitions. For example.” Upgrading metadata. Installation and Configuration Guide. It is comprised of two services for communication with the PowerCenter Server. Data Integration Web Services You can use Data Integration Web Services to write applications to communicate with the PowerCenter Server. suggest candidate keys. Data Integration Web Services is a web-enabled version of the PowerCenter Server functionality available through Load Manager and Metadata Exchange. You can specify the size of the cache used to store the XML tree. Support for multiple XML output files. you can profile source data to evaluate source data and detect patterns and exceptions.0. After you create a profiling warehouse. You can create XML files of several gigabytes in a PowerCenter 7. Documentation ♦ ♦ Glossary.” This chapter describes changes to repository ♦ xxx Preface . You can also define the file names for XML output files in the mapping. Then you can view reports based on the profile data in the profiling warehouse. This book now contains chapters titled “Connecting to Databases from Windows” and “Connecting to Databases from UNIX. Load Manager and Metadata Exchange Web Services running on the Web Services Hub. Circular references occur when an element is a direct or indirect child of itself. − − PowerCenter 7. The Installation and Configuration Guide contains a glossary of new PowerCenter terms.0 This section describes new features and enhancements to PowerCenter 7. you can create profiling mappings and run sessions. PowerCenter now supports XML files. Increased performance for large XML targets. The connectivity information in the Installation and Configuration Guide is consolidated into two chapters. Data Profiling If you have the Data Profiling option. The Installation and Configuration Guide now contains a chapter titled “Upgrading Repository Metadata. You can define commits to trigger flushes for XML target files. detect data patterns.1 XML session by using the following enhancements: − ♦ Spill to disk.

PowerCenter Metadata Reporter includes the following features: ♦ Metadata browsing. you can now choose to load from a named pipe. worklets. The Soundex function encodes a string value into a four-character string. The change in functionality for existing objects depends on the version of the existing objects. you can group PowerCenter Servers registered to the same repository into a server grid. You access the Informatica installation CD from the command line to create the control file and install the product. server load. Consult the upgrade information in this chapter for each upgraded object to determine whether the upgrade applies to your current version of PowerCenter. If you purchase the Server Grid option. When using external loaders on Windows. PowerCenter Metadata Reporter PowerCenter Metadata Reporter replaces Runtime Metadata Reporter and Informatica Metadata Reporter. PowerCenter Servers balance the workload among all the servers in the grid. External loading enhancements. You can use PowerCenter Metadata Reporter to analyze operational metadata. source and target tables. ♦ Installation ♦ Remote PowerCenter Client installation. The Metaphone function encodes string values. session errors. It uses the first character of the input string as the first character in the return value and encodes the remaining three unique consonants as numbers. Functions ♦ Soundex. including session load time. The session configuration object has new properties that allow you to define error logging. and warehouse growth. Metadata analysis. You can enable bulk loading when you load to IBM DB2 8. you can now choose to load from staged files. When using external loaders on UNIX. Distributed processing. You can specify the length of the string that you want to encode. METAPHONE encodes characters of the English language alphabet (A-Z). In a server grid.objects impacted by the upgrade process. It encodes both uppercase and lowercase letters in uppercase. Row error logging. You can use PowerCenter Metadata Reporter to browse PowerCenter 7. and distribute it to other users to install the PowerCenter Client. Preface xxxi ♦ ♦ . and transformations. SOUNDEX works for characters in the English alphabet (A-Z).1. Metaphone. session completion status. You can create a control file containing installation information.0 metadata. ♦ PowerCenter Server ♦ ♦ DB2 bulk loading. such as workflows. mappings. You can choose to log row errors in a central location to help understand the cause and source of errors.

update. Audit trail. groups. You can export and import multiple objects and objects types.♦ External loading using Teradata Warehouse Builder. Concurrent processing. This enables more efficient joins with minimal usage of memory and disk cache. You can export and import objects with or without their dependent objects. You can use pmrep to perform change management tasks. and permissions through the Repository Server Administration Console. You can also export objects from a query result or objects history. the repository maintains an association between your repository user name and your external login name. The ♦ ♦ xxxii Preface . Trusted connections. deploying. The deployment and object import commands require you to use a control file to define options and resolve conflicts. upsert. The Use Repository Manager privilege allows you to perform tasks in the Repository Manager. maintain labels. and change object status. You can choose to insert. You do not have to delete user names from the repository. ♦ ♦ ♦ Repository Server ♦ Object export and import enhancements. Teradata Warehouse Builder can simultaneously read from multiple sources and load data into one or more tables. the PowerCenter Server flags rows for insert. You can use Teradata Warehouse Builder to load to Teradata. importing. It writes a column in the target file or named pipe to indicate the update strategy. such as copy object. If you use LDAP. You can track changes to repository users. Additionally. You can now export and import objects using the Repository Manager and pmrep. You can apply the transformation logic to rows defined by transaction boundaries. checking in. the security module passes your login name to the external directory for authentication. You can now use a Microsoft SQL Server trusted connection to connect to the repository. ♦ ♦ Security ♦ LDAP user authentication. delete. When you log in to the repository. and listing objects. such as the Aggregator transformation. such as maintaining deployment groups and labels. pmrep commands. The control file uses these values to determine how to load data to the target. You can now use default repository user authentication or Lightweight Directory Access Protocol (LDAP) to authenticate users. The PowerCenter Server now reads data concurrently from sources within a target load order group. You can now use real-time processing in sessions that also process active transformations. The Repository Agent logs security changes to a log file stored in the Repository Server installation directory. You can now use data driven load mode with Teradata external loaders. The repository maintains a status for each user. Real time processing enhancements. Mixed mode processing for Teradata external loaders. Use Repository Manager privilege. privileges. exporting. You can also use pmrep to run queries. When you select data driven loading. or delete data. or update. You can perform the same tasks in the Designer and Workflow Manager if you have the Use Designer and Use Workflow Manager privileges. You can now enable or disable users from accessing the repository by changing the status.

Each version is a separate object with unique properties. and workflows in the Workflow Manager. If you want to permanently remove an object version. Custom transformations operate in conjunction with procedures you create outside of the Designer interface to extend PowerCenter functionality. track changes. such as changes to folder properties. you can purge it from the repository. and the properties a mapping developer can modify. distribute the template with the DLL or shared library you develop. ♦ ♦ ♦ ♦ Preface xxxiii . and you can compile the procedure with any C compiler. Delete or purge a version. adding or removing a user or group. You can compare tasks. and use deployment groups to copy specific groups of objects from one repository to another. The Custom transformation replaces the Advanced External Procedure transformation. You can create templates that customize the appearance and available properties of a Custom transformation you develop. Compare objects. worklets. control development on the object. Check out and check in versioned objects. Deployment. Version control allows you to maintain multiple versions of an object. Unlike copying a folder. When you create a Custom transformation template. ♦ Joiner transformation. Version control in PowerCenter includes the following features: ♦ Object versioning. You can check out and reserve an object you want to edit. You can use the Joiner transformation to join two data streams that originate from the same source. Version Control The PowerCenter Client and repository introduce features that allow you to create and manage multiple versions of objects in the repository. You can create Custom transformations with multiple input and output groups. The Repository Manager and Workflow Manager allow you to compare two repository objects of the same type to identify differences between them. You can also compare different versions of the same object. You can delete an object from view and continue to store it in the repository. and check in the object when you are ready to create a new version of the object in the repository. The PowerCenter Client tools allow you to compare objects across open folders and repositories. You can recover or undelete deleted objects. This gives you greater control over the specific objects copied from one repository to another. You can specify the icons used for transformation. the colors. and adding or removing privileges. sessions. copying a deployment group allows you to copy a select number of objects from multiple folders in the source repository to multiple folders in the target repository. This allows you to store multiple copies of a given object during the development cycle.audit trail log contains information. You can compare Designer objects and Workflow Manager objects in the Repository Manager. Individual objects in the repository are now versioned. Transformations ♦ Custom transformation.

Increased performance for large XML files. This allows you to see the changes made to an object over time. declare multiple namespaces. The XML wizard allows you to view the structure of XML schema. This allows you to associate multiple objects in groups defined by the label. You can use XPath to locate XML nodes.♦ Deployment groups. XML schemas also allow you to define some complex datatypes. You can create a query that specifies conditions to search for objects in the repository. increase performance for large XML files. you can set commits and periodically flush XML data to the target instead of writing all the output at the end of the session. You can view a history that includes all versions of an object and compare any version of the object in the history to any other version. ♦ ♦ ♦ XML Support PowerCenter contains XML features that allow you to validate an XML file against an XML schema. You can now copy objects from all the PowerCenter Client tools using the copy wizard to resolve conflicts. A label is an object that you can apply to versioned objects in the repository. You can copy objects within folders. Within the Designer. Comparing objects. XML target enhancements. You can use an XML schema to validate an XML file and to generate source and target definitions. XML schemas allow you to declare multiple namespaces so you can use prefixes for elements and attributes. You can also compare all objects from within the Repository Manager. XPath support. You can make a private query. When you process an XML file or stream. You can also configure the PowerCenter Server to not output empty elements to the XML target. to other folders. Labels. and parse or generate XML data from various sources. you can also copy segments of mappings to a workspace in a new folder or repository. and to different repositories. format your XML file output for increased readability. or create a dynamic deployment group that uses a query to populate the group. You can create a static deployment group that you manually add objects to. XML support in PowerCenter includes the following features: ♦ XML schema. You can choose to append the data to the same target file or create a new target file after each flush. or you can share it with all users in the repository. improve query results. and organize groups of objects for deployment or export and import. You can save queries for later use. ♦ ♦ ♦ Usability ♦ Copying objects. Track changes to an object. You can use labels to track versioned objects during development. use XPath to locate XML nodes. You can format the XML target file so that you can easily view the XML file in a text editor. You can compare workflows and tasks from the Workflow Manager. ♦ xxxiv Preface . Queries. You can create a deployment group that contains references to objects from multiple folders across the repository.

workflows. the Workflow Manager accesses the repository to retrieve the last-saved version of the object. Before you edit or delete versioned objects. you can choose to propagate changed attributes throughout the mapping. expressions. Validate multiple objects. Enhanced partitioning interface. Refresh session mappings. or workflows. You can validate sessions. View dependencies. Viewing dependencies help you modify objects and composite objects without breaking dependencies. you can refresh a session mapping. The Designer propagates ports. ♦ ♦ ♦ ♦ ♦ ♦ Preface xxxv . In the Workflow Manager. The Session Wizard is enhanced to provide a graphical depiction of a mapping when you configure partitioning. and conditions based on the direction that you propagate and the attributes you choose to propagate. The PowerCenter Client writes messages in the Output window that describe why it invalidates a mapping or workflow when you modify a dependent object. you can view dependencies to see the impact on other objects. mappings. You can save and optionally check in objects that change from invalid to valid status as a result of the validation. You can validate multiple objects in the repository without fetching them into the workspace. mapplets. targets. and worklets. When you do this. mappings. You can now revert to the last saved version of an object in the Workflow Manager. You can view parent and child dependencies and global shortcuts across repositories. Revert to saved. Enhanced validation messages.♦ Change propagation. such as sources. When you edit a port in a mapping.

Provides information to help you create and run workflows in the Workflow Manager. Provides basic tutorials for getting started. Troubleshooting Guide. users. Lists error messages that you might encounter while using PowerCenter. Includes information to help you create mappings. This guide also provides information about how to use the web services that the Web Services Hub hosts. Provides information to install PowerCenter Connect for JMS. Provides information on how to create and configure each type of transformation in the Designer. and transformations. Batch Web Services. XML User Guide. Transformation Guide. Includes information on running sessions with XML data. Provides information you need to install and configure the Web Services Hub. folders. Installation and Configuration Guide. Also includes details on using the midstream XML transformations to parse or generate XML data within a pipeline. Also includes a description of the transformation datatypes used to process and transform source data. Provides information you need to create XML definitions from XML. Provides information needed to use the Designer. ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ xxxvi Preface . Workflow Administration Guide. and Metadata Web Services. Provides syntax descriptions and examples for each transformation function provided with PowerCenter. The Web Services Hub hosts Real-time Web Services. such as creating and maintaining repositories. Provides information about how to profile PowerCenter sources to evaluate source data and detect patterns and exceptions. and permissions and privileges. Provides information needed to install and configure the PowerCenter tools. Repository Guide. and load data into JMS messages. Each error message includes one or more possible causes and actions that you can take to correct the condition. including details on environment variables and database connections. or DTD files. and relational or other XML definitions. Includes details on functionality available in the Repository Manager and Administration Console. Designer Guide. extract data from JMS messages. Web Services Provider Guide. Also contains information on administering the PowerCenter Server and performance tuning. mapplets. Provides information needed to administer the repository using the Repository Manager or the pmrep command line program. Getting Started. PowerCenter Connect® for JMS® User and Administrator Guide.About Informatica Documentation The complete set of documentation for PowerCenter includes the following books: ♦ ♦ Data Profiling Guide. Transformation Language Reference. XSD. as well as monitor workflows in the Workflow Monitor. groups. build mappings.

About this Book The Repository Guide is written for the database administrator and developers who manage the repositories. The material in this book is available for online use. This is generic text that should be replaced with user-supplied values. This guide assumes you have knowledge of relational database concepts. This is the variable name for a value you enter as part of an operating system command. unless you follow the specified procedure. refer to the documentation accompanying your database products. This is a code example. This is an operating system command you enter from a prompt to run a task. The following paragraph provides additional facts. You should also be familiar with the interface requirements of your supporting applications. or mainframe systems in your environment. Document Conventions This guide uses the following formatting conventions: If you see… It means… The word or set of words are especially emphasized. For additional information on related database connectivity issues not covered by this guide. italicized text boldfaced text italicized monospaced text Note: Tip: Warning: monospaced text bold monospaced text Preface xxxvii . and the database engines. The following paragraph notes situations where you can overwrite or corrupt data. Emphasized subjects. flat files. The following paragraph provides suggested uses.

Other Informatica Resources In addition to the product manuals. newsletters.com.informatica. and locating your closest sales office. detailed descriptions of specific features. and tips and tricks to help you develop data warehouses. please email webzine@informatica. upcoming events. The site contains product information.informatica. training and education.com. the Informatica Knowledgebase. Visiting the Informatica Developer Network The Informatica Developer Network is a web-based forum for third-party software developers. Visiting the Informatica Web Site You can access Informatica’s corporate web site at http://www. the Informatica Webzine. This journal provides solutions to common tasks. go to http://my. The site contains information about Informatica. and implementation services.com. Informatica provides these other resources: ♦ ♦ ♦ ♦ ♦ Informatica Customer Portal Informatica Webzine Informatica web site Informatica Developer Network Informatica Technical Support Visiting Informatica Customer Portal As an Informatica customer. you can access the Informatica Customer Portal site at http:// my. as well as literature and partner information. user group information. its background.com. access to the Informatica customer support case management system (ATLAS). If you have any questions. and access to the Informatica user community.com xxxviii Preface . The services area of the site includes important information on technical support. To register for an account. Informatica Webzine. The Informatica Webzine is a password-protected site that you can access through the Customer Portal. You will also find product information.informatica. The Customer Portal has an online registration form for login accounts to its webzine and web support. Visiting the Informatica Webzine The Informatica Documentation team delivers an online journal.informatica. You can access the Informatica Developer Network at the following URL: http://devnet.

m.563.The site contains information on how to create. (local time) France Phone: +33 1 41 38 92 26 Hours: 9 a. You can request a user name and password at http://my. . White Waltham Maidenhead.m.m.m.6 p. Obtaining Technical Support There are many ways to access Informatica technical support. 6 Waltham Park Waltham Road.5800 Fax: 650. (local time) Netherlands Phone: +31 306 082 089 Hours: 9 a. .5:30 p.m.m.m.informatica. . You can call or email your nearest Technical Support Center listed below or you can use our WebSupport Service.com.213. (local time) Preface xxxix .com Africa / Asia / Australia / Europe Informatica Software Ltd.385. (local time) Germany Phone: +49 1805 702 702 Hours: 9 a. . (local time) Singapore Phone: +65 322 8589 Hours: 9 a.5:30 p. WebSupport requires a user name and password.5:30 p.9489 Hours: 6 a.m.m. (local time) Switzerland Phone: +41 800 81 80 70 Hours: 8 a.5 p. (PST/PDT) email: support@informatica. (GMT) email: support_eu@informatica. Berkshire SL6 3TN Phone: 44 870 606 1525 Fax: +44 1628 511 411 Hours: 9 a.m.m. North America / South America Informatica Corporation 2100 Seaport Blvd. market.m.m.com Belgium Phone: +32 15 281 702 Hours: 9 a.m.m. Redwood City.m. . .5:30 p. . CA 94063 Phone: 866.5 p. .5:30 p.6332 or 650. and support customer-oriented addon solutions based on Informatica’s interoperability interfaces.

xl Preface .

6 Understanding Metadata. 9 Administering Repositories. 3 Repository Connectivity. 16 1 .Chapter 1 Understanding the Repository This chapter covers the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 13 Version Control. 4 Repository Server Notifications. 2 Repository Architecture. 11 PowerCenter Domains.

permissions. the Repository Server connects the client application directly to the Repository Agent process. When you configure shared folders in a repository. that you can create or modify using the PowerCenter Client tools. You can back up the repository to a binary file. Metadata describes different types of objects. You can connect multiple repositories in a domain. such as mappings or transformations. For each repository database it manages. The Repository Server uses multiple Repository Agent processes to manage multiple repositories on different machines on the network. the Repository Server uses a process called the Repository Agent to access the database tables. Create folders. You can create user and group profiles and configure folder permissions. The repository also stores administrative information such as user names. You can store multiple versions of objects in a versioned repository. and deployment. PowerCenter Client tools and the PowerCenter Server communicate with the Repository Server over TCP/IP. or metadata. Administer the repository using the Repository Manager client tool or the pmrep and pmrepagent command line programs. you can enable the repository for version control. You can restore the repository from a binary backup file. Enabling version control also allows you to perform change management tasks such as version comparison. All repository client applications access the repository database tables through the Repository Server. change tracking. querying. The Repository Server uses native drivers to communicate with the repository database. The Repository Server also notifies you when objects you are working with are modified or deleted by another user. Sharing objects allows you to reuse metadata. The PowerCenter Server uses repository objects to extract. labeling. 2 Chapter 1: Understanding the Repository . Configure security. You can copy the repository to another database. Restore. Delete. transform. you can share the objects in the folder with other repositories in the domain. and load data. You can delete all of the repository tables on the database. and privileges. The Repository Server protects metadata in the repository by managing repository connections and using object locking to ensure object consistency. Repository administration tasks include the following: ♦ ♦ ♦ ♦ ♦ ♦ Back up. Copy. The repository uses database tables to store metadata. You can create folders in the repository to organize metadata. passwords.Overview The PowerCenter repository is a relational database managed by the Repository Server that stores information. If you purchase the Team-Based Development option with PowerCenter. When a client application connects to the repository. used by the PowerCenter Server and Client tools.

The Repository Server configures and manages a Repository Agent process for each registered repository database. pmrep and pmrepagent. The Repository Server manages repository connection requests from client applications. When you start the PowerCenter Server. The Repository Server Administration Console allows you to manage the Repository Server and repositories. transform. Use pmrepagent to perform repository functions such as restoring and deleting repositories. Use pmrep to perform repository administration tasks such as listing repository objects. The repository database tables contain the instructions required to extract. When you run a workflow. The Repository Server accepts client connections and requests from the following PowerCenter applications: ♦ The PowerCenter Client tools. ♦ ♦ ♦ Repository Architecture 3 . The Repository Agent uses object locking to ensure the consistency of metadata in the repository. The Repository Agent is a multi-threaded process that fetches. the PowerCenter Server writes workflow status information to the repository. Use the Workflow Manager to store workflow metadata. it connects to the repository to schedule workflows. You can use multiple Repository Servers to manage repositories in a domain. Repository client applications access the repository database tables through the Repository Server. and updates metadata in the repository database tables. During the workflow run. The Repository Server managing the local repository communicates as a client application with the Repository Server managing the global repository. inserts. the PowerCenter Server retrieves workflow task and mapping metadata from the repository. The Repository Server can manage multiple repositories on different machines on the network. Use the Designer to create and store mapping metadata in the repository. The PowerCenter Server.Repository Architecture The PowerCenter repository resides on a relational database. Other Repository Servers. and load data. and PowerCenter Server registration information in the repository. Use the Workflow Monitor to retrieve workflow run status information and session logs written by the PowerCenter Server. Use the Repository Manager to organize and secure metadata by creating folders and creating users and groups. connection object information. and creating and editing users and groups.

it requires only one connection. pmrep. For example. The Repository Agent process uses native drivers to communicate directly with the repository database.Repository Connectivity PowerCenter applications such as the PowerCenter Client. and the Repository Agent re-uses them to service requests from client tools or the server. and repository client applications: Figure 1-1. Configure the Repository Server TCP/IP port number when you install the Repository Server. The PowerCenter Server opens additional connections to the Repository Agent process for each Load Manager and DTM process. The Repository Agent creates new database connections only if all the current connections are in use. the Repository Agent opens ten connections. Figure 1-1 illustrates the connectivity between the Repository Server. PowerCenter Server. The Repository Agent process supports multiple connections from each client. Each client tool opens a separate connection to the Repository Agent process. The Repository Agent maintains a pool of database connections for client applications. The Repository Server uses one Repository Agent process for each repository database. The Repository Server stores the connectivity information required for the Repository Agent process to connect to the repository database. and pmrepagent connect to the repository through the Repository Server. These connections remain open. PowerCenter Repository Connectivity 4 Chapter 1: Understanding the Repository . You can set the maximum number of open connections for a repository by setting the Database Pool Size parameter in the repository configuration file. PowerCenter applications communicate with the Repository Server through a specified port over a TCP/IP connection. It reuses the same database connection for all the requests. If the ten clients send requests simultaneously. if ten clients send requests to the Repository Agent one at a time. repository database.

the Repository Server. and the repository database. The Repository Server starts the Repository Agent process for the repository database. 4. or deleted. Decrease the number of network hops between the repository client application.The following process describes how the Repository Server connects a repository client application to the repository: 1. 2. modified. Check the hard disk on the repository database machine. The client application sends a repository connection request to the Repository Server. 3. Slow disk access on the repository database can slow metadata transactions and repository performance. The Repository Server can manage a repository residing on a database on a different machine on the network. Have your system administrator determine if your network runs at an optimal speed. The Repository Server verifies connectivity information for the target repository. 5. The Repository Server uses the Repository Agent process to communicate with the repository database server and perform repository metadata transactions for the client application. Use the following guidelines when you configure your repository environment: ♦ Improve network speed. The Repository Server monitors the repository. and notifies the client application when objects in the repository are created. ♦ Repository Connectivity 5 . Have the system administrator evaluate the hard disk on the repository database machine. Slow network connections can increase transaction times for metadata and slow repository performance.

see “Repository Manager Tasks” on page 516. you must configure the Designer to receive Repository Server notifications. or deleted: ♦ ♦ ♦ ♦ ♦ ♦ Mappings Mapplets Shortcuts Source definitions Target definitions Transformations To receive any type of notification message about an object. Receiving Notifications in the Designer The Designer receives notification messages from the Repository Server when the following objects are created.Repository Server Notifications The Repository Server sends notification messages when users create. see “Mappings” in the Designer Guide. For example. the object must be open in the workspace. 6 Chapter 1: Understanding the Repository . or delete repository objects. The Repository Server notifies you of the change so that you know the source in your mapping is out of date. In this case. suppose you are working with a mapping in the Designer. Another user opens and edits the properties of a source definition used in the mapping and save the changes to the repository. Receiving Notifications in the Repository Manager The Repository Manager receives notification messages from the Repository Server when the following objects are created. or deleted: ♦ ♦ ♦ Folders Users Groups You must be connected to the repository to receive notifications about folders. Each PowerCenter Client tool and the PowerCenter Server receive notification messages for different types of objects. Repository Server notification messages keep you informed of ongoing changes to metadata you are working with. For details on configuring the Designer to receive Repository Server notifications. modified. and the folder containing the object must be open in the Navigator. you can update the mapping with the version of the source definition saved in the repository. see “Using the Designer” in the Designer Guide. For information on the privileges and permissions to receive user and group notifications. modified. For more information. modify. To receive a modification or deletion notification.

PowerCenter Server Notifications The PowerCenter Server receives notification messages from the Repository Server when the following objects are created. For details on configuring the Workflow Monitor to receive Repository Server notifications. you must configure the Workflow Monitor to receive Repository Server notifications. you must open the object in the workspace. or deleted: ♦ ♦ ♦ ♦ Sessions Tasks Workflows Worklets To receive any type of notification message about an object. Receiving Notifications in the Workflow Monitor The Workflow Monitor receives notification messages from the Repository Server when the following objects are created. For details on configuring the Workflow Manager to receive Repository Server notifications. Repository Server Notifications 7 . The Repository Server also sends the PowerCenter Server a notification message when it copies a folder into the repository. see “Configuring the Workflow Manager” in the Workflow Administration Guide. you must configure the Workflow Manager to receive Repository Server notifications.Receiving Notifications in the Workflow Manager The Workflow Manager receives notification messages from the Repository Server when the following objects are created. or deleted: ♦ ♦ ♦ Workflows Schedulers Folders If you delete a folder. see “Monitoring Workflows” in the Workflow Administration Guide. and the folder containing the object must be open in the Navigator. or deleted: ♦ ♦ Folders PowerCenter Servers To receive any type of notification message about an object. The PowerCenter Server reschedules all workflows in the folder when it receives the notification. To receive a modification or deletion notification. the PowerCenter Server removes workflows from the schedule when it receives the notification. and you must be connected to the repository. modified. modified. modified.

8 Chapter 1: Understanding the Repository . For more information on creating and sending notification messages. or to users connected to all of the repositories managed by a Repository Server.User-Created Notifications You can create and send notification messages to all users connected to a single repository. Use notification messages tell users to disconnect if you want to shut down the repository. see “Sending Repository Notifications” on page 74.

During a session. and load source and target data. or COBOL files that provide source data. Multi-dimensional metadata refers to the logical organization of data used for analysis in OLAP applications. You can use shortcuts to repository objects in shared folders. a repository. views. Transformations describe how the PowerCenter Server transforms data. or a domain. and add instances of the transformation to individual mappings or mapplets. A transformation generates. Target definitions. You use different PowerCenter Client tools to develop each kind of object. Use the Warehouse Designer tool in the Designer to import or create target definitions. transform. Mappings. You can create local shortcuts to shared folders within the same repository and global shortcuts to shared folders in the global repository of the domain. Use the Mapplet Designer tool in the Designer to create mapplets. Reusable transformations. Use the Designer to create shortcuts.Understanding Metadata The repository stores metadata that describes how to extract. Shortcuts. PowerCenter metadata describes several different kinds of repository objects. and any constraints applied to these columns. Use the Mapping Designer tool in the Designer to create mappings. Mappings can also include shortcuts. Mappings include source and target definitions and transformations. then add instances of the mapplet to individual mappings. column names and datatypes. reusable transformations. You can design a transformation that you can reuse in multiple mappings or mapplets within a folder. Use the Transformation Developer tool in the Designer to create reusable transformations. including the table name. Dimensions and cubes are most often used by end users of OLAP applications. XML files. and mapplets. the PowerCenter Server writes the transformed data to targets. Rather than recreate the same transformation each time. modifies. Detailed descriptions of database objects (tables. Mapplets. Transformations. You can design a mapplet to contain sets of transformation logic to be reused in multiple mappings within a folder. you can create a mapplet containing the transformations. A mapping specifies how to move and transform data from sources to targets. flat files. Use the Source Analyzer tool in the Designer to import and create source definitions. or XML files to receive transformed data. Detailed descriptions for database objects. Shortcuts to metadata in shared folders. Use the Warehouse Designer tool to create dimensions and cubes. you add transformations and configure them to handle data according to your business purpose. you can make the transformation reusable. Rather than recreate the same set of transformations each time. or passes data through ports that you connect in a mapping or mapplet. ♦ ♦ ♦ ♦ ♦ ♦ ♦ Understanding Metadata 9 . a source definition might be the complete structure of the EMPLOYEES table. When you build a mapping or mapplet. Use the Designer to create and edit the following repository objects: ♦ Source definitions. For example. Multi-dimensional metadata. a repository. or a domain. and synonyms). flat files. such as NOT NULL or PRIMARY KEY.

place it in a workflow. You can control access to a folder by configuring the folder permissions. You create a session for each mapping you want to run.For details on using the Designer to work with repository objects. For example. PowerCenter also allows you to extend the metadata stored in the repository by associating information with repository objects. and nest worklets in other worklets. Workflow tasks include commands. see “Version Control” on page 16. Workflow tasks are instructions the PowerCenter Server executes when running a workflow. you may wish to store the name of that person with the source definition. ♦ ♦ ♦ For details on working with repository objects using the Workflow Manager. You can run worklets in workflows. Folders organize and store metadata in the repository. You can also configure a repository user with privileges that allow the user to perform specific tasks in the repository. You can also configure a folder to share stored metadata with other repository users. Workflow tasks. and external loader connections in the Workflow Manager. Repository users have a user name and password that allow access to the repository. You create connection objects in the repository when you define database. when someone in your company creates a source definition. Sessions are workflow tasks that contain information about how the PowerCenter Server moves data through mappings. see “Metadata Extensions” on page 325. divided into tasks. User groups. see the Designer Guide and the Transformation Guide. and load data. For details on version control and change management. PowerCenter allows you to store multiple versions of metadata objects in the repository. see the Workflow Administration Guide. To run the session. Workflows. the PowerCenter Server uses to extract. Worklets are objects that represent a set of workflow tasks that allow you to reuse a set of workflow logic in several workflows. User groups organize individual repository users. For details on using metadata extensions. Connection objects. ♦ ♦ If you enable version control. You can assign privileges to a user group. Individual users inherit all privileges assigned to the user group. Use the Repository Manager to create and edit the following repository objects: ♦ Folders. Use the Workflow Designer in the Workflow Manager to create sessions. transform. decisions. transforming. and email notification. FTP. 10 Chapter 1: Understanding the Repository . Workflow tasks perform functions supplementary to extracting. A workflow is a set of instructions. The PowerCenter Client and Server use database connections to connect to the source and target databases. Each repository user belongs to at least one user group. timers. Use the Workflow Manager to create and edit the following repository objects: ♦ ♦ ♦ Database connections. You associate information with repository metadata using metadata extensions. Worklets. Users. Sessions. and loading data.

repository privileges. so its contents are available to all other folders in the same repository. If you plan to use the same object in several projects. You can configure a folder to be shared. and restore repositories. Although you can view the repository tables. folder permissions. The Repository Server uses the Repository Agent process to create and update the repository tables. you designate a user as the owner of the folder. For details on working with folders. Administering Repositories 11 . and then assign different folder permissions to that user. Security To secure data in your repository. You can restore the entire repository from a binary file. you can add folders to it. Warning: The Informatica repository tables have an open architecture. You can back up the repository to a binary file. When you create a folder. and maintain the repository. you might put it in the shared folder. For details on working with repositories. Folders let you organize repository objects. For example.Administering Repositories You use the Repository Manager to create. These tables store metadata in a specific format the PowerCenter Server and the PowerCenter Client tools use. see “Working with Folders” on page 165. and configuring permissions and privileges for users and groups. you can also make shortcuts to the table in folders in local repositories registered to the repository. providing a way to separate different types of metadata or different projects into easily identifiable areas. You can make shortcuts to the table in other folders in the same repository. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables. set up users and user groups and determine the repository privileges you want them to have. After you create a repository. You use the Repository Server Administration Console to copy. You can also copy all the repository tables to another database. the user’s group. see “Managing the Repository” on page 49 and “Configuring the Repository” on page 103. you can put a definition of the CUSTOMERS table that provides data for a variety of purposes in a shared folder. folder creation and organization. Creating Folders After you create the repository. If you are working in a domain. organize. you should never manually edit them through other utilities. Repository administration tasks include repository creation. back up. and others accessing the repository. user groups. Creating the Repository The Repository Manager connects to the repository database through the Repository Server. the repository provides a system of users. and object locking.

or backing up the repository.Privileges permit or restrict the ability for users to perform tasks such as creating mappings. For details on configuring repository security. 12 Chapter 1: Understanding the Repository . Permissions permit or restrict access to folders and objects in the repository. running sessions. see “Repository Security” on page 125.

PowerCenter Domains 13 . You can also copy objects in shared folders. the code pages of the local and global repository must be compatible. you can navigate to any local repository in the domain. simplify. required to create the global repository. and manage the process of developing and maintaining multiple data warehouses. To register a local repository. You can also use the Designer to create shortcuts to reference objects in other repositories. To copy objects from the local repository to the global repository. You can use one Repository Server to manage all of the repositories in the domain. You can connect repositories together within the domain. you need to have all of the following: ♦ ♦ ♦ A licensed copy of PowerCenter. ♦ ♦ ♦ A database created and configured for each repository. ♦ PowerCenter allows you to share data and metadata between global and local repositories by copying individual repository objects and entire folders within and between repositories. Compatible repository code pages. The hub of this system. or create copies of objects in non-shared folders. the global repository. Storing and reusing shared metadata.PowerCenter Domains The domain allows you to organize. Network connections between the Repository Servers and PowerCenter Servers. serves several purposes: ♦ Opening connections between repositories. the code page of the global repository must be a subset of each local repository code page in the domain. the global repository stores information needed to connect to each repository. The Repository Server accesses the repository faster if it is installed on the machine on which the repository resides. Local repositories can then use shortcuts to objects in the global repository shared folders. If you are connected to a local repository. A licensed copy of PowerCenter for each local repository you want to create. You can save any metadata that you plan to share across repositories in the global repository. If you are connected to a global repository. Building the Domain Before building your domain. A Repository Server installed and configured to manage the repositories. To preserve system security and to simplify the task of connecting from one repository to another. You can also use multiple Repository Servers to manage the repositories in the domain. you can navigate to the global repository without connecting to it separately. A domain consists of a single global repository and any number of local repositories.

You create a global repository by promoting an existing local repository. see “Creating or Promoting a Repository” on page 116. you need everyone in all parts of the organization to use the same calculation. or making other decisions. Register other repositories with the global repository. marketing. It also helps enforce standards for the design of transformations at the enterprise level. PowerCenter provides a mechanism for sharing metadata among multiple repositories. Once you make a repository a global repository. Once the local repository is registered. 3. you can connect to the global repository from the local repository. 14 Chapter 1: Understanding the Repository . The profitability calculation might appear in several mappings in the sales division repository. building a sales strategy. even in other repositories. Create user profiles for users performing cross-repository work. Although the user name and password must remain the same. Create a repository and configure it as a global repository. 2. The R&D. and accounting divisions also need to use the same calculation in many mappings in their repositories. see “Registering a PowerCenter Repository” on page 75. Sharing metadata can help you save time and reduce work by reusing metadata. you might want to reuse it in other mappings. based on variables such as production costs and marketing expenses. and to the local repository from the global. When you develop the component of a mapping that performs this calculation. For details on creating and configure a repository. the user can be a member of different user groups and can have a completely different set of privileges in each repository. If you can share the profitability calculation. see “Repository Security” on page 125. A user who needs to connect to multiple repositories must have an identical repository user name and password in each repository. you cannot demote it to a local repository.Connecting separate repositories into a domain is a three-step process: 1. For example. This calculation is likely to be complex. For details on registering repositories. you can be sure that everyone looks at the value of each product to the company in the same way. Reusing Metadata In a domain you frequently need to share metadata across repositories. For details on creating user profiles and configuring repository security. a sales division develops a standard calculation for the profitability of each product. Since profitability is important information when investing in product development.

perform the same profitability calculations. Often. If a folder is not shared. transforms. the throughput for the entire organization is lower than it could be. transform. A more efficient approach would be to read. each department may need to read the same product data from operational sources. see “Working with Folders” on page 165. For example. Or you can display date and time values in a standard format. and updates that have occurred in the PRODUCTS table since the last time you updated the central data store. you can use shortcuts to that folder in any repository in the domain. each folder within a repository might represent a different development project. Reusing Data The need to share data is just as pressing as the need to share metadata. If the shared folder is in a global repository. However. every project in the repository needs to store bug reports in a consistent format. you cannot create shortcuts to objects in the folder.Shared Folders You can configure folders in global and local repositories to be shared. and write the data to one central data store shared by all users. so you might put the source definition for the BUG_REPORTS table in a shared folder. For details on folders. PowerCenter Domains 15 . Once you designate a folder as shared. If each department reads. you might want to capture incremental changes to sources. For example. For example. For example. To improve performance further. several departments in the same organization need the same information. Shared folders are useful when you want to use the same repository objects in several projects within the same repository. and format this information to make it easy to review. you can improve performance by capturing only the inserts. you can still create copies of objects in non-shared folders. you can filter employee data that should remain confidential. and writes this product data separately. you can create shortcuts to objects in that folder. rather than reading all the product data each time you update the central data store. A central data store improves throughput at the level of the entire enterprise. You can use shortcuts in any other folder in the repository. The central data store also allows you to format data in a standard fashion. deletes. However. You can perform these and other data cleansing tasks when you move data into the central data store instead of performing them repeatedly.

You can create a deployment group that contains references to objects from multiple folders across the repository. and deploy metadata into production. and check in the object when you are ready to create a new version of the object in the repository. or create a dynamic deployment group that uses a query to populate the group. You can also compare any version of the object in the history to any other version. and organize groups of objects for deployment or import and export. or versions. You can recover. You can view an object history that includes all versions of the object. Queries. You can create a query that specifies conditions to search for objects in the repository. of an object. ♦ ♦ ♦ For more information on working with versioned objects. Each version is a separate object with unique properties. A versioned repository can store multiple copies. The PowerCenter Client tools allow you to compare objects across open folders and repositories. ♦ ♦ For more information on grouping versioned objects. You can make a private query. You can also roll back a deployment operation. or you can share it with all users in the repository. During development. you can enable version control for the repository. You can create a static deployment group that you manually add objects to. Delete or purge a version. PowerCenter version control features allow you to efficiently develop. You can use labels to track versioned objects during development. and Designer allow you to compare two repository objects of the same type to identify differences between them. Compare objects. The Repository Manager.Version Control If you have the Team-Based Development option. This allows you to associate multiple objects in groups defined by the label. You can use the following features to group versioned objects: ♦ Labels. see “Working with Versioned Objects” on page 199. mark development milestones. You can copy objects in a deployment group from one repository to another. copying a deployment group allows you to copy one or more objects from multiple folders in the source repository to multiple folders in the target repository. improve query results. A label is an object that you can apply to versioned objects in the repository. This allows you to see the changes made to an object over time. see “Grouping Versioned Objects” on page 217. You can check out and reserve an object you want to edit. You can also choose to copy part of a composite object. provided that the object is present in the target 16 Chapter 1: Understanding the Repository . Deployment groups. You can save queries for later use. Unlike copying a folder. deleted objects. you can purge it from the repository. You can delete an object from view and continue to store it in the repository. If you want to permanently remove an object version. or undelete. test. Track changes to an object. You can also compare different versions of the same object. Workflow Manager. you can use the following change management features to create and manage multiple versions of objects in the repository: ♦ Check out and check in versioned objects.

you can automate the process for copying deployment groups. This gives you greater control over the specific objects copied from one repository to another and allows you to update only those objects that were modified. You can also use pmrep to perform change management tasks. For more information on copying objects in a deployment group. For more information on using pmrep for change management. Version Control 17 . This allows you to use pmrep scripts and files to automate change management tasks. see “Copying Folders and Deployment Groups” on page 241.repository. see “Using pmrep and pmrepagent” on page 403. For example.

18 Chapter 1: Understanding the Repository .

37 Validating Multiple Objects. 20 Repository Manager Windows. 48 19 .Chapter 2 Using the Repository Manager This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 29 Working with Repository Connections. 42 Comparing Repository Objects. 34 Viewing Object Dependencies. 22 Adding and Removing a Repository. 45 Truncating Workflow and Session Log Entries. 30 Searching for Repository Objects.

the Main window. such as deleting a folder or unlocking an object. and Output windows. Dependency. The Navigator window allows you to connect to a repository. You can view dependency information for sources. Before you remove or change an object. navigate through the folders. Repository Manager Tasks You can use the Repository Manager to perform the following tasks: ♦ Add or remove a repository. The Output window also displays Repository Server notification messages. and Output windows. the Dependency window displays the dependency details when you select an object in the Navigator window. For more information. When you select an object in a node. You can import the file on a different machine and add the repository connection information to the client registry. see “Viewing Object Dependencies” on page 37. For more information. see “Searching for Repository Objects” on page 34. and the Output window. mappings. The Navigator window organizes the repository objects of the same type in each folder in groups called nodes. you can view dependencies to see the impact on other objects. and shortcuts. see “Adding and Removing a Repository” on page 29. If you add keywords to target definitions. and browse repository objects. You can dock and undock the Navigator. Search for repository objects or keywords. View object dependencies. You can add or remove multiple repositories to the Navigator window and client registry. You can connect to one repository or multiple repositories. ♦ ♦ ♦ 20 Chapter 2: Using the Repository Manager . such as copying. The Output window displays detailed information for complex repository operations. restoring. When you configure the Repository Manager to display object dependencies.Overview The Repository Manager allows you to navigate through multiple folders and repositories and perform basic repository tasks. see “Working with Repository Connections” on page 30. Note: Since the status of the repository changes as users access it. refresh your view of the repository before performing tasks. Repository Manager Windows The Repository Manager can display four main windows: the Navigator window. For more information. the Dependency window. Work with repository connections. you can view details for the object in the Main window. you can use a keyword to search for a target definition. You can also hide and display the Navigator. Dependency. or upgrading a repository. targets. For more information. You can export repository connection information from the client registry to a file. You can search for repository objects containing specified text.

see “Releasing Locks” on page 158. For details. For details. You can truncate all logs. You can truncate the list of session and workflow logs that the PowerCenter Server writes to the repository.♦ Compare repository objects. Terminate user connections. or truncate all logs older than a specified date. Exchange metadata with other business intelligence tools. For more information. see “Managing User Connections” on page 151. ♦ ♦ ♦ ♦ Overview 21 . For more information. You can export metadata to and import metadata from other business intelligence tools. see “Comparing Repository Objects” on page 45. see “Truncating Workflow and Session Log Entries” on page 48. Release locks. You can use the Repository Manager to release residual locks left by residual connections. Releasing a valid lock can result in repository inconsistencies. see “Exchanging Metadata” on page 313. Truncate session and workflow log entries. For more information. so only release a lock when you know that the locked object is not in use. You can use the Repository Manager to view and terminate residual user connections. such as Cognos ReportNet Framework Manager. The Repository Manager allows you to compare two repository objects of the same type to identify differences between the objects.

Progress Indicator 22 Chapter 2: Using the Repository Manager .Repository Manager Windows The Repository Manager has a main window and a status bar for information on the operation you are performing. The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1. the Status Bar reflects the connection in progress with a progress indicator. Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository.

To close a window: ♦ Click the small x in the upper right corner of the window. the Navigator and the Main windows appear. From the menu. Nodes.Displaying Windows The Repository Manager allows you to dock and undock the following windows: ♦ ♦ ♦ Navigator Dependency Output To dock or undock a window: ♦ Double-click the title bar. The Navigator window displays the following objects when they exist in the repository: ♦ ♦ ♦ ♦ ♦ Repositories. The Dependency window appears when you want to view dependencies. workflow logs. transformations. mapplets. 2. mappings. sources. Folders. Folders can be shared or not shared. Double-click the title bar. depending on the task you perform. workflows. Repository Manager Windows 23 . Repository objects displayed in the Navigator can include sources. and the Output window appears when the Repository Manager displays status messages. local. targets. Navigator Window Use the Navigator window to connect to a repository and navigate through the folders and objects in the repository. and session logs. However. Deployment groups contain collections of objects for deployment to another repository in the domain. To display a window: 1. and mappings. worklets. worklets. When you launch the Repository Manager. transformations. Repository objects. tasks. The Repository Manager displays windows as necessary. choose View. Nodes can include sessions. targets. drag the title bar toward or away from the Main window. tasks. Deployment groups. PowerCenter repositories can be standalone. workflows. Then select the window you want to open. sessions. Or. you can also configure the Repository Manager to hide or display any window. mapplets. or global.

24 Chapter 2: Using the Repository Manager . you can view all tabs on the Properties dialog box. Repository Manager Navigator Repositories Deployment Groups Shared Folder Mappings Nodes Workflows Viewing Properties You can view the properties of the objects in the Navigator by selecting the object. Note: If you enable versioning when you create the repository. You can also right-click the object in the Navigator and select Properties from the shortcut menu. For more information about object properties.Figure 2-2 shows the Navigator components: Figure 2-2. and then clicking the View Properties button in the toolbar. see “Viewing Version Properties” on page 203.

Note: You can double-click an object in the Main window to view its properties. to sort mappings by validity. Source Definition Object Properties Main Window The Main window of the Repository Manager displays details about the object selected in the Navigator. if you select a repository in the Navigator. To do this. Or. Click the heading again to reverse the order in which the mappings are sorted. For example. you might want the Valid column to appear first. then click the Valid column heading. The Repository Manager displays the columns in the new order until you change the display. select a node in the Navigator.Figure 2-3 shows the object properties for a source definition: Figure 2-3. Repository Manager Windows 25 . Sorting and Organizing You can sort items in the Main window by each of the columns. For example. on the left side of the Main window. to view detailed information about a particular repository object. For example. the Main window displays all the folders in the repository along with additional folder information. drill down on a node and select the object. select the mappings node. such as whether the folder is shared or in use. drag the Valid column heading to the desired location. Viewing Object Details To view information about repository objects. You can also change the order in which the columns appear.

Select a transformation to view details for the specified transformation ports. Displays properties for each source file associated with the session. The Target Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Displays properties for each deployment group in the selected repository. and other objects associated with the worklet. Displays session log information for the selected session. Select a mapplet to view the Transformations node containing the mapplet. tasks. The Workflow Logs node displays under each workflow in the Workflows node. Displays the properties for each mapplet in the selected node. Tasks Node Sessions Node Worklets Node Workflows Node Workflow Logs Node Session Logs Node Source Connections Node Source File Connections Node Target Connections Node 26 Chapter 2: Using the Repository Manager . Displays the properties for each target with the selected node. targets. Select a target definition to view details for each target definition port. Select a worklet to view the nodes for sessions. Displays workflow log information for the selected workflow. Displays the properties for each reusable transformation in the selected node. Select a mapping to view sources. Displays connection properties for each source connection associated with the session. Displays properties for each session in the folder. Displays properties for each worklet in the folder. Displays properties for each task in the selected node. Select a static deployment group to view details for deployment group objects. Select a workflow to view information for tasks and objects associated with the selected workflow. and transformation nodes that contain the sources. The Sessions Logs node displays under each session in the Sessions node. The Source File Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node.Table 2-1 shows the object details displayed in the Repository Manager Main window: Table 2-1. Displays connection properties for each target connection associated with the session. source connections and target connections nodes for the selected session. Displays the properties for each mapping in the node. Select a target in a mapping to view details for each port in the selected target definition. targets.and post-session email and commands. Object Details Displayed in Repository Main Window Node Repository Node Deployment Groups Node Sources Node Targets Node Transformations Node Mapplets Node Mappings Node Information Displayed Displays properties for each folder in the selected repository. Displays the properties for each source within the selected node. and transformations used in the mapping. The Source Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Select a session to view session logs. Select a task to view the task details. Displays properties for each workflow in the folder. The Main window also displays information about pre. Select a source definition to view details for each port in the selected source definition.

Figure 2-4 shows the Dependency window: Figure 2-4. When you view mapping dependencies. When you view shortcut dependencies. the left pane of the Dependency window lists the object for which you want dependency information. the Dependency window lists all sources or targets related to the selected object. Object Details Displayed in Repository Main Window Node Target File Connections Node Transformation Logs Node Information Displayed Displays properties for each target file associated with the session. Dependency Window Selected Object Dependencies The Dependency window can display the following types of dependencies: ♦ Source-target dependencies.Table 2-1. Mapping dependencies. if you select a reusable transformation. For information on using the Dependency dialog box. You can also view dependencies using the Dependency dialog box. You can view dependencies by using the menu items or the dependency buttons on the toolbar. see “Viewing Object Dependencies” on page 37. Dependency Window The Dependency window appears when you configure the Repository Manager to display dependencies. you view all mappings using that transformation and details about each mapping. For example. such as the repository and ♦ ♦ Repository Manager Windows 27 . Displays log details for each transformation in the session when you select the Transformation Logs node. you view all sources that provide data for that target. The Target File Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. if you select a target. as well as relevant information about those mappings. including relevant details about those sources or targets. the Dependency window lists all shortcuts to the selected object and relevant details. and the dependency information appears in the right pane of the window. When viewing dependencies. For example. When you view source-target dependencies. along with details about each source. the Dependency window lists all mappings containing the selected object. Shortcut dependencies.

and shortcuts. it displays dependencies for the object in the Navigator that you select.. the status bar displays the word Ready. see “Using the Designer” in the Designer Guide.folder in which the shortcut exists. however. When you edit an object referenced by shortcuts. mapplets. You can also view mapping object dependencies in the Designer. such as copying a folder. targets. For details. When you open the Dependency window. mappings. Figure 2-5 shows the Output window: Figure 2-5. when you connect to a repository. The Designer allows you to view dependencies for sources. transformations. the Repository Manager displays status messages in the status bar. With more complex operations. the status bar displays the following message: Accessing the repository. you can use the Repository Manager to see which folders contain the shortcut. For example. When you perform a more lengthy operation.. Once connected to the repository. the Repository Manager displays detailed information in the Output window. Output Window You can change the font type and size displayed in the output window by right-clicking the window and selecting Change Font. Output Window When possible. 28 Chapter 2: Using the Repository Manager . the Repository Manager writes details about the operation into the Output window.

select the repository you want to remove. For details on creating a repository. but you can no longer access it. For details on connecting to a repository. and click Delete. Removing a Repository When you remove a repository. 2. you can also remove it from the PowerCenter Client registry. see “Creating or Promoting a Repository” on page 116. After you remove a repository from the Navigator. 3. When a message box appears. 2.Adding and Removing a Repository You can add or remove a repository from the Repository Manager. Adding a Repository Add a repository when a repository already exists but does not appear in the Navigator of the PowerCenter Client. You add a repository when you want to access an existing repository from the PowerCenter Client. To add a repository: 1. Adding a repository to the Navigator window does not create the repository. 4. you remove it from the Navigator of the PowerCenter Client. choose Repository-Add Repository. see “Connecting to a Repository” on page 30. To remove a repository from the client registry: 1. Select the repository you want to remove. you can connect to it. To reverse this action. 2. click OK to remove the repository. To remove a repository from the Navigator: 1. The Repository Manager adds the repository to the Navigator. After you remove a repository. you need to add the repository and reconfigure the connection information. In the Repository Manager. The repository remains intact. select the repository you want to remove. In the Navigator of the Repository Manager. Choose Tools-Remove Repository. After adding a repository. You remove a repository when you want to remove access to an existing repository. you can reverse your action by adding it. Press Delete. In the Navigator of the Repository Manager. Enter the repository name and your repository user name. Adding and Removing a Repository 29 .

You can also choose Repository-Connect. To connect to a repository for the first time: 1. you can connect to single or multiple repositories. you can export that information and import it to a different client machine using the same operating system. 3. The repository administrator can connect to the repository as Administrator and change the default password. Click the Connect button. 2. Enter the database user name and password used to create the repository. The Repository Manager also saves repository connection information in the registry. Connecting to a Repository You can connect to a repository for the first time or connect to a repository you have previously accessed. Launch the PowerCenter Client tool and select the repository you want to connect to in the Navigator window. The default password for Administrator is Administrator. see “Installing and Configuring the Repository Server on Windows. When you create a repository. 4. The Connect to Repository dialog box appears. You can connect to a repository for the first time or connect to a repository you have previously accessed. see “Default Groups” on page 127. To simplify the process of setting up client machines. For details on starting and stopping the Repository Server. For more information on the default users in the Administrators group. the Repository Server creates two default users in the Administrators group. the database user name used to create the repository and Administrator.” or “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. 30 Chapter 2: Using the Repository Manager . Verify the Repository Server is started.Working with Repository Connections From the Repository Manager.

Connecting to Multiple Repositories The PowerCenter Client allows you to connect to multiple repositories and work in multiple folders at one time. Click Connect. Working with Repository Connections 31 . Alternatively. 6. Click More. Launch the PowerCenter Client tool. Click Connect. To make these connections. 2. you can also connect from a local repository to a global repository and from a global repository to any local repository in a domain. The password must be in 7-bit ASCII. When working in a domain. you must have identical logins in both repositories. In the Navigator. Enter your repository user name and password. Enter the host name of the machine the Repository Server is running on and the port number the Repository Server uses for connections. To connect to multiple repositories separately: 1.5. 3. you can select the repository icon and choose Repository-Connect. select a repository and choose Repository-Connect. Existing folders in the repository now appear beneath the repository. and a new icon representing the repository appears in the Repository Manager. connect from the local repository to the global. Folders within the repository now appear underneath the icon for that repository. 7. Select the icon for the repository and click the Connect button on the toolbar. To create a global shortcut. The Connect to Repository dialog box expands. The Repository Server now opens a connection to the database. To connect to a repository that you have accessed before: 1. 4.

If the repository is part of a domain. use the extension . Double-click the icon for the local repository you wish to access. as well as folders in the local repository. To connect from the global repository to a local repository: 1. you can access its contents. Exporting/Importing Repository Connection Information The Repository Manager saves repository connection information in the registry. To connect from a local repository to the global repository: 1. In the Repository Manager. an icon for the global repository appears beneath the local repository icon.reg. You now open a connection to the global repository. 2. 2. Connect to the local repository. By double-clicking a folder in either repository. You see the folders within the global repository as well as those in the local repository. A dialog box appears. 32 Chapter 2: Using the Repository Manager . such as MySources. choose Tools-Export Registry. The section of the registry you can import and export contains the following repository connection information: ♦ ♦ ♦ Repository name Repository user name and 7-bit ASCII password Repository Server host name and port number The Repository Server uses repository configuration information separate from the connection information stored in the registry to manage repositories. you can export that information. Double-click the icon for the global repository. Click OK. and then import it to a different client machine. Connect to the global repository. Icons for all the local repositories in the domain appear beneath the global repository. Enter the name of the export file. If you want to export or import repository configuration information for the Repository Server. To simplify the process of setting up client machines. 3. choose Repository-Connect. 2.reg. To export the registry: 1. To identify the file. informing you that the Repository Manager successfully exported the repository registry file. Select another repository. Both machines must use the same operating systems. The contents of the local repository appear.2. see “Exporting and Importing Repository Configurations” on page 115.

informing you that the Repository Manager successfully merged the repository connection information into your registry. Navigate to the directory containing the import file and select it. In the Repository Manager. To import the registry: 1. A dialog box appears. 3. Click Open. Working with Repository Connections 33 .You can now distribute this file for import on other client machines with the same operating systems. 2. choose Tools-Import Registry.

connect to a repository. comments. or Enter a keyword in the Keyword window. 34 Chapter 2: Using the Repository Manager . Performing Keyword Searches Once you add keywords to target definitions. To search for targets containing a keyword: 1. The Search Target Tables For Keyword dialog box appears. you can use them to perform searches in the Repository Manager. or you can select one from the list of all keywords applied to target definitions in the repository. 2. Choose Analyze-Search by Target Keyword. 3. If you want to select a keyword. click List Keywords. group names or owner names associated with the repository object. then click OK. Use Search All when you want to search through text in object names.Searching for Repository Objects In the Repository Manager. you can search for repository objects using the following methods: ♦ ♦ Keyword search Search text Perform a keyword search when you have associated a keyword with a target definition. select a keyword. In the Repository Manager. You can enter a keyword.

If not selected. Click OK. the Repository Manager looks for keywords that contain the keyword entered. Searching for Repository Objects 35 . For example. source and target fields. You can search for text in the repository objects such as transformations. or owner name associated with repository objects. group name. Searching All Repository Objects Use Search All to search for text in the object name. the search would return a keyword match for REPOSITORY. the Repository Manager does not try to match the case of the keyword entered.4. To search for text in all repositor y objects: 1. Select the options you want to use in the search: Option Exact Match Description If selected. The screen splits. the keyword search is case-sensitive. the Repository Manager only looks for the entire keyword entered. Otherwise. and tasks. Ignore Case 5. displaying the list of matching keywords in the bottom window. In the Repository Manager. If selected. comments. The Repository Manager now searches for matching keywords in all target definitions in the repository. if you enter REPOS without selecting the Exact Match option. connect to the repository.

The Repository Manager selects all objects by default. The Search All dialog box appears. 8. In the item list. Select Match Case if you want to perform a case-sensitive search. 4. select the repository objects in which you want to search for the text. 3. Click Find Next to find the next repository object matching the search text. Click Close to close the Search All dialog box. 6. The Repository Manager selects all attributes by default. Click Find Next. 36 Chapter 2: Using the Repository Manager . Select the repository object attributes in which you want to search for the text. Choose Analyze-Search All. 5. The Repository Manager displays the first repository object matching the search text in the Main window. 7.2.

Sources within the same folder that reference the source through a foreign key relationship. and Designer. . . In addition. You can view dependencies from the View History window when you view the history of an object. .Global and local shortcuts to the transformation. You can view dependencies from the Query Results window when you search for object dependencies or run an object query.Transformations the mapplet uses. . .Global and local shortcuts to the target. . Workflow Manager. Workflow Manager. . you can view dependencies when you review the results of the following tasks: ♦ ♦ ♦ View object history.Targets the mapplet uses. .Transformations the mapping uses.Sources the mapplet uses.Global and local shortcuts to the source. . For example.Viewing Object Dependencies Before you change or delete repository objects. Mapplets Mapping Designer Mapplet Designer Sources Mapplet Designer Mapping Designer Source Analyzer Mapping Designer Warehouse Designer Mapplet Designer Mapping Designer Transformation Developer Targets Transformations Viewing Object Dependencies 37 . You can view dependencies from the View Checkouts window when you search for persistent checkouts. View checkouts. . before you remove a session. In the Repository Manager. and Designer tools.Targets the mapping uses.Global and local shortcuts to the mapping.Global and local shortcuts to the mapplet. you can view dependencies to see the impact on other objects. . Viewing Object Dependencies Parent Object Mappings Tool Mapping Designer Types of Child Objects Displayed . you can find out which workflows use the session. but you cannot check in original objects for global shortcuts. View query results. You can view dependencies for repository objects in the Repository Manager. Note: You can check in objects from the View Dependencies dialog box. Table 2-2 lists the Workflow Manager and Designer tools you can use to display dependencies.Targets within the same folder that reference the target through a foreign key relationship. and the objects that View Dependencies displays when you view dependencies: Table 2-2.Sources the mapping uses. . you can view dependencies from the tools in the Workflow Manager and Designer.

Sessions the workflow uses. . . . You can view object dependencies when you open objects in the following tools: ♦ ♦ ♦ ♦ Mapping Designer Mapplet Designer Workflow Designer Worklet Designer The Dependencies dialog box displays the object name. . . .Session configuration the session uses.Tasks the session uses. and a list of dependent objects and their properties.Transformations the session uses. .Targets the worklet uses. .Mapping the session uses. .Sources the session uses. .Mapplets the session uses.Mapplets the worklet uses. 38 Chapter 2: Using the Repository Manager .Mapplets the workflow uses. .Table 2-2.Targets the session uses.Schedulers the worklet uses.Tasks the workflow uses.Transformations the worklet uses. Viewing Object Dependencies Parent Object Sessions Tool Task Developer Worklet Designer Workflow Designer Types of Child Objects Displayed . . . .Session configuration the worklet uses.Targets the workflow uses. . .Session configuration the workflow uses. .Schedulers the workflow uses.Tasks the worklet uses.Mappings the session uses. . Workflows Workflow Designer Worklets Worklet Designer Workflow Designer Note: You can perform all searches in this table from the Repository Manager. .Mappings the worklet uses. . . . You can view object dependencies in the Workflow Manager and Designer when you work with objects in the workspace. . . .Mappings the workflow uses.Worklet the workflow uses.Sessions the worklet uses.Transformations the workflow uses. object type.Sources the worklet uses.Sources the workflow uses. .

View primary and source object dependencies where there is a primary key-foreign key relationship. Viewing Object Dependencies 39 . the results might include a workflow or worklet. if you search for the parent objects for a session. View global shortcuts across repositories. For example. Dependencies Dialog Box Select options. or primary key-foreign key dependencies. the results might include sessions and worklets. View the objects that the selected object uses. For example. All Children PK/FK Dependencies Go Across Repositories When you search for dependencies. Dependencies Options Option All Parents Description View the objects that use the selected object. Filter by object type when you search for parent or child dependencies. When you search for dependencies. Table 2-3 shows the options you can select when you search for dependencies: Table 2-3. the results window displays the properties for each dependent object.Figure 2-6 shows the Dependencies dialog box: Figure 2-6. You can select this option when you search for parents. children. Search for dependencies. you can filter the results by selecting options and object types. if you search for the child objects for a workflow.

Figure 2-7 shows the View Dependencies window: Figure 2-7. the group type can be Oracle. The type of dependent object. or XML.Foreign key dependency . Time the object was created or saved.Shortcuts .Source definition The version number of the dependent object. For example. View Dependencies Window Object Properties Output Window Comments Window Labels Window Table 2-4 describes the object properties that display in the View Dependencies window: Table 2-4. Object Properties for View Dependencies Window Properties Object Name Group Name Object Type Description The name of the dependent object. Status of the object. DBD associated with the source of the object.Mapplets .Workflows . DB2.Sessions . Active or Deleted. Version Time Stamp Status Version Comments 40 Chapter 2: Using the Repository Manager .Worklets .Target definition . Comments associated with the dependent object.Mappings . Dependent objects can be any of the following types: .

The View Dependencies window also displays output. Figure 2-8 shows an example of the HTML file saved from a View Dependencies window: Figure 2-8. Object Dependencies Saved as HTML Viewing Object Dependencies 41 . and label information associated with the object. Object Properties for View Dependencies Window Properties Folder Name User Name Host Name Checkout Type Purged by User Is Reusable Is Deleted Repository Description The folder name where the dependent object resides. To save the list of dependent objects as an HTML file. Name of the user who purged the object. and the Comments window displays text entered during object check in or check out. Repository hosting the object. Yes or No. User who created the object. Persistent or Non-Persistent. Status of object as reusable. The Output window displays validation information. The Labels window displays labels associated with the object and information associated with the label object. Status of object deletion. Yes or No.Table 2-4. choose File-Save to File. comments. Type of checkout for object. Host name for the machine hosting the object.

If you select objects from query results or an object dependencies list. mapplets. If you do not choose to save the objects in the repository. workflows. see the Workflow Administration Guide. Select the objects you want to validate. and you can select them from within the Repository Manager. and worklets. Designer. The Validate Objects dialog box displays. For information about mapping validation. you can choose different types of objects to validate. You can validate sessions. you must right-click one of the selected objects and choose Validate. Choose whether to check in validated objects. You can select objects to validate from the Repository Manager navigator. For information on validating sessions and workflows. If you are checking in validated objects you must enter check in comments. Otherwise this option is disabled. you can also choose Tools-Validate to initiate a validation. If you select objects from the Repository Manager navigator. You can only select this option if you have selected the Save Objects option and versioning is enabled in the repository.Validating Multiple Objects PowerCenter allows you to validate multiple objects in the repository without fetching them into the workspace. If you select objects from query results or a list view. see the Designer Guide. 2. To validate multiple objects: 1. mappings. the validation just provides a report. Select validation options from the Validate Objects dialog box: ♦ ♦ Save validated objects. you can only select objects of the same type. or Workflow Manager. ♦ 42 Chapter 2: Using the Repository Manager . If you are selecting objects from the Navigator. 3. in the same folder. Initiate the validation. Check in comments. You can also select objects from query results or an object dependencies list. You can save and optionally check in objects that change from invalid to valid status as a result of the validation. You can automatically check in valid objects.

The output window of your current screen shows the status of each object being validated. The number of validated objects you cannot save because someone has them locked.Objects that do not require validation. such as sources. The number of invalid objects provided for validation.4. You can cancel the validation from the progress dialog box. Figure 2-9 shows the Validate Objects results box. The validation displays status in a progress dialog box. The results box displays when validation completes. The total number of objects saved. Click Validate. If you do not choose the Save Objects or Check In Objects options. Table 2-5. The total includes skipped objects. The number of the following types of objects: . click the hyperlink. transformations. Validate Objects Properties Properties Objects provided for validation Skipped objects Description The total number of objects that you selected to validate. Objects that were invalid before the validation Objects successfully validated Objects still invalid Saved/checked in objects Cannot save objects due to lock conflict Validating Multiple Objects 43 .Objects that cannot be fetched. . The number of selected objects that are valid. you cancel the remaining operations in the validation. you do not cancel the current operation. Validate Objects Results Hyperlinks to view the objects in the group. such as a deleted mapping associated with a session being validated. Figure 2-9. Table 2-5 describes the information that displays in the Validate Objects window. and shortcuts. If you cancel. targets. this number is zero. To view the objects in each total. The number of objects that require fixing or editing. Use the results box to determine how many objects were validated and saved.

5. Validation results that have more than zero objects in them have hyperlinks to the object details. a dialog box displays each object in the results group you select. 44 Chapter 2: Using the Repository Manager . Click a hyperlink to view the objects in the results group. When you click the hyperlink.

You cannot compare objects of different types. see “Comparing Versions” on page 210. you must have both the folders open. connect to the repository. such as tasks. To do this. Workflow Manager objects. ♦ You can compare instances of the same type in detail. Comparing Repository Objects 45 . select the object you want to compare. see the Workflow Administration Guide. worklets. For example. Further. You can compare Workflow Manager objects. You can compare schedulers and session configuration objects in the Repository Manager. In the Navigator. 2. You can also compare different versions of the same object. You can compare a reusable object with a non-reusable object. You can compare instances of mappings and transformations in a session comparison. For more information about comparing objects in the Workflow Manager. In the Repository Manager. you can compare instances of the same type within a mapping or mapplet comparison. mapplets and mappings. sessions. You can compare objects across folders and repositories. but not in the Workflow Manager. and workflows. When you compare two objects. you can compare the instances to see if they differ. you cannot compare a source definition with a target definition. Tip: To compare the first two objects in a node. you can compare two sessions to check for differences. see the Designer Guide. To compare objects. you must have read permission on each folder that contains the objects you want to compare. For example. To compare repository objects: 1. the Repository Manager displays their attributes. if the workflows you compare contain worklet instances with the same name. For example. select the node. transformations. Use the following procedure to compare objects. For more information about comparing objects in the Designer. targets. such as sources. You can compare instances of sessions and tasks in a workflow or worklet comparison. You can compare the following types of objects: ♦ Designer objects. For more information about versioned objects.Comparing Repository Objects The Repository Manager allows you to compare two repository objects of the same type to identify differences between the objects. You can compare Designer objects.

Choose Edit-Compare Objects. 46 Chapter 2: Using the Repository Manager . A dialog box similar to the following one appears: 4. the Sources window shows the result of comparing two sources: View object differences. such as a source. Click Compare. If you choose a Designer object.3.

Differences between objects are highlighted and the nodes are flagged. Compare object instances. Displays the properties of the node you select. Comparing Repository Objects 47 . the Diff Tool window shows the result of comparing two sessions: Filter nodes that have same attribute values.If you choose a Workflow Manager object. such as a session. Differences between object properties are marked.

Use the Repository Manager to truncate the list of workflow logs. To truncate workflow and session log entries: 1. and it always retains the most recent session log entry for each session. In the Repository Manager. The repository always retains the most recent workflow log entry for each workflow. Choose whether you want to delete all workflow and session log entries. The Repository Server deletes the workflow and session log entries from the repository. 3. enter the date and time. you can remove the entries from the repository. The repository also creates an entry for each saved workflow log and session log. If you move or delete a session log or workflow log from the workflow log directory or session log directory. select the workflow in the Navigator window or in the Main window. If you want to delete all entries older than a certain date. 5. or all workflow and session log entries with an end time older than a certain date. or you can truncate all workflow logs before a specified date.Truncating Workflow and Session Log Entries When you configure a session or workflow to archive session logs or workflow logs. The Repository Server truncates the workflow log list and the session log list at the same time. You can truncate all of the workflow logs entries in the list. The Truncate Workflow Log dialog box appears. Click OK. 4. the PowerCenter Server saves those logs in local directories. 48 Chapter 2: Using the Repository Manager . Choose Edit-Truncate Log. 2.

77 Propagating Repository Domain Connection Information. 66 Starting and Stopping the Repository. 74 Registering a PowerCenter Repository. 85 Registering and Unregistering LDAP Security Modules.Chapter 3 Managing the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 52 Registering and Connecting to the Repository Server. 97 49 . 88 Reading the Repository Log Files. 64 Backing Up and Restoring a Repository. 83 Registering and Unregistering Repository Plug-ins. 50 Navigating the Administration Console. 58 Tuning Repository Performance. 78 Viewing User Connections and Locks. 75 Migrating the Repository to a Different Repository Server. 62 Deleting a Repository. 79 Closing User Connections and Locks. 71 Sending Repository Notifications. 60 Copying a Repository.

For details on repository architecture and connectivity. see “Upgrading a Repository” in the Installation and Configuration Guide. Edit repository license files. enable. You use the Repository Server Administration Console to create and administer the repository through the Repository Server. creating repositories. Send repository notification messages. Back up and restore a repository. and remove repository configurations. The Repository Server performs all metadata transactions between the repository database and repository client applications. A Repository Server can manage multiple repositories. Close repository connections. Permissions and Privileges When you connect to a Repository Server in the Administration Console. 50 Chapter 3: Managing the Repository . Create a repository. View repository connections and locks. Propagate domain connection information for a repository.Overview The PowerCenter repository is a collection of database tables containing metadata. see “Configuring the Repository” on page 103. Register and remove repository plug-ins. Register and unregister a repository. you use the administrator password specified in the Repository Server setup. see “Repository Architecture” on page 3 and “Repository Connectivity” on page 4. stop. When you connect to a Repository Server. promoting repositories. and licenses. The Repository Server manages repositories. For details on working with repository configurations. Promote a local repository to a global repository. Upgrade a repository. Copy a repository. For details on upgrading a repository. Export and import repository configurations. Delete a repository from the database. You can use the Administration Console to perform the following tasks: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Add. Start. you can perform all tasks in the Administration Console for repositories the Repository Server manages. edit. and disable repositories.

Overview 51 . or restore a repository. For more information on code pages. copy. do not select an EBCDIC code page for the repository code page. The PowerCenter Client and Server code pages must be compatible with the repository code page. Note: EBCDIC code pages appear in the list of possible repository code pages when they are compatible with the PowerCenter Client code page. since you cannot create a repository on mainframes. see “Globalization Overview” in the Installation and Configuration Guide.Repository Code Pages Every repository has an associated code page. When you create. you must choose a repository code page from a list of code pages that are compatible with the PowerCenter Client. However.

Administration Console Main Window Console Tree Nodes Console Tree The Console Tree allows you to browse Repository Servers and managed repositories. The Administration Console uses Microsoft Management Console (MMC) technology. such as creating. For details on starting and stopping the Repository Server. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. starting. You can also launch the Administration Console from the Windows Start menu. On Windows. see the online help for MMC. and backing up repositories. start the Repository Server service from the Services control panel. The Administration Console is a snap-in for MMC. start the Repository Server from the command line. For more information on using MMC. MMC is a console framework for server and network management applications called snapins. The Administration Console allows you to navigate multiple Repository Servers and repositories and perform repository management tasks. To launch the Administration Console from the Repository Manager. choose RepositoryManage Repository Server.Navigating the Administration Console Use the Administration Console to connect to the Repository Server and perform repository administration tasks. You must start the Repository Server before you can perform repository administration tasks. The Administration Console displays a different set of Action menu items depending on which 52 Chapter 3: Managing the Repository . On UNIX. Figure 3-1 shows the Administration Console: Figure 3-1.

Lists repository information. In List view. Expand this node to perform repository functions. HTML view includes hypertext links that allow you to perform actions on the selected node. such as backing up. The Console Tree contains the following nodes: ♦ ♦ ♦ Repository Servers. Select this node to view user connection information and to manually close connections. and user connections. Select this node to view existing object locks in the repository. ♦ Navigating the Administration Console 53 . The Main window displays results in the following views: ♦ List view. locks. and registering with a global repository. Figure 3-2 on page 55 shows the Administration Console in HTML view. Select this node to view the latest activity performed on all repositories managed by the Repository Server. and to start or stop all repositories managed by the Repository Server. Locks. Repository name. Lists repository locks. or you can list them with or without item details. Lists the registered Repository Servers. Backups. You can view items as large or small icons. such as copying or backing up a repository. Lists the repository backup files available in the Repository Server backup directory. you can arrange the items in different ways by choosing the View menu. such as the status and start time. Lists recent Repository Server activity. upgrading. the Main window displays the properties of the repository. Activity Log. The Administration Console only displays repositories in HTML view. Available Packages. Lists the plug-ins available to the Repository Server. The hypertext links are shortcuts to some Action menu items. Repository Server name. Choose ViewDetails to view detailed information for a node in List view. Activity Log. Lists the nodes under it: Repositories. Expand this node to connect to a Repository Server or to register a Repository Server.node you select in the Console Tree. Backups. Displays repository information as a dynamic HTML page. You can also right-click a node to access the Action menu items. For example. Expand this node to add or import a repository configuration. Displays a collection of items that includes an icon and a label. Lists the managed repositories. HTML view. Repositories. ♦ ♦ ♦ ♦ ♦ ♦ Main Window The Main window displays details of the node you select in the Console Tree. Figure 3-1 on page 52 shows the Administration Console in List view. and Available Packages. if you select a repository in the Console Tree. Select this node to restore a repository from a backup file. Lists user connection details. Select this node to register and remove plug-ins. Connections.

54 Chapter 3: Managing the Repository . Table 3-2 list Repositories node details that display in the Administration Console: Table 3-2. The start time of the repository. either running. the Main window displays details about each repository managed by the Repository Server. the Main window displays details about each registered Repository Server. The Main window also displays HTML links that allow you perform some repository tasks. Activity Log. either connected or not connected. The status of the repository. stopped. The connection status of the repository. or disabled. the Main window displays details about the repository in HTML view. Repositories Node Details Column Name Name Status Start Time Description The name of the repository. Repository Name Node Details When you select a repository in the Console Tree. Repository Server Name Node Details When you select a Repository Server in the Console Tree. Backups. the Main window displays each node under the Repository Server node: Repositories. Table 3-1 lists Repository Servers node details that display in the Administration Console: Table 3-1. Repositories Node Details When you select the Repositories node. and Available Packages. The port number used to access the Repository Server.Repository Servers Node Details When you select the Repository Servers node in the Console Tree. Repository Servers Node Details Column Name Host Name Port Number Status Description The name of the computer hosting the Repository Server.

The type of database where the repository resides. use this number to identify which error messages apply to the Repository Agent. Database Type Table 3-4 lists the HTML links for performing some repository tasks: Table 3-4. this property resets to 0. see “Stopping the Repository” on page 72. Repository Details Attribute Status Start Time Number of Restarts Process ID Description The status of the repository. The Repository Server and Repository Agent append this number to entries in the Repository Server and Repository Agent log files. For more information. For more information on the repository log file. If you shut down the Repository Server.Figure 3-2 shows repository details: Figure 3-2. HTML Links for Performing Repository Tasks HTML Link Stop Backup Description Stop the repository. Repository Details HTML View Hypertext Link Table 3-3 lists repository details displayed in the Administration Console: Table 3-3. When you troubleshoot the repository. The date and time the repository last started. The Windows or UNIX process identification number assigned to the Repository Agent. Back up the repository to a binary file. The date display format is MM/DD/YYYY 24 HH:MI:SS. either running. stopped. stopping. The total number of times the repository started since the Repository Server started. or disabled. see “Reading the Repository Log Files” on page 97. Navigating the Administration Console 55 . see “Backing Up a Repository” on page 66. For more information. starting.

Figure 3-3 shows the Activity Log window: Figure 3-3. the Administration Console shows the Activity Log in a popup window. When you perform some repository management tasks. see “Viewing Locks” on page 80.Table 3-4. This includes activities such as upgrading or starting a repository. the Main window displays details about the locks associated with the selected repository. the Main window displays user connections to the repository. such as starting a repository. View general. Upgrade the repository to the latest version. see “Viewing User Connections” on page 79. Activity Log Node Details When you select the Activity Log node. you can save the activity information to a text file by choosing Action-Save As. Activity Log Window 56 Chapter 3: Managing the Repository . This information also displays in the Main window when you select the Activity Log node. database. When you select the Activity Log node. For more information. see “Upgrading a Repository” in the Installation and Configuration Guide. For details. the Main window displays all activity the Repository Server performed on all managed repositories since you launched the Administration Console and connected to the Repository Server. network. Locks Node Details When you select the Locks node. and server configuration parameters for the repository. For details. HTML Links for Performing Repository Tasks HTML Link Restore Upgrade Properties Description Recover metadata from a repository binary backup file. For more information see “Restoring a Repository” on page 67. see “Adding a Repository Configuration” on page 105. Connections Node Details When you select the Connections node. For more information.

Available Packages Node Details When you select the Available Packages node. see “Reading the Repository Log Files” on page 97.When you right-click the Activity Log window. For more information about Repository Server log files. Clear all text. Backups Node Details When you select the Backups node. The Administration Console does not display Repository Server log file messages. Navigating the Administration Console 57 . the Main window displays the plug-in files available to register in the Repository Server plug-in directory. Change the font of all text. you can perform the following tasks: ♦ ♦ ♦ ♦ ♦ Select all text. the Main window displays the repository backup files available in the backup directory specified in the Repository Server setup. Save the information to a text file. Copy selected text.

and click OK. You can connect concurrently to multiple Repository Servers.Registering and Connecting to the Repository Server To perform repository administration tasks. 2. Right-click the Repository Server and choose Connect. 3. 2. When you connect to a Repository Server. Launch the Administration Console and expand the Repository Servers node in the Console Tree. Choose Action-New Server Registration. The Administration Console connects to the Repository Server and displays the managed repositories. 58 Chapter 3: Managing the Repository . the Administration Console maintains the connection until you disconnect from the Repository Server or close the Administration Console. 3. To connect to the Repository Server: 1. The Repository Server icon in the Console Tree changes depending on the connection state. To register a Repository Server: 1. Connecting to the Repository Server Use the following procedure to connect to the Repository Server. see “Installing and Configuring the Repository Server on Windows” or “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. Click OK. You must register a Repository Server to connect to it. The Administration Console adds the Repository Server to the Console Tree. For details on configuring the Repository Server. you must connect to the Repository Server. Registering a Repository Server Use the following procedure to register a Repository Server. Launch the Administration Console and select the Repository Servers node. Enter the Repository Server host name and port number. In the Connecting to Repository Server dialog box. enter the password you use to administer the Repository Server and the port number used to access the Repository Server.

To disconnect from the Repository Server: 1. Registering and Connecting to the Repository Server 59 .Disconnecting from the Repository Server Use the following procedure to disconnect from the Repository Server. expand the Repository Servers node. Right-click the Repository Server and choose Disconnect. In the Console Tree. 2.

For more details. see “pmrepagent Commands” on page 477. or copy a repository. backup. You have the option of skipping the information that is not essential to the function of the repository. Most databases keep and use column distribution statistics to determine which index to use to execute SQL queries optimally. and restore repositories. the impact of choosing a sub-optimal query plan can affect performance drastically. Increasing Repository Copy. PowerCenter identifies and updates the statistics of all repository tables and indexes when you copy. you reduce the time it takes to copy. In large repositories. Updating Repository Statistics The PowerCenter repository has more than 170 tables. When you back up. In frequently-used repositories. and restore dialog box contains an Advanced button that allows you to choose the information you want to skip. and almost all tables use at least one index to speed up queries. back up. 60 Chapter 3: Managing the Repository . You can update statistics and skip information when you copy. Backup. see “Updating Repository Statistics (UpdateStatistics)” on page 447. Each copy. Over time. For details. You can also update statistics using the pmrep command Updatestatistics. Database servers do not update these statistics continuously. You can also skip this information when you use the pmrepagent commands. upgrade. restore. backup.Tuning Repository Performance PowerCenter includes features that allow you improve the performance of the repository. the repository becomes slower and slower. or restore a repository. or restore the repository. these statistics can become outdated very quickly and SQL query optimizers may not choose the best query plan. you can choose to skip the following types of information: ♦ ♦ ♦ Workflow and session logs Deploy group history MX data By skipping this information. and Restore Performance Large repositories may contain a lot of log and history information that slows down repository performance.

see “Creating a Repository” in the Installation and Configuration Guide. If you are restoring a repository. Select the data you want to skip. Backup Repository dialog box. or Restore Repository dialog box. Tuning Repository Performance 61 . 4. follow the steps to restore a repository in “Restoring a Repository” on page 67. Note: You can optimize repository performance for repositories on IBM DB2 EEE. backing up. and continue copying. follow the steps to copy a repository in “Copying a Repository” on page 62. 2. or restoring the repository. Click the Advanced button on the Copy From Another Repository dialog box. 3. For more information. or restoring a repository: 1. follow the steps to back up a repository in “Backing Up a Repository” on page 66. Click OK. If you are copying a repository.To skip information when copying. If you are backing up repository. backing up.

set allow nulls by default to TRUE at the database level. If a repository exists in the target database. the copy operation fails. Choose Action-All Tasks-Copy From. The Copy From Another Repository dialog box appears. 3. Setting this option changes the default null type of the column to null in compliance with the SQL standard.Copying a Repository You can copy a repository from one database to another. Copying repositories provides a quick way to copy all metadata you want to use as a basis for a new repository. and select a repository from the repository list. select the target repository configuration. 2. you must select a code page for the target repository that is compatible with the original repository. you must add or import a repository configuration for the target repository. If you want to copy a repository managed by the same Repository Server. To copy a repository. 62 Chapter 3: Managing the Repository . The Repository Server uses the connection information in this repository configuration to connect to the target database when it copies the source repository. To copy a repository: 1. Copy a repository to preserve the original repository before upgrading. When you copy a repository. choose Managed By the Same Repository Server. Note: If you want to copy a Sybase repository. In the Console Tree. For details. You can also copy a repository when you want to move a repository from development into a production environment. see “Adding a Repository Configuration” on page 105 and “Importing a Repository Configuration” on page 115. You must back up and delete the existing repository from the target database before copying the repository.

Copying a Repository 63 . The Repository Server starts the repository when it finishes copying it. deploy history. Click OK. To skip workflow and session logs. 6. Repository Server host name. and Restore Performance” on page 60. If you want to copy a repository managed by a different Repository Server. Enter the repository user name and password for the source repository. 5. Backup. and MX data.4. 7. You can view the progress of the copy in the Activity Log. The Repository Server copies the repository from the source repository to the database specified in the destination repository configuration. and enter the repository name. and Repository Server port number. select Managed By a Different Repository Server. For more details. click the Advanced button. see “Increasing Repository Copy.

and click OK. you must choose to unregister all local repositories. There was an error deleting the repository. contains registered repositories (<local repository names>). The Repository Server stops the repository. The Administration Console displays the following message: This repository. select the repository you want to delete. Deleting a repository is an irreversible action. Note: You can also use the pmrepagent Delete command to delete repositories. 2. 64 Chapter 3: Managing the Repository . If the repository you want to delete is a global repository. This option instructs the Repository Server to delete the repository metadata and tables from the database. The Repository Server disables the repository so that other users cannot start it. If the repository contains information that you might need. choose Action-Stop. 3. Delete the repository in the database. 4. <global repository name>. To delete a repository: 1. Choose Action-Delete. Select Delete the Repository.Deleting a Repository Delete a repository when you want to delete all metadata and repository database tables in the repository. If the repository is running. see “Deleting a Repository (Delete)” on page 481. Choose Action-Disable. In the Console Tree. For more information on stopping and disabling the repository. You must stop and disable the repository before you delete it. For more information. The Deleting a Repository dialog box appears. 5. Unless you unregister all local repositories. You might delete a repository if metadata is obsolete. back up the repository before you delete it. see “Stopping the Repository” on page 72 and “Disabling the Repository” on page 73. the Repository Server does not delete the global repository.

You can monitor the progress of the delete operation in the Activity Log. 8. When you click Yes. When you click No. and it keeps a backup of the repository configuration file in the Repository Server configuration directory. you can choose to keep or remove the repository configuration. 7. 9. When prompted to delete the repository. the Administration Console removes the repository from the Console Tree. 10. Deleting a Repository 65 . If the repository is a global repository. Click OK. The Delete Repository Content dialog box appears. The Repository Server deletes the repository. Enter your repository user name and password. After the Repository Server deletes the repository. you can choose to unregister all local repositories. Click No to keep the repository configuration.6. the Administration Console keeps the repository in the Console Tree. or click Yes to remove it. click OK.

Backing Up a Repository When you back up a repository. Specify the backup directory in the Repository Server setup. connection information. you can restore the contents of the repository from this binary file. and the backup occurs the first week of May. 66 Chapter 3: Managing the Repository . the Repository Server stores the file in the Repository Server backup directory. Tip: You can also click Backup in the Main window.rep. The Repository Server saves the backup file in the Repository Server backup directory. select the repository you want to back up.Backing Up and Restoring a Repository Regularly back up your repositories to prevent data loss due to hardware or software problems. Choose Action-All Tasks-Backup. and code page information. For example. The Backup Repository dialog box appears. the Repository Server saves the repository in a binary file. you might name the file DEVELOPMENTMay7. password. The Repository Server uses the extension . Enter your repository user name.rep for all repository backups. if the name of the repository is DEVELOPMENT. You can also enter a description for the backup file. Use an easily distinguishable name for the file. If you need to recover the repository. and file name for the repository backup file. 3. 2. To back up a repository: 1. Specify a name for the backup file. In the Console Tree. When you back up a repository. including the repository objects.

and you do not choose to replace the existing file. and connectivity license keys to the repository license file when you edit the repository configuration you use to restore the repository backup file. 5. PowerCenter can restore repositories from the current version only. If a repository already exists at the target database location. The actual amount of disk space required to restore the repository depends on the size of the repository backup file. Verify you add the product. You must delete the repository database before restoring a backup repository. Note: If you want to create. For example. You can view the backup operation in the Activity Log. If you have a backup file from an earlier version of PowerCenter or PowerMart. Restoring a Repository You can recover metadata from a repository binary backup file. If you want to overwrite an existing repository backup file. and MX data. restore. When restoring a repository. you must have a Team-Based Development option license key to restore a versioned repository. or upgrade a Sybase repository. For details on the minimum system resources required to create a repository. 6. the Repository Server does not back up the repository. For more details. To skip workflow and session logs. see “Increasing Repository Copy. Setting this option changes the default null type of the column to null in compliance with the SQL standard. you must have at least the minimum system resources required to create a repository. see “Creating a Repository” on page 116. replace the existing file. You can restore the repository in a database that has a compatible code page with the original database. you must use the earlier version to restore the repository. set allow nulls by default to TRUE at the database level. see “Restoring a Repository (Restore)” on page 485 and “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Backing Up and Restoring a Repository 67 . In the Administration Console. and Restore Performance” on page 60. You can also use the pmrepagent Restore command to restore repositories. For more information. deploy history. you must have a database available for the repository. you can restore a repository from either the Backups node or a repository name node. If you specify a file name that already exists in the Repository Server backup directory. or the Bulkrestore command to restore Teradata repositories. The Repository Server does not restore a repository if one already exists in the target database location. option. Backup. see “Working with PowerCenter Licenses” on page 119. you must delete it before restoring a repository backup file. click Advanced. For more information on licenses.4. Click OK. If you want to restore a repository.

click Advanced. 4. and MX data. The Administration Console allows you to create a repository configuration or use an existing repository configuration for the restored repository. deploy history. Backup. For details on creating a repository configuration. Use an existing repository configuration. and choose ActionRestore. select the Backups node. The Main window lists the available backup files in the Repository Server backup directory. 3. select the repository backup file to restore. In the Console Tree. Create a repository configuration. To skip workflow and session logs.To restore a repository from the Backups node: 1. 5. see “Increasing Repository Copy. Click OK. 2. The Restore Repository dialog box appears. For details. Choose to create a repository configuration or to use an existing repository configuration. 68 Chapter 3: Managing the Repository . see “Adding a Repository Configuration” on page 105. and Restore Performance” on page 60. In the Main window.

the Administrator account password becomes “Administrator. If you choose to keep the external module. 2. The Repository Agent verifies that the password is valid for the user name on the target server.” The other user names become disabled. The Repository Agent does not assume that the same user authentication module is on the new system. 6. In the Console Tree. To restore a repository from a repository name node: 1. Click OK. The Repository Server restores the repository. 7. you must choose whether to restore the repository with the external module or to unregister the security module when you restore. so it verifies that the administrative user can connect to the repository if the restore completes. If you choose to unregister the security module.If the repository uses a security module. You can view the restore process in the Activity Log. Backing Up and Restoring a Repository 69 . If the Restore Repository-Security Module dialog box displays. you must specify the repository administrator user name and password. Choose Action-All Tasks-Restore. select a repository configuration under the Repositories node to use for the restored repository. the Restore Repository-Security Module dialog box displays.

the Restore Repository-Security Module dialog box displays. you must specify the repository administrator user name and password. The Repository Agent verifies that the password is valid for the user name on the target server. and MX data. You can view the restore process in the Activity Log. click Advanced. select the backup file to restore. 6. For details. 4. deploy history. To skip workflow and session logs. 5. If the repository uses an authentication module. If the Restore Repository-Security Module dialog box displays. The Administration Console lists backup files in the Repository Server backup directory. see “Increasing Repository Copy. Backup. 7. Click OK. 70 Chapter 3: Managing the Repository . you must choose whether to restore the repository with the external module or to unregister the security module when you restore. The Repository Server restores the repository. If you choose to unregister the security module. Click OK. In the Restore Repository dialog box. If you choose to keep the external module.” The other user names become disabled.3. The Repository Agent does not assume that the same user authentication module is on the new system. so it verifies that the administrative user can connect to the repository if the restore completes. the Administrator account password becomes “Administrator. and Restore Performance” on page 60.

The Repository Server starts the repository. You can use the Start command to ensure a repository with a new or edited configuration initializes properly. 5. The Enable option is available when the repository is disabled. In the Console Tree. The Starting and Stopping the Repository 71 . The Repository Server enables the repository. Perform the repository administration task or edit the repository configuration. see “Editing a Repository Configuration” on page 113. choose Action-Start. 3. For more information on dynamic updating. You should also stop the repository when you edit repository configuration parameters that are not dynamically updated. You can also use the Start command to restart the repository if it stops unexpectedly. or enable the repository. You must stop the repository to perform the following repository administration tasks: ♦ ♦ ♦ Upgrade the repository. Remove the repository configuration. Delete the repository.Starting and Stopping the Repository The Administration Console allows you to manually start. If you want to start the repository. Starting the Repository The Start command allows you to manually start the repository. select the repository you want to enable. Start the repository. Use these commands when you perform repository administration tasks that require you to stop the repository. 2. Use the following steps as a guideline when you perform these tasks: 1. disable. To enable the repository: 1. Stop the repository. stop. Disable the repository to prevent other users or applications from starting it. 2. 4. enable the repository to allow other users or applications to start it. Choose Action-Enable. After restoring or upgrading the repository. 3. Enabling the Repository Enable the repository to allow you or other users full access to start a disabled repository.

Note: Before you start the repository. To start a single repository: 1. 72 Chapter 3: Managing the Repository . Check for active user connections before you stop the repository. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. 3. For more information on licenses. see “Disabling the Repository” on page 73. send a notification telling repository users to save work in progress and disconnect from the repository.Repository Server starts an enabled repository for client applications requesting a connection to the repository. For details on viewing user connections. Choose Action-Disable if you want to prevent other users or applications from restarting the repository. You can view the progress of the stop operation in the Activity Log. To stop a single repository: 1. 2. Choose Action-Start. see “Viewing User Connections” on page 79. In the Console Tree. choose Action-Enable. In the Console Tree. The Repository Server starts the repository. select the repository you want to stop. You can also use the Stop All command to stop all repositories managed by the Repository Server. The repository closes all connections to repository client applications before stopping. Stop all repositories if you need to shut down the Repository Server. Stopping the Repository The Stop command allows you to manually stop the repository to perform administration tasks. Note: To avoid loss of data. Choose Action-Stop. You must stop the repository before upgrading or deleting it. For details on starting the Repository Server. disable the repository. You can also disable the repository while it is running. you must start the Repository Server. The Repository Server only starts a repository if the repository license file exists in the Repository Server installation directory and it contains a valid product license key. see “Working with PowerCenter Licenses” on page 119. For details on disabling the repository. 3. To prevent other repository client applications from starting the repository after you stop it. If the repository is disabled. The Repository Server stops the repository. You can view the startup progress in the Activity Log. select the repository you want to start. 2.

Disabling the Repository When you disable the repository. the repository continues to run and the repository status indicates it is running. Choose Action-Disable. you prevent other users or repository client applications from starting it. 2. If the repository is running. The Repository Server disables the repository. You must enable the repository to start it. When you disable a running repository. Choose Action-Stop All. When you stop a disabled repository. You can view the progress of the stop operation in the Activity Log. The Repository Server stops all repositories it manages. You can disable a repository while it is running. see “Enabling the Repository” on page 71.To stop all repositories: 1. the repository status changes to disabled when you stop the repository. Disable the repository when you need to restore or upgrade the repository. 2. In the Console Tree. select the repository you want to disable. Starting and Stopping the Repository 73 . You must enable the repository before starting it again. In the Console Tree. For details on enabling the repository. You should also disable the repository when you edit configuration parameters that the Repository Server does not dynamically update. the repository status changes from running to disabled. select the Repositories node. To disable the repository: 1.

Choose Action-All Tasks-Notify Users. In the Console Tree. A message box informs the user that the notification was received. The Notification Message dialog box appears. Choose whether you want to send the notification message to users connected to the selected repository or all repositories managed by the Repository Server. select the repository you want to send the message to. You might want to send a notification message to notify users of scheduled repository maintenance or other tasks that require you to stop the repository or Repository Server. or to all users connected to all repositories managed by the Repository Server. 4. 3.Sending Repository Notifications You can create and send repository notification messages to users connected to the repository. You can send a repository notification message to users connected to a single repository. The Repository Server sends the notification message to all PowerCenter Client users connected to the repository. 74 Chapter 3: Managing the Repository . Enter the message you want to send. 2. You can view the message text on the Notifications tab of the PowerCenter Client Output window. To send a repository notification message: 1. and click OK.

you can register all local repositories with the copy of the global repository. Registering a PowerCenter Repository 75 .Registering a PowerCenter Repository You can register local repositories with a global repository to create a domain. see “Propagating Repository Domain Connection Information” on page 78. For example. The Repository Server reestablishes all global shortcuts unless you delete objects from the copied repository. If you unregister a repository from the global repository and then register it again. 2. Promote metadata from a local repository to a global repository. if you create a copy of the global repository and delete the original. see “Globalization Overview” and “Code Pages” in the Installation and Configuration Guide. you can perform the following tasks: ♦ ♦ ♦ ♦ Navigate from local to global repositories without connecting to each repository separately. Copy objects from the local repository to the global repository. propagate the domain connection information for the moved repository to other repositories in the domain. When you register a local repository. A Repository Server running on the same machine on which the repository resides yields higher performance for repository transactions. To register a local repository: 1. For details on code page compatibility. This allows you to copy objects from the local repository to the global repository and to create shortcuts or copy objects from the global repository to the local repository. For details on propagating repository domain registration information. the code pages of the local and global repository must be compatible. making it accessible to all local repositories in the domain. Choose Action-All Tasks-Register. select the global repository. You can register a local repository to the global repository managed by a different Repository Server. You might want to have the local and global repositories managed by different Repository Servers if the repositories reside on different machines. When working in a domain. Tip: You can also click Register in the Main window. Copy objects from or create shortcuts to metadata in the global repository. the Repository Server reestablishes global shortcuts. In the Console Tree. When you move a registered local or global repository to a different Repository Server in the domain.

76 Chapter 3: Managing the Repository . The Repository Server registers the local repository with the global repository. 6.The Register Repositories dialog box appears. Choose the global repository from the global repository list. 4. If you want to register a local repository managed by a different Repository Server. and enter your repository user name and password. Click Register. choose Managed By the Same Repository Server and select a repository from the local repository list. the host name of the Repository Server. Enter the repository user name and password for the local repository. Click Close. 7. and the port number the Repository Server uses for connections. 5. 3. 8. If you want to register a local repository managed by the same Repository Server. choose Managed By a Different Repository Server and enter the name of the local repository.

and stop the repository. see “Removing a Repository Configuration” on page 114. see “Connecting to the Repository Server” on page 58 and “Stopping the Repository” on page 72. For details. You can also export the repository configuration from the existing Repository Server. For details. Select the repository configuration under the new Repository Server. Use the following steps to migrate a repository to a different Repository Server: 1. If the repository you are moving is in a domain. and import the configuration into the target Repository Server. 4. If you want to migrate a repository that is in a domain. 3. For details. For details. see “Starting the Repository” on page 71. Move the repository license file specified in the repository configuration from the previous the Repository Server installation directory to the new Repository Server installation directory. Connect to the Repository Server hosting the repository. see “Propagating Repository Domain Connection Information” on page 78. see “Exporting and Importing Repository Configurations” on page 115. and start the repository. move and propagate each repository completely before moving another repository. The repository contacts other repositories in the domain and updates the domain connectivity information. propagate domain connectivity information for the repository. 6. For details on propagating domain connectivity information. Connect to the target Repository Server. For details. If you want to move multiple repositories in a domain to different Repository Servers.Migrating the Repository to a Different Repository Server You can change the Repository Server that manages a repository. Migrating the Repository to a Different Repository Server 77 . 5. Remove the repository configuration from the existing Repository Server. you must propagate domain connectivity information for the repository. and add a repository configuration. 2. see “Propagating Repository Domain Connection Information” on page 78.

you must update the connection information for other repositories in the domain. and propagate the connection information for local and global repositories in a specific order. you must configure repository connectivity. see “Upgrading a Repository” in the Installation and Configuration Guide. 78 Chapter 3: Managing the Repository . you must stop. 2. For details on migrating a repository. For details on upgrading a domain. start. upgrade. Use the Propagate command when you want to perform the following tasks: ♦ Upgrade a domain from a previous version of PowerCenter. If you want to change the Repository Server that manages a repository. Click OK. In the Console Tree. start. and propagate connection information for local and global repositories in a specific order. 3. The Repository Server contacts other registered repositories in the domain and updates the connectivity information for the repository.Propagating Repository Domain Connection Information Each local and global repository in a domain contains connectivity information to connect to the other repositories in the domain. Migrate one or more repositories in a domain to another Repository Server. When you upgrade a domain. If you want to change the Repository Server managing one or more repositories in a domain. Enter your repository user name and password. select the repository for which you want to change the repository connection information. see “Migrating the Repository to a Different Repository Server” on page 77. configure repository connectivity. Choose Action-All Tasks-Propagate. ♦ To update the connection information for a registered repository: 1.

Viewing User Connections You can use the Repository Manager or the Administration Console to view connection details for users and applications connected to the repository. To view user connection details: 1. The port number the machine hosting the repository client application uses to communicate with the repository. Launch the Repository Manager and connect to the repository.Viewing User Connections and Locks The Repository Manager and Administration Console allow you to view the connection details and locks details for users connected to a repository. Viewing User Connections and Locks 79 . The TCP/IP address of the machine associated with the connection. The time of the last metadata transaction between the repository client application and the repository. The identification number assigned to the repository connection. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. The name of the machine running the application. The repository client application associated with the connection. Repository User Connection Details Property User Connection ID Application Hostname Host Address Login Time Last Active Time Remote Host Port Description The user name associated with the connection. Table 3-5 describes the repository user connection details: Table 3-5. The time the user connected to the repository.

The Repository Connections dialog box appears. Viewing Locks You can view locks and identify residual locks in the Repository Manager or in the Administration Console. click on the column name. To view user connection details: 1. The Administration Console displays the repository user connection details in the Main window: 2. In the Console Tree. select the repository containing the user connections you want to view. and select the Connections node. 80 Chapter 3: Managing the Repository . Choose Edit-Show User Connections. Viewing Connection Details in the Administration Console Use the following procedure to view connection details in the Administration Console. To sort the connections by column. 3. click on the column name.2. To sort the connections by column.

Type of object. Type of lock: in-use. choose Edit-Show locks. or source. To sort your view of the locks by column. write-intent. Object Lock Properties Column Name User Connection ID Folder Object Type Object Name Lock Type Lock Time Hostname Application Description User name locking the object. The Object Locks dialog box appears. mapping. 3. Name of the locked object. Time the lock was created. Workflow Manager. 4. Name of the machine locking the object. To view updated lock information. To show all repository locks: 1. Folder in which the locked object is saved.Table 3-6 describes the object lock information in both the Repository Manager and the Administration Console: Table 3-6. click on the column name. The identification number assigned to the repository connection. click Refresh. version. 2. or execute. Viewing User Connections and Locks 81 . or Repository Manager. In the Repository Manager. To view all locks in the repository. such as folder. Viewing Locks in the Repository Manager Use the following procedure to view locks in the Repository Manager. connect to a repository. Application locking the object: Designer.

To show all repository locks: 1.Viewing Locks in the Administration Console Use the following procedure to view locks in the Administration Console. 2. Select the Locks node under the repository. The Administration Console displays the repository object lock details in the Main window: 3. select the repository containing the locks you want to view. In the Console Tree. 82 Chapter 3: Managing the Repository . To sort your view of the locks by column. click on the column name.

To manually close a connection in the Repository Manager: 1. When the Repository Agent closes the connection. see “Repository Manager Tasks” on page 516. You can also use the Repository Manager or Administration Console to manually close residual user connections and release residual locks in the repository. If an object or folder is locked when one of these events occurs. select the connection you want to terminate. the Repository Server also closes all other connections to the same PowerCenter Server.Closing User Connections and Locks Sometimes. repository. The Repository Agent closes the residual connection after three times the number of seconds specified for KeepAliveTimeout in the repository configuration. If a system or network problem causes a repository client application to lose connectivity to the repository. For information on the privileges and permissions to terminate other user connections and unlock objects. Informatica recommends that you allow the Repository Agent to automatically detect and release residual locks. In the Repository Connections dialog box. The PowerCenter Server opens additional connections to the repository for each Load Manager and DTM process. 3. Close residual connections only. the Repository Agent detects the residual connection. the repository does not release the lock. A residual repository connection also retains all repository locks associated with the connection. Warning: Closing an active connection may cause repository inconsistencies. If you close a repository connection to a PowerCenter Server. Launch the Repository Manager and connect to the repository. This is called a residual lock. 2. PowerCenter Server. However. Closing User Connections and Locks 83 . The repository has a residual connection when the repository client application or machine is shut down but the connection remains in the repository. the Repository Server does not immediately disconnect a user from the repository. A PowerCenter Client. This can happen in the following situations: ♦ ♦ Network problems occur. Closing Connections in the Repository Manager Use the following procedure to close connections in the Repository Manager. Choose Edit-Show User Connections. You do not need special privileges to terminate connections associated with your repository user name. or database machine shuts down improperly. it also releases all repository locks associated with the connection.

Verify the user is not connected to the repository. You can enter the user name and password associated with the connection. For more information. In the Console Tree. Enter the repository user name and password. Click Close to return to the Repository Manager. 3. The Main window displays the connections details. To terminate a connection associated with a residual lock. The Repository Server closes the connection and releases all locks associated with the connection. see “Viewing Locks in the Repository Manager” on page 81. Closing Connections in the Administration Console Use the following procedure to close connections in the Administration Console. select the repository containing the connection you want to release. 6. Click End Connection. see “Viewing Locks in the Administration Console” on page 82. Select the user connection and choose Action-End Connection. 84 Chapter 3: Managing the Repository . 4. To manually close a connection in the Administration Console: 1. and select the Connections node.4. or a user name and password with Super User privilege. 5. 5. first view the repository object locks to identify the connection ID number associated with the locks you want to release. Verify the user is not connected to the repository. For more information. 7. To terminate a connection associated with a residual lock. first view the repository object locks to identify the connection ID number associated with the locks you want to release. The Repository Server closes the user connection and releases all locks associated with the connection. 2.

please consult the plug-in documentation. select the Available Packages node. 2. The Repository Server registers plug-ins from the plug-in directory specified in the Repository Server setup program. For details.Registering and Unregistering Repository Plug-ins Use the Administration Console to register and remove repository plug-ins. You can also update an existing repository plug-in. Stop and disable the repository if it is running. see “Starting and Stopping the Repository” on page 71. The Repository Server lists the available plug-ins in the Repository Server plug-in directory. the plug-in directory is \Plugin in the Repository Server installation directory. By default. Repository plugins are third-party or other Informatica applications that extend PowerCenter functionality by introducing new repository metadata. Registering and Unregistering Repository Plug-ins 85 . Registering a Repository Plug-in Register a repository plug-in to add its functionality to the repository. In the Console Tree. For installation issues specific to your plug-in. To register a plug-in: 1.

select the repository in which to register the plug-in. Select the plug-in to register. 6. 3. You can view the registration process in the Activity Log. The Repository Server registers the plug-in with the repository. 86 Chapter 3: Managing the Repository . Enter your repository user name and password. You can choose to update a plug-in already registered in the repository. and connect to the Repository Server. To unregister a plug-in: 1. For the repository with the registered package. and choose Action-Register. Verify that all users are disconnected from the repository before you unregister a plug-in. 5. With the Registered Packages node selected. 2. drill down to the Registered Packages node in the Console Tree. You might choose to do this when you upgrade the plug-in to a new version. Use the following procedure to remove a plug-in from the repository. Unregistering a Repository Plug-in When you unregister a repository plug-in.3. the Repository Server stops and restarts the repository. 4. In the Register Security Module dialog box. right-click the package you want to unregister in the Main window. Open the Administration Console. Click OK.

Enter your repository user name and password. Click OK. Choose Unregister.4. 5. Registering and Unregistering Repository Plug-ins 87 . 6.

Registering and Unregistering LDAP Security Modules
You can register and unregister an LDAP security module by using the Repository Server Administration Console or the appropriate pmrepagent commands.

Registering an LDAP Security Module
If you are using an LDAP directory to maintain users and passwords for a repository, you must register and configure the authentication module with the repository. You can register the authentication module by using the Repository Server Administration Console, or by using the pmrepagent Registerplugin command. For information on the Registerplugin command, see “Registering a Plug-in (Registerplugin)” on page 482. You can configure the authentication module using the Administration Console, or you can update the configuration file with a text editor. When you install the Repository Server on Windows, the installation places an LDAP external module library file and an associated XML file in the Repository Server security folder.
C:\repserver\bin\security\ldapauthen.dll C:\repserver\bin\security\ldap_authen.xml

The ldap_authen.xml file displays in the Available Packages folder of the Repository Server Administration Console. This XML file specifies the security module. The following is a sample LDAP XML file:
<?xml version="1.0" encoding="us-ascii"?> <POWERMART> <REPOSITORY CODEPAGE ="us-ascii"> <PLUGIN ID ="3014" NAME ="LDAPAuthenPlugin" VERSION ="1.0.0" VENDORID ="1" VENDORNAME ="Informatica" DESCRIPTION ="LDAP Authentication Security module">

<TEMPLATE ID="400100" NAME="LDAP Authentication Module" TYPE="AUTHENTICATIONMODULE" DESCRIPTION="Authentication module implemented using LDAP" COMPONENTVERSION="1.0.0">

<LIBRARY NAME="ldapauthen.dll" OSTYPE="NT" TYPE="REPAGENT"/>

88

Chapter 3: Managing the Repository

</TEMPLATE> </PLUGIN> </REPOSITORY> </POWERMART>

The NAME attribute in the LIBRARY element specifies the .dll file that implements the authentication. The OSTYPE attribute specifies the operating system running the library file. The TYPE should be REPAGENT.
Note: If you back up and restore a repository to a machine with a different operating system,

the restore process might unregister the external security module if it cannot find the security library on the new platform. Change the NAME attribute and the OSTYPE in the XML file to use it on the new machine.

Registering the Authentication Module
Use the Repository Server Administration Console to select and register the LDAP authentication module for a repository server.
To register an LDAP security module using the Administration Console: 1. 2. 3.

Connect to the Repository Server. Stop and disable the repository if it is running. For details, see “Starting and Stopping the Repository” on page 71. Open the Available Packages node in the Console Tree.

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

Table 3-7 describes the information to enter in the Register Security Module dialog box:.
Table 3-7. Register Security Module Options Field Repository Update Security Module Registration Username Password External Directory Login Password Enable CRC Description Select the repository in which to register the module. Check this box if you are updating an existing security module. Leave it blank if this is the first time you are registering this module. Enter a user name that has Repository administrator privileges. You must have administrator privileges to register the security module. Enter the password for the Repository administrator. Enter a valid external login name for the module to use to connect to the external directory service. Enter the correct password for the external login name. Select Enable CRC to enable a runtime check the integrity of the authentication module library. This option stores the CRC of the plug-in library in the Repository. When the Repository Agent loads the authentication module, it checks the library against the CRC.

5.

Click OK. The Repository Server registers the plug-in with the repository. The LDAP security module displays under the repository in the Console Tree.
Registering and Unregistering LDAP Security Modules 91

Configuring the LDAP Authentication Module
When you use the LDAP authentication module you must configure it for the repository by updating the ldap_config.txt configuration file. This file resides in the bin\security folder in the Repository Server install directory. You can manually update this file, or you can use the Administration Console to update it.
To update the configuration using the Administration Console: 1. 2.

Open the Repository Server Administration Console and connect to the Repository server. Double-click the Available Packages node in the Navigator. The Repository Server displays the available plug-ins.

3.

Right-click the ldap_authen.xml authentication module and choose Configure. The Configure LDAP Authentication Module dialog box displays. You need to update both tabs to set the configuration.

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

Table 3-8 describes the LDAP server configuration file options:
Table 3-8. LDAP Server Configuration Options Field Server name Port Search Base Scope Description The name of the LDAP server. Port number to connect to the LDAP server. The port is usually 636 for SSL enabled servers, or 389 for non-SSL enabled servers. Distinguished name (DN) of the entry that serves as the starting point to search for user names. Scope of the user search. Options are: - base. Search the entry identified by SearchBase. - onelevel. Search all entries one level beneath the SearchBase entry. - subtree. Search the entire subtree at all levels beneath the SearchBase entry. Distinguished name (DN) for the principal user. Leave this blank for anonymous login. Password for the principal user. Leave this blank for anonymous login.

Principal User Name Principal User Password 5.

Click the Login Properties Tab to enter login properties and SSL information.

Registering and Unregistering LDAP Security Modules

93

Table 3-9 describes the Login Properties tab options:
Table 3-9. LDAP Login Properties Options Field Login Attribute Login Filter UseSSL Certificate Database Description The directory attribute that contains login names. Condition to filter results for user search. The filter can specify attribute types, assertion values, and matching criteria. Indicates if the LDAP server uses SSL. The path to the certificate database if you are using SSL. Click the browse button to find and select the certificate file.

Example
The following example shows ldap_config.txt options for a Microsoft Active Directory server running on server6. When a user connects to the repository, the authentication module binds as the principal user JSmith to the LDAP server server6. The LDAP server searches for users within the search base starting at the organizational unit TestUsers, and searches down the subtree. It checks objects in the “person” object class. The server searches for the object with the sAMAccountName equal to the user’s login name.
serverName=server6 port=389 principal=CN=JSmith credential=testpasswd searchBase=ou=TestUsers, dc=informatica, dc=com scope=subtree loginAttr=sAMAccountName loginFilter=(objectclass=person) useSSL=no certDB=

The following example shows ldap_config.txt options for a SunONE directory server running on port 503 on server mars. The principal user and credential options are blank, which indicates that the users access the LDAP server through anonymous login.
serverName=mars port=503 principal= credential= searchBase=ou=people, dc=informatica, dc=com scope=subtree loginAttr=uid

94

Chapter 3: Managing the Repository

loginFilter=(objectclass=person) useSSL=no certDB=

Unregistering an LDAP Security Module
You can unregister the LDAP authentication module by using the Repository Server Administration Console or by using the pmrepagent Unregisterplugin command. For information on the Unregisterplugin command, see “Unregistering Plug-ins (Unregisterplugin)” on page 487. If you unregister the external security module, PowerCenter switches to repository authentication mode. All user passwords reset to the values in the repository instead of the values in the external directory. When you unregister the security module you lose the mapping between the repository user names and the external security login names unless you specify to keep the user name/external login mapping. If you keep the mapping, you can reuse it later if you register a new security module.
Note: Although you can save the associations between external logins and repository user

names, the Repository Manager does not display the external logins while running under repository user authentication. You must specify a new password for the administrator when you unregister the security module. This ensures that you can access the repository once the external security directory is unregistered. You should unregister the LDAP package when no users are accessing the repository. When you unregister the package you have to restart the repository. All users are disconnected.
To unregister an LDAP package: 1. 2.

Open the Repository Server Administration Console and connect to the Repository Server. Double-click the Available Packages node in the Navigator. The Repository Server displays the available plug-ins.

3.

Right-click the ldap_authen.xml authentication module and choose Unregister.

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

Enter the LDAP Login properties shown in Table 3-10:
Table 3-10. LDAP Login Properties Options Field Administrator Username Password New Administrator Password Confirm Password Keep Username/ External Login Mapping Description The external login name for the repository administrator. The external login password for the repository administrator. The new password for the administrator to use with repository security after unregistering the external security module. Confirms the new password for the administrator. Keeps the mapping between the external user names and the login names in the repository. You can reuse this mapping if you register another external security module.

96

Chapter 3: Managing the Repository

Reading the Repository Log Files
The Repository Server and Repository Agent write error and operation messages to separate log files. The Repository Server log file contains information about managing the Repository Agents for all of the repositories configured to run on the Repository Server. The Repository Agent log file contains information about the operation of the Repository Agent managing each repository. The Repository Server and Repository Agent use a common format to log messages. Each message contains a log file code and process identification number used for troubleshooting purposes. The Repository Server and Repository Agent continuously append error and information messages to the log files. Depending on the number of repository transactions and the message severity level configured for the repository, the log files can grow to contain a large number of messages. Informatica recommends periodically deleting the Repository Server and Repository Agent log files and writing only higher severity level messages to the log files for normal operations.

Log File Codes
You can use the Repository Server and Repository Agent log files to determine the cause of repository problems. To troubleshoot repository problems, locate the relevant log file codes and text prefixes in the repository log file. Table 3-11 describes the codes that can appear in the Repository Server and Repository Agent log files:
Table 3-11. Repository Log Codes Log Code CNX LKM OBJM REP RCORE SF Description Messages related to connections to repository client applications. Messages related to obtaining and releasing repository object locks. Messages related to fetching, inserting, or updating repository objects. Messages related to communication between the Repository Agent and Repository Server. Messages related to Repository Server internal functions. Messages related to Repository Server status and management operations.

Process Identification
The Repository Server and Repository Agent append Windows or UNIX process identification numbers to the prefix of each message it writes to the Repository Server or Repository Agent log file. The process identification number helps you identify messages from a specific Repository Server or Repository Agent if you configure multiple repositories to write log messages to the same file.
Reading the Repository Log Files 97

You can verify the process ID number for the Repository Agent by checking the repository status. The process identification is printed before the message text in the repository log. The following example illustrates a connection message from a Repository Agent using process ID number 2548:
INFO : CNX_53037 [Thu Jul 15 10:45:44 2004]: (476|2548) Thread closing connection to the client.

Repository Server Log
By default, the Repository Server writes messages to the file pmrepserver.log. You can specify a unique log file name by configuring the Output to File option in the Windows Repository Server setup program. You can also configure the Windows Repository Server to log messages in the Windows event log. To view Repository Server messages in the Windows event log, you must be a system administrator on the machine hosting the Repository Server. You can specify a unique log file name on UNIX by configuring the Repository Server LogFileName option.

Repository Server Message Severity Level
You can configure the Repository Server to write the following levels of messages in the Repository Server log:
♦ ♦

Error. Indicates the repository failed to perform an operation or respond to a request from a repository client application. Error messages have the highest severity level. Warning. Indicates the Repository Server is performing an operation that may cause an error. This can cause repository inconsistencies. Warning messages have the second highest severity level. Information. Indicates the Repository Server is performing an operation that does not indicate errors or problems. Information messages have the third lowest severity level. Tracing. Indicates Repository Server operations at a more specific level than Information. Tracing messages are generally record message sizes. Trace messages have the second lowest severity level. Debug. Indicates Repository Server operations at the thread level. Debug messages generally record the success or failure of individual internal Repository Server operations. Debug messages have the lowest severity level.

♦ ♦

When you configure the repository to write messages of a specific severity level to the Repository Server log file, the Repository Server also writes all messages of greater severity to the log file. For example, if you configure the Repository Server to write Warning severity level messages to the log file, the Repository Server also writes Error severity level messages to the log file.

98

Chapter 3: Managing the Repository

INFO : SF_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed. Database : penguin@production. Sample Application Log If you configure the Repository Server to log messages in the event log. since some message codes are embedded within other codes. Repository Server Log File Sample The following sample is an excerpt from a Repository Server log file that illustrates log file codes: INFO : SF_34058 [Fri Jul 16 09:16:46 2004] : (1324|1452) Service started. Messages sent from the Repository Server display PmRepServer in the Source column. you must view the text of the message. to ensure you are viewing the true message code. the messages appear in the Application Log component of the Windows Event Viewer. the file can grow to contain a large number of entries. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information. INFO : REP_51036 [Fri Jul 16 09:37:37 2004] : (1396|1952) Error logging enabled INFO : REP_51035 [Fri Jul 16 09:37:37 2004] : (1396|1952) Repository agent connected to repository PRODUCTION. Reading the Repository Log Files 99 .When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. Informatica recommends setting the Severity Level option in the Repository Server configuration to Warning or Error unless you are troubleshooting a problem with the Repository Server. INFO : REP_51003 [Fri Jul 16 09:37:33 2004] : (1396|1952) Copyright (c) Informatica Corporation 2000-2001 INFO : REP_51004 [Fri Jul 16 09:37:33 2004] : (1396|1952) Informatica Repository Agent starting up. However. INFO : SF_34012 : (1324|1452) Opened Server Port [5001] to listen for client connections. INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. Database User : admin1 INFO : REP_51009 [Fri Jul 16 09:37:37 2004] : (1396|1952) Informatica repository agent ready to receive request on port 5003. INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up.

Application Log Message Detail Repository Agent Log File By default. Event Viewer Application Log Message Figure 3-5 shows the text of the message when you double-click it: Figure 3-5. You can specify a unique log file name for individual repositories by configuring the LogFileName option when you create or edit a repository configuration. 100 Chapter 3: Managing the Repository .log. You can write repository log messages from multiple repositories to the same log file. the Repository Agent writes messages to the file pmrepagent.Figure 3-4 shows a sample Windows Event Viewer: Figure 3-4. You can view the repository log file using a text editor program such as Windows Notepad.

♦ ♦ When you configure the repository to write messages of a specific severity level to the log file. Information. INFO : REP_51036 [Fri Jul 16 10:46:17 2004] : (2280|2256) Error logging enabled . Indicates the repository is performing an operation that may cause an error in a repository client application. For example. INFO : REP_51006 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized configuration information.You can also configure the Repository Agent to write messages of different severity levels to the log file depending on the value of the ErrorSeverityLevel configuration option when you create or edit a repository configuration. This can cause repository inconsistencies or cause repository client applications to report errors. if you configure the repository to write Warning severity level messages to the log file. Indicates the repository failed to perform an operation or respond to a request from a repository client application. Error messages have the highest severity level. INFO : REP_51008 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized request dispatcher. The Repository Agent also writes all messages of greater severity to the log file. Warning. the Repository Agent also writes Error severity level messages to the log file. Trace. the file can grow to contain a large number of entries. Warning messages have the second highest severity level. Reading the Repository Log Files 101 . Information messages have the second lowest severity level. When you configure the repository to write Information or Trace severity level messages to the repository log file. the Repository Agent writes a warning message to the Repository Agent log if you stop the repository when it has active connections. Repository Agent Log File Sample The following sample is an excerpt from a Repository Agent log file that illustrates log file codes and severity level messages: INFO : REP_51007 [Fri Jul 16 10:46:16 2004] : (2280|2256) Repository runtime manager initialized. Indicates the repository is performing an operation that does not indicate errors or problems with the repository. Repository Agent Message Severity Level You can configure the repository to write the following levels of messages in the Repository Agent log: ♦ ♦ Error. Trace messages have the lowest severity level. For example. Indicates repository operations at a more specific level than Information. Trace messages are generally record message sizes and locking operations for specific objects in the repository. Informatica recommends setting the ErrorSeverityLevel option in the repository configuration to Warning or Error unless you are troubleshooting a problem with the repository.

102 Chapter 3: Managing the Repository . port 2706. .. . TRACE : REP_51047 [Fri Jul 16 10:46:17 2004] : (2280|1980) Sending message of size 278 bytes. INFO : CNX_53039 [Fri Jul 16 10:46:17 2004] : (2280|1980) Received TCP connection from host p153894. .72. . WARNING: CNX_53056 [Wed Jul 14 13:21:51 2004] : (2588|2608) Shutting down the repository server with 3 connection(s) active.173).informatica. ERROR : CNX_53021 [Wed Jul 14 13:20:54 2004] : (2588|2336) Received an invalid request.1.com (10.

119 103 . 113 Removing a Repository Configuration. 115 Creating or Promoting a Repository. 114 Exporting and Importing Repository Configurations. 116 Working with PowerCenter Licenses. 105 Editing a Repository Configuration.Chapter 4 Configuring the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 104 Adding a Repository Configuration.

Database connection. Network. Promote a local repository to a global repository. This includes information. Export repository configurations. Create a repository. Use the Administration Console to perform the following tasks: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ 104 Chapter 4: Configuring the Repository . Add repository configurations. Edit repository license files. Edit repository configurations. Configuration. the Repository Server starts the repository using the stored connection information. This displays the license key information stored in the repository license file. such as repository name and version control. When you connect to the repository. This includes repository configuration information.Overview Each repository managed by the Repository Server contains connection information saved in a configuration file. ♦ Licenses. This includes receive and send timeout limits. Import repository configurations. You can also update the license keys in the license file. The Repository Server uses this information to connect to the repository database. You configure this file on the following tabs of the New Repository dialog box: ♦ ♦ ♦ ♦ General. Remove repository configurations. such as refresh interval and maximum connections. Enable version control for a repository.

and adds the repository name to the Console Tree. see “Upgrading a Repository” in the Installation and Configuration Guide. see “Restoring a Repository” on page 67. the Administration Console creates a configuration file in the Repository Server configuration directory. To add a repository configuration: 1. Upgrade an existing repository from an earlier version of PowerCenter or PowerMart. For more information. Restore a repository from a backup file. For more information. For more information. select the Repositories node and choose Action-New Repository.Adding a Repository Configuration Use the Administration Console to add repository configurations to the Repository Server. you can perform the following tasks: ♦ ♦ ♦ ♦ Create a repository in a database. Adding a Repository Configuration 105 . For more information. In the Console Tree. When you add a repository configuration. The New Repository dialog box appears. displaying the General tab. see “Migrating the Repository to a Different Repository Server” on page 77. When you add a repository configuration. see “Creating a Repository” on page 116. Change the Repository Server managing the repository.

To enable a repository for version control. Global Data Repository Optional Enable Version Control Optional Creation Mode Required 3. Click the Database Connection tab. Creates a versioned repository. Choose to create a new repository based on this repository configuration.2. Creates a global repository. Do not use the following characters when creating a repository name: \ / : * ? < > " | . New Repository . You can promote an existing repository to a versioned repository later. Once created.General Tab Option Name Required/ Optional Required Description The name of the repository. you cannot change a global repository to a local repository. Only enable this option if you are sure you want to create a versioned repository. you must have the Team-Based Development option license key in the repository license file. You can promote an existing local repository to a global repository later. Add the license key on the Licenses tab. 106 Chapter 4: Configuring the Repository . Table 4-1 describes the options available on the General tab: Table 4-1. Enter general information about the repository. Only enable this option if you are sure you want to create a global repository. or to add the repository configuration without creating a repository in the database.

or dbname. The repository code page. When you specify the tablespace name.Database Connection Tab Option Database Type CodePage Required/ Optional Required Required Description The type of database storing the repository. use the ODBC data source name. To improve repository performance on IBM DB2 EEE repositories. servername@dbname for Microsoft SQL Server. Set up this account using the appropriate database client tools. specify a tablespace name with one node. see “Creating a Repository” in the Installation and Configuration Guide. The account for the database containing the repository. see Table 16-1 on page 405. the Repository Server creates all repository tables in the same tablespace. Must be in 7-bit ASCII.world for Oracle). this is not an ODBC data source name. The native connect string the Repository Server uses to access the database containing the repository. The user name that starts the Repository Server must be a valid Windows user with access to the Microsoft SQL Server database. The repository database password corresponding to the database user. The Repository Server uses the character set encoded in the repository code page when writing data to the repository. Note that for most databases. the Repository Server uses Windows authentication to access the Microsoft SQL Server database. For Teradata databases. New Repository . If selected. For more information on using the tablespace names. ConnectString Required DBUser DBPassword Trusted Connection Required Required Optional TablespaceName Optional Adding a Repository Configuration 107 .Table 4-2 describes the options available on the Database Connection tab: Table 4-2. The tablespace name for IBM DB2 repositories. For a list of connect string syntax. You cannot use spaces in the tablespace name. but a native connect string (for example.

Default is 3. Enter the network information. Number of seconds the Repository Server waits while sending a message to a client application before timing out. 5. Table 4-3 describes the options available on the Network tab: Table 4-3. New Repository . Default is 3.4. Click the Network tab. 108 Chapter 4: Configuring the Repository .Network Tab Option MessageReceiveTimeout MessageSendTimeout Required/ Optional Required Required Description Number of seconds the Repository Server waits to receive a message from a client application before timing out.

Specify one of the following message levels: . . The level of error messages written to the Repository Agent log file.Information. The default date display format is DY MON DD HH 24:MI:SS YYYY.Trace. If the date display format is invalid. DateDisplayFormat Required Adding a Repository Configuration 109 . . Enter the repository configuration information. Informatica recommends using the Trace and Information logging levels for troubleshooting purposes only.6.Error. Writes INFO.Warning. the Repository Server uses the PowerCenter default date display format. Table 4-4 describes the options available on the Configuration tab: Table 4-4. WARNING. Writes TRACE. Default is 200. Writes WARNING and ERROR code messages to the log file. Writes ERROR code messages to the log file. and ERROR code messages to the log file. Click the Configuration tab. and ERROR code messages to the log file. INFO. 7. WARNING. . New Repository . The Repository Server validates the date display format and uses it when writing entries to the repository log file.Configuration Tab Option MaximumConnections ErrorSeverityLevel Required/ Optional Required Required Description The maximum number of connections the repository accepts from repository client applications.

Select to track changes made to users.Configuration Tab Option DynamicConfig RefreshInterval ThreadWaitTimeout Required/ Optional Required Required Description The number of seconds the repository waits to poll for updates to its configuration. Default is 50. For more information. Logged to pmsecaudit. is issued. The number of rows to fetch each time an array database operation. Minimum is 20. Default is 500. The path and name of the Repository Agent log file. Minimum is 30. the Administration Console displays a messaging informing you that the license file is empty. see “Repository Security” on page 125.log. The maximum number of locks the repository places on metadata objects. Default is 100.<repository_name>. New Repository . privileges. Default is 60. it times out the connection attempt after the number of seconds specified for DatabaseConnectionTimeout. the Repository Agent closes the connection.Table 4-4. The number of seconds the master thread running repository processes waits for process threads to stop before stopping. If you specify the same log file name for multiple repositories. and permissions. If you set this option to 0. MaximumLocks LogFileName Required Required KeepAliveTimeout Required DatabasePoolSize Required DatabaseConnection Timeout CheckinCommentsRequired SecurityAuditTrail Required Optional Optional DatabaseArrayOperationSize Optional 8.log file in the Repository Server installation/bin directory.000. The default is pmrepagent. The maximum number of connections to the repository database that the Repository Agent can establish. Click the Licenses tab. 110 Chapter 4: Configuring the Repository . Default is 60. The first time you click the Licenses tab when you create a repository configuration. groups. such as insert or fetch. If the Repository Agent tries to establish more connections than specified for DatabasePoolSize. The number of seconds the Repository Agent waits for a response from a repository client application before closing the connection. Default is 30 seconds. the Repository Agent does not timeout or close connections. The number of seconds the Repository Agent waits to establish a connection to the repository database before timing out. the Repository Agent writes messages for each repository to the same file. Default is 10. Requires users to add check in comments. If the Repository Agent receives no response from the repository client application in three times the number of specified seconds.

Consider the following rules and guidelines when you add license keys: ♦ You must add the product license key to the license file before you enter any option or connectivity license key. For more information about how the Administration Console creates repository file names. and click Update. You can use the Licenses tab to update and view the repository license file. enter the key in the License Key field. PowerCenter adds the product license key to the license file. PowerCenter only adds option and connectivity license keys to a license file when the license file contains a valid product license key. the Administration Console informs you it updated the license file successfully. The option and connectivity license keys you add must match the repository type. the Administration Console converts them to an underscore and a letter. The license file name is repository_name-es. either development or production. Click OK to close the message dialog box. Do this for every option and connectivity license key. of the other license keys in the license file. However. see “Repository License Files” on page 120. Add a license key to the repository license file. 10. Adding a Repository Configuration 111 . Displays the license keys and their properties in the license file. The Administration Console does not add invalid or expired license keys or license keys that already exist in the license file. If you have any option or connectivity license key. Displays the repository license file name. Displays the license key repository type.lic and is located in the Repository Server installation directory. The file is located in the Repository Server installation directory. ♦ ♦ When you enter a valid license key string. Add the product license key in the License Key field and click Update.9. either production or development. 11. when you use special characters in the repository name. You can also add license keys at any time.

When you restore a repository. the repository appears in the Console Tree under the Repositories node. Tip: To change the repository code page after you create the repository.For more information on licenses. 112 Chapter 4: Configuring the Repository . When the Repository Server finishes creating the repository. see “Working with PowerCenter Licenses” on page 119. you can specify any compatible code page. you can back it up and restore it. the Repository Server begins building the repository in the database. The Administration Console saves the repository configuration and adds it to the Repository Server configuration directory. If you select the Create all Database Tables for This Repository option on the General tab. 12. Click OK to save the configuration options.

2.Editing a Repository Configuration You can edit a repository configuration at any time. Enable the repository to allow other users or applications to start it. Use the following steps if you want changes to the repository configuration to take effect immediately: 1. see “Adding a Repository Configuration” on page 105. If you edit the configuration while the repository is running. Start the repository. Editing a Repository Configuration 113 . remove the repository configuration and create a new one with the correct tablespace name. If you create a repository configuration with a wrong or an invalid tablespace name. Stop the repository. 4. select the repository in the Console Tree and choose Action-Properties. the Repository Server updates changes to the configuration at an interval specified in the DynamicConfigRefreshInterval configuration option. Edit and apply changes in the Properties dialog box. 3. Disable the repository to prevent other users or applications from starting it. Note: You cannot change the tablespace name in the repository configuration after you enter it. 5. To edit a repository configuration. The Repository Server can update the following configuration parameters while the repository is running: ♦ ♦ ♦ ♦ MaximumConnections MaximumLocks ErrorSeverityLevel DatabasePoolSize Changes to other repository configuration parameters take effect the next time you start the repository. For details on the options in the Properties dialog box. Edit the repository configuration.

For details.Removing a Repository Configuration You can use the Administration Console to remove a repository configuration. see “Stopping the Repository” on page 72. The Repository Server removes the repository configuration. Click OK. see “Deleting a Repository” on page 64. The tables and metadata remain in the database. Note: If you select Delete the Repository. When you remove the repository configuration. Disable the repository to prevent other users or applications from starting it. You might want to remove a repository configuration if you migrate the repository to a different Repository Server and no longer want to use the old configuration to run the repository. 3. In the Console Tree. To remove a repository configuration: 1. When you remove the repository configuration. 2. For details. It does not remove the repository license file. select the repository. Choose to remove the repository from the server cache. Remove the repository configuration. and choose Action-Delete. see “Deleting a Repository” on page 64. 114 Chapter 4: Configuring the Repository . you remove the configuration only. For more information. see “Disabling the Repository” on page 73. For details on deleting the repository from the database. the Administration Console removes the repository from the Console Tree. 4. 5. the Repository Server deletes the repository from the database. The Deleting a Repository dialog box appears. and deletes the configuration file from the Repository Server configuration directory. This instructs the Repository Server to remove the repository configuration only. Stop the repository.

3. By default. If you want to export and import the repository registry information stored in the client registry. and choose Action-All Tasks-Export Connection. You can export and import configurations when you want move the repository to a different Repository Server. Importing a Repository Configuration Use the following procedure to import a repository configuration from a file. Locate the repository configuration file you want to import. select the Repositories node.Exporting and Importing Repository Configurations You can export a repository configuration to a . it displays the imported repository configuration under the Repositories node in the Console Tree. To export a repository configuration: 1. Choose Action-Import Repository Connection. When the Repository Server imports a configuration file. 3. select the repository from which you want to export the configuration information.cfg file. To import a repository configuration: 1. Click OK. see “Exporting/Importing Repository Connection Information” on page 32. and click OK. In the Console Tree. the Administration Console saves the file in the Repository Server configuration directory. In the Console Tree. Enter a name and location to store the export configuration file. You can import a repository configuration from a .cfg file. Exporting and Importing Repository Configurations 115 . The Export Repository Configuration to a File dialog box appears. The Repository Server imports the configuration information and creates a repository entry under the Repositories node in the Console Tree. Exporting a Repository Configuration Use the following procedure to export a repository configuration to a file. 2. 2.

the create operation fails.Creating or Promoting a Repository You can create a repository in a database based on a repository configuration. If you create a repository on a database with an existing repository. Note: If you want to create. consider keeping it separate from overloaded machines. you can register local repositories to create a domain. If you have the Team-Based Development option. you cannot change it to a local or standalone repository. The machine running the repository database system must have a network connection to the machine running the Repository Server. For more information. The repository database name must be unique. When you create a repository. In the new repository. this login becomes a default user with full privileges in the repository. Create and configure the database to contain the repository. You can create the repository on any supported database system. Tip: You can optimize repository performance on IBM DB2 EEE databases when you store an Informatica repository in a single-node tablespace. Setting this option changes the default null type of the column to null in compliance with the SQL standard. You can promote an existing repository to a global repository. set allow nulls by default to TRUE at the database level. Before you can create a repository. see “Creating a Repository” in the Installation and Configuration Guide. you must have the following information available: ♦ 116 Chapter 4: Configuring the Repository . 2. verify the repository database system meets the following requirements: ♦ ♦ ♦ Windows or UNIX operating system 100-150 MB disk space 128 MB RAM Database user name and password. After promoting a repository. Once you promote a repository to a global repository. When setting up an IBM DB2 EEE database. Creating a Repository Before you create a repository. restore. The password must be in 7-bit ASCII. This login must have database permissions to create the repository. or upgrade a Sybase repository. PowerCenter also allows you to enable version control for a new or existing repository. However. You must add the Team-Based Development option license key to the repository license file before you can enable version control. to protect your repository and improve performance. You must delete the existing repository in the target database before creating the new repository. Once you enable version control for a repository you cannot disable it. Add or import a repository configuration. the database administrator must define the database on a single node. you must complete the following steps: 1.

For more information on licenses. you can promote it to a global repository. the global and local repository code pages must be compatible. The Administration Console allows you to select from a list of code pages compatible with the PowerCenter Client code page. You must start the repository before you can promote it to a global repository. In the Console Tree. 2. Note: If a repository already exists in the database. 2. Choose Action-Properties. make sure the repository code page is compatible with each local repository you want to register. Verify the repository license file contains a valid product license key and any connectivity and option license key. For more information. it starts the Repository Agent. Contains the character set of the data in the repository. To promote a repository: 1. you cannot change the code page. For details on global and local repositories. Before promoting a repository to a global repository. you must create at least one folder before you can create objects in the Designer or Workflow Manager. see “Working with PowerCenter Licenses” on page 119. You can see the progress in the Activity Log. For more information. select a repository configuration under the Repositories node. you cannot change it to a local repository. see “PowerCenter Domains” on page 13. You must delete the existing repository in the target database before creating the new repository. When registering local repositories with a global repository. When the Repository Server finishes creating the repository. Choose Action-Create. once you create a global repository. In the Console Tree. you can specify a compatible code page. Creating or Promoting a Repository 117 . Tip: To change the repository code page after you create the repository. see “Creating a Folder” on page 171. However. When you restore a repository. see “Adding a Repository Configuration” on page 105. For details. ♦ Note: You can create a repository after you add a repository configuration. After creating a repository. see “Globalization Overview” in the Installation and Configuration Guide. you can back up and restore it. Once specified.♦ Code page. Promoting a PowerCenter Repository After you create a local repository. The repository code page must be compatible with the PowerCenter Server and Client code pages. The Repository Server begins building the repository. the Repository Server does not create the repository. select the repository you want to promote. License keys. To create a repository: 1.

queries. Enter your repository user name and password. The Repository Server promotes the repository to a global repository. To enable version control for a repository: 1. You must start the repository before you can enable version control. 3. For more information on working with versioned objects and versioned object properties. you can enable it for version control. see “Working with Versioned Objects” on page 199. select the Supports Version Control option. Version control allows you to maintain multiple versions of an object. you cannot disable it. control development on the object. Enter your repository user name and password and click OK. 118 Chapter 4: Configuring the Repository . Choose Action-Properties. 4. Enabling Version Control After you create a repository. The Repository Server enables version control for the repository and stops and restarts the repository for the changes to take effect. queries. and deployment groups. In the Console Tree. You can also use labels. The Administrator Console displays the Login Information dialog box.3. In the Properties dialog box. Note: To enable a repository for version control. you must have the Team-Based Development option license key in the repository license file. 4. When you enable version control for a repository. In the Properties dialog box. the repository assigns all versioned objects version number 1 and each object has an active status. Once you enable version control for a repository. see “Grouping Versioned Objects” on page 217. 2. and deployment groups to associate and copy specific groups of objects from one repository to another. and click OK. For more information on using labels. select the repository for which you want to enable version control. The Administrator Console displays the Login Information dialog box. and track changes. select the Global Data Repository option.

see “Managing License Files” on page 122. such as Team-Based Development. They also allow you to access PowerCenter Connect sources. A license file can contain multiple connectivity license keys. PowerCenter provides license keys based on the type of repository you have. License Key Types PowerCenter provides the following types of license keys: ♦ Product. and Server Grid. For more information about updating a license file. A license file can contain multiple option license keys. Informatica gives you one license key string that contains information for multiple connectivity licenses. These license keys allow you to access options. Option. These license keys allow you to access sources and targets. such as PowerCenter Connect for SAP R/3. This license key allows you to start the PowerCenter Server and the Repository Server and create repositories. You enter a product license key when you install the PowerCenter Server and Repository Server. You must update the PowerCenter Server license file with option and connectivity license keys after you install the product. Informatica gives one product license key for each product you purchase. PowerCenter provides different license key types. ♦ ♦ When you buy multiple connectivity license keys at the same time. When you create or upgrade a repository. The repository type applies to all license keys and license files. when you buy multiple option license keys at the same time. Use development license keys in a development environment. option. you can use the set of license keys for all repositories and PowerCenter Servers in your development environment. However. Also. You must have this license key when you install the PowerCenter Server and Repository Server. Note: You can update license files with option and connectivity license keys at any time. and connectivity license keys to the license file. Partitioning. development or production. When you purchase development license keys. either a PowerCenter Server license file or a repository license file. License Key Repository Types PowerCenter provides license keys based on the type of repository you have. you must add the product. development or production: ♦ Development. Working with PowerCenter Licenses 119 . PowerCenter stores the license keys in a license file. The installation program creates a license file in the PowerCenter Server installation directory to store the product license key you enter.Working with PowerCenter Licenses Informatica provides license keys for each PowerCenter Server and each repository. Informatica gives you one license key string that contains information for multiple connectivity licenses. Connectivity.

♦ Production. Table 4-5 describes how the Administration Console converts special characters in repository license file names: Table 4-5. You cannot mix development and production license keys in a license file. Note: You do not need a license file to start a PowerCenter Client tool. For example. the Administration Console converts them to an underscore and a letter. The license file is repository_name-es. such as the Designer. Informatica gives you a set of license keys for each repository you buy. the PowerCenter Server or repository fail to start. You cannot change the repository license file name. when you use special characters in the repository name. Note: Do not update a license file with a product key of a different repository type. or restore a repository. the Administration Console ignores all existing license keys and adds the product license key you specify. When you purchase production license keys. Repository License Files PowerCenter creates a repository license file for every repository configuration you create in the Administration Console. run. However. When you mix development and production license keys. When you do this. Use production license keys in a production environment. do not update a license file containing development license keys with a production product license key. The license file necessary to run the PowerCenter Server. Use one set of license keys for one repository and one PowerCenter Server only. + = ~ ` Characters Used in Repository License File Name _0 _A _B _C _D _E _F 120 Chapter 4: Configuring the Repository . Converting Special Characters in Repository License File Names Special Character in Repository Name _ . License File Types PowerCenter uses the following types of license files: ♦ ♦ Repository license file.lic. copy. PowerCenter Server license file. and it is located in the Repository Server installation directory. You lose the ability to use those option and connectivity license keys. The license file necessary to create.

see “Adding a Repository Configuration” on page 105. : / ? . the Repository Server verifies that the license file exists in the Repository Server installation directory. When you start a repository. If you have option or connectivity license keys. add them to the license file after you add the product license key. or if the file contains an invalid or expired product license key.Table 4-5. Working with PowerCenter Licenses 121 . If the Repository Server cannot find the license file. For more information on adding license keys to the repository license file. < > \ | \t (tab) \r (carriage return) \n (new line) Characters Used in Repository License File Name _G _H _I _J _K _L _M _N _O _P _Q _R _S _T _U _V _W _X _Y _Z _a _b _c _d _e You must add a valid product license key to the repository license file when you create the repository configuration. it fails to start the repository. Converting Special Characters in Repository License File Names Special Character in Repository Name ! % ^ & * ( ) [ ] { } ' " .

lic. the session or workflow might fail. The connectivity license key for that relational database. 122 Chapter 4: Configuring the Repository . It creates a license file. or if the file contains an invalid or expired product license key. Data Cleansing option license key. any file you specify must exist in the PowerCenter Server installation directory for the PowerCenter Server to start. The PowerCenter Server License File Must Contain.PowerCenter Server License Files When you install the PowerCenter Server. If they do not match. You can configure the PowerCenter Server to use a different license file. Managing License Files You manage license files using different PowerCenter tools. You can update and view repository license files for repositories managed by Repository Servers on UNIX and Windows. The connectivity license key for the particular PowerCenter Connect product. License File Compatibility Requirements When a Workflow Contains this Repository Object. The license keys in the PowerCenter Server license file must match the license keys in the repository license file when the PowerCenter Server runs workflows in the repository. in the PowerCenter Server installation directory. Table 4-6 describes the compatibility requirements when a PowerCenter Server runs a workflow: Table 4-6. the session fails. PowerCenter Connect for Web Services connectivity license key. A session configured to use multiple partitions. Source or target definition using a relational database connection. Application Source Qualifier transformation. Server grid option license key. You can manage license files using the following PowerCenter tools: ♦ Administration Console. However. see “Adding a Repository Configuration” on page 105. Workflow configured to run on a server grid. When you run the workflow. assign the workflow to a PowerCenter Server that has the Partitioning option license key.. Partitioning option license key. For example. depending on the license file type and the operating system. To verify the session completes. For more information about using the Administration Console to manage license files. You cannot start the PowerCenter Server if the specified license file does not exist. You include the session in a workflow and assign the workflow to a PowerCenter Server that does not have the Partitioning option license key. Source definition configured to extract data from web services.. pm. you create multiple partitions in a session.. Parse or Address transformation available with the Data Cleansing option. the installation program prompts you for the product license key..

For more information about using pmlic. That license file must exist in the PowerCenter Server installation directory for the PowerCenter Server to start. Do not modify license files manually. Then add option and connectivity license keys. To manage a PowerCenter Server license file for a PowerCenter Server on UNIX. For information about using the PowerCenter Server Setup to manage PowerCenter Server license files. You must purchase a production license key for every repository and PowerCenter Server in your production environment. ♦ Note: Only use the PowerCenter tools to edit a license file. PowerCenter Server setup. Do not edit them manually. For details. Specify the PowerCenter Server license file name in the PowerCenter Server setup. Use production license keys in a production environment. The repository license file specified in the repository configuration must exist in the Repository Server installation directory for the repository to start. You can manage all license file types. All license keys in a license file must be of the same repository type. Use the PowerCenter tools to modify license files. You can use a development license key for all PowerCenter Servers and repositories in your development environment. see “PowerCenter Server License Files” on page 122. Update PowerCenter Server license file with connectivity and option licenses after you install the PowerCenter Server. Enter the product license key on the Licenses tab of the repository configuration when you create a new repository configuration. you must use pmlic. ♦ ♦ ♦ ♦ ♦ ♦ Working with PowerCenter Licenses 123 .♦ pmlic. Rules and Guidelines Use the following rules and guidelines when you work with PowerCenter license keys and license files: ♦ ♦ ♦ ♦ Enter the product license key when you install the PowerCenter Server or Repository Server. see “Installing and Configuring the PowerCenter Server on Windows” in the Installation and Configuration Guide. see “Installing and Configuring the PowerCenter Server on Windows” in the Installation and Configuration Guide. either production or development. Use development license keys in a development environment. You can manage license files for a PowerCenter Server on Windows. Verify that the PowerCenter Server that runs workflows in a repository uses a license file with the same license keys that exist in the repository license file.

124 Chapter 4: Configuring the Repository .

Chapter 5 Repository Security This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 142 Permissions. 148 Managing User Connections. 160 Troubleshooting. 127 User Authentication. 134 Repository Privileges. 126 User Groups. 154 Handling Locks. 163 125 . 151 Creating an Audit Trail. 153 Repository Locks. 131 Creating and Editing Repository Users. 157 Tips.

Locking. You can use an external directory service to manage your user names and passwords. you need to determine if the owner of the lock is using the object. Folder permissions. Repository users. you may require permission to perform the task within a given folder. User connections. and the rest of the repository users. fetch. ♦ ♦ ♦ ♦ ♦ ♦ Informatica recommends taking time to plan your overall strategy so that you can implement appropriate security measures to protect your repository. you need to determine if the user has an active connection before closing the connection. Most tasks also require the appropriate repository privileges. The ability to perform tasks within an individual folder. You can assign privileges to individual user names. Each user must have a unique repository user name to use folder and object locking properly. The repository locks repository objects and folders by user.Overview PowerCenter offers several layers of security that you can customize for your repository. The ability to perform actions within the repository and to start and stop the PowerCenter Server. write-intent. You assign repository privileges to users and groups. The repository creates five kinds of locks depending on your task: in-use. Versioning objects include labels. execute. Repository privileges. You can assign users to multiple groups. You can plan and implement security using these features: ♦ User groups. Repository groups for user names. The Repository Server locks and unlocks all objects in the repository. deployment groups. The ability to use versioning objects for change management. You can grant versioning object permissions to users and groups. User name used to access the repository. and save. You can grant permissions on three levels: to the folder owner. You can also assign privileges to groups. but to avoid repository inconsistencies. a group to which the owner belongs. You must assign each user to at least one user group. You can perform some tasks with folder permissions only. 126 Chapter 5: Repository Security . Every user in a group receives the privileges for that group. Versioning objects permissions. You can use the Repository Manager to monitor user connections to the repository. To avoid repository inconsistencies. Even if you have the repository privilege to perform certain tasks in the repository. You can end connections when necessary. You can manually release a lock on an object by ending the connection of the user holding the lock. and queries.

However. These two groups exist so you can immediately create users and begin developing repository objects. Each repository user must be assigned to at least one user group. For details. Inherits any change to group privileges. you assign that group a set of privileges. This grants the user the privileges of each group. if a user has been granted the privilege individually (as with default privileges). When you assign a user to a group. the Repository Manager creates two repository user groups. After creating a new user group. For a list of default privileges. You can also assign users to multiple groups. Note: When you revoke a privilege from a group. Use the Repository Manager to create and edit repository user groups. Loses and gains privileges if you change the user group membership. see “Repository Privileges” on page 142. Default Groups When you create a repository. you must revoke the privilege individually to restrict that user. For information on the privileges and permissions to administer repository user groups see “Repository Manager Tasks” on page 516. The Repository Manager creates two default users in the Administrators group: ♦ ♦ Administrator The database user name used to create the repository You cannot delete these users from the repository or remove them from the Administrators group. User Groups 127 . you can also create custom groups and assign specific privileges and permissions to those groups. the user: ♦ ♦ ♦ Receives all group privileges. you revoke the privilege from each user in the group. There are two default repository user groups: ♦ ♦ Administrators Public You cannot delete these groups from the repository or change the default privileges.User Groups You create custom user groups to manage users and repository privileges efficiently. The Repository Manager does not create any default user for the Public group. see “Default Privileges” on page 143. However.

Choose Security-Manage Users and Privileges.User Groups and Folder Permissions When you create or edit a folder. For example. 3. you must choose one of those groups to receive Owner’s Group permissions. you must select one of those listed groups to receive Owner’s Group permissions. you can define Owner’s Group permissions for the folder. the Production group receives read and write permissions on the folder. If the owner of the folder belongs to both the Developer group and the Production group. You can only grant Owner’s Group permissions to one of the groups to which the folder owner belongs. If you assign read and write folder permissions to Owner’s Group. if the owner of a folder belongs to only one group. If the owner belongs to more than one group. connect to a repository. 2. 128 Chapter 5: Repository Security . the Developer group receives Owner’s Group permissions on the folder. In the Repository Manager. then every user in the Developer group has read and write permission for the folder. Developer. Select the Groups tab. Creating a User Group Perform the following steps to create a user group. To create a user group: 1. If you select the Production group.

Choose Security-Manage Users and Privileges. Public and Administrators. Click OK again to save your changes. 6. connect to a repository. 2. the Repository Manager reassigns those users to the Public group. Select a group in the Groups tab and click Edit. 3. and click OK. You can enter up to 2. To edit a user group: 1. The new group now appears in the list of all groups defined for the repository. connect to a repository. User Groups 129 .4. Select the group in the Groups tab that you want to delete. Deleting a User Group You can delete any user group in the repository except the default repository user groups. Click OK. You can now assign privileges and users to the group. 7. 5. In the Repository Manager. Note: If you delete a group that contains users. Click OK to return to the Repository Manager. Choose Security-Manage Users and Privileges. Enter the name of the group. 5. 4. Editing a User Group You can edit the description of an existing user group at any time. you cannot edit the default groups. Edit the description. Click Add. In the Repository Manager. Public and Administrators. 3. To delete a user group: 1. 2. However.000 characters. Only the first 256 characters display in the Manage Users and Privileges window.

Click OK. 6. Click Remove. Click OK to save your changes. A message appears stating all users in the group will be assigned to the Public group. 130 Chapter 5: Repository Security .4. 5.

you User Authentication 131 . The user cannot access the repository. If you use LDAP to authenticate users. The repository administrator maintains the user name-login associations. The security module verifies users against these user names and passwords. For more information see “Registering a Plug-in (Registerplugin)” on page 482.User Authentication Each repository user needs a user name and password to access the repository. When you create a new user. Tip: If you are using default authentication. A user receives this status if the repository administrator disables the user. repository users can have one of the following statuses: ♦ ♦ Enabled. The default password for Administrator is Administrator. The security module supports the following types of user authentication: ♦ ♦ PowerCenter default authentication Lightweight Directory Access Protocol (LDAP) authentication PowerCenter default authentication enables you to create users and maintain passwords in the repository. see “Repository Manager Tasks” on page 516. Using Default Authentication If you use default authentication. When you create a repository. The database user name and password used when you created the repository. Database user. the repository creates two default users: ♦ ♦ Administrator. the repository security module passes a user login to the external directory for authentication. but does not maintain user passwords in the repository. These users are in the Administrators user group. For information on the privileges and permissions to administer repository users. with full privileges within the repository. LDAP defines a network protocol for accessing a directory service. You cannot remove them from the Administrators group or delete them from the repository. Using LDAP Authentication If you use LDAP authentication for repository users. the repository maintains an association between repository user names and external login names. change the Administrator password immediately after creating the repository to protect your metadata. the repository maintains an association between repository user names and external login names. New users receive the enabled status. PowerCenter uses a security module to verify user log in. To accomplish this. Disabled. If you use an external directory service. The user name is valid for accessing the repository. you must ensure that the Administrator has a valid external login name when you register the authentication module with the repository.

A repository user called JSmith might have a directory login of JohnS on the new server. This status occurs when you change from the default authentication to an external directory service. Repository User Names and External Login Names User Status Login Name Repository User Name The user status indicates if a user can access the repository.can select the login name from the external directory. The user cannot access the repository. When you view users in the repository. or if you know the directory login name. Figure 5-1 shows the repository user names and associated login names: Figure 5-1. You must associate JSmith with the directory login JohnS in order for him to access the repository. When you add new users they receive the enabled status. No login assigned. For more information about Registeruser. The repository user name is not linked to an external login name. Disabled. 132 Chapter 5: Repository Security . The user name is valid for accessing the repository. Users can have one of the following statuses: ♦ ♦ ♦ Enabled. see “Enabling a User” on page 139. you might deploy a repository to a new server. Explicitly disabled from accessing the repository by the Administrator. you can use the pmrep Registeruser command to create the user name and associated login name. The Repository Administrator must explicitly enable the user by linking the user name to the login name. you can see the repository user names and the directory login names. For more information on associating a user name to a login name. see “Registering a User (Registeruser)” on page 457. For example.

the status for the associated user name becomes “no login assigned. if your login changes on the external directory.♦ Login suggested. ♦ User status changes for the following reasons: ♦ ♦ ♦ Switching Between Default and External User Authentication If you switch from default authentication to external directory authentication. but is not linked to a login name (as above) in the external directory. For example. This status is similar to “no login assigned” except that the security module finds a possible matching login name that you can enable. your existing repository users receive the “no login assigned” or “login suggested” status. However. The system administrator enables or disables it. You do not see the associations in the Repository Manager. The login changes on the LDAP directory. When you retain the repository user name-login associations you can reuse the associations if you register another external directory service for authentication. Account removed.” The Repository Administrator must explicitly enable you by linking your repository user name to a new login name in the external directory. The user name is no longer on the external directory. the users you add under the external directory service have the disabled status.” User Authentication 133 . but user authentication does not use them. The status changes to “account removed. You must enable these users by associating their repository user names with valid external directory login names. and the user cannot access the repository. If a login is not valid on the new external directory. The user authentication mode changes between LDAP and default authentication. you can retain the user name-login associations in the repository. The user name is in the repository. If you switch from using external directory authentication to default authentication. the security module cannot find the login name.

When you create a user. you create a different user name for each user accessing the repository. create user groups. The New User dialog box displays. you enter user names in the repository and assign a password for each user name you create. In the Repository Manager. To create a user under default authentication: 1. then remove the user from the Public group. Click Add. 134 Chapter 5: Repository Security . Creating a User Under Default Authentication If you are using default user authentication.Creating and Editing Repository Users In the Repository Manager. you must first add the user to another group. 2. For information on the privileges and permissions to create a repository user. see “User Groups” on page 127. and assign the appropriate privileges to those groups. Choose Security-Manage Users and Privileges. For details on groups. To change the group. see “Repository Manager Tasks” on page 516. Each user belongs to at least one user group. 3. connect to a repository. The Manage Users and Privileges dialog box displays. the Repository Manager assigns the user to the Public group. Tip: Before creating repository users.

5. The group to which the user belongs appears in the Member Of list. Creating and Editing Repository Users 135 . with no leading or trailing spaces. To add the user to a group. Click Group Memberships. You can use the optional Description and Contact Info fields to further identify the user. 6. select the group in the Not Member list.4. and click Add. Enter a user name and password between 1 and 75 characters long. The remaining groups appear in the Not Member Of list.

2. For information on the privileges and permissions to edit your own password see “Repository Manager Tasks” on page 516. 136 Chapter 5: Repository Security . 5. 7. Click OK to return to the Repository Manager. select the group in the Member list. Editing a User Password If you are using default authentication. Click OK. you can edit your user password. Note: You cannot remove a user from a group when the user belongs to only one group. connect to the repository. Enter the old password. and click Remove. Enter the new password twice to confirm it. In the Repository Manager. 3. To remove the user from a group. To edit a password: 1. Choose Security-Change Current Password.The group appears in the Member list. 8. 4.

click Check Names. If you select more than one name. connect to a repository. you add repository users from a list of login names from the external directory. Choose Security-Manage Users and Privileges. 2. Note: You can type a name at the bottom of the screen. To add users with an external directory service: 1. The Add Users dialog box displays a list of names from the external directory service.Creating a Repository User Under an External Directory Service If you are using an external directory service for maintaining repository users. 4. Creating and Editing Repository Users 137 . the names display at the bottom separated by semi-colons. but it must match a valid login name in the directory. 3. The login name displays at the bottom of the screen. Select a login name from the external directory list and click Add. You do not create repository user passwords. To check the spelling. Click Add. In the Repository Manager.

Editing a User You can edit users to maintain their group memberships and change their login status. you can remove it from the repository. You cannot edit any property for the Database user except contact information. If you use default authentication. The Manage Users and Privileges screen displays the user name. Click OK. You cannot change group memberships for the Administrator user. If any of the names you type in do not match a valid directory service login. so the repository user name maps to a new login name. In the Repository Manager. you can change the password. or editing a user description. 3. To edit a user: 1. login name and enabled status. 6. If you use default authentication. You can edit users with the following exceptions: ♦ ♦ ♦ ♦ You cannot edit passwords if you use an external directory for security. you must correct the name or remove it from your selections on the Invalid Name dialog box. To change the password. with no leading or trailing spaces. The password can be between 1 and 75 characters long.5. you can change a user password. You cannot change a user name. 4. If you use an external directory service you can change the user name-login association. 138 Chapter 5: Repository Security . The Edit User dialog box displays. connect to a repository. Refer to the next section for information on adding a user to a group. 2. enter the new password twice. Highlight a user and click Edit. Passwords must be in 7-bit ASCII only. If a user name becomes obsolete. Choose Security-Manage Users and Privileges. Click OK on the Add Names dialog box to add your selections to the user name-login name association.

and click Remove. Enabling a User A user with a status other than enabled cannot access the repository. When you enable a user and you are using an external directory service. you link their repository user name with their directory login name. To edit group memberships. 7. One of the following actions occurs for each selected user: ♦ ♦ The user status changes to enabled. The group appears in the Member Of list. To edit the description. The first 256 characters display in the Manage Users window. The Manage Users and Privileges dialog box displays. To save your changes. 10. You can select multiple users at a time. select the group in the Not Member Of list. 2. This occurs if you use default authentication. and click Add. When you enable a user under default authentication. The Select Login Name dialog box displays. only the status changes. The selected group appears in the Not Member Of list. 6. Click Enable. If the user belongs to only one group. 3. To remove the user from a group.5. You must explicitly enable the user. To enable a user: 1. click OK. Click OK again to return to the Repository Manager. select the group in the Member Of list. It displays if you are using an external directory service. you must add the user to another group before removing the user from the original group.000 characters. Creating and Editing Repository Users 139 . enter up to 2. This dialog box displays a list of valid login names from the external directory service. To add a group membership. Select the users you want to enable. click Group Memberships. 9. Choose Security-Manage Users and Privileges. 8. or if you are enabling a user that has a suggested login name.

2. connect to a repository. If you use the Select Login Name dialog box. Click Disable. select a login name from the list and click OK. 140 Chapter 5: Repository Security . you enable the association immediately when you click Enable. see “Editing a User (Edituser)” on page 454. The Manage Users and Privileges dialog box displays the login name and the associated repository user name. For more information about Edituser. In the Repository Manager. Choose Security-Manage Users and Privileges. 3. If you enable more than one user. this dialog box displays again for the next user. When you disable a user. The user status changes to disabled. To associate the user name with a different login name. You can select multiple users at a time. Note: You can disable users from the command line.If a user has a suggested login name. You can disable users when you use default security or external user authentication. see “Editing a User (Edituser)” on page 454. For more information. The user status becomes enabled. so you can quickly enable the user at a later time. 4. Disabling a User When you disable a repository user you change the user status from enabled to disabled. Select the users you want to disable. To disable a repository user: 1. you can disable and then enable the user. You can also use the pmrep Edituser command. you retain the user name in the repository. 4. Disabled users cannot access the repository.

you remove the user name in the user name login association. 4. 3. 2. If you use default authentication. you remove the user name from the repository. Click Yes to confirm that you want to remove the user. Creating and Editing Repository Users 141 . connect to a repository. In the Repository Manager. Choose Security-Manage Users and Privileges.Removing a Repository User When you remove a user from the repository that is using an external directory service. To remove a repository user: 1. Select a user and click Remove.

you can also grant privileges to individual users. however. For more information on versioning object permissions. You can add or remove privileges from any user or group except: ♦ ♦ Administrators and Public (the default read-only repository groups) Administrator and the database user who created the repository (the users automatically created in the Administrators group) Ordinarily. This limits the number of users with the Super User privilege. Folder related tasks. generally require one or more folder permissions in addition to the related repository privilege to perform the task. Users with only the Use Designer or Use Workflow Manager privilege can do many of the tasks that Use Repository Manager allows. such as stopping the PowerCenter Server or creating user groups. and execute permissions. if you grant the Administer Repository privilege to the user. grant the Super User privilege to an individual user. but only within the Designer or Workflow Manager. if you move a user from a group that has the Administer Repository privilege into a group that does not. 142 Chapter 5: Repository Security . not an entire group. you grant privileges to groups. The Use Repository Manager privilege enables you to use management functions such as mass validating or applying labels. For example. see “Configuring Versioning Object Permissions” on page 149. However. and ensures that the user retains the privilege even if you remove the user from a group. You can perform some tasks in the repository with only repository privileges. write. However. For tighter security. see “Permissions and Privileges by Task” on page 509. A privilege granted to an individual user remains with the user until you remove it.Repository Privileges The Repository Manager grants a default set of privileges to each new user and group for working within the repository. For a list of common repository tasks and the permissions and privileges necessary to perform those tasks. Versioning objects and connection objects have separate read. the user loses the Administer Repository privilege. the user retains this privilege regardless of changes in group membership.

Default Privileges The Repository Manager grants each new user and new group the default privileges.Change your user password.Copy objects into the folder. .Add and remove reports.Create shortcuts to objects in the folder.Copy objects from the folder.Create shortcuts from shared folders. or remove the registry. . . .Export objects. .Copy a folder.Import objects. .Browse repository. Table 5-1 lists the default repository privileges: Table 5-1. . .View objects in the folder. Read Folder Read/ Execute Read/Write Use Designer n/a Query Query n/a Read Folder Read/Write Folder Use Repository Manager* n/a Write n/a Deployment group Repository Privileges 143 . . Default Repository Privileges Default Privilege Browse Repository Permission n/a Permission Object n/a Grants You the Ability to . . .Create or edit metadata.Import.Freeze folders you own.Delete from deployment group.Connect to the repository using the Repository Manager. You must also have Administer Repository or Super User privilege in the target repository. . .Remove label references. export. . . . .Search by keywords. .Unlock objects and folders locked by your user name.Edit folder properties for folders you own.Perform Use Repository Manager tasks in the Designer.View dependencies. . . .Create or edit query.Configure connection information. .Connect to the repository using the Designer. . .Run query. .

.Stop workflow.Run the Workflow Monitor. . . .Change status of the object. . . and external loader connections in the Workflow Manager. .Edit database. .View session log. .View tasks. .Mass validation (Needs write permission if options selected.Change object version comments if not the owner.Export objects.Validate workflows and tasks.Export objects.Start workflows immediately. .Schedule or unschedule workflows.Resume workflow. . . . .Abort workflow.Restart workflow.Perform Use Repository Manager tasks in the Workflow Manager.Create database.Copy objects. FTP. . .Check out/undo check-out. . .Table 5-1.Delete objects from folder. Read Read Write Read Write Read Write/ Execute Use Workflow Manager n/a Folder Folder Deployment group Original folders Target folder Folder Label n/a . . . and external loader connections in the Workflow Manager. .Add to deployment group.Connect to the repository using the Workflow Manager. Read/Write Execute Connection Folder Read Folder Read/ Execute Read/ Execute Read/Write Folder Connection Folder 144 Chapter 5: Repository Security . . .View session details and session performance details.Create and edit workflows and tasks.) .Apply label.View workflows. . .Check in.Import objects. . .Recover after delete. Default Repository Privileges Default Privilege Permission Write Permission Object Folder Grants You the Ability to .Import objects.View sessions. FTP. .

. Default Repository Privileges Default Privilege Permission Read/Write Read Permission Object Folder Connection Grants You the Ability to . . .Create. and restore the repository.Freeze folder. delete.Create and edit sessions. Repository Privileges 145 . * The Use Designer and Use Workflow Manager privileges enable you to do many of the tasks that you can do in the Repository Manager with the Use Repository Manager privilege.Copy a folder into the repository.Administer label permissions. . the Repository Manager provides extended privileges that you can assign to users and groups.Create deployment group. groups. stop. .Copy a folder within the same repository. enable. . .Manage connection object permissions.Create label.Copy a folder into a different repository when you have Administer Repository privilege on the destination repository. .Copy deployment group. users. .Edit folder properties. Extended Privileges In addition to the default privileges listed above.Check in or undo check out for other users. . upgrade. backup.Manage passwords.Edit label. . and check the status of the repository. Read Read n/a Connection Read/Write Read/Write Read/Write Read Read/ Execute Write Deployment group Folder Label Original folder Deployment group Folder . .Purge a version.Table 5-1. Table 5-2 lists the extended repository privileges: Table 5-2. disable. The Repository Manager grants extended privileges to the Administrator group by default. . Extended Repository Privileges Extended Privilege Administer Repository Permission n/a Permission Object n/a Grants You the Ability to . . and privileges.Create and edit deployment group. .Start. .Administer deployment group permissions.

. .View the session log. For information on the privileges and permissions to assign or revoke privileges.Start workflows immediately. The user entered in the PowerCenter Server setup must have this repository privilege.Mass updates.Perform all tasks.Start the PowerCenter Server. . .Resume workflow. . However. .Edit server variable directories. .Stop workflow.Abort workflow.Restart workflow. 146 Chapter 5: Repository Security . . Extended Repository Privileges Extended Privilege Administer Server Permission n/a Permission Object n/a Grants You the Ability to . Informatica recommends that you reserve extended privileges for individual users and grant default privileges to groups. Assigning and Revoking a Privilege You can assign and revoke repository privileges to a user or group. When you change privileges for a group. Note: You cannot change the privileges of the default user groups or the default repository users. across all folders in the repository. . .Manage connection object permissions. . . . Repository Manager.Table 5-2. . users retain individually granted privileges until you revoke them individually.Manage versioning object permissions.Use pmcmd to start workflows in folders for which you have execute permission. .Stop the PowerCenter Server through the Workflow Manager. see “Repository Manager Tasks” on page 516. Extended privileges allow you to perform more tasks and expand the access you have to repository objects. . and Workflow Monitor.Connect to the PowerCenter Server. . Super User n/a n/a Workflow Operator n/a Read n/a Folder Execute Folder Read Execute Execute Execute Folder Connection Folder Connection The default privileges allow you to perform basic tasks in the Designer. Workflow Manager.View session details and performance details. you change the privileges granted to every user in the group.Register PowerCenter Servers with the repository.Schedule and unschedule workflows. .Stop the PowerCenter Server using the pmcmd program.

2. Select the privileges you want to assign to each user or group. 5. 2. Note: If you assign Super User privileges to a user. Choose Security-Manage Users and Privileges. Click OK to save your changes. To revoke a privilege from a user or group: 1. Super User privilege enables all privileges for that user. Choose Security-Manage Users and Privileges. connect to a repository.To assign a privilege to a user or group: 1. 3. Click Privileges. Click OK to save your changes. In the Repository Manager. connect to a repository. 4. Clear the privileges you want to revoke. 3. 4. Repository Privileges 147 . In the Repository Manager. you cannot change the other privileges for them.

you might have the Use Designer privilege. if you grant only read permission to a folder Owner. For example. and connections.Permissions You can maintain user and group permissions for access to folders and versioning objects. If you have the Super User privilege. You can grant folder permissions on three levels of security. you do not require any permissions. Repository Each permission level includes the members of the level above it. If the owner belongs to more than one group. you can start a workflow if you have only read permission. All groups and users in the repository. Execute permission. see the Workflow Administration Guide. maintain queries or labels. Versioning objects are labels. the folder owner has both read and write permission on the folder. as listed in the owner menu. 148 Chapter 5: Repository Security . including the owner. add or delete objects from deployment groups. Configuring Folder Permissions Certain privileges require fewer folder permissions to perform a given task. but you must also have folder read and write permission to open and edit a mapping in a folder. If you do not have both the privilege and permissions. If you have the Workflow Operator privilege. This becomes the Owner’s Group. if you have the default Use Workflow Manager privilege. deployment groups. apply labels. you must select one of those groups in the folder dialog box. Allows you to run or schedule a workflow in the folder. you cannot open or edit mappings in that folder. Allows you to view the folders and objects. and grant read and write permission to the Owner’s Group. Allows you to create or edit objects in a folder. while the Super User privilege requires no folder permissions. Folder Object Security Levels Level Owner Owner’s Group Includes The owner of the folder. You can maintain the following permissions for each type of object: ♦ ♦ ♦ Read permission. or copy deployment groups. For details on configuring connection object permissions. To perform a task you must have the privilege to perform the task in the repository as well as the applicable permission. Table 5-3 lists folder security levels: Table 5-3. queries. which allows you to connect to the repository through the Designer. Each member of the group to which the owner belongs. Write permission. run queries. For example. For example. you must have both read and execute permission to start a workflow in a folder.

A repository user name for an individual. 2. you do not have read permission for the folder. 5. Versioning Object Security Levels Level User Group User Includes Repository group of user names. For information on the privileges and permissions to edit folder properties. change the query type to public. Choose Folder-Edit. select a new owner from the Owner menu. If necessary. select a group from the Group menu. Click OK to save your changes. Edit the folder permissions as necessary. The object owner is the user who creates the object. Permissions 149 . 3. 7. When you assign privileges to versioning objects you can assign them on two levels. When you add users or groups. To enable others to use it. 6. The permissions list contains users or groups and their permissions for the object. If the owner belongs to more than one group. Each versioning object has a permissions list. Configuring Versioning Object Permissions To configure and manage permissions to versioning objects you must have the Super User privilege or be the owner of the versioning object. use the following rules and guidelines: ♦ ♦ ♦ ♦ The object owner receives all permissions by default. Select the folder in the Navigator. When you configure versioning object permissions. connect to a repository. 4. You cannot assign permissions to a private query. Table 5-4 lists versioning object security levels: Table 5-4. you can assign them permissions. Users with Super User privilege receive all permissions by default. Every user in a group receives the privileges for that group. You also can change the object owner. To edit folder permissions and properties: 1.You can edit folder permissions and properties at any time. If the folder does not appear in the Navigator. World users receive no permissions by default. Users that belong to the Administrators group receive all permissions by default. see “Repository Manager Tasks” on page 516. In the Repository Manager.

Add a new group or user. 150 Chapter 5: Repository Security . Change group.For information on tasks you can perform with user privileges. You cannot change permissions of users with Super User privilege and users belonging to the Administrators group. and versioning object permissions. Click to define permissions. Change owner. see “Repository Privileges” on page 142. folder permissions. select a versioning object in a versioning objects browser and click Permissions. The Permissions dialog box displays. To configure permissions for versioning objects.

The Repository Connections dialog box appears. Viewing User Connections Use the Show User Connections menu command in the Repository Manager to show connection details for users and applications connected to the repository. 3. The time of the last metadata transaction between the repository client application and the repository. The Repository Manager also allows you to terminate user connections. Repository Connection Properties Property User Connection ID Application Hostname Host Address Login Time Last Active Time Description The user name of the user associated with the connection. Managing User Connections 151 . 2. The TCP/IP address of the machine associated with the connection. Launch the Repository Manager and connect to the repository. Click Close to return to the Repository Manager. Table 5-5 describes the properties in the Repository Connections dialog box: Table 5-5. The time the user connected to the repository. The name of the machine running the application. To view user connection details: 1.Managing User Connections The Repository Manager allows you to view the connection details for users connected to the repository. The repository client application associated with the connection. The identification number assigned to the repository connection. Choose Edit-Show User Connections.

Choose Edit-Show User Connections. Terminate residual connections only. Verify the user is no longer connected to the repository. 3. Launch the Repository Manager and connect to the repository. Warning: Terminating an active connection may cause repository inconsistencies. This can happen in the following situations: ♦ ♦ Network problems occur. Use the Repository Manager to terminate residual user connections and release residual locks in the repository. If you terminate a repository connection to a PowerCenter Server. The repository has a residual connection if the connection remains in the User Connections dialog box when the repository client application or machine is actually shut down. 152 Chapter 5: Repository Security . The PowerCenter Server opens additional connections to the repository for each Load Manager and DTM process. In the Repository Connections dialog box. Click Close to return to the Repository Manager.Handling User Connections Sometimes. To terminate a residual connection: 1. The Repository Server closes the user connection. the Repository Server also terminates all other connections to the same PowerCenter Server. 5. select the connection you want to terminate. 4. the Repository Server does not disconnect the user from the repository. A PowerCenter Client or PowerCenter Server shuts down improperly. A residual repository connection also retains all repository locks associated with the connection. 6. 2. Click End Connection.

privileges. or permissions for a folder.<repositoryname>. the ownership defaults to Administrator owner or the Public group. Adding or removing users from a group.Creating an Audit Trail You can track changes to Repository users. Adding or removing a group. the Repository Agent logs security changes to the pmsecaudit. see “Adding a Repository Configuration” on page 105. Changing the password of another user. The audit trail logs the following operations: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Changing the owner. Changing global object permissions. For more information on configuring the Repository.log file in the Repository Server installation directory. groups. The delete operation causes a log entry. Adding or removing user and group privileges. This change does not create a log entry. and permissions by selecting the SecurityAuditTrail configuration option in the Repository Server Administration Console. Changing permissions of queries. Installing or removing an external security authorization module. but after you delete the owner or owner’s group. The audit trail does not log the following operations: ♦ ♦ ♦ ♦ Creating an Audit Trail 153 . Changing your own password. If you check this option. Deleting the owner or owner’s group for a folder. owner’s group. Adding or removing a user.

allowing you to view the object.Repository Locks The repository uses locks to prevent users from duplicating or overriding work. and one execute lock simultaneously on each repository object. The repository then issues an in-use lock for the object. . and another user can view the session properties at the same time. Execute lock. edit.Viewing an object in a folder for which you have write permission. . . The repository allows multiple users to obtain in-use locks on an object. or resuming a workflow. if you obtain a write-intent lock on a workflow before the PowerCenter Server starts the workflow. This means that you can edit a session while the PowerCenter Server runs the session. Write-intent lock. such as workflows and sessions.Importing an object. The Repository Server creates and releases locks on repository objects. Locks objects you want to run or execute. Repository Locks Repository Lock In-use Created When .Viewing an object that is already write-locked. . The repository allows only one write-intent lock per object. restarting aborting. the repository displays a message box: The [object_type] [object_name] is already locked by [user name].Starting. Maximum per Object Unlimited Write-intent 1 Execute 1 Locking the Same Object The repository permits multiple in-use locks. The repository allows only one execute lock per object. .Exporting an object. Placed on objects you want to view. one write-intent lock.Editing a repository object in a folder for which you have write permission. If you attempt to modify an object that already has a write-intent lock. or execute them in a workflow: ♦ ♦ ♦ In-use lock. This keeps you from starting a workflow that is already running.Viewing an object in a folder for which you do not have write permission. Placed on objects you want to modify. . For example. The Repository Server creates the following types of locks on repository objects when you view. Table 5-6 lists each repository lock and the conditions that create it: Table 5-6. thus preventing repository inconsistencies. This keeps multiple users from editing the object at one time. the PowerCenter Server runs the version of the workflow existing in the 154 Chapter 5: Repository Security . which can cause the PowerCenter Server to load duplicate or inaccurate data.

preventing you from copying or editing the business component. the PowerCenter Server runs the newly-edited workflow. For example. and mappings contain at least one source and target definition. and marks the session and every other session using the mapping invalid. see “Validating Multiple Objects” on page 42. For example.repository when the workflow starts. the repository might mark the other objects invalid. Locking Within Objects Some repository objects contain other repository objects. If you save changes after the workflow starts. the PowerCenter Server obtains an execute lock on the workflow and tasks in the workflow. If you save changes to the repository before the workflow starts. If you try to start the workflow. you receive a in-use lock. the repository notes the mapping has been changed. When you edit a property of a cube or dimension. the PowerCenter Server runs the original workflow and the repository updates your changes after the workflow completes. sessions contain mappings. For example. However. the repository displays a message stating the workflow is already running. When the workflow starts. The change might invalidate any workflow containing the session. workflows contain sessions and tasks. When you save the mapping. For details on validating the workflow. the Repository Server locks all related dimension tables until you save your changes. For information about validating objects. the Repository Server creates a write-intent lock on all related objects until you save your changes or cancel your edit. you might notice an object is locked even when no one is working with it. the Repository Server locks the business component tree while its contents are being edited. you open a mapping used by a session. Any user who tries to edit a related dimension table receives an in-use lock on the table. if you save changes to an object used by other objects. Repository Locks 155 . you must validate them. if you use the Dimension Editor to change a Level Property field. if that object is a part of a cube or dimension being edited. Therefore. You can view an object (obtain an in-use lock) used by another object without affecting the other object. see “Working with Workflows” in the Workflow Administration Guide. delete a transformation. and save your changes. Locking Business Components To maintain the integrity of your repository data. Locking with Cubes and Dimensions Editing or deleting cubes and dimensions can affect many objects in the repository. If you try to edit the workflow or task when another user has a write-intent lock. Before you can use invalidated objects.

Locking occurs at the root directory of the business component tree. The Repository Server releases a lock when you choose Repository-Save. if Finance is the root directory of your tree. the Repository Server locks the Finance directory while you make changes to the Accounts Receivable or General Ledger subdirectories. For example. see “Handling Locks” on page 157. 156 Chapter 5: Repository Security . You can use the Show Locks feature to see if the business component or objects it points to are locked. For details. with General Ledger and Accounts Receivable as subdirectories.

Handling Locks 157 . In the Repository Manager. The Object Locks dialog box appears. Object Lock Properties Column Name User Connection ID Description User name locking the object. The identification number assigned to the repository connection. Repository locks are associated with user connections. see “Managing User Connections” on page 151. repository. the repository does not release a lock. For more details on user connections. 2. you must identify the connection associated with the lock and close the connection. or database machine shuts down improperly. This is called a residual lock. PowerCenter Server.Handling Locks Sometimes. Use the Show Locks menu command to view all locks in the repository. Table 5-7 describes the object lock information in the Object Locks dialog box: Table 5-7. To view all locks in the repository. This can happen in the following situations: ♦ ♦ Network problems occur. To release a residual lock. connect to a repository. choose Edit-Show Locks. A PowerCenter Client. If an object or folder is locked when one of these events occurs. Viewing Locks You can view existing locks in the repository in the Repository Manager. To show all repository locks: 1. the repository does not release the lock.

View object locks and identify the connection identification number associated with the locks you want to release. Application locking the object: Designer. 2. You can unlock objects and folders by identifying the user connection associated with the lock and terminating the user connection. or source. 3. verify that the object is not being used and verify that the user is not connected to the repository. 158 Chapter 5: Repository Security . Name of the locked object. match the connection identification number from the Object Locks dialog box with the connection identification number in the User Connections dialog box. Type of lock: in-use. Object Lock Properties Column Name Folder Object Type Object Name Lock Type Lock Time Hostname Application 3. To view updated lock information. write-intent. Warning: Before unlocking any object. 5. Open the Repository Manager and connect to the repository. Name of the machine locking the object. note which user owns the lock. click the Refresh button. Time the lock was created. or Repository Manager. click on the column name. For information on the privileges and permissions to terminate other user connections and unlock objects see “Repository Manager Tasks” on page 516. Releasing Locks If a system or network problem causes the repository to retain residual locks. you may need to unlock an object before using it. Type of object: such as folder. Verify the user is not connected to the repository. mapping. In the User Connections dialog box. You do not need special privileges to terminate connections associated with your repository user name. To sort your view of the locks by column. Description Folder in which the locked object is saved. Workflow Manager.Table 5-7. To unlock a folder or repository object: 1. 4. 4. choose Edit-Show User Connections. After you view the object locks. or execute.

Handling Locks 159 . The Repository Server closes the user connection and releases all locks associated with the connection. Click Close to return to the Repository Manager. 7.6. Select the user connection and click End Connection.

Do not use shared accounts. Then create separate user groups for each type. limit the ability of other repository users to perform unnecessary actions. assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. limit privileges. To do this. you can create appropriate user groups.Tips When setting up repository security. and limit folder permissions. the easier it is to maintain. but the simpler the configuration. Once you establish separate groups. answer the following questions: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ After you evaluate the needs of the repository users. 160 Chapter 5: Repository Security . Using shared accounts negates the usefulness of the repository locking feature. To avoid repository inconsistencies: ♦ Do not use shared accounts. across all folders? Before implementing security measures. Create groups with limited privileges. The simplest way to prevent security breaches is to limit the number of users accessing the repository. such as running sessions or administering the repository. determine how many types of users access the repository. the tighter your repository security. Then. Breaking a valid lock can cause repository and inconsistencies. The repository creates locks on objects in use. The more distinct your user groups. keep it simple. Securing the environment involves the following basic principles: ♦ ♦ ♦ Limiting users Restricting privileges Defining permissions Who needs access to the repository? What do they need the ability to do? Where can I limit repository privileges by granting folder permissions instead? Who creates transformations and mappings? Do they need access to all folders? Who schedules workflows? Who needs to start workflows manually? Do they need to access all workflows in the repository? Who administers the repository? Who starts and stops the PowerCenter Server? Who needs the ability to perform all functions within the repository. You have the tools to create a complex web of security.

restrict the number of users who need this all-encompassing privilege. you can add individual privileges to that user. see who owns the lock and make sure the owner is not using the object. To protect your repository and target data. but this user also administers the PowerCenter Server. When working in a multiple repository environment (PowerCenter only). Since this feature is often used to deploy folders into production. Users with either the Browse Repository or Administer Repository privilege can unlock any object or folder locked by their own user name. For details on locking. You can allow users a limited ability to unlock locks by granting them the Browse Repository or Administer Repository privilege. Therefore. This becomes more important when repositories contain folders with the same or similar names. Customize user privileges. The Administer Repository privilege permits a user to copy a folder from one repository to another. Tips 161 . The Super User privilege permits you to perform any task despite folder-level restrictions. you should limit this privilege in production repositories.♦ ♦ Before unlocking an object or folder. The Repository Manager grants the Super User privilege automatically to the Administrators group. see “Repository Locks” on page 154. Restricting the number of crossover users limits the possibility of a user connecting to the wrong repository and editing objects in the wrong folder. limit the number of users and groups accessing more than one repository. If a single user requires more privileges than those assigned to the user's group. This includes starting any workflow. Limit user and group access to multiple repositories. Limit the Administer Repository privilege. Limit the Super User privilege. you must also limit the number of users you assign to the Administrators group. For example. and unlocking other user's locks. Ask all users to exit the repository before unlocking multiple objects or closing user connections. you can add the Administer Server privilege to the individual user. if you have a user working in the Developers group. You can allow users a limited ability to run workflows by granting the Use Workflow Manager privilege with read and execute permission. and you need to keep the user in that group for the purpose of folder permissions.

Instead.Restrict the Workflow Operator privilege. Misuse of the privilege can result in invalid data in your target. the user needs only execute permission for the folder. and read and execute permission for the folders in which the user works. if the user needs to use the Workflow Manager to start workflows. Where possible. 162 Chapter 5: Repository Security . you can assign the user the Use Workflow Manager privilege. If the user uses pmcmd to start workflows. You can also use the pmcmd program to start any workflow in the repository. With the Workflow Operator privilege. you can use the Workflow Manager to start any workflow within the repository for which you have read permission. avoid granting the Workflow Operator privilege.

however. you do not need to view a folder before starting a workflow within the folder. you must also have the default privilege Browse Repository. you need to edit the database user to allow all privileges in the database. My privileges indicate I should be able to edit objects in the repository. Therefore. and granting different sets of privileges. you can start any workflow in the repository if you have the Workflow Operator privilege or execute permission on the folder. Therefore.Troubleshooting The solutions to the following situations might help you with repository security. You must. to remove the privilege from users in a group. I created a new group and removed the Browse Repository privilege from the group. I have the Administer Repository Privilege. or you can inherit Browse Repository from a group. To perform administration tasks in the Repository Manager with the Administer Repository privilege. You may be working in a folder with restrictive permissions. Troubleshooting 163 . Browse Repository is a default privilege granted to all new users and groups. With pmcmd. If the database user (one of the default users created in the Administrators group) does not have full database privileges in the repository database. but I cannot access a repository using the Repository Manager. but I cannot edit any metadata. You can assign Browse Repository directly to a user login. Why does every user in the group still have that privilege? Privileges granted to individual users take precedence over any group restrictions. you must remove the privilege from the group. I find that none of the repository users can perform certain tasks. Check the folder permissions to see if you belong to a group whose privileges are restricted by the folder owner. know the exact name of the workflow and the folder in which it exists. even the Administrator. How does read permission affect the use of the pmcmd program? To use pmcmd. Repository privileges are limited by the database privileges granted to the database user who created the repository. you do not need read permission to start workflows with pmcmd. After creating users and user groups. and every user in the group.

164 Chapter 5: Repository Security .

171 Comparing Folders. 174 165 . 168 Configuring a Folder. 166 Folder Properties.Chapter 6 Working with Folders This chapter contains information on the following topics: ♦ ♦ ♦ ♦ Overview.

You can also copy and replace folders within the repository or across repositories. 166 Chapter 6: Working with Folders . or stored in a shared folder and accessed through a shortcut. schemas. Folders are designed to be flexible. If you work with multiple repositories. When you create a workflow. When you create a session in a folder. tasks. you can copy the entire folder. Keep in mind that any mapping in a folder can use only those objects that are stored in the same folder. you can copy it into your working folder. you can create a folder that allows all repository users to see objects within the folder. dimensions. You can copy objects from one folder to another. to help you logically organize the repository. Each folder has a set of configurable properties that help you define how users access the folder. Use the Copy Wizard to copy individual workflows to other folders. including mappings. but not to edit them. business components. you can also copy objects across repositories. and mappings. you use folders to store workflows. targets. Using Folders in the Designer In the Designer. you can use any object in the folder. and sessions. To copy all workflows within a folder to a different location. Organizing Folders Folders are designed to be flexible. Using Folders in the Workflow Manager In the Workflow Manager. In the Repository Manager. You can copy a session within a folder or to another folder. you can create a folder that allows users to share objects within the folder. and sessions. so if you want to use an object in a nonshared folder.Overview Folders provide a way to organize and store all metadata in the repository. Note: You must create a folder in a repository before you can connect to the repository using the Designer or Workflow Manager. you use folders to store sources. When you create a mapping in a folder. You can create shared and non-shared folders. Or. you can use any mapping in the folder. and you can create shortcuts to objects in shared folders. providing the means to organize the repository in the most logical way. Using Folders in the Repository Manager You create and maintain folders in the Repository Manager. cubes. transformations. For example. you can view the users accessing folders and the objects within each folder. you can include any session or task in the folder. mapplets.

you should understand the security measures associated with folders so you can best protect repository objects.In a repository. and reusable transformations) that you create through the Designer. If users work on separate projects. user. designed to store work for that user only. For example: ♦ You might create a single folder for each type of data. you might create one folder for accounts payable and another for accounts receivable. target definitions. or type of metadata. mappings. Overview 167 . You can create a folder for each repository user. you might create folders for each development project. this technique avoids any problems that might occur if two people attempt to edit the same piece of metadata at the same time. subject area. schemas. For example. if you want to organize accounting data. You might create a different folder for each type of metadata (source definitions. ♦ ♦ Before creating a system of folder organization.

see “Permissions and Privileges by Task” on page 509. you can apply a status to all versioned objects in the folder.Folder Properties Each folder has several configurable properties on the folder property sheet. For list of permissions and privileges combinations allowing you to perform each task. Write permission. Allows you to create or edit objects in the folder. Allows you to execute or schedule a workflow in the folder. write. see “Working with Version Properties” on page 203. while permitting the appropriate users access to the folder. you can control user access to the folder. and execute tasks within a specific folder. You can use these properties to protect metadata saved in the folder. 168 Chapter 6: Working with Folders . For details on how folder permissions interact with repository privileges. Execute permission. write. see “Repository Security” on page 125. Folders have the following permission types: ♦ ♦ ♦ Read permission. Privileges grant access to specific tasks while permissions allow you to read. With folder permissions. Permissions Permissions allow repository users to perform tasks within a folder. and the tasks you permit them to perform. Folder permissions work closely with repository privileges. and execute all tasks across all folders in the repository and can perform any task using the PowerCenter Client tools. For more information on changing the status of all objects in a folder. Note: Any user with the Super User privilege has read. Folders have the following properties: ♦ ♦ ♦ ♦ Folder permissions Folder owner Owner’s group Allow shortcuts If folder is in a repository enabled for version control. Allows you to view the folder as well as objects in the folder.

Then restrict Repository permissions. You want a folder allowing full access to one group while limiting access to the other. Note: All users in the Administrators group or with the Super User privilege have full access to all folders in the repository. If you have an object that you want to use in several mappings or across multiple folders. As long as a group does not have the Super User privilege. All users and groups in the repository. In the Designer. Folder Permissions Permission Level Owner Owner’s Group Repository Includes Owner of the folder. The owner of the folder has an additional ability to edit the folders properties as long as the owner has the Browse Repository privilege and read permission on the folder. Table 6-1 lists the users included in each permission level: Table 6-1. like an Expression transformation that calculates sales Folder Properties 169 . the Owner and Owner’s Group retain the permission. the repository contains users in two user groups. your choices for these settings affect how repository users access objects within the folder. Each permission level includes the members in the level above it. then grant all folder permissions to Owner and Owner’s Group. Any other user must have Administer Repository and read permission.Permission Levels You can grant three levels of security on folder permissions. you can select any user in the repository to be the folder owner. If you restrict a permission from the Owner or Owner’s Group. restricting Repository permission limits that group’s folder permissions. you must select one group for the Owner’s Group. that group automatically becomes the Owner’s Group. shared folders allow users to create shortcuts to objects in the folder. If the owner belongs to only one group. you make a user in the fullaccess group the owner of the folder. To do this. If the folder owner belongs to more than one repository group. Folder Owner and Owner's Group Because you grant permissions to Owner and Owner’s Group. or the Super User privilege to edit folder properties. Shared Folders You can designate a folder to be shared. then grant the same permission to Repository. When you create a folder. For example. you can also choose a repository group as the Owner’s Group. If the owner belongs to more than one group. as desired. Each user in the owner’s repository user group.

Then all shortcuts to the Expression transformation inherit the changes. So if. and create a shortcut to a shared folder for the official sales commission Expression transformation. As with local shared folders. 170 Chapter 6: Working with Folders . Shared Folders in Global Repositories Shared folders in global repositories can be used by any folder in the domain. for example. Note: Once you make a folder shared. You can then access the object from other folders by creating a shortcut to the object. you can change the Expression transformation in the shared folder. if you are working in a folder in a local repository.commissions. you can place the object in a shared folder. If you want to use an object in a shared folder without inheriting any future changes. For example. you change the way your company calculates sales commissions. you can copy the existing object. you cannot reverse it. the repository updates all shortcuts in the domain to reflect those changes. you can connect to the global repository. if changes are made to the original object. Shortcuts inherit changes to their shared object.

The owner can have a different level of permissions within the folder. Each status defines the ability of users to check out and edit objects in the folder and whether copy deployment group operations can create new versions of objects in the folder. Specifies a status applied to all objects in the folder. Defines the ability of users and groups to access the folder. The name of the folder in the repository. Folder permissions. To create a folder: 1. You can then view these comments in the Repository Manager. and the ability to administer the folder. connect to the repository. separate from general users. Allows shortcuts. In the Repository Manager. Folder owner. Determines whether the folder is shared. Owner’s group. Folder status. ♦ ♦ You can optionally enter a description of the folder. The group selected can also have a different level of permissions in the folder.Configuring a Folder Each folder in the repository must have the following information configured in the folder properties dialog box: ♦ ♦ ♦ ♦ Folder name. Creating a Folder For information on the privileges and permissions to create a folder. see “Repository Manager Tasks” on page 516. Configuring a Folder 171 .

Only groups to which the owner belongs can be selected. Any user in the repository can be the folder owner. Click OK. For details. If selected. 3. Choose Folder-Create.2. The status applied to all objects in the folder. the folder displays an open hand icon. 172 Chapter 6: Working with Folders . For more information on object status. makes the folder shared. Description of the folder that appears in the Repository Manager. If the folder is shared. Permissions Required 4. Enter the following information: Folder Properties Name Description Owner Owner’s Group Allow Shortcut Status Required/ Optional Required Optional Required Required Optional Required Description Folder name. Owner of the folder. The folder appears in the Navigator. This option applies to versioned repositories only. see “Working with Version Properties” on page 203. see “Permissions” on page 168. Folder permissions for users in the repository. Repository user group to receive Owner’s Group permissions.

you can delete that folder from the repository. 3. Choose Folder-Delete. For information on the privileges and permissions to delete a folder see “Repository Manager Tasks” on page 516. make sure no users are accessing the folder when you edit the folder. 2. connect to a repository and select a folder.Editing a Folder For information on the privileges and permissions to edit a folder see “Repository Manager Tasks” on page 516. In the Repository Manager. Deleting a Folder If a folder becomes obsolete. To delete a folder: 1. click OK. connect to a repository and select a folder. Choose Folder-Edit. When asked if you really want to delete the folder. 3. In the Repository Manager. and click OK. Configuring a Folder 173 . Enter the desired changes. To avoid repository inconsistencies due to changes in folder properties. 2. To edit a folder: 1. Note: The Repository Server updates changes in folder properties immediately.

Direction of comparison. Compared Object Types and Attributes Object Type Sources Targets Reusable transformations Compared Attribute Source name and database name Target name and database name Transformation name and type 174 Chapter 6: Working with Folders . the Repository Manager uses the latest checked in version of an object for comparison. Table 6-2 lists the object types and attributes you can compare: Table 6-2. You must also have privileges to access the repositories containing the folders.Comparing Folders Before you copy or replace a folder in a repository. For more information on Compare Objects. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. Compare objects between two folders in different repositories. The wizard compares objects based on specific object attributes. See Table 6-2 on page 174 for a list of compared attributes for object types. Similarities between objects Differences between objects Outdated objects Each comparison also allows you to specify the following comparison criteria: ♦ ♦ The wizard displays the following information: ♦ ♦ ♦ You can edit and save the result of the comparison. You can specify the object types to compare and display between folders. You can specify either one-way or two-way comparisons. Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. The wizard performs directional comparisons. A directional comparison checks the contents of one folder against the contents of the other. The Compare Folders Wizard allows you to perform the following comparisons: ♦ ♦ Compare objects between two folders in the same repository. you might want to verify the contents of a folder or compare it with other folders. If you use a versioned repository. You must have read permission for each folder you want to compare. You can also compare two objects of the same type using Compare Objects. see “Comparing Objects” in the Designer Guide. Object types to compare.

Compared Objects in Compare Selected Object Source field Target field Reusable transformation field Mapping variable External procedure initialization properties Session component Compared Object Source Target Reusable transformation Mapping Transformation instance Session Comparing Folders 175 . Table 6-3 lists objects the wizard compares by default when you select certain objects to compare: Table 6-3.Table 6-2. regardless of whether you select the other objects to compare. Compared Object Types and Attributes Object Type Mappings Mapplets Source fields Target fields Reusable transformation fields Sessions Session components Tasks Task instances Workflows Workflow events Workflow variables Worklets Shortcuts Transformation instances Mapping variables External procedure initialization properties Schedulers Configurations Compared Attribute Mapping name Mapplet name Column names Column names Port names Session name Component value Task name Task instance name Workflow name Workflow event name Workflow variable name Worklet name Shortcut name and object type Transformation instance name and type Mapping variable name Property name Scheduler name Configuration name Some objects you choose to compare also cause the wizard to compare other objects.

present in ADS2 176 Chapter 6: Working with Folders . A two-way comparison can sometimes reveal information a one-way comparison cannot. if two folders have matching source names and column or port names but differing port or column attributes. A one-way comparison does not note a difference if an object is present in the target folder but not in the source folder. You can choose to compare based on the following criteria: ♦ ♦ ♦ Different objects. Object name and type exist in one folder but not the other. One-Way and Two-Way Comparisons Comparison results depend on the direction of the comparison. such as precision or datatype. Object modification date is older than objects with the same name. Object name. the source definition ORDER_ITEMS. and modification date are the same in both folders. The wizard does not compare the field attributes of the objects in the folders when performing the comparison. Similar objects. the wizard does not note these as different. For example. Two-way comparisons check objects in Folder1 against those in Folder2 and also check objects in Folder2 against those in Folder1. Compared Objects in Compare Selected Object Task Instance Workflow event Workflow variable Compared Object Workflow and worklet Workflow and worklet Workflow and worklet The wizard compares the attribute of each object in the source folder with the attribute of each object in the target folder. If you compare the folders using a one-way comparison.Table 6-3. ADS1 and ADS2. One-way comparisons check the selected objects of Folder1 against the objects in Folder2. Outdated objects. Figure 6-1 shows two folders in the same repository. type.

By default the results file is saved in the My Documents directory.rtf file. and outdated objects in blue text.txt file. If you compare the folders using a two-way comparison. 2. To retain the color and font attributes of the result. In the Repository Manager. Comparing Folders 177 . is not noted as a comparison. A two-way comparison notes the absence of ORDER_ITEMS in ADS1 as a difference. To compare folders: 1. verify that you have Read permission for each folder you want to compare. even if you do not choose to display differences or similarities in the edit field. Steps for Comparing Folders Before comparing folders. The Compare Folders Wizard always displays the total number of differences. choose Folder-Compare.but not in ADS1. similarities. You can save the results of the comparison in the edit field to an . One-Way and Two-Way Comparisons A one-way comparison does not note the presence of ORDER_ITEMS in ADS2 as a difference. unmatched objects denoting a difference in red text. Figure 6-1. The Compare Folders wizard displays similar objects in green text. and outdated objects found during the comparison.rtf or a . the absence of ORDER_ITEMS in ADS1 is noted as a difference. Editing and Saving Results Files You can edit and save the result of a folder comparison. Connect to the repositories containing the folders in the wizard. Click Next. save it as an .

4. Connect to repository. 5. Select the object types you want to compare. Connect to the repositories containing the folders you want to compare and select folders for comparison. Click Next.3. 178 Chapter 6: Working with Folders . 6. Click Next.

13. If you chose to save the results to a file. Comparing Folders 179 . Save the compare results to a file. and outdated objects. Click Next. If you want to save the comparison results to a file. 10. 9. Click Finish. 12. specify the file type. Select display options. Click Save. View the results of the comparison. 11. select Save results to file. and directory. name. The wizard always displays the number of differences.7. 8. similarities.

180 Chapter 6: Working with Folders .

194 Tips. 183 Understanding Shortcut Properties. 197 Troubleshooting. 190 Working with Shortcuts. 182 Shortcuts Versus Copies. 187 Creating a Global Shortcut.Chapter 7 Local and Global Shortcuts This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 198 181 . 184 Creating a Local Shortcut.

Overview Shortcuts allow you to use metadata across folders without making copies. A shortcut created in the same repository as the original object. You can create shortcuts to objects in shared folders. Shortcuts allow you to reuse an object without creating multiple objects in the repository. If you try to create a shortcut to a nonshared folder. You can create the following types of shortcuts: ♦ ♦ 182 Chapter 7: Local and Global Shortcuts . Instead of creating 10 copies of the same source definition. Global shortcut. you use a source definition in 10 mappings in 10 different folders. You can create shortcuts to the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ Source definitions Reusable transformations Mapplets Mappings Target definitions Business components Local shortcut. you can configure the shortcut name and description. For example. When the object the shortcut references changes. the shortcut inherits the additional column. you ensure each use of the shortcut matches the original object. For example. Note: In a versioned repository. and you add a column to the definition. you can create 10 shortcuts to the original source definition. By using a shortcut instead of a copy. one in each folder. the Designer creates a copy of the object instead. the shortcut inherits those changes. A shortcut created in a local repository that references an object in a global repository. a shortcut always inherits the properties of the latest version of the object that it references. ensuring uniform metadata. A shortcut inherits all properties of the object to which it points. if you have a shortcut to a target definition. Once you create a shortcut.

Shortcuts have the following advantages over copied repository objects: ♦ ♦ You can maintain a common repository object in a single location. you need to edit each copy of the object. If you need to edit the object. mapplets. You can develop complex mappings. However. create a copy. and all sessions using those mappings. if you use a shortcut to a reusable transformation. In contrast. to obtain the same results. or recopy the object. you can edit the original repository object. instead of creating copies of the object in multiple folders or multiple repositories. see “Exporting and Importing Objects” on page 263. all shortcuts immediately inherit the changes you make. Therefore. For example. If you need to change all instances of an object. ♦ ♦ For details on exporting and importing objects to makes copies. if you have multiple copies of an object. then reuse them easily in other folders. Otherwise. if you want the object to inherit changes immediately. some changes can invalidate mappings and sessions. Shortcuts Versus Copies 183 . or reusable transformations. then change a port datatype. You can save space in your repository by keeping a single repository object and using shortcuts to that object. create a shortcut. you can invalidate all mappings with shortcuts to the transformation. All shortcuts accessing the object inherit the changes.Shortcuts Versus Copies One of the primary advantages of using a shortcut is maintenance. You can restrict repository users to a set of predefined metadata by asking users to incorporate the shortcuts into their work instead of developing repository objects independently.

you can add object descriptions for each shortcut. Afterwards. The shortcut inherits the following properties that cannot be edited in the shortcut object: ♦ ♦ ♦ Object business name and owner name Port attributes. 184 Chapter 7: Local and Global Shortcuts . You can edit the default shortcut name at any time. the Designer names the shortcut Shortcut_To_ObjectName. When you enable this option. including datatype. if the description of the referenced object subsequently changes. Note: If the business name contains characters that are not allowed as in the object name. scale. precision. the Designer displays all objects in the Navigator by name. Default Shortcut Name The Designer names a shortcut after the object it references based on the object name as it appears in the Navigator when you create the shortcut: Shortcut_To_DisplayedName. default value. shortcuts do not inherit those changes. By default. Since the description is unique to the shortcut. However. you can enable the Designer tools option to display sources and targets by business name.Understanding Shortcut Properties When you create a shortcut to a repository object. the Designer names the shortcut Shortcut_To_BusinessName. the Designer displays sources and targets by business names if they exist. and port description Object properties (such as tracing level) The shortcut also inherits a name and description which you can edit in the shortcut. the shortcut inherits the attributes of the object. Describing the Object and the Shortcut Shortcuts inherit the description associated with the referenced object when you first create the shortcut. the Designer replaces the character with an underscore (_). If you create a shortcut to a source or target when this option is enabled. If you create a shortcut with this default.

However. Figure 7-1 shows the shortcut with a description inherited from the original transformation.For example. Object and Shortcut Description Description from the original object Description added to the shortcut Shortcuts do not inherit edits to the description of the referenced object. as well as comments for the shortcut: Figure 7-1. The shortcut object displays the following details about the referenced object: ♦ ♦ ♦ Repository name Folder name Table or transformation name Understanding Shortcut Properties 185 . Locating the Referenced Object Each shortcut tracks the location of the object it references and displays it in the transformation property sheet. any shortcuts created after the change then contain the latest description.

Referenced Shortcut Object Original Object Location Note: If you move or delete an object referenced by a shortcut. 186 Chapter 7: Local and Global Shortcuts .Figure 7-2 shows the transformation property sheet with the referenced shortcut objects: Figure 7-2. the shortcut becomes invalid.

Once you create a local shortcut. When you drag it into the workspace. You can create a local shortcut in any folder in the repository. the shortcut icon indicates the transformation is a shortcut. Figure 7-3 shows shortcut icons in the Navigator and Workspace windows: Figure 7-3. named Shortcut_To_DetectChanges appears in the Transformations node of the folder. Shortcut_To_ObjectName. the shortcut. you can make a copy of the object. you can reuse it within the same folder. After you create a shortcut. If an object is in a nonshared folder. For example. when you create a shortcut to the DetectChanges reusable Expression transformation. You can create a local shortcut to objects in a shared folder in the same repository. Transformation Shortcut Icon Shared Folder Original Object Shortcut Icon Shortcut Creating a Local Shortcut 187 . the same shortcut icon appears. it appears in the Navigator as an available repository object with the shortcut icon.Creating a Local Shortcut You can reuse metadata within a single repository by creating a local shortcut. When you drag the resulting shortcut into the workspace. The Designer names shortcuts after the original object by default.

see “Managing Business Components” in the Designer Guide. save the object. 188 Chapter 7: Local and Global Shortcuts . To create a shortcut. expand the shared folder containing the object you want to use and drill down to locate the object. the Designer displays the following message: Create a shortcut to <object type> <object name>? Note: If the object is not saved in the repository. expand the shared folder containing the object you want to use and drill down to locate the object. Drag the object from the shared folder to the destination folder. Select the appropriate Designer tool for the shortcut. cancel the operation. The shortcut now appears in the Navigator. Open the destination folder. To create a local shortcut in the Navigator: 1. choose the Warehouse Designer or Mapping Designer tool. To create a shortcut for a target. the Designer creates a shortcut if the object does not already exist in the destination folder. click OK to create a shortcut. or click Cancel to cancel the operation. to create a shortcut for a source. then create the shortcut. You can now use the shortcut in this folder. the folder in which you want the shortcut. you must have one of the following sets of privileges and permissions for the shared folder containing the original object: ♦ ♦ Use Designer privilege with read permission on the folder Super User privilege You must also have the one of the following sets of privileges and permissions on the destination folder: ♦ ♦ Use Designer privilege with read and write permission on the folder Super User privilege You can create a local shortcut in the Navigator or in the workspace. In the Navigator.Note: When you drag an object from a shared folder to a business component directory. 3. Choose Repository-Save. 4. To create a local shortcut. In the Navigator. 3. 2. the Designer displays a message asking if you want to create a copy of the object. After you drop the object. To create a local shortcut in the workspace: 1. the folder in which you want the shortcut. When prompted for confirmation. 2. For details. Open the destination folder. choose the Source Analyzer or Mapping Designer tool. For example. 5.

4.

Drag the object from the shared folder into the workspace. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
5.

When prompted for confirmation, click OK to create a shortcut, or click Cancel to cancel the operation. The shortcut now appears in the workspace and in the Navigator.

6.

Choose Repository-Save.

You can now use the shortcut in this folder. For details on working with shortcuts, see “Working with Shortcuts” on page 194.

Creating a Local Shortcut

189

Creating a Global Shortcut
You can reuse metadata between repositories by creating a global shortcut. A global shortcut is a shortcut in a local repository that references an object in a global repository. The local and global repository must be in the same domain. You can create a global shortcut in any folder in the local repository. Once you create the global shortcut in a folder, you can reuse it in the folder as you would any other repository object. You can create a global shortcut to any object in a shared folder in a global repository. If a folder is not shared, you can make a copy of these objects if the global and local repository have compatible code pages. For details on code page compatibility, see “Globalization Overview” in the Installation and Configuration Guide. To create a global shortcut, you must be able to connect to the global repository through the local repository. That is, if you connect to the local repository directly, the global repository must appear in the local repository. Similarly, if you connect to the global repository directly, the local repository must appear in the global repository. For example, Figure 7-4 shows the DEVELOPMENT repository as a local repository with the PRODUCTION global repository:
Figure 7-4. Create a Global Shortcut

To create a global shortcut: - Connect to the global repository through the local repository. OR - Connect to the local repository through the global repository.

You can use the Designer to connect to both the local and the global repositories individually. However, to create a global shortcut, you must connect to one repository through the other. You can connect to the PRODUCTION global repository first, then the DEVELOPMENT repository directly below PRODUCTION to create a global shortcut. You can also connect to the DEVELOPMENT repository then connect to the PRODUCTION repository appearing below it.

190

Chapter 7: Local and Global Shortcuts

To create a global shortcut, you must have one of the following sets of privileges and permissions in the global repository:
♦ ♦

Use Designer with read permission on the shared folder Super User privilege

To create a global shortcut, you must also have one of the following sets of privileges and permissions in the local repository:
♦ ♦

Use Designer with read and write permission on the folder Super User privilege

You can create a global shortcut in the Navigator or in the workspace.
To create a global shortcut in the Navigator: 1.

In the Designer, connect to the local repository and open the folder in which you want a shortcut. The global repository appears in the Navigator below the local repository. If it does not, the repository to which you are connected is not registered with the global repository.

2.

In the Navigator, connect to the global repository appearing below the local repository. The Designer expands the global repository, displaying folders for which you have read permission. If the Designer does not allow you to connect to the global repository, you might need to reconfigure aspects of your repository domain. For details, see “Configuring the Global Shortcut Environment” on page 192.

3. 4.

In the global repository, drill down through the shared folder until you locate the object you want to use. Drag the object into the destination folder in the local repository. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
5.

When prompted for confirmation, click OK to create a global shortcut, or click Cancel to cancel the operation. The shortcut now appears in the Navigator.

6.

Choose Repository-Save.

You can now use the shortcut in this folder.
To create a global shortcut in the workspace: 1.

In the Designer, connect to the local repository and open the folder in which you want a shortcut.
Creating a Global Shortcut 191

The global repository appears in the Navigator below the local repository. If it does not, the repository to which you are connected is not registered with the global repository.
2.

Select the appropriate Designer tool for the shortcut. For example, to create a shortcut for a source, choose the Source Analyzer or Mapping Designer tool. To create a shortcut for a target, choose the Warehouse Designer or Mapping Designer tool.

3.

In the Navigator, connect to the global repository appearing below the local repository. The Designer expands the global repository, displaying folders for which you have read permission. If the Designer does not allow you to connect to the global repository, you might need to reconfigure aspects of your repository domain. For details, see “Configuring the Global Shortcut Environment” on page 192.

4. 5.

In the global repository, drill down through the shared folder until you locate the object you want to use. Drag the object from the shared folder into the workspace. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
6.

When prompted for confirmation, click OK to create a global shortcut, or click Cancel to cancel the operation. The shortcut now appears in the workspace and in the Navigator.

7.

Choose Repository-Save.

You can now use the shortcut in this folder. For details on working with shortcuts, see “Working with Shortcuts” on page 194.

Configuring the Global Shortcut Environment
To create a global shortcut, configure the following:
♦ ♦ ♦

Repository code pages Repository user names and passwords for individual users Repository user name and password for the PowerCenter Server

Repository Code Pages
Before you can create a global shortcut in a repository, the repository must be registered with a global repository. To register a local repository with a global repository, the local repository code page must be a superset of the global repository code page. The Repository Manager
192 Chapter 7: Local and Global Shortcuts

validates code page compatibility when you register a repository. Once you register a local repository, you can create global shortcuts to the global repository. For details on code page compatibility between repositories, see “PowerCenter Domains” on page 13. For details on code page compatibility, see “Code Pages” in the Installation and Configuration Guide.

Repository User Name and Passwords for Individual Users
To create a global shortcut, you need to connect to the global repository through the local repository, or connect to the local repository through the global repository. To do this, you need to log into the first repository using a repository user name and password that is valid in the second repository. The second connection does not ask for a different user name/password combination. For example, you connect to the ERP repository using the user name/password, dev1/mouse. To create a global shortcut, you need to connect to the Development global repository that appears below the ERP repository. When you try to connect, the Designer verifies your user name/password exists in the Development global repository and checks your permissions and privileges. If your user name/password exists, and if you have the Use Designer repository privilege, the Designer opens the connection to the global repository.

Repository User Name and Password for the PowerCenter Server
To run a workflow with a session that uses a global shortcut, the PowerCenter Server must access both the repository in which the mapping is saved, and the global repository for the shortcut information. You enable this behavior by entering a repository user name and password in the server configuration parameter. This user name and password must exist in both of the following:
♦ ♦

The local repository with which the server is registered The global repository in the domain

To access the necessary information, this user name must have one of the following repository privileges in each repository:
♦ ♦ ♦

Use Workflow Manager with folder read and execute permissions Workflow Operator with folder read permission Super User privilege

Creating a Global Shortcut

193

Working with Shortcuts
Once you create a shortcut, you can reuse it in the folder as often as necessary. When you edit an object referenced by a shortcut, the Designer does not automatically validate mappings using shortcuts to the object. Some changes might invalidate mappings, such as deleting a port or changing the port datatype, precision, or scale. When a mapping is invalid, the PowerCenter Server cannot run the session. When editing a referenced object, use the View Dependencies features in the Repository Manager to determine which mappings contain shortcuts to the object. To ensure mappings are valid, open and validate the mapping. When validating a mapping, make sure you have the most recent version of the mapping. For details on viewing dependencies in the Repository Manager, see “Viewing Object Dependencies” on page 37. You can also view object dependencies in the Designer. For details on viewing dependencies in the Designer, see “Using the Designer” in the Designer Guide.

Refreshing Shortcut Properties
When working with shortcuts, it is critical to ensure you have the most recent version of the local or global shortcut in your workspace. If you launch the Designer, then drag a shortcut, or a mapping or mapplet using a shortcut, into the workspace, you view the current version of the object the shortcut references. However, if another user then edits and saves changes to the referenced object, the shortcut displayed in your workspace is no longer an accurate description of the referenced object. Therefore, when working in this type of environment, be sure to update your view of local and global shortcuts. The PowerCenter Server always uses the latest version of a referenced object. When the PowerCenter Server starts a session containing a shortcut, it accesses the repository to retrieve the mapping. If the mapping contains a shortcut, the PowerCenter Server accesses the repository for details about the original object.

Updating Views of Global and Local Shortcuts
The Designer updates properties for a global or local shortcut when it retrieves object information from the repository. If you think the original object referenced by a global or local shortcut has changed, you can refresh your view of the shortcut by performing one of the following:

Open metadata. When you drag an object into the Designer workspace, the Designer retrieves the object from the repository. If the object is a shortcut or contains a shortcut, the Designer retrieves and displays the most recent version of the shortcut. For example, if you open a folder to view a shortcut to a source or a mapping using that shortcut, the Designer displays the most recent version of the source.

194

Chapter 7: Local and Global Shortcuts

Note: When possible, the Designer uses information in memory. If the mapping was open

on your client machine, the Designer might display the version in memory rather than accessing the repository for the latest version. To ensure you have the most recent version, perform one of the following in addition to opening metadata.

Revert to saved. When you use the Designer menu command, Edit-Revert To Saved, the Designer accesses the repository to retrieve the last-saved version of the object. If you select a shortcut or a mapping using a shortcut, then choose Edit-Revert To Saved, the Designer displays the last-saved version of the object in the workspace. Close the folder or close all tools. To ensure you have correct shortcut information, you can clear the Designer memory by closing the folder or closing all tools (Repository-Close All Tools) then reopening the folder or tool.

For example, a mapping includes a shortcut named Shortcut_To_FIL_InsertChanged. This shortcut points to a reusable transformation named FIL_InsertChanged. Another user edits the filter condition in the original transformation, FIL_InsertChanged, and saves changes to the repository. When you open the mapping in the Designer, it retrieves the mapping from the repository. It also retrieves information for Shortcut_To_FIL_InsertChanged (and any other shortcuts used in the mapping). To validate the mapping, choose Mappings-Validate. However, if the mapping is already in memory, the Designer uses the version in memory. To ensure you have the correct version, choose Edit-Revert to Saved. Designer displays the mapping with the latest shortcut properties. To validate the mapping, choose MappingsValidate.

Copying a Shortcut
You can copy a shortcut to other folders. When the Designer copies a shortcut, it creates another shortcut in the new folder. The new shortcut points to the original object used by the original shortcut. The Designer cannot copy a shortcut (resulting in another shortcut), when it cannot find the object the shortcut references. This might occur if, for example, you copy a local shortcut from one repository to an unrelated repository. When the Designer cannot successfully copy a shortcut, it creates a copy of the shortcut object. The copy of the shortcut object is identical to the original object the shortcut references. Unlike an actual shortcut, the copy will not inherit any changes to the original object. You can use the copy of the shortcut as you would the original object. However, if the object is a source definition, you might need to rename the source definition.

Working with Shortcuts

195

Table 7-1 lists the results of copying global and local shortcuts to different repositories:
Table 7-1. Copying Global or Local Shortcuts Shortcut Type Local shortcut Local shortcut Local shortcut Global shortcut Global shortcut Local shortcut Local shortcut Shortcut Location Standalone repository Local repository Local repository Local repository Local repository Global repository Global repository Copied to Another folder, same repository Another folder, same repository Different local repository, same domain* Different local repository, same domain* Different repository, different domain* Local repository, same domain Different repository, different domain* Designer Creates Local shortcut to original object Local shortcut to original object Copy of the shortcut object Global shortcut to original object Copy of the shortcut object Global shortcut to original object Copy of the shortcut object

* To avoid losing metadata during the copy, the code pages of both repositories must be compatible.

For example, if you copy a shortcut named Shortcut_to_Employees from one standalone repository to another, the Designer creates a new source definition in the destination folder named Shortcut_to_Employees. This source definition is a copy of the original shortcut, but is not a shortcut. When you use the source definition in a mapping, the default SQL used to extract data from the source defines the source as Shortcut_to_Employees. If the source table is named Employees in the source database, you must rename the source definition (Employees) or enter a SQL override for the source qualifier connected to the source definition (renaming the source table Employees) for the PowerCenter Server to extract source data. For example, the fourth row of the table indicates when you copy a global shortcut (a shortcut to an object in a global repository) from one local repository to another local repository in the same domain, the Designer creates a global shortcut to the object in the global repository.

Renaming Source Qualifiers to Shortcut Sources
By default, shortcuts are named after their original object, Shortcut_To_ObjectName. If you create a shortcut to a source, and you have enabled the Mapping Designer option to automatically create source qualifiers, the Mapping Designer creates a source qualifier based on the source name. Therefore, if you do not change the name of the source shortcut, the resulting source qualifier is named SQ/ESQ/NRM_Shortcut_To_SourceName. Despite the name, however, the source qualifier is not a shortcut.
Tip: If names of source qualifiers automatically created for shortcut sources cause confusion,

you might want to rename those source qualifiers.
196 Chapter 7: Local and Global Shortcuts

Tips
The following suggestions can extend the capabilities of shortcuts. Keep shared objects in centralized folders. This keeps maintenance simple. This also simplifies the process of copying folders into a production repository. Only create shortcuts to finalized objects. Changes to an object referenced by shortcuts can invalidate the mappings or mapplets using the shortcut, as well as any sessions using these objects. To avoid invalidating repository objects, only create shortcuts objects in their finalized version. After editing a referenced object, make sure affected mappings are still valid. If you need to edit an object referenced by a shortcut, use the Analyze Dependencies feature in the Repository Manager to view affected mappings. After editing the object, see if your changes invalidate the listed mappings. To ensure a mapping is valid, open and validate it in the Designer. Refresh views of shortcuts when working in a multiuser environment. To refresh a shortcut in the workspace, choose Edit-Revert To Saved. You can also use Repository-Close All Tools in the destination folder then reopen the workspace.

Tips

197

Troubleshooting
The solutions to the following situations might help you with local and global shortcuts. The following message appears in the Designer status bar when I try to create a shortcut: “The selected folder is not open.” You are trying to create a shortcut from a shared folder to a folder that is not open. Open the destination folder (by opening at least one tool in the folder or by choosing Folder-Open) before creating the shortcut. When I try to create a shortcut, the Designer creates a copy instead. This can occur when one of the following is true:

The object is not saved in the repository. You can only create shortcuts to objects that are already in the repository. Save the object to the repository, then try creating the shortcut again. You are trying to create a shortcut for an object in a non-shared folder. You can only create shortcuts to objects in shared folders. You are holding down the Ctrl key when dragging the object. To create a shortcut, drag the object without holding down any additional keys. You are trying to create a shortcut between two local repositories, or between two repositories that are not in the same domain. You can only create a shortcut between repositories in the same domain. In addition, you can only create a shortcut in a local repository, referencing an object in a global repository. You cannot create a shortcut in a global repository that references an object in the local repository. You are dragging an object from a shared folder in the global repository to a folder in the local repository, but you are connecting to the repositories separately. To create a global shortcut, you must connect to one repository, then connect to the second repository through the first repository.

♦ ♦ ♦

I cannot connect to my global repository through my local repository to create a global shortcut (but I can connect to both separately). This can occur if you do not have the same user name and password in both repositories.

198

Chapter 7: Local and Global Shortcuts

Chapter 8

Working with Versioned Objects
This chapter includes the following topics:
♦ ♦ ♦ ♦ ♦

Overview, 200 Working with Version Properties, 203 Tracking Changes to Versioned Objects, 208 Checking Out and Checking In Objects, 211 Deleting and Purging Versioned Objects, 215

199

you can purge it from the repository. and prepare them for deployment to a production environment. A versioned repository assigns multiple version numbers to versions of the same object. You can check out an object to reserve it while you edit the object. deleted objects. track changes to those objects. Each time you check in an object. You can perform the following tasks when you work with a versioned object: ♦ ♦ ♦ ♦ 200 Chapter 8: Working with Versioned Objects . the repository saves a new version of the object and allows you to add comments to the version. This allows you to determine changes made to an object over time. If you want to permanently remove an object version. Track changes to an object. and compare any version of the object in the history to any other version. Object versioning allows you to store copies of previous versions of objects in development. Each versioned object has a set of version properties and a status. the repository increments the version number by one and stores a new version of the object in the repository database. you can configure the repository to store multiple versions of objects. A repository enabled for versioning can store multiple versions of the following objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Sources Targets Transformations Mappings Mapplets Sessions Tasks Workflows Worklets Session configurations Schedulers Cubes Dimensions View object version properties. You can also find objects checked out by yourself and other users. Delete or purge the object version. You can recover. or you can upgrade an existing repository to support versioned objects.Overview If you have the team-based development license. You can configure a repository for versioning when you create it. You can delete an object from view and continue to store it in the repository. You can also configure the status of a folder to freeze all objects it contains or make them active for editing. or undelete. You can view a history that includes all versions of a given object. When you check in an object. Check the object version in and out.

When you finish editing the mapping. it disappears from view in the Navigator window. the repository creates a new version of the object and assigns it a version number. Overview 201 . For more information on working with labels. see “Grouping Versioned Objects” on page 217. you check it in to the repository. you check it in to commit changes to a new version. including source definition. Other users are unable to edit the objects you have checked out. and transformations. the repository locks the object for your use. Creating Successive Versions After creating a session and workflow and testing the initial version of the mapping. you want to exclusively edit objects. and include versioned objects in deployment groups. noting that it is the initial version of the mapping. You can perform these tasks in the Repository Manager.You can also apply labels to versioned objects. Sample Scenario Suppose your environment includes a development repository and a production repository. and Workflow Manager. You purge all versions of the transformation. While you are working with the mapping. retain older versions. and freeze the folder when you are finished with development to prevent further changes to the objects it contains. You create and test metadata in the development repository. target definition. but the repository retains all versions of the transformation in the repository database. When the mapping is ready to test. Each time you check in the mapping. queries. When you check in the mapping. and deployment groups. Creating the Initial Version You use the Designer to create a mapping. The first time you check in the object. and then copy it to the production repository. the repository creates a new version and increments the version number by one. Designer. You also include comments with the checked in version. permanently removing them from the repository and freeing up space in the repository database. When you delete the transformation. run queries to search for objects in the repository. you edit the mapping based on the results of your tests. While working in the development repository. Deleting and Purging an Object You want to remove a transformation instance from the mapping. You do not need to use this transformation any more. the repository assigns it version number one.

For more information about viewing checked out objects. Results View Windows List 202 Chapter 8: Working with Versioned Objects . Freezing the folder prevents other users from checking out objects. see “Viewing Object Dependencies” on page 37. a query locates the object in the repository and includes it in a dynamic deployment group. see “Working with Deployment Groups” on page 236. For more information about viewing object histories. see “Tracking Changes to Versioned Objects” on page 208. ♦ ♦ ♦ To switch between open results view windows. For more information about viewing object dependencies.Freezing a Folder After you finish developing and testing your metadata. Object histories allow you to see the changes made to the object. For more information about viewing object queries. Checked out objects. For more information about creating deployment groups. You choose to freeze the folder and allow deployment of objects in the folder. you decide to freeze the folder. View object dependencies to see the impact of changing or deleting an object. Later. Viewing Results View Windows You can query the repository for information about versioned objects. You can view results for the following types of versioned objects: ♦ Object dependencies. An object query allows you to search for versioned objects in the repository that meet conditions you specify. Object queries. see “Working with Object Queries” on page 224. You can view objects you and other users have checked out. Figure 8-1 shows the Results View Windows List: Figure 8-1. Object histories. see “Checking Out and Checking In Objects” on page 211. choose Window-Results View List. The deployment group specifies objects in the development repository you want to put into production.

the Properties dialog box only displays the Object Status tab. you can purge older versions you no longer need from the Repository Manager. and the status of the object in the Properties dialog box. Each time you check in an object. Workflow Manager. For more information on purging objects. or Repository Manager to view the version properties of an object. select the object in the Navigator and choose View-Properties. You can view the version properties. Object properties are associated with the object when you create it. To access the object properties. Or.Working with Version Properties When you enable version control in a repository. The repository assigns each copy. You can also view the current object version number and whether the object is checked out. the Navigator and workspace always display the latest version of an object. the Properties dialog box for a versioned object has the following tabs: Object. and Object Status. In a non-versioned repository. You can view the version history of an object or create a query to search for previous versions of an object. labels applied to the version. By default. the repository creates a new version and increments the version number by one. see “Purging a Version” on page 216. Labels. different versions of the same object may have different names. Working with Version Properties 203 . of the object a version number. Object Properties The Object tab of the Properties dialog box shows the object properties. Every version of an object takes up approximately the same amount of space in the repository database. right-click the object in the Main window or Navigator and choose Properties. If you rename an object during development. you allow the repository to store multiple copies of the same object as you make changes and save it. To conserve space. Viewing Version Properties You can use the Designer. or version. Version. In a versioned repository.

Object Properties Version Properties On the Version tab.Figure 8-2 shows the Object tab in the Properties dialog box: Figure 8-2. and any comments associated with the version. This includes the version number. Version Properties 204 Chapter 8: Working with Versioned Objects . you can view properties that are specific to the latest version of the object. the user and host that created the version. Figure 8-3 shows the Version tab in the Properties dialog box: Figure 8-3.

Labels Properties For more information on creating and applying labels. you can view the current status of the object.Labels Properties On the Labels tab. and comments associated with the label. For each label. you can also view the name of the user who applied the label. Object Status Properties On the Object Status tab. you can view all labels applied to the object. the time the label was applied. Working with Version Properties 205 . You can also change the object status on this tab from the Repository Manager. Figure 8-4 shows the Labels tab of the Properties dialog box: Figure 8-4. see “Working with Labels” on page 219.

deployment group contents. Each version of an object maintains its own status. 206 Chapter 8: Working with Versioned Objects . Changing Object Status You can change the status of individual repository objects from the Repository Manager. You can manually change the status of an object from the Repository Manager. object dependencies. see “Deleting and Purging Versioned Objects” on page 215. the repository removes the object from view. The object is marked as deleted and is not visible in the Navigator. Object Status Properties The object status defines what actions you and other users can perform on the object. perform the following steps. If you change the status of an object from Active to Deleted. or checkouts. For more information on deleting objects and recovering deleted objects. No other objects can use or reference the deleted object. You must check in the object for other users to view changes to the object status. This is true even if you delete the object. An object can have one of the following statuses: ♦ ♦ Active. You and other users can edit the object. query results.Figure 8-5 shows the Object Status tab of the Properties dialog box: Figure 8-5. You can recover a deleted object by changing its status from Deleted to Active. You can find a deleted object through a query. To change object status. You can change the status of an object when you view object history. Deleted.

Frozen. In the Properties dialog box. In the development repository. Working with Version Properties 207 . To change the folder status. The View History window appears. In the Repository Manager.To change the status of an object: 1. 6. You can configure a folder with one of the following statuses: ♦ ♦ ♦ Active. Deployment into the folder creates new versions of the objects. choose a status for the object. The Frozen Do Not Allow Deploy to Replace status prevents other users and copy deployment group operations from creating new versions of the objects. 4. and choose Tools-View Properties. Do Not Allow Deploy to Replace. Suppose the environment contains a developing repository for creating and testing metadata and a production repository for running the workflows and sessions. you might want to verify that other users do not have objects in the folder checked out. Check in the object for other users to view changes to the status. For more information. Allow Deploy to Replace. This status does not allow users to check out objects in the folder. edit the folder in the Repository Manager. This status does not allow users to check out objects in the folder. 5. You can also change the status of folders in the repository. 2. but allows a copy deployment group operation to create new versions of objects. Changing Folder Status Changing the folder status allows you to control what operations you can perform on all versioned objects that the folder contains. This prevents other users from checking out objects in the folder and creating new versions. you might change the status of a folder from Active to Frozen Do Not Allow Deploy to Replace in a code freeze scenario. Select the latest version of the object. 3. The Frozen Allow Deploy to Replace status prevents other users from checking out objects in the folder. choose the Object Status tab. This status allows users to check out versioned objects in the folder. Click OK. You cannot deploy objects into this folder. you might change the status of a folder from Active to Frozen Allow Deploy to Replace to ensure that copy deployment group operations successfully complete. From the Object Status list. Note: Before you change the status of a folder. see “Folder Properties” on page 168. Each of the Frozen statuses allows the Repository Manager to add objects in the folder to a deployment group. In the production repository. The object properties appear. right-click the object in the Navigator and choose Versioning-View History. You might change the status of a folder to serve different purposes depending on the configuration of your environment and your development processes. Frozen.

To accomplish tasks like these. right-click the object in the Main window or the Navigator and choose Versioning-View History. You can also compare two versions of an object displayed in the history. Select the object in the workspace and choose Versioning-View History from the menu. Use the following methods to view the object version history in the Designer or Workflow Manager: ♦ ♦ ♦ Right-click the object in the Navigator and choose Versioning-View History. To view object version history in the Repository Manager. Right-click the object in the workspace and choose Versioning-View History. When you choose View History. the object history retains a record of the version in the object history and specifies the user who purged the version. version number one. As the number of versions of an object grows. The object history allows you to view user changes to an object. It stores multiple versions of an object as you check out. Troubleshoot changes in functionality between different versions of metadata. 208 Chapter 8: Working with Versioned Objects . and comments associated with and labels applied to each version. you may want to view the object version history. the date and time of changes. Repository Manager. the PowerCenter Client allows you to view a history of all of the versions of an object stored in the repository. Viewing Object History The history of an object is a record of all of the versions of an object stored in the repository. You may want to do this for the following reasons: ♦ ♦ Determine what versions are obsolete and no longer necessary to store in the repository. going back to the initial version.Tracking Changes to Versioned Objects A repository enabled for version control maintains an audit trail of version history. You can view the history of a versioned object in the Designer. and check it in. If you or another user purges a version from the repository. modify. and Workflow Manager. the View History window displays the object version history.

Figure 8-6 shows the View History window: Figure 8-6. See “Viewing Object Dependencies” on page 37. View version properties. See “Viewing Version Properties” on page 203. See “Working with Deployment Groups” on page 236. For more information on exporting and importing objects. Save object version history to a file. View History Window Table 8-1 lists additional tasks you can perform from the View History window: Table 8-1. See “Checking Out and Checking In Objects” on page 211. Purge a version. View object dependencies. choose File-Save to File. Add version to deployment group. See “Working with Labels” on page 219. Export the version to an XML file. To save the version history to an HTML file. Undo check out or check in. See “Deleting and Purging Versioned Objects” on page 215. see “Exporting and Importing Objects” on page 263. Export object version to an XML file. Apply or remove a label. Tasks Available in View History Window Task Compare versions. Tracking Changes to Versioned Objects 209 . Description See “Comparing Versions” on page 210.

This allows you to view all of the differences between the objects. When you compare two versions of an object. To compare two versions of an object. The interface for comparing two versions of the same object is the same as the interface for comparing two different objects. the PowerCenter Client displays the attributes of each object.Comparing Versions When you view the version history of an object. you can compare two selected versions of the object. select one version and choose Tools-Compare-Previous Version. 210 Chapter 8: Working with Versioned Objects . For information on comparing objects. see “Comparing Repository Objects” on page 45. Or. select the versions that you want to compare in the object history and choose Tools-Compare-Selected Versions.

the Repository Agent checks in the non-reusable Aggregator transformation implicitly. When you work with composite objects. the Repository Agent treats non-reusable objects as part of the parent object. When you check in the parent mapping.Checking Out and Checking In Objects When you work with versioned objects. You might want to view checkouts to see if an object is available for you to work with. Viewing Checked Out Objects You can view objects you and other users have checked out. For more information on performing check outs. see “Using the Designer” in the Designer Guide or “Using the Workflow Manager” in the Workflow Administration Guide. Checking in an object adds a new version to the object history. the Repository Server releases the write-intent lock on the object and you lose the changes you made to the object. You can check out and check in objects in the Designer and the Workflow Manager. so you cannot check in or out individual non-reusable objects. the repository obtains a write-intent lock on the object for you if no other user has checked it out. if you have a mapping that contains a non-reusable Aggregator transformation. You cannot check out objects from the Repository Manager. and check it in when you want to commit your changes to the repository. choose Versioning-Find Checkouts. This allows you to reserve an object while you work on it. Use the following steps as a guideline when you search for checked out objects: To view checkouts: 1. If you disconnect from the repository without saving a checkout. Workflow Manager. In the Designer. By user. You can choose to narrow or broaden your search for checked out objects in the following ways: ♦ ♦ By folder. you cannot check in the Aggregator transformation individually. or Repository Manager. or if you need to check in all of the objects you have checked out. Checking Out and Checking In Objects 211 . Search for checkouts in the selected folder. For example. or search for objects checked out by all users in the repository. you check out an object each time you want to change it. You must check out the object again when you reconnect. Search for objects checked out by yourself. Checking Out Objects When you open an object in the workspace. No other repository users can edit the object while you have it checked out. or search all folders in the repository. The Repository Agent reverts back to last checked-in version of the object.

see “Viewing Version Properties” on page 203. 212 Chapter 8: Working with Versioned Objects . The View Checkouts window appears. View the object and version properties of the checkout. 2. For more information. and click OK. Specify users. Compare the selected checkout with the previous checked in version.. Table 8-2 lists additional tasks you can perform from the View Checkouts window: Table 8-2. Specify folders. For more information. Select options to narrow or broaden your search. see “Comparing Versions” on page 210. For more information.. The results depend on the options you select for the search. Tasks Available in View Checkouts Window Task Compare versions.The Find Checkouts dialog box appears. View version properties.

Undoing a Checkout You can undo a checkout. the repository creates a new version of the object and assigns it a version number. you cannot check in the Aggregator transformation individually. Checking In Objects When you finish making changes to a checked out object. Undo check out or check in.. View dependencies for the selected checkout. The most recently checked in version of the object becomes the latest version of the object. To undo a check out. View object history. You can undo a checkout from the Query Results window when you search for object dependencies or run an object query. For more information on exporting and importing objects. the Repository Agent treats non-reusable objects as part of the parent object. You can undo a check out when you review the results of the following tasks: ♦ ♦ ♦ View object history. If you want to modify the object again. Check in or undo check out for the selected unmodified checkouts. select the checkout object and choose Tools-Undo Checkout. You can undo a check out from the View History window. View query results. Checking Out and Checking In Objects 213 . Tasks Available in View Checkouts Window Task View object dependencies. When you check in the parent mapping. Export object version to an XML file. You can undo a check out from the View Checkouts window. choose File-Save to File. Save object version history to a file. View the object version history for the selected checkout. see “Exporting and Importing Objects” on page 263. Export the version to an XML file. When you undo a checkout. see “Viewing Object History” on page 208. the Repository Agent checks in the non-reusable Aggregator transformation implicitly. See “Undoing a Checkout” on page 213 and “Checking In Objects” on page 213.Table 8-2. For more information. When you work with composite objects. If you want to check in all objects used in a mapping. For example. View checkouts. The Repository Agent does not check in reusable objects when you check in a composite parent object. For more information. you must check in reusable objects separately. When you check in an object. see “Viewing Object Dependencies” on page 37. To save the version history to an HTML file.. you must check it out. so you cannot check in or out individual non-reusable objects. For more information. you can check it in and commit the changes to the repository. The repository increments the version number each time you check in an object. if you have a mapping that contains a non-reusable Aggregator transformation. such as a mapping. the repository releases the write-intent lock on the object and removes the checkout version from the repository.

You must save an object before you can check it in. or Repository Manager. Workflow Manager. see “Using the Designer” in the Designer Guide or “Using the Workflow Manager” in the Workflow Administration Guide. 214 Chapter 8: Working with Versioned Objects . You can check in objects from the Designer. For more information on performing a check in.

Workflow Manager. 3. If the recovered object has the same name as another object that you created after you deleted the recovered object. You can choose to search for all objects marked as deleted. and removes the object from view in the workspace and the Navigator. For more information on creating and running queries. When you delete a versioned object. This makes the object visible in the Navigator or the workspace. You can recover a deleted object by changing its status to Active. the repository removes the object from view in the Navigator window or in the workspace. such as a mapping. you must rename the object. see “Working with Object Queries” on page 224. For information on changing the status of an object. you must purge the version from the Repository Manager. but does not delete the object or any object version from the repository database. If you purge all versions of an object. You must check in deleted objects for other users to view the changed status. Instead. the repository creates a new version of the object and changes the object status to Deleted. You might want to purge a version if you no longer need to retain the version for development reasons and you want to reduce the size of the repository in the database. the repository changes the object status to Deleted. Deleting a Versioned Object You can delete a versioned object in the Designer. or add conditions to narrow your search. Create and run a query to search for deleted objects in the repository. that contains non-reusable objects. You can use a query to search for deleted objects.Deleting and Purging Versioned Objects When you delete an object in a versioned repository. When you delete a composite object. If you want to permanently remove the object from the repository. 2. you must purge it from the Repository Manager. You must use the Repository Manager to recover a deleted object. If you want to permanently remove a version of an object from the repository. the Repository Server treats the non-reusable object as part of the parent object and deletes it. or Repository Manager. Change the status of the object you want to recover from Deleted to Active. Recovering a Deleted Object You can recover a deleted object by changing the object status to Active. see “Changing Object Status” on page 206. Deleting and Purging Versioned Objects 215 . Use the following process as a guideline when you recover a deleted object: 1. The repository retains the metadata information for all versions of a deleted object. you permanently remove the object from the repository.

If you purge the latest version. the name of the previous version changes to src_Records. the repository maintains a record of the purge in the object history. You can purge a version from the View History window. Choose Tools-Purge Object Version. the repository permanently removes it from the repository database. For example. To purge a version. the prior version takes the name of purged version. If you purge the latest version. but the name of the previous version in the history is src_RecordsWeekly. you must purge all versions. If you purge the latest version. the repository does not maintain or keep a record of the purge. you must purge it from the Repository Manager. include the following condition in your query: Object Status Is Equal To Deleted Purging a Version To permanently remove an object version from the repository. If you purge a version earlier than the latest version. To completely purge an object from the repository. When you purge an object version. The latest version is named src_Records. You can also purge multiple versions of an object from the repository at the same time. select it from the object version history in the Repository Manager. and the prior version has a different name. you have the source src_Records.Tip: To query the repository for deleted objects. 216 Chapter 8: Working with Versioned Objects .

218 Working with Labels.Chapter 9 Grouping Versioned Objects This chapter includes the following topics: ♦ ♦ ♦ ♦ Overview. 224 Working with Deployment Groups. 219 Working with Object Queries. 236 217 .

and you can group objects from the Designer. You use labels to associate groups of versioned objects in a repository. Run queries. you create a dynamic deployment group that runs a query against the source database at deployment time. you create a deployment group to identify objects for deployment to another repository. and deployment groups to identify versioned objects that meet a certain criteria. ♦ ♦ You can use labels. You create deployment groups to deploy objects to another repository within the domain. and Repository Manager. 218 Chapter 9: Grouping Versioned Objects . You might want to run a query to find objects to export or deploy. and deployment groups in the Repository Manager. You can create labels. see “Working with Labels” on page 219. Create deployment groups. You can group objects in the following ways: ♦ Apply labels. This populates the deployment group with a new set of objects each time you deploy the group. and deployment groups to locate and group objects for deployment. You can apply a label to a group of objects across repositories in a domain. The query returns objects that reside in different folders in your development repository. see “Working with Object Queries” on page 224. For more information about queries. you assign a deployment label to those objects you have tested and are ready to deploy. Workflow Manager. you want to track the different versions of objects you create and deploy the latest versions of these objects to the production repository. You then create a query to locate all the objects that use the deployment label. You can deploy objects when you move from test to production. Use labels to track versioned objects. queries. Finally. your environment includes a development repository and a production repository. queries. For information about labels. You use queries to search for versioned objects in the repository. or to compare versions.Overview You can use labels. You create and test metadata in the development repository. see “Working with Deployment Groups” on page 236. and then deploy it to the production repository. As you create objects. For more information about deployment groups. You want to deploy the objects that you test each day. queries. For example. While working in the development repository. To do this.

you might want to apply a label to a group of objects to indicate that you tested the objects and are ready to deploy them. Improve query results. you might apply a label to sources. mappings. Associate groups of objects for deployment. choose Versioning-Labels to browse for a label. Working with Labels 219 . choose Versioning-Labels from the Repository Manager to open the Label Browser. you can lock it to prevent users from editing the label or applying the label to other objects. You can choose to apply the label to multiple object versions when you do not need to limit label applications. Associate groups of objects for import and export. and sessions associated with a workflow so that you can deploy the workflow to another repository without breaking any dependency. For example. Or you can choose to apply the label to one object version when you need to limit the number of times users apply labels. Creating and Editing Labels When you create or edit a label. and add comments. You lock a label to limit access to the label or ensure you apply a label only once. Once you apply the label. You may want to apply labels to versioned objects to achieve the following results: ♦ ♦ ♦ ♦ Track versioned objects during development. Or you can specify that you can apply the label to one version of the object only. which prevents other users from editing or applying the label. You can create and modify labels in the Label Browser. To create a label. For example.Working with Labels A label is a versioning object that you can associate with any versioned object or group of versioned objects in a repository. targets. you can specify the label name. specify the number of times users can apply the label. You can apply the label to multiple versions of an object. You can also choose to lock the label. From the Repository Manager.

Select from the options in the Label Editor to create a label object. Lock the label to prevent users from editing or applying the label. 220 Chapter 9: Grouping Versioned Objects . You can lock the label when you edit it. When you edit a label object. or you can choose to lock the label to prevent other users from editing or applying the label. Label Browser Note: Click a column heading to sort labels by that column.Figure 9-1 shows the Label Browser: Figure 9-1. Select New to open the Label Editor. Figure 9-2 shows the Label Editor options: Figure 9-2. Label Editor Options Enter a name for the label object. you can edit the name or the comments associated with it.

choose Tools-Labels-Apply Label from the Query Results window. and tasks associated with the workflow. You can apply labels to objects when you complete one of the following tasks from the Designer. the Repository Server permanently deletes all instances of the label that have been applied to versioned objects. or Repository Manager: ♦ ♦ View the history of an object. Workflow Manager. which allows you to apply labels to groups of objects. Or. you can choose to label all children objects.When you delete a label. The Repository Server applies labels to sources. When you deploy labels to global shortcut dependencies. targets. if you deploy objects to multiple repositories. choose ToolsLabels-Apply Label from the View History window. you can apply the label to dependent objects in all registered local repositories in a global repository. When you view the history of an object. You can also apply the label to selected dependent objects. you can apply the label to dependent objects in a global repository from a local repository. Applying Labels You can apply one or more labels to any versioned object in the repository. you can apply labels by selecting Versioning-Apply Labels in the Repository Manager. you can apply the label to global shortcut dependencies. you open the Label Wizard. Apply Label Dialog Box Working with Labels 221 . if you want to group dependencies for a workflow. You can select any label you have execute permissions for. mappings. Or. When you run an object query. For example. Create an object query. Or. In the Repository Manager. Figure 9-3 shows the Apply Label dialog box: Figure 9-3.

When you search for an object. you can view metadata for the labels applied to an object. choose Versioning-Apply Labels and click Next. and the comments you entered when applying the label to the object. Applying Labels to Groups of Objects In the Repository Manager. You can apply labels to the following groups of objects: ♦ ♦ ♦ One or more objects in a folder All objects in one or more folders All objects in one or more selected repositories 222 Chapter 9: Grouping Versioned Objects . Previews the group of objects that the Repository Agent applies the label to when you apply labels to dependent objects. If the Repository Server detects the label is applied to another version of the same object. Select one of the previous options. The Repository Agent applies the label to global shortcuts that meet the conditions you specify. Label all Children Label all Parents Primary/Foreign Key Dependencies Global Shortcut Dependencies Preview When you apply a label to parent or child objects. You can view the label owner. you can use the Label Wizard to apply a label to groups of objects. the Repository Agent applies the label to objects that are checked in to the repository. or view object properties. view an object history. You cannot apply labels to checked out objects.Table 9-1 describes the label options: Table 9-1. Applies the label to all repository objects that use the selected object. such as Label all children. you can choose to move the label to the selected version of the object. the timestamp when the label was applied. To open the label wizard. Applies the label to global shortcut objects. and select Global Shortcut dependencies. Applies the label to the source object containing the primary key referenced by the foreign key in the selected source object. Applies the label to all repository objects that the selected object uses. Label Options and Description Label Options Move Label Description Moves the label from a previous version of the object to the latest version of the object.

Figure 9-4 shows the Apply Label Wizard: Figure 9-4. You can select Preview to view the objects the Repository Agent labels. Apply Label Wizard Select the folder or folders containing objects you want to label. After you select objects to label. see Table 9-1 on page 222. Label selected objects. Label all objects in a selected repository. For more information about label options. browse to select the label to apply and choose label options. Working with Labels 223 .

Working with Object Queries
You use an object query to search for versioned objects in the repository that meet specified conditions. When you run a query, the repository returns results based on those conditions. You may want to create an object query to perform the following tasks:

Track objects during development. You can add Label, User, Last saved, or Comments parameters to queries to track objects during development. For more information, see “Query Parameters” on page 227. Associate a query with a deployment group. When you create a dynamic deployment group, you can associate an object query with it. For more information, see “Working with Deployment Groups” on page 236. Find deleted objects you want to recover. For more information about recovering deleted items, see “Recovering a Deleted Object” on page 215. Find groups of invalidated objects you want to validate. For more information about validating groups of objects, see “Validating Multiple Objects” on page 42.

♦ ♦

The Query Browser allows you to create, edit, run, or delete object queries. You can also view the list of available queries in the Query Browser. Choose Versioning-Queries to browse for a query. You can also configure permissions for the query from the Query Browser. For more information about configuring query permissions, see “Permissions” on page 148. Figure 9-5 shows the Query Browser:
Figure 9-5. Query Browser

Edit a query. Delete a query. Create a query. Configure permissions. Run a query.

Note: Click a column heading to sort queries by that column.

224

Chapter 9: Grouping Versioned Objects

In the Query Browser, select New or Edit to open the Query Editor. You can create, validate, and run a query in the Query Editor. Figure 9-6 shows the Query Editor:
Figure 9-6. Query Editor Save query. Validate query. Run query. Add a logical operator. Add a query condition.

Specify query conditions.

When you create a query, you can make it personal or shared. You can run personal object queries you own and any shared object query in the repository.

Configuring Query Conditions
Each query condition consists of a parameter, an operator, and a value. You can add, cut, copy, paste, and move query conditions. Each time you add a query parameter, you specify an operator and a value. You can view the valid operators and values for each parameter when you add the parameter to a query. You may need to configure multiple query conditions to effectively narrow your results. You can use the AND or OR logical operators to add multiple query conditions. For example, you might want to deploy a group of objects with the Deployment_2 label, but you also want to ensure that the objects were saved after a particular date.

Working with Object Queries

225

Figure 9-7 shows a query with multiple conditions:
Figure 9-7. Query with Multiple Conditions Add, edit or move query conditions and operators.

Add logical operators. Add multiple query conditions.

When the Repository Agent processes a parameter with multiple conditions, it processes them in the order you enter them. To receive expected results and improve performance, enter parameters in the order you want them to run. If you nest several parameters within a query, the Repository Agent resolves each inner parameter condition until it can resolve the outer parameter condition. For example, when you run the following query with nested conditions, the Repository Agent resolves the innermost conditions and the next outer conditions until it resolves all parameter conditions:
5 2 1

4

3

226

Chapter 9: Grouping Versioned Objects

Query Parameters
You build queries using query parameters. Each query parameter uses operators and accepts values. Table 9-2 describes the query parameters and the valid operators and values for each parameter:
Table 9-2. Query Parameters and Values Parameter AND Business Name Description Joins query conditions or groups of query conditions. Displays sources and targets based on their business names. For example, the query Business Name is equal to Informatica returns sources and targets that contain the Informatica business name, and filters out all other objects. The query Business Name is not equal to Informatica, filters out sources and targets with the Informatica business name and keeps all other objects. The Business Name query does not return shortcuts to objects that contain business names. Displays objects that are checked in at, before, or after a specified time or within a specified number of days. Valid Operator None Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With Accepted Values None String

Check-in time

Greater Than Is Between Less Than Is Not Between Within Last (days) Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With Greater Than Is Between Less Than Is Not Between Within Last (days) Greater Than Is Between Less Than Is Not Between Within Last (days)

Date/time Numeric

Comments

Displays comments associated with a source, target, mapping or workflow.

String

Deployment Dispatch History

Displays objects deployed to another folder or repository through deployment groups in a given time period.

Date/time Numeric

Deployment Receive History

Displays objects deployed from another folder or repository using deployment groups in a given time period.

Date/time Numeric

Working with Object Queries

227

Table 9-2. Query Parameters and Values Parameter Folder Description Displays objects in a specified folder. Valid Operator Is Equal To Is Not Equal To Is Not One Of Is One Of Where (Value 1) depends on (Value 2) Accepted Values Folder name

Include Children

Displays child dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig N/A

Include Children and Parents

Displays child and parent dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Where (Value 1) depends on (Value 2)

Include Parents

Displays parent dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

Table 9-2. Query Parameters and Values Parameter Invalidated Status Label Description Displays objects invalidated due to changes to a child dependent object. Displays objects associated with a label or group of labels. Valid Operator Is Equal To Is Equal To Is Not Equal To Is Not One Of Is One Of Greater Than Is Between Less Than Is Not Between Within Last (days) Is Equal To Is Not Equal To Is One Of Accepted Values Is invalidated Is not invalidated Labels for which you have execute permissions Date/time Numeric

Last Saved Time

Displays objects saved at a particular time or within a particular time range.

Latest Status

Displays objects based on the object history. The query can return local objects that are checked out, the latest version of checked-in objects, or a collection of all older versions of objects. For more information about restoring deleted objects, see “Recovering a Deleted Object” on page 215. For more information about purging older versions of objects, see “Purging a Version” on page 216. Displays objects based on an extension name or value pair. You can use this query parameter to find non-reusable metadata extensions. The query does not return user-defined reusable metadata extensions. Displays objects based on the object name.

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With

String

Working with Object Queries

229

Table 9-2. Query Parameters and Values Parameter Object Type Description Displays objects based on the object type. For example, you can find all workflows in a specified folder. Valid Operator Is Equal To Is Not Equal To Is Not One Of Is One Of Accepted Values Cube Dimension Mapping Mapplet Scheduler Session Session Config Source Definition Target Definition Task Transformation Workflow Worklet Unused Used

Object Used Status

Displays objects that are used by other objects. For example, you can find mappings that are not used in any session. If any version of an object is used by another object, the query returns the most recent version of the object. This occurs even when the most recent version of the object is unused. The query does not return workflows or cubes, as these objects cannot be used by other objects. For more information about dependencies, see “Viewing Object Dependencies” on page 37. Displays objects based on shortcut status. If you select this option, the query returns local and global shortcut objects. Shortcut objects are considered valid regardless of whether the objects they reference are valid. Displays reusable or non-reusable objects. Displays objects checked in or checked out by the specified user.

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

Is Equal To Is One of Is Equal To Is Not Equal To Is Not One Of Is One Of Is Equal To Is Equal To Is One of

Non-reusable Reusable Users in specified repository

Valid Status Version Status

Displays valid, invalid, and invalidated objects. Displays objects based on deleted or non-deleted status.

Invalid Valid Deleted Not deleted

Note: Valid operators and values depend upon the tool you use to create and view queries.

230

Chapter 9: Grouping Versioned Objects

Validating and Saving a Query
After you create the object query and specify the conditions, you validate it. Select Validate to run the query validation. The Validate Query window displays the validation results. If the validation returns an error, review the error message and validate the query again. Once you validate the query, you can save it for later use. For example, if you regularly run an object query on checkin histories, you might want to save the object query so that you can easily run it again.

Invalid Queries
The query parameters you can view and use in the Query Editor are determined by the tool you use to create queries. When you create a query in one PowerCenter Client tool, the query may appear invalid when you open it in another tool. For example, you can view query parameters such a workflows, worklets, and sessions in the Workflow Designer. If you open a query that uses Workflow Designer parameters in the Designer, the query may appear invalid. For example, you create a query in the Workflow Manager using the following parameters.
♦ ♦

Object Type is equal to Workflow. Valid Status is equal to Invalid.

When you open the query in the Designer, the query appears invalid:
Workflow query invalidated in the Designer.

Queries can be invalidated when you use logical operators with the wrong number or kind of query conditions. For example, an AND logical operator requires at least one parameter to be valid. The following example shows a query that is invalid because the AND operator has no parameters:
The query is invalid because the logical operator requires parameters.

Working with Object Queries

231

Running a Query
After you create and validate the object query, you can run it. The Repository Agent queries the repository and displays the results of the query in the Query Results window. Figure 9-8 shows sample query results from the object query shown in Figure 9-7 on page 226:
Figure 9-8. Sample Query Results

From the Query Results window, you can complete tasks by selecting the object and choosing Tools. Table 9-3 lists additional tasks you can perform from the Query Results window:
Table 9-3. Tasks Available in Query Results Window Task View history. Compare versions. Validate multiple objects. Check in. Undo check out. Export to an XML file. Apply or remove a label. View object dependencies. Task Information See “Viewing Object History” on page 208. See “Comparing Versions” on page 210. See “Validating Multiple Objects” on page 42. See “Checking Out and Checking In Objects” on page 211. See “Checking Out and Checking In Objects” on page 211. See “Exporting and Importing Objects” on page 263. See “Working with Labels” on page 219. See “Viewing Object Dependencies” on page 37.

232

Chapter 9: Grouping Versioned Objects

Table 9-3. Tasks Available in Query Results Window Task View version properties. Add version to deployment group. Change object status. Purge a version. Save object version history to a file. Open object in a workspace. Task Information See “Viewing Version Properties” on page 203. See “Working with Deployment Groups” on page 236. See “Changing Object Status” on page 206. See “Purging a Version” on page 216. To save the version history to an HTML file, choose File-Save to File. Select this option to open an object in the workspace when the object type is compatible with the tool in which you run the query. For example, you can open a workflow in the Workflow Manager using this option.

For more information on managing versioned objects, see “Working with Versioned Objects” on page 199.

Viewing Query Results
By default, when you run an object query, the Repository Agent returns objects that meet the following criteria:
♦ ♦ ♦

Objects are the latest version, either local checkout versions or checked-in versions. Objects are reusable. Objects that are not deleted.

If you want to view deleted or older objects, you must specify these values in the query parameter. You can search for deleted objects using the Deleted value in the Version Status parameter. You can search for older versions of objects when you specify the Older value in the Latest Status query parameter.
Note: If you run a query without specifying query conditions, the query returns reusable

objects in the repository.

Sample Queries
The following sample queries illustrate how to create query conditions with different parameters, operators, and values.

Finding Recently Deployed Objects
The following query returns the latest checked-in version of objects deployed within the last seven days and are reusable or non-reusable:

Working with Object Queries

233

Finding Invalidated Mappings
The following query returns the latest checked-in version of objects that are invalidated and whose object type is mapping. The Designer or Workflow Manager invalidates a parent object when you modify a child object in such a way that the parent object may not be able to run. The query returns invalidations for composite objects such as mapplets, mappings, sessions, worklets and workflows:

Note: You can use the invalidated object query to search for invalidated objects and run a

validation on multiple objects. For information about validating multiple objects, see “Validating Multiple Objects” on page 42.

Finding Invalid Mappings
The following query returns the latest checked-in version of objects in the repository that are invalid and whose object type is mapping. The Designer or Workflow Manager invalidates a parent object when you modify a child object in such a way that the parent object may not be able to run.

Finding The Used Status of Objects
The following query returns the latest checked-in version of objects that are mappings and that are not used by any session:

Finding Older Versions of Objects
The following query returns objects that are mappings and that are older and that are checked in by the Administrator:

234

Chapter 9: Grouping Versioned Objects

Select source definitions and target definitions for Value 1 and select mapping for Value 2. choose to include children and parent dependencies.Finding Object Dependencies The following query returns sources and targets in the Vendors folder that are dependent on the mapping. Mapping_deploy. select both reusable and non-reusable dependency in Value 3: Working with Object Queries 235 . To search for parent and child dependencies. To include reusable and non-reusable dependencies.

View the objects in a static or dynamic deployment group. You use the result set from an object query to populate the deployment group. choose Versioning-Deployment Groups from the Repository Manager. You can complete the following tasks: ♦ ♦ ♦ ♦ Create or edit a deployment group. see “Creating and Editing a Deployment Group” on page 237. View the history of a deployment group.Working with Deployment Groups A deployment group is a versioning object that allows you to group versioned objects for deployment to a different repository. For more information. You populate the deployment group by manually selecting objects. For more information. For more information see “Permissions” on page 148. You can create the following types of deployment groups: ♦ ♦ Static. 236 Chapter 9: Grouping Versioned Objects . see “Viewing Deployment History” on page 237. and user who ran the deployment. Note: Click a column heading to sort deployment groups by that column. Deployment Group Browser Preview the objects in a deployment group. Figure 9-9 shows the Deployment Group Browser: Figure 9-9. You can view the history of a deployment group. including the source and target repositories. Dynamic. You can run a query to preview the objects that the Repository Agent will deploy. deployment date. Configure permissions for a deployment group. View the history of a deployment group. To work with deployment groups.

Viewing Deployment History To view the history of a deployment group. and configure the options in the Deployment Group Editor. you add objects to a static group or associate an object query with a dynamic group. You can view the following information about groups you deployed: ♦ ♦ ♦ ♦ ♦ Date/time. Source repository. The user name of the person who deployed the group. select a deployment group in the Deployment Group Browser and choose View History. The name of the deployment group. Deployment group name. Choose a static or dynamic group. Target repository. The repository where you deployed the group. Select a query to associate with a dynamic deployment group. Figure 9-10 shows the Deployment Group Editor: Figure 9-10.Creating and Editing a Deployment Group To create or edit a deployment group. Deployment Group Editor Enter a name for the deployment group. The date and time you deployed the group. choose New or Edit from the Deployment Group Browser. User name. Once you create the deployment group. Working with Deployment Groups 237 . The repository you deployed the group from.

Figure 9-11 shows the Deployment Group History: Figure 9-11. When you roll back a deployment. Select a deployment to roll back. Deployment Group History Initiate a rollback. The rollback also fails if the rollback process causes you to create duplicate object names. 3. Rolling Back a Deployment You can roll back a deployment. The rollback results display at the end of processing. The rollback ensures that the check-in time for the repository objects is the same as the deploy time. If any of the checks fail. 238 Chapter 9: Grouping Versioned Objects . create a new object with the same name. 2. If the check-in time is different.For more information about deploying objects to repositories. To roll back a deployment: 1. The Repository Agent checks the object versions in the deployment run against the objects in the target repository. then the repository object is not the same as the object in the deployment. Select a deployment group in the Deployment Group Browser and choose View History. You can initiate a rollback on a deployment as long as you roll back only the latest versions of the objects. and attempt to roll back the original deployment. Click Rollback. Rolling back a deployment purges the deployed versions from the target repository. see “Copying Folders and Deployment Groups” on page 241. The rollback fails. the Repository Agent notifies you of the object that caused the failure. This might occur if you rename a deployed object. You cannot roll back part of a deployment. you roll back all the objects in a deployment group that you deployed at a specific date and time.

You can add checked in objects to a static deployment group from the Repository Manager. In the Repository Manager. For example. choose Tools-Add to deployment group. right-click an object in the Navigator or in a detail window. To add several objects to a deployment group. You cannot add checked out objects to a deployment group. You manually add or delete objects from a static deployment group. You can add objects to a deployment group when you view the results of an object query or view the results of an object history query from the Repository Manager. Non-reusable. you might group objects for deployment on a certain date and deploy all objects at once. Dependent objects can include dependent objects within a workflow or mapping as well as objects that shortcuts reference and primary key sources where there is a primary keyforeign key relationship.Working with Static Deployment Groups You might want to create a static deployment group if you do not expect the set of deployment objects to change. For information on deploying groups to a repository. you can also add child dependent objects to the deployment group. In the View History window. Select to deploy non-reusable dependent child objects. Figure 9-12 shows the Dependency for deployment group dialog box: Figure 9-12. you add all dependent objects to the static deployment group. Working with Deployment Groups 239 . No dependencies. You can specify the following conditions for adding child dependencies: ♦ ♦ ♦ All dependencies. select the group of objects in the Navigator and drag them into the deployment group. Select to skip deploying dependent objects. Dependency for Deployment Group Dialog Box When you select All Dependencies. see “Copying Folders and Deployment Groups” on page 241. When you add objects to a static deployment group. and choose Versioning-View History. choose Tools-Add to deployment group. To add objects from the Query Results or View History windows. Select to deploy all child dependencies.

The parent object and non-reusable child objects in a dynamic deployment group may not have the same label applied to them in the following circumstances: ♦ ♦ You changed the parent object. You can associate an object query with a deployment group when you edit or create a deployment group. you must create all mappings in the group with labels. For example. If the dynamic deployment group contains a non-reusable object in an unlabeled mapping. You can run the dynamic deployment group query multiple times and add new objects to the group each time you run the query. 240 Chapter 9: Grouping Versioned Objects . the group will not deploy. see “Working with Versioned Objects” on page 199.Working with Dynamic Deployment Groups You might want to create a dynamic deployment group if you expect the set of deployment objects to change frequently. the Repository Agent runs the query at the time of deployment. see “Copying Folders and Deployment Groups” on page 241. You applied different labels to reusable or non-reusable objects when viewing the object history in the results view. you might use a dynamic deployment group if you develop multiple objects for deployment on different schedules. but did not apply a label to the latest version of the object. Using Queries with Dynamic Deployment Groups When you associate an object query with the deployment group. For more information on managing versioned objects. For more information on deploying groups of objects. If you want to find the latest versions of objects in a dynamic deployment group.

242 Using the Copy Wizards. 244 Copying or Replacing a Folder. 254 241 . 248 Copying a Deployment Group.Chapter 10 Copying Folders and Deployment Groups This chapter contains information on the following topics: ♦ ♦ ♦ ♦ Overview.

If the repository is enabled for versioning. or from a source repository into a target repository. you have a development and production repository. As development continues you make changes to a session in the folder. You can copy a folder and all of its contents from a source repository and replace an existing folder of the same name in the target repository. You do not need to copy all of the metadata in the folder to production. You edit the Sales folder in the development repository and test the changes. When you copy the deployment group. Copying a deployment group also allows you to specify individual objects to copy. You can copy the objects in a dynamic or static deployment group to multiple target folders in the target repository. you can replace the folder. Replace a folder. You might use copy folder and copy deployment group together in your repository environment at different stages of the development process. For example. For example. After a week in production. When the folder is ready for production. The deployment operation creates new versions of existing objects in the target folders. or you can replace the existing Sales folder with the new one. ♦ If you want to archive or share metadata or deploy metadata into production. you want to make minor changes. If you want to update the metadata in a folder already in production. You can perform the following copy operations: ♦ ♦ Copy a folder. the repository does not allow the PowerCenter Server to fetch objects from the target repository. When you complete initial development for the metadata in a new folder and you are ready to deploy the objects into production you copy the folder and all of its objects into the production repository. Copying a deployment group allows you to copy objects in a single copy operation from across multiple folders in the source repository into multiple folders in the target repository. You can copy a folder and all of its contents within a repository. resulting in two copies of the folder in production. you have a folder called Sales in the development repository. When a PowerCenter 242 Chapter 10: Copying Folders and Deployment Groups . you copy the Sales folder into the production repository. When it is ready for production. You can also effectively use different copy operations together. Copy a deployment group. Replacing the folder allows you to update the production repository without creating multiple copies of the folder. you may use copy folder to copy an entire folder. you can either copy the folder into the production repository. PowerCenter Server Processing When you copy or replace a folder. rather than the entire contents of a folder.Overview You can use the Repository Manager to copy multiple objects from one repository to another. the Copy Deployment Group wizard creates a new version of the session in the target folder. you may also copy the objects in a deployment group from one repository to another. The contents of the replaced folder are overwritten. so you add the session to a deployment group. or copy a deployment group.

Overview 243 . session. The current operation will be suspended until the deployment is completed.Server tries to access the repository to run a workflow. if the PowerCenter Server tried to fetch session information to run a session in a workflow. It cannot fetch objects in that repository during this time. When the repository allows access again. workflow log. The current operation will resume. or task. it displays the following message: The folder/object deployment has completed. session. The PowerCenter Server pauses until the repository completes the deploy. the message appears in the workflow log. For example. or session log. depending on which operation the PowerCenter Server tried to perform. The error message appears in either the server log. The PowerCenter Server fetches the repository object and completes the workflow. the repository denies access and returns the following message: Access to the repository is blocked since a folder/object deployment is in progress. or task while a repository is blocked.

Copy database. Retain assigned PowerCenter Server settings. Copy the saved persisted values for mapping variables used in a session and workflow variables used in a workflow. You can choose the shared folder to associate shortcuts. you must perform many of the same actions to ensure both the Copy Folder and Copy Deployment Group wizards allow you to perform the following actions: ♦ ♦ Choose a PowerCenter Server. Copy plug-in application component information that does not exist in the target repository. ♦ ♦ ♦ ♦ For specific instructions on using the Copy Folder Wizard to copy or replace a folder. The wizard might have to determine how the folders are related before establishing shortcuts. you must choose from the following Copy Wizard modes: ♦ ♦ Typical.Using the Copy Wizards The Repository Manager provides a wizard to copy and replace folders and to copy deployment groups. You can override the defaults for shortcuts to local and global shared folders. 244 Chapter 10: Copying Folders and Deployment Groups . For specific instructions on using the Copy Deployment Group Wizard to copy a deployment group. Copy Modes When you copy a folder or deployment group. Copy the metadata extension values associated with repository objects. Retain the assigned server settings for workflows and session instances configured to run on specific PowerCenter Servers in a server grid. see “Copying a Deployment Group” on page 254. see “Copying or Replacing a Folder” on page 248. When you copy a folder or deployment group. Copy persisted values. Use the PowerCenter Server to run all workflows in the folder if a matching server does not exist in the target repository. Advanced. The wizard steps vary depending on the operation and the contents of the folder or deployment group you want to copy. Copy metadata extension values. Copy plug-in application information. The wizard uses the defaults for shortcuts to local and global shared folders. and Application connection information if matching connection names do not exist in the target repository. FTP. external loader. Copy connections.

the Copy Wizard uses the existing connection. If the target repository has no registered PowerCenter Servers. the wizard does not copy PowerCenter Server connection information. you can associate them with multiple PowerCenter Servers in the target repository. the Workflow Manager assigns all workflows to that first PowerCenter Server. ♦ Tip: If you want to use PowerCenter Servers with the same name. the wizard associates the workflow with the same PowerCenter Server in the target repository. you can choose a PowerCenter Server to run the workflow. the wizard lists all of the PowerCenter Servers in the target repository. Using the Copy Wizards 245 . The wizard does not overwrite connections in the target repository. when you register a PowerCenter Server with the repository. ♦ ♦ ♦ Associating with Multiple PowerCenter Servers If the workflows in a folder are associated with multiple PowerCenter Servers in the originating repository. If a PowerCenter Server with the same name does not exist in the target repository. If you associate another PowerCenter Server with a workflow when you copy a folder. the wizard registers those workflows with the existing PowerCenter Servers. it registers all unassociated workflows. Instead. If there is only one PowerCenter Server in the target repository. make sure that the directory structure for server variables and other directory paths in the session properties match.Registered PowerCenter Servers Each workflow is configured to run on an associated PowerCenter Server in the repository. You then select one of those Servers to run all unassociated workflows. If the target repository does not contain a PowerCenter Server with the same name. you must register those servers before you copy the folder. The wizard associates or prompts you to associate a copied session with a PowerCenter Server in the target repository under the following circumstances: ♦ If the target repository contains a PowerCenter Server name that matches the PowerCenter Server or servers configured to run the folder workflows. The Copy Folder Wizard uses the following rules to associate servers: ♦ If the target repository contains a PowerCenter Server name that matches the PowerCenter Servers configured to run the folder workflows. Connections The Copy Wizard copies connections used by sessions in the folder or deployment group. If the connection already exists in the target repository.

♦ User-defined extensions. When you copy an object that contain user-defined. Reusable Metadata Extensions Reusable metadata extensions apply to all repository objects of a certain type. such as all workflows or all Expression transformations. Reusable metadata extensions that you create exist in the User Defined Metadata Extension domain. A matching object with the same name exists in the target repository. the wizard displays the following information about connections: ♦ ♦ ♦ No Match Found. The metadata extension values may or may not be available in the target repository. This depends on whether the extensions are non-reusable or reusable.Permission Denied. Permissions Denied. The wizard copies the object and renames it by appending a number to the name. the wizard retains the value of the metadata extension in the target repository. or promote it to a reusable extension. the Copy Wizard copies the extension to the target repository with the object. For more information about non-reusable metadata extensions. If the definition does not exist in the target repository. You have access to the object in the originating repository. ♦ Metadata Extensions When you copy objects to another repository. Match Found .When you copy a folder or deployment group. The wizard copies the object. A matching object with the same name exists in the target repository. 246 Chapter 10: Copying Folders and Deployment Groups . When you copy an object that contains a non-reusable metadata extension. see “Working with Metadata Extensions” on page 327. You have access to the object in the originating repository. the Copy Wizard copies the extensions to the target repository. will copy and rename to [new_name]. If the metadata extension contains a value. Non-Reusable Metadata Extensions Non-reusable metadata extensions apply to single objects such as one source definition or one session. No match exists in the target repository. The extension becomes nonreusable in the target repository. delete it. the copied extensions become non-reusable. You can edit it. You have access to the objects in both the originating and target repositories. You have no access to the object in the originating repository. Match Found. the Copy Wizard copies the metadata extension values associated with those objects to the target repository. You create non-reusable metadata extensions in the Designer or Workflow Manager. All sessions using this connection are invalidated. If the definition exists in the target repository. the copied extensions become reusable in the target repository. but no access to the object in the target repository. reusable metadata extensions. Reusable extensions that other applications create exist in the appropriate vendor domain.

see “Working with Metadata Extensions” on page 327. If the vendor domain exists in the target repository. When you copy an object that contains vendor-defined metadata extensions. Therefore. Using the Copy Wizards 247 . the extensions are not available in the target repository. If you continue. the metadata extensions become available so you can view them and change their values. The source folder contains a source or target with a plug-in application database type. For more information about reusable metadata extensions and domains. you can view them or change the values as you do with the other metadata extensions in that domain. The source folder or deployment group depends on a plug-in application in the following cases: ♦ ♦ ♦ The source folder contains metadata extension values from a vendor-defined metadata domain.♦ Vendor-defined extensions. If the vendor domain does not exist in the target repository. the Copy Wizard copies the extensions to the target repository and retains their values. Copying Plug-in Application Information When you copy a folder or deployment group. The source folder uses plug-in application connections. if the folder or deployment group depends on the plug-in application information. you can copy plug-in application information. the Copy Wizard allows you to cancel the copy or continue. When you install the vendor application. the metadata extensions become part of that domain in the target repository.

the Copy Folder Wizard allows you to perform the following actions: ♦ ♦ ♦ Reestablish shortcuts. or replace them with values from the source folder. you can rename the copy of the source folder created the Copy Folder Wizard creates in the target repository. When you replace folder. the wizard copies all of the metadata objects in the folder. the wizard makes you the owner of the copied folder. back up your repository before replacing a folder. you can replace the existing folder with the updated data. You might replace a folder when you want to update a folder that is already in production. the folder replacement operation overwrites the objects in the target folder. If you copy the latest object version in the source folder. Compare folders. Note: When you copy a folder. You can choose to retain existing workflow logs.Copying or Replacing a Folder In the Repository Manager. Copy latest object versions or all object versions. the wizard maintains properties of the replaced folder. When you replace a folder. or all versions. You can choose to retain existing values. the wizard rolls back all changes. To ensure no metadata is lost. You can also copy a folder into a different repository within the same domain or to a different domain. You can choose to retain existing values. You can choose to copy only the latest version of objects in the source folder. you can copy a folder within the same repository. You can choose to retain existing values. It does not overwrite previous versions in the target folder. and external loader connection information. Maintain shortcuts to objects in shared folders. FTP. the wizard creates a new version of existing replaced objects in the target folder. such as shortcuts. If a folder in the target repository has the same name as the folder you are copying. When replacing a folder. Retain persisted values for mapping variables. the wizard deletes the existing folder. When you copy a folder. or replace them with workflow logs from the source folder. or replace them with values from the source folder. ♦ You can also copy and replace a folder across repositories. Compare folders to determine how they are related. Copy latest object versions or all object versions. the wizard allows you to perform the following additional actions: ♦ ♦ ♦ ♦ ♦ Retain current values for Sequence Generator and Normalizer transformations. Use the Copy Folder Wizard to perform the copy or replace operation. or replace them with values from the source folder. Retain persisted values for workflow variables. The wizard copies and replaces folders as a single transaction. The Copy Folder Wizard allows you to perform all of the tasks listed in “Using the Copy Wizards” on page 244. Instead of creating a second copy of the folder in the production repository. Rename folders. 248 Chapter 10: Copying Folders and Deployment Groups . Workflow logs. If you copy all versions from the source folder. If you cancel the copy before it completes. Each time you copy or replace a folder.

the wizard appends the date to the folder name. the wizard names the copy after the folder. the wizard asks you to copy it again. local shortcuts become global shortcuts. the wizard deletes all shortcuts and marks all affected mappings invalid. verify that no objects in the target folder are checked out. Locking and Checkouts To protect the integrity of the repository. Local Shortcuts The wizard can reestablish local shortcuts to shared folders if you have a current copy of the shared folders in the target repository. Shortcuts The folder or you want to copy might contain shortcuts to shared folders in the same repository or to shared folders in the global repository. the wizard does not allow you to copy a folder when the folder. Shortcuts to the global repository are called global shortcuts. dd=days. If the folder name already exists in the repository. If you are replacing a folder in a repository that is enabled for versioning. Before you copy a folder. In the advanced mode. If you copy the folder from the global repository to a local repository in the same domain. Shortcuts to folders in the same repository are known as local shortcuts. are being saved. you must copy shared folders before copying the folder. see “Repository Security” on page 125. Therefore. and you choose not to replace it. For more information on changing the status of an object. view object locks to verify that the folder is not in use. if you edit the original shared folder after you copy it to the target repository. If you a replacing a folder in a target repository enabled for versioning. you can compare the folders to see which folder is most recent. Therefore. Copying or Replacing a Folder 249 . you can keep shortcuts intact by copying the necessary local shared folders to the target repository before copying the folder. see “Viewing Checked Out Objects” on page 211. to copy shortcuts correctly.Naming When you copy a folder. as follows: <folder_name>_mm/dd/yyyy (where mm=months. For more information on searching for checkouts in the repository. The wizard does not establish shortcuts to an outdated shared folder. In typical mode. you cannot save objects in a folder as the wizard copies the folder. Likewise. For details on locking. the wizard verifies whether the copy is current. or objects in the folder. you must also verify that no objects in the target folder are checked out. If shared folders exist in the target repository. If you do not copy the shared folders before copying the folder. and yyyy=year). see “Working with Version Properties” on page 203.

If it does. Global Shortcuts The wizard can reestablish global shortcuts if you copy the folder or deployment group to another repository in the same domain in the following situations: ♦ ♦ ♦ When you copy a folder from one local repository to another within the domain. If you want to copy the folder again. you can also choose to establish local shortcuts to the shared folder in the local repository. using a naming convention that clearly defines the existing folder. If you copy the folder in advanced mode. the wizard asks you to rename the folder. use the Repository Manager to verify no users are accessing objects in the folder. and the copied folder continues to use the same connection and server information. you establish global shortcuts to the shared folder in the global repository.For example. local shortcuts become global shortcuts. you might want to rename the existing folder in the target repository. If you copy a folder that contains global shortcuts between domains. If it does not. The Copy Wizard will either reestablish global shortcuts as a local shortcuts. the wizard recreates global shortcuts to the global repository. Steps for Copying or Replacing a Folder Before you copy a folder. it asks you to rename the folder. copy any shared folders from the local and global repositories in the source domain to either the local or global repository in the target domain. The wizard reestablishes all shortcuts. Copying From Local Repositories When you copy a folder from a local repository to another repository. the wizard uses the folder name for the copied folder. If you have edited objects in any local shared folders used by the folder. When you copy a folder from a local repository to its global repository. or establish the copied shortcuts as global shortcuts. Copying Within a Repository When you copy a folder within the same repository. You might want to rename existing shared folders before performing the copy. you must copy those shared folders into the target repository before copying the folder. Then copy the non-shared folder. You might want to ask all users to exit the repository Also. First copy the shared folder into the local repository. you want to copy a shared folder and a non-shared folder with shortcuts from a global repository to a local repository. When you copy a folder from a global repository to a local repository within the domain. the wizard verifies whether a folder of the same name exists in the target repository. If you choose to copy the folder in typical mode. the global shortcuts become local shortcuts. copy dependent 250 Chapter 10: Copying Folders and Deployment Groups .

The Copy Folder Wizard appears. or all versions. verify no users are accessing objects in the target repository. 5. and choose Edit-Paste. connect to the target repository.shared folders to the target repository before copying a folder. In the Navigator. see “Repository Manager Tasks” on page 516. The wizard might have to determine how the folders are related before establishing shortcuts. To stop the replacement. The Copy Wizard prompts you for more information based on the content of the folders and the copy mode you selected. You can choose the shared folder to associate shortcuts. compare the folders to determine the similarities and differences between the folders. If copying to a different repository. Replace Folder Folder Modified Compare Folders Typical/Advanced Typical/Advanced Typical/Advanced Sequence Generators and Normalizers Mapping Variables Typical/Advanced Typical/Advanced Copying or Replacing a Folder 251 . 3. Choose to retain current values for Sequence Generator and Normalizer transformations. The wizard rolls back all changes. If you are replacing a folder. If you specified that the source folder contains new or modified objects. If you are replacing a folder. displaying the folder name and target repository name. You can override the defaults for shortcuts to local and global shared folders. connect to the source repository and select the folder you want to copy. Copy persisted values for mapping variables if they exist. For information on the privileges and permissions to copy a folder. copying the latest version adds a new version to the existing objects in the target folder. List existing copies of the folder or all folders in the repository Specify if objects in the source folder have been created or modified since the last copy. The wizard uses the defaults for shortcuts to local and global shared folders. 2. Tip: You can also drag and drop the folder into the target repository after connecting to the repository. To copy or replace a folder: 1. Table 10-1 lists the dialog boxes and prompts that you may see when you copy a folder: Table 10-1. 6. 4. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Latest Version Only Mode Typical/Advanced Prompt Choose to copy the latest version of objects in the folder. click Cancel. Advanced. select the target repository. The Copy Folder dialog box prompts you to select a mode: ♦ ♦ Typical. Click Next. Choose Edit-Copy. In the Repository Manager.

Copy persisted values for workflow variables. To preserve shortcuts and prevent invalid mappings. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Retain Mapping Variables Dependency Information Workflow Variables Retain Workflow Variable Persisted Values Copy Workflow Log Retain Workflow Logs Folder Exists Mode Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Prompt If you are replacing a folder. Choose to copy workflow logs if they exist. if it exists. Choose to retain the assigned PowerCenter Server information for workflows and sessions configured to run on specific PowerCenter Servers in a server grid. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. Allows you to select a PowerCenter Server to run all nonassociated workflows.Table 10-1. Lists all application connections in the folder. Otherwise. click Cancel and copy all listed local shared folders before copying the folder. Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder. Lists local shared folders in the target repository that you need to copy first. Lists all external loader connections in the folder. To preserve shortcuts and prevent invalid mappings. click Cancel and copy all listed local shared folders before copying the folder. choose to retain persisted values for mapping variables. Copy dependency information for objects in mappings. indicating the connections for which you do not have read permission. indicating the connections for which you do not have read permission. Lists all FTP connections in the folder. If the target repository contains less than two PowerCenter Servers. indicating the connections for which you do not have read permission. the wizard skips this step. indicating the connections for which you do not have read permission. Retain Server Settings Typical/Advanced Database Connections MQ Connections FTP Connections External Loaders Application Connections Plug-in Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Servers Typical/Advanced Local Shared Folders Typical Global Shared Folders Typical 252 Chapter 10: Copying Folders and Deployment Groups . Choose to retain persisted values. Lists all MQ connections in the folder. Lists all database connections in the folder. it appends the date to the original folder name. Lists global shared folders in the target repository that you need to copy first. Rename the target folder if a folder of the same name exists in the target repository.

Also displays objects that are older or newer than matching objects in the global shared folder. Lists folders you can select to establish shortcuts if you choose to override the default folder selection in the Select Shared Folders dialog box. Lists all dependent local and global shared folders. Lists the results from the folder compare. click Cancel and copy all listed local shared folders before copying the folder. To preserve shortcuts and prevent invalid mappings. Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different.Table 10-1. Select Shared Folders Advanced Override Shared Folder Advanced Compare Shared Folder Compare Results Advanced Advanced Copying or Replacing a Folder 253 . The wizard takes you back to Select Shared Folders dialog box. If there are differences between the folders. a message warns you that shortcuts to missing objects will be removed. You can choose to accept or override the shared folder. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. Displays objects that exist in the local shared folder but not in the global shared folder. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Outdated Shared Folders Mode Typical Prompt Lists outdated folders in the target repository that you need to copy first.

If you choose to deploy part of a composite object. When you copy a deployment group. An object in the target repository may also have the same name as an object in the deployment group. As a result. For details on object naming. but have a different name. The wizard does not allow you to reestablish global shortcuts. The next time you copy the object. the Copy Deployment Group Wizard does not allow you to copy a deployment group when objects targeted for replacement are checked 254 Chapter 10: Copying Folders and Deployment Groups . the wizard first runs the query associated with the deployment group and then copies the objects from the results of the query. ♦ ♦ ♦ The status of the object in the target repository is different from the status of the object in the deployment group. you can also use the Copy Deployment Group Wizard to copy objects in a deployment group into multiple deployment folders in the target repository. the wizard replaces the copy of the object and create a new version of the object with the same name as the deployment group object. Object names in the target repository are different from or conflict with the deployment group object. you must ensure that the correct shared folders and necessary global shortcuts exist in the target repository. When you create a deployment group you can choose to copy all or part of composite objects. At the time of deployment. After it creates the new version. In this situation. the wizard cannot copy the deployment group object. but may not be a copy of the deployment group object. You copy local and global shortcuts. see “Object Naming” on page 257. the wizard copies all objects included in a static deployment group. If you are copying a dynamic deployment group. see “Copying Composite Objects” on page 255. see “Copying Shortcuts” on page 256. the wizard identifies the previously copied object and replaces it. Locking and Checkouts To protect the integrity of repository metadata. The first time you copy an object in a deployment group to the target repository. The status of an object in a deployment group may change after the copy operation depending on the status of the copy of the object to be replaced. you must be aware of the relationships between objects in the deployment group and the target repository under the following circumstances: ♦ You copy part of a composite object. For details on copying composite objects in a deployment group. An object in the target repository may be a copy of the object in the deployment group. creating a new version of the object in the target repository. the wizard checks in the object. As a result. For more information.Copying a Deployment Group If the repository is enabled for versioning. For details on changes to object status when you copy a deployment group. If this naming conflict occurs. the wizard allows you to reestablish local shortcuts to objects in shared folders. see “Object Status” on page 257. the wizard creates a new object in the target repository. you must ensure that dependent objects exist in the target folder.

and several non-reusable transformations. For details on locking. the deployment group objects may be copied to the target repository. If you choose to copy no dependencies or non-reusable dependencies for a composite object. search for checkouts in the target repository and verify that no deployment target objects are checked out.out or locked. Before you copy a deployment group. You must ensure that the dependent objects are also included in the deployment group or already exist in the target repository. the objects will be stored in the repository as checked out objects. Change the folder status to Frozen. Copying Composite Objects A composite object is one that uses other objects. but not checked in. View checkouts and manually check in the objects to complete the copy operation. If the wizard cannot locate necessary dependencies in the target repository. For more information on viewing checked out objects in the repository. Allow Deploy. For example. If this happens. but the wizard can still copy and check in deployment group objects. nonreusable dependencies. see “Repository Security” on page 125. You add the mapping to a deployment group with no dependencies because you do not want to update any non-reusable or reusable transformations in the mapping. The next time you deploy the group. you can add all or some object dependencies to the deployment group. you edit a mapping variable in a mapping. Copying a Deployment Group 255 . However. other users cannot check out objects in the folder. it fails the copy operation. Each of these objects is a child dependency of the mapping. You can copy the following composite objects to a deployment group: ♦ ♦ ♦ ♦ ♦ ♦ Local shortcuts Mappings Mapplets Sessions Worklets Workflows When you create a deployment group. When you copy the mapping to the production repository. you must include all dependencies of the composite object. For more information on changing the status of an object. The first time you deploy a group. You want to update the copy of the mapping currently stored in the production repository. the Repository Agent rolls back changes. see “Working with Version Properties” on page 203. For example. or no dependencies for composite objects. the wizard uses existing copies of objects in the target repository for all child dependencies not included in the deployment group. Note: If the repository stops unexpectedly during the copy operation. see “Checking Out and Checking In Objects” on page 211. you can choose to include all dependencies. a mapping may use a reusable source. When you freeze a folder. reusable target. You can freeze the target deployment folder to ensure that no target objects are checked out when you copy a deployment group.

You can design the query to search for dependencies of a composite object. You may want to further refine the query for a dynamic deployment group by specifying other parameters. For example. You can also add dependencies to the deployment group. the wizard asks you to copy it again. In advanced mode. You may want to add all dependencies the first time you copy an object to another repository. Shortcuts to folders in the same repository are known as local shortcuts. see Table 10-2 on page 258. If you do not copy the shared folders before copying the deployment group. the Repository Agent treats associated non-reusable objects as deleted. Use one of the following methods to ensure that you include dependencies in the deployment group: ♦ Manually add the dependencies to the static deployment group. Copying Shortcuts The deployment group you want to copy might contain shortcuts to shared folders in the same repository or to shared folders in the global repository. see “Working with Deployment Groups” on page 236. Shortcuts to the global repository are called global shortcuts.the wizard replaces the current version of the mapping and associates all existing transformations with the new version. You can keep these shortcuts intact by copying the necessary local shared folders to the target repository before you copy the deployment group or by including the object the shortcut references in the deployment group. if the parent object is deleted. If the referenced object already exist in the target repository. The PowerCenter Client prompts you to do this when you manually add an object to a static deployment group. the wizard compares 256 Chapter 10: Copying Folders and Deployment Groups . When you compare folders. the wizard verifies that the copy is current. Local Shortcuts The wizard can reestablish local shortcuts to objects in shared folders if you have a current copy of the object in the target repository. the Repository Agent treats the non-reusable objects in the composite object as part of the parent object. For details about the status of deployed objects. To ensure that necessary dependencies exist in the target repository. ♦ For more information on creating static and dynamic deployment groups. In typical mode. and then decide to cancel and copy the shared folder again or proceed with the copy operation. you can compare the contents of the folders to see which contains the most recent copies of referenced objects. Design the query associated with the dynamic deployment group to find dependencies. the wizard deletes all shortcuts and marks all affected mappings invalid. you might want to copy the entire folder to the target repository the first time you copy the objects. You can then use deployment groups to update individual objects over time. Note: When you deploy composite objects. if you edit the original shared folder after you copy it to the target repository.

If you are copying the object for the first time. the naming conflict causes the copy operation to fail. you change the name of the mapping in the development repository to m_OrdersWeekly. creating a new version. The wizard deletes the shortcut and marks all affected mappings invalid. Copying a Deployment Group 257 . the copy operation fails because the XML source src_Records has the same name. verify that a copy of the object. As a result. You add this new version of the mapping to a deployment group and copy it to the production repository. you have the mapping m_Orders in the development repository. You can then use a deployment group to copy subsequent versions of the object. and replaces it. you delete src_Records from the production repository and create a new XML source. the copy operation fails. but the copy has a different name. The object may be of a different type. If you copy a global shortcut alone. you might add an object to a deployment group that has an existing copy in the target folder. To ensure that global shortcuts are preserved when you copy a composite object. but is not a copy of the object. the wizard completes the copy operation but does not copy the shortcut. The latest version of the mapping in the production repository is now m_OrdersWeekly. if you copy a local shortcut into the same folder that contains the object the shortcut references. the wizard cannot reestablish the shortcut. In this situation. including the shortcut. You add it to a deployment group and copy it to the production repository. Also. Object Naming Different versions of an object may have different names. also named src_Records. For example. the status of the source object may change if a copy of the object already exists in the target folder. Object Status When you copy an object in a deployment group. The wizard determines that m_Orders is an older copy of m_OrdersWeekly. but is a different object. If this happens. Later. you have a mapping that uses relational source src_Records in the development repository. If the global shortcut is part of a composite object you want to copy. consider copying the entire folder. You might also have an object in the target repository that has the same name as a deployment group object. the wizard detects the relationship between the two objects and replaces the copy in the target folder with the deployment group object. If you then use a deployment group to copy the relational source src_Records to the target repository. Global Shortcuts If the deployment group contains global shortcuts.the version of the objects in the deployment group with the latest version of objects in the target folder. exists in the target repository. the wizard does not reestablish them when you copy them to the target repository. As you continue development. For example. You add the mapping to a deployment group and copy it to the production repository.

For example. Also. see “Working with Deployment Groups” on page 236. It also allows you to perform the following tasks: ♦ ♦ Choose deployment folders. The repository stores a deployment history for each deployment group. ♦ ♦ You can copy a deployment group only if the source and target repositories are both enabled for version control. you might want to move a label from the last version to the latest version before you deploy an object. You can apply labels to the deployment group objects in the source and target repositories.Table 10-2 describes the status an object may take after copying the deployment group. Move labels. Clear the static deployment group when you finish copying. You can choose the specific folders in the target repository you want to deploy. depending on the status of the source and target objects: Table 10-2. The Copy Deployment Group Wizard allows you to perform all of the tasks listed in “Using the Copy Wizards” on page 244. you might want to deploy an earlier version of an object and apply the latest label to the object. Steps for Copying a Deployment Group Use the Copy Deployment Group Wizard to copy objects in a deployment group. Apply labels to source and target objects. Change In Object Status After Copying Deployment Group Objects Status of Deployment Group Object Active Object Active Object Deleted Object Deleted Object Deployment Wizard Action Deploys the object Deploys the object Deploys the object Skips the object Status of Target Repository Object Deleted Active Active Deleted Status of Target Repository Object After Copying Active Active Deleted Deleted Note: Non-reusable objects derive status from their parent composite objects. If a parent composite object has a deleted status. verify that existing objects in the target repository are not checked out or locked. copy dependent shared folders for shortcuts in the deployment group. Or. Before you copy a deployment group. You can remove the copied objects from a static deployment group when you finish copying them into the target repository. associated non-reusable objects also have a deleted status. 258 Chapter 10: Copying Folders and Deployment Groups . For example. you may want to apply a label to the source and target objects that specifies when the source object version was deployed and when the target object version was created. For details on viewing a deployment history. You can move labels from version to version in source and target repositories.

2. The wizard might have to determine how the folders are related before establishing shortcuts. The wizard rolls back all changes. Choose to retain persisted values. Table 10-3 lists the dialog boxes and prompts that you may see when you copy a deployment group: Table 10-3. Clear Source Deployment Group Sequence Generators and Normalizers Retain Mapping Variables Dependency Information Retain Workflow Variable Persisted Values Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Copying a Deployment Group 259 . 5. Choose to retain current values for Sequence Generator and Normalizer transformations. if they exist. 4. You can choose the shared folders to associate shortcuts. To copy a deployment group: 1. Select the deployment group to copy. Select a label in the source repository to apply to the copied object versions. Advanced. displaying the folder name and target repository name. Choose to retain persisted values for mapping variables. You can override the defaults for shortcuts to local and global shared folders.Use the following steps as a guideline when you copy a deployment group. Connect to the source and target repositories. Override the default selections for deployment folders. click Cancel. Choose to remove objects from the deployment group after the wizard completes the deployment operation. The Copy Deployment Group Wizard dialog box prompts you to select a mode: ♦ ♦ Typical. and select a label in the target repository to apply to the newly created object versions. To stop the replacement. Click Next. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Select Deployment Folders Override Deployment Folder Select Compare Folders Select Labels Mode Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Prompt Choose the folders you want to deploy objects to. 3. Select the folders you want to compare. Copy dependency information for objects in mappings. The wizard uses the defaults for shortcuts to local and global shared folders. Click and drag or paste the deployment group to the target repository. The Copy Deployment Group Wizard appears. The Copy Wizard prompts you for more information based on the content of the folders and the copy mode you selected.

Choose to retain the assigned PowerCenter Server information for workflows and sessions configured to run on specific PowerCenter Servers in a server grid. Lists all dependent local and global shared folders. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Retain Workflow Logs Retain Server Settings Mode Typical/Advanced Typical/Advanced Prompt Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder. Lists all database connections in the folder. Lists all external loader connections in the folder. Lists outdated folders in the target repository that you need to copy first. the wizard skips this step.Table 10-3. Lists all application connections in the folder. click Cancel and copy all listed local shared folders before copying the folder. You can choose to accept or override the shared folder. Lists folders you can select to establish shortcuts if you choose to override the default folder selection in the Select Shared Folders dialog box. indicating the connections for which you do not have read permission. If the target repository contains less than two PowerCenter Servers. Lists local shared folders in the target repository that you need to copy first. Database Connections MQ Connections FTP Connections External Loaders Application Connections Plug-in Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Servers Typical/Advanced Local Shared Folders Typical Outdated Shared Folders Typical Select Shared Folders Advanced Override Shared Folder Advanced 260 Chapter 10: Copying Folders and Deployment Groups . To preserve shortcuts and prevent invalid mappings. To preserve shortcuts and prevent invalid mappings. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. Lists all FTP connections in the folder. Lists all MQ connections in the folder. Allows you to select a PowerCenter Server to run all nonassociated workflows. click Cancel and copy all listed local shared folders before copying the folder. indicating the connections for which you do not have read permission. indicating the connections for which you do not have read permission. indicating the connections for which you do not have read permission.

Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Compare Shared Folder Compare Results Mode Advanced Advanced Prompt Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different. Lists the results from the folder compare. Also displays objects that are older or newer than matching objects in the global shared folder. Copying a Deployment Group 261 . a message warns you that shortcuts to missing objects will be removed. The wizard takes you back to Select Shared Folders dialog box.Table 10-3. Displays objects that exist in the local shared folder but not in the global shared folder. If there are differences between the folders.

262 Chapter 10: Copying Folders and Deployment Groups .

269 Working with Dependent Objects.Chapter 11 Exporting and Importing Objects This chapter includes information on the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 264 The XML and DTD Files. 267 Exporting and Importing Multiple Objects and Object Types. 270 Working with Object Versions. 296 263 . 273 Working with Shortcuts. 280 Steps for Exporting Objects. 285 Steps for Importing Objects. 287 Troubleshooting. 274 Exporting Objects. 276 Importing Objects.

you must be connected to both repositories. but you do not want to disclose repository connection information for security reasons. Search for the old port name and replace all references to it with the new port name. you have a mapping with an unconnected Lookup transformation. You can export the mapping to an XML file and open it in a text editor. you can export repository objects to an XML file and then import repository objects from the XML file. For example. You can export objects to an XML file that you no longer need before removing them from the repository. For example. when you copy objects between folders or repositories. Copy metadata between repositories. You can copy objects between repositories that you cannot connect to from the same client. After you test a mapping in a development repository. Then import the object from the XML file into the target repository. Export the object and transfer the XML file to the target machine. pmrep. You can search for a property name and replace all occurrences of it with a different name. Workflow Manager. You might export and import objects to incrementally deploy metadata by exporting and importing part of a composite object. However. you can resolve object name conflicts. Archive metadata. you can export it to an XML file and then import it from the XML file into a production repository. You can use the following client applications to export and import repository objects: ♦ ♦ ♦ ♦ Repository Manager. You can share metadata with a third party. You can export and import only Workflow Manager objects. When you export an object from one repository and import the object into another repository. You can export and import repository objects to accomplish the following tasks: ♦ Deploy metadata into production. You can export and import only Designer objects. Share metadata. For more information on using pmrep to export and import objects. You might use pmrep to automate exporting objects on a daily or weekly basis. You want to change the name of a port in the unconnected Lookup transformation. The third party can import the mapping from the XML file and analyze the metadata. Search and replace property names in an entire repository object. Exporting and importing an object is similar to copying an object from one folder or repository to another. you do not need to be connected to both repositories. You can export and import both Designer and Workflow Manager objects. so you want to make sure you change the port name in all other expressions. Then import the mapping into the repository. when you copy an object between folders or export and import that object.Overview In the PowerCenter Client. For example. Designer. ♦ ♦ ♦ ♦ 264 Chapter 11: Exporting and Importing Objects . You can export and import both Designer and Workflow Manager objects. see “Exporting Objects (ObjectExport)” on page 432 and “Importing Objects (ObjectImport)” on page 433. you want to send a mapping to someone else for testing or analysis. Several other transformations call the lookup port through an expression. You can export the mapping to an XML file and edit the repository connection information before sending the XML file.

Working with Objects and Object Types You can export and import the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Sources Targets Transformations Mapplets Mappings Tasks Sessions Schedulers Session configurations Worklets Workflows When you export and import repository objects. ♦ ♦ ♦ Working with Different Repository Versions You can share objects with other repositories by exporting and importing objects between repositories with the same version. For more information. You can also import objects exported from a repository version PowerCenter supports upgrading. you can choose to export and import the following types of objects: ♦ Multiple object types. Dependent objects. For more information. The combination of object types you can export and import depends on the PowerCenter Client you use. you can do this when you access a query result from the Designer. Also. You can export and import an object with or without its dependent objects. Overview 265 . Using the Repository Manager or pmrep. However. Workflow Manager. For more information on exchanging metadata. see “Working with Dependent Objects” on page 270. You can export and import one or more object types. or Repository Manager. Multiple objects. see “Exporting and Importing Multiple Objects and Object Types” on page 269.You can also export and import relational sources and targets to share metadata with other business intelligence and data modeling tools. see “Exporting and Importing Multiple Objects and Object Types” on page 269.0 and later. Objects from multiple folders. You can export and import one or more objects. see “Exchanging Metadata” on page 313. you can export and import objects from one or more folders in the same repository. you can only import sessions exported from version 6. For more information.

For more information on changes the upgrade process makes on repository metadata. The permissions and privileges required to import and export objects change depending on whether you are using the Designer.When you import an object exported from an earlier repository version. you must have the proper folder permissions and user privileges. You import the transformation in the current repository version. The PowerCenter Client imports the transformation and changes it to a Custom transformation. Permissions and Privileges To export and import repository objects. see “Upgrading Repository Metadata” in the Installation and Configuration Guide. the PowerCenter Client displays an error message and does not import any object. or Repository Manager. 266 Chapter 11: Exporting and Importing Objects . the repository updates the object metadata to conform with the current repository version. The code page of the originating repository must be a subset of the destination repository code page. Exporting and Importing Objects Permissions and Privileges PowerCenter Client Designer Repository Privilege Use Designer Super User Workflow Manager Use Workflow Manager Super User Repository Manager Use Repository Manager Super User Folder Permission Read for exporting Read/Write for importing N/A Read for exporting Read/Write for importing N/A Read for exporting Read/Write for importing N/A Code Pages To ensure no data is lost when you import an object. For example. see “Globalization Overview” and “Code Pages” in the Installation and Configuration Guide. the PowerCenter Client only allows you to export and import objects between repositories with compatible code pages. For details on code page compatibility. If the two repository code pages are not compatible. you export an Advanced External Procedure transformation from an earlier repository version. Table 11-1 lists the permissions and privileges you need to export and import objects: Table 11-1. Workflow Manager.

it might not catch all invalid changes.dtd.dtd into the client installation directory. You also need to make sure the metadata in the XML file conforms to Designer and Workflow Manager rules. An XML file is valid if it complies with the constraints expressed in its associated DTD. the PowerCenter Client creates the XML file based on the structure specified in powrmart. you can only modify some attributes and elements before importing the object into a repository. the PowerCenter Client might include a CRCVALUE (Cyclic Redundancy Checking) code in one or more elements in the XML file. when you define a shortcut to an object.dtd. the XML file is invalid if the element occurs more than once or not at all. Do not modify the powrmart. the installation program copies powrmart. If you import into your repository an object that does not conform to Designer or Workflow Manager rules. For more information on reading DTD files.dtd. Although PowerCenter validates the XML file before importing repository objects from it. define the folder in which the referenced object resides as a shared folder.dtd is not in the client installation directory. VSAM source objects always contain a CRCVALUE code. see “Modifying an Exported XML File” on page 277. you might cause data inconsistencies in your repository. if powrmart. When you export a Designer object. you need to make sure that the XML file conforms to the structure of powrmart. When you export or import an object.dtd.w3.dtd file.dtd. When you export repository objects. the PowerCenter Client validates the XML file against powrmart. Therefore.dtd states that an element must occur once in an XML file. When you import repository objects.The XML and DTD Files When you export repository objects. Note: If you modify an exported XML file. If powrmart. the PowerCenter Client looks for powrmart. see “XML Concepts” in the XML User Guide. When the PowerCenter Client includes a CRCVALUE code in the exported XML file. Or. CRCVALUE Codes Informatica restricts which elements you can modify in the XML file. see the W3C specifications for XML at http:// www. For example. for more information on XML. For example. The CRCVALUE code is another attribute in an element. For information on modifying XML files. For example. the PowerCenter Client creates an XML file that contains the metadata of the exported repository objects. The XML file has an associated Document Type Definition (DTD) file called powrmart.org/. you cannot import repository objects. You can use this same file to import the repository objects into a repository. When you install PowerCenter. an exported XML file is valid if it complies with the constraints expressed in powrmart. so you can only The XML and DTD Files 267 .dtd in the client installation directory.

see “Modifying an Exported XML File” on page 277... For example.modify some attributes in a VSAM source object.. </SOURCE> CRCVALUE code The CRCVALUE attribute for the element SOURCE in Figure 11-1 is 3108520154. Note: The PowerCenter Client only includes CRCVALUE codes in the XML file when you export Designer objects. 268 Chapter 11: Exporting and Importing Objects .> .. if you modify the OWNERNAME attribute in the source object in Figure 11-1. you cannot import the object.CBL" IBMCOMP ="YES" CRCVALUE ="3108520154" OWNERNAME ="" DESCRIPTION ="" BUSINESSNAME ="" DATABASETYPE ="VSAM" . you cannot import the source into the Designer. Figure 11-1 shows part of the element for a source object with the CRCVALUE code: Figure 11-1. CRCVALUE Code in an Exported XML File <SOURCE NAME ="SALES_FILE" DBDNAME ="SALES. For details on which attributes and objects you can modify. If you modify certain attributes in an element that contains a CRCVALUE code.

You cannot export multiple mappings or mapplets.Multiple object types from multiple folders When you import objects from multiple folders.Multiple objects from one folder . you can export a reusable Email task and a reusable Session task.Multiple workflows from one folder For example. Exporting and Importing Multiple Objects and Object Types 269 . you can choose which folders to import into.Multiple objects from one folder . and Command tasks from one folder . you can export reusable transformations and reusable worklets to the same file.Multiple objects from multiple folders . . . .Multiple objects from one folder . you can choose which folders to import into using the control file. pmrep Designer Workflow Manager .Multiple objects from multiple folders .Multiple object types from multiple folders For example.Multiple worklets from one folder .Multiple object types from multiple folders When you import objects from multiple folders.Multiple object types from one folder You can import Workflow Manager objects only. or reusable transformations from one folder For example.Multiple sources. However.Multiple object types from one folder For example. the combination of object types depends on the PowerCenter Client application you use. . Session. you cannot export both sources and targets from the Navigator. Note: You can export different object types from all PowerCenter Client tools by exporting the results of an object query. . you can export multiple mappings to the same file. targets.Multiple objects from multiple folders . You cannot export multiple object types. Table 11-2 lists the multiple objects you can export and import: Table 11-2.Multiple reusable Email.Multiple object types from one folder You can import Designer objects only.Exporting and Importing Multiple Objects and Object Types You can export and import multiple objects and multiple object types at the same time. Options for Importing . Options for Exporting and Importing Multiple Objects PowerCenter Client Application Repository Manager Options for Exporting .

Table 11-3 lists the dependent objects that the PowerCenter Client includes in the XML file by default: Table 11-3. see “Working with Shortcuts” on page 274. see “Exporting and Importing Parent Objects” on page 271. Any reusable or non-reusable metadata extension associated with the object. a source definition referenced by a shortcut is a dependent object of that shortcut. Verify you register a plug-in in the destination repository before you import an object using a vendor-defined metadata extension associated with the plug-in. sessions. Dependent Objects Exported Parent Object Mapping Mapplet Source with foreign key Target with foreign key Shortcut Any repository object Session Dependent Child Objects Exported Sources. A dependent object is an object that is used by another object. Reusable and non-reusable tasks. Parent object without dependent child objects. the PowerCenter Client imports the object without the metadata extension. Worklet Workflow *The PowerCenter Client always exports metadata extensions.Working with Dependent Objects When you export an object. Scheduler and reusable and non-reusable tasks. Mapping used by the session when you export from the Repository Manager or pmrep. the PowerCenter Client exports certain dependent objects by default. and mapplets. sessions. A dependent object is a child object to the parent object that uses the dependent object. ♦ 270 Chapter 11: Exporting and Importing Objects . The PowerCenter Client exports the dependent child objects listed in Table 11-3 by default. but not the child object. If the plug-in is not registered. see “Exporting and Importing Parent Objects” on page 271. targets.* Session configuration and reusable and non-reusable tasks when you export from any client application. you can export and import any of the following combination of objects: ♦ Parent object with dependent child objects. For more information on registering plug-ins. see your PowerCenter Connect documentation. The PowerCenter Client does not export all dependent objects. For more information. The object the shortcut references. Sources and reusable transformations. reusable and non-reusable transformations. and worklets. Source definition containing the primary key. The XML file contains metadata for the parent object. For more information. The XML file contains metadata for parent and child objects. Target definition containing the primary key. For example. and worklets. When you export and import objects. For information on exporting and importing shortcuts.

When you export a mapping. You might want to export and import an object without its dependent objects if you change a workflow property. and reusable transformations when you export a mapping. and all non-reusable tasks for a worklet or workflow. Export Options Dialog Box Table 11-4 describes the options in the Export Options dialog box: Table 11-4. mapplet. the PowerCenter Client exports all reusable objects used by the parent object. or workflow. Description When you export a source or target containing a foreign key. When you export a mapping. the PowerCenter Client exports the metadata for the parent object and the dependent objects. the PowerCenter Client exports all non-reusable objects used by the parent object. Working with Dependent Objects 271 . Export non-reusable objects used by objects being exported. but you did not change any task in the workflow. Figure 11-2 shows the export options for dependent objects: Figure 11-2. Export original object referred by the shortcut when exporting shortcuts. the PowerCenter Client exports the source or target containing the primary key. the PowerCenter Client exports all sources. For example. To access the Export Options dialog box. or workflow. the PowerCenter Client exports the metadata for the object. the PowerCenter Client exports the actual object referenced by the shortcut. When you export an object without its dependent objects. the PowerCenter Client exports all non-reusable transformations for a mapping or mapplet. Options for Exporting Objects Export Option Export primary key tables when exporting sources/targets with foreign keys. worklet. such as a workflow variable. You can choose the export options in the Export Options dialog box.Exporting and Importing Parent Objects You can choose to export a parent object with or without its dependent child objects. For example. click the Advanced Options link in the Export dialog box when you export objects. targets. mapplet. worklet. Export reusable objects used by objects being exported. When you export an object with its dependent child objects. When you export a shortcut.

If the mapping does not exist or is invalid. Dependent objects do not exist in XML file. However. When you import an object. the object you export still references the dependent objects even though they do not exist in the XML file. it uses the object in the destination folder. However. but not the associated mapping. the PowerCenter Client looks for an object in the destination folder with the same name. You want to update only the link condition when you import the workflow into a different folder. When you export a session from the Workflow Manager. you create a workflow with multiple worklets. such as the sources. If the PowerCenter Client does not find an object with the same name. it does not import the object. the PowerCenter Client does not import the session. However. The PowerCenter Client uses the worklets. You can also create an XML file that contains both the session and mapping objects by using pmrep or the query results accessed from the Repository Manager to select both objects and export them. when you use the Repository Manager or pmrep. when you export a session from the Repository Manager. the PowerCenter Client exports the session and the associated mapping. the session does not need to be valid before you export it. the associated mapping must exist in the target folder and be valid. For example. the PowerCenter Client imports all dependent objects. For example. the PowerCenter Client imports the workflow metadata only. the PowerCenter Client imports all objects used by the mapping. the PowerCenter Client exports the session. To import a session. Or. You change the link condition between two tasks. sessions. and tasks that exist in the destination folder. When you import an object. you export a mapping including its dependent objects. ♦ Working with Sessions When you export a session. 272 Chapter 11: Exporting and Importing Objects . You might want to export an invalid session to send to someone else to troubleshoot. sessions. However. Then edit one of the XML files to include both objects. When you import the mapping.but does not export metadata for the dependent objects. If the PowerCenter Client finds an object with the same name. Export the workflow and do not export the reusable and non-reusable tasks. When you import an object that uses dependent objects. the results differ depending on whether or not the dependent objects exist in the XML file: ♦ Dependent objects exist in XML file. and tasks. When you import the workflow. the associated mapping must be valid. you can import the session if the XML file contains the metadata for the associated mapping. you can use the Designer to export the mapping and the Workflow Manager to export the session.

or reusing the object. the PowerCenter Client exports the latest version of the object. the PowerCenter Client exports only the latest version of the source. For example. but the PowerCenter Client exports only the latest version selected for that object. your query results contain two mappings that use different versions of the same source. Working with Object Versions 273 . the PowerCenter Client does not change the version of the existing target definition. For more information on running an object query. You can select multiple object versions to export. see “Running a Query” on page 232. the PowerCenter Client handles object versions differently depending on how you resolve the object conflict. select the objects to export and choose Tools-Export to XML File. the PowerCenter Client creates a new target definition and assigns it a version of one. the target folder contains a target called WEEKLY_ORDERS and the latest version is three. When you import an object that exists in the target folder. renaming. you can select it from a query result or object history. Note: You cannot export deleted objects from a query result or object history. When you export an object from the Navigator or workspace. For example. If you want to export an earlier version of an object.Working with Object Versions You can export one version of an object at a time. For information on versioned objects. the PowerCenter Client changes the existing target definition to version four. see “Viewing Object History” on page 208. When you reuse the target. For more information on viewing object history. and does not change the version of the existing target definition. You import a target with the same name. When you replace the target. In the View History or Query Results window. You can resolve an object conflict by replacing. If you export both mappings. When you rename the target. see “Working with Versioned Objects” on page 199.

When you import a shortcut into a global repository. the PowerCenter Client imports the actual object into the destination repository using the metadata in the XML file. The PowerCenter Client searches for the referenced object in the folder you specify to establish the shortcut. The type of shortcut the PowerCenter Client creates does not depend on the shortcut type specified in the XML file. you can choose to export the object the shortcut references. For more information on exporting the object a shortcut references. When both the shortcut and referenced object exist in the same repository. You always specify a folder for the referenced object. whether or not you also import the referenced object into that folder. The PowerCenter Client imports the shortcut object into the destination repository using the metadata in the XML file. You might want to export the referenced object if it does not exist in the destination repository.Working with Shortcuts You can export and import local and global shortcuts. The PowerCenter Client does not find the referenced object. and the referenced object exists in a global repository in the same domain. The PowerCenter Client writes a message notifying you it imported the actual object instead of the shortcut object. the PowerCenter Client creates a local shortcut. the PowerCenter Client creates a global shortcut. the import behavior is based on whether or not the PowerCenter Client finds the referenced object in the folder you specify: ♦ The PowerCenter Client finds the referenced object. 274 Chapter 11: Exporting and Importing Objects . it does not import the shortcut. you can specify a folder from the local repository or the global repository in the domain. see “Working with Dependent Objects” on page 270. you can specify a folder from the global repository only. The new shortcut points to the object in the folder you specify for the referenced object. When the XML file does not contain the metadata for the referenced object. The PowerCenter Client finds the referenced object in the folder because the object already existed in the folder. or because you imported it along with the shortcut. Shortcut Types The type of shortcut the PowerCenter Client creates in the destination repository depends on the folders you specify for the shortcut and the referenced object. When you export a shortcut. you can specify folders for the shortcut and the referenced object. When the shortcut exists in a local repository. You can import the shortcut and the referenced object concurrently. However. The PowerCenter Client creates a shortcut in the folder you specify. ♦ When you import a shortcut into a local repository. When the XML file contains the metadata for the referenced object. When you import a shortcut.

Also in the Import Wizard. and is not a shortcut. The PowerCenter Client does not find an object with the same name in the folder you specified. the default SQL used to extract data from the source defines the source as Shortcut_To_Employees. the imported object does not inherit any changes you make to the original object in the source repository. You use the Designer to import the shortcut into a different repository. When you use the source definition in a mapping. However. The XML file defines the metadata for the object. For example. you must rename the source definition (Employees) or enter a SQL override for the source qualifier connected to the source definition (renaming the source table Employees) for the PowerCenter Server to extract source data.Importing Shortcuts to Sources When the PowerCenter Client imports the object instead of the shortcut. The Designer creates a new source definition in the destination folder named Shortcut_To_Employees. You can use the imported object as you would the original object. you choose a folder in the destination repository to specify the location of an existing referenced object. so it imports the actual object instead. Working with Shortcuts 275 . if the object is a source definition. If the source table in the source database is named Employees. In the Import Wizard. you export a shortcut named Shortcut_To_Employees and you also export the referenced object. you might need to rename the source definition. you choose to import the shortcut. This source definition is a copy of the original object. the folder does not contain an object with the same name as the referenced object specified in the XML file. but you do not import the referenced object. However.

Target1 from the Sales folder . Source1 in the Items folder Mapping1 in the Items folder Target1 in the Sales folder The Designer behavior depends on the other objects you export: Exported Objects . pmrep. ♦ However. When you export the latest version of an object. For example. when you export shortcuts from the query results accessed from the Designer. or the query results accessed from the Repository Manager. including any change you made to it since you last saved it to the repository. from the same folder that contains the referenced object. Mapping1.Shortcut_to_Source1 from the Orders folder . The XML file complies with powrmart. the PowerCenter Client exports either the version of the object saved in the repository or the version of the object you have open in the Designer or Workflow Manager: ♦ Version saved in the repository. When you export an object from the Repository Manager. After you export objects. you can modify the XML file. Source1. The Designer exports the version of Source1 you have open in the Designer because you export an object. Workflow Manager. Therefore. including changes you made to them since you last saved the repository.Shortcut_to_Source1 from the Orders folder .dtd. Version you have open in the Designer or Workflow Manager. Source1. see “Modifying an Exported XML File” on page 277. The query result contains the following objects: ♦ ♦ ♦ ♦ Shortcut_to_Source1 in the Orders folder. you run an object query from the Designer. the PowerCenter Client exports the latest version of the object. the Designer exports either the version of the referenced object you have open in the Designer or the version of referenced object saved in the repository. The shortcut references Source1 in the Items folder.Exporting Objects When you export an object. When you export an object from the Designer.Mapping1 from the Items folder Designer Export Behavior The Designer exports the saved version of Source1 because you do not export any object from the same folder that contains the referenced object. the PowerCenter Client exports the version of the object saved in the repository. For more information. the Designer exports the latest versions of all objects in the Items folder. or query results accessed from the Designer or Workflow Manager. the PowerCenter Client writes the definition of the object to an XML file. depending on the other objects you export. 276 Chapter 11: Exporting and Importing Objects .

The Modifiable Attributes column lists the attributes Exporting Objects 277 . do not associate a Source Qualifier transformation with a VSAM source. if powrmart. and then import the mapping with the new values. You cannot modify attributes in an element containing a CRCVALUE unless the attribute is listed in Table 11-5 on page 278. you can modify the XML attributes before importing the object into a repository. suppose you have inconsistent column names across a mapping.dtd says that an element must include a specified child element. You can export the mapping into an XML file. unless the attributes are listed in Table 11-5 on page 278. You can modify the BUSINESSNAME and DESCRIPTION attributes in any element. You want to globally search and replace Cust_ID and Customers_ID with Customer_ID. You can modify all attributes listed in Table 11-5 on page 278. For example.dtd. regardless of CRCVALUE codes. Table 11-5 on page 278 lists the repository objects you can modify. For example. However. Informatica restricts the elements and attributes you can modify in the XML file. Modifying an XML file is an easy way to change the metadata for a repository object. modify the values in the XML file.dtd.Modifying an Exported XML File After exporting an object. For example. Do not modify powrmart. You cannot modify attributes in an element if its parent element contains a CRCVALUE code. Make sure the structure of the XML file complies with the constraints in powrmart. Use the following rules when you modify XML files: ♦ Make sure you define metadata that you could create in the Designer or Workflow Manager. make sure you include the child element. ♦ ♦ ♦ ♦ ♦ ♦ Modifiable Objects You can modify some attributes and elements in an XML file.

The Create New column indicates which objects you can define directly in the XML file and then import.you can modify for an exported object and then import. Modifiable Repository Objects Repository Object Source Type Relational Flat File VSAM MQ XML PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Null source Target Relational SAP BW XML MQ TIBCO Null target Reusable Transformation Mapping All Relational Flat File VSAM MQ XML PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Modifiable Attributes All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All All All All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All Create New Yes Yes No No No No No No Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes No No No No No No Yes Yes 278 Chapter 11: Exporting and Importing Objects . Table 11-5.

Table 11-5. Modifiable Repository Objects Repository Object Mapplet Type Relational Flat File PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Session Task Worklet Workflow Reusable Non-reusable Reusable Non-reusable Reusable Non-reusable N/A Modifiable Attributes All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All All All All All All Create New Yes Yes No No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Exporting Objects 279 .

Resolve object conflicts. Parses the XML file. replace. You can choose all or some objects listed in the XML file. ♦ ♦ ♦ Validating XML Files Against the DTD You can only import objects from a valid XML file. When you import an object into a folder that contains an object with the same name. Validates the XML file against powrmart. The Import Wizard allows you to perform the following actions: ♦ ♦ Choose the XML file. and only Workflow Manager objects when you use the Workflow Manager. The XML file must comply with powrmart. For more information on resolving object conflicts. or Repository Manager. The PowerCenter Client validates the XML file against the DTD and parses the XML file before importing. Choose an existing label or create a new one. Choose which objects to import. you can apply a label to them. the PowerCenter Client displays an error message and does not import the objects. When you import an object in the Designer. If the XML file contains both Designer and Workflow Manager objects. Match folders. the Import Wizard only shows Designer objects when you use the Designer. You can import all object types using the Repository Manager. You can enter check in comments in the Import Wizard. When you import an object. see “Importing Objects (ObjectImport)” on page 433. 2. the PowerCenter Client performs the following tasks: 1. you can check in the objects after you import them. Validates the objects in the XML file. The DTD file. When you import using pmrep. see “Resolving Object Conflicts” on page 281. you can match folders listed in the XML file with folders in the destination repository. 3.dtd. For information on using pmrep to import objects.dtd. powrmart. the Import Wizard appears. When you use the Repository Manager to import objects into a versioned repository. 280 Chapter 11: Exporting and Importing Objects . see “The XML and DTD Files” on page 267. you use a control file to specify the same import options in the Import Wizard. You can import objects that you exported from the same repository or a different repository.dtd. If you check in the objects. you can choose to rename. or reuse the object. Creates the objects in the repository.Importing Objects You can import objects from a valid XML file. 4. When you use the Repository Manager to import. Workflow Manager. For details. is located in the PowerCenter Client directory. If the XML file is not valid. Check in the objects and apply a label.

For more information on the Import Wizard. Create rules on the Specify Rules for Conflict Resolutions page of the Import Wizard. the PowerCenter Client validates objects with CRCVALUE codes to ensure that certain elements and attributes of Designer objects in the XML file have not been modified. Importing Objects 281 . see “Steps for Importing Objects” on page 287. For details on CRCVALUE codes. When you create an object resolution rule. Resolving General Object Conflicts You can resolve some object conflicts by creating rules that apply to a set of objects. You can choose to resolve object conflicts in the following ways: ♦ ♦ Create general object resolution rules. Resolve specific object conflicts. see “The XML and DTD Files” on page 267. Resolving Object Conflicts When you import objects. a mapplet cannot contain a target definition. The PowerCenter Client validates each object in the XML file to ensure that it conforms to the PowerCenter specifications for that object. sometimes an object in the XML file has the same name as an object in the destination folder. the PowerCenter Client resolves object conflicts for objects to which the rule applies.Validating Objects You can only import valid objects into the repository. For example. The PowerCenter Client does not import objects with CRCVALUE codes that have been modified nor objects that do not conform to PowerCenter specifications. The CRCVALUE code determines whether or not you can modify certain elements and attributes. In addition.

Choose how to resolve object conflicts. . Applies to all objects you import. the PowerCenter Client applies the uppermost rule only. You can create multiple rules.All objects. You can select this option when you import objects into a versioned repository. Applies to all objects with the label you choose. Applies to objects of the type you choose. Table 11-6 describes the different columns you define for each rule: Table 11-6. 282 Chapter 11: Exporting and Importing Objects .Objects with label. Resolving General Conflicts During Import Column Select Criteria Description Choose the set of objects the rule applies to. . You can select this option when you import objects into a versioned repository.Resolve General Object Conflicts Apply rule to these objects. If multiple rules apply to one object.Objects of type.Objects in query. Applies to all objects that result from the object query you choose. Import Wizard . Use the buttons in the Import Wizard to move the rules up and down. .Figure 11-3 shows where you can resolve general object conflicts in the Import Wizard: Figure 11-3. You can choose the following sets of objects: . The PowerCenter Client applies the rules to objects in order.

. Creates a new object in the destination folder with a new name. For more information on the Conflict Resolution Wizard. When you choose Rename. you can define the specific conflict resolutions in the Conflict Resolution Wizard. Allows you to choose a resolution on an object by object basis. Replaces the existing object in the destination folder. you can resolve specific object conflicts using the Import Wizard. choose the label name in this column. For example.Resolve Specific Object Conflicts Importing Objects 283 . Resolving General Conflicts During Import Column Select Value Select Resolution Description Choose a value that modifies the first column. Import Wizard . you can specify a different name in the Conflict Resolution Wizard. .Table 11-6. For more information on the Conflict Resolution Wizard.Prompt User.Replace. Resolving Specific Object Conflicts Some object conflicts may still exist after you define rules to resolve conflicts. Choose how to resolve the object conflicts. After you create general object resolution rules.Reuse. When you choose Prompt User.Rename. You can resolve specific object conflicts in the Import Wizard. . see “Resolving Specific Object Conflicts” on page 283. if you select Objects with label in the first column. You can resolve conflicts using the following methods: . Uses the existing object in the destination folder. see “Resolving Specific Object Conflicts” on page 283. Figure 11-4 shows where you can resolve specific object conflicts in the Import Wizard: Figure 11-4.

It also displays the object resolution status for objects in each folder: ♦ Unresolved. You must resolve all object conflicts before you can import objects. No object in this folder conflicts with objects in the target folder.The Import Wizard displays all folders listed in the XML file. However. it opens the Conflict Resolution Wizard. Figure 11-5 shows the Conflict Resolution Wizard: Figure 11-5. After you resolve object conflicts in the Conflict Resolution Wizard. 284 Chapter 11: Exporting and Importing Objects . Click Resolve to resolve the object conflicts. you return to the Import Wizard. Some objects in this folder conflict with objects in the target folder. The user interface is similar and you resolve the same type of object conflicts in both. The Import Wizard is ready to import these objects. Conflict Resolution Wizard The Conflict Resolution Wizard is similar to the Copy Wizard. you can view or edit the object conflict resolutions by clicking View/Edit. ♦ When the Import Wizard detects unresolved conflicts for objects in a folder. For information on resolving conflicts in the Copy Wizard. Resolved. see “Copying Objects” on page 297.

see “Working with Dependent Objects” on page 270. 2. Choose Repository-Export Objects. To export objects from the query result or object history. or Repository Manager: 1. Repository Manager. or object history. navigate to the directory where you want to save the XML file. choose which dependent objects to export and click OK. For more information. To export an object from the Designer. 5. In the Navigator or workspace. 4.Steps for Exporting Objects You can export objects from the repository using the Designer. 6. Workflow Manager. query result. In the Export Options dialog box. For information on using pmrep to export objects. click Advanced Options. Enter a name for the XML file and click Save. select the objects to export. select the objects to export and choose Tools-Export to XML File. To choose which dependent objects to export. see “Exporting Objects (ObjectExport)” on page 432. In the Export dialog box. Workflow Manager. Choose which dependent objects to export. Steps for Exporting Objects 285 . Open the folder that contains the objects you want to export. 3.

The PowerCenter Client exports the objects to an XML file. and displays export status in the Exported Objects dialog box: View the XML file the PowerCenter Client creates. Click Close in the Exported Objects dialog box. 7. 286 Chapter 11: Exporting and Importing Objects . You can click View File to view the XML file the PowerCenter Client creates.

You can compare objects when importing objects with the Import Wizard. To import an object: 1. In the Import Wizard. see “Importing Objects (ObjectImport)” on page 433. click Browse to locate the XML file. Select the XML file and click OK. or Repository Manager. Steps for Importing Objects 287 .Steps for Importing Objects You can import objects into the repository using the Designer. Navigate to the directory where the XML file is located. Open the folder into which you want to import an object. 2. For information on using pmrep to import objects. 3. Workflow Manager. The Import Wizard opens to guide you through the process of importing the objects into the target folder. Choose Repository-Import Objects.

5. the Import Wizard imports all sources listed under that database definition node. When you import objects using the Repository Manager. After you add an object to the list of objects to import. 288 Chapter 11: Exporting and Importing Objects . Or. you can select objects from multiple folders from one repository. when you click a particular database definition node.4. the Import Wizard adds all objects listed under that node. Select a folder or repository in the Folders field. You can filter which objects to view in the Objects in File pane. When you select a node in the Objects in File pane and click Add. Click Next. Note: When you import objects using the Designer or Workflow Manager. To remove an object from the Objects to Import pane. when you select Sources and click Add. the Import Wizard displays a check mark on the icon for objects in the Objects in File pane. For example. you can select objects from one folder. select the object and click Remove. You can right-click an object and choose Properties to view the properties associated with an object. Select the objects to import and click Add. the Import Wizard adds all sources for that folder.

Tip: You can create a new folder in the destination repository by clicking Create Folder. You can match folders listed in the XML file to folders in the destination repository. Click Next. 7. You must select a different folder for each folder listed in the Import Wizard. or when you import a shortcut object in the Designer. The Folder Selection dialog box appears. 8. Select a folder in the destination repository and click OK.6. Open Button This step of the Import Wizard appears when you import objects using the Repository Manager. Specify the folder properties in the Create Folder dialog box. Click the Open button for a folder listed in the Import Wizard. Steps for Importing Objects 289 .

To check in all objects after importing them. In the Label Browser dialog box. select Check In and enter comments in the comment field. 290 Chapter 11: Exporting and Importing Objects . This step of the Import Wizard appears when you use the Repository Manager to import objects into a versioned repository. select Apply Label and click Select Label. You can check in the objects and apply labels to the them after importing.9. 11. You can only apply a label to the objects if you choose to check them in. To apply a label to all objects you import. choose the label and click OK. 10. Click Next.

Steps for Importing Objects 291 .12. You can create rules to resolve general object conflicts. or all objects. This step of the Import Wizard appears when you import objects using the Repository Manager. To create a new rule. see “Resolving Object Conflicts” on page 281. Click Next. Click Next. objects listed in an object query. 14. For more information on resolving object conflicts. Choose to which objects to apply the rule and select a resolution. 13. click New Rule. You can apply rules to objects with a certain label. objects of the same type.

Use the Conflict Resolution Wizard to resolve specific object conflicts. 292 Chapter 11: Exporting and Importing Objects . see “Copying Objects” on page 297. The Diff Tool window appears. The Conflict Resolution Wizard is similar to the Copy Wizard. Click Compare Conflict to compare conflicting objects in the XML file and target repository. 15. For information on resolving conflicts in the Copy Wizard. You can save the comparison as a text or HTML file.The Import Wizard opens the Conflict Resolution Wizard for objects in one of the folders listed in the XML file.

Click Next to proceed through the Conflict Resolution Wizard.If the objects in the XML file exist in the target repository. 17. the Targets window appears instead of the Diff Tool window. Steps for Importing Objects 293 . 16. Click Close when you resolve all the conflicts for this folder. Resolve object conflicts as they appear in the Conflict Resolution Wizard.

You can click View/Edit to view or edit the object conflicts for the objects in that folder. 294 Chapter 11: Exporting and Importing Objects .The Import Wizard opens the Conflict Resolution Wizard for objects in any other folder listed in the XML file. Click Resolve in the Action column for that folder to open the Conflict Resolution Wizard and resolve the object conflicts. Note: If you cancel the Conflict Resolution Wizard for a folder. the Import Wizard displays the status of that folder as unresolved. the Import Wizard proceeds with the import process. When you resolve conflicts for all objects in all folders.

The PowerCenter Client imports the objects into the destination repository.18. Errors and warnings are designated by colored text. Steps for Importing Objects 295 . and displays the progress of the import process. Click Done. 19. Click Import in the Import Wizard to import the objects into the repository. The Output window displays the results of the import process.

I imported a mapping from an XML file I modified. You must be able to create the object you define in the Designer or Workflow Manager. make sure the source is not a VSAM source. it imports the object the shortcut references using the metadata in the XML file. When it cannot connect to the source repository. When I tried to import a shortcut to an object. but the Designer marked it invalid. the Designer must be able to connect to the source repository to re-establish the shortcut. if you edit the metadata for a mapplet. Make sure that the metadata you define in the XML file is valid. 296 Chapter 11: Exporting and Importing Objects . The Designer marks mapplets with VSAM sources as invalid.Troubleshooting The solutions to the following situations might help you with exporting and importing objects. For example. To import a shortcut to an object into a repository. the Designer imported the actual object instead of the shortcut.

310 297 . 300 Steps for Copying Objects. 298 Resolving Copy Conflicts. 302 Viewing Object Dependencies. 306 Copying Designer Objects.Chapter 12 Copying Objects This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ Overview. 305 Copying Workflow Manager Objects.

mappings. Next Conflict/ Option View Object Dependencies Overview Area 298 Chapter 12: Copying Objects . worklets. you must first open the target folder. or skip copying the object. targets. The Copy Wizard Copy From/ Copy To Conflict Message Edit name. or to a different repository. a description of the conflict displays in the Conflict Message section of the screen. For a duplicate object you can rename. The Copy Wizard displays possible resolutions in the Resolution area of the screen. reuse. tasks. Designer. sources. For example. replace. You can copy repository objects such as workflows.Overview The Workflow Manager. If you want to copy an object to another folder. The Copy Wizard checks for conflicts in the target folder and provides choices to resolve the conflicts. mapplets. Figure 12-1 shows the Copy Wizard: Figure 12-1. to a different folder. Compare Conflict Link Apply resolution to other conflicts. You can also copy segments of workflows or mappings. if an item exists in the target folder. You can copy objects within the same folder. and transformations. and Repository Manager provide a Copy Wizard that allows you to copy repository objects. sessions.

Table 12-1 describes the areas of the Copy Wizard: Table 12-1. Displays object dependencies for the current object. For more information. Enables you to edit the object name if you choose to rename the object. and a green icon next to each object without a conflict. and action taken to resolve the conflict. existing conflicts.It displays a red icon next to each object with a conflict. if any. target instance name. Displays the elected resolution or a list of choices for resolution. After you choose a resolution. Copy Wizard Areas Area Copy From/Copy To Overview Area Description Displays the original repository and folder name and the target repository and folder name. For more information. Identifies the current conflict and the name of the object with the conflict. such as applying default connections or retaining server connections during the copy. original instance name. Choices might be different. Applies the resolution to all unresolved conflicts or just the conflicts for the same object type. depending on the conflict. Conflict Message Resolution Edit ApplyThisResolution to Other Conflicts Compare Conflict Next Conflict/Option View Object Dependencies You can configure display settings and functions of the Copy Wizard by choosing ToolsOptions in the Designer or Workflow Manager. Displays the items to copy. Compares duplicate objects in the target folder to the objects you are copying. Overview 299 . see “Comparing Repository Objects” on page 45. see “Viewing Object Dependencies” on page 305. the message describes the resolution. Allows you to choose additional options for session and workflow resolutions. Next Conflict/Option displays only with session or workflow conflicts that you resolve by renaming or replacing the target.

When an object with the same name exists in the target folder. you can compare them to the objects you are copying to determine the differences. or mapping in the target folder it displays the Browse button. When an object with the same name exists in the target folder. Replace the existing object in the target folder. When a reusable object exists in the target folder. When the Copy Wizard cannot find a server. You must select a valid object in the target folder for the copy process to succeed. Table 12-2 describes the Copy Wizard resolutions: Table 12-2. see “Comparing Repository Objects” on page 45. Availability When the Copy Wizard cannot find a connection object in the target repository. For more information about comparing repository objects. or mapping. Click the Compare Conflict link on the Copy Wizard to display source and target views of the objects. 300 Chapter 12: Copying Objects . The Copy Wizard provides you with the resolutions depending on the type of conflict. If the target folder has duplicate objects. connection. Copy Wizard Resolutions Resolution Name Copy Browse Description Copy a connection object. Rename Replace Reuse Skip Use the existing object in the target folder. connection. Change the object name when copying it to the target folder. it prompts you to resolve the conflict before continuing the copy process.Resolving Copy Conflicts When the Copy Wizard encounters a conflict. When copying to another folder in the same repository or another folder in a different repository and an object with the same name exists in the target folder. Skips copying the object. Click Browse to choose a server.

click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type. To apply the resolution to more objects. Resolving Copy Conflicts 301 .Figure 12-2 shows the conflict that occurs when you try to copy an object to a folder that already contains an object of the same name. Copy Wizard Resolutions The wizard prompts you to select a resolution for each unresolved object in your copy. Optionally. or to all conflicts in your copy. Figure 12-2. you can apply the resolution to all unresolved objects of the same type. The selected resolution reuses the object.

5. 4. and mappings display under the Mappings node. To copy an object using the Copy Wizard: 1. Open the target folder. the sessions display under the Sessions node. Figure 12-3 shows the first of two unresolved mapping conflicts to resolve. For example. The Copy Wizard displays objects by type. Click Next if you do not encounter a conflict. In the Navigator. Drag or copy the object into the target folder. The 302 Chapter 12: Copying Objects . choose a resolution from the Resolution options. If you encounter a conflict. select the object you want to copy. The Copy Wizard displays a red icon on objects with conflicts. 3.Steps for Copying Objects Use the following procedure to copy an object using the Copy Wizard. 2. To cancel the copy operation. Click Yes on the Copy Confirmation prompt. The Copy Wizard appears. click the Cancel button or press the Esc key. It displays conflicts one object type at a time. For example.

Copy Wizard Mapping Conflicts Copy Conflict 6. Steps for Copying Objects 303 . For example. Next Conflict/Option displays when you have session and workflow conflicts. If you work with session or workflow conflicts. use Next Conflict/Option if you want to apply default connections in the target during the copy. Figure 12-3. Repeat steps 5-6 until you resolve all conflicts.resolution option requires you to browse for an appropriate mapping. Figure 12-1 on page 298 shows the Next Conflict/Option button. Click Browse to select a mapping. and you choose to Rename or Replace the target objects. you can click Next Conflict/Option to configure additional options for sessions or workflows with conflicts. 7. Click Next to view the next conflict.

The Copy Summary information displays: 8. 304 Chapter 12: Copying Objects . Click Finish to complete the copy process.

The Dependency dialog box displays the objects that use a selected object.>> To view dependencies for an object: 1. Select the object from the Overview area of the Copy Wizard. the Copy Wizard copies all dependent objects. the View Object Dependencies dialog box displays the following message: <<No dependencies found for this object. 2. The objects display upward in a hierarchy. Object You Selected In the Overview Area Dependent Objects Viewing Object Dependencies 305 . The Dependency dialog box appears. if you view the object dependencies of a connection object when you copy a workflow. if you are going to copy a session and an associated connection object in a workflow. you can select the connection object in the Copy Wizard and see which sessions in the workflow use the connection.Viewing Object Dependencies When you copy an object. Click the View Object Dependencies button. While you set up a copy. For example. you might want to view the objects or instances that depend on the object you are copying. the Dependency dialog box shows the session that uses the source object and the workflow that uses the session. If there are no object dependencies. For example.

The server connection for this session does not exist in the target. Session conflicts. see “Workflow Manager Tasks” on page 511. When you copy a workflow or worklet. or workflow component with the same name exists in the target folder. Server connections from the original workflow do not exist for the target. To copy these objects.Copying Workflow Manager Objects The Workflow Manager allows you to copy workflows. you must first copy a mapping to the target folder in the Designer before you can copy the session. Cannot find server connection. you can select a new mapping or connection. see “Resolving Copy Conflicts” on page 300. you may need to choose the connections and mappings after you copy the session. If the target folder has no mappings. If you rename or replace the session you can use default mappings and connections. When you copy a session. the Copy Wizard copies all of the worklets. you can select a connection or skip the conflict and choose a server connection after you copy the workflow. ♦ 306 Chapter 12: Copying Objects . If a server connection does not exist. Note: The Workflow Manager provides an Import Wizard that allows you to import objects from an XML file. This includes the associated mapping and the database connection. you might encounter the following copy conflicts: ♦ Duplicate name. you must resolve all conflicts that occur in the target folder. A workflow. sessions. and sessions using the Copy Wizard. You cannot copy server connections. worklet. you might encounter the following copy conflicts: ♦ ♦ Duplicate name. Copying Workflows and Worklets When you copy a workflow or a worklet. For details on resolving conflicts. ♦ Copying Sessions When you copy a Session task. worklets. When you copy a workflow. workflow segments. If the mapping or connection does not exist. A session with the same name exists in the target folder. You can also use the Copy Wizard to copy segments of a workflow. You can rename the existing session. the Copy Wizard looks for the database connections and associated mappings in the target folder. reuse the session in the target folder or replace it. For more information about the Import Wizard. see “Importing Objects” on page 280. the Copy Wizard checks session components for possible conflicts. Otherwise. The Import Wizard also provides options to resolve conflicts. For information on the privileges and permissions to copy Workflow Manager objects. and tasks included in the original workflow or worklet. Cannot find server connection.

the Copy Wizard either copies the variables to the target folder or retains the saved variable values already in the folder. Mapping Variables When you copy a session that uses mapping variable values. If the target folder does not have any mapping in it. you can do one of the following: ♦ ♦ ♦ Select any connection of the same type in the target folder. If the mapping does not exist. the associated sessions become invalid. The associated mapping is not in the target folder. A database connection object does not exist in the target repository. To avoid this problem you can copy the mapping to the target folder in the Designer before copying the session. You can select an available mapping in the target folder. If you override the lookup or stored procedure database connection in the session properties. Copying Workflow Manager Objects 307 . If you have no mappings in the target. you can choose a different mapping from the target folder. Otherwise it uses the connection name in the session properties. the Copy Wizard verifies that the associated mapping exists in the target folder. the Copy Wizard prompts you to either copy the connection information or choose another connection. Note: You cannot copy server connections when you copy workflows. the Copy Wizard prompts you to create one: There are no mappings in this folder. even if the connection does not exist in the target folder. Skip the connection conflict. If a connection of the same name does not exist in the target.♦ Cannot find mapping. Copy the connection to the target repository. you must cancel the session copy. Cannot find database connections. After you copy the session. You must cancel the copy process to create a mapping. ♦ Mapping Conflicts When you copy a session. you must verify that the lookup or stored procedure database connection exists in the target folder to validate the session. Select connections from the target repository. When you cancel. Database Connection Conflicts When you copy a session to a different repository. the Copy Wizard does not copy any object. click Browse. To find available mappings in the target folder. the session uses the same database connection name and type as it has in the source folder. If you replace a mapping with an invalid mapping. Please create a mapping in the Mapping Designer.

You can copy reusable and non-reusable objects in segments. The Workflow Manager retains the saved variable values in the target folder if you replace a session that already has saved variable values. and any condition in the links. You paste a segment to another folder. If you replace the task instance. The Copy Wizard creates a copy of the task and assigns it a new name. You copy a session into a folder to replace an existing session. ♦ Cannot find mapping. Note: You can copy individual non-reusable tasks by selecting the task and following the instructions for copying segments. you can resolve this conflict by replacing the task instance or renaming the task instance with a unique name. but the target folder does not contain the associated database connection. A segment consists of one or more tasks. You can copy segments into workflows and worklets within the same folder. choose to create a copy of the instance instead of replace it. You must select a new mapping. When you overwrite the segment. If you copy to a folder in a different repository. You can also paste segments of workflows or worklets into an empty Workflow or Worklet Designer workspace. select any ♦ 308 Chapter 12: Copying Objects . you might encounter the following copy conflicts: ♦ Duplicate name. Cannot find database connection. You paste a segment into another workflow or worklet containing a task instance with the same name as the one you are copying. and a connection of the same name does not exist. it creates a new copy of the object you are pasting and renames it so that it does not overwrite any objects. The new session contains a mapping that has an associated mapping variable from the copied session. To avoid overwriting an object instance in a target workflow or worklet. Copying Workflow Segments You can copy segments of workflows and worklets when you want to reuse a portion of workflow logic. within another folder. For example. you cannot overwrite the original task with the copied task. When you copy a segment. Each time the Copy Wizard locates a duplicate instance in the target workflow or worklet. You paste a segment to another folder without the associated mappings in the target folder. the Copy Wizard overwrites the task instance in the target workspace. For reusable objects. If the target folder does not contain a mapping. If you copy and paste a task within the same workflow or worklet. or within a folder in a different repository. if you copy a segment from Workflow_A containing s_Session1 into Workflow_B containing a session named s_Session1. The replaced session in the target folder does not have saved variable values. the links between the tasks. you must copy a mapping to the target folder before you can copy the segment. the conditions in the copied link overwrite the link conditions in the target workflow or worklet.The Workflow Manager copies the variable values to the target folder under the following conditions: ♦ ♦ You copy a session into a folder to create a new session.

Open the workflow or worklet. Choose Edit-Paste or press Ctrl+V. To copy a segment from a workflow or worklet: 1. You can also copy the object into the Workflow or Worklet Designer workspace. copy the connection to the target repository. or skip the connection conflict. Open the workflow or worklet into which you want to paste the segment.connection of the same type in the target folder. The Copy Wizard opens and notifies you if it finds copy conflicts. ♦ Segment contains user-defined workflow variable. 5. User-defined workflow variables are only valid in the workflow or worklet in which they were created. expressions using the variable become invalid. Select a segment by highlighting each task you want to copy. 3. Copying Workflow Manager Objects 309 . 4. 2. You can also select segments by dragging the pointer in a rectangle around objects in the workspace. If you paste a segment containing a user-defined workflow or worklet variable. Copy the segment to the clipboard. You can select multiple reusable or non-reusable objects.

A segment can include a source. you can choose to copy the associated installed ABAP program. see “Resolving Copy Conflicts” on page 300. you might have the following copy conflicts or options: ♦ Duplicate item name. Choose the Copy SAP Program Information checkbox. target. Copy a source included in a primary key-foreign key relationship that is not included in the mapping. or to a different repository. When you copy objects you might have duplicate objects in the target folder. For details on resolving conflicts. select this option to retain the current value of the generated key sequence. To copy these objects. select and copy the segments from the Mapping Designer and paste them into a target mapping or an empty mapping or mapplet workspace. You can copy any of the Designer objects such as sources. If you copy Sequence Generator transformations. transformations. When copying a Normalizer transformation. mappings. You might have some duplicate components in the target folder. When you copy Designer objects. To copy mapping segments. 310 Chapter 12: Copying Objects . Copy SAP Program information. you must resolve all conflicts that occur in the target folder. see “Resolving Copy Conflicts” on page 300. If you copy an SAP R/3 mapping. When you copy a mapping with a source object that has a primary keyforeign key relationship with another object not included in the mapping. or you select resolutions all at once. the wizard attempts to copy all the components of the mapping to the target. This option displays only when you copy Sequence Generator or Normalizer transformations. For information on the privileges and permissions to copy designer objects. see “Designer Tasks” on page 510.Copying Designer Objects You can copy Designer objects within the same folder. transformation. and dimensions. For more information on resolving conflicts. select the Sequence Generator and Normalizer Current Value to retain the current value of the sequence number. When you copy a mapping or mapplet. the Copy Wizard asks you if you want to copy the referenced object. or shortcut. to a different folder. For more information about ABAP programs see the PowerCenter Connect for SAP R/3 documentation. You can copy segments across folders or repositories. ♦ ♦ ♦ Copying Mapping and Mapplets Segments You can copy segments of mappings and mapplets when you want to reuse a portion of the mapping logic. targets. Retain current values in reusable Sequence Generator or Normalizer transformations. mapplets. mapplet. This option displays when you copy an SAP R/3 mapping across repositories. You must open the target folder before you can copy to it. A segment consists of one or more objects in a mapping or mapplet. You can resolve these conflicts individually.

If you are creating duplicate objects in a folder. You can select multiple objects. 2. You can also select segments by dragging the pointer in a rectangle around objects in the workplace. 5. You can also paste the segment into an empty workspace. the Designer assigns a unique name to the new object. Choose Edit-Paste or press Ctrl+V. 3. Select a segment by highlighting each object you want to copy. Open a mapping or mapplet. Copying Designer Objects 311 . 4.To copy a segment of a mapping or mapplet: 1. Copy the segment to the clipboard by pressing Ctrl+C or choosing Edit-Copy. Open a target mapping or mapplet.

312 Chapter 12: Copying Objects .

316 Steps for Importing Metadata. 314 Steps for Exporting Metadata.Chapter 13 Exchanging Metadata This chapter includes the following topics: ♦ ♦ ♦ Overview. 319 313 .

To exchange metadata between PowerCenter and another tool. ♦ To export metadata. For information on resolving conflicts in the Copy Wizard. For more information on exporting metadata. When the Metadata Import Wizard detects object conflicts during import. For more information on importing metadata. The Conflict Resolution Wizard is similar to the Copy Wizard. Use the BI or data modeling tool as the source tool. export metadata to a file recognized by the target tool.dtd to exchange metadata with PowerCenter. but you must be able to export or import XML files that conform to powrmart. In the source BI or data modeling tool. select a folder and choose Repository-Import Metadata. export metadata to a file recognized by the source tool. For more information on exporting and importing objects. see “Steps for Importing Metadata” on page 319. MIMB uses the specifications in powrmart.dtd. select an object and choose Repository-Export Metadata. You do not need a PowerCenter Metadata Exchange option license key. and then use the target BI or data modeling tool to import metadata from the file. and then use PowerCenter to import metadata from the file. 314 Chapter 13: Exchanging Metadata . such as Business Objects Designer. you can use one of the follow methods: ♦ Use PowerCenter as the source tool. see “Exporting and Importing Objects” on page 263. it opens the Conflict Resolution Wizard. The wizard prompts you for different options. PowerCenter uses the Meta Integration® Model Bridge (MIMB) from Meta Integration Technology. To import metadata. see “Copying Objects” on page 297. see “Steps for Exporting Metadata” on page 316. PowerCenter can be the source or target tool. The Repository Manager uses a wizard to guide you through the export or import process. Inc. To exchange metadata you export the metadata from the source tool and import the metadata into the target tool. depending on the BI or data modeling tool. You can export to and import from the following BI and data modeling tools: ♦ ♦ ♦ ♦ ♦ ♦ Business Objects Designer Cognos ReportNet Framework Manager IBM DB2 Cube Views IBM Rational Rose Microsoft Visio Database Oracle Warehouse Builder Cognos Impromptu You can import from the following BI tool: ♦ Note: You can also exchange metadata with BI and data modeling tools by using the Export Objects and Import Objects menu commands. In PowerCenter.Overview You can use the Repository Manager to share source and target metadata with other business intelligence (BI) and data modeling tools. to exchange metadata with other BI and data modeling tools.

You cannot export shortcuts. the Repository Agent also exports the source or target containing the corresponding primary key.Rules and Guidelines Consider the following rules and guidelines when you exchange metadata with BI or data modeling tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ You can export and import relational source and target definitions. see “Working with PowerCenter Licenses” on page 119. You cannot export cubes and dimensions. You can export multiple source definitions or multiple target definitions at a time. you can export targets to some tools as dimensions. You cannot export source and target definitions at the same time. You must have a Metadata Exchange option license key to exchange metadata for a specific tool. For more information on licenses. You can import multiple source and target definitions at a time. When you export a source or target with a foreign key. Overview 315 . However.

To export metadata: 1. You can click More Info to read about the tool requirements.Steps for Exporting Metadata Use the following procedure to export metadata from PowerCenter to a file recognized by the target BI or data modeling tool. In the Repository Manager Navigator. Choose the target tool you want to export the object to. and choose Repository-Export Metadata. Choose a path and file name. 2. 316 Chapter 13: Exchanging Metadata . select the object or objects you want to export. The Metadata Export Wizard appears.

5. Click Next. Enter the options specific for the tool to which you are exporting.3. Choose a path and file name for the target file. Steps for Exporting Metadata 317 . and click Next. 4. The consistency check verifies the object meets the metadata requirements for the target tool. 6. Choose the level of consistency checking you want MIMB to perform. The Metadata Export Wizard displays options specific to the tool you select.

You can click Save Log to save the message log to a text file. You can click Show Details to view detailed messages about the metadata conversion.7. 8. Click Export. 318 Chapter 13: Exchanging Metadata . Click Finish to close the wizard.

Choose the target tool from which you want to import the object. To import metadata: 1. The wizard uses the file name as the source database name for each object you import.Steps for Importing Metadata Use the following procedure to import metadata from a file created by another BI or data modeling tool. You can click More Info to read about the tool requirements. and choose Repository-Import Metadata. Steps for Importing Metadata 319 . 2. In the Repository Manager. The Metadata Import Wizard appears. select the folder into which you want to import metadata.

The PowerCenter Options page of the wizard appears. 5. Click Next. 6. Enter the PowerCenter options. 4.3. and click Next. Click the Browse button to navigate to the file that contains the metadata. Enter the options specific for the tool from which you are importing. 320 Chapter 13: Exchanging Metadata . such as IBM DB2 Cube Views. The Metadata Import Wizard displays options specific to the tool you select.

The wizard can define the object definition database type based on the metadata defined in the file. The DBD under which you want to group the repository objects in the Navigator. the Metadata Import Wizard groups all objects under a DBD based on the source or target database. Default is auto detect. Metadata Import Wizard . Indicates whether or not to retain the column properties when you replace an existing object. Default is source. Default is MS1252.Table 13-1 describes the PowerCenter options you define in the Metadata Import Wizard: Table 13-1.PowerCenter Options Option Table Type Database Type Require/ Optional Required Required Description The type of repository objects to create. Database Name Optional Codepage Indentation Retain Physical Properties Required Optional Optional 7. The code page of the repository you import the metadata into. The Metadata Import Wizard converts the metadata in the file to a format recognized by PowerCenter. Default is False. or you can override the database type by choosing a database type here. Click Next. Default is no indentation. Choose the database type for the source or target definitions the wizard creates. The number of spaces used to indent the file you import. Steps for Importing Metadata 321 . You can create source or target definitions. If you do not specify a DBD.

The Metadata Import Wizard adds the objects to the folder in the repository. 8. the Metadata Import Wizard opens the Conflict Resolution Wizard. Click Next. In the Object Selection page. If the folder contains objects with the same name as those you import. and click Finish. select which objects to import into the repository.You can click Save Log to save the message log to a text file. Use the Conflict Resolution Wizard to resolve specific object conflicts. You can click Show Details to view detailed messages about the metadata conversion. see “Copying Objects” on page 297. The Conflict Resolution Wizard is similar to the Copy Wizard. For information on resolving conflicts in the Copy Wizard. 9. 322 Chapter 13: Exchanging Metadata .

see “Comparing Objects” in the Designer Guide. Click Compare Conflict to compare conflicting objects in the import file and target repository.10. The Metadata Import Wizard imports all objects. Click Next to proceed through the Conflict Resolution Wizard. 11. Steps for Importing Metadata 323 . Resolve object conflicts as they appear in the Conflict Resolution Wizard. Click Close when you resolve all conflicts. 12. For more information on comparing sources or targets.

324 Chapter 13: Exchanging Metadata .

331 Deleting Reusable Metadata Extensions. 327 Creating Reusable Metadata Extensions.Chapter 14 Metadata Extensions This chapter covers the following topics: ♦ ♦ ♦ ♦ ♦ Overview. 328 Editing Reusable Metadata Extensions. 332 325 . 326 Working with Metadata Extensions.

If you are using third-party applications or other Informatica products. but you cannot create. For example. You can create. delete. or redefine them. You see the domains when you create. when you create a mapping. When you create metadata extensions for repository objects. You create user-defined metadata extensions using PowerCenter. and view user-defined metadata extensions. PowerCenter Client applications can contain the following types of metadata extensions: ♦ Vendor-defined. you can store your contact information with the mapping. You associate information with repository metadata using metadata extensions.Overview Informatica allows end users and partners to extend the metadata stored in the repository by associating information with individual objects in the repository. User-defined metadata extensions exist within the User Defined Metadata Domain. delete. Vendor-defined metadata extensions exist within a particular vendor domain. Both vendor and user-defined metadata extensions can exist for the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Source definitions Target definitions Transformations Mappings Mapplets Sessions Tasks Workflows Worklets 326 Chapter 14: Metadata Extensions . Third-party application vendors create vendor-defined metadata extensions. User-defined. ♦ All metadata extensions exist within a domain. you may see domains such as Ariba or PowerCenter Connect for Siebel. edit. edit. You can also change the values of user-defined extensions. You can view and change the values of vendor-defined metadata extensions. You cannot edit vendordefined domains or change the metadata extensions in them. you add them to this domain. or view metadata extensions.

Therefore. Create. Vendor-defined metadata extensions are always reusable. and delete metadata extensions for multiple objects at one time. Non-reusable extensions are associated with a single repository object. and delete user-defined metadata extensions using the following tools: ♦ Designer. You can also promote non-reusable metadata extensions to reusable extensions. edit. So. If you want to create. and delete non-reusable metadata extensions for sessions. when you create a reusable extension for a mapping. see “Using the Designer” in the Designer Guide. For details. and mapplets. Repository Manager. and worklets. you must have one of the following privileges: ♦ ♦ Administer Repository Super User Working with Metadata Extensions 327 . Create. edit. You can create. and delete reusable metadata extensions for all types of repository objects. It is not available for other targets. ♦ ♦ To create. but you cannot change a reusable metadata extension to non-reusable. that extension is available only for the target you edit. transformations. and delete reusable user-defined metadata extensions. Create. edit. edit. You can promote a non-reusable metadata extension to reusable. mappings. You associate reusable metadata extensions with all repository objects of a certain type.Working with Metadata Extensions You can create reusable or non-reusable metadata extensions. edit. For details. You can also promote non-reusable metadata extensions to reusable extensions. workflows. use the Repository Manager. if you edit a target and create a non-reusable extension for it. edit. it is available for all mappings. see “Using the Workflow Manager” in the Workflow Administration Guide. targets. and delete non-reusable metadata extensions for sources. Workflow Manager.

the metadata extension becomes part of the properties of that type of object. suppose you create a reusable metadata extension for source definitions called SourceCreator. Anyone who creates or edits a source can enter the name of the person that created the source into this field. connect to the appropriate repository. User-Defined Metadata Extensions This dialog box lists the existing user-defined and vendor-defined metadata extensions. The Edit Metadata Extensions dialog box opens. User-defined metadata extensions appear in the User Defined Metadata Domain. In the Repository Manager. For example. If vendor-defined metadata extensions exist. Open the User Defined Metadata Domain. Choose Edit-Metadata Extensions. 328 Chapter 14: Metadata Extensions .Creating Reusable Metadata Extensions You can create reusable metadata extensions for repository objects using the Repository Manager. 3. 2. Click Add. To create a reusable metadata extension: 1. the SourceCreator extension appears on the Metadata Extensions tab. 4. they appear in their own domains. When you create a reusable metadata extension for any type of repository object. When you create or edit any source definition in the Designer.

string. the value must be an integer between -2. You can select a single database type or all database types. Enter the metadata extension information. For a boolean metadata extension. The database type is required for source and target definition objects. The datatype: numeric (integer). Object Type Required Database Type Required for source and target definition objects Required Optional Datatype Default Value Creating Reusable Metadata Extensions 329 . The database type. worklet.147. Metadata extension names cannot contain any special character except underscore.147. if you create a metadata extension for Expression transformations.647 bytes. mapping. or all of these objects. Table 14-1 describes the options available in the Add Metadata Extension dialog box: Table 14-1.647. For a string metadata extension.147. transformation.483.647 and 2. target definition. For example.The Add Metadata Extensions dialog box opens. workflow. An optional default value. choose true or false. Metadata extension names must be unique for each type of object in a domain. or boolean. you can enter a default value of more than one line. up to 2. mapplet. This can be a source definition.483. For a numeric metadata extension. The type of repository object to which the metadata extension is associated.483. it is available only for Expression transformations. You associate metadata extensions with specific types of transformations. 5. and they cannot begin with a number. Options for Creating Reusable Metadata Extensions Field Extension Name Required/ Optional Required Description Name of the metadata extension. session.

Optional Click Create. the Repository Manager grants Share Read permission as well. If you enable Share Write permission. Share Read Share Write Optional Optional Private Optional Description 6. Optional description of the metadata extension. Click Done. If you select this option. Options for Creating Reusable Metadata Extensions Field Maximum Length Client Visible Client Editable Required/ Optional Required for string objects Optional Optional Description The maximum length for string metadata extensions. The Repository Manager enables this option when third-party application vendors create vendor-defined metadata extensions only. 330 Chapter 14: Metadata Extensions . Specifies whether the value of the metadata extension is editable across vendor domains.Table 14-1. Specifies whether the metadata extension is visible in PowerCenter. Specifies whether the value of the metadata extension is editable in PowerCenter. Specifies whether the metadata extension is visible in vendor domains. the Repository Manager grants Client Visible permission as well. 7. Specifies whether the metadata extension is private to the domain in which it is created.

select the appropriate metadata extension in the Metadata Extensions dialog box. and then click Edit. When you edit a reusable metadata extension.Editing Reusable Metadata Extensions You can edit user-defined. you change the properties of the metadata extension. reusable metadata extensions for repository objects using the Repository Manager. edit the repository object using the Designer or Workflow Manager. To change the value of a metadata extension. Note: You cannot edit vendor-defined metadata extensions. To edit a reusable metadata extension. You can modify the following fields: ♦ ♦ ♦ Default Value Permissions Description Editing Reusable Metadata Extensions 331 .

reusable metadata extensions for repository objects using the Repository Manager. select the appropriate extension in the Metadata Extensions dialog box. you remove the metadata extension and its values from the properties of all objects of that type.Deleting Reusable Metadata Extensions You can delete user-defined. 332 Chapter 14: Metadata Extensions . Note: You cannot delete vendor-defined metadata extensions. and click Delete. To delete a reusable metadata extension. When you delete a reusable metadata extension for a repository object.

390 Deployment Views. 401 333 . 347 Mapping and Mapplet Views. 366 Workflow. 334 Database Definition View. 396 Change Management Views.Chapter 15 Using Metadata Exchange (MX) Views This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Viewing the Repository Metadata. 392 Repository View. 338 Source Views. 353 Metadata Extension Views. 339 Target Views. 398 Folder View. Worklet. 364 Transformation Views. 395 PowerCenter Server Views. and Task Views. 371 Security Views.

Provides details of transformation instances by folder.Viewing the Repository Metadata Informatica Metadata Exchange (MX) provides a set of relational views that allow easy SQL access to the Informatica metadata repository. Instead. use MX to access the repository. The Repository Manager generates these views when you create or upgrade a repository. Table 15-1 lists the available MX views by category: Table 15-1. see “Database Definition View” on page 338. Worklets. For more information. For more information. Therefore. see “Metadata Extension Views” on page 364. Worklet. For more information. MX View Categories MX views provide information to help you analyze metadata stored in the repository. Provides repository details such as repository name and connection information. Metadata Extensions Transformations Workflows. Provides deployment details such as deployment groups and objects that were deployed from one repository to another. Provides details such as server name and host name. Provides a list of target definitions by folder. do not directly access the actual repository tables. Although you can view the repository tables. see “Workflow. Provides a list of source definitions by folder. and transformations used in mappings and mapplets by folder. For more information. targets. see “Mapping and Mapplet Views” on page 353. and Task Views” on page 371. MX View Categories Category Database Sources Targets Mappings and Mapplets Description Provides a list of database definitions in the repository. For more information. Informatica strongly advises against altering the tables or data within the tables. see “Target Views” on page 347. see “Deployment Views” on page 392. For more information. see “Source Views” on page 339. For more information. For more information. see “Security Views” on page 390. Provides details of metadata extensions defined for objects. Provides user and group information. Provides static and run time details for workflows and worklets by folder. Provides a list of sources. For more information. see “Repository View” on page 395. For more information. and Tasks Security Deployment Repository PowerCenter Server 334 Chapter 15: Using Metadata Exchange (MX) Views . Warning: The PowerCenter repository tables have an open architecture. see “Transformation Views” on page 366. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables. For more information. see “PowerCenter Server Views” on page 396.

mappings. and transformation data. Likewise. You can access comments about individual tables. and you need to re-import the source definition into your repository. Almost all views support access to comment information. data fields. Reduces time and resources required to support end-user requests. MX also helps you make precise information requests that draw from data models. For more information. You can use these views to create reports using third-party reporting tools. table relationships. see “Folder View” on page 401. MX View Categories Category Changed Management Folders Description Provide version history of object and label details. For more information. Expands the ability to provide information resources in a controlled manner. MX allows you to drill down to the operational metadata level and expose information needed to support decisions. if you want to view source and target dependencies for a mapping. which is enabled by default. You can add comments to any object within PowerCenter through the Designer and Workflow Manager. you could use the REP_SRC_MAPPING view to see how many mappings include this source. The prepackaged dashboards and reports enable you to analyze the following types of metadata stored in a PowerCenter repository: ♦ ♦ ♦ ♦ ♦ ♦ Source and target metadata Transformation metadata Mapping and mapplet metadata Workflow and worklet metadata Session metadata Change management metadata Viewing the Repository Metadata 335 . and data transformations. Using PowerCenter Metadata Reporter PowerCenter Metadata Reporter is a reporting tool that enables you to browse and analyze PowerCenter metadata. which can be easily customized to meet your business needs. Provides details such as folder name and description. if a source table changes. For IS professionals. such as Crystal Reports. MX facilitates the integration of decision support metadata between the PowerCenter repository and popular Decision Support System (DSS) tools. For example.Table 15-1. The Metadata Reporter prepackages a set of reports and dashboards. Note: The Designer includes an option to Save MX Data. you could use REP_TBL_MAPPING. see “Change Management Views” on page 398. and any other metadata resources. data modeling tools. the MX architecture provides the following benefits: ♦ ♦ ♦ Improves warehouse maintenance and management capability.

sq_) in the Designer. You can run these SQL scripts (*mxdrp.♦ ♦ User and group metadata Operational metadata See the PowerCenter Installation and Configuration Guide for more information. SQL Definition of Views PowerCenter provides two sets of SQL scripts: one to create the MX views and one to drop MX views. Dropping MX Views If you delete a repository. Table 15-3 lists the SQL scripts to drop MX views: Table 15-3.sq_ 336 Chapter 15: Using Metadata Exchange (MX) Views .sq_ termxbld.sq_ infmxdrp. SQL Script to Create MX Views Repository Database DB2 Informix Oracle Microsoft SQL Server Sybase Teradata SQL Script db2mxbld. Table 15-2 lists the SQL scripts to create MX views: Table 15-2.sq_ oramxbld.sq_ oramxdrp. SQL Script to Drop MX Views Repository Database DB2 Informix Oracle Microsoft SQL Server SQL Script db2mxdrp.sq_ sqlmxdrp. Creating MX Views Each time you create or upgrade a repository.sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory. the Repository Server executes a SQL script that drops the MX views.sq_ sybmxbld.sq_ sqlmxbld. the Repository Server executes a SQL script. that creates the MX views.sq_ infmxbld.

vendors of popular query and reporting tools can quickly create a metadata link between their products and the PowerCenter repository. Integrating MX Views with Third-Party Software With MX software and support from Informatica.sq_ termxdrp. SQL Script to Drop MX Views Repository Database Sybase Teradata SQL Script sybmxdrp.sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory. The next generation of MX. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories. called Metadata Exchange SDK.Table 15-3. Software vendors can integrate Informatica metadata with their products through different methods. Viewing the Repository Metadata 337 . from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access.

REP_DATABASE_DEFS Table 15-4 lists database definition details: Table 15-4. Source of the definition. 338 Chapter 15: Using Metadata Exchange (MX) Views . Version ID of the source. Informatica recommends using the fields in bold to join views. REP_DATABASE_DEFS MX View Column Name DATABASE_NAME DEF_SOURCE SUBJECT_AREA VERSION_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER Description Database definition name. MX provides the REP_DATABASE_DEFS view to help you analyze database definitions. Folder name. flat file or RDBMS.Database Definition View The database definition view provides a list of all database definitions in the repository. A database definition includes the source database names. and the folder where the database definition resides.

Source Views Source views provide a list of the latest version of all source definitions defined by folder of any PowerCenter repository. For more information. Table 15-6 lists source information in the REP_ALL_SOURCES view: Table 15-6. source metadata extensions. see “REP_ALL_SOURCES” on page 339. These views provide access to the fields in a non-relational source. These views also show source properties such as shortcuts. and business name. For more information. see “REP_SRC_FILES” on page 343. see “REP_SRC_TBL_FLDS” on page 346. see “REP_SRC_TBLS” on page 344. This view provides access to the fields in relational sources. They also provide information such as source columns. description. Source Views 339 . see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345. Table 15-5 lists the different views that help you analyze source metadata: Table 15-5. and mappings and mapplets where these sources are used. column properties. For more information. version. This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. REP_ALL_SOURCES MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_SOURCE_NAME PARENT_SOURCE_BUSINESS_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. Name of the parent source Business name of the parent source. see “REP_ALL_SOURCE_FLDS” on page 341. Sources include both relational sources and non-relational sources such as XML files and flat files. REP_SRC_FILES REP_SRC_TBLS REP_SRC_FILE_FLDS REP_SEG_FLDS REP_SRC_TBL_FLDS REP_ALL_SOURCES This view provides a list of the latest version of sources defined in each folder of a repository. Source Views View REP_ALL_SOURCES REP_ALL_SOURCE_FLDS Description This view provides a list of the latest version of sources defined in each folder of a repository. Folder ID. For more information. creation date. Source definitions can be defined for both relational and nonrelational sources. You can use the source name to retrieve all the fields belonging to the source. For more information. This view provides a list of all file definitions in the repository. For more information.

Source ID. Source name. Specifies whether the source is a relational or a non-relational source. Physical size (compressed binary). Source version number. 340 Chapter 15: Using Metadata Exchange (MX) Views . UTC time for source checkin. Description of the parent source.Table 15-6. Name of the database type of the parent source. Specifies whether the source version is active or has been deleted. Source description. Time when the parent source was last modified. ID of the first field in the source. Parent source display size (uncompressed binary). Source version number. Folder ID. UTC time when the parent source was last modified. UTC time when the source display was last saved. Database name of the parent source. UTC time (Coordinated Universal Time) when the parent source was checked in. Name of the source schema. Time when the source was last saved. File organization information. Folder name. Parent source physical size (compressed binary). REP_ALL_SOURCES MX View Column Name PARENT_SOURCE_ID PARENT_SOURCE_DESCRIPTION PARENT_SOURCE_VERSION_NUMBER PARENT_SOURCE_VERSION_STATUS PARENT_SOURCE_UTC_CHECKIN PARENT_SOURCE_UTC_LAST_SAVED PARENT_SOURCE_CREATION_TIME PARENT_SOURCE_SCHEMA_NAME PARENT_SOURCE_FIRST_FIELD_ID PARENT_SOURCE_SELECT_INFO_ID PARENT_SOURCE_DISPLAY_SIZE PARENT_SOURCE_PHYSICAL_SIZE PARENT_SRC_MIN_PHYSICAL_SIZE PARENT_SOURCE_DATABASE_NAME PARENT_SOURCE_TYPE PARENT_SOURCE_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID SOURCE_NAME SOURCE_ID SOURCE_DESC SOURCE_VERSION_NUMBER SOURCE_VERSION_STATUS SOURCE_UTC_CHECKIN SOURCE_UTC_LAST_SAVED SOURCE_LAST_SAVED Datatype NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER Description ID of the parent source. Parent source version status.

The repository name. REP_ALL_SOURCE_FLDS This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. For global shortcuts. UTC time when the parent source was checked in. Informatica recommends using the fields in bold to join views. 0 = not a shortcut. Specifies whether the source is a global shortcut. Parent folder ID. Specifies whether the source is a shortcut. For local shortcuts. Parent source name. Database type of the parent source. Version number of the parent source. Database name of the parent source. Business name of the parent source.Table 15-6. UTC time when the parent source was last saved. Time when the parent source was last modified. Source Views 341 . Source type such as relational database or flat file. 1 = shortcut. REP_ALL_SOURCE_FLDS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_SOURCE_NAME PARENT_SOURCE_BUSINESS_NAME PARENT_SOURCE_ID PARENT_SOURCE_DESCRIPTION PARENT_SOURCE_VERSION_NUMBER PARENT_SOURCE_VERSION_STATUS PARENT_SOURCE_UTC_CHECKIN PARENT_SOURCE_UTC_LAST_SAVED PARENT_SOURCE_CREATION_TIME PARENT_SOURCE_TYPE PARENT_SOURCE_DATABASE_NAME PARENT_SOURCE_DATABASE_TYPE Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (240) VARCHAR2 (50) Description Parent folder name. the name of the shortcut displays. Table 15-7 lists source field information in the REP_ALL_SOURCE_FLDS view: Table 15-7. 1 = shortcut. REP_ALL_SOURCES MX View Column Name SOURCE_DATABASE_NAME REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Source database name. 0 = not a shortcut. Parent source ID. the names of shortcut and the parent targets display. Description of the parent source. Status of the parent source version.

REP_ALL_SOURCE_FLDS MX View Column Name SUBJECT_AREA SUBJECT_ID SOURCE_NAME SOURCE_ID SOURCE_DESCRIPTION SOURCE_VERSION_NUMBER SOURCE_VERSION_STATUS SOURCE_UTC_CHECKIN SOURCT_UTC_LAST_SAVED SOURCE_LAST_SAVED SOURCE_DATABASE_NAME SOURCE_FIELD_NAME SOURCE_FIELD_BUSINESS_NAME SOURCE_FIELD_ID SOURCE_FIELD_DESCRIPTION SOURCE_FIELD_NUMBER SOURCE_FIELD_NEXT_FIELD_ID SOURCE_FIELD_LEVEL SOURCE_FIELD_PICTURE_TEXT SOURCE_FIELD_OCCURS_TIME SOURCE_FIELD_REDEFINES_FIELD SOURCE_FIELD_DISPLAY_OFFSET SOURCE_FIELD_DISPLAY_LENGTH SOURCE_FIELD_PHYSICAL_OFFSET SOURCE_FIELD_PHYSICAL_LENGTH SOURCE_FIELD_CHILD_FIELD_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description Folder name. Null for relational sources. Source field number. Picture text that a COBOL source uses. Offset of this field within this FD. ID of the field that follows the current field. 342 Chapter 15: Using Metadata Exchange (MX) Views . Folder ID. Field level number for non-relational sources. Name of the database for the source. Offset of this field within the source.Table 15-7. Source ID. Source description. UTC time when the source was last checked in. Display field length. UTC time when the source was last saved. ID of the source field (primary key). Specifies whether the source version is active or has been deleted. Time when the source was last saved. Description of the source field. Business name of the source field. Number of time that the field (or record) occurs in the source. The next child. Source name. if any. for a non-relational COBOL source. Source field name. Physical field length. Identifies the field/record that this field/ record redefines. Source version number.

File organization information. Any flat file imported through the Source Analyzer has an entry. Source Views 343 . Source field picture usage name. REP_SRC_FILES MX View Column Name FILE_ID SUBJECT_AREA DATABASE_TYPE DATABASE_NAME FILE_NAME SCHEMA_FILE_NAME SELECT_INFO_ID DISPLAY_SIZE PHYSICAL_SIZE MIN_PHYSICAL_SIZE Datatype INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER Description Source ID (primary key). Minimum physical size (varying records). Folder name. Scale for the field. Display size (uncompressed). You can use FIRST_FIELD_ID to retrieve the fields belonging to a non-relational source by following the links in the REP_SRC_FILE_FLDS view. Name of file definitions. 1 = nulls not allowed. Type of database extracted from. 0 = not a shortcut. Repository name. 1 = shortcut. Informatica recommends using the fields in bold to join views. REP_SRC_FILES This view provides a list of all file definitions in the repository. Length or precision for the field.Table 15-7. 1 = shortcut. Specifies whether the source is a shortcut. Specifies whether nulls are allows. 0= nulls allowed. REP_ALL_SOURCE_FLDS MX View Column Name SOURCE_FIELD_KEY_TYPE SOURCE_FIELD_DATATYPE SOURCE_FIELD_PRECISION SOURCE_FIELD_SCALE SOURCE_FIELD_PIC_USAGE_NAME SOURCE_FIELD_NULLTYPE REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (50) VARCHAR2 (40) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Specifies whether the source field key is a primary key or a foreign key. Table 15-8 lists file information in the REP_SRC_FILES view: Table 15-8. Name of database extracted from (DSN). 0 = not a shortcut. Field datatype. File from which schema was extracted. Physical size (compressed binary). Specifies whether the source is a global shortcut.

Informatica recommends using the fields in bold to join views.Table 15-8. Type of database extracted from. REP_SRC_TBLS This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. Folder ID. Folder version ID. Link to first field. Source version number. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9. Source description. Name of database extracted from. Source description. Source version number. Version ID. Unique key. Last time the source table was saved. 344 Chapter 15: Using Metadata Exchange (MX) Views . Informatica recommends using the fields in bold to join views. Folder name. Name of schema extracted from. REP_SRC_FILES MX View Column Name FIRST_FIELD_ID SOURCE_DESCRIPTION VERSION_ID SOURCE_VERSION_NUMBER Datatype INTEGER VARCHAR2 (2000) INTEGER NUMBER Description Link to first field of file definitions. Folder version name. Business name of the table. REP_SRC_TBLS MX View Column Name TABLE_NAME TABLE_BUSNAME TABLE_ID SUBJECT_AREA DATABASE_TYPE DATABASE_NAME SCHEMA_NAME FIRST_FIELD_ID SOURCE_DESCRIPTION VERSION_ID VERSION_NAME LAST_SAVED SOURCE_VERSION_NUMBER SUBJECT_ID Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2( 240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Table name.

. COMP type (binary compressed fields). Offset using display length. Source Views 345 . Redefines this field. 0 = not a key. Display length. Source ID (primary key).REP_SRC_FILE_FLDS and REP_SEG_FLDS These views provide access to the fields in a non-relational source. PIC clause. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views Column Name FIELD_ID SUBJECT_AREA FILE_ID FIELD_NAME FIELD_LEVEL FIELD_NUMBER FIELD_DESCRIPTION PICTURE_TEXT OCCURS REDEFINES_FIELD KEY_TYPE DISPLAY_OFFSET DISPLAY_LENGTH PHYSICAL_OFFSET PHYSICAL_LENGTH USAGE_TYPE DATA_PRECISION DATA_SCALE CHILD_ID SIBLING_ID VERSION_ID Datatype INTEGER VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER INTEGER VARCHAR2 (2000) VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER Description Field ID (primary key). Table 15-10 lists source field information in the REP_SRC_FILE_FLDS and REP_SEG_FLDS views: Table 15-10. 02). Each field is contained in the scanned tables listed in the REP_SEG_FLDS view. Field level (i. Physical length. Informatica recommends using the fields in bold to join views. Link to next field at this level. Key type. Physical offset. Decimal precision for numeric fields or field length for CHAR fields. Decimal scale for numeric fields. Field name. 1 = primary key. Order number of the field. Link to child field if this is a group item. Folder name. Version ID of the source. 01.e. Number of OCCURS. Comments for this field.

Folder name. Source table ID. Folder ID. Business name of the table. REP_SRC_TBL_FLDS MX Views Column Name COLUMN_NAME COLUMN_BUSNAME COLUMN_ID SUBJECT_AREA TABLE_ID TABLE_NAME TABLE_BUSNAME COLUMN_NUMBER COLUMN_DESCRIPTION KEY_TYPE SOURCE_TYPE DATA_PRECISION DATA_SCALE NEXT_COLUMN_ID VERSION_ID VERSION_NAME SOURCE_VERSION_NUMBER SUBJECT_ID Datatype VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (2000) VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER VARCHAR2 (240) NUMBER NUMBER Description Field name. Folder version ID.REP_SRC_TBL_FLDS This view provides access to the fields in relational sources. Folder version name. Table name. Source version number. Data type for this column. Order number of the column. Decimal precision for numeric fields or field length for CHAR fields. Key type for this column. 346 Chapter 15: Using Metadata Exchange (MX) Views . You can use the source name to retrieve all the fields belonging to the source. Informatica recommends using the fields in bold to join views. The columns in this view are part of the tables listed in the REP_SRC_TBLS views. Table 15-11 lists relational source fields in the REP_SRC_TBL_FLDS view: Table 15-11. Decimal scale for numeric fields. Business name of the field. Description of the column. Link to next field in source table. Field ID (primary key).

target metadata extensions. These views also show target properties such as shortcuts. For more information. Target version number. Targets include both relational and non-relational targets such as XML files and flat files. This view provides a list of targets in the repository. the name of the shortcut displays. see “REP_TARG_TBLS” on page 350. For more information. and mappings and mapplets where these target are used. For local shortcuts. For more information. Folder ID. This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. REP_ALL_TARGETS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_TARGET_NAME PARENT_TARGET_BUSINESS_NAME PARENT_TARGET_ID PARENT_TARGET_DESCRIPTION PARENT_TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER Description Parent folder name. version. Target Views View REP_ALL_TARGETS REP_ALL_TARGET_FIELDS Description This view provides a list of the latest version of all targets defined in each folder of a repository. Target description. Target Views 347 . Target name. the names of shortcut and the parent targets display. see “REP_ALL_TARGETS” on page 347. see “REP_TARG_TBL_COLS” on page 351. Business name for the target. Table 15-13 lists target details in the REP_ALL_TARGETS view: Table 15-13. REP_TARG_TBLS REP_TARG_TBL_COLS REP_ALL_TARGETS This view provides a list of the latest version of all targets defined in each folder of a repository. column properties. For more information. see “REP_ALL_TARGET_FIELDS” on page 349. creation date. For global shortcuts.Target Views Target views provide a list of the latest version of all target definitions defined by folder of a PowerCenter repository for both relational and non-relational sources. Table 15-12 lists the different views that help you analyze target metadata: Table 15-12. Target ID (primary key). FIRST_COLUMN_ID is a link to the set of columns for this table. description. This view provides the properties of columns defined for the target tables in a data warehouse or data mart. and business name. They also provide information such as target columns.

Table 15-13. Folder ID. UTC time (Coordinated Universal Time) when the target was last checked in. Folder name. 1 = shortcut. Target description. Link to first field of this table. Repository name. Options for use when generating DDL. Link to first field of this table. 1 = shortcut. UTC time (Coordinated Universal Time) when the parent target was checked in. Time when the target was last saved. User-specified constraint string used when the DDL is generated. UTC time when the target was last saved. UTC time when the target was last saved. Target version number. Database type for the parent target. Informatica recommends using the fields in bold to join views. 0 = not a shortcut. Specifies whether the target is a shortcut. Time when the target was last modified. 348 Chapter 15: Using Metadata Exchange (MX) Views . Target ID. Specifies whether the target is a global shortcut. Status of the target version. 0 = not a shortcut. REP_ALL_TARGETS MX View Column Name PARENT_TARGET_VERSION_STATUS PARENT_TARGET_UTC_CHECKIN PARENT_TARGET_UTC_LAST_SAVED PARENT_TARGET_CREATION_TIME PARENT_TARGET_FIRST_FIELD_ID PARENT_TARGET_CONSTRAINT PARENT_TARGET_CREATE_OPTIONS PARENT_TARGET_FIRST_INDEX_ID PARENT_TARGET_FILE_ID PARENT_TARGET_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID TARGET_NAME TARGET_ID TARGET_DESCRIPTION TARGET_VERSION_NUMBER TARGET_VERSION_STATUS TARGET_UTC_CHECKIN TARGET_UTC_LAST_SAVED TARGET_CREATION_TIME REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 VARCHAR2 (2000) VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Status of the parent target version. Target name. ID for the parent target file.

Business name of the parent target.REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Database type of parent target. Time when target was last modified. Name of parent target. Parent target ID. the names of the shortcut and the parent targets display. UTC time when the parent target was last saved. ID of the first field of parent target. UTC time (Coordinated Universal Time) when the parent target was last checked in. Target version number. Table 15-14 lists target field data in the REP_ALL_TARGET_FIELDS view: Table 15-14. UTC time when the target was last saved. ID of parent target file. Time when the parent target was last modified. For local shortcuts. Status of the parent target version. Target Views 349 . UTC time when the target was last checked in. Target description. Target version number. For global shortcuts. Folder ID. the shortcut name displays. Status of the target version. Folder name. Target name. Target ID. REP_ALL_TARGET_FIELDS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_TARGET_NAME PARENT_TARGET_BUSINESS_NAME PARENT_TARGET_ID PARENT_TARGET_DESCRIPTION PARENT_TARGET_VERSION_NUMBER PARENT_TARGET_VERSION_STATUS PARENT_TARGET_UTC_CHECKIN PARENT_TARGET_UTC_LAST_SAVED PARENT_TARGET_LAST_SAVED PARENT_TARGET_FILE_ID PARENT_TARGET_FIRST_FIELD_ID PARENT_TARGET_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID TARGET_NAME TARGET_ID TARGET_DESCRIPTION TARGET_VERSION_NUMBER TARGET_VERSION_STATUS TARGET_UTC_CHECKIN TARGET_UTC_LAST_SAVED TARGET_CREATION_TIME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) Description Folder name. Folder ID. Description of parent target.

All tables contained in the target table model are part of this view. Text. Datatype of target field. Money. Specifies whether target field is null. It is the primary table list used to delineate a PowerCenter data model. Link to source from which this field was created. Target field number. The tables are virtual. 1 = Not Null. REP_TARG_TBLS This view provides a list of targets in the repository. Datatype group codes. Description of target field. Repository name. not physically created. 1 = shortcut. FIRST_COLUMN_ID is a link to the set of columns for this table. 0 = Null. REP_ALL_TARGET_FIELDS MX View Column Name TARGET_FIELD_NAME TARGET_FIELD_BUSINESS_NAME TARGET_FIELD_ID TARGET_FIELD_DESC TARGET_FIELD_NUMBER TARGET_FIELD_NEXT_FIELD_ID TARGET_FIELD_PICTURE_TEXT TARGET_FIELD_IS_NULLABLE TARGET_FIELD_SOURCE_FIELD_ID TARGET_FIELD_KEY_TYPE TARGET_FIELD_DATATYPE TARGET_FIELD_DATATYPE_GROUP Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) CHAR (1) Description Target field name. 0 = not a shortcut. and Bigint Precision for target field. Therefore. verify that the table exists before using this view. Target field ID. Specifies whether the target is a shortcut. String. B = Binary and Bit C = Character. and Byte D = Date N = Numeric. 0 = not a shortcut. Business name of target field. Specifies whether the target is a global shortcut. Key type of target field. Picture text that COBOL sources use. 350 Chapter 15: Using Metadata Exchange (MX) Views . ID of the next field in target.Table 15-14. TARGET_FIELD_PRECISION TARGET_FIELD_SCALE REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Informatica recommends using the fields in bold to join views. 1 = shortcut. Scale for target field.

Link to first index. REP_TARG_TBLS MX View Column Name SUBJECT_AREA TABLE_NAME BUSNAME VERSION_ID VERSION_NAME DESCRIPTION FIRST_COLUMN_ID TABLE_CONSTRAINT CREATE_OPTIONS FIRST_INDEX_ID LAST_SAVED TARGET_VERSION_NUMBER SUBJECT_ID TABLE_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Folder name. Table name. Informatica recommends using the fields in bold to join views. Business name of the table. Time target table was last saved. Table business name.Table 15-15 lists the columns in the REP_TARG_TBLS view: Table 15-15. Table 15-16 lists target table column properties for the REP_TARG_TBL_COLS view: Table 15-16. Order number of the column. Business name of this column. Folder ID. Column ID (primary key). Target version number. Table creation options specified in the Warehouse Designer. Folder version ID. Folder version name. Target Views 351 . REP_TARG_TBL_COLS This view provides the properties of columns defined for the target tables in a data warehouse or data mart. Column name. Table constraint specified in Warehouse Designer. Table this column belongs to. Link to first field of this table. Description of the table. REP_TARG_TBL_COLS MX View Column Name SUBJECT_AREA TABLE_NAME TABLE_BUSNAME COLUMN_NAME COLUMN_BUSNAME COLUMN_NUMBER COLUMN_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER INTEGER Description Folder name. Table ID.

Folder version name. Not a Key. Whether NULLs are accepted. Primary Key. Target version number. C = Character D = Date N = Numeric Decimal precision for numeric fields or field length for CHAR fields. Native database datatype. Decimal scale for numeric columns.Table 15-16. DATA_PRECISION DATA_SCALE NEXT_COLUMN_ID IS_NULLABLE SOURCE_COLUMN_ID TARGET_VERSION_NUMBER INTEGER INTEGER INTEGER INTEGER INTEGER NUMBER Informatica recommends using the fields in bold to join views. Link to source this column was created from. Primary and Foreign Key. Datatype group. Link to next column. Foreign Key. REP_TARG_TBL_COLS MX View Column Name VERSION_ID VERSION_NAME DESCRIPTION COLUMN_KEYTYPE DATA_TYPE DATA_TYPE_GROUP Datatype INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (240) CHAR (1) Description Folder version ID. Column description. 352 Chapter 15: Using Metadata Exchange (MX) Views .

These views also display properties of mappings and mapplets such as description.Mapping and Mapplet Views Mapping and mapplet views allow you to see the sources. This view shows all of the source fields used in a mapping. This view shows all sources used in a mapping. targets. and whether the mapping or the mapplet is a shortcut. This view provides access to the compound table-level transformation expressions for each target table. see “REP_MAPPING_PORT_CONN” on page 363. For more information. see “REP_ALL_MAPPINGS” on page 354. and transformations used in a mapping or a mapplet by folder in a PowerCenter repository. see “REP_TARG_MAPPING” on page 356. see “REP_TBL_MAPPING” on page 360. see “REP_MAPPING_UNCONN_PORTS” on page 362. Table 15-17 lists the different views that help you analyze mapping and mapplet metadata: Table 15-17. For more information. version and creation date. For more information. For more information. targets. For more information. see “REP_SRC_MAPPING” on page 359. This view provides a list of the latest version of all mapplets defined in each folder of a repository. see “REP_TARG_TBL_JOINS” on page 361. For more information. see “REP_SRC_FLD_MAP” on page 359. This view displays the port-level connections between the objects of a mapping. Mapping and Mapplet Views View REP_ALL_MAPPINGS Description This view provides a list of the latest version of all mappings defined in each folder of a repository. see “REP_TARG_FLD_MAP” on page 357. For more information. For more information. For more information. This view contains join information between target tables. For more information. This view shows all of the target tables used in a mapping and provides source to target mapping information. This view shows compound field-level transformation expressions associated with a target. This is the companion view for the REP_TBL_MAPPING view. and transformations in a mapping. This view shows the source fields used by the target fields in a mapping. This view displays the unconnected ports in sources. see “REP_ALL_MAPPLETS” on page 355. REP_ALL_MAPPLETS REP_TARG_MAPPING REP_TARG_FLD_MAP REP_FLD_MAPPING REP_SRC_MAPPING REP_SRC_FLD_MAP REP_TBL_MAPPING REP_TARG_TBL_JOINS REP_MAPPING_UNCONN_PORTS REP_MAPPING_PORT_CONN Mapping and Mapplet Views 353 . see “REP_FLD_MAPPING” on page 358. the validity of the mapping or mapplet. For more information.

the name of the shortcut displays.REP_ALL_MAPPINGS This view provides a list of the latest version of all mappings defined in each folder of a repository. the names of the shortcut and the parent mappings display. UTC time (Coordinated Universal Time) when the parent mapping was checked in. Specifies whether the mapping is a global shortcut. The UTC time when mapping was last saved. UTC time when the mapping was last saved. Specifies whether the parent mapping is valid. Folder ID. For local shortcuts. Name of the parent mapping. Repository name. Mapping version number. Parent mapping version status. Parent mapping version number. REP_ALL_MAPPINGS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_MAPPING_NAME PARENT_MAPPING_ID PARENT_MAPPING_VERSION_NUMBER PARENT_MAPPING_VERSION_STATUS PARENT_MAPPING_UTC_CHECKIN PARENT_MAPPING_UTC_LAST_SAVED PARENT_MAPPING_LAST_SAVED PARENT_MAPPING_IS_VALID PARENT_MAPPING_DESCRIPTION MAPPING_NAME MAPPING_ID MAPPING_VERSION_NUMBER MAPPING_VERSION_STATUS MAPPING_UTC_CHECKIN MAPPING_UTC_LAST_SAVED MAPPING_LAST_SAVED MAPPING_DESCRIPTION REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER Description Parent folder name. For global shortcuts. Mapping description. Status of the mapping version. Sequence ID of the parent mapping. 0 = not a shortcut. 1 = shortcut. 354 Chapter 15: Using Metadata Exchange (MX) Views . Folder name. Table 15-18 lists mapping information in the REP_ALL_MAPPINGS view: Table 15-18. Parent mapping description. Name of mapping. Parent folder ID. UTC time when the mapping was checked in. Time when the mapping was last saved. Sequence ID for mapping. Date and time when parent mapping was last saved.

Name of parent mapplet. Mapping and Mapplet Views 355 . 0 = not a shortcut. REP_ALL_MAPPLETS This view provides a list of the latest version of all mapplets defined in each folder of a repository. Sequence ID of parent mapplet.Table 15-18. REP_ALL_MAPPINGS MX View Column Name IS_SHORTCUT Datatype NUMBER Description Specifies whether the mapping is a shortcut. For global shortcuts. For local shortcuts. Folder name. Specifies whether the parent mapplet is valid. Mapplet ID. Parent folder ID. Field ID (primary key). 1 = shortcut. Parent mapplet description. Parent mapplet version status. UTC time (Coordinated Universal Time) when the parent mapplet was checked in. Status of the mapplet version. The date and time when parent mapplet was last saved. UTC time when the mapplet was checked in. Name of mapplet. Informatica recommends using the fields in bold to join views. the name of the shortcut displays. REP_ALL_MAPPLETS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_MAPPLET_NAME PARENT_MAPPLET_ID PARENT_MAPPLET_VERSION_NUMBER PARENT_MAPPLET_VERSION_STATUS PARENT_MAPPLET_UTC_CHECKIN PARENT_MAPPLET_UTC_LAST_SAVED PARENT_MAPPLET_LAST_SAVED PARENT_MAPPLET_IS_VALID PARENT_MAPPLET_DESCRIPTION MAPPLET_NAME MAPPLET_ID MAPPLET_VERSION_NUMBER MAPPLET_VERSION_STATUS MAPPLET_UTC_CHECKIN MAPPLET_UTC_LAST_SAVED MAPPLET_LAST_SAVED Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Description Parent folder name. Folder ID. Time when the mapplet was last saved. The UTC time when mapplet was last saved. UTC time when the mapplet was last saved. the names of the shortcut and the parent mapplets display. Table 15-19 lists mapplet metadata in the REP_ALL_MAPPLETS view: Table 15-19. Mapplet version number.

Target business name. Foreign key that points to generated mapplet transformation. REP_ALL_MAPPLETS MX View Column Name MAPPLET_DESCRIPTION REF_WIDGET_ID REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER Description Mapplet description. Folder version name. 356 Chapter 15: Using Metadata Exchange (MX) Views . Compound conditional load. Repository name. Description of transformation expression. Compound SQL override expression. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Specifies whether the mapplet is a shortcut. It does not contain information about sources.Table 15-19. Note: Use the REP_TBL_MAPPING view to analyze source and target relationships. Specifies whether the mapplet is a global shortcut. This view contains information about mappings defined for target tables only. Description of mapping. Folder version ID. REP_TARG_MAPPING This view provides access to the compound table-level transformation expressions for each target table. 1 = shortcut. Join REP_TBL_MAPPING and REP_TARG_MAPPING by MAPPING_NAME to include column-level mapping information in the REP_FLD_MAPPING view. 0 = not a shortcut. REP_TARG_MAPPING MX View Column Name TARGET_NAME TARG_BUSNAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME SOURCE_FILTER CONDITIONAL_LOAD GROUP_BY_CLAUSE SQL_OVERRIDE DESCRIPTION MAPPING_COMMENT Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) Description Target name. Folder name. Compound group by expression. Mapping name. 1 = shortcut. Compound source filter condition. This view pulls information from all the transformation objects that contribute to the target table in a valid mapping. Table 15-20 lists expression information in the REP_TARG_MAPPING view: Table 15-20. 0 = not a shortcut.

There might be many mappings for a set of fields. each distinguished by the MAPPING_NAME field. Folder version ID. Table 15-21 lists expression metadata that you find in the REP_TARG_FLD_MAP view: Table 15-21. Mapping version number. Business name of target table. see the Transformation Language Reference. The field-level expression contains all the source fields (both file definition/non-relational source) that make up the value of the target field. Compound transformation expression. Name of target (table). Time the mapping was saved last. This view pulls information from all transformation objects that contribute to the target table in a valid mapping. Mapping version number. For details on the syntax of the transformation expression. Informatica recommends using the fields in bold to join views. REP_TARG_FLD_MAP MX View Column Name TARGET_COLUMN_NAME TARG_COL_BUSNAME TARGET_NAME TARG_BUSINESS_NAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Name of target field (table field). Target version number. REP_TARG_MAPPING MX View Column Name MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER NUMBER Description Time the mapping was saved last. End user comment.Table 15-20. Target version number. Business name of target field. Mapping comment. Folder name. REP_TARG_FLD_MAP This view shows compound field-level transformation expressions associated with a target. Mapping and Mapplet Views 357 . Mapping name. Folder version name. Informatica recommends using the fields in bold to join views. Administrator comment.

Table 15-22 lists the source and target field metadata in the REP_FLD_MAPPING view: Table 15-22. Name of the source table. REP_FLD_MAPPING MX View Column Name SOURCE_FIELD_NAME SRC_FLD_BUSNAME SOURCE_NAME SRC_BUSNAME TARGET_COLUMN_NAME TARG_COL_BUSNAME TARGET_NAME TARG_BUSNAME SUBJECT_AREA SUBJECT_ID MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER SOURCE_ID TARGET_ID MAPPING_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Descriptions Name of the source field. Folder version name. Administrator comment. Business name of the target column. Business name of the target. Folder version ID. Mapping comment. Target name. Time the mapping was saved last.REP_FLD_MAPPING This view shows the source fields used by the target fields in a mapping. Source version number. Business name of the source table. Target table ID. Informatica recommends using the fields in bold to join views. Folder name. It contains both source and target column names and details. End user comment. Business name of the source field. Target field transformation expression. Mapping ID. Name of the target field. Mapping version number. Folder ID. This is the companion view for the REP_TBL_MAPPING view. Target version number. Name of the mapping. Source table ID. 358 Chapter 15: Using Metadata Exchange (MX) Views .

This view creates these expressions by pulling information from all transformation objects that contribute to the target table in a valid mapping. Table 15-24 lists mapping source fields: Table 15-24. It does not contain information about the targets involved in a mapping. The REP_TBL_MAPPING view contains the entire source and target mapping relationship. Informatica recommends using the fields in bold to join views. Folder ID. Source version number. Business name of source table. Table 15-23 lists mapping source metadata in the REP_SRC_MAPPING view: Table 15-23. The transformation expression corresponds to the target fields that get data from a particular source field. Query this view by MAPPING_NAME and VERSION_NAME. REP_SRC_MAPPING MX View Column Name SOURCE_NAME SOURCE_ID SRC_BUSNAME SUBJECT_AREA SUBJECT_ID MAPPING_NAME MAPPING_ID VERSION_ID VERSION_NAME MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Name of the source. Folder version name. Source ID. This view contains the mapping names defined for an individual source table. Mapping comment. Business name of the field. Mapping name. Mapping ID.REP_SRC_MAPPING This view shows all sources used in a mapping. Folder version ID. Mapping version number. Mapping and Mapplet Views 359 . Mapping Source Fields Column Name SOURCE_FIELD_NAME SRC_FLD_BUSNAME Datatype VARCHAR2 (240) VARCHAR2 (240) Description Source field name. REP_SRC_FLD_MAP This view shows all of the source fields used in a mapping. A mapping might contain several sources. Time the mapping was last saved. Folder name.

Name of the mapping. Informatica recommends using the fields in bold to join views. Mapping version number. Field transformation expression. Source version number. Target name. End user comment. Mapping comment. Time the mapping was saved last. This view pulls information from all transformation objects that contribute to the target table in a valid mapping to provide the table-level expressions. Folder version name. Business name of the source table. Folder name. Table 15-25 lists mapping target metadata in the REP_TBL_MAPPING view: Table 15-25. REP_TBL_MAPPING MX View Column Name SOURCE_NAME SOURCE_ID SRC_BUSNAME TARGET_NAME TARGET_ID TARG_BUSNAME SUBJECT_AREA SUBJECT_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER Description Name of the source object. REP_TBL_MAPPING This view shows all of the target tables used in a mapping and provides source to target mapping information. Source ID.Table 15-24. Compound target. Folder name. Target ID. Business name of the target. Business name of the source. Folder version ID. Mapping Source Fields Column Name SOURCE_NAME SRC_BUSNAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Name of the source. 360 Chapter 15: Using Metadata Exchange (MX) Views . Administrator comment. Folder ID. Target version number.

Target version number. Mapping comment. Business name of first table. ID of first table in the join. Use this view to query the PowerCenter defined joins for a target table model. or through primary key-foreign key relationships. Source version number. It is populated when you link fields in the Warehouse Designer. Table 15-26 lists target table join metadata in the REP_TARG_TBL_JOINS view: Table 15-26. REP_TARG_TBL_JOINS This view contains join information between target tables. Name of column in first table. Mapping ID. Folder version ID. Folder version name. Informatica recommends using the fields in bold to join views. REP_TBL_MAPPING MX View Column Name MAPPING_NAME MAPPING_ID VERSION_ID VERSION_NAME SOURCE_FILTER CONDITIONAL_LOAD GROUP_BY_CLAUSE SQL_OVERRIDE DESCRIPTION MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Name of the mapping. Folder version name. Compound conditional load. Folder version ID. Mapping and Mapplet Views 361 . Mapping version number. Time the mapping was saved last. Compound source filter condition. Name of first table in the join. REP_TARG_TBL_JOINS MX View Column Name SUBJECT_AREA VERSION_ID VERSION_NAME TABLE1_NAME TABLE1_BUSNAME TABLE1_ID COLUMN1_NAME COLUMN1_BUSNAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. Compound group by clause. Business name of column in first table.Table 15-25. Description of transformation. Compound SQL override expression.

REP_MAPPING_UNCONN_PORTS MX View Column Name SUBJECT_AREA SUBJECT_ID MAPPING_NAME MAPPING_ID MAPPING_VERSION_NUMBER OBJECT_INSTANCE_NAME OBJECT_INSTANCE_ID OBJECT_TYPE OBJECT_TYPE_NAME FIELD_ID FIELD_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) Description Folder name. Business name of second table. Table1 version number. Name of the mapping. Number of column in second table. Business name of column in second table. ID of column in first table. Name of column in second table. Name of the instance. Object type. Name of second table in the join. ID of second table in the join.Table 15-26. 362 Chapter 15: Using Metadata Exchange (MX) Views . Mapping version number. Folder ID (primary key). Object type name. Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS view: Table 15-27. Informatica recommends using the fields in bold to join views. and transformations in a mapping. targets. REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources. Sequence ID for the mapping (primary key). ID of column in second table. Table2 version number. Source field name. Source field ID (primary key). Unique ID for the instance in a mapping. REP_TARG_TBL_JOINS MX View Column Name COLUMN1_NUMBER COLUMN1_ID TABLE2_NAME TABLE2_BUSNAME TABLE2_ID COLUMN2_NAME COLUMN2_BUSNAME COLUMN2_NUMBER COLUMN2_ID TABLE1_VERSION_NUMBER TABLE2_VERSION_NUMBER Datatype NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Number of column in first table.

target. mapplet. target. Target object instance ID. Target object type name. REP_MAPPING_PORT_CONN MX View Column Name SUBJECT_ID SUBJECT_AREA MAPPING_ID MAPPING_NAME MAPPING_VERSION_NUMBER FROM_OBJECT_ID FROM_OBJECT_TYPE FROM_OBJECT_TYPE_NAME FROM_OBJECT_NAME FROM_OBJECT_INSTANCE_ID FROM_OBJECT_FIELD_NAME FROM_OBJECT_VERSION_NUMBER TO_OBJECT_ID TO_OBJECT_TYPE TO_OBJECT_TYPE_NAME TO_OBJECT_NAME TO_OBJECT_INSTANCE_ID TO_OBJECT_FIELD_NAME TO_OBJECT_VERSION_NUMBER Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Description Folder ID. Mapping and Mapplet Views 363 . Source object type. Source object instance ID. Mapping name. Target object ID. Target object version number. Sequence ID for the mapping (primary key). transformations. Unconnected transformations are not included. Name of the source object type. REP_MAPPING_UNCONN_PORTS MX View Column Name OBJECT_VERSION_NUMBER Datatype NUMBER Description Version number of the source. Target object name. REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a mapping. Target object field name. Source object ID. and mapplets. Source object name. Mapping version number. Source object version number.Table 15-27. Folder name. Objects include sources. Informatica recommends using the fields in bold to join views. Source object field name. Informatica recommends using the fields in bold to join views. Target object type such as port. targets. or transformation. Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN view: Table 15-28. and transformation.

Datatype of the metadata extension value. Table 15-30 lists metadata extension information in the REP_METADATA_EXTNS view: Table 15-30. Table 15-29 lists the different views that help you analyze metadata extensions metadata: Table 15-29.Metadata Extension Views Metadata views allow you to see metadata extension details including reusable metadata extensions defined for objects in metadata extension domains. see “REP_METADATA_EXTN_DEFINES” on page 365. Permissions type. Folder ID. Name of the object type. 364 Chapter 15: Using Metadata Exchange (MX) Views . Description of the metadata extension. REP_METADATA_EXTNS This view displays the details of all metadata extensions in the repository. Metadata Extension Views View REP_METADATA_EXTNS REP_METADATA_EXTN_DEFINES Description This view displays the details of all metadata extensions in the repository. Metadata extension name. Line number of the text when there are multiple lines of text. REP_METADATA_EXTNS MX View Column Name OBJECT_ID SUBJECT_ID METADATA_EXTN_NAME METADATA_EXTN_OBJECT_TYPE METADATA_EXTN_OBJECT_ID METADATA_EXTN_DATA_TYPE PERMISSIONS METADATA_EXTN_VALUE LINE_NO METADATA_EXTN_DESCRIPTION VERSION_NUMBER OBJECT_TYPE_NAME DOMAIN_ID DOMAIN_NAME Datatype NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (240) Description Object the metadata is associated with. Unique name for a user-defined metadata domain. For more information. Globally unique domain identifier. Metadata extension value. This view displays reusable metadata extensions defined for objects in metadata extension domains. Object the metadata value is associated with. Object type the metadata is associated with. Object version number. For more information. see “REP_METADATA_EXTNS” on page 364.

Domain description. Name of the database type. REP_METADATA_EXTN_DEFINES This view displays reusable metadata extensions defined for objects in metadata extension domains. Table 15-31 lists information in the REP_METADATA_EXTN_DEFINES view: Table 15-31. Name of the vendor. 2= Domain is editable through client tool. Specifies domain usage. 4 = Domain has full access without a key. Unique name for metadata within a domain. Metadata Extension Views 365 . DOMAIN_DESCRIPTION VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. Description of the metadata extension. REP_METADATA_EXTN_DEFINES MX View Column Name DOMAIN_NAME DOMAIN_ID METAEXT_NAME OBJECT_TYPE_NAME DATABASE_TYPE METAEXT_DESC VENDOR_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) Description Unique name for a user-defined domain Globally unique domain identifier. REP_METADATA_EXTNS MX View Column Name DOMAIN_KEY DOMAIN_USAGE Datatype VARCHAR2 (240) NUMBER Description Domain password. 1= Domain is visible through client tool. Object type name. Informatica recommends using the fields in bold to join views.Table 15-30.

For more information. These views also display properties such as attributes. REP_WIDGET_INST REP_WIDGET_DEP REP_WIDGET_ATTR REP_WIDGET_FIELD REP_ALL_TRANSFORMS This view provides a list of the latest version of all transformations and their properties in each folder of a repository. Folder name. It also shows all shortcut transformations in a folder. and sessions. For more information. This view displays the details of all transformation instances. Folder ID. see “REP_WIDGET_FIELD” on page 369.Transformation Views Transformation views display details of all reusable and non-reusable transformation instances by folder in a PowerCenter repository. This view displays field level details for transformations. Parent folder ID. Parent transformation ID (primary key). For local shortcuts. 366 Chapter 15: Using Metadata Exchange (MX) Views . dependencies. Name of the parent transformation. Transformation Views View REP_ALL_TRANSFORMS Description This view provides a list of the latest version of all transformations and their properties in each folder of a repository. see “REP_ALL_TRANSFORMS” on page 366. This view displays both reusable transformations defined in the Transformation Designer and transformation instances defined in mapping and mapplets. see “REP_WIDGET_ATTR” on page 369. the names of the shortcut and the parent transformation display. This view displays attribute details for transformations. For more information. For more information. the name of the shortcut displays. instances. see “REP_WIDGET_INST” on page 368. For more information. This view displays the details of dependencies between transformation instances in a mapping. For global shortcuts. Table 15-33 lists transformation metadata in the REP_ALL_TRANFORMS view: Table 15-33. Table 15-32 lists the different views that help you analyze transformation metadata: Table 15-32. see “REP_WIDGET_DEP” on page 368. and field level details of transformations. port-level connections. REP_ALL_TRANSFORMS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_WIDGET_NAME PARENT_WIDGET_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Description Parent folder name.

UTC time when the transformation was last saved.Table 15-33. Parent transformation description. Status of the transformation version. 1= reusable. Transformation type ID. Status of the parent transformation version. 1 = shortcut. 0 = not a shortcut. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. UTC time when the transformation was checked in. Name of the transformation. REP_ALL_TRANSFORMS MX View Column Name PARENT_WIDGET_VERSION_NUMBER PARENT_WIDGET_VERSION_STATUS PARENT_WIDGET_UTC_CHECKIN PARENT_WIDGET_UTC_LAST_SAVED PARENT_WIDGET_LAST_SAVED PARENT_WIDGET_IS_REUSABLE PARENT_WIDGET_DESCRIPTION WIDGET_NAME WIDGET_ID WIDGET_VERSION_NUMBER WIDGET_VERSION_STATUS WIDGET_UTC_CHECKIN WIDGET_UTC_LAST_SAVED WIDGET_LAST_SAVED WIDGET_TYPE_ID WIDGET_TYPE_NAME WIDGET_DESCRIPTION REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER Description Parent transformation ID. 0 = not reusable. Transformation ID. UTC time when the parent transformation was last saved. Time when the transformation was last saved. Specifies whether the transformation is a global shortcut. Version number of the transformation. Specifies whether the transformation is a shortcut. Transformation Views 367 . Date and time when transformation was last saved. Repository name. Transformation description. Transformation type name. 1 = shortcut. Specifies whether the transformation is reusable. UTC time (Coordinated Universal Time) when the parent transformation was last checked in. 0 = not a shortcut.

REP_WIDGET_INST MX View Column Name MAPPING_ID WIDGET_ID SUBJECT_ID WIDGET_TYPE WIDGET_TYPE_NAME INSTANCE_ID INSTANCE_NAME COMMENTS VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER Description Mapping ID Transformation ID Folder ID. Name of the transformation instance. 368 Chapter 15: Using Metadata Exchange (MX) Views . Name of the transformation instance. ID of the transformation instance.REP_WIDGET_INST This view displays the details of all transformation instances. Version number of the transformation. Description of the transformation instance. Table 15-35 lists transformation dependency information in the REP_WIDGET_DEP view: Table 15-35. Table 15-34 list transformation metadata in the REP_WIDGET_INST view: Table 15-34. Description of the transformation instance. Transformation name. Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. Transformation type. Version number of the mapping. REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a mapping. Field ID of the target transformation instance. Target field ID. Field ID of the source transformation instance. REP_WIDGET_DEP MX View Column Name MAPPING_ID FROM_INSTANCE_ID FROM_FIELD_ID TO_INSTANCE_ID TO_FIELD_ID INSTANCE_NAME COMMENTS VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER Description Mapping ID Source transformation instance ID.

Attribute ID. Transformation type. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37. Used to break up long strings into multiple rows. instances. instances. Instance ID. Mapping ID. Informatica recommends using the fields in bold to join views. or transformation) version number. Table 15-36 lists attribute details for transformations.REP_WIDGET_ATTR This view displays attribute details for transformations. Session task ID. Table 15-36. Transformation field precision. and sessions. Attribute data type Attribute name. Partition ID. Transformation field name. Object type ID. Attribute type. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID. Transformation Views 369 . Attribute value. REP_EIDGET_ATTR MX View Column Name WIDGET_ID WIDGET_TYPE MAPPING_ID INSTANCE_ID ATTR_ID ATTR_COMMENT ATTR_DATATYPE ATTR_NAME ATTR_TYPE OBJECT_TYPE_ID LINE_NO ATTR_VALUE PARTITION_ID SESSION_TASK_ID VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Transformation ID. Transformation field ID. and sessions. Object (session. mapping. REP_WIDGET_FIELD This view displays field level details for transformations. Description of the attribute.

Table 15-37. Comments on the field. Default value of the transformation field. Transformation port type. 370 Chapter 15: Using Metadata Exchange (MX) Views . Expression name. Transformation datatype of the port. Comments on the expression. Informatica recommends using the fields in bold to join views. Transformation version number. Source field ID for normalizer transformation. Expression type. External database type. Transformation order. Transformation field data type. Field-level property used by transformations. The ID of the corresponding instance in the mapplet's mapping. Datatype number. REP_WIDGET_FIELD MX View Column Name WGT_SCALE WGT_DATATYPE PORTTYPE FIELD_ORDER COMMENTS WIDGET_FLD_PROP DEFAULT_VALUE SRC_FIELD_ID GROUP_ID VERSION_NUMBER DATATYPE_NUM DATATYPE DATATYPE_GROUP_CODE DATABASE_TYPE EXPRESSION EXPR_COMMENT EXPR_TYPE Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (40) CHAR (1) NUMBER VARCHAR2 (2000) VARCHAR2 (2000) NUMBER Description Transformation field scale. Datatype group code.

end time. This view displays the run statistics and folder reference for tasks within a workflow or worklet. and task metadata: Table 15-38. For more information. For more information. and metadata extensions associated with a workflow or a worklet. see “REP_ALL_TASKS” on page 374. and the PowerCenter Server on which a workflow or worklet runs and its run status. For more information. see “REP_TASK_INST_RUN” on page 378. Workflow. tasks. sources and targets defined in a session. This view displays a list of all variables declared within a workflow or worklet. Workflow. and run status. This view displays all task instances within workflows and worklets. Worklet. This view shows how individual tasks and worklets are connected within a worklet or a workflow. see “REP_EVENT” on page 376. connections. This view displays a list of schedulers by folder. end time. see “REP_SESSION_CNXS” on page 381. workflow and worklet execution details such as start time. and Task Views 371 . session connections. This view provides information about reusable sessions in the repository. This view displays the run statistics for all workflows by folder. schedules. For more information. These views also give information on session runtime details like start time. For more information. see “REP_WFLOW_VAR” on page 375. For more information. see “REP_ALL_SCHEDULERS” on page 374.Workflow. see “REP_WFLOW_RUN” on page 379. creation date. see “REP_TASK_INST” on page 377. Worklet. Table 15-38 lists the different views that help you analyze workflow. and metadata extensions associated with a sessions. see “REP_WORKFLOWS” on page 372. worklet. For more information. worklet. The views also provide information on events. This view provides a list of all reusable and non-reusable tasks that can be used by a workflow or a worklet. For more information. and Task Views Workflow. For more information. and Task Views View REP_WORKFLOWS REP_ALL_TASKS REP_ALL_SCHEDULERS REP_WFLOW_VAR REP_EVENT REP_TASK_INST REP_WORKFLOW_DEP REP_TASK_INST_RUN REP_WFLOW_RUN REP_LOAD_SESSIONS REP_SESSION_CNXS Description This view contains information about individual workflows and workflow scheduling. Task views provide both static and run time details about tasks such as sessions created in each folder of a PowerCenter repository. and task views provide both static and run time details about all workflows and worklets created in each folder in a PowerCenter repository. see “REP_WORKFLOW_DEP” on page 377. For more information. These views provide information such as the validity of a session. Worklet. see “REP_LOAD_SESSIONS” on page 380. These views provide information on worklets and sessions inside a workflow. This view displays the details of events created at the workflow or worklet level. For more information. This view contains information about connections associated with reusable sessions.

see “REP_SESS_PARTITION_DEF” on page 385. This view displays session configuration parameter details. see “REP_SESSION_INSTANCE_FILES” on page 383. Start time configured for the scheduler. This view contains file connections associated with reusable sessions. If the session overrides a parameter in the configured object. see “REP_SESS_TBL_LOG” on page 388. Scheduler associated with the workflow. This view contains information about the status of an individual session run against a target. and transformations in a session. Worklet. This view displays the attribute values and overridden values for session and workflow tasks. For more information. see “REP_SESS_LOG” on page 387. For more information. Table 15-39 lists workflow and scheduling information in the REP_WORKFLOWS view: Table 15-39. see “REP_SESSION_INSTANCES” on page 381. For more information. End time configured for the scheduler. REP_TASK_ATTR REP_SESS_LOG REP_SESS_TBL_LOG REP_WORKFLOWS This view contains information about individual workflows and workflow scheduling. For more information. see “REP_SESS_CONFIG_PARM” on page 385. For more information. This view contains file connections associated with reusable sessions. see “REP_SESSION_FILES” on page 382. For more information. This view displays the list of tasks such as a command or an email for each session. For more information. For more information. see “REP_TASK_ATTR” on page 386 This view provides log information about sessions. 372 Chapter 15: Using Metadata Exchange (MX) Views . This view contains information about the sources and targets used in a session. For more information. and Task Views View REP_SESSION_INSTANCES REP_SESSION_FILES REP_SESSION_INSTANCE_F ILES REP_SESS_WIDGET_CNXS REP_COMPONENT REP_SESS_PARTITION_DEF REP_SESS_CONFIG_PARM Description This view contains connection information for session instances. REP_WORKFLOWS MX View Column Name SUBJECT_AREA WORKFLOW_NAME SCHEDULER_NAME START_TIME END_TIME IS_RUN_ON_LIMIT Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) TIMESTAMP TIMESTAMP NUMBER Description Folder name. the view displays two rows. Workflow. targets. This view provides partition details of the sources.Table 15-38. For more information. see “REP_COMPONENT” on page 384. Workflow name. see “REP_SESS_WIDGET_CNXS” on page 383.

4 = Run every DELTA_VALUE seconds. 16 = Run on server initialization. Specifies if scheduler is reusable. Date and time when the workflow was last saved. END_OPTIONS INTEGER RUN_COUNT WORKFLOW_VERSION_NUMBER SCHEDULER_VERSION_NUMBER SUBJECT_ID WORKFLOW_ID WORKFLOW_IS_VALID WORKFLOW_LAST_SAVED WORKFLOW_COMMENTS SCHEDULER_ID SCHEDULER_IS_REUSABLE SCHEDULER_COMMENTS DELTA_VALUE SERVER_NAME SERVER_ID INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER Informatica recommends using the fields in bold to join views. Specifies whether the workflow is valid or not. 2 = Run forever. Workflow. Number of times the PowerCenter Server runs the workflow before stopping the workflow. Description of the workflow. The stop condition option for the workflow schedule type. 2 = Run once. Name of the PowerCenter server registered with the repository. 0 = invalid. Records the following values for each stop condition option: 0 = End on a date. Number of seconds the PowerCenter Server waits between successive workflow runs. REP_WORKFLOWS MX View Column Name RUN_OPTIONS Datatype INTEGER Description The workflow schedule type. Version number of the scheduler.Table 15-39. 1 = End after the number of runs stored in RUN_COUNT. 32 = Run continuously. 8 = Customized repeat. Worklet. PowerCenter Server ID. 1 = valid. Scheduler ID. Workflow version number. Folder ID. Scheduler description. and Task Views 373 . Records the following values for each schedule type: 1 = Run on demand. Workflow ID.

1 = enabled. Table 15-41 lists information in the REP_ALL_SCHEDULERS view: Table 15-41. Values are: 1 = reusable. 0 = invalid. Task name. or session is valid. 0 = not reusable. Folder ID. Task type name. worklet. UTC time when task was last saved. UTC checkin time. REP_ALL_SCHEDULERS MX View Column Name SUBJECT_ID SCHEDULER_ID SCHEDULER_NAME START_TIME Datatype NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (30) Description Folder ID. Version number of the task. Informatica recommends using the fields in bold to join views. Scheduler ID (primary key). REP_ALL_TASKS MX View Column Name SUBJECT_AREA SUBJECT_ID TASK_NAME TASK_ID IS_VALID DESCRIPTION VERSION_NUMBER IS_ENABLED UTC_CHECKIN UTC_LAST_SAVED IS_REUSABLE TASK_TYPE TASK_TYPE_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER NUMBER VARCHAR2 (240) Description Folder name. Description of the task. Specifies whether the task is enabled or not. Name of the scheduler.REP_ALL_TASKS This view provides a list of all reusable and non-reusable tasks that can be used by a workflow or a worklet. REP_ALL_SCHEDULERS This view displays a list of schedulers by folder. Table 15-40 lists reusable and non-reusable task information in the REP_ALL_TASKS view: Table 15-40. Task ID. Task type. Specifies whether the task is reusable or not. 0 = disabled. 374 Chapter 15: Using Metadata Exchange (MX) Views . Start time configured for the object associated with the scheduler. Specifies whether a workflow. 1 = valid.

20 = Run on server init and Delta schedule. REP_ALL_SCHEDULERS MX View Column Name END_TIME RUN_OPTIONS Datatype VARCHAR2 (30) NUMBER Description End time configured for the object associated with the scheduler. 24 = Run on server init and Custom repeat. END_OPTIONS DELTA_VALUE RUN_COUNT DESCRIPTION IS_REUSABLE LAST_SAVED VERSION_NUMBER UTC_LAST_SAVED UTC_CHECKIN NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER Informatica recommends using the fields in bold to join views. Description of the scheduler. 40 = Run continuously and Custom repeat. REP_WFLOW_VAR This view displays a list of all variables declared within a workflow or worklet. Number of workflow runs. Date and time when this task was last saved. The scheduler type. 5 = Run on demand and Delta schedule. Used by END_OPTIONS column. 18 = Run on server init and Run once schedule. UTC time (Coordinated Universal Time) when the scheduler was last saved. UTC checkin time. Version number of the scheduler. Workflow.Table 15-41. Figure 15-42 lists variable information in the REP_WFLOW_VAR view: Table 15-42. Specifies when the task must stop running. 9 = Run on demand and Custom repeat. 3 = Run on demand and Run once schedule. and Task Views 375 . Unique ID for a variable within a workflow (primary key). REP_WFLOW_VAR MX View Column Name SUBJECT_ID WORKFLOW_ID VARIABLE_ID Datatype NUMBER NUMBER NUMBER Description Folder ID. Workflow ID (primary key). Worklet. Records the following values for each schedule type: 1 = Run on demand. 2 = Run once schedule. 34 = Run continuously and Run once schedule. Specifies whether the scheduler is reusable or not. Delta between successive runs (stored as seconds). 36 = Run continuously and Delta schedule.

VARIABLE_DEFAULT_VALUE LAST_SAVED TASK_INST_ID TASK_INST_NAME BIT_OPTIONS VARCHAR2 (2000) VARCHAR2 (30) NUMBER VARCHAR2 (240) NUMBER VERSION_NUMBER NUMBER Informatica recommends using the fields in bold to join views. Comments on the variable. Event description. Datatype of a workflow variable. Workflow ID (primary key). 376 Chapter 15: Using Metadata Exchange (MX) Views . REP_WFLOW_VAR MX View Column Name VARIABLE_NAME VARIABLE_TYPE VARIABLE_DESCRIPTION VARIABLE_DATATYPE Datatype VARCHAR2 (30) NUMBER VARCHAR2 (2000) NUMBER Description Name of the variable. 0 = built in. Date and time that this task was last saved. 1 = user-defined. ID of the instance where the variable is defined. Event type. Variable type. 0 = built in. 2 = workflow variable is NULL. Table 15-43 lists event information in the REP_EVENT view: Table 15-43.Table 15-42. Date and time that this event was last saved. 1 = workflow variable is persistent. Event scope. REP_EVENT MX View Column Name SUBJECT_ID WORKFLOW_ID EVENT_ID EVENT_NAME EVENT_TYPE EVENT_SCOPE EVENT_DESCRIPTION LAST_SAVED Datatype NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (30) Description Folder ID. Event ID (primary key). 1 = user-defined. Name of the event. Name of the task instance. REP_EVENT This view displays the details of events created at the workflow or worklet level. Specifies whether the workflow variable is null or persistent. 3 = decimal 4 = integer 5 = small integer 7 = real 8 = double 11 = date/time 12 = string Default value of a variable. Workflow version number.

Table 15-43. REP_TASK_INST MX View Column Name WORKFLOW_ID INSTANCE_ID TASK_ID TASK_TYPE TASK_TYPE_NAME INSTANCE_NAME IS_ENABLED DESCRIPTION IS_VALID VERSION_NUMBER SERVER_ID Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Workflow ID (primary key). Description of the task. Workflow. Task ID. Table 15-44 lists task instance information in the REP_TASK_INST view: Table 15-44. Informatica recommends using the fields in bold to join views. Instance ID (primary key). REP_TASK_INST This view displays all task instances within workflows and worklets. Task type. REP_EVENT MX View Column Name VERSION_NUMBER Datatype NUMBER Description Workflow version number. 1 = valid. Specifies whether the task is valid. Informatica recommends using the fields in bold to join views. 0 = invalid. REP_WORKFLOW_DEP MX View Column Name WORKFLOW_ID FROM_INSTANCE_ID Datatype NUMBER NUMBER Description Workflow ID. Table 15-45 lists task and worklet connection information in the REP_WORKFLOW_DEP view: Table 15-45. Workflow version number. Server ID associated with the workflow. The ID of the source task instance. Name of the instance. Worklet. Specifies whether the task instance is enabled. and Task Views 377 . Name of the object. REP_WORKFLOW_DEP This view shows how individual tasks and worklets are connected within a worklet or a workflow.

Object name. Name of the task instance. Task error message. The value that identifies the condition associated with the link. Run ID of a child task in a worklet. Run ID of the parent workflow. Table 15-46 lists run statistics and folder reference information in the REP_TASK_INST_RUN view: Table 15-46. Task error code. Version number. REP_TASK_INST_RUN This view displays the run statistics and folder reference for tasks within a workflow or worklet. REP_TASK_INST_RUN MX View Column Name SUBJECT_AREA WORKFLOW_NAME VERSION_NUMBER SUBJECT_ID WORKFLOW_ID WORKFLOW_RUN_ID WORKLET_RUN_ID CHILD_RUN_ID INSTANCE_ID INSTANCE_NAME TASK_ID TASK_TYPE_NAME TASK_TYPE START_TIME END_TIME RUN_ERR_CODE RUN_ERR_MSG Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER DATE DATE NUMBER VARCHAR2 (2000) Description Folder name. ID of an instance within a workflow or a worklet. Start time configured for task execution. REP_WORKFLOW_DEP MX View Column Name TO_INSTANCE_ID CONDITION_ID VERSION_NUMBER CONDITION Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) Description The ID of the target task instance. ID of the parent workflow. Informatica recommends using the fields in bold to join views. 378 Chapter 15: Using Metadata Exchange (MX) Views . Version number. Task ID. Condition ID. Task type. Run ID of a worklet in a workflow. Folder ID.Table 15-45. Workflow name. End time configured for task execution.

PowerCenter Server ID.Table 15-46. End time configured for the workflow. Workflow ID. Full path and name of the log file. 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Task name. Start time configured for the workflow. REP_TASK_INST_RUN MX View Column Name RUN_STATUS_CODE Datatype NUMBER Description Status code of the task. REP_WFLOW_RUN MX View Column Name SUBJECT_ID WORKFLOW_ID WORFLOW_RUN_ID WORKFLOW_NAME SERVER_ID SERVER_NAME START_TIME END_TIME LOG_FILE RUN_ERR_CODE Datatype NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) DATE DATE VARCHAR2 (2000) NUMBER Description Folder ID. Workflow. Workflow name. Task version number. Error message code. Server name. REP_WFLOW_RUN This view displays the run statistics for all workflows by folder. Worklet. TASK_NAME TASK_VERSION_NUMBER SERVER_ID SERVER_NAME VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) Informatica recommends using the fields in bold to join views. Name of the server. ID of the PowerCenter Server. Table 15-47 lists workflow run statistic information in the REP_WFLOW_RUN view: Table 15-47. Workflow run ID. and Task Views 379 .

Session ID. Source ID. REP_LOAD_SESSIONS MX View Column Name SUBJECT_AREA SESSION_NAME LAST_SAVED SESSION_ID MAPPING_NAME VERSION_ID VERSION_NAME IS_ACTIVE STARTTIME SESS_INTERVAL REPEAT_COUNT SESSION_LOG_FILE BAD_FILE_LOCATION TARGET_ID SOURCE_ID SESSION_VERSION_NUMBER MAPPING_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description Folder name. 380 Chapter 15: Using Metadata Exchange (MX) Views . Repeat count. Folder version ID. Name of the user who ran the workflow. Status code for the workflow run. Name of the mapping this session uses. Specifies how the workflow was run. Session start time. Table 15-48 lists reusable session information in the REP_LOAD_SESSIONS view: Table 15-48.Table 15-47. Folder name. Workflow version number. Target ID. REP_WFLOW_RUN MX View Column Name RUN_ERR_MSG RUN_STATUS_CODE USER_NAME RUN_TYPE VERSION_NUMBER SUBJECT_AREA Datatype VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) Description Error message. Session log file name. Location of the reject file. Time the session was last saved. Folder version name. Version number of the session. Name of the session. REP_LOAD_SESSIONS This view provides information about reusable sessions in the repository. Version number of the mapping. Session interval. 1 = Normal. 2 = Recovery. Specifies whether the session is active. Informatica recommends using the fields in bold to join views.

0 = source connection. Session ID. and Task Views 381 . CONNECTION_NAME CONNECTION_ID SESSION_VERSION_NUMBER VARCHAR2 (240) INTEGER NUMBER Informatica recommends using the fields in bold to join views. Workflow. REP_SESSION_CNXS This view contains information about connections associated with reusable sessions. Name of the connection. Table 15-49 lists reusable session connection information in the REP_SESSION_CNXS view: Table 15-49. 1 = target connection. This view does not show connection information for reusable sessions that are not associated with any workflows. Specifies whether the session is valid or not. Version number of the session. REP_SESSION_CNXS MX View Column Name SUBJECT_AREA SUBJECT_ID SESSION_NAME SESSION_ID IS_TARGET Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER Description Folder name in which the session is stored. Sequence ID for the mapping associated with the session. If a session instance overrides the connection information in a reusable session. Connection ID. Specifies whether the connection is the target or the source. 0 = invalid. REP_LOAD_SESSIONS MX View Column Name SUBJECT_ID IS_VALID IS_REUSABLE COMMENTS MAPPING_ID Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER Description Folder ID. Worklet. 1 = valid. Name of the session.Table 15-48. Folder ID. Informatica recommends using the fields in bold to join views. 1= reusable. 0 = not reusable. Specifies whether the session is reusable or not. this view shows the connection in the session instance and the connection information in the reusable session. REP_SESSION_INSTANCES This view contains connection information for session instances. Description of the session.

1 = target connection. 0 = source connection. Name of the connection associated with the session instance. Version number of the session. Name of the session. Session ID. REP_SESSION_FILES This view contains file connections associated with reusable sessions. Table 15-51 lists reusable session file connection information in the REP_SESSION_FILES view: Table 15-51. Workflow version number. Session instance name. 1 = target file connection. Specifies the connection type. Informatica recommends using the fields in bold to join views. REP_SESSION_INSTANCES MX View Column Name SUBJECT_AREA SUBJECT_ID WORKFLOW_NAME WORKFLOW_ID SESSION_INSTANCE_NAME SESSION_INSTANCE_ID SESSION_ID IS_TARGET CONNECTION_NAME CONNECTION_ID WORKFLOW_VERSION_NUMBER SESSION_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER INTEGER VARCHAR2 (240) INTEGER NUMBER NUMBER Description Folder name. Name of the source or target file. Connection ID associated with the session instance. REP_SESSION_FILES MX View Column SUBJECT_AREA SESSION_NAME SESSION_VERSION_NUMBER IS_TARGET FILE_NAME DIR_NAME Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (240) Description Name of the folder containing the session. Session version number.Table 15-50 lists session instance connection information in the REP_SESSION_INSTANCES view: Table 15-50. Directory where the source or target file is stored. Session instance ID. 382 Chapter 15: Using Metadata Exchange (MX) Views . 0 =source file connection. Folder ID. Name of the workflow the session instance belongs to. Specifies the connection type. Workflow ID.

Informatica recommends using the fields in bold to join views. REP_SESS_WIDGET_CNXS MX View Column WIDGET_INSTANCE_ID WIDGET_TYPE INSTANCE_NAME Datatype NUMBER NUMBER VARCHAR2 (240) Description The instance ID of a source.Table 15-51. Identifies a source. or transformation. REP_SESS_WIDGET_CNXS This view contains information about the sources and targets used in a session. Workflow. target. Directory where the source or target file is stored. Instance name. REP_SESSION_INSTANCE_FILES This view contains file connection information for session instances associated with workflows. Workflow version number. Specifies the connection type. REP_SESSION_FILES MX View Column CODE_PAGE Datatype VARCHAR2 (240) Description Code page associated with the source or target file. 1 = target file connection. Code page associated with the source or target file. 0 = source file connection. Table 15-53 lists connection information in the REP_SESS_WIDGET_CNXS view: Table 15-53. target. Worklet. REP_SESSION_INSTANCE_FILES MX View Column SUBJECT_AREA WORKFLOW_NAME WORKFLOW_VERSION_NUMBER SESSION_INSTANCE_NAME IS_TARGET FILE_NAME DIR_NAME CODE_PAGE Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) Description Name of the folder containing the session. Informatica recommends using the fields in bold to join views. If a reusable session is not associated with a workflow. and Task Views 383 . Name of the workflow to which the session instance belongs. this view does not show file connection information for the session. Name of the session instance. The reader and writer types and the connection name also display. Name of the source or target file. Table 15-52 lists session instance file connection information in the REP_SESSION_INSTANCE_FILES view: Table 15-52. or transformation.

Session instance ID. REP_COMPONENT MX View Column WORKFLOW_ID TASK_ID TASK_INST_ID REF_OBJ_TYPE OBJECT_TYPE OBJECT_SEQ_TYPE VERSION_NUMBER PM_VALUE VAL_NAME DESCRIPTION Datatype NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (2000) Description ID of the workflow to which the session belongs. Identifies the referred object's sequence type. Object version number. Description of the value. Type of referenced object. REP_COMPONENT This view displays the list of tasks such as a command or an email for each session. ID of the referenced object. Object type. Informatica recommends using the fields in bold to join views. Indicates whether the object is a reader or a writer. Informatica recommends using the fields in bold to join views. Session instance ID. Component value. Figure 15-54 lists session component information in the REP_COMPONENT view: Table 15-54. Connection name. Transformation instance ID referenced by a session (primary key). 79 = writer. REP_SESS_WIDGET_CNXS MX View Column READER_WRITER_TYPE CNX_NAME SESSION_ID SESSION_WIDG_INST_ID SESS_EXTN_OBJECT_TYPE SESS_EXTN_OBJECT_SUBTYPE SESS_CNX_REFS_OBJECT_TYPE SESS_CNX_REFS_OBJECT_SUBTYPE SESS_CNX_REFS_OBJECT_ID WORKFLOW_ID SESSION_INSTANCE_ID SESSION_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Description Type of reader or writer used. Indicates a specific reader or writer.Table 15-53. Session version number. Session ID. Indicates a specific object. ID of a task within a session. 78 = reader. 384 Chapter 15: Using Metadata Exchange (MX) Views . Name of the value. Workflow ID. Session ID.

If the session overrides a parameter in the configured object. or transformation in a session. Instance ID of a source. Session configuration ID. Partition ID Partition name. Informatica recommends using the fields in bold to join views. and Task Views 385 . Select the row which contains the session ID reference. REP_SESS_PARTITION_DEF MX View Column SESSION_ID SESS_WIDG_INST_ID PARTITION_ID PARTITION_NAME DESCRIPTION LAST_SAVED VERSION_NUMBER MAPPING_ID WIDGET_ID WIDGET_TYPE INSTANCE_ID INSTANCE_NAME TYPE_NAME Datatype NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (30) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Session ID. Object type name. REP_SESS_CONFIG_PARM This view displays session configuration parameter details. target. Session version number. or transformation. Table 15-55 lists partition information in the REP_SESS_PARTITION_DEF view: Table 15-55. ID of the mapping used by the session. Session instance ID. Table 15-56 lists session configuration information in the REP_SESS_CONFIG_PARM view: Table 15-56. ID of a source. Session version number. targets.REP_SESS_PARTITION_DEF This view provides partition details of the sources. Time when the partition was last modified. Worklet. Session configuration attribute ID. REP_SESS_CONFIG_PARM MX View Column SESSION_ID SESSION_VERSION_NUMBER CONFIG_ID ATTR_ID ATTR_TYPE Datatype NUMBER NUMBER NUMBER NUMBER NUMBER Description Session ID. Identifies a source. Description of the partition. target. Session configuration attribute type. and transformations in a session. the view displays two rows. or transformation. target. Instance name. Workflow.

386 Chapter 15: Using Metadata Exchange (MX) Views . Task attribute ID. Task attribute name. Session version number if task attribute is overridden at session level. REP_TASK_ATTR This view displays the attribute values and overridden values for session and workflow tasks. Session ID. Informatica recommends using the fields in bold to join views. Attribute value.Table 15-56. Attribute value. Task ID. Table 15-57 lists attribute information in the REP_TASK_ATTR view: Table 15-57. Task type. Informatica recommends using the fields in bold to join views. Workflow version number if task attribute is overridden at workflow level. Task type name. REP_SESS_CONFIG_PARM MX View Column ATTR_NAME ATTR_VALUE Datatype VARCHAR2 (240) VARCHAR2 (2000) Description Session configuration attribute name. Group ID. Task instance ID. REP_TASK_ATTR MX View Column WORKFLOW_ID INSTANCE_ID TASK_ID TASK_TYPE REF_SESSION_ID TASK_TYPE_NAME ATTR_ID ATTR_NAME ATTR_VALUE LINE_NO GROUP_ID VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Workflow ID. Used for storing multiple lines of attribute values. Line number of attribute values.

which might contain one or many target tables. Number of failed source rows. Location of the reject file. LAST_ERROR_CODE LAST_ERROR TASK_VERSION_NUMBER WORKFLOW_VERSION_NUMBER SESSION_LOG_FILE BAD_FILE_LOCATION SUCCESSFUL_SOURCE_ROWS FAILED_SOURCE_ROWS SUCCESSFUL_ROWS FAILED_ROWS FIRST_ERROR_CODE NUMBER VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Workflow. Session log file name.REP_SESS_LOG This view provides log information about sessions. and Task Views 387 . This view supplies the status of the last session. First error code. Session instance name. Actual time session started. 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Last error code. Run status code. Session ID. Number of failed target rows. Number of successfully read source rows. Worklet. Folder ID. Last error message. Time completed. Workflow version number. REP_SESS_LOG MX View Column SUBJECT_AREA SUBJECT_ID SESSION_ID SESSION_INSTANCE_NAME ACTUAL_START SESSION_TIMESTAMP RUN_STATUS_CODE Datatype VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) DATE (DB SPECIFIC) DATE (DB SPECIFIC) NUMBER Description Folder name. Version number of the task. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. Number of successfully loaded target rows.

Folder ID. 388 Chapter 15: Using Metadata Exchange (MX) Views . row counts. Name of the table for this log. Session instance ID. It provides the last update time. Run ID of a worklet in a workflow. and error status based on a last update timestamp on a per target basis. Name of the workflow that contains the session instance. Session ID. Target instance name for the session. Informatica recommends using the fields in bold to join views. Version number of the target. Business name of the target. Mapping name. Workflow run ID. REP_SESS_LOG MX View Column FIRST_ERROR_MSG WORKFLOW_NAME MAPPING_NAME SESSION_NAME WORKFLOW_ID WORKFLOW_RUN_ID WORKLET_RUN_ID INSTANCE_ID TOTAL_ERR Datatype VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description First error message. Table 15-59 lists individual session information in the REP_SESS_TBL_LOG view: Table 15-59. Workflow version number. Instance ID. Session name. Workflow ID.Table 15-58. REP_SESS_TBL_LOG MX View Column Name SUBJECT_AREA SUBJECT_ID SESSION_NAME SESSION_ID SESSION_INSTANCE_NAME SESSION_INSTANCE_ID WORKFLOW_ID WORKFLOW_VERSION_NUMBER TABLE_NAME TABLE_ID TABLE_VERSION_NUMBER TABLE_BUSNAME TABLE_INSTANCE _NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. Session name. Total error code. Name of the session instance. Target table ID. Workflow ID. REP_SESS_TBL_LOG This view contains information about the status of an individual session run against a target.

Object unique type ID. Last error code. Version number of the session. Number of affected target rows Number of failed target rows. Session timestamp. Time the target load started. Mapplet instance name. Group name. Object name. Performance numbers for the target. Location of the reject file. Worklet. Name of the partition.Table 15-59. Transformation name. Last error message. Time the target load ended. REP_SESS_TBL_LOG MX View Column Name SUCCESSFUL_ROWS SUCCESSFUL_AFFECTED_ROWS FAILED_ROWS LAST_ERROR LAST_ERROR_CODE START_TIME END_TIME SESSION_TIMESTAMP BAD_FILE_LOCATION SESSION_VERSION_NUMBER PARTITION_NAME MAPPLET_INSTANCE_NAME WIDGET_NAME TYPE_NAME GROUP_NAME THROUGHPUT TYPE_ID Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER DATE DATE NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Number of successfully loaded target rows. Informatica recommends using the fields in bold to join views. and Task Views 389 . Workflow.

Informatica recommends using the fields in bold to join views. see “REP_GROUPS” on page 391. REP_USERS MX View Column USER_ID USER_NAME USER_PRIVILEGES1 USER_DESCRIPTION USER_FLAGS CONTACT_INFO IS_VISIBLE USER_ISENABLED USER_EXTERNAL_ID USER_EXTERNAL_LOGIN Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description User ID (primary key). 0 = disabled. User contact information. Unique global user ID. see “REP_USER_GROUPS” on page 391.Security Views Security views allow you to see user and group information such as privileges and contact information. 0 = system-created. User login ID used by external authentication modules. Description of the user. Specifies whether user can log in. Security Views View REP_USERS REP_USER_GROUPS REP_GROUPS Description This view provides a list of all PowerCenter users along with details on user privileges and contact information. This view provides a list of PowerCenter groups along with details on group privileges and contact information. Specifies whether user is valid. This view provides association details between PowerCenter users and the group to which they belong. 390 Chapter 15: Using Metadata Exchange (MX) Views . Table 15-60 lists the different views that help you analyze security metadata: Table 15-60. 1 = valid. Table 15-61 lists user information in the REP_USERS view: Table 15-61. see “REP_USERS” on page 390. User name. 1 = enabled. Specifies whether the user is system-created or usercreated. For more information. 1 = user-created. Privileges granted to the user. For more information. 0 = deleted. REP_USERS This view provides a list of all PowerCenter users along with details on user privileges and contact information. For more information.

Group privileges. Contact information for the group. REP_GROUPS This view provides a list of PowerCenter groups along with details on group privileges and contact information. Informatica recommends using the fields in bold to join views. Table 15-62 lists group association information in the REP_USER_GROUPS view: Table 15-62. REP_GROUPS MX View Column GROUP_ID GROUP_NAME GROUP_PRIVILEGES GROUP_DESCRIPTION GROUP_FLAGS Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER Description Group ID (primary key).REP_USER_GROUPS This view provides an association between PowerCenter users and the group to which they belong. Table 15-63 lists group information in the REP_GROUPS view: Table 15-63. Specifies whether the group is system-created or usercreated. 0 = system-created. Group description. Group name. 1 = user-created. REP_USER_GROUPS MX View Column USER_ID GROUP_ID Datatype NUMBER NUMBER Description User ID. CONTACT_INFO VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. Group ID. Security Views 391 .

Query user. Table 15-64 lists the different views that help you analyze deployment metadata: Table 15-64. 392 Chapter 15: Using Metadata Exchange (MX) Views . For more information. 0 = static. and objects which were deployed from one repository to another. Name of user who created the deployment group. Group ID. Query ID associated with a dynamic group. Query description. Deployment group name. see “REP_DEPLOY_GROUP_DETAIL” on page 393. Creation time. This view provides Change Management deployment details. Last saved time. Query group ID. source and target repository names associated with deployment. Deployment Views View REP_DEPLOY_GROUP REP_DEPLOY_GROUP_DETAIL Description This view provides information on deployment group in Change Management.Deployment Views Deployment views allow you to see deployment information such as deployment groups. deployment date. 1 = dynamic. Name of user who created the query. Table 15-65 lists deployment group information in the REP_DEPLOY_GROUP view: Table 15-65. see “REP_DEPLOY_GROUP” on page 392. Query name associated with a dynamic group. For more information. REP_DEPLOY_GROUP MX View Column DEP_GROUP_ID DEP_GROUP_NAME DESCRIPTION CREATED_BY OWNER_ID GROUP_ID CREATION_TIME LAST_SAVED GROUP_TYPE QUERY_ID QUERY_NAME QUERY_DESCRIPTION QUERY_CREATED_BY QUERY_OWNER_ID QUERY_GROUP_ID Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (30) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Deployment group ID. Description of the group. REP_DEPLOY_GROUP This view provides information on deployment groups. User ID. Deployment group type.

Target repository name. 0 = invalid. REP_DEPLOY_GROUP_DETAIL MX View Column DEP_RUN_ID OBJECT_ID OBJECT_NAME OBJECT_TYPE OBJECT_TYPE_NAME SRC_VERSION_NUMBER TARG_VERSION_NUMBER SRC_SUBJECT_ID SRC_SUBJECT_AREA TARG_SUBJECT_AREA IS_SHORTCUT DEP_GROUP_ID DEP_GROUP_NAME DEPLOY_TIME DEPLOY_TYPE Datatype NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Unique deployment run ID. Specifies whether the object is a shortcut. Informatica recommends using the fields in bold to join views. Name of the object. TARGET_REP_NAME REP_GID USER_ID VARCHAR2 (240) VARCHAR2 (240) NUMBER Deployment Views 393 . Query last saved time. Deployment start time. 1 = public. 0 = not a shortcut Deployment group ID. Query type. Folder name in the target repository.Table 15-65. REP_DEPLOY_GROUP MX View Column QUERY_CREATION_TIME QUERY_LAST_SAVED QUERY_TYPE Datatype VARCHAR2 (30) VARCHAR2 (30) NUMBER Description Query creation time. Deployment type. Deployment group name. Object type. Folder name in the source repository. 1 = shortcut. Global ID of the repository. Object version number in the target repository. REP_DEPLOY_GROUP_DETAIL This view provides deployment details. Object type name. Deployment user ID. Object ID. 1 = deploy to. 2 = deploy from. Table 15-66 lists deployment information in the REP_DEPLOY_GROUP_DETAIL view: Table 15-66. Folder ID in the source repository. Object version number in the source repository. 2 = personal.

Deployment rollback time. ROLLBACK_TIME NUMBER Informatica recommends using the fields in bold to join views. 2 = rollback failed. REP_DEPLOY_GROUP_DETAIL MX View Column GROUP_ID USER_NAME UTC_DEPLOY_TIME DEPLOY_STATUS Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Group ID. UTC deployment time. Deployment user name. 0 = deployed. 394 Chapter 15: Using Metadata Exchange (MX) Views . 1 = rollback. Deployment status.Table 15-66.

2 = standalone. Repository type. DOMAIN_NAME DATABASE_USER DATABASE_TYPE HOSTNAME PORTNUM VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Informatica recommends using the fields in bold to join views. Repository ID. Repository name. REP_REPOSIT_INFO MX View Column RECID REPOSIT_NAME REPOSIT_DESCRIPTION REPOSITORY_ID REPOSITORY_TYPE Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER NUMBER Description Repository record ID. 1 = global. Description of the repository. Table 15-67 lists repository information in the REP_REPOSIT_INFO view: Table 15-67. Repository type. MX provides the REP_REPOSIT_INFO view to help you analyze repository metadata. Global domain name. Repository View 395 . 3 = local. REP_REPOSIT_INFO This view provides repository information such as repository name and type. domain name. and database type. and whether the repository is local or global. Database user name used to connect to the repository. database type. Port number of the Repository Server. Name of the machine hosting the Repository Server. connection information on which the repository is created.Repository View The repository view allows you to see repository name.

see “REP_REPOSIT_INFO” on page 395. For more information. Table 15-69 lists PowerCenter Server information in the REP_SERVER_INFO view: Table 15-69.PowerCenter Server Views The PowerCenter Server views allow you to see information about PowerCenter Server resources. and recent activity. Port number of the machine hosting the PowerCenter Server. and timeout. REP_SERVER_INFO MX View Column SERVER_ID SERVER_NAME HOST_INFO TIMEOUT PORT_NO HOSTNAME IP_ADDRESS LAST_SAVED Datatype NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (30) Description PowerCenter Server ID (primary key). see “REP_SERVER_NET_REF” on page 397. PowerCenter Server Views View REP_SERVER_INFO Description This view provides information about PowerCenter Server name. and usage. The views allow you to see information about your server grid. This view provides information about PowerCenter Server identification and usage. Informatica recommends using the fields in bold to join views. host name. Time when an object was last saved. 396 Chapter 15: Using Metadata Exchange (MX) Views . IP address of the host machine. IP address. see “REP_SERVER_NET” on page 397. such as the server name and host name that can be used to run workflows in PowerCenter. host name. IP address. For more information. For more information. Information on the machine hosting the PowerCenter Server. Name of the machine hosting the PowerCenter Server. descriptions. PowerCenter Server name. REP_SERVER_NET REP_SERVER_NET_REF REP_SERVER_INFO This view provides PowerCenter Server information such as server name. Table 15-68 lists the different views that help you analyze server resources and your access to them: Table 15-68. such as server locations. Specified timeout when attempting to communicate with the server. This view provides information on PowerCenter Server description. location. and timeout.

REP_SERVER_NET MX View Column SERVER_NET_ID SERVER_NET_NAME SERVER_NET_DESCRIPTION LAST_SAVED Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (30) Description Server ID within the grid (primary key). Description of the server. PowerCenter Server ID (primary key). Server name. Use network = 1. Table 15-70 lists PowerCenter Server information in the REP_SERVER_NET view: Table 15-70. Time when the server was last saved. REP_SERVER_NET_REF MX View Column SERVER_NET_ID SERVER_ID BIT_OPTIONS Datatype NUMBER NUMBER NUMBER Description PowerCenter Server ID within the grid (primary key). PowerCenter Server job distribution options. Informatica recommends using the fields in bold to join views. Use network and used by network = 3. REP_SERVER_NET_REF This view provides PowerCenter Server identification within the grid and usage information. Table 15-71 lists PowerCenter Server identification and usage information within the grid in the REP_SERVER_NET_REF view: Table 15-71. Informatica recommends using the fields in bold to join views.REP_SERVER_NET This view provides PowerCenter Server grid information and provides description and usage information. PowerCenter Server Views 397 .

mapplets. Change Management Views View REP_VERSION_PROPS REP_CM_LABEL REP_CM_LABEL_REF Description Provides information on the version history of all objects in a PowerCenter repository. and tasks. Table 15-73 lists label information in the REP_VERSION_PROPS view: Table 15-73. transformations. 398 Chapter 15: Using Metadata Exchange (MX) Views .Change Management Views Change Management views allow you to see the version history of all objects in a PowerCenter repository and label metadata. Object type ID (primary key). Description of the object. For more information. Object subtype ID. User who last modified this version of the object. mappings. REP_VERSION_PROPS This view provides the version history of all objects in a PowerCenter repository. workflows. sessions. Time when object was last saved. For more information. Name of the object. Host machine name from which the version of the object is saved. UTC time when the object was last modified. Table 15-72 lists the different views that help you analyze version history of objects and label metadata: Table 15-72. Objects can be defined as tables. Database name used by source objects. Labels can be defined on all objects. Provides information on labels in Change Management. REP_VERSION_PROPS MX View Column OBJECT_ID OBJECT_TYPE OBJECT_SUBTYPE VERSION_NUMBER SUBJECT_ID USER_ID OBJECT_NAME GROUP_NAME LAST_SAVED UTC_LAST_SAVED COMMENTS SAVED_FROM Datatype NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (30) NUMBER VARCHAR2 (2000) VARCHAR2(240) Description Object ID. Folder ID. see “REP_CM_LABEL_REF” on page 399. see “REP_VERSION_PROPS” on page 398. worklets. For more information. see “REP_CM_LABEL” on page 399. Object version number. Provides information on label details in Change Management.

Table 15-74 lists label information in the REP_CM_LABEL view: Table 15-74. Time when label was last saved. REP_CM_LABEL_REF This view provides information on label details. Change Management Views 399 . Name of user who created the label. Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. Object version number. User ID. Object ID. 2 = Can apply label to only one version of the object. Table 15-75 lists label information in the REP_CM_LABEL_REF view: Table 15-75. REP_CM_LABEL_REF MX View Column LABEL_ID OBJECT_ID OBJECT_TYPE VERSION_NUMBER SUBJECT_ID Datatype NUMBER NUMBER NUMBER NUMBER NUMBER Description Label ID. Label status.Table 15-73. 1 = label unlocked. Label name. Label description. 2 = label locked. Folder ID. REP_VERSION_PROPS MX View Column PURGED_BY_USERID Datatype NUMBER Description User ID who purged the object from the repository. REP_CM_LABEL This view provides label information. Label creation time. Group ID. Label type. REP_CM_LABEL MX View Column LABEL_ID LABEL_NAME DESCRIPTION CREATED_BY OWNER_ID GROUP_ID CREATION_TIME LAST_SAVED LABEL_TYPE LABEL_STATUS Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (30) NUMBER NUMBER Description Label ID. Object type ID.

Informatica recommends using the fields in bold to join views. Label description.Table 15-75. Time when label was applied to the object. 400 Chapter 15: Using Metadata Exchange (MX) Views . REP_CM_LABEL_REF MX View Column USER_ID DESCRIPTION APPLY_TIME Datatype NUMBER VARCHAR2 (2000) VARCHAR2 (30) Description User ID.

ID. MX provides the REP_SUBJECT view to help you analyze folder metadata: REP_SUBJECT This view displays folder information such as folder name and description. Folder View 401 . REP_SUBJECT MX View Column SUBJECT_AREA SUBJECT_ID DESCRIPTION Datatype VARCHAR2 (240) NUMBER VARCHAR2 (2000) Description Folder name. Folder ID. Folder description. It describes the name. Table 15-76 lists folder information in the REP_SUBJECT view: Table 15-76.Folder View The folder view allows you to see all the folders defined in the PowerCenter repository. Informatica recommends using the fields in bold to join views. and description of each folder.

402 Chapter 15: Using Metadata Exchange (MX) Views .

491 Tips. 407 pmrep System Commands.Chapter 16 Using pmrep and pmrepagent This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 410 pmrep Repository Commands. 406 Running Commands in Interactive Mode. 412 pmrep Security Commands. 404 Running Commands in Command Line Mode. 492 403 . 460 pmrepagent Commands. 406 Specifying Options and Arguments. 449 pmrep Change Management Commands. 477 Scripting pmrep and pmrepagent Commands.

When you use pmrep and pmrepagent.Overview pmrep and pmrepagent are command line programs that you use to update repository information and perform repository functions. For more information on pmrepagent commands. and exit pmrep. Add. Use system commands when you work with pmrep repository and security commands. clean up persistent resources. see “pmrep Repository Commands” on page 412. Connect to the repository. change connection names. Using Native Connect Strings Some pmrep and pmrepagent commands. such as pmrep CreateConnection and pmrepagent Restore. see “pmrepagent Commands” on page 477. and update server variables. see “pmrep Change Management Commands” on page 460. see “Running Commands” on page 406. require a native connect string. see “pmrep System Commands” on page 410. Security commands. Add or remove user and group privileges. For more information on repository commands. For more information on running commands in these modes. create relational connections. such as restoring repositories. copy. Using pmrep Use pmrep to update session-related parameters and security information in the Informatica PowerCenter repository. Repository commands. Check in objects. update session notification email addresses. Change management commands. pmrep and pmrepagent install in the Repository Server installation directory and also in the PowerCenter Client installation directory. Import or export objects. pmrepagent runs in command line mode only. Execute queries. Edit user profiles and password information. Back up a repository. get help information. You can use pmrep in either command line mode or interactive mode. For more details on change management commands. 404 Chapter 16: Using pmrep and pmrepagent . ♦ ♦ ♦ Using pmrepagent Use pmrepagent to perform repository functions. Add or delete labels. you can enter commands in interactive mode or command line mode. or delete deployment groups. For more details on security commands. see “pmrep Security Commands” on page 449. Add or remove users and groups. pmrep uses the following types of commands to perform repository tasks: ♦ System commands. For more information on system commands.

Overview 405 .world sambrown@mydatabase TeradataODBC TeradataODBC@mydatabase TeradataODBC@jsmith *Use Teradata ODBC drivers to connect to source and target databases.Table 16-1 lists the native connect string syntax for each supported database when you create or update connections: Table 16-1. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.world (same as TNSNAMES entry) servername@dbname ODBC_data_source_name or ODBC_data_source_name@db_name or ODBC_data_source_name@db_user_name Example mydatabase mydatabase@informix sqlserver@mydatabase oracle.

. scripts. For more information on scripting pmrep or pmrepagent commands. At the command prompt. Running Commands in Interactive Mode The interactive mode invokes pmrep and allows you to issue a series of commands from a pmrep prompt without exiting after each command. The command line mode is useful if you want to run pmrep or pmrepagent commands through batch files. switch to the directory where the pmrep executable is located. To run pmrep commands in interactive mode: 1. At the command prompt. 406 Chapter 16: Using pmrep and pmrepagent .. Enter pmrep at the command prompt to invoke interactive mode. To run pmrep commands in command line mode: 1. 3. You can issue pmrep and pmrepagent commands directly from the system command line. type the following command to run pmrepagent: pmrepagent command_name [-option1] argument_1 [-option2] argument_2. At the command prompt. Command line mode. you can enter commands in interactive mode or command line mode.. You cannot use pmrepagent in interactive mode. pmrep does not exit after it completes a command. or other programs. ♦ ♦ Interactive mode. To run pmrepagent commands in command line mode: 1. type the following command to run pmrep: pmrep command_name [-option1] argument_1 [-option2] argument_2. 2. At the command prompt. Enter pmrepagent followed by the command name and its required options and arguments. Enter pmrep followed by the command name and its required options and arguments. switch to the directory where the pmrepagent executable is located. You can issue pmrep commands from an interactive prompt. Running Commands in Command Line Mode The command line mode invokes and exits pmrep or pmrepagent each time you issue a command. The Command syntax contains options and arguments you use when you specify commands.Running Commands When you use pmrep and pmrepagent. 3. You can use command line mode to script pmrep and pmrepagent commands. see “Scripting pmrep and pmrepagent Commands” on page 491.. 2.

you must provide the name of the repository when using the connect command: connect -r production ♦ Specify options in any order. both of the following commands are valid: connect -r production -n sambrown connect -n sambrown -r production ♦ Options are case-sensitive when the command contains an upper-case and lower-case option. Option Arguments Use the following rules to specify arguments: ♦ The first word after the option letter is considered the argument. pmrep and pmrepagent ignore quotes that do not enclose an argument. Specifying Options and Arguments Commands in pmrep and pmrepagent may require you to specify options and arguments. For example.This starts pmrep in interactive mode and displays a pmrep> prompt. At the pmrep> prompt. pmrep runs the command and displays the pmrep> prompt again.. An option and its argument do not have to be separated by a space. For example. 3. For example. such as -x and -X.. Back quotes (‘) are not allowed. Type a command and its options and arguments. type: command_name [-option1] argument_1 [-option2] argument_2. you can use both of the following Connect commands to connect to a repository: connect -r production connect -rproduction ♦ If any argument for an option or command contains more than one word. You do not have to type pmrep before each command in interactive mode. Options Use the following rules when you specify command options and arguments: ♦ Specify options by typing a minus sign followed by a letter. Commands fail and display an error message if any required option or argument is missing or not specified. you must enclose the argument in double quotes. as shown using the Connect command: connect -r ♦ Most options require arguments. Running Commands 407 ♦ . Type exit to end an interactive session. 2.

The password is an encrypted value. At the shell prompt. 2. Use the environment variable with the appropriate pmrep. the password entered was “monday. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. 2. type: setenv PASSWORD YourEncryptedPassword 408 Chapter 16: Using pmrep and pmrepagent . In a UNIX session. and Backup. 3.” Encrypted string -->bX34dqq<-Will decrypt to -->monday<-- Your encrypted password is bX34dqq. and pmrepserver in scripts. To encrypt a password: 1. Create. pmrepagent. or pmrepserver command. For more details on the pmrepserver command. The following is sample output. You may want to encrypt your repository password to maintain security when you use pmrep. Use the command line program. When you use password environment variables. pmpasswd. Configure the PASSWORD environment variable to set the encrypted value. to encrypt your repository password.Using Password Environment Variables Some pmrep commands use password environment variable options. Use the following steps as a guideline to use an encrypted password as an environment variable: 1. To configure a password environment variable: If you are in a UNIX C shell environment. type: pmpasswd YourPassword This command runs the encryption utility pmpasswd located in the PowerCenter Server installation directory. pmrepagent. The encryption utility generates and displays your encrypted password. In this example. navigate to the PowerCenter Server installation directory. you must encrypt your repository password. You can use the PASSWORD environment variable for commands such as Connect. Configuring Repository Passwords on UNIX You can enter your repository password at the command line as an environment variable. You set the password on the PowerCenter Repository Server and encrypt it with the pmpasswd utility.

2. Enter environment variables in the Windows System Properties.” Encrypted string -->bX34dqq<-Will decrypt to -->monday<-- Your encrypted password is bX34dqq. the password entered was “monday. The following is sample output. 2. For information about setting environment variables for your Windows operating system. At the command line. navigate to the PowerCenter Server installation directory. To configure a password environment variable: 1. type: PASSWORD= YourEncryptedPassword export PASSWORD You can assign the environment variable any valid UNIX name. Enter your encrypted password in the Value field. To encrypt a password: 1. User variables take precedence over system variables. consult your Windows documentation. You can set these up as either a user or system variable. The password is an encrypted value.If you are in a UNIX Bourne shell environment. Configuring Repository Passwords on Windows You can enter your repository password at the command line as an environment variable. In Windows DOS. type: pmpasswd YourPassword The encryption utility generates and displays your encrypted password. Using Password Environment Variables 409 . In this example. Enter the name of your password environment variable in the Variable field.

See “Getting Help (Help)” on page 411. Connect Options and Arguments (pmrep) Option -r -n -x -X -h -o Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Argument Name repository_name repository_username repository_password repository_password_ environment_variable repserver_host_name repserver_port_number Argument Description Name of the repository you want to connect to. Use the -x or -X option. Cleans up persistent resources created by pmrep during a session. Password for the repository user name. but not both. Displays help for all commands or for a specified command. See “Cleaning up Persistent Resources (Cleanup)” on page 411. “Exiting pmrep (Exit)” on page 411. pmrep System Commands pmrep Command Connect Help Cleanup Exit Command Description Connects to the repository. 410 Chapter 16: Using pmrep and pmrepagent . All commands require a connection to the repository. but not both. Repository user name used to connect to the repository. Use the -x or -X option. Exits from pmrep. The port number the Repository Server uses for connections. The password environment variable for the repository. Connect uses the following command syntax: connect -r repository_name -n repository_username -x repository_password -X repository_password_environment_variable -h repserver_host_name -o repserver_port_number Table 16-3 lists pmrep Connect options and arguments: Table 16-3. See “Connecting to a Repository (Connect)” on page 410. Connecting to a Repository (Connect) The first time you use pmrep in either command line or interactive mode.pmrep System Commands This section describes basic pmrep commands that you use in conjunction with other pmrep repository and security commands. The host name of the machine running the Repository Server. Table 16-2 lists pmrep system commands: Table 16-2. you must call the Connect command.

and you are not connected to that repository.In the command line mode. The help information printed to the screen shows the command name. it returns an error. and specifies which arguments to provide. options. The command line mode invokes and exits pmrep each time you issue a command. If you call Cleanup in the interactive mode. pmrep disconnects from the first repository and then connects to the second repository. type exit. To exit the pmrep interactive mode. If you call Connect again. In command line mode. pmrep connects to and disconnects from the repository with every command. If you use pmrep to perform tasks in multiple repositories in a single session. pmrep retains the connection until you exit pmrep or connect again. the previous connection remains disconnected and you will not be connected to any repository. If you issue a command that requires a connection to the repository. If pmrep is called without a successful connect. pmrep System Commands 411 . To clean up persistent resources. pmrep uses the connection information specified in the last successful connection made to the repository from any previous session of pmrep. Informatica recommends calling Cleanup in the command line mode only. If the second connection fails. pmrep retains information from the last successful connection until you use the Cleanup command. pmrep disconnects any repository you are connected to. Calling Cleanup as the first command in a session always returns an error. Help uses the following command syntax: help [command] Cleaning up Persistent Resources (Cleanup) The Cleanup command cleans up any persistent resource created by pmrep. pmrep uses the information specified by the last call to connect to the repository. use the following syntax: cleanup Exiting pmrep (Exit) The Exit command exits from the pmrep interactive mode. you must issue the Connect command each time you want to switch to a different repository. In the interactive mode. This command also cleans up any connection information from previous sessions of pmrep. Getting Help (Help) The Help command prints help for all commands or for a specified command.

pmrep Repository Commands
pmrep allows you to perform repository administration tasks, such as backing up the repository, creating relational connections, and updating PowerCenter Server variables. Table 16-4 describes pmrep repository administration commands:
Table 16-4. pmrep Repository Commands pmrep Command Addserver Addrepository Backup CreateConnection Deleteconnection Deleteserver Disablerepository Enablerepository ListObjects Listtablesbysess ListObjectDependencies Notify ObjectExport ObjectImport Register Removerepository Run Command Description Adds a PowerCenter Server. See “Adding a Server (Addserver)” on page 413. Adds a repository configuration to the Repository Server. See “Adding Repository Configurations (Addrepository)” on page 414. Backs up a repository. See “Backing up a Repository (Backup)” on page 416. Creates a relational connection. See “Creating a Relational Connection (CreateConnection)” on page 417. Deletes an existing relational connection. See “Deleting a Connection (Deleteconnection)” on page 420. Deletes a PowerCenter Server. See “Deleting a Server (Deleteserver)” on page 421. Disables a repository. See “Disabling a Repository (Disablerepository)” on page 421. Enables a repository. See “Enabling a Repository (Enablerepository)” on page 422. Lists objects in the repository. See “Listing Repository Objects (ListObjects)” on page 423. Lists sources or targets in a session. See “Listing Tables by Session (Listtablesbysess)” on page 428. Lists dependent objects. See “Listing Object Dependencies (ListObjectDependencies)” on page 429. Sends notification messages. See “Sending Notification Messages (Notify)” on page 431. Exports objects to an XML file. See “Exporting Objects (ObjectExport)” on page 432. Imports objects from an XML file. See “Importing Objects (ObjectImport)” on page 433. Registers local repositories with global repositories. See “Registering Local Repositories (Register)” on page 434. Removes a repository from the Repository Server cache entry list. See “Removing Repositories From the Cache (Removerepository)” on page 435. Displays messages stating whether a run has completed or failed. See “Running Script Files (Run)” on page 436.

412

Chapter 16: Using pmrep and pmrepagent

Table 16-4. pmrep Repository Commands pmrep Command ShowConnectioninfo Command Description Shows repository name, server, port and user information for the current connection. See “Showing Connection Information (ShowConnectioninfo)” on page 437. Stops the repository you last connected to using pmrep. See “Stopping a Repository (StopRepository)” on page 437. Changes the name of an existing connection. See “Changing the Connection Name (SwitchConnection)” on page 438. Truncates log details from repository level, folder level, or workflow level. See “Truncating Workflow and Session Logs (Truncatelog)” on page 439. Unregisters local repositories from global repositories. See “Unregistering Local Repositories (Unregister)” on page 440. Changes user name, password, and connect string for a connection. See “Updating a Database Connection (UpdateConnection)” on page 441. Updates the session notification email addresses. See “Updating the Notification Email Addresses (Updateemailaddr)” on page 442. Updates transformation properties for Sequence Generator transformations. See “Updating Sequence Generator Transformations (Updateseqgenvals)” on page 444. Edit server details. See “Updating Server Details (Updateserver)” on page 443. Updates source table owner names. See “Updating the Source Table Owner Name (Updatesrcprefix)” on page 445. Updates server variables. See “Updating Server Variables (Updatesrvvar)” on page 446. Updates statistics for repository tables and indexes. See “Updating Repository Statistics (UpdateStatistics)” on page 447. Updates target table name prefixes. See “Updating the Target Table Name Prefix (Updatetargprefix)” on page 447.

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

Adding a Server (Addserver)
Use the Addserver command to add PowerCenter Servers. For more information about adding a PowerCenter Server see “Registering the PowerCenter Server” in the Installation and Configuration Guide. To add a server, you must have the Administer Repository privilege. Addserver uses the following command syntax:
addserver -v server_name -h new_host_name -o new_port_number -t new_timeout_value -p new_protocol_name -l new_codepage_name

pmrep Repository Commands

413

Table 16-5 lists pmrep Addserver options and arguments:
Table 16-5. Addserver Options and Arguments (pmrep) Option -v -h -o -t -p -l Required/ Optional Required Required Optional Optional Optional Optional Argument Name server_name new_host_name new_port_number new_timeout_value new_protocol_name new_codepage_name Argument Description The name of the PowerCenter Server you want to change. The server host name or IP address of the server machine. The port number of the server machine. The number of seconds the Workflow Manager waits for a response from the server. The protocol the server uses. The character set associated with the PowerCenter Server. Select the code page identical to the PowerCenter Server operating system code page. Must be identical to or compatible with the repository code page.

Adding Repository Configurations (Addrepository)
The Addrepository command adds repository configurations to the Repository Server. You might use Addrepository to add a repository configuration after restoring or creating a repository in the database using pmrepagent. When you add a repository configuration, pmrep connects to the Repository Server and adds a configuration file to the Repository Server installation directory. You do not need to connect to a repository to use this command.
Note: To configure other repository options, edit the repository configuration in the

Repository Server Administration Console. For more information on adding and editing repository configurations, see “Adding a Repository Configuration” on page 105. Addrepository uses the following command syntax:
addrepository -h repserver_host_name -o repserver_port_number -a repserver_password -A repserver_password_environment_variable -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -d code_page -e DB2_tablespace_name -l license_file_name

414

Chapter 16: Using pmrep and pmrepagent

Table 16-6 lists pmrep Addrepository options and arguments:
Table 16-6. Addrepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required Argument Name repserver_host_name repserver_port_number repserver_password Argument Description The host name of the Repository Server that manages the repository. The port number of the Repository Server that manages the repository. The password you use to administer the Repository Server that manages the repository. Use the -a or -A option, but not both. The password environment variable you use to administer the Repository Server that manages the repository. Use the -a or -A option, but not both. The name of the repository. The type of database storing the repository. The account for the database containing the repository. Set up this account using the appropriate database client tools. Use a trusted connection to connect to the database. Valid for Microsoft SQL Server only. The repository database password corresponding to the database user. Must be in 7-bit ASCII. Not required if you are using option -m. Use the -p or -P option, but not both. The repository database password environment variable corresponding to the database user. Must be in 7-bit ASCII. Not required if you are using option -m. Use the -p or -P option, but not both. The native connect string the Repository Server uses to access the database containing the repository. For information on connect string syntax, see Table 16-1 on page 405. The repository code page. The Repository Server uses the character set encoded in the repository code page when writing data to the repository. If you omit this option, pmrep uses the code page of the global locale for the Repository Server.

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

Table 16-6. Addrepository Options and Arguments (pmrep) Option -e Required/ Optional Optional Argument Name DB2_tablespace_name Argument Description The tablespace name for IBM DB2 repositories. When you specify the tablespace name, the Repository Server creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name. Use the same tablespace name with this command and the pmrepagent Create and Restore commands. To improve repository performance on IBM DB2 EEE repositories, use a tablespace name with a single node. For more information on specifying the tablespace name, see “Adding a Repository Configuration” on page 105. The name of the license file.

-l

Optional

license_file_name

Backing up a Repository (Backup)
The Backup command backs up the repository to the file specified with the -o option. You must provide the backup filename. You can use this command when the repository is running. You must be connected to a repository to use this command. Backup uses the following command syntax:
backup -o output_file_name -f -d description -b skip_workflow/ session_logs -j skip_deploy_group_history -q skip_MX_data

Table 16-7 lists pmrep Backup options and arguments:
Table 16-7. Backup Options and Arguments (pmrep) Option -o -f -d Required/ Optional Required Optional Optional Argument Name output_file_name n/a description Argument Description The name and path of the file for the repository backup. Overwrites an existing file with the same name. Creates a description of the backup file based on the string that follows the option. The backup process truncates any character beyond 2,000. Specify this option if you want to skip tables related to workflow and session logs during backup. Skips deployment group history during backup. Skips tables related to MX data during backup.

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

To restore the backup file, use the Repository Manager Administration Console, or use the pmrepagent Restore command. For details, see “Restoring a Repository (Restore)” on page 485.

416

Chapter 16: Using pmrep and pmrepagent

Note: You can also use the pmrepagent Backup command to back up a repository that is not

running. For details, see “Backing up a Repository (Backup)” on page 477.

Creating a Relational Connection (CreateConnection)
The CreateConnection command creates a relational source or target connection in the repository. You must be connected to a repository to use this command. Relational database connections for each relational subtype require a subset of all CreateConnection options and arguments. For example, Oracle connections do not accept the -z, -d, or -t options. CreateConnection uses the following command syntax:
createconnection -a data_source_name -s database_type -n connection_name -u username -p password -P password_environment_variable -c connect_string -l code_page -r rollback_segment -e environment_sql -z packet_size -b database_name -v server_name -d domain_name -t trusted_connection -x

Table 16-8 lists pmrep CreateConnection options and arguments:
Table 16-8. CreateConnection Options and Arguments (pmrep) Option -a -s -n -u -p Required/ Optional Required Required Required Required Required/ Optional Required/ Optional Required Argument Name data_source_name database_type connection_name username password Argument Description The Teradata ODBC data source name. Valid for Teradata connections only. The type of relational connection. For a list of valid database types, see Table 16-9 on page 418. The name of the connection. The user name used for authentication when you connect to the relational database. The password used for authentication when you connect to the relational database. Use the -p or -P option, but not both. The password environment variable used for authentication when you connect to the relational database. Use the -p or -P option, but not both. The connect string the PowerCenter Server uses to connect to the relational database. For a list of native connect strings, see Table 16-1 on page 405. The code page associated with the connection. For a list of valid code page IDs, see Table 16-10 on page 419. Valid for Oracle connections only. The name of the rollback segment. A rollback segment records database transactions that allow you to undo the transaction.

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

Table 16-8. CreateConnection Options and Arguments (pmrep) Option -e -z Required/ Optional Optional Optional Argument Name environment_sql packet_size Argument Description Enter SQL commands to set the database environment when you connect to the database. Valid for Sybase and Microsoft SQL Server connections only. Optimizes the ODBC connection to Sybase and Microsoft SQL Server. The name of the database. Valid for Sybase and Microsoft SQL Server connections only. The name of the database server. Valid for Sybase and Microsoft SQL Server connections only. Valid for Microsoft SQL Server connections only. The name of the domain. Used for Microsoft SQL Server on Windows. Valid for Microsoft SQL Server connections only. If selected, the PowerCenter Server uses Windows authentication to access the Microsoft SQL Server database. The user name that starts the PowerCenter Server must be a valid Windows user with access to the Microsoft SQL Server database. Enables enhanced security. Grants you read, write, and execute permissions. Public and world groups are not granted any permissions. If this option is not enabled, all groups and users are granted read, write, and execute permissions. For more information about enhanced security, see “Configuring the Workflow Manager” in the Workflow Administration Guide.

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

Specifying Database Type
When you create a new connection, you must specify a database type using the exact string associated with that database type in pmrep. The strings are not case-sensitive. Use quotes when specifying a string with spaces in an argument. Table 16-9 lists the required pmrep database type strings according to database:
Table 16-9. Database Type Strings Database IBM DB2 Informix Microsoft SQL Server ODBC Oracle Sybase Teradata Database Type String DB2 Informix Microsoft SQL Server ODBC Oracle Sybase Teradata

418

Chapter 16: Using pmrep and pmrepagent

Specifying Database Code Page Information
The -l option specifies the code page information for the database connection. To specify database code page information, you must use the string associated with the code page you want to assign to the database connection. If you configure the PowerCenter Server for data code page validation, changing the database connection code page can cause sessions to fail under the following conditions:
♦ ♦

The source database connection code page is not a subset of the PowerCenter Server code page. The target database connection code page is not a superset of the PowerCenter Server code page.

If you configure the PowerCenter Server for relaxed data code page validation, changing the database connection code page can cause data inconsistencies if the new code page is not compatible with the source or target database connection code pages. For details on data code page validation, see “Globalization Overview” in the Installation and Configuration Guide. For a list of supported code pages and code page compatibility reference, see “Code Pages” in the Installation and Configuration Guide. Table 16-10 lists the code page ID strings pmrep accepts to update database connection code page information:
Table 16-10. Code Page ID by Name (pmrep) Code Page Name 7-bit ASCII IBM EBCDIC Chinese (Simplified) IBM EBCDIC Chinese (Traditional) IBM EBCDIC French IBM EBCDIC German IBM EBCDIC International Latin-1 IBM EBCDIC Italian IBM EBCDIC Japanese IBM EBCDIC UK English IBM EBCDIC US English ISO 8859-1 Western European ISO 8859-2 Eastern European ISO 8859-3 Southeast European ISO 8859-4 Baltic ISO 8859-5 Cyrillic ISO 8859-6 Arabic pmrep ID String US-ASCII IBM935 IBM937 IBM297 IBM273 IBM500 IBM280 IBM930 IBM285 IBM037 Latin1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6

pmrep Repository Commands

419

Table 16-10. Code Page ID by Name (pmrep) Code Page Name ISO 8859-7 Greek ISO 8859-8 Hebrew ISO 8859-9 Latin 5 (Turkish) ISO 8859-10 Latin 6 (Nordic) ISO 8859-15 Latin 9 (Western European) Japan Extended UNIX Code (incl. JIS x 0212) MS-DOS Thai, superset of TIS 620 MS Windows Arabic MS Windows Baltic Rim MS Windows Chinese (Simplified), superset of GB 2312-80, EUC encoding MS Windows Chinese (Traditional), superset of Big 5 MS Windows Cyrillic (Slavic) MS Windows Greek MS Windows Hebrew MS Windows Japanese, superset of Shift-JIS MS Windows Korean superset of KS C 5601-1992 MS Windows Korean (Johab) MS Windows Latin 1 (ANSI), superset of Latin 2 MS Windows Latin 2 (Central Europe) MS Windows Latin 5 (Turkish), superset of ISO 8859-9 MS Windows Vietnamese UTF-8 encoding of Unicode pmrep ID String ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-15 JapanEUC MS874 MS1256 MS1257 MS936 MS950 MS1251 MS1253 MS1255 MS932 MS949 MS1361 MS1252 MS1250 MS1254 MS1258 UTF-8

Deleting a Connection (Deleteconnection)
The Deleteconnection command deletes a relational connection from the repository. To delete a connection, you must have Administer Repository privilege, be the owner of the connection object, have write permission on the object, or belong to the same group as the owner. Deleteconnection uses the following command syntax:
deleteconnection -n relational_connection_name -f force_delete

420

Chapter 16: Using pmrep and pmrepagent

Table 16-11 lists pmrep Deleteconnection option and argument:
Table 16-11. Deleteconnection Options and Arguments (pmrep) Option -n -f Required/ Optional Required Optional Argument Name relational_connection_name force_delete Argument Description Name of the relational connection to delete. Connection will be deleted without further confirmation.

The command returns “deleteconnection completed successfully” or returns “Failed to execute deleteconnection” message. The delete might fail for the following reasons:
♦ ♦ ♦

The database connection does not exist. You do not have the appropriate privilege. The Repository Server cannot obtain a lock on the connection object.

Deleting a Server (Deleteserver)
The Deleteserver command deletes a server from the repository. To delete a server, you must have Administer Repository privilege. Deleteserver uses the following command syntax:
deleteserver -v server_name

Table 16-12 lists pmrep Deleteserver option and argument:
Table 16-12. Deleteserver Options and Arguments (pmrep) Option -v Required/ Optional Required Argument Name server_name Argument Description Name of the PowerCenter Server to delete.

The command returns an “operation successfully completed” or returns “operation failed” message. The delete might fail for the following reasons:
♦ ♦ ♦

The server does not exist. You do not have the appropriate permissions to delete a server. The Repository Server cannot acquire a lock on the object.

Disabling a Repository (Disablerepository)
The Disablerepository command disables a repository. If a running repository is disabled, it will continue to run. Once a disabled repository is stopped, it cannot be restarted until it is enabled. When you disable the repository, you must enable it before you can start it again. To disable a repository, you must have Administer Repository privilege.
pmrep Repository Commands 421

Disablerepository uses the following command syntax:
disablerepository -h host_name -o port_number -a repserver_password -A repserver_password_environment_variable -r repository_name

Table 16-13 lists pmrep Disablerepository option and argument:
Table 16-13. Disablerepository Options and Arguments (pmrep) Option -h -o -a -A Required/ Optional Required Required Required/ Optional Required/ Optional Required Argument Name host_name port_number repserver_password repserver_password_ environment_variable repository_name Argument Description Name of the machine hosting the Repository Server. Port number where the Repository Server is running. Repository Server administrator password. Use the -a or -A option, but not both. Repository Server administrator password environment variable. Use the -a or -A option, but not both. Name of the repository to disable.

-r

The command returns a “disablerepository completed successfully” or returns “Failed to execute disablerepository” message. The command might fail for the following reasons:
♦ ♦ ♦

You did not give the repository name in the argument. The connection to the repository server failed. The Repository Server failed to disable the repository.

Enabling a Repository (Enablerepository)
The Enablerepository command enables a repository that has been disabled. To enable a repository, you must have Administer Repository privilege. Enablerepository uses the following command syntax:
ensablerepository -h host_name -o port_number -a repserver_password -A repserver_password_environment_variable -r repository_name

Table 16-14 lists pmrep Enablerepository options and arguments:
Table 16-14. Enablerepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Argument Name host_name port_number repserver_password Argument Description Name of the machine hosting the Repository Server. Port number where the Repository Server is running. Repository Server administrator password. Use the -a or -A option, but not both.

422

Chapter 16: Using pmrep and pmrepagent

Tip: When you specify characters to separate records and columns and to indicate the end of the listing. You can also specify the character or characters to indicate the end of the listing.Table 16-14. For example. but not both. Create a shell script that uses ListObjects to return Sequence Generator transformation information. pmrep returns each object in a record and returns each object metadata in a column. you do not need read permission on the folders. You must connect to a repository to use this command. It separates records by a new line by default. When you list objects. parse the metadata. you can use ListObjects to list all Sequence Generator transformations in the repository. Name of the repository to enable. use characters that are not used in repository object names. You can use ListObjects in a shell script to return the object metadata. parse the data ListObjects returns. pmrep Repository Commands 423 . pmrep returns object metadata to the screen. and use Updateseqgenvals to update the sequence values. Listing Repository Objects (ListObjects) The ListObjects command returns objects in the repository. Use the -a or -A option. and then use the parsed data in another pmrep command. You can specify the character or characters to use to separate records and columns. The command might fail for the following reasons: ♦ ♦ ♦ You did not give the repository name in the argument. This helps you use a shell script to parse the object metadata. -r The command returns an “enablerepository completed successfully” or returns “Failed to execute enablerepository” message. you must have one of the following sets of privileges and permissions: ♦ ♦ Browse Repository privilege with read permission on the folder Super User privilege Note: When you list folders. Enablerepository Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Required Argument Name repserver_password_ environment_variable repository_name Argument Description Repository Server administrator password environment variable. The connection to the Repository Server failed. The Repository Server failed to enable the repository because the repository is not currently disabled. To list objects.

Task. List mappings with latest or checked out version in a folder. 424 Chapter 16: Using pmrep and pmrepagent . including shortcuts but excluding instances of reusable mapplets. List reusable and non-reusable worklets with latest version or checked out version in a folder. including shortcuts but excluding instances of reusable mapplets. List reusable and non-reusable transformations with latest or checked out version in a folder. Session. List reusable and non-reusable sessions with latest or checked out version in a folder. and query object types are not associated with folders. excluding instances of reusable worklets. Transformation. Folder. label. Sessionconfig. List mapplets with latest or checked out version in a folder. Mapplet. List labels in the repository. Source. Worklet. The deploymentgroup. List deployment groups in the repository. List sources with latest or checked out version in a folder. Scheduler. All other object types require the -f option. folder. List folders in the repository Label. List the workflows with latest version or checked out version in a folder. List queries in the repository. Target. but excluding objects according to the following rules for each object type: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Deploymentgroup. The command lists the latest versions or checked out versions of objects. List reusable and non-reusable schedulers with latest or checked out version in a folder. Query. ♦ ♦ ListObjects uses the following command syntax: listobjects -o object_type -t object_subtype -f folder_name -c column_separator -r end_of_record_separator -l end-of-listing_indicator -b verbose Do not use the -f option if the object type you list is not associated with a folder. including shortcuts and excluding instances of reusable transformations. Mapping. including shortcuts but excluding source instances. excluding instances of reusable sessions. List the session configurations with latest or checked out version in a folder. List reusable and non-reusable tasks with latest or checked out version in a folder.You can use the object_type option to define the objects you want to list. List targets with latest or checked out version in a folder. including shortcuts. Workflow. including shortcuts but excluding target instances.

creator name and creation time. pmrep ignores the -t and -f options. Specify a character or set of characters that is not used in repository object names.When you specify folder. If you omit this option. Verbose format includes the object status. Use a character or set of characters that is not used in repository object names. For a list of subtypes to use with ListObjects.Table 16-15 lists pmrep ListObjects options and arguments: Table 16-15. pmrep uses a single space. such as label. version number. If you omit this option. you must include the -f option. folder name. you can include this option to return a specific type. you print a shorter format including the object type. Verbose format includes the label type. The type of transformation or task to list. and you can optionally include the -t option. The folder to search. The character or set of characters used to specify the end of the object metadata. Use this option for all object types except deploymentgroup. the object name and path. . and checked out information. and query. ListObjects Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object to list. Use a character or set of characters that is not used in repository object names. and connection. you must include the -f option. you might want to avoid using a space as a column separator. Print more than the minimum information about the objects. If any repository object name contains spaces. folder. . deployment group. pmrep uses a period. The character or set of characters used to specify the end of the object list.When you specify transformation or task. you do not need to include any other option. includes the object type and object name. query. the word reusable or nonreusable. deployment group type. If you omit this option.When you specify objects other than folders. . see Table 1616 on page 426. query type. The short format for versioning objects. The default is newline /n. -t Optional object_subtype -f -c Required Optional folder_name column_separator -r Optional end_of_record_separator -l Optional end_of_listing_indicator -b Optional verbose pmrep Repository Commands 425 . label. When you specify transformation or task for the object type. The character or set of characters used to separate object metadata columns.

Table 16-16 lists the transformation types and values to use with pmrep commands: Table 16-16. Transformation and Task Types to Use with pmrep Object Type Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Task Task Task Task Task Task Task Subtype Custom Aggregator Application Source Qualifier Application Multi-Group Source Qualifier Expression External Procedure Filter Input Joiner Lookup Mapplet MQ Source Qualifier Normalizer Output Rank Router Sequence Generator Sorter Source Qualifier Stored Procedure Transaction Control Update Strategy XML Source Qualifier Assignment Command Control Decision Email Event-raise Event-wait Subtype Value custom_transformation aggregator application_source_qualifier app_multi-group_source_qualifier expression external_procedure filter input_transformation joiner lookup_procedure mapplet mq_source_qualifier normalizer output_transformation rank router sequence sorter source_qualifier stored_procedure transaction_control update_strategy xml_source_qualifier assignment command control decision email event_raise event_wait 426 Chapter 16: Using pmrep and pmrepagent .

Table 16-16. pmrep ignores the subtype and folder name. Or. to list all folders in the repository. When you list objects. Transformation and Task Types to Use with pmrep Object Type Task Task Subtype Start Timer Subtype Value start timer Listing Folders You can use ListObjects to return each folder in the repository. For example. see Table 16-16 on page 426.sp_nsproc pmrep Repository Commands 427 . to list all Stored Procedure transformations in a folder.seqgen_empid . pmrep returns the name of the object with the path when applicable. For example. when a transformation is in a mapping or mapplet. enter the following text at the pmrep> prompt: listobjects -o transformation -f myfolder pmrep returns the following information: stored_procedure reusable sp_sproc1 expression reusable exp1 stored_procedure non-reusable mapping1. pmrep returns mapping_name.transformation_name. For a list of transformation or task return values. For example. to list all transformation types in a folder. When you specify folder for the object type.transformation_name or mapplet_name. enter the following text at the pmrep> prompt: listobjects -o transformation -t stored_procedure -f myfolder pmrep returns the following information: stored_procedure reusable sp_sproc1 stored_procedure non-reusable mapping1. pmrep does not include instances of reusable objects.sp_nsproc sequence non-reusable smallmapplet. you can specify a different column separator and end of listing indicator: listobjects -o folder -c “**” -l # Listing Objects You can use ListObjects to list reusable and non-reusable objects in the repository or in a folder.listobjects completed successfully. you must include the folder name for all objects that are associated with a folder. enter the following text at the pmrep> prompt: listobjects -o folder Or.

To list sources or targets. or specify target to list targets. if the mapping contains a mapplet with a source.. For example. The name of the session containing the sources or targets.listobjects completed successfully. However. You can specify a reusable or non-reusable session. Listing Tables by Session (Listtablesbysess) The Listtablesbysess command returns sources or targets used in a session. pmrep returns source and target instance names as they appear in the session properties. For example. When you list sources or targets. When you use Listtablesbysess. -t Required table_type 428 Chapter 16: Using pmrep and pmrepagent . Specify source to list sources. pmrep returns source or target instance names to the screen. To specify a non-reusable session in a workflow. You can use Listtablesbysess in a shell script with other pmrep commands.wl_shirt_orders.s_shirt_orders . you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with read permission on the folder Super User privilege Listtablesbysess uses the following command syntax: listtablesbysess -f folder_name -s session_name -t table_type Table 16-17 lists pmrep Listtablesbysess options and arguments: Table 16-17.listobjects completed successfully. you cannot specify an instance of a reusable session. To list all sessions in a folder.s_sales_Q3 session non-reusable wf_orders.session_name. pmrep returns the source instance name in the following format: mapplet_name. you can create a shell script that uses Listtablesbysess to return source instance names and uses Updatesrcprefix to update the source owner name. enter the workflow name and the session name as workflow_name. Listtablesbysess Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. enter the following text at the pmrep> prompt: listobjects -o session -f myfolder pmrep returns the following information: session reusable s_sales_by_CUSTID session non-reusable wf_sales.source_name You must connect to a repository to use this command.

For example. or Validate pmrep commands.ORDERS. If you want to list dependencies for non-reusable objects. These files are the same format. see “Using the Persistent Input File” on page 494. For more information on using a persistent input file.s_nrsess1 -t target pmrep returns the following information: target1_inst ORDERS_BY_CUSTID Shortcut_To_tgt2_inst listtablesbysess completed successfully. Listing Object Dependencies (ListObjectDependencies) Use the ListObjectDependencies command list dependency objects for reusable and nonreusable objects.ORDERS Shortcut_To_ITEM_ID listtablesbysess completed successfully. Note: ListObjectDependencies accepts a persistent input file and it can create a persistent output file. AddToDeployment Group. such as mapplet1. To list object dependencies.For example. ListObjectDependencies returns the number of records if the command runs successfully. Note: When the mapping contains a mapplet with a source. pmrep includes the mapplet name with the source. you can use it as input to the ApplyLabel. enter the following text at the pmrep> prompt: listtablesbysess -f myfolder -s s_reus_sess1 -t source pmrep returns the following information: ITEMS mapplet1. to list all sources in a reusable session. You can create this file by running a query and choosing to create a text file. you can list all targets in a non-reusable session in a workflow: listtablesbysess -f myfolder -s wf_workkflow1. If you create an output file. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the folder ListObjectDependencies uses the following command syntax: ListObjectDependencies -n object_name -o object_type_name -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_object_type -p dependency_direction -s include_pk-fk_dependency -g across_repositories -u persistent_output_file_name -a append -c column_separator -r end-ofrecord_separator -l end-of-listing_indicator -b verbose pmrep Repository Commands 429 . you must use a persistent input file containing object IDs.

You can specify ALL or one or more object types. AddToDeployment Group. session. workflow. cube. then pmrep lists all supported dependent objects. Send the dependency result to a text file. List dependent objects for an object version other than the latest version. Find object dependencies across repositories. You can use the text file as input to the ApplyLabel. -f options to specify objects. If ALL. Ignored for other object types. The type of dependent objects to list. The type of transformation or task. then you cannot use the -n. worklet.Note: ListObjectDependencies displays non-reusable objects as parent.parentobject_name. The parents or children dependent objects to list. session. then pmrep lists dependent objects only for these types. -o. The text file of objects generated from ExecuteQuery or Validate commands. If you choose one or more objects. transformation. session config. You can specify parents. Append the result to the persistent output file name file instead of overwriting it. separate them by commas without spaces. see “Using the Persistent Input File” on page 494. and dimension. For valid subtypes. or Validate pmrep commands. For more information on using the persistent input file. The default is ALL. The default sends the query result to stdout. task. To specify multiple objects. Required if you do not use the -p option. scheduler. The object type to list dependencies for. If you use this option. children. Table 16-18 lists pmrep ListObjectDependencies options and arguments: Table 16-18. ListObjectDependencies Options and Arguments (pmrep) Option -n -o Required/ Optional Optional Required Argument Name object_name object_type_name Argument Description The name of a specific object to list dependencies for. mapping. Folder is required if object type is not a folder and you are not using the -i option. or both. see Table 16-16 on page 426. Required if you do not use the -s option. -t -v -f Required/ Optional Optional Required/ Optional Optional object_subtype version_number folder_name -i persistent_input_file -d Optional dependency_object_t ype -p Required/ Optional Required/ Optional Optional Optional dependency_direction -s include_pkfk_dependency across_repositories persistent_output_file _name -g -u -a Optional append 430 Chapter 16: Using pmrep and pmrepagent . You can specify source. You must use this file if you want to list dependencies for non-reusable objects. Include the primary key-foreign key dependency object regardless of the direction of the dependency.nonreusableobject_name. The folder containing object_name. target.

The character or set of characters used to specify the end of the object list. The default is newline /n. The character or set of characters used to specify the end of the object metadata.Table 16-18. and connection. the word reusable or nonreusable. If you omit this option. If you omit this option. you must have Administer Repository privilege. If you omit this option. such as label. pmrep uses a period. -r Optional end-ofrecord_separator -l Optional end-oflisting_indicator -b Optional verbose Sending Notification Messages (Notify) Use the Notify command to send notification messages to users connected to a repository or users connected to all repositories managed by a Repository Server. you might want to avoid using a space as a column separator. the object name and path. pmrep prints a shorter format including the object type. Specify a character or set of characters that is not used in repository object names. includes the object type and object name. Verbose format includes the version number and folder name. Use a character or set of characters that is not used in repository object names. If any repository object name contains spaces. Print more than the minimum information about the objects. To send notification messages. pmrep uses a single space. The Notify command uses the following command syntax: Notify -h hostname -o port_number [-a repserver_password | -A repserver_password_environment_variable] -r repository_name -t notify | broadcast -m message Table 16-19 lists pmrep Notify options and arguments: Table 16-19. The number of the port where the Repository Server is running. ListObjectDependencies Options and Arguments (pmrep) Option -c Required/ Optional Optional Argument Name column_separator Argument Description The character or set of characters used to separate object metadata columns. Notify Options and Arguments (pmrep) Option -h -o Required/ Optional Required Required Argument Name hostname port_number Argument Description The name of the machine hosting the Repository Server. Verbose format includes the creator name and creation time. Use a character or set of characters that is not used in repository object names. The short format for versioning objects. deployment group. query. pmrep Repository Commands 431 .

The Repository Server password environment variable. you export the latest version of the object. Notify Options and Arguments (pmrep) Option -a -A Required/ Optional Required/ Optional Required/ Optional Required Required Argument Name repserver_password repserver_password_ environment_variable repository_name notify | broadcast Argument Description The Repository Server password. If you use the persistent input file then you do not use the other parameters to specify objects. objects referred by shortcut. You can optionally include reusable and non-reusable dependent objects. Use the -a or -A option. You failed to connect to the Repository Server. Notify sends a message to users connected to the repository. but not both. and related objects in a primary key-foreign key relationship. If you want to include dependent objects. The type of message you want to send to user. Validate.dtd file. you must add the appropriate pmrep options. Use the -a or -A option. To export objects. see “Using the Persistent Input File” on page 494. If you export a mapping. by default the PowerCenter client exports only the mapping and its instances.Table 16-19. Broadcast sends a message to users connected to all repositories managed by the given Repository Server. The notification might fail for the following reasons: ♦ ♦ ♦ The message type you entered is invalid. You can create this file by using the ExecuteQuery. see “Overview” on page 264. you must specify the folder that contains it. If you do not specify a version number. For more information on using the persistent input file. You can use a persistent input file to specify different objects to export at one time. or ListObjectDependencies pmrep commands. For more information on exporting objects. The Repository Server failed to notify users. The name of the repository whose users you want to notify. Exporting Objects (ObjectExport) Use the ObjectExport command to export objects to an XML file defined by the powrmart. but not both. The message you want to send. You export an object by name. If you specify an object. -r -t -m Required message The command returns “notify successfully completed” or returns “failed to execute notify” message. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the source folder 432 Chapter 16: Using pmrep and pmrepagent .

-f options to specify objects. If you do not specify an object name. see “Using the Object Import Control File” on page 496. The name of the XML file to contain the object information. If you do not specify this option. -o Required/ Optional Required/ Optional Optional Required object_type -t object_subtype -v -f version_number folder_name -i Optional persistent_input_file -u -l Required Optional xml_output_file_name log_file_name Importing Objects (ObjectImport) Use the ObjectImport command to import objects from an XML file. then you must specify the folder containing the object. all the latest or checked out objects in the folder export. you must have the following privileges and permissions: ♦ Use Repository Manager privilege pmrep Repository Commands 433 . This argument is ignored for other object types. The control file is an XML file defined by the impcntl. scheduler. then all the objects in this folder export. To import objects. ObjectExport Options and Arguments (pmrep) Option -n Required/ Optional Optional Argument Name object_name Argument Description The name of a specific object to export. worklet. For more details about the control file. The type of transformation or task. -o. target. then you cannot use the -n. The text file list of objects generated from ExecuteQuery. mapping. For more information on importing objects. Specifies a log file to collect all the export files. If you do specify an object name.ObjectExport uses the following command syntax: ObjectExport -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -u xml_output_file_name -l log_file_name Table 16-20 lists pmrep ObjectExport options and arguments: Table 16-20. Validate. The object type of the object name. or ListObjectDependencies. The name of the folder containing the object to export. workflow. session. see “Importing Objects” on page 280. task. see Table 16-16 on page 426. This command requires a control file to specify the objects to import and how to resolve conflicts. Export a version other than the latest version of the object. It contains object records with encoded IDs.dtd file. transformation. You can specify source. If you use this parameter. session config. For valid subtypes.

See “Using the Object Import Control File” on page 496.♦ Write permission on the target folder ObjectImport uses the following command syntax: ObjectImport -i input_XML_file_name -c control_file_name Table 16-21 lists pmrep ObjectImport options and arguments: Table 16-21. To register a local repository. Use the -a or -A option. Registering Local Repositories (Register) Use the Register command to register a local repository with a connected global repository. The login password environment variable for the local target repository. ObjectImport Options and Arguments (pmrep) Option -i -c Required/ Optional Required Required Argument Name input_XML_file_name control_file_name Argument Description The name of the XML file to import. The name of the control file that defines import options. Use the -x or -X option. but not both. You must connect to the global repository before you register the local repository. you must have Administer Repository privilege. but not both. The password you use to administer the global Repository Server. Note: The ObjectImport command does not automatically create a folder if the folder you specify does not exist in the repository. -a 434 Chapter 16: Using pmrep and pmrepagent . Register Options and Arguments (pmrep) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_ environment_variable global_repserver_password Argument Description The name of the local repository to register. The local repository user name. Register uses the following command syntax: Register -r repository_name -n repository_user_name [-x repository_password -X repository_password_environment_variable] [-a global_repserver_password | -A global_repserver_password_environment_variable] -h local_repository_host_name -o local_repository_port_number Table 16-22 lists pmrep Register options and arguments: Table 16-22. Use the -x or -X option. The login password for the local target repository. but not both.

Table 16-22. pmrep Repository Commands 435 . Use the -a or -A option. The number of the port where the Repository Server is running. The port number of the Repository Server. The login password for the repository. but not both. Use this option when the local repository is managed by a different Repository Server. you must use the -o option as well. Use this option when the local repository is managed by a different Repository Server. Use the -a or -A option. Removerepository uses the following command syntax: Removerepository -h hostname -o port_number -a repository_password -A repository_server_password_environment_variable -r repository_name Table 16-23 lists pmrep Removerepository options and arguments: Table 16-23. If you use this option. you must use the -h option as well. The Repository Server failed to register the local repository with the global repository. Removing Repositories From the Cache (Removerepository) The Removerepository command removes repositories from the Repository Server cache entry list. -h -o Optional local_repository_port_numb er The command returns “register successfully completed” or returns “failed to execute register” message. Register Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Optional Argument Name global_repserver_password _environment_variable local_repository_host_name Argument Description The password environment variable you use to administer the global Repository Server. Removerepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Argument Name hostname port_number repository_password Argument Description The hostname of the machine hosting the Repository Server. The hostname of the local repository. If you use this option. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. but not both. The Repository Server failed to initialize information about the global repository. You failed to connect to the Repository Server.

Table 16-23. -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. You failed to connect to the Repository Server. 436 Chapter 16: Using pmrep and pmrepagent . Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. The commands are echoed back to the script. but not both. Run Options and Arguments (pmrep) Option -f -o Required/ Optional Required Optional Argument Name script_file_name output_file_name Argument Description The name of the script file. All repository users can run script files. Use the -a or -A option. This option writes all messages generated by the commands in the script file into the output file. Stops the running of the script after a command returns an error. The Run command uses the following command syntax: run -f script_file_name -o output_file_name -e echo_commands -s stop_at_first_error Table 16-24 lists pmrep Run options and arguments: Table 16-24. The name of the output file. The name of the repository to remove. The run might fail if the Repository Server cannot open the script file or output file. Removerepository Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Required Argument Name repository_password_ environment_variable repository_name Argument Description The login password environment variable for the repository.

server. if you do not specify a repository. and -r options. StopRepository uses the following command syntax: stopRepository [-a repserver_password -A repserver_password_environment_variable] -h hostname -o port_number -r repository_name Note: If you use the -h. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. see “Connecting to a Repository (Connect)” on page 410. For more information about connections in command line mode and interactive mode.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. and user information for the current connection. pmrep does not keep connection information in command line mode. a message indicating failure to execute the command is given. the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. StopRepository stops the repository you last connected to. if you run pmrep and enter: showconnectioninfo pmrep returns information similar to the following: connected to Repository MyRepository [servername:port#] connected as user MyUserName Use the ShowConnectioninfo command in interactive mode. Otherwise. For example. pmrep Repository Commands 437 . When you connect to a repository in interactive mode. pmrep connects to the Repository Server and stops the Repository Agent. When you use the ShowConnectioninfo command in command line mode. ShowConnectioninfo requires no parameters. the repository that you last connected to stops. -o. The ShowConnectioninfo command does not connect to the repository. port. the named repository stops. However. When you use the StopRepository command. You must be connected to a repository to use this command.

You must be connected to a repository to use this command. The name of the repository to stop. the Repository Server replaces the relational connection. you have a relational and an application source. you must also use the -h and -r options. When you use SwitchConnection. StopRepository Option and Argument (pmrep) Option -a Required/ Optional Required/ Optional Required/ Optional Argument Name repserver_password Argument Description The password you use to administer the Repository Server that manages the repository. The password environment variable you use to administer the Repository Server that manages the repository. The Repository Server port number. pmrep does not replace any relational connection in the repository because it cannot determine the connection type for the source connection entered as ITEMS. but not both. the Repository Server replaces the relational database connections for all sessions using the connection in one of the following locations: ♦ ♦ ♦ ♦ ♦ ♦ Source connection Target connection Connection Information property in Lookup transformations Connection Information property in Stored Procedure transformations $Source Connection Value session property $Target Connection Value session property If the repository contains both relational and application connections with the same name and you specified the connection type as relational in all locations in the repository. Use the -a or -A option. The hostname of the Repository Server that manages the repository to stop. 438 Chapter 16: Using pmrep and pmrepagent . each called ITEMS. When you use this option. When you use this option. -A repserver_password_ environment_variable -h Optional hostname -o -r Optional Optional port_number repository_name Changing the Connection Name (SwitchConnection) The SwitchConnection command changes the name of an existing connection. but not both. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. For example. you must also use the -o and -r options. Use the -a or -A option. In a session. you must also use the -h and -o options.Table 16-25 lists pmrep StopRepository option and argument: Table 16-25. When you use this option. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection.

Truncatelog Options and Arguments (pmrep) Option -t Required/ Optional Required Argument Name all | endtime Argument Description Use “all” or “endtime. If you give both the folder name and workflow name. SwitchConnection Options and Arguments (pmrep) Option -o -n Required/ Optional Required Required Argument Name old_connection_name new_connection_name Argument Description The name of the existing connection you want to change. or delete logs for a folder or workflow. Truncating Workflow and Session Logs (Truncatelog) The Truncatelog command deletes details from the repository. Truncatelog uses the following command syntax: Truncatelog -t all| endtime -f folder_name -w workflow_name Table 16-27 lists pmrep Truncatelog options and arguments: Table 16-27. then you delete all logs from the repository.SwitchConnection uses the following command syntax: switchconnection -o old_connection_name -n new_connection_name To replace connections with pmrep. you must have Super User privilege. you must also provide the folder name. To run Truncatelog. You can also specify a date and delete all logs older than that date. The Repository Server deletes all logs from the repository if you do not give both the folder name and the workflow name. Table 16-26 lists pmrep SwitchConnection options and arguments: Table 16-26. If you do not give both the folder name and the workflow name. Deletes logs associated with the workflow. Otherwise. pmrep deletes all logs older than the endtime. Deletes logs associated with the folder. you must have Administer Repository privilege. The new connection name. You can delete all logs. use endtime and specify a time with a format of: MM/DD/YYYY HH24:MI:SS. -f Optional folder_name -w Optional workflow_name pmrep Repository Commands 439 . If you specify the workflow name.” Use “all” to delete all the logs. the Repository Server deletes logs associated with the workflow.

Use the -a or -A option. you must have Administer Repository privilege. The local repository user name. Use the -a or -A option. The folder name is invalid. but not both. The password environment variable you use to administer the global Repository Server. -a -A global_repserver_password_ environment_variable 440 Chapter 16: Using pmrep and pmrepagent . Use the -x or -X option. but no folder name. but not both. but not both. You must connect to the global repository before you unregister the local repository. Unregister Options and Arguments (pmrep) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_ environment_variable global_repserver_password Argument Description The name of the local repository to unregister. You specified a workflow. but not both.The command returns “truncatelog completed successfully” or returns “Failed to execute truncatelog” message. Use the -x or -X option. To unregister a local repository. Unregistering Local Repositories (Unregister) Use the Unregister command to unregister a local repository from a connected global repository. The login password for the local target repository. The truncation might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The password you use to administer the global Repository Server. The login password environment variable for the local target repository. The workflow does not exist in the given folder. Unregister uses the following command syntax: Register -r repository_name -n repository_user_name [-x repository_password | -X repository_password_environment_variable] [-a global_repserver_password | -A global_repserver_password_environment_variable] -h local_repository_host_name -o local_repository_port_number Table 16-28 lists pmrep Unregister options and arguments: Table 16-28.

password. pmrep cannot acquire a lock on the object. The current user does not have the appropriate permissions. and attributes for a database connection. A failure might occur for the following reasons: ♦ ♦ ♦ ♦ ♦ The database type is not supported. The number of the port where the Repository Server is running. You failed to connect to the Repository Server. If you use this option. UpdateConnection uses the following command syntax: updateconnection -t database_type -d database_connection_name -u new_user_name -p new_database_password -P new_database_password_environment_variable -c new_database_connection_string -a attribute_name -v new_attribute_value pmrep Repository Commands 441 . To update a connection. The Repository Server failed to unregister the local repository to the global repository. The connection object does not exist.Table 16-28. you must use the -o option as well. connect string. you must have one of the following privileges and permissions: ♦ ♦ ♦ Write permission for the connection object Ownership of the object Membership in a group that owns the object The command returns an “operation successfully completed” or returns “operation failed” message. If you use this option. Use this option when the local repository is managed by a different Repository Server. Unregister Options and Arguments (pmrep) Option -h Required/ Optional Optional Argument Name local_repository_host_name Argument Description The hostname of the local repository. Use this option when the local repository is managed by a different Repository Server. One of the required parameters is missing. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The Repository Server failed to initialize information about the global repository. -o Optional local_repository_port_number The command returns “unregister successfully completed” or returns “failed to execute unregister” message. Updating a Database Connection (UpdateConnection) The UpdateConnection command updates the user name. you must use the -h option as well.

If you did not previously specify a success or failure Email task for the session. -P new_database_password_ environment_variable -c Required new_database_connection _string attribute_name new_attribute_value -a -v Optional Optional Updating the Notification Email Addresses (Updateemailaddr) The Updateemailaddr command updates the session notification email addresses associated with the Email tasks assigned to the session. the command does not update the email addresses.Table 16-29 lists pmrep UpdateConnection options and arguments: Table 16-29. The new attribute value of the connection. but not both. see Table 16-9 on page 418. Updateemailaddr uses the following command syntax: updateemailaddr -d folder_name -s session_name -u success_email_address f failure_email_address 442 Chapter 16: Using pmrep and pmrepagent . UpdateConnection Options and Arguments (pmrep) Option -t -d -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Argument Name database_type database_connection_na me new_user_name new_database_password Argument Description The type of relational connection. The name of the attribute. The connect string the PowerCenter Server uses to connect to the relational database. You can specify different addresses to receive either success or failure notifications. Enter “yes” or “no” for attributes you enable through a checkbox. Use the -p or -P option. see Table 16-1 on page 405. The password environment variable used for authentication when you connect to the relational database. You can update the email notification addresses only for a non-reusable session with a unique name in the folder. The database connection name. This command requires you to connect to a repository. For a list of native connect strings. The password used for authentication when you connect to the relational database. For a list of valid database types. Use the -p or -P option. but not both. The user name used for authentication when you connect to the relational database.

The new name of the PowerCenter Server. Only the values that you specify update. Updating Server Details (Updateserver) The Updateserver command updates PowerCenter Server details with the values that you specify in the command. The protocol the PowerCenter Server uses. pmrep Repository Commands 443 . Email address to send session failure notifications. Updateemailaddr Options and Arguments (pmrep) Option -d -s -u -f Required/ Optional Required Required Required Required Argument Name folder_name session_name success_email_address failure_email_address Argument Description Name of the session folder. Email address to send session success notifications.Table 16-30 lists pmrep Updateemailaddr options and arguments: Table 16-30. Select the code page identical to the PowerCenter Server operating system code page. Name of the session. you must have the Administer Repository privilege. For more information about PowerCenter Server details see “Registering the PowerCenter Server” in the Installation and Configuration Guide. The character set associated with the PowerCenter Server. Must be identical to or compatible with the repository code page. The server host name or IP address of the server machine. The number of seconds the Workflow Manager waits for a response from the PowerCenter Server. Updateserver Options and Arguments (pmrep) Option -v -h -k -o -t -p -l Required/ Optional Required Optional Optional Optional Optional Optional Optional Argument Name server_name new_host_name new_servername new_port_number new_timeout_value new_protocol_name new_codepage_name Argument Description The name of the PowerCenter Server you want to change. To update server details. The port number the PowerCenter Server. Updateserver uses the following command syntax: updateserver -v server_name -h new_host_name -k new_servername -o new_port_number -t new_timeout_value -p new_protocol_name -l new_codepage_name Table 16-31 lists pmrep Updateserver options and arguments: Table 16-31.

you must include the mapping name. The mapping name. When you update values for a nonreusable Sequence Generator transformation. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent .Updating Sequence Generator Transformations (Updateseqgenvals) The Updateseqgenvals command updates one or more of the following properties for the specified Sequence Generator transformation: ♦ ♦ ♦ ♦ Start Value End Value Increment By Current Value You might want to update sequence values when you move a mapping from a development environment to a production environment. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with write permission on the folder Super User privilege Updateseqgenvals uses the following command syntax: updateseqgenvals -f folder_name -m mapping_name -t sequence_generator_name -s start_value -e end_value -i increment_by -c current_value Table 16-32 lists pmrep Updateseqgenvals options and arguments: Table 16-32. You must connect to a repository to use this command. To update sequence values. The Sequence Generator transformation name. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations. see “Sequence Generator Transformation” in the Transformation Guide. Updateseqgenvals Options and Arguments (pmrep) Option -f -m Required/ Optional Required Required/ Optional Required Argument Name folder_name mapping_name Argument Description The folder name. However. You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. For more information on configuring Sequence Generator transformations.

it fails the session. The maximum value the PowerCenter Server generates.Table 16-32. the current value must be greater than or equal to the start value and less than the end value. pmrep updates source table owner names only if you previously edited the source table name in the session properties. If you designate an invalid value. pmrep gives an error message and does not update the Sequence Generator transformation. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with write permission on the folder Super User privilege pmrep Repository Commands 445 . To update source table owner names. pmrep gives an error message and does not update the Sequence Generator transformation. Enter the value you want the PowerCenter Server to use as the first value in the sequence. If you want to cycle through a series of values. Updatesrcprefix updates the owner name for source tables at the session level. You must connect to a repository to use this command. The current value of the sequence. If the PowerCenter Server reaches this value during the session and the sequence is not configured to cycle. If you designate an invalid value. pmrep gives an error message and does not update the Sequence Generator transformation. Updateseqgenvals Options and Arguments (pmrep) Option -s Required/ Optional Optional Argument Name start_value Argument Description The start value of the generated sequence you want the PowerCenter Server to use if the Sequence Generator transformation uses the Cycle property. the PowerCenter Server cycles back to this value when it reaches the end value. If you designate an invalid value. You can update the owner name for one or all sources in a session. If you designate an invalid value. If you select Cycle in the transformation properties. -e Optional end_value -i Optional increment_by -c Optional current_value Updating the Source Table Owner Name (Updatesrcprefix) Use the Updatesrcprefix command to update the owner name for session source tables. The difference between two consecutive values from the NEXTVAL port. pmrep gives an error message and does not update the Sequence Generator transformation.

pmrep updates all source table owner names in the session. You cannot change default server variables. For a list of server variables. If you omit this option. The name of the session containing the sources to update. When you include this option.session_name or workflow_name. When you do not include this option. For reusable sessions.When you include the -n option. you must enter the dbd name and the source table name as dbd_name. For non-reusable sessions. This option has no argument.Updatesrcprefix uses the following command syntax: Updatesrcprefix -f folder_name -s session_name -t source_name -p prefix_name -n Table 16-33 lists the pmrep Updatesrcprefix options and arguments: Table 16-33. such as worklet_name. Updatesrcprefix Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. The owner name you want to update in the source table.source_name. You can update any of the PowerCenter Server variables using Updatesrvvar. . pmrep matches the source_name argument with the source table names. but you can change the case of the default server variables. pmrep matches the source_name argument with source instance names. The name of the source to update.session_name.When you omit the -n option. . Informatica recommends you include the -n option. specify session_name. You can find the source dbd name in the Designer Navigator. enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command. The Designer generates the dbd name from the source type or data source name when you create a source definition in the repository. -t Optional source_name -p -n Required Optional prefix_name n/a Updating Server Variables (Updatesrvvar) The Updatesrvvar command updates the value of the specified server variable. This command requires you to connect to a repository. you must also specify the session path. see “Configuring the Workflow Manager” in the Workflow Administration Guide. Updatesrvvar uses the following command syntax: updatesrvvar -s server_name -v variable_name -u new_value 446 Chapter 16: Using pmrep and pmrepagent .

You must connect to a repository to use this command. Updatesrvvar Options and Arguments (pmrep) Option -s -v -u Required/ Optional Required Required Required Argument Name server_name variable_name new_value Argument Description Name of the PowerCenter Server. see “Updating Repository Statistics” on page 60. you must have Administer Repository privilege. The command returns “updatestatistics successfully completed” or returns “updatestatistics failed” message. Name of the server variable to update. Updatestatistics Options and Arguments (pmrep) Option -s Required/ Optional Optional Argument Name tables-to-skip_file_name Argument Description The name of the file that contains a list of repository tables to skip during update. To update repository statistics. pmrep updates table name prefixes if you previously edited the table name prefix at the session level.Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34. pmrep Repository Commands 447 . Value of updated server variable. The update fails if you do not have Administer Repository privilege. UpdateStatistics uses the following command syntax: updatestatistics -s tables-to-skip_file_name Table 16-35 lists pmrep Updatestatistics options and arguments: Table 16-35. You can update the owner name for one or all targets specified in a session. Updating the Target Table Name Prefix (Updatetargprefix) Use the Updatetargprefix command to update the table name prefix for session target tables. The table name prefix specifies the owner of the table in the database. Updating Repository Statistics (UpdateStatistics) The UpdateStatistics command updates statistics for repository tables and indexes. Updatetargprefix updates the target table name prefix at the session level. For more information about updating statistics.

When you include this option.session_name. Updatetargprefix Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. you must also specify the session path. The name of the target to update. you must enter the target table name instead of the target instance name. When you include the -n option. pmrep matches the target_name argument with target instance names. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with write permission on the folder Super User privilege Updatetargprefix uses the following command syntax: Updatetargprefix -f folder_name -s session_name -t target_name -p prefix_name -n Table 16-36 lists the pmrep Updatetargprefix options and arguments: Table 16-36. pmrep matches the target_name argument with the target table names. pmrep updates all target table name prefixes in the session. When you do not include this option. such as worklet_name.session_name or workflow_name. The name of the session containing the targets to update. Informatica recommends you include the -n option.To update target table name prefixes. enter the name of the target instance as displayed in the session properties or as output by the Listtablesbysess command. specify session_name. This option has no argument. The table name prefix you want to update in the target table. If you omit this option. For non-reusable sessions. For reusable sessions. When you omit the -n option. -t Optional target_name -p -n Required Optional prefix_name n/a 448 Chapter 16: Using pmrep and pmrepagent .

See “Listing All Groups (Listallgroups)” on page 455. See “Creating a User (Createuser)” on page 452. Creates a user.pmrep Security Commands pmrep allows you to perform security tasks for users and groups. See “Registering a User (Registeruser)” on page 457. See “Modify Folder Properties (ModifyFolder)” on page 456. Removes a user from the repository. See “Creating a Folder (CreateFolder)” on page 451. See “Deleting a Folder (DeleteFolder)” on page 453. You must have the Administer Repository privilege to use pmrep repository security commands. pmrep Security Commands pmrep Command Addprivilege Addusertogroup Changepasswd CreateFolder Creategroup Createuser DeleteFolder Edituser Listallgroups Listallprivileges Listallusers ModifyFolder Registeruser Rmgroup Rmprivilege Rmuser Rmuserfromgroup Command Description Adds a privilege to a user or group. See “Listing All Privileges (Listallprivileges)” on page 455. Changes the password for the user currently connected to the repository. Adds a user to a group. Removes a privilege from a user or group. Creates a new folder. Lists all groups registered with the repository. See “Adding a User to a Group (Addusertogroup)” on page 450. See “Listing All Users (Listallusers)” on page 455. Removes a group from the repository. See “Removing a Privilege (Rmprivilege)” on page 458. See “Editing a User (Edituser)” on page 454. See “Removing a User (Rmuser)” on page 458. Lists all privileges that you can assign to a user or group. Edits the profile of a user. Removes a user from a group. Creates a group. Modifies folder properties. Lists all users registered with the repository. See “Creating a Group (Creategroup)” on page 452. See “Removing a User from a Group (Rmuserfromgroup)” on page 459. See “Removing a Group (Rmgroup)” on page 457. Table 16-37 describes commands you use to perform repository security tasks: Table 16-37. pmrep Security Commands 449 . See “Changing the Repository Password (Changepasswd)” on page 450. Registers a user from an external directory service to access the Repository. See “Adding a Privilege (Addprivilege)” on page 450. Deletes a folder.

If you add a privilege to a group.” The name of the user to whom you want to add the privilege. To add a privilege to a user or a group. You must be connected to the repository to use this command. -u -g Required Required username group_name Adding a User to a Group (Addusertogroup) The Addusertogroup commands adds an existing user to a group. all users in the group inherit the privilege. If you use this option. you cannot use the -g option. The name of the group to which you want to add the user. It cannot add a privilege to a user and a group at the same time. 450 Chapter 16: Using pmrep and pmrepagent . you cannot use the -u option. Note: You cannot use this command with an external security module. If you use this option. Addusertogroup Options and Arguments (pmrep) Option -u -g Required/ Optional Required Required Argument Name username group_name Argument Description The user name of the user to add to the group. If the privilege contains spaces. To add a user to a group. You must connect to the repository to use this command. use the following syntax: addprivilege -p privilege -u username -g group_name Table 16-38 lists pmrep Addprivilege options and arguments: Table 16-38. such as “Administer Repository. You must connect to the repository to use this command.Adding a Privilege (Addprivilege) The Addprivilege command adds a privilege to a user or group. Changing the Repository Password (Changepasswd) The Changepasswd command changes the password of the user currently connected to the repository. Addprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to add. you must enclose this argument in quotes. The user inherits all of the permissions and privileges associated with the group. The name of the group to which you want to add the privilege. use the following syntax: addusertogroup -u username -g group_name Table 16-39 lists pmrep Addusertogroup options and arguments: Table 16-39.

CreateFolder Options and Arguments (pmrep) Option -n -d -o -g -s -p Required/ Optional Required Optional Optional Optional Optional Optional Argument Name folder_name folder_description owner_name group_name shared_folder permissions Argument Description Folder name. do not use the -c option. -c Required/ Optional confirm_new_password -P Required/ Optional new_password_environ ment_variable Creating a Folder (CreateFolder) The CreateFolder command creates a new folder in the repository. The confirm_new_password argument must match the new_password argument. The password environment variable that replaces the existing password for the current user. The owner of the folder.To change the password of the user connected to the repository. Repository Server assigns default permissions. use the following syntax: changepasswd -p new_password -c confirm_new_password -P new_password_environment_variable Table 16-40 lists pmrep Changepasswd options and arguments: Table 16-40. you must use the -c option. You must use this option when you use the -p option. Repository user group to receive Owner’s Group permissions. If selected. Access rights for the folder. Only groups to which the owner belongs can be selected. Changepasswd Options and Arguments (pmrep) Option -p Required/ Optional Required/ Optional Argument Name new_password Argument Description The password that replaces the existing password for the current user. makes the folder shared. CreateFolder uses the following command syntax: Createfolder -n folder_name -d folder_description -o owner_name -g group_name -s shared_folder -p permissions Table 16-41 lists CreateFolder options and arguments: Table 16-41. If not specified. Description of the folder that appears in the Repository Manager. but not both. you must have Administer Repository privilege. Any user in the repository can be the folder owner. Use the -p or -P option. This option confirms the new password. but not both. When you use this option. When you use this option. The default owner is the user creating the folder. pmrep Security Commands 451 . Use the -p or -P option. To run CreateFolder.

or the sum of any of those numbers. 2. Designate 4 for read permission. A valid user name has no spaces and is case-sensitive. You must connect to the repository before using this command. 1. 452 Chapter 16: Using pmrep and pmrepagent . Creating a Group (Creategroup) The Creategroup command adds a new group to the repository. 2 for write permission. group. If you create a user that has the same name as a user already registered with the repository. The first digit corresponds to owner permissions. The owner’s group has read and write permissions (6 = 4+2). For example. All others have read permission. and repository permissions by giving three digits when you use the -p option. Creating a User (Createuser) The Createuser command adds a new user to the repository. you use the following command syntax: -p 764 This gives the folder owner read. pmrep returns an error message. write. The description of the group you want to create. Each permission is associated with a number. and 1 for execute permission. Note: You cannot use this command if the repository is using an external security module. if you want to assign default permissions. The command returns “createfolder successfully completed” or returns “createfolder failed” message. and execute permissions (7 = 4+2+1). and the third corresponds to all other permissions. use the following syntax: creategroup -g group_name -d description Table 16-42 lists pmrep Creategroup options and arguments: Table 16-42. the second corresponds to the permissions of the group that the user belongs to. Creategroup Options and Arguments (pmrep) Option -g -d Required/ Optional Required Optional Argument Name group_name description Argument Description The name of the group you want to create. The owner does not exist or does not belong to the group. Specify one number for each set of permissions. The creation might fail for the following reasons: ♦ ♦ ♦ You do not have Administer Repository privilege. pmrep creates the group with the default permissions and privileges assigned to the Public group. To assign permissions. The folder already exists.Assigning Permissions You can assign owner. To create a group. you specify 4.

To create a new user. The new user inherits all permissions and privileges granted to the group. You must use this option when you use the -p option. use the following syntax: deletefolder -n folder_name Table 16-44 lists DeleteFolder option and argument: Table 16-44. pmrep assigns the new user to the Public group. Use the -p or -P option. Createuser Options and Arguments (pmrep) Option -u -p Required/ Optional Required Required/ Optional Argument Name username password Argument Description User name of the new user. pmrep returns an error and does not carry out the command. When you use this option. The confirm_password argument must match the password argument. When you use this option. do not use the -c option. To delete a folder. The password is case-sensitive and cannot contain spaces. This option ensures you enter the correct password. you add the user to the Public group. The password of the new user. you must use the -c option. A description of the new user. -c Required/ Optional Required/ Optional confirm_password -P new_password_en vironment_variable -d -g Optional Optional description group_name If you specify a group that does not exist. but not both. Deleting a Folder (DeleteFolder) The DeleteFolder command deletes an existing folder from the repository. The password environment variable of the new user. pmrep Security Commands 453 . you must have Administer Repository privilege. If you do not specify a group. If you do not specify a group for the new user. To delete a folder. The password is case-sensitive and cannot contain spaces. but not both. use the following syntax: createuser -u username -p password -c confirm_password -P new_password_environment_variable -d description -g group_name Table 16-43 lists pmrep Createuser options and arguments: Table 16-43. The group assigned to the new user. The user name is case-sensitive and cannot contain spaces. Use the -p or -P option. DeleteFolder Options and Arguments (pmrep) Option -n Required/ Optional Required Argument Name folder_name Argument Description The name of the folder.

This option ensures you enter the correct password. You can use this option if you are using native authentication security. do not use the -c option. you must use the -c option. Edituser Options and Arguments (pmrep) Option -u -p Required/ Optional Required Required/ Optional Argument Name username new_password Argument Description Replace the user name of the user currently connected to the repository. The folder is being used by another user. The folder does not exist. To edit the profile of the user currently connected to the repository. Editing a User (Edituser) The Edituser command edits the user name. When you use this option. When you use this option. If you use the -p option with this command. Use the -p or -P option. Otherwise the command fails. This command requires you to connect to the repository. you must also use the -c option. use the following syntax: edituser -u username -p new_password -c confirm_new_password -P new_password_environment_variable -d description -l login_name -e Table 16-45 lists pmrep Edituser options and arguments: Table 16-45. password. but not both. You can also disable or enable users. Replace the password of the user currently connected to the repository. The confirm_new_password argument must match the new_password argument. but not both. -c Required/ Optional confirm_new_password -P Required/ Optional new_password_ environment_variable -d Optional description 454 Chapter 16: Using pmrep and pmrepagent . The new password environment variable to replace the password of the user currently connected to the repository. and description of the user currently connected to the repository.The command returns “DeleteFolder successfully completed” or returns “DeleteFolder failed.” The deletion might fail for the following reasons: ♦ ♦ ♦ You do not have Administer Repository privilege. Otherwise the command fails. You can use this option if you are using native authentication security. Use the -p or -P option. Update the description of the user currently connected to the repository.

To list all repository privileges. Enables or disables a user. To list all groups registered to the repository. For example. JSmith with the external login name of JohnS and enables him to use the repository. you could use the following pmrep command to enable a user called JSmith. use the following syntax: listallusers pmrep Security Commands 455 . use the -l option with this option. edituser -u JSmith -l JohnS -e yes The command associates his repository user name. use the following syntax: listallgroups Listing All Privileges (Listallprivileges) The Listallprivileges command lists all valid repository privileges for users or groups. Edituser Options and Arguments (pmrep) Option -l -e Required/ Optional Optional Optional Argument Name login_name n/a Argument Description Specifies a login to which to map the user name. Listing All Groups (Listallgroups) The Listallgroups command lists all groups registered with the repository by name. You must connect to the repository before using this command. if you use LDAP to authenticate users in the repository. You can enter a yes or no argument. To enable a user and specify a login name. To list all users registered to the repository. You must connect to the repository before using this command. Use the list of privileges to provide the privilege argument when adding or removing a privilege with pmrep. use the following syntax: listallprivileges Listing All Users (Listallusers) The Listallusers command lists all user names registered with the repository. Use the no argument to disable a user.Table 16-45. You can use this option only with an external directory service.

use the following command syntax: -p 764 This gives the folder owner read. Each permission is associated with a number. To modify a folder. Access rights for the folder. Description of the folder that appears in the Repository Manager. write. All others have read permission. If not specified. If selected. The current owner of the folder. and repository permissions by giving three digits when you use the -p option. The default owner is the current user. you must have Administer Repository privilege or be the folder owner. Repository Server uses existing permissions. and the third corresponds to all other permissions. To modify a folder. if you want to assign default permissions.Modify Folder Properties (ModifyFolder) The ModifyFolder command modifies folder properties. The first digit corresponds to owner permissions. Repository user group to receive Owner’s Group permissions. ModifyFolder Option and Argument (pmrep) Option -n -d -o Required/ Optional Required Optional Optional Argument Name folder_name folder_description owner_name Argument Description Folder name. 2. and 1 for execute permission. 456 Chapter 16: Using pmrep and pmrepagent . 1. use the following syntax: modifyfolder -n folder_name -d folder_description -o owner_name -g group_name -s shared_folder -r new_folder_name -p permissions Table 16-46 lists the ModifyFolder options and arguments: Table 16-46. Any user in the repository can be the folder owner. To assign permissions. or the sum of any of those numbers. Only groups to which the owner belongs can be selected. group. Designate 4 for read permission. the second corresponds to the permissions of the group that the user belongs to. For example. 2 for write permission. you specify 4. makes the folder shared. -g Optional group_name -s -r -p Optional Optional Optional shared_folder new_folder_name permissions Assigning Permissions You can assign owner. Rename the folder. and execute permissions (7 = 4+2+1). Specify one number for each set of permissions. The owner’s group has read and write permissions (6 = 4+2).

the user is assigned to Public. If any user in the group is connected to the repository when you remove the group. Registering a User (Registeruser) Use the Registeruser command to register a login from an external directory service and associate it with a repository user name. The folder does not exist. When you remove a group.The command returns “ModifyFolder successfully completed” or returns “ModifyFolder Failed” message. To remove a group. users in the group lose the privileges inherited from the group. Removing a Group (Rmgroup) The Rmgroup command removes a group from the repository and reassigns all users in that group to the Public group. The login name in the external directory. A folder with the new folder name already exists. the privilege changes take effect the next time the user connects to the repository. Registeruser uses the following syntax: registeruser -u repository_user_name -l external_login -d description -g group_name -i contact_info Table 16-47 lists the pmrep Registeruser options and argument: Table 16-47. Assigns the user to a group. The modification might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have the appropriate privilege. A description of the user. If you omit this option. Note: You cannot remove the Public or Administrators group. The new owner does not exist or does not belong to the group. Use this command if you use LDAP to authenticate repository users. use the following syntax: rmgroup -g group_name pmrep Security Commands 457 . You must connect to the repository to use this command. Registeruser Option and Argument (pmrep) Option -u -l -d -g -i Required/ Optional Required Required Optional Optional Optional Argument Name repository_user_name external_login description group_name contact_info Argument Description The name to add as a repository user. Contact information about the user.

use the following syntax: rmuser -u username 458 Chapter 16: Using pmrep and pmrepagent . To remove a privilege. The name of the group from which you want to remove the privilege. use the following syntax: rmprivilege -p privilege -u username -g group_name Table 16-49 lists pmrep Rmprivilege options and arguments: Table 16-49. such as “Administer Repository. Rmprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to remove. you cannot use the -g option. If the user or users in the group are connected to the repository when you remove the privilege. If you use this option. -u -g Required Required username group_name Removing a User (Rmuser) The Rmuser command removes a user from the repository or from the user name-login mapping. you cannot use the -u option. You cannot remove the Administrator user name from the repository. You must connect to the repository to use this command. the removal takes effect after the user disconnects from the repository. If the privilege contains spaces. If you use this option. You cannot remove a privilege from a user and a group at the same time. depending on the type of user authentication you use. the change takes effect the next time the user connects to the repository. you must enclose this argument in quotes. Rmgroup Option and Argument (pmrep) Option -g Required/ Optional Required Argument Name group_name Argument Description The name of the group you want to remove. If you remove a user while the user is connected to the repository.Table 16-48 lists the pmrep Rmgroup option and argument: Table 16-48. You must connect to a repository to use this command. To remove a user. Removing a Privilege (Rmprivilege) The Rmprivilege command removes a privilege from a user or group.” The name of the user from whom you want to remove the privilege.

pmrep Security Commands 459 . Removing a User from a Group (Rmuserfromgroup) The Rmuserfromgroup command removes an existing user from a group. The user loses permissions and privileges associated with the group.Table 16-50 lists the pmrep Rmuser option and argument: Table 16-50. If the user is connected to the repository when you remove the user from a group. You must be connected to the repository to use this command. the change takes effect the next time the user connects to the repository. Rmuserfromgroup Options and Arguments (pmrep) Option -u -g Required/ Optional Required Required Argument Name username group_name Argument Description User name to remove from the group. The name of the group from which to remove the user. To remove a user from a group. use the following syntax: rmuserfromgroup -u username -g group_name Table 16-51 lists pmrep Rmuserfromgroup options and arguments: Table 16-51. Rmuser Option and Argument (pmrep) Option -u Required/ Optional Required Argument Name username Argument Description User name you want to remove from the repository.

pmrep Change Management Commands pmrep allows you to perform change management tasks such as deploying objects. See “Creating a Label (CreateLabel)” on page 466. Deletes a label object and all object references to the label. Applies a label to an object or set of objects in a folder. See “Clearing a Deployment Group (ClearDeploymentGroup)” on page 465. See “Listing Checked Out Items (FindCheckout)” on page 472. See “Checking In Objects (Checkin)” on page 464. Clears all objects from a deployment group. Creates a label object. running queries. Copies a deployment group. Undoes an object check out. See “Deploying a Folder (DeployFolder)” on page 469. Validates objects. and applying labels. 460 Chapter 16: Using pmrep and pmrepagent . Executes a query. See “Deploying a Deployment Group (DeployDeploymentGroup)” on page 467. See “Creating a Deployment Group (CreateDeploymentGroup)” on page 465. See “Deleting a Deployment Group (DeleteDeploymentGroup)” on page 466. See “Undoing a Checkout (UndoCheckout)” on page 473. See “Validating Objects (Validate)” on page 474. Checks in an object. Table 16-52 describes the pmrep change management tasks: Table 16-52. Prints a list of checked out objects in the repository. Deploys a folder. Creates a deployment group. pmrep Change Management Commands pmrep Command AddToDeploymentGroup ApplyLabel Checkin ClearDeploymentGroup CreateDeployment Group CreateLabel DeleteDeploymentGroup DeleteLabel DeployDeploymentGroup DeployFolder ExecuteQuery FindCheckout UndoCheckout Validate Command Description Adds objects to a deployment group. See “Adding to a Deployment Group (AddToDeploymentGroup)” on page 461. release the lock and revert to the last checked in version. Deletes a deployment group. checking objects in and out. See “Labeling (ApplyLabel)” on page 462. See “Executing a Query (ExecuteQuery)” on page 470. See “Deleting a Label (DeleteLabel)” on page 467.

Adding to a Deployment Group (AddToDeploymentGroup) The AddToDeploymentGroup command adds objects to a deployment group. you must use a persistent input file that contains encoded object IDs. You can specify objects using command options or you can use a persistent input file. Use AddToDeployment Group to add reusable input objects. see Table 16-16 on page 426. see “Working with Deployment Groups” on page 236. scheduler. and task objects. You can specify source. target. see “Using the Persistent Input File” on page 494. session configuration. scheduler. session. If AddToDeploymentGroup runs successfully. session configuration. AddToDeploymentGroup Options and Arguments (pmrep) Option -p -n Required/ Optional Required Required/ Optional Argument Name deployment_group_name object_name Argument Description The name of the deployment group to add objects to. If you want to add non-reusable input objects. You must use this parameter when you add a specific object. session. If the command fails. You cannot specify an object if you use the -i option. -o Required/ Optional object_type -t Required/ Optional object_subtype pmrep Change Management Commands 461 . cube. or it returns a list of objects that already are in the deployment group. you can specify only the deployment group name option. Required when adding a specific object. mapping. The type of object you are adding. worklet. For more information on adding to a deployment group. workflow. If you use a persistent input file. The name of the object you are adding to the deployment group. mapping. and dimension. To add objects to a deployment group. Use AddToDeploymentGroup to add source. You cannot add checked out objects to a deployment group. transformation. For valid subtypes. For more information on using a persistent input file. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Write permission on the folder AddToDeploymentGroup uses the following command syntax: AddToDeploymentGroup -p deployment_group_name -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_types Table 16-53 lists pmrep AddToDeploymentGroup options and arguments: Table 16-53. worklet. You cannot specify a checked out object. target. workflow. it displays the reason for failure. task. The type of task or transformation you are adding. it either sends back no status information. transformation.

you must have the following privileges and permissions: ♦ ♦ ♦ Use Repository Manager privilege Read permission on the folder Execute permission on the label 462 Chapter 16: Using pmrep and pmrepagent . AddToDeploymentGroup Options and Arguments (pmrep) Option -v Required/ Optional Optional Argument Name version_number Argument Description The version of the object to add. If you specify “all”.” If you specify “non-reusable” pmrep adds the object(s) and the corresponding non-reusable dependent objects to the deployment group. If you want to label non-reusable input objects. to the deployment group. If ApplyLabel succeeds. you must use a persistent input file that contains encoded object IDs. The folder that contains the object you are adding.Table 16-53. pmrep displays either no status information or a list of objects that already have the label. If you specify a folder. -f -i Required/ Optional Optional folder_name persistent_input_file -d Optional dependency_types Labeling (ApplyLabel) Use the ApplyLabel command to apply a label to an object or a set of objects in a folder. pmrep does not allow the -n. To label objects. see “Applying Labels” on page 221. You must specify the folder if you specify an object name. If you omit this parameter. If you use this parameter. You can apply the label to dependent objects. Use ApplyLabel to label reusable input objects. pmrep adds the object(s) and all dependent objects. You can specify “non-reusable” or “all. The dependent objects to add to the deployment group with the object. If the command fails. separate each object type name by a comma with no spaces between them on the command line. A text file generated from ExecuteQuery. and -f options. or ListObjectDependencies that contains a list of object records with encoded IDs. To apply a label to selected dependent objects. see “Using the Persistent Input File” on page 494. all the objects in the folder receive the label. If you use the dependent_object_type option. then you do not add dependent objects to the deployment group. For more information on applying labels. For more information about using a persistent input file. Validate. -o. For more information on using a persistent input file. pmrep labels all dependent objects. pmrep displays the failure reason. see “Using the Persistent Input File” on page 494. The default is to add the latest version of the object to the deployment group. reusable and non-reusable.

see Table 16-16 on page 426. or Validate. You cannot specify objects if you use the -i option. The command fails if the version is checked out. If you specify an object type. If you are updating a specific object. For valid subtypes. see “Using the Persistent Input File” on page 494. all dependent objects receive the label. object type. For more information on using the persistent input file. or folder name to specify objects. The type of object to apply the label to. then this parameter is required. -o Required/ Optional object_type -t Required object_subtype -v Optional version_number -f Optional folder_name -i Optional persistent_input_file -d Required dependent_object_type -p Optional dependency_direction pmrep Change Management Commands 463 .ApplyLabel uses the following command syntax: ApplyLabel -a label_name -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependent_object_type -p dependency_direction -s include_pk-fk_dependency -m move_label -c comments Table 16-54 lists pmrep ApplyLabel options and arguments: Table 16-54. The folder that contains the object(s). The name of the object to receive the label. Applies the label to the latest version of the object by default. If you specify a folder. then the label applies to dependent objects of that object type. The name of a text file generated from ExecuteQuery. If you specify a folder with an object name. Required when applying a label to a specific object. You can specify source. You cannot specify a folder if you use the -i option. worklet. The kind of task or transformation you are labeling. workflow. ApplyLabel Options and Arguments (pmrep) Option -a -n Required/ Optional Required Required/ Optional Argument Name label_name object_name Argument Description The label name to apply to the object. but no object name. You can specify parents. Contains a list of objects to receive the label. both. If you use this option. cube. The dependent objects to label. If you do not specify option -d. or dimension. The dependent parents or children to apply the label to. Use this option with option -p. mapping. pmrep applies the label to all objects in the folder. session. pmrep ignores other object types. target. If you do not specify this option. children. task. ListObjectDependency. session config. then do not use the object name. pmrep searches the folder for the object. scheduler. transformation. the label applies only to the specified object. The version of the object to apply the label to.

See “Creating a Label (CreateLabel)” on page 466. Comments about the check in. workflow.Table 16-54. task. session config. The folder to contain the new object version. Move a label from the current version to the latest version of an object. mapping. scheduler. You can use this argument only when the label type is one_per_object. When you check in an object. Checkin Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object you are checking in: source. or dimension. see “Checking In Objects” on page 213. Comments relating to ApplyLabel. The name of the object that you are checking in. worklet. Not required for other object types. session. transformation. ApplyLabel Options and Arguments (pmrep) Option -s -m Required/ Optional Optional Optional Argument Name include_pk-fk_dependency move_label Argument Description Include the primary key-foreign key dependency objects regardless of the direction of the dependency. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Repository Manager privilege and write permission on the folder Administer Repository privilege and write permission on the folder Checkin uses the following command syntax: Checkin -o object_type -t object_subtype -n object_name -f folder_name -c comments Users with Administer Repository privilege can check in objects for other users. cube. Table 16-55 lists pmrep Checkin options and arguments: Table 16-55. For more information on checking in objects. The version number is one number greater than the version number of the last checked-in version. target. To check in objects. the repository creates a new version of the object and assigns it a version number. For valid subtypes. -t Optional object_subtype -n -f -c Required Required Optional object_name folder_name comments 464 Chapter 16: Using pmrep and pmrepagent . The type of task or transformation to check in. -c Optional comments Checking In Objects (Checkin) Use the Checkin command to check in an object that you have checked out previously. see Table 16-16 on page 426.

You can specify static or dynamic. Default is static. To create a dynamic deployment group. CreateDeploymentGroup Options and Arguments (pmrep) Option -p -t Required/ Optional Required Optional Argument Name deployment_group_name group_type Argument Description The name of the deployment group to create. Create a static group or use a query to dynamically create the group. Remove objects without confirmation. You can create a dynamic or static deployment group. and indicate whether the query is private or public. Creating a Deployment Group (CreateDeploymentGroup) Use the CreateDeploymentGroup command to create a deployment group. To create a deployment group. To clear a deployment group. pmrep Change Management Commands 465 . you must supply a query name. If you omit this argument. the command prompts you for a confirmation before it clears the objects. You can use this command to retain the deployment group but remove the objects. see “Working with Deployment Groups” on page 236.Clearing a Deployment Group (ClearDeploymentGroup) Use the ClearDeploymentGroup command to clear all objects from a deployment group. ClearDeploymentGroup Options and Arguments (pmrep) Option -p -f Required/ Optional Required Optional Argument Name deployment_group_name force_delete Argument Description The name of the deployment group that you want to clear. CreateDeploymentGroup uses the following command syntax: CreateDeploymentGroup -p deployment_group_name -t group_type -q query_name -u query_type -c comments Table 16-57 lists pmrep CreateDeploymentGroup options and arguments: Table 16-57. you must have the Use Repository Manager privilege. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Read and write permission on the deployment group ClearDeploymentGroup uses the following command syntax: ClearDeploymentGroup -p deployment_group_name -f force_delete Table 16-56 lists ClearDeploymentGroup options and arguments: Table 16-56. For more information on creating deployment groups.

you can apply the label to only one version. -u Required query_type -c Optional comments Creating a Label (CreateLabel) Use the CreateLabel command to create a label that you can use to associate groups of objects during development. When you create a label. you also remove all objects from the deployment group. see “Working with Deployment Groups” on page 236. If you delete a static deployment group. CreateLabel uses the following command syntax: CreateLabel -a label_name -t label_type -c comments Table 16-58 lists pmrep CreateLabel options and arguments: Table 16-58. To create a label. 466 Chapter 16: Using pmrep and pmrepagent . The type of query to create a deployment group. Allows multiple versions to have this label. Required if the deployment group is dynamic. For more information on deleting deployment groups. but ignored if the group is static. -c Optional n/a Deleting a Deployment Group (DeleteDeploymentGroup) Use the DeleteDeploymentGroup command to delete a deployment group.Table 16-57. CreateLabel Options and Arguments (pmrep) Option -a -t Required/ Optional Required Optional Argument Name label_name label_type Argument Description The name of the label you are creating. but ignored if the group is static. CreateDeploymentGroup Options and Arguments (pmrep) Option -q Required/ Optional Required Argument Name query_name Argument Description The name of the query associated with the deployment group. you must have the Administer Repository privilege. Comments about the new deployment group. or you can specify that a label can apply to only one version of an object (one per object). Required if the deployment group is dynamic. You can associate a label with any versioned object or group of objects in a repository. you can specify that the label can apply to multiple versions of an object (one per version). You can specify shared or personal. Comments about the label. If you omit this option. see “Creating and Editing Labels” on page 219. For more information on creating labels.

the command prompts you for a confirmation before it deletes the label. see “Working with Labels” on page 219. To delete a label. If you omit this argument. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Write permission on the label For more information about deleting labels. the delete fails. Deleting a Label (DeleteLabel) Use the DeleteLabel command to delete a label and remove the label from all objects that use it. pmrep prompts you for a confirmation before it deletes the Deployment Group. DeleteLabel Options and Arguments (pmrep) Option -a -f Required/ Optional Required Optional Argument Name label_name force_delete Argument Description The name of the label to delete.To delete a deployment group. Deletes the Deployment Group without confirmation. Deploying a Deployment Group (DeployDeploymentGroup) Use the DeployDeploymentGroup command to deploy a deployment group. If the label is locked. DeleteLabel uses the following command syntax: DeleteLabel -a label_name -f force_delete Table 16-60 lists pmrep DeleteLabel options and arguments: Table 16-60. pmrep Change Management Commands 467 . If you omit this argument. DeleteDeploymentGroup Options and Arguments (pmrep) Option -p -f Required/ Optional Required Optional Argument Name deployment_group_name force_delete Argument Description The name of the deployment group to delete. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Write permission on the deployment group DeleteDeploymentGroup uses the following command syntax: DeleteDeploymentGroup -p deployment_group_name -f force_delete Table 16-59 lists pmrep DeleteDeploymentGroup options and arguments: Table 16-59. You can optionally use this command to copy deployment groups to different repositories. Delete the label without confirmation.

dtd file. but not both. see “Copying a Deployment Group” on page 254. The login user name for the target repository. The control file is required. The host name of the Repository Server managing the target repository. Not required if you copy the deployment group to the same repository. Not required if you copy the deployment group to the same repository. see “Using the Deployment Control File” on page 504. For more information on using the control file. For more details about the control file. To copy a deployment group. Not required if you copy the deployment group to the same repository. The login password environment variable for the target repository. For more information on deploying a deployment group. Use the -x or -X option. The repository you are deploying the group to. -r -u Required Required/ Optional Required/ Optional target_repository_name target_repository_user_name -x target_repository_user_passwo rd -X Required/ Optional target_repository_password_en vironment_variable -h Required/ Optional target_repository_server_host_ name 468 Chapter 16: Using pmrep and pmrepagent . The name of the XML file containing the Copy Wizard specifications. you must create a control file with all the specifications that the Copy Wizard requires. DeployDeploymentGroup Options and Arguments (pmrep) Option -p -c Required/ Optional Required Required Argument Name deployment_group_name control_file_name Argument Description The name of the group to deploy. Not required if you are copying the deployment group to the same repository. The control file is an XML file defined by the depcntl. The login password for the target repository. you must have the following privileges and permissions: ♦ ♦ ♦ Administer Repository Manager privilege Read permission on the original folders Read and execute permissions on the deployment group DeployDeploymentGroup uses the following command syntax: DeployDeploymentGroup -p deployment_group_name -c control_file_name -r target_repository_name -u target_repository_user_name -x target_repository_user_password -X target_repository_password_environment_variable -h target_repository_server_host_name -n target_repository_server_port_number -l log_file_name Table 16-61 lists pmrep DeployDeploymentGroup options and arguments: Table 16-61.To use this command. see “Using the Deployment Control File” on page 504. Use the -x or -X option. but not both.

Not required if you are copying the deployment group to the same repository. For more information on the control file. Not required if you are copying the deployment group to the same repository. It requires a control file containing specifications that the Copy Wizard requires. -l Deploying a Folder (DeployFolder) The DeployFolder command allows you to deploy a folder. Use the -x or -X option. The control file is an XML file defined by the depcntl.Table 16-61. but not both. The name of the XML file containing the copy wizard specifications. DeployDeploymentGroup Options and Arguments (pmrep) Option -n Required/ Optional Required/ Optional Optional Argument Name target_repository_server_port_ number log_file_name Argument Description The port number of the Repository Server.dtd file. For more details about the control file. DeployFolder Options and Arguments (pmrep) Option -f -c Required/ Optional Required Required Argument Name folder_name control_file_name Argument Description The name of the folder to deploy. To copy a folder. The repository name to deploy the group to. see “Using the Deployment Control File” on page 504. Not required if the target repository is the same as the source. it outputs to the screen. The login user name for the target repository. Not required if you are copying the deployment group to the same repository. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Read permission on the original folder DeployFolder uses the following command syntax: DeployFolder -f folder_name -c control_file_name -r target_repository_ name -u target_repository_user_name -x target_repository_user_password -X target_repository_password_environment_variable -h target_repository_server_host_name -n target_repository_server_port_ number -l log_file_name Table 16-62 lists pmrep DeployFolder options and arguments: Table 16-62. -r Optional target_repository_name -u Optional target_repository_user_name -x Required/ Optional target_repository_user_passwo rd pmrep Change Management Commands 469 . see “Using the Deployment Control File” on page 504. The log file that records each deployment step. The login password for the target repository. If you omit this option.

Use the -x or -X option. You can choose to display the result or write the result to a persistent input file. it outputs to the screen. -h Optional target_repository_server_host_ name target_repository_server_port_ number log_file_name -n Optional -l Optional Executing a Query (ExecuteQuery) Use the ExecuteQuery command to run a query. 470 Chapter 16: Using pmrep and pmrepagent . Not required if you copy the deployment group to the same repository. and Validate commands. If not specified. If the query is successful. AddToDeploymentGroup. DeployFolder Options and Arguments (pmrep) Option -X Required/ Optional Required/ Optional Argument Name target_repository_password_en vironment_variable Argument Description The login password environment variable for the target repository. You can use this file as input to the ApplyLabel. but not both.Table 16-62. The port number of the Repository Server. The type of query to run. You can specify public or private. If you omit this option. To execute a query. The log file that records each deployment step. you must have the following privileges and permissions: ♦ ♦ ♦ Browse Repository privilege Write permission on the folder Read and execute permissions on the query ExecuteQuery uses the following command syntax: ExecuteQuery -q query_name -t query_type -u persistent_output_file_name a append -c column_separator -r end-of-record_separator -l end-oflisting_indicator -b verbose Table 16-63 lists pmrep ExecuteQuery options and arguments: Table 16-63. see “Using the Persistent Input File” on page 494. Not required if you copy the deployment group to the same repository. The host name of the Repository Server managing the target repository. it returns the total number of qualifying records. pmrep searches all the private queries first to find the matching query name. For more details on using a persistent input file. Not required if you are copying the deployment group to the same repository. Then it searches the public queries. ExecuteQuery Options and Arguments (pmrep) Option -q -t Required/ Optional Required Optional Argument Name query_name query_type Argument Description The name of the query to run.

version number. pmrep prints a shorter format including the object type. you might want to avoid using a space as a column separator. includes the object type and object name. If any repository object name contains spaces. pmrep uses a new line. Verbose format includes the label type. creator name. Use a character or set of characters that is not used in repository object names. Verbose format includes the object status. Specify a character or set of characters that is not used in repository object_names. If you omit this option. ExecuteQuery Options and Arguments (pmrep) Option -u -a Required/ Optional Optional Optional Argument Name persistent_output_file_name append Argument Description Send the query result to a text file. The character or set of characters used to specify the end of the object list. pmrep uses a period. query type. folder name. deployment group. and checked out information. If you omit this option. Print more than the minimum information about the objects. The character or set of characters used to specify the end of the object metadata. pmrep overwrites the file content. If you omit this option. the query result goes to stdout. pmrep uses a single space. -c Optional column_separator -r Optional end-of-record_separator -l Optional end-of-listing_indicator -b Optional verbose pmrep Change Management Commands 471 . If you do not specify to append.Table 16-63. and connection. the object name and path. The character or set of characters used to separate object metadata columns. If you omit this option. and creation time. If you do not specify a file name. The option to append the query results to the persistent output file. the word reusable or non-reusable. query. Use a character or set of characters that is not used in repository object names. deployment group type. The short format for versioning objects such as label.

The default is to list objects for the object type across folders. Note: You can use FindCheckout with no options. The character or set of characters used to separate object metadata columns. pmrep returns all the checked out objects in the repository. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the folder FindCheckout uses the following command syntax: FindCheckout -o object_type -f folder_name -u all_users -c column_ separator -r end-of-record_separator -l end-of-listing_indicator -b verbose Table 16-64 lists pmrep FindCheckout options and arguments: Table 16-64. scheduler. Use a character or set of characters that is not used in repository object names. workflow. To list checked out items. target. You can specify source. If you omit this option. see “Checking Out and Checking In Objects” on page 211. mapping. session. pmrep uses a single space. For more information about finding checked out objects. The listing contains only your checked out items unless you specify “all users. List the checked out objects by all users. or dimension. If any repository object name contains spaces. Folder name is optional if you specify an object type. -f Optional folder_name -u -c Optional Optional all_users column_separator 472 Chapter 16: Using pmrep and pmrepagent . If you do not specify an object type. transformation. If you omit object type. task. then you can list checked out objects in a specific folder or across all folders. you might want to avoid using a space as a column separator.” If you choose an object type.Listing Checked Out Items (FindCheckout) Use the FindCheckout command to print a list of checked out objects in the repository. cube. session config. Return a list of checked out objects for the object type in the specified folder. worklet. pmrep ignores the -f and -u options and the command returns all checked-out objects in the repository. FindCheckout Options and Arguments (pmrep) Option -o Required/ Optional Optional Argument Name object_type Argument Description The object type you want to list. The default is to list only checked out objects by the current user.

UndoCheckout uses the following command syntax: UndoCheckout -o object_type -t object_subtype -n object_name -f folder_name pmrep Change Management Commands 473 . If you want to modify the object again. see “Using the Designer” in the Designer Guide. Use a character or set of characters that is not used in repository object names. pmrep prints a shorter format including the object type. deployment group. includes the object type and object name. For details on undoing a checkout. you must check it out. or “Using the Workflow Manager” in the Workflow Administration Guide.Table 16-64. -l Optional end-of-listing_indicator -b Optional verbose Undoing a Checkout (UndoCheckout) Use the UndoCheckout command to undo a checkout of an object. If you omit this option. The short format for versioning objects such as label. Use a character or set of characters that is not used in repository object names. Print more than the minimum information about the objects. and connection. The character or set of characters used to specify the end of the object list. the repository releases the write-intent lock on the object and reverts to the most recently checked in version of the object. Verbose format includes the creator name and creation time. The default is newline /n. To undo a checkout. the object name and path. If you omit this option. query. FindCheckout Options and Arguments (pmrep) Option -r Required/ Optional Optional Argument Name end-of-record_separator Argument Description The character or set of characters used to specify the end of the object metadata. the word reusable or non-reusable. When you undo a checkout. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager or Administer Repository privilege Write permission on the folder Users with Administer Repository privilege can undo checkouts for other users. Verbose format includes the version number and folder name. pmrep uses a period.

You can specify source. task. UndoCheckout Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object. workflow. dimension. You can validate the following types of objects: ♦ ♦ ♦ ♦ ♦ Mappings Mapplets Sessions Workflows Worklet objects If you use another type of object in the input parameter. If you use the wrong type of object in a persistent input file. pmrep reports an error and skips the object. invalid objects. transformation. save_failed. For valid subtypes. Shortcuts and object types that do not require validation. session config. Ignored for other object types. target. The summary includes the number of valid objects. Note: The pmrep Validate command does not validate shortcuts. encoded IDs.Table 16-65 lists pmrep UndoCheckout options and arguments: Table 16-65. see Table 16-16 on page 426. The persistent output file contains standard information. 474 Chapter 16: Using pmrep and pmrepagent . You can choose to output the results to a persistent output file or standard output. Objects invalid before the validation check. session. -t -n -f Required/ Optional Required Required object_subtype object_name folder_name Validating Objects (Validate) The Validate command validates objects. When you run Validate. The name of the checked out object. and a CRC check. invalid_after. The type of transformation or task. The name of the folder containing the object. worklet. invalid_before. Objects invalid after the validation check. It also displays a validation summary to stdout. skipped. and skipped objects. Objects that did not save because of lock conflicts or they were checked out by another user. you can choose to output information about object status: ♦ ♦ ♦ ♦ ♦ ♦ valid. Objects saved after validation. saved. cube. pmrep returns an error. You can choose to save and check in the objects that change from invalid to valid. scheduler. Objects successfully validated. mapping.

scheduler. The kind of object you want to output to the persistent output file or stdout after validation. separate them by commas. cube. Validate. The text file from ExecuteQuery. or -f arguments. Check in saved objects. Add comments when you check in an object. Required if you use the -k option. Ignored for other object types. session. dimension. To specify one or more options. You can specify source. Required if you use -s. You cannot use this file if you are specifying objects using the -n. The version of the object to validate. and the current repository requires checkin comments. workflow. The type of task or transformation. task. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Write permission on the folder Validate uses the following command syntax: Validate -n object_name -o object_type -t object_subtype -f folder_name -v version_number -i persistent_input file -s save_upon_valid -k check_in_upon_valid -m check_in_comments -p output_options -u persistent_output_file_name -a append -c column_separator -r end-of-record_separator -l end-of-listing_indicator -b verbose Table 16-66 lists pmrep Validate options and arguments: Table 16-66. You can specify valid. transformation. The name of the folder containing the object. -t Required/ Optional Required Optional Optional object_subtype -f -v -i folder_name version_number persistent_input file -s -k -m Optional Optional Required/ Optional Optional save_upon_valid check_in_upon_valid check_in_comments -p output_options pmrep Change Management Commands 475 . For valid subtypes. or ListObjectDependencies commands.To validate objects. target. Save objects that change from invalid to valid to the repository. skipped. -o. Contains a list of object records. The default is the latest or checked out version of the object. Do not use this option if you are using the -i argument. mapping. saved. The type of object to validate. Validate Options and Arguments (pmrep) Option -n -o Required/ Optional Required Required/ Optional Argument Name object_name object_type Argument Description The name of the object to validate. see Table 16-16 on page 426. Required if you are not using a persistent input file. invalid_before. or invalid_after. worklet. session config. You should specify output_options when you use the persistent_output_file_name. save_failed.

pmrep uses a single space. -a -c Optional Optional append column_separator -r Optional end-of-record_separator -l Optional end-of-listing_indicator -b Optional verbose 476 Chapter 16: Using pmrep and pmrepagent . If you omit this option. the object name and path. you might want to avoid using a space as a column separator. The default is newline /n. Print more than the minimum information about the objects. If you omit this option. If any repository object name contains spaces. Verbose format includes the version number and folder name. pmrep prints a shorter format including the object type. deployment group. Use a character or set of characters that is not used in repository object names. Specify a character or set of characters that is not used in repository object names. The character or set of characters used to specify the end of the object list. The short format for versioning objects such as label. Validate Options and Arguments (pmrep) Option -u Required/ Optional Optional Argument Name persistent_output_file_name Argument Description The name of an output text file. If you specify a file name. query. The character or set of characters used to specify the end of the object metadata. The character or set of characters used to separate object metadata columns. Append the results to the persistent output file instead of overwriting it. Use a character or set of characters that is not used in repository object names. Verbose format includes the creator name and creation time. the query writes the results to a file.Table 16-66. and connection. You should also specify output_options. If you omit this option. pmrep uses a period. the word reusable or non-reusable. includes the object type and object name.

Restores a Teradata repository from a repository backup file using Fastload. Unregisters a plug-in module from the repository. Creates repository tables in the database. See “Restoring a Repository (Restore)” on page 485. Backup uses the following command syntax: backup -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m trusted_connection -c database_connect_string -o output_file_name -d description -f -b skip_workflow/session_log -j skip_deploy_group_history -q skip_MX_data pmrepagent Commands 477 . See “Deleting a Repository (Delete)” on page 481. pmrepagent runs in command line mode only. To run pmrepagent commands. You must provide the backup filename. switch to the Repository Server \bin directory and enter pmrepagent followed by the command name and its required options and arguments. Upgrades an existing repository to the latest version. See “Registering a Plug-in (Registerplugin)” on page 482. See “Creating a Repository (Create)” on page 480. pmrepagent.pmrepagent Commands You can use the Repository Agent command line program. See “Unregistering Plug-ins (Unregisterplugin)” on page 487. Backing up a Repository (Backup) The Backup command backs up a repository to the file specified with the -o option. Specify pmrepagent options and arguments the same way you specify pmrep options and arguments. See “Backing up a Repository (Backup)” on page 477. to perform repository functions such as restoring and deleting repositories. Deletes the repository tables from the database. Registers a new external module to the repository. See “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Table 16-67 describes pmrepagent commands: Table 16-67. Restores a repository from a repository backup file. See “Upgrading a Repository (Upgrade)” on page 490. Use this command when the repository is not running. pmrepagent Commands pmrepagent Command Backup Bulkrestore Create Delete Registerplugin Restore Unregisterplugin Upgrade Command Description Backs up a repository.

Table 16-68 lists pmrepagent Backup options and arguments: Table 16-68. For a list of connect string syntax. The repository user name. This option has no argument. 478 Chapter 16: Using pmrep and pmrepagent . Skips tables related to MX data during backup. Skips tables related to workflow and session logs during backup. see “Backing up a Repository (Backup)” on page 416. Backup Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name repository_user_name repository_password repository_password_environ ment_variable database_type database_user_name database_password Argument Description The name of the repository you want to back up. Not required if you are using option -m. The type of database the repository resides on. The description of the repository you backup. Valid for Microsoft SQL Server only. Use the -p or -P option. but not both. but not both. but not both. The repository database password. You can use the pmrep Backup command when the repository is running. The repository database password. The repository database user name. but not both. Include this option if you want to overwrite any existing file with the same name. Use the -x or -X option. Use the -p or -P option. Skips deployment group history during backup. The connect string the Repository Agent uses to connect to the repository database. The repository password. The repository password environment variable. -P database_password_environ ment_variable trusted_connection database_connect_string -m -c -o -d -f -b -j -q Required Required Optional Optional Optional Optional output_file_name description n/a skip_workflow/session_log skip_deploy_group_history skip_MX_data Note: pmrep also allows you to back up a repository. For details. The name and path of the file for the repository backup. Use the -x or -X option. Not required if you are using option -m. see Table 16-1 on page 405. Use a trusted connection to connect to the database.

but not both. Enter “fastload” for Teradata. Bulkrestore Options and Arguments (pmrepagent) Option -r -t -u -p -P -c Required/ Optional Required Required Required Required/ Optional Required/ Optional Required Argument Name repository_name database_type database_user_name database_password database_password_environ ment_variable database_connect_string Argument Description The name of the repository you want to restore. The repository database user name. The repository database password. The port number of the Repository Server that manages the repository. but not both. the Repository Server looks for the file in the Repository Server backup directory. see Table 16-1 on page 405. Use the -p or -P option. This option has no argument. You can specify any file name and path local to the Repository Server. The repository code page. The name of the repository backup file. For a list of connect string syntax. Bulkrestore uses the following command syntax: bulkrestore -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -d codepage -h host_name -o port_number -g -i backup_file_name -e external_loader_type -s server_name -a license_file_name -y enable_object_versioning -b skip_workflow/ session_log -j skip_deploy_group_history -q skip_MX_data Table 16-69 lists pmrepagent Bulkrestore options and arguments: Table 16-69. Use the -p or -P option. Use this option if you want to promote the repository to a global repository. The repository database password environment variable. The connect string the Repository Agent uses to connect to the repository database. The Bulkrestore command can be faster than the Restore command when the repository backup file is greater than 100 MB. The host name of the Repository Server that manages the repository. If you do not specify a path. -d -h -o -g -i Optional Required Required Optional Required codepage host_name port_number n/a backup_file_name -e -s Required Required external_loader_type server_name pmrepagent Commands 479 . Enter “Teradata” to restore to a Teradata database.Restoring Teradata Repositories using Fastload (Bulkrestore) The pmrepagent Bulkrestore command restores Teradata repositories using Fastload. The name of the Teradata database server.

Before you can create a repository. The repository database user name.Table 16-69. Not required if you are using option -m. Bulkrestore Options and Arguments (pmrepagent) Option -a -y -b -j -q Required/ Optional Required Optional Optional Optional Optional Argument Name license_file_name enable_object_versioning skip_workflow/session_log skip_deploy_group_history skip_MX_data Argument Description The name of the license file. you must create and configure the database to contain the repository. -P database_password_environme nt_variable n/a database_connect_string -m -c 480 Chapter 16: Using pmrep and pmrepagent . Use the -p or -P option. but not both. Skips tables related to workflow and session logs during backup. For a list of connect string syntax. Use the -p or -P option. Skips deployment group history during backup. Valid for Microsoft SQL Server only. see “Creating a Repository” on page 116. Enables object versioning. The repository database password environment variable. Use a trusted connection to connect to the database. The type of database the repository resides on. Skips tables related to MX data during backup. Create Options and Arguments (pmrepagent) Option -r -t -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name database_type database_user_name database_password Argument Description The name of the repository you want to create. Create uses the following command syntax: Create -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -d code_page -h host_name -o port_number -g -v -a license_file_name -z repository_creation_parameters Table 16-70 lists pmrepagent Create options and arguments: Table 16-70. Not required if you are using option -m. The connect string the Repository Agent uses to connect to the repository database. but not both. Creating a Repository (Create) The pmrepagent Create command creates a repository in the database. For more information on creating repositories. see Table 16-1 on page 405. The repository database password.

Delete uses the following command syntax: Delete -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -f Table 16-71 lists pmrepagent Delete options and arguments: Table 16-71. but not both. For more information about deleting a repository. This option has no argument. Create Options and Arguments (pmrepagent) Option -d -h -o -g -z Required/ Optional Optional Required Required Optional Optional Argument Name code_page host_name port_number n/a repository_creation_parameters Argument Description The repository code page. -a -v Required Optional license_file_name n/a The name of the license file. but not both. pmrepagent Commands 481 . Include this option if you want to promote the repository to a global repository. The repository user name. Use this option to specify the tablespace name for IBM DB2 EEE databases. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” Do not include spaces around the equals sign. The port number of the Repository Server that manages the repository. pmrepagent interprets the spaces as part of the tablespace name. Delete Options and Arguments (pmrepagent) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_envir onment_variable Argument Description The name of the repository you want to delete. The repository password. Deleting a Repository (Delete) The pmrepagent Delete command deletes the repository tables from the repository database. The host name of the Repository Server that manages the repository. This option has no argument. The repository password environment variable. Include this option if you want to enables object versioning for the repository. Use the -x or -X option. Use the -x or -X option. see “Deleting a Repository” on page 64.Table 16-70.

-f Required/ Optional n/a Registering a Plug-in (Registerplugin) The pmrepagent Registerplugin command registers an external plug-in to a repository. Registerplugin uses the following command syntax: Registerplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -i input_xml_file_name -e -f force_registration -l login_name -w login_password -W login_password_environment_variable -k Table 16-72 lists pmrepagent Registerplugin options and arguments: Table 16-72. For more information about registering a plug-in. Use the -p or -P option. The repository database password environment variable. see Table 16-1 on page 405. The repository database password. The repository password. Use the -x or -X option. but not both. Use this option to delete a global repository. Registerplugin Options and Arguments (pmrepagent) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_envir onment_variable Argument Description The name of the repository.Table 16-71. but not both. Delete Options and Arguments (pmrepagent) Option -t -u -p -P -c Required/ Optional Required Required Required/ Optional Required/ Optional Required Argument Name database_type database_user_name database_password database_password_enviro nment_variable database_connect_string Argument Description The type of database the repository resides on. All registered local repositories must be running. For a list of connect string syntax. 482 Chapter 16: Using pmrep and pmrepagent . The repository password environment variable. Use the -p or -P option. Use the -x or -X option. but not both. This option unregisters local repositories. You can use the Registerplugin command to update existing plug-ins. see “Registering a Repository Plug-in” on page 85. but not both. The repository user name. The repository database user name. Registering a plug-in adds its functionality to the repository. The connect string the Repository Agent uses to connect to the repository database.

The repository database user name. The repository database password. The connect string the Repository Agent uses to connect to the repository database. Indicates to use a trusted connection to connect to the database. see Table 16-1 on page 405. Use the -p or -P option. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. The password is not required if you are using option -m. Use the -w or -W option. but not both. The repository database password environment variable. it generates an error. The name of the XML file describing the plug-in. Indicates to unregister and re-register a plug-in if it already exists. but not both. Not applicable for authentication modules. but not both. Valid for Microsoft SQL Server only. For a list of connect string syntax. The external directory password of the user registering the module. This login becomes the administrator user name in the repository. or the registration fails. The NIS login of the user registering an external security module. Do not use this option for other plug-ins. Do not use this option for other plug-ins. If the plug-in exists. -P database_password_enviro nment_variable n/a database_connect_string -m -c -i -e -f Required Optional Optional input_xml_file_name n/a force_registration -l Required if registering security module components Required/ Optional login_name -w login_password pmrepagent Commands 483 . and you do not specify this option. The password is not required if you are using option -m. If the plug-in contains an authentication module you must supply the external login name.Table 16-72. Update an existing plug-in. Required if registering authentication module components. Use the -p or -P option. Registerplugin Options and Arguments (pmrepagent) Option -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name database_type database_user_name database_password Argument Description The type of database the repository resides on. Not applicable for authentication modules.

When he upgrades PowerCenter. The upgrade installs the LDAP security module in the repository security folder. When the Repository Agent loads the module. the administrator user must use this login name and password to access the repository. but not both. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. Stores the CRC of the plug-in library in the repository. Registerplugin Options and Arguments (pmrepagent) Option -W Required/ Optional Required/ Optional Argument Name login_password_environme nt_variable Argument Description The external directory password environment variable of the user registering the module. The -i option contains the XML file name that describes the security module.Table 16-72. it checks the library against the CRC. Required if registering authentication module components. or the administrator cannot access the repository using LDAP. -k Optional n/a Registering a Security Module If you want to use an external directory service to maintain users and passwords for a repository. 484 Chapter 16: Using pmrep and pmrepagent . you must register the security module with the repository. Note: The login name and password must be valid in the external directory. You can use the Registerplugin command to register the security plug-in. see “Registering and Unregistering LDAP Security Modules” on page 88. For more information about this XML file. Do not use this option for other plug-ins. The administrator runs the pmrepagent command to register the new external module with the repository: pmrepagent registerplugin -r repositoryname -n Administrator -x RepoPasswd -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -i security/ldap_authen. he decides to use the LDAP for repository user authentication. Use the -w or -W option. Example An administrator administers PowerCenter for a company that has a centralized LDAP NIS for user authentication. After registration.xml -l adminuser -w admnpass The -l login name and -w login password options contain the valid NIS login information for the user running the pmrepagent command.

The target database must be empty. you can use the -v administrator_username and -x administrator_password to verify that one administrative user can connect to the repository if the restore completes. For a list of connect string syntax. The repository database password. The repository database password environment variable. then the Administrator’s password does not change when you restore the repository. the Repository Agent does not assume that the same user authentication module is on the new system. The repository database user name. but not both. see Table 16-1 on page 405. The repository code page. Not required if you are using option -m. The Repository Agent resets the Administrator’s password to “Administrator.Restoring a Repository (Restore) The pmrepagent Restore command restores a repository backup file to a database. Restore uses the following command syntax: Restore -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -d code_page -h repserver_host_name -o repserver_port_number -g -i backup_file_name -z repository_creation_parameters -v administrator_username -x verify_password -X verify_password_environment_variable -a license_file_name -w -b skip_workflow/session_log -j skip_deploy_group_history -q skip_MX_data Table 16-73 lists pmrepagent Restore options and arguments: Table 16-73. Use the -p or -P option. The connect string the Repository Agent uses to connect to the repository database. Restore Options and Arguments (pmrepagent) Option -r -t -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name database_type database_user_name database_password Argument Description The name of the repository you want to restore. -P database_password_environme nt_variable n/a database_connect_string -m -c -d Optional code_page pmrepagent Commands 485 . If you do not use these options. or if the password is incorrect. Valid for Microsoft SQL Server only. Not required if you are using option -m. If the repository you are restoring uses an external directory service. When you restore a repository to a different system. The type of database you want to restore to.” Note: If the repository uses repository authentication. but not both. the Repository Agent unregisters the external module and resets the Administrator password after the restore. Use the -p or -P option. see “Restoring a Repository” on page 67. For more information about restoring a repository. Use a trusted connection to connect to the database.

Use this option to specify the tablespace name for IBM DB2 EEE databases. Verify password. -v Optional/ Required for retaining an external security module. Include this option if you want to promote the repository to a global repository. pmrepagent interprets the spaces as part of the tablespace name. administrator_username Specifies repository administrator user name. Use this option to force the Repository Agent to verify that the administrator user is valid with the current authentication module. The name of the repository backup file. Use the -x or -X option.Table 16-73. The Repository Agent verifies that this password is valid for the user name on the target server. This option has no argument. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” -i Required backup_file_name -z Optional repository_creation_parameters Do not include spaces around the equals sign. Restore Options and Arguments (pmrepagent) Option -h -l -o -g Required/ Optional Required Required Required Optional Argument Name repserver_host_name license_file_name repserver_port_number n/a Argument Description The host name of the Repository Server that manages the repository. Use this option only with a repository using an external security module. -x Required/ Optional verify_password 486 Chapter 16: Using pmrep and pmrepagent . You must use either the -x or -X option when you want to retain an external security module. Use this option only with a repository using an external security module. The port number of the Repository Server that manages the repository. Use this option with the -v option when you want to retain the external security module after restoring. The repository license file name. You must use this option to retain the external module registration after the restore. but not both. You can use any file name and path local to the Repository Server.

Removes user name-login mapping. Skips deployment group history during backup. Use this option only when unregistering an external module. -a -w -b -j -q Required Optional Optional Optional Optional license_file_name n/a skip_workflow/session_log skip_deploy_group_history skip_MX_data Note: You can also restore Teradata repositories using Fastload. You must use either the -x or -X option when you want to retain an external security module. Skips tables related to workflow and session logs during backup. The Repository Agent verifies that this password is valid for the user name on the target server.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. Skips tables related to MX data during backup. Unregisterplugin uses the following command syntax: Unregisterplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable-m -c database_connect_string -v vendor_id -l plugin_id -g remove_user_name_login_mapping -w new_password -W new_password_environment_variable pmrepagent Commands 487 . see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. For more information on unregistering plug-ins. restore -r repository1 -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -h solaris001 -o 5001 -v adminuser -x adminpass -i repository1_backup. but not both. Example The following example restores a repository to a Solaris machine and specifies the administrator user name and password in order to keep the LDAP security module registration. Use this option only with a repository using an external security module. For more information. see “Unregistering a Repository Plug-in” on page 86. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. The name of the license file. Use the -x or -X option.Table 16-73. Use this option with the -v option when you want to retain the external security module after restoring.

The repository user name. Indicates to use a trusted connection to connect to the database. you retain the mapping in the repository.Table 16-74 lists pmrepagent Unregisterplugin options and arguments: Table 16-74. The type of relational connection. The repository database password environment variable. For a list of connect string syntax. You define this identification number when you register the plug-in. remove_user_name_login_mappi ng 488 Chapter 16: Using pmrep and pmrepagent . The repository database user name. but not both. Use this option only when you are unregistering a security module. Use the -x or -X option. Use the -p or -P option. The password is not required if you are using option -m. Valid for Microsoft SQL Server only. see Table 16-1 on page 405. If you omit this option. -P database_password_environment _variable -m -c Optional Required n/a database_connect_string -v Required vendor_id -l Required plugin_id -g Optional. Removes the mapping between user names and login names in the repository when you unregister an external security module. see Table 16-9 on page 418. but not both. Identifies the plug-in by identification number. Applicable when registering an external security module. but not both. Identifies the security plug-in by vendor identification number. For a list of valid database types. The repository database password. The repository password environment variable. Use the -p or -P option. You define this number when you register the plug-in. The password is not required if you are using option -m. The repository password. The connect string the Repository Agent uses to connect to the repository database. Unregisterplugin Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_environment _variable database_type database_user_name database_password Argument Description The name of the repository you want to upgrade. but not both. but the Repository Manager does not display them anywhere. Use the -x or -X option.

-W Required/ Optional new_password_environment_vari able Unregistering an External Security Module You can use the Unregisterplugin command to discontinue using an external security module with a repository. Unregisterplugin Options and Arguments (pmrepagent) Option -w Required/ Optional Required/ Optional Argument Name new_password Argument Description Specifies a new password for the user running the unregister command. When you unregister an external authentication module. pmrepagent Commands 489 . Use the -w or -W option. Any users that you added to the system under repository authentication can log in with their old user names and passwords. You must specify a new password in order to access the repository. Any users you added to the repository under the LDAP security cannot log in until you enable their user names. You can use the mapping again if you register a new security module. you decide to switch from the LDAP security module back to repository authentication. Required when the plug-in contains a security module. Required when the plug-in contains a security module.Table 16-74. you do not lose the mapping between the repository user names and the external security login names unless you specify the -g option. but not both. Specifies a new password environment variable for the user running the unregister command. If you unregister the external security module. When you unregister the security module. You must specify a new password in order to access the repository. Example As an administrator. all user passwords reset to the values in the repository. all user passwords reset to the values in the repository. but not both. PowerCenter switches to repository authentication mode. Use the -w or -W option. the Repository Manager does not display the external logins while running under repository user authentication. Note: Although you can save the associations between external logins and repository user names. You remove the user name-login mapping. When you unregister an external authentication module. Note: The Administrator must provide his LDAP NIS login and password to use the Unregisterplugin command. He must also provide a new password to use after he switches back to repository user authentication. You must use the -w or -W option to create a new password for yourself when you unregister the security module. All user passwords reset to the values in the repository instead of the values in the external directory.

The repository password environment variable. but not both. -P database_password_environment _variable n/a database_connect_string -m -c 490 Chapter 16: Using pmrep and pmrepagent . The type of database you want to upgrade to. The repository database password. see “Upgrading a Repository” in the Installation and Configuration Guide. The repository user name. Valid for Microsoft SQL Server only. see Table 16-1 on page 405. Upgrade uses the following command syntax: Upgrade -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string Table 16-75 lists pmrepagent Upgrade options and arguments: Table 16-75.The administrator might use a command similar to this: pmrepagent unregisterplugin -r repositoryname -n Administrator -x RepoPasswd -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -v 1 -l 3014 -g -w newadmnpass Upgrading a Repository (Upgrade) The pmrepagent Upgrade command upgrades a repository to the latest version. The connect string the Repository Agent uses to connect to the repository database. Use the -p or -P option. Upgrade Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name repository_user_name repository_password repository_password_environment _variable database_type database_user_name database_password Argument Description The name of the repository you want to upgrade. Not required if you are using option -m. For a list of connect string syntax. For more information on upgrading repositories. but not both. Not required if you are using option -m. Use the -x or -X option. The repository password. but not both. but not both. Use the -x or -X option. Use a trusted connection to connect to the database. The repository database user name. Use the -p or -P option. The repository database password environment variable.

connects to and backs up a repository called Production on a server named Central: backupproduction. In this case.. You cannot run pmrep batch files while in pmrep interactive mode. you might use pmrep to perform a daily backup of a production repository. For example.rep You can run script files from the command interface..bat REM This batch file uses pmrep to connect to and back up the repository Production on the server Central @echo off echo Connecting to repository Production.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. c:\PowerCenter\pmrep\pmrep connect -r Production -n Administrator -x Adminpwd -t “microsoft sql server” -u sbrown -p sbrownx -c Central@Production echo Backing up repository Production.bat. backupproduction. For instance.. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup.. Informatica recommends that you include a connect command as the first command called by the script file. This helps ensure you are performing tasks on the correct repository. you might use some commands with specific options and arguments on a regular basis. Return code (0) indicates that the command succeeded. Tip: When you create script files using pmrep commands. Scripting pmrep and pmrepagent Commands 491 . the following Windows batch file. you can create a script file to call one or more pmrep commands including its options and arguments. Return code (1) indicates the command failed. pmrep and pmrepagent indicate the success or failure of a command with a return code.

Bulkrestore uses Fastload when it restores a Teradata database. When you include the -n option. and to indicate the end of the listing. If you do not specify this option with the valid administrator user name and password. The source or target instance name must match the name displayed in the session properties or the name output by the Listtablesbysess command. Use the -n option to use the Listtablesbysess command with the Updatesrcprefix or Updatetargprefix commands in a shell script if the source and target instance names match. Use characters that are not used in repository object names when you specify characters to separate records and columns. use the -n option to update a source even if the session uses a shortcut to a mapping.Tips Use Bulkrestore to restore Teradata repositories. You lose the login name-user name mappings. Use the -v option when restoring a repository that uses an external directory service for user management. the restored repository defaults to repository authentication mode. 492 Chapter 16: Using pmrep and pmrepagent . Use the -n option when you use the Updatesrcprefix or Updatetargprefix commands. you can retain the external directory service registration for the repository. specify a character or set of characters that is not used in repository object names for the column separator. end of record indicator. The Bulkrestore command is faster than the Restore command when the repository backup file is greater than 100 MB. This helps you use a shell script to parse the object metadata. and end of listing indicator. Also. When you include the -v option with Restore. When using ListObjects. you must enter the name of the source or target instance for the -t option.

494 Using the Object Import Control File. 496 Using the Deployment Control File. 504 Scripting pmrep and pmrepagent Commands. 507 493 .Appendix A Working with pmrep Files This appendix includes the following topics: ♦ ♦ ♦ ♦ Using the Persistent Input File.

and it can create one. The persistent input file represents objects already in your repository. The following is a sample persistent input file: 2072670638:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944199885:138608640183285:1376256153425:131072168215:65536142655:0288235: 088154:65536122855. and it can create one. For more information about the CRCVALUE. ApplyLabel.M_ITEMS_2.Using the Persistent Input File When you run pmrep with some tasks.mapping.mapping. You can use a persistent input file with the following pmrep commands: ♦ ♦ ♦ ♦ ♦ ♦ AddToDeploymentGroup. Export objects to an XML file.EXPORT. The persistent input file has the following format: encoded ID. object_name. You can create a persistent input file manually or by using pmrep.none. When you create a persistent input file with pmrep. The pmrep commands that use a persistent input file get object information from the encoded IDs.none. object_subtype.EXPORT. This ID identifies which repository the record comes from and prevents you from misusing the file and corrupting a repository. or ListObjectDependencies commands. Validate. ObjectExport.EXPORT. The encoded IDs enable pmrep to process your input file quickly. Run a query to create a persistent input file.none. You can use the file for other pmrep commands. It also contains an encrypted repository GID. This command can use a persistent input file for processing. see “CRCVALUE Codes” on page 267. Add objects to a Deployment Group.1 494 Appendix A: Working with pmrep Files . Label objects.M_NIELSEN. ExecuteQuery. you can use a persistent input file to specify repository objects that you want to process.M_ITEMS. List dependency objects. This command can use a persistent input file for processing.2 1995857227:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944135065:13867417666804:1376256233835:19660880104:65536271545:0319425:01 7154:6553644164. resusable|non-reusable Creating a Persistent Input File with pmrep You can create a persistent input file using the pmrep ExecuteQuery. it creates the file in the pmrep installation directory. These commands create files that contain a list of objects with encoded IDs and a CRCVALUE (Cyclic Redundancy Checking) code. You can specify a different path.mapping. object_type. version_number. foldername. ListObjectDependencies.3 1828891977:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944279765:138739712184505:137625613474:65536221345:65536133675:091734:090 53:65536156675. Validate. Validate objects.

and tasks.EXPORT. Use the “reusable or non-reusable” column only for object types that can be reusable or non-reusable. Using the Persistent Input File 495 . You might create a query called “find_deleted_objects. such as transformations. it finds all the deleted objects in the repository and outputs the results to a persistent input file. worklets. The record has the word “none” in place of the encoded ID. myfolder. pmrep requires you to enter all the column arguments. ObjectExport -i deletes_workfile -u exported_del_file Creating a Persistent Input File Manually If you manually create a persistent input file you must enter the word “none” in place of the encoded ID. You must put the arguments in the correct order. Object_subtype is the type of transformation or task.1 Example You can use the ExecuteQuery command to create a persistent input file of objects to process in another pmrep command. For example.source.none.M_OS1.mapping.newsrc. ExecuteQuery -q find_deleted_objects -t private -u deletes_workfile You can use deletes_workfile as the persistent input file to ObjectExport. except for the last column. This is an example from a manually created file: none.2 The object is a source object. The pmrep commands get the object information from the other arguments in the records. put the word “none” in the object_subtype argument.” When you run the query with pmrep.Oracle. sessions.3267622055:57bfc2ff-df64-40fc-9cd4a15cb489bab8:353894462954:138805248300075:1376256151365:6553675414:65536174015:0273455:024 1435:65536261685. If the object is not a transformation or task. ObjectExport exports all the referenced objects to an XML file called exported_del_file. It includes the database definition as a prefix.none. suppose you want to export all logically deleted objects from the repository. For information on valid transformations and task types see Table 16-16 on page 426. and the record does not require the reusable argument.

g.Version 7. you must create an XML file defined by impcntl. normalizer and XML DSQ current values in the destination --> <!--COPY_SAP_PROGRAM Copy SAP program information into the target repository --> <!--APPLY_DEFAULT_CONNECTION Apply the default connection when a connection used by a session does not exist in the target repository --> <!ELEMENT IMPORTPARAMS (FOLDERMAP*.1 --> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> <!--RETAIN_GENERATED_VALUE Retain existing sequence generator. you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard.dtd. This should comforming to the element name in powermart. The following is a sample of the impcntl. The import control file installs with the PowerCenter Client. but you must include its location in the input XML file. SOURCE. e. TARGET and etc. RESOLVECONFLICT?)> <!ATTLIST IMPORTPARAMS CHECKIN_AFTER_IMPORT CHECKIN_COMMENTS APPLY_LABEL_NAME RETAIN_GENERATED_VALUE COPY_SAP_PROGRAM APPLY_DEFAULT_CONNECTION > (YES | NO) "NO" CDATA CDATA #IMPLIED #IMPLIED (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <!ELEMENT FOLDERMAP EMPTY> <!ATTLIST FOLDERMAP SOURCEFOLDERNAME CDATA #REQUIRED #REQUIRED #REQUIRED #REQUIRED SOURCEREPOSITORYNAME CDATA TARGETFOLDERNAME CDATA TARGETREPOSITORYNAME CDATA > <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import.dtd file: <!-.--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files .dtd. TYPEFILTER*.Informatica Object Import Control DTD Grammar .Using the Object Import Control File When you use the pmrep ObjectImport command. To create a control file.

The combination of specified child nodes can be supplied --> <!ELEMENT RESOLVECONFLICT (LABELOBJECT | QUERYOBJECT | TYPEOBJECT | SPECIFICOBJECT)*> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <!ELEMENT LABELOBJECT EMPTY> <!ATTLIST LABELOBJECT LABELNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <!ELEMENT QUERYOBJECT EMPTY> <!ATTLIST QUERYOBJECT QUERYNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <!ELEMENT TYPEOBJECT EMPTY> <!ATTLIST TYPEOBJECT OBJECTTYPENAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--SPECIFICOBJECT allows a particular object(name. typename etc.required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <!ELEMENT SPECIFICOBJECT EMPTY> <!ATTLIST SPECIFICOBJECT NAME DBDNAME CDATA CDATA #REQUIRED #IMPLIED #REQUIRED #REQUIRED #REQUIRED #REQUIRED> OBJECTTYPENAME CDATA FOLDERNAME CDATA REPOSITORYNAME CDATA RESOLUTION (REPLACE | REUSE | RENAME) Using the Object Import Control File 497 .) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import.

Reuse. Object Import Control File Elements and Attributes (pmrep) Element IMPORTPARAMS Attribute Name CHECKIN_AFTER_IMPORT CHECKIN_COMMENTS APPLY_LABEL_NAME RETAIN_GENERATED_VALUE Attribute Description Checks in objects when they successfully import. Retains existing Sequence Generator. or Rename. Copies SAP program information into the target repository. and XML Source Qualifier transformation current values in the destination. or mappings. Replace. Rename. Specifies the import folder name to match to a folder in the target repository. targets. Applies the default connection when a connection used by a session does not exist in the target repository. The default connection is the first connection from the sorted list of available connections. Reuse. for conflict resolution specification. Replace.Object Import Control File Parameters Table A-1 lists pmrep Object Import control file parameters: Table A-1. Specifies the repository containing the source folder. Replace. Imports just the objects from a specific node. Identifies objects by label name for conflict resolution specification. Identifies objects from this query result for conflict resolution specification. Allows you to specify conflict resolutions for objects. Applies the label name on the imported objects. Find the list of connections in the Workflow Manager. Identifies objects by type. Specifies the target folder name for matching. such as sources. Normalizer. Specifies the repository containing the target folder. or Rename. Object type for this conflict resolution. COPY_SAP_PROGRAM APPLY_DEFAULT_CONNECTION FOLDERMAP SOURCEFOLDERNAME SOURCEREPOSITORYNAME TARGETFOLDERNAME TARGETREPOSITORYNAME TYPEFILTER RESOLVECONFLICT LABELOBJECT TYPENAME (see the following elements) LABELNAME RESOLUTION QUERYOBJECT QUERYNAME RESOLUTION TYPEOBJECT OBJECTTYPENAME RESOLUTION SPECIFICOBJECT NAME DBDNAME OBJECTTYPENAME 498 Appendix A: Working with pmrep Files . Source DBD name to identify source object. Applies the comments to the checked in objects. Reuse. Specific object name for this conflict resolution.

Replace.Table A-1. Reuse. The repository containing the object. Object Import Control File Elements and Attributes (pmrep) Element Attribute Name FOLDERNAME REPOSITORYNAME RESOLUTION Attribute Description The folder the containing object. Using the Object Import Control File 499 . or Rename.

It lists what types of objects to import and shows several methods that you can use to resolve conflicts. you want to replace all the duplicate objects labeled “Monthend. It specifies to check in the imported objects and label them.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. you want to rename conflicting source objects that contain “Yr_End” in the object name. including specifying a resolution for query results. The file specifies the target folder and repository. You have a query called “yr_end_qry” that finds these objects. In the target folder.dtd"> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> 500 Appendix A: Working with pmrep Files . and specifying resolutions for specific objects.” However. specifying resolutions for object types.0" encoding="UTF-8"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl.dtd"> <IMPORTPARAMS CHECKIN_AFTER_IMPORT ="NO"> <FOLDERMAP SOURCEFOLDERNAME ="OLD_ACCOUNTING" SOURCEREPOSITORYNAME ="OLD_REPOS" TARGETFOLDERNAME ="NEW_ACCOUNTING" TARGETREPOSITORYNAME ="NEW_REPOS"/> <TYPEFILTER TYPENAME ="SOURCE"/> <RESOLVECONFLICT> <LABELOBJECT LABELNAME ="Monthend" RESOLUTION = "REPLACE"/> <QUERYOBJECT QUERYNAME ="yr_end_qry" RESOLUTION ="RENAME"/> </RESOLVECONFLICT> </IMPORTPARAMS> Sample Import XML File The following is a sample XML control file for ObjectImport. You might create a control file with the following attributes: <?xml version="1. <?xml version="1.Example Suppose you want to import only source objects.

--> <TYPEFILTER TYPENAME="SOURCE"/> <TYPEFILTER TYPENAME="TARGET"/> <TYPEFILTER TYPENAME="MAPPLET"/> <TYPEFILTER TYPENAME="MAPPING"/> <TYPEFILTER TYPENAME="TRANSFORMATION"/> <TYPEFILTER TYPENAME="SHORTCUT"/> <TYPEFILTER TYPENAME="CONFIG"/> <TYPEFILTER TYPENAME="TASK"/> <TYPEFILTER TYPENAME="SESSION"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKFLOW"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKLET"/> <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. The combination of specified child nodes can be supplied --> <RESOLVECONFLICT> <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <QUERYOBJECT QUERYNAME="Q_MAPS_CREATED_1027" RESOLUTION="RENAME"/> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <LABELOBJECT LABELNAME="LABEL_DT1027" RESOLUTION="REPLACE"/> <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <TYPEOBJECT OBJECTTYPENAME="WORKFLOW" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="WORKLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="SESSION" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPING" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="Source definition" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Target definition" RESOLUTION="REUSE"/> Using the Object Import Control File 501 . e.g.<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_PARENT_TYPOBJ_REPLACE_CHILDREUSE" APPLY_LABEL_NAME="LABEL_IMPORT_PARENT_REPLACE_CHILDREUSE_ALL"> <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <FOLDERMAP SOURCEFOLDERNAME="PMREP_CHECKED_OUT" SOURCEREPOSITORYNAME="PMREP_AUTOMATION_1027" TARGETFOLDERNAME="PMREP_CHECKED_OUT_IMPORT" TARGETREPOSITORYNAME="PMREP_AUTOMATION_1027"/> <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import. TARGET and etc. SOURCE. This should conforming to the element name in powermart.dtd.

required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="ADDRESS1" DBDNAME="sol805" OBJECTTYPENAME="Target Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="MAP_MLET_ADD1" OBJECTTYPENAME="Mapplet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="MAP_ADD1" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="R_AGG1" OBJECTTYPENAME="Aggregator" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_CUSTOM11_M" OBJECTTYPENAME="Custom Transformation" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_EXP11_M" OBJECTTYPENAME="Expression" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_FIL11_M" OBJECTTYPENAME="Filter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> 502 Appendix A: Working with pmrep Files .) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .<TYPEOBJECT OBJECTTYPENAME="Expression" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Filter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Aggregator" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Rank" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Normalizer" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Router" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sequence" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sorter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="update strategy" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Custom Transformation" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Lookup Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Transaction control" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Stored Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="External Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Joiner" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Email" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Command" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Scheduler" RESOLUTION="REUSE"/> <!--SPECIFICOBJECT allows a particular object(name. typename etc.

<SPECIFICOBJECT NAME="R_LKP1_M" OBJECTTYPENAME="Lookup Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_JOIN1_M" OBJECTTYPENAME="Joiner" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RANK1_M" OBJECTTYPENAME="Rank" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RANK1_M" OBJECTTYPENAME="Rank" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RTR1_M" OBJECTTYPENAME="Router" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_SEQ1_M" OBJECTTYPENAME="Sequence" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_SORT1_M" OBJECTTYPENAME="Sorter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_TC1_M" OBJECTTYPENAME="Transaction control" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_UPD11_M" OBJECTTYPENAME="update strategy" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_CREATEINDEX1_M" OBJECTTYPENAME="Stored Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_DROPINDEX1_M" OBJECTTYPENAME="Stored Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_External_M" OBJECTTYPENAME="External Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="default_session_config" OBJECTTYPENAME="SessionConfig" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="Config1" OBJECTTYPENAME="SessionConfig" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Sched1" OBJECTTYPENAME="Scheduler" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Command" OBJECTTYPENAME="Command" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Email" OBJECTTYPENAME="Email" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="s_M_FLAT" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="s_M_FLAT1" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WLET1" OBJECTTYPENAME="Worklet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WLET_CYCLE" OBJECTTYPENAME="Worklet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WF_ALL_REUSE_OBJS" OBJECTTYPENAME="Workflow" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WF_NESTED" OBJECTTYPENAME="Workflow" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> </RESOLVECONFLICT> </IMPORTPARAMS> Using the Object Import Control File 503 .

<!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?. To use pmrep deployment commands you must create an XML file that works with depcntl. but you should include its location in the input XML file. you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard. DEPLOYGROUP?)> <!ATTLIST DEPLOYPARAMS DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS CDATA #IMPLIED (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "YES"> <!--criteria specific to deploying folders--> <!ELEMENT DEPLOYFOLDER (REPLACEFOLDER?. The following is a sample of the depcntl. The deployment control file installs with the PowerCenter Client.dtd file.dtd. OVERRIDEFOLDER*)> <!ATTLIST DEPLOYFOLDER NEWFOLDERNAME CDATA #IMPLIED> <!--criteria for replacing a target folder--> <!ELEMENT REPLACEFOLDER EMPTY> <!ATTLIST REPLACEFOLDER FOLDERNAME RETAINMAPVARPERVALS CDATA #REQUIRED (YES | NO) "NO" RETAINWFLOWVARPERVALS (YES | NO) "YES" RETAINWFLOWSESSLOGS MODIFIEDMANUALLY (YES | NO) "NO" (YES | NO) "NO"> <!--shared folder to override--> <!ELEMENT OVERRIDEFOLDER EMPTY> <!ATTLIST OVERRIDEFOLDER SOURCEFOLDERNAME SOURCEFOLDERTYPE TARGETFOLDERNAME TARGETFOLDERTYPE CDATA #REQUIRED (LOCAL | GLOBAL) "LOCAL" CDATA #REQUIRED (LOCAL | GLOBAL) "LOCAL" 504 Appendix A: Working with pmrep Files .Using the Deployment Control File When you use DeployDeploymentGroup or DeployFolder pmrep commands.

Creates a new folder with this name. Copies mapping variable persistent values. Does not allow replacing of manually modified target folders. Deployment Control File Elements and Attributes (pmrep) Element DEPLOYPARMS Attribute Name DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS DEPLOYFOLDER REPLACEFOLDER NEWFOLDERNAME FOLDERNAME RETAINMAPVARPERVALS RETAINFLOWVARPERVALS RETAINWFLOWSESSLOGS MODIFIEDMANUALLY OVERRIDEFOLDER SOURCEFOLDERNAME SOURCEFOLDERTYPE Attribute Description Specifies the PowerCenter Server in the target repository to run workflows. Specifies the current folder that shortcuts point to. Retains workflow session logs in the target. Retains workflow variable persistent values. Name the folder after replacing it.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Copies dependency information for objects in mappings. Copies only the latest version. Indicates local or global folder. Keeps the current value for Sequence Generator or Normalizer transformations. Using the Deployment Control File 505 . Copies workflow logs. Copies SAP R/3 installed ABAP program. Copies workflow variable persistent values. Retains mapping variable persistent values in the target. Retains server network related values in tasks. APPLYLABEL?)> <!ATTLIST DEPLOYGROUP CLEARSRCDEPLOYGROUP (YES | NO) "NO"> <!--labels used to apply on the src objects and deployed objects--> <!ELEMENT APPLYLABEL EMPTY> <!ATTLIST APPLYLABEL SOURCELABELNAME SOURCEMOVELABEL TARGETLABELNAME TARGETMOVELABEL CDATA (YES | NO) CDATA YES | NO) #IMPLIED "NO" #IMPLIED "NO"> Deployment Control File Parameters Table A-2 lists pmrep deployment control file parameters: Table A-2.

and you need to point the shortcuts from the sc_folder to the new_sc_folder. you can choose to move the label to the selected version of the object.” You might create a control file with following attributes: <?xml version="1. You need to retain the current values in a Sequence Generator transformation.Table A-2. After you copy the folder. Deployment Control File Elements and Attributes (pmrep) Element Attribute Name TARGETFOLDERNAME TARGETFOLDERTYPE DEPLOYGROUP APPLYLABEL CLEARSRCDEPLOYGROUP SOURCELABELNAME SOURCEMOVELABEL Attribute Description Changes folder that shortcuts point to.0" encoding="ISO-8859-1"?> <!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl.dtd"> <DEPLOYPARAMS DEFAULTSERVERNAME ="info7261" COPYPROGRAMINFO ="NO" COPYWFLOWVARPERVALS ="NO" COPYWFLOWSESSLOGS ="NO" COPYDEPENDENCY ="YES" LATESTVERSIONONLY = "NO"> <REPLACEFOLDER FOLDERNAME ="NEW_YEAR" RETAINVARPERVALS ="YES"/> <OVERRIDEFOLDER SOURCEFOLDERNAME ="SC_FOLDER" OVERRIDEFOLDERNAME ="NEW_SC_FOLDER"/> </DEPLOYPARAMS> 506 Appendix A: Working with pmrep Files . If the Repository Agent detects the label is applied to another version of the same object. Moves the label from a different version of the object in the source group to the deployment group version of the object. you want to rename it to “new_year. If the Repository Agent detects the label is applied to another version of the same object. you can choose to move the label to the latest version of the object. Moves the label from a different version of the object in the target group to the deployment group version of the object. Removes objects from source group after deploying. TARGETLABELNAME TARGETMOVELABEL Example Suppose you want to deploy the latest version of a folder and include all dependencies. Applies a label to all the objects in the source group. Indicates local or global folder. Applies a label to all the objects deployed to the target repository.

connects to and backs up a repository called Production on a server named Central: backupproduction. the following Windows batch file. Tip: When you create script files using pmrep commands. Return code (0) indicates that the command succeeded. In this case. For instance. Return code (-1) indicates the command failed.. Scripting pmrep and pmrepagent Commands 507 . c:\PowerCenter\pmrep\pmrep connect -r Production -n Administrator -x Adminpwd -t “microsoft sql server” -u sbrown -p sbrownx -c Central@Production echo Backing up repository Production. you might use pmrep to perform a daily backup of a production repository.rep You can run script files from the command interface..Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. For example. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup. backupproduction.bat REM This batch file uses pmrep to connect to and back up the repository Production on the server Central @echo off echo Connecting to repository Production. You cannot run pmrep batch files while in pmrep interactive mode... pmrep and pmrepagent indicate the success or failure of a command with a return code.bat. Informatica recommends that you include a connect command as the first command called by the script file. This helps ensure you are performing tasks on the correct repository. you can create a script file to call one or more pmrep commands including options and arguments. you might use commands with specific options and arguments on a regular basis.

508 Appendix A: Working with pmrep Files .

511 Workflow Monitor Tasks. 520 509 . 519 pmrepagent Tasks.Appendix B Permissions and Privileges by Task This appendix summarizes the available tasks in the PowerCenter Client tools. 515 Repository Manager Tasks. 513 pmcmd Tasks. 516 pmrep Tasks. It then lists the repository privileges and folder permissions required to perform each task in these tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Designer Tasks. 510 Workflow Manager Tasks.

Read and write permission for the destination folder. you can edit a mapping if you have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with both read and write permission on the folder Super User privilege Table B-1 lists the required privileges and permissions for Designer tasks: Table B-1. For example. transformations. and mappings Create shortcuts from a shared folder Repository Privilege Use Designer Use Designer Use Designer Use Designer Folder Permission None required Read Read/Write Read permission in the shared folder. transformations. Read permission in the originating folder. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. targets. Read/Write Read Read Read/Write Read Read/Execute Read Copy object from one folder to another Copy and paste objects in mappings or mapplets in the same folder Compare objects Export objects Import objects Edit breakpoints Create a debug session Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer and Use Workflow Manager Use Designer and Workflow Operator 510 Appendix B: Permissions and Privileges by Task . Read and write permission in the destination folder. you must have one of the listed sets of privileges and permissions. and mappings Create/edit sources.Designer Tasks To perform the following Designer tasks. targets.

Execute None required Execute Execute Workflow Manager Task Connect to the repository using the Workflow Manager Create workflows and tasks Edit workflows and tasks Create and edit sessions Delete Connection Folder Permission None required Read/Write Read/Write Read/Write None required None required None required Schedule or unschedule workflows Use Workflow Manager Workflow Operator Read/Execute Read Read/Execute Read Start workflows immediately Use Workflow Manager Workflow Operator Workflow Manager Tasks 511 . you must also have read permission for connection objects associated with the session. Write permission and belong to the same group as the owner of the connection object. if you enabled enhanced security.Workflow Manager Tasks To perform the following Workflow Manager tasks. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. you must have one of the listed sets of privileges and permissions. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Administer Repository Use Workflow Manager Use Workflow Manager Connection Object Permission None required None required None required Read Write Write permission and own the connection object. For example. you can edit a session if you have one of the following sets of permissions and privileges: ♦ ♦ Use Workflow Manager privilege with both read and write permission on the folder Super User privilege Note: In addition.

and external loader connections in the Workflow Manager Manage connection object permissions Register PowerCenter Servers and configure server variable directories Export objects Import objects Validate workflows and tasks Run Workflow Monitor None required None required None required Read. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . FTP. and external loader connections in the Workflow Manager Edit database.Table B-2. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager and Administer Server Use Workflow Manager Use Workflow Manager Administer Repository Administer Server Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Connection Object Permission None required Workflow Manager Task Stop the PowerCenter Server Folder Permission None required Configure database. FTP.

Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task Connect to repository Repository Privilege Use Workflow Manager or Workflow Operator Workflow Operator Use Workflow Manager View the session log Workflow Operator Use Workflow Manager Restart workflow Workflow Operator Use Workflow Manager Stop workflow Workflow Operator Use Workflow Manager Abort workflow Workflow Operator Use Workflow Manager Resume workflow Workflow Operator Use Workflow Manager Folder Permission None required Connection Object Permission None required Connect to the PowerCenter Server None required None required Read Read/Execute Execute Execute Execute Execute Execute Execute Execute Execute None required None required None required None required None required None required None required None required None required None required None required None required Workflow Monitor Tasks 513 . you can restart a workflow if you have one of the following sets of permissions and privileges: ♦ ♦ ♦ Workflow Operator privilege with execute permission for the folder containing the workflow. For example. Super User privilege Table B-3 lists the required privileges and permissions for Workflow Monitor tasks: Table B-3. Use Workflow Manager privilege with read and execute permissions for the folder containing the workflow. you must have one of the listed sets of privileges and permissions.Workflow Monitor Tasks To perform the following Workflow Monitor tasks.

Table B-3. Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task View session details and session performance details Repository Privilege Use Workflow Manager Use Workflow Manager Folder Permission Read Read Connection Object Permission None required None required 514 Appendix B: Permissions and Privileges by Task .

Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4. you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above.pmcmd Tasks To perform the following pmcmd tasks. you must have one of the listed sets of privileges and permissions. For example. Required Privileges and Permissions for pmcmd Tasks pmcmd Task Ping the PowerCenter Server Stop the PowerCenter Server All other tasks Repository Privilege None required Administer Server Use Workflow Manager Workflow Operator Folder Permission None required None required Execute None required Connection Object Permission None required None required Execute Execute pmcmd Tasks 515 . you can start a workflow using pmcmd if you have the following permissions and privileges: ♦ ♦ Workflow Operator privilege Execute permission on the folder Note: If you enabled enhanced security.

you must have one of the listed sets of privileges and permissions. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Add to deployment group Apply label Change object version comments Change status of an object Change your password Check in Check in/undo check out for other users Check out/undo check out Connect to the repository using the Repository Manager Copy a folder to a different repository Repository Privilege Use Repository Manager Use Repository Manager Use Repository Manager or be check-out owner Use Repository Manager Browse Repository Use Repository Manager Administer Repository Use Repository Manager Browse Repository Browse Repository on the originating repository and Administer Repository on the destination repository Administer Repository Folder Permission Read Read Write Write None required Write Write Write None required Read permission on the original folder None required None required None required None required None required None required Read Other Permission Write on deployment group Execute on label Copy a folder within the same repository Read permission on the original folder Read permission on the original folder Read on the original folders Write on target Read Browse Repository None required Copy global object Use Repository Manager 516 Appendix B: Permissions and Privileges by Task . you can edit the properties of a folder if you have one of the following sets of permissions or privileges: ♦ ♦ ♦ Browse Repository privilege. For example. as the folder owner with read permission on the folder Administer Repository privilege with read permission on the folder Super User privilege Table B-5 lists the required permissions and privileges for Repository Manager tasks: Table B-5.Repository Manager Tasks To perform the following Repository Manager tasks.

Folder owner and read permission Read Folder owner and read permission Read Read Folder owner and read permission Read Read/Write None required None required Write Write None required Write N/A N/A Other Permission None required Edit: Write on deployment group Edit: Write on label Write on query None required None required None required Write on deployment group Read and execute on deployment group None required None required None required None required None required None required None required None required None required None required None required None required None required None required None required Read on query Repository Manager Tasks 517 . export. and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder. groups.Table B-5. or remove the registry Manage users. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Create a folder Create or edit deployment group Create or edit label Create or edit query Delete (versioning) Delete a folder Repository Privilege Administer Repository Administer Repository Administer Repository Browse Repository Use Repository Manager Browse Repository Administer Repository Delete from Deployment Group Deploy Edit folder Use Repository Manager Administer Repository Browse Repository Administer Repository Edit folder properties Browse Repository Administer Repository Export objects Freeze folder Use Repository Manager Browse Repository Administer Repository Import objects Import.

Table B-5. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Search target tables by keyword Terminate other users and unlock objects Unlock an object or folder locked by your username Unlock any locked object or folder in the repository View dependencies Repository Privilege Browse Repository Super User Browse Repository Super User Browse Repository Folder Permission Read None required Read None required Read Other Permission None required None required None required None required None required 518 Appendix B: Permissions and Privileges by Task .

For example. you must have one of the listed sets of privileges and permissions.pmrep Tasks To perform the following pmrep tasks. Required Permissions and Privileges for pmrep Tasks pmrep Task List repository objects (Listobjects) List sources or targets in a session (Listtablesbysess) Export objects (ObjectExport) Import objects (ObjectImport) Change the name of an existing connection (Switchconnection) Update email addresses (Updateemailaddr) Update source table owner names (Updatesrcprefix) Update target table name prefixes (Updatetargprefix) Update transformation properties for Sequence Generator transformations (Updateseqgenvals) All other tasks Repository Privilege Browse Repository Use Workflow Manager Use Repository Manager Use Repository Manager Super User Folder Permission Read Read Read Read/Write None required Connection Object Permission None required None required None required None required None required Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Designer Write Write Write Write None required None required None required None required Administer Repository None required None required pmrep Tasks 519 . you can list objects in a repository if you have one of the following permissions or privileges: ♦ ♦ Browse Repository privilege with read permission on the folder Super User privilege Table B-6 lists the required permissions and privileges for pmrep tasks: Table B-6.

The repository user name does not require any folder or connection object permissions. However. 520 Appendix B: Permissions and Privileges by Task .pmrepagent Tasks You do not need any privilege or permission to perform pmrepagent tasks. use one with the Administer Repository privilege. when you must provide a repository user name and password.

Index A activity log Administration Console 56 addprivilege description 450 Addrepository description 414 Addserver description 413 AddToDeploymentGroup description 461 Addusertogroup description 450 Administer Repository privilege limiting 161 Administration Console activity log 56 adding repository configurations 105 backing up repositories 66 closing connections 83 connecting to Repository Server 58 Console Tree 52 copying repositories 62 creating repositories 116 deleting repositories 64 disabling repositories 73 editing repository configurations 113 enabling repositories 71 exporting repository configurations 115 HTML view 53 importing repository configurations 115 List view 53 Main window 53 MMC 52 overview 50 privileges 50 promoting repositories 117 propagating domain information 78 registering local repositories 75 registering repository plug-ins 85 removing repository configurations 114 repositories node 54 repository name node 54 Repository Server name node 54 Repository Servers node 54 restoring repositories 67 sending repository notifications 74 starting 52 starting repositories 71 stopping repositories 71 unregistering repository plug-ins 85 updating licenses 111 using 52 viewing connections 79 advanced mode copying deployment groups 259 copying folders 244 521 .

ApplyLabel description 462 associating server with sessions 245 audit trails 208 configuration setting 110 creating 153 authenticating users description 131 authentication switching methods 133 using LDAP 131 B backing up repositories 66 repositories with pmrep 416 repositories with pmrepagent 477 Backup command pmrep 416 pmrepagent 477 Bulkrestore command description 479 C Changepassword description 450 Checkin description 464 CheckinCommentsRequired repository configuration 110 checking in description 213 non-reusable objects 213 when importing objects 280 checking out description 211 non-reusable objects 211 undoing a checkout 213 checkouts searching for checked out objects 211 viewing 211 Cleanup description 411 ClearDeploymentGroup description 465 code pages See also Installation and Configuration Guide 522 Index exporting objects 266 global repository 117 importing objects 266 local repository 75 repository 51. 45 conflicts copying Designer objects 310 copying workflow segments 308 database connections 307 mapping 307 resolving when importing 281 connect string examples 405 syntax 405 connecting to repositories 30. 31 connection objects See also Workflow Administration Guide definition 10 permissions and privileges 245 connections terminating 83 viewing 79 connectivity connect string examples 405 connectivity license keys overview 119 ConnectString setting for repository configuration 107 Console Tree Administration Console 52 control file deployment 504 object import 496 ObjectImport XML example 500 Copy Wizard copying objects 302 resolving conflicts 300 viewing object dependencies 305 . 192 command line program See pmrep See also pmrepagent comments accessing metadata 335 comparing See also Designer Guide See also Workflow Administration Guide folders 174 Repository objects 45 Workflow Manager objects 21.

copying See also copying deployment groups 254 See also copying folders 248 Copy Wizard procedure 302 deployment groups 254 Designer objects 310 folders 250 in Workflow Manager 306 mapping segments 310 mapping variables 307 mapplet segments 310 repositories 62 resolving conflicts 300 sessions 306 shortcuts 195 workflow segments 308 workflows 306 worklets 306 copying deployment groups copying composite objects 255 copying shortcuts 256 in advanced mode 244 in typical mode 244 steps 258 copying folders from local to global repositories 250 in advanced mode 244 in typical mode 244 shortcuts in folders 249 within a repository 250 CRCVALUE codes overview 267 Create command description 480 CreateConnection description 417 CreateDeploymentGroup description 465 Creategroup description 452 CreateLabel description 466 Createuser description 452 creating global shortcuts 190 local shortcuts 187 metadata extensions 328 MX views 336 repositories 116 repositories using pmrepagent 480 repository users 134 user groups 128 users under an external directory 137 D database connections See also Workflow Administration Guide during folder or deployment group copy 245 permissions and privileges 245 database definitions MX view 338 DatabaseArrayOperationSize configuration setting 110 setting for repository configuration 110 DatabaseConnectionTimeout setting for repository configuration 110 DatabasePoolSize setting for repository configuration 110 DatabaseType setting for repository configuration 107 DateDisplayFormat setting for repository configuration 109 DB2 See IBM DB2 DBPassword setting for repository configuration 107 DBUser setting for repository configuration 107 Decision Support Systems (DSS) working with Informatica metadata 335 default groups security 127 default users editing 131 Delete command description 481 Deleteconnection description 420 DeleteDeploymentGroup description 466 DeleteFolder description 453 DeleteLabel description 467 Deleteserver description 421 deleting folders 173 metadata extensions 332 Index 523 .

recovering deleted objects 215 repositories 64 repositories using pmrepagent 481 user groups 129 versioned objects 215 depcntl.dtd 504 rolling back a deployment 238 deployment groups copying 254.dtd listing 504 dependencies source-target 27 viewing 27. 276 parent objects 271 permissions 266 524 Index . 37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl. 258 copying composite objects 255 copying shortcuts 256 creating 237 definition 218 dynamic 240 editing 237 rolling back a deployment 238 static 239 Designer See also Designer Guide copying objects 310 permissions 510 development license key overview 119 Disablerepository description 421 documentation conventions xxxvii description xxxvi domains building 13 configuring for global shortcuts 192 connectivity 75 reusing data 15 dropping MX views 336 DTD file exporting and importing objects 267 plug-in template 484 dynamic deployment groups associating with a query 240 definition 236 editing 240 DynamicConfigRefreshInterval setting for repository configuration 110 E editing folder permissions 149 folders 173 metadata extensions 331 repository users 138 user 138 user groups 129 Edituser description 454 Enablerepository description 422 enabling a user description 139 environment variables repository username and password 408 Error Severity Level Repository Agent messages 101 Repository Server messages 98 setting for repository configuration 109 exchanging metadata 314 execute lock description (repository) 154 ExecuteQuery description 470 Exit description 411 exiting pmrep 411 exporting metadata 314 registries 32 repository configurations 115 sources and targets 314 exporting objects code pages 266 dependent objects 270 multiple objects 269 overview 264.

192 creating 14 promoting 112. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182.powrmart.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 249 environment 192 repository usernames 193 server username 193 tips 197 updating 194 updating views 194 groups creating user 128 default security 127 editing description 129 F FindCheckout description 472 flat files MX view of repository file definitions 343 view of fields 345 folder permissions description 126 editing 149 overview 148. 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117. 453 deploying 469 Designer uses 166 editing 173 editing permissions 149 locking during folder copy 249 maintaining connections during copy 245 modifying 456 naming copies 249 organizing 166 overview 166 owner and owner’s group 169 H HTML view Administration Console 53 I IBM DB2 connect string example 405 setting tablespace name 107 Import Wizard importing objects 287 resolving object conflicts 281 Index 525 . 171 renaming 173 Repository Manager uses 166 shared 15.

dtd 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart. 466 definition 218 deleting 467 editing 219 launching Administration Console 52 LDAP authentication description 131 LDAP authentication module configuring 92 LDAP security module registering 88 unregistering 95 license files compatibility between files 122 overview 120 PowerCenter Server 122 repository 120 license key types development 119 production 119 license keys connectivity 119 option 119 overview 119 product 119 repository types 119 licenses See also license files 119 See also license keys 119 overview 119 rules and guidelines 123 updating 111 List view Administration Console 53 Listallgroups description 455 Listallprivileges description 455 Listallusers description 455 ListObjectDependencies description 429 Listobjects description 423 listing folders 427 listing transformations 427 transformation types 426 Listtablesbysess description 428 . 462 applying when importing 280 526 Index creating 219.dtd 267 privileges 266 resolving conflicts 281 sessions 272 shortcuts 274 steps for 287 validating objects 281 validating XML file 280 XML file 267 Informatica documentation xxxvi Webzine xxxviii Informix connect string syntax 405 interactive mode pmrep 406 in-use lock description (repository) 154 K KeepAliveTimeout setting for repository configuration 110 keywords searching for target definitions 34 L labels applying 221.importing metadata 314 objects 280 ODBC data sources 33 registries 32 repository configurations 115 sources and target 314 importing objects code pages 266 CRCVALUE codes 267 dependent objects 270 DTD file 267 impcntl.

157 log entries truncating 48 log files codes 97 Repository Agent 100 Repository Server 98 LogFileName setting for repository configuration 110 logs deleting 439 Repository Agent 100 Repository Server 98 M main window Administration Console 53 sorting and organizing 25 mapping segments copying 310 mappings See also Designer Guide conflicts 307 copying mapping variables 307 copying segments 310 dependencies 27 description 9 metadata extensions in 326 view of source fields 359 view of source fields used by targets 358 view of sources 359 view of target tables 360 mapplet segments copying 310 mapplets See also Designer Guide description 9 metadata extensions in 326 MaximumConnections setting for repository configuration 109 MaximumLocks setting for repository configuration 110 MessageReceiveTimeOut setting for repository configuration 108 MessageSendTimeout setting for repository configuration 108 metadata adding to repository 9 analyzing 335 definition 2 exchanging 314 exporting 314 importing 314 multi-dimensional 9 protection levels within folders 168 reusing 14 reusing across folders 182 sharing 14 viewing 334 metadata exchange See MX (Metadata Exchange) metadata extensions copying 246 creating 328 deleting 332 description 326 editing 331 non-reusable 327 overview 326 reusable 327 Microsoft Management Console See MMC Microsoft SQL Server connect string syntax 405 MMC Administration Console 52 Modifyfolder description 456 MQ connections See PowerCenter Connect for IBM MQSeries User and Administrator Guide Index 527 .local repositories See also repositories code page 75. 249 tips 197 updating 194 updating views 194 locking description 126 during deployment group copy 254 during folder copy 249 locks releasing 83 viewing 80. 192 promoting to global 112 registering 75 local shortcuts behavior when copying folders 249 creating 187 definition 182.

396 folder view 401 integrating views with third-party software 337 label views 398 mapping views 353 mapplet views 353 metadata extension views 364 overview 334 PowerCenter Server views 396 repository view 395 security views 390 source views 339 target views 347 task views 371 transformation views 366 workflow views 371 worklet views 371 MX views categories 334 creating 336 dropping 336 field-level summary 338 integrating with third-party software 337 REP_ALL_MAPPINGS 354 REP_ALL_MAPPLETS 355 REP_ALL_SCHEDULERS 374 REP_ALL_SOURCE_FLDS 341 REP_ALL_SOURCES 339 REP_ALL_TARGET_FIELDS 349 REP_ALL_TARGETS 347 REP_ALL_TASKS 374 REP_ALL_TRANSFORMS 366 REP_CM_LABEL 399 REP_CM_LABEL_REF 399 REP_COMPONENT 384 REP_DATABASE_DEFS 338 REP_DEPLOY_GROUP 392 REP_DEPLOY_GROUP_DETAIL 393 REP_EVENT 376 REP_FLD_MAPPING 358 REP_GROUPS 391 REP_LOAD_SESSIONS 380 REP_MAPPING_PORT_CONN 363 REP_MAPPING_UNCONN_PORTS 362 REP_METADATA_EXTN_DEFINES 365 REP_METADATA_EXTNS 364 REP_REPOSIT_INFO 395 REP_SEG_FLDS 345 REP_SERVER_INFO 396 REP_SERVER_NET 397 REP_SERVER_NET_REF 397 REP_SESS_CONFIG_PARM 385 REP_SESS_LOG 387 REP_SESS_PARTITION_DEP 385 REP_SESS_TBL_LOG 388 REP_SESS_WIDGET_CNXS 383 REP_SESSION_CNXS 381 REP_SESSION_FILES 382 REP_SESSION_INSTANCE_FILES 383 REP_SESSION_INSTANCES 381 REP_SRC_FILE_FLDS 345 REP_SRC_FILES 343 REP_SRC_FLD_MAP 359 REP_SRC_MAPPING 359 REP_SRC_TBL_FLDS 346 REP_SRC_TBLS 344 REP_SUBJECT 401 REP_TARG_FLD_MAP 357 REP_TARG_MAPPING 356 REP_TARG_TBL_COLS 351 REP_TARG_TBL_JOINS 361 REP_TARG_TBLS 350 REP_TASK_ATTR 386 REP_TASK_INST 377 REP_TASK_INST_RUN 378 REP_TBL_MAPPING 360 REP_USER_GROUPS 391 REP_USERS 390 REP_VERSION_PROPS 398 REP_WFLOW_RUN 379 REP_WFLOW_VAR 375 REP_WIDGET_ATTR 369 REP_WIDGET_DEP 368 REP_WIDGET_FIELD 369 REP_WIDGET_INST 368 REP_WORKFLOW_DEP 377 REP_WORKFLOWS 372 SQL scripts 336 N naming copied folders 249 replaced folders 249 native connect string See connect string Navigator Administration Console 52 528 Index .MX (Metadata Exchange) Change Management views 398 database definition views 338 deployment views 392.

433 modifying in XML file 277 validating for import 281 validating multiple 42 viewing dependencies 37 ODBC data sources See also Installation and Configuration Guide importing 33 option license keys overview 119 Oracle connect string syntax 405 Output window Repository Manager 28 Owner security level description (folder) 148 Index 529 . 432 importing 280.Repository Manager 23 notifications receiving in Designer 6 receiving in Repository Manager 6 sending 74 notify description 431 Owner’s Group security level description (folder) 148 P