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

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

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

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

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

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

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

xvi Table of Contents .

. . . . . 2-9. . . . . . . . . . .. . . . . . .. . . . .. . .. . . . . .. . . . . . .. . . 24 . . .. Apply Label Wizard . . . . . . . . . . .. . . . .. . . .. .. .. . 9-8. . .. . .. . . . . . . . . . . . .. . . . . . ... . . . Object Properties . .. 9-5. .. .. . . . . . ... .. . . ... . . .. . . . 2-7. . . . . . . 27 . . . .. . . . . . CRCVALUE Code in an Exported XML File . . .. . . . . . . . . . ... . .. . . . . .. . . . . . .. . . . . . . . . . Deployment Group Editor .. . . Query with Multiple Conditions . .. . . . Query Browser . . . . . . . . . . . . .. . . . . . . . . . . 9-11. . 2-8. . . .. . . . 7-2. . . . ... .. . . . . . . . 7-4. . . . . . . . . . . . .. . . . . ... . 4 .. . . . . . . . 9-9. . . .. . . . . . . . . . . .. . .. . .. . . . . . 2-6. .. . . . . . . .. .. .. . . . . . . .. .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. .. . . . . .. . . . . . . . . ... . . . . . . ... .. . . . Administration Console . . .. 7-3.. . . . . . . . . . . . .. . . .. . . . . . . . . . . . .. . . . . . .. . .. . . . . One-Way and Two-Way Comparisons .. . . .... . . . . .. . . . .. . . ... .. . . .. . . . . . Repository Details . .. . . . . 2-2. . .. . . . . . . . . . .. . . .. . . . . . . 9-2.. . . .. . Deployment Group Browser . . . . . ... . . . . . . . .. .. .. . . . . . 9-4. ... . . . . . . . . . . Dependency Window . .. . . . . . 25 ... . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . 8-1. . . . Dependency for Deployment Group Dialog Box . . . . . . .. .. . . . . . ... . . Event Viewer Application Log Message . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . . . .. . . . . . . . .. . . . . . .... . . .. . . . . . . Output Window .. . .. . . .. . . . . . .. .. .. .. . . . . . . . . . . . .. 43 . . . . . . . . . . .. . . . . . . . Object and Shortcut Description . .. . . . . . . . . . . . . ... . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . .. . . 55 . . . . . . . . 9-12. 8-3. . . . . . . .. . . . .. .. . . . . . . . . . . . . . .. . . 8-5. 9-6. . .... . .. . . . . . . .. . . . . . .. . . . ... . .. 9-1. . . . . . . . . . . . . . ... . . . . .. 52 . . . Apply Label Dialog Box . . . . 2-5. .. .. .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . Deployment Group History . . . . . . . . . . . . . . . . . . . . View Dependencies Window . . .. . . . . . . . . . . Sample Query Results . . . . . ... .. . . . .. . .. . 2-3.. Validate Objects Results . . . . . .. . . . . . . . . . . . .. . 8-4. . . . . .. . . . . . .. . Dependencies Dialog Box . . . . Source Definition Object Properties . . . . . . . .. .. .. . .. . . .. . . . . . .. . . . . . .. . . . .. . . . . . . . . . . Application Log Message Detail . . . . . . . . . . . . . . . . . . . .. . . . . . 2-1. . . . 11-1. . 9-3. . .. . . . . . . .. . . .. . . .. . . 3-5. . . . . . . . . . . . . ... . . . . . . . . ... . .. . . . . . .. . .. . . . . ... . . . . Query Editor . . . . . . . .. . Transformation Shortcut Icon . . .. . .. Activity Log Window . . . 3-4. . . PowerCenter Repository Connectivity . . . . ... .. . . . . . . . . . Repository Manager Components . . .. .. 40 . . . . . .. . . . 41 . .. . . . . . . . . . . .. . ... Label Editor Options . . . . . . 2-4. . Repository Manager Navigator . . 5-1. . . . . . . . . . . . . .. . . . . . . . . . ... . . . . . . Repository User Names and External Login Names 6-1. .. .. Object Dependencies Saved as HTML . .... . . . . .. . . . . . . . . . . ... . . . . . . .. . . . . . . ... . . . Referenced Shortcut Object . . . . . . . . . . .. . . .. . . . Label Browser . . . . .. 8-6. . . . 39 . . . ... . . . . .. . .. . . . . . . . . . Results View Windows List . ... 8-2. . . . . . .. Object Status Properties . . . 9-7. . . . ... . . . Labels Properties . . . . .. . . . .. . . . . . . . .. . . . .. . . View History Window . . . .. . 3-1. . .. . . . . . . .. . . . . . . . . . . .. . . . .. . . . 22 . . . . . ... . . . .. . . . . . . . . . . . . . . . . . 28 . 3-2. . . . . . . . . .. 3-3. Version Properties . . .. . . . . . . . .. . . . . . . . .. . 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 . . . . . . 7-1. . . . . Create a Global Shortcut . . . . . . .. . . . . . . .. . . . .. .. . ... . . . . 9-10. . . . . . . . . . . .. . . .. ..

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

. . . . HTML Links for Performing Repository Tasks . . . . . . .. . . . . . . . . . . . 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . 5-5. . . New Repository . . . . . . 3-8. . . . . . .. .. . . . . .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. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . 94 . . . . . . . . .. . . . . . . . . . . 5-4. . . Object Details Displayed in Repository Main Window . . .. . . . . . New Repository . .. . . . Default Repository Privileges . . . 4-2. . . . . . 5-6. Repository Connection Properties .. . . . .. . . Repository Locks . . . . . . . .. .. . . . . . . . . . . .. 55 . Viewing Object Dependencies . . . . . . . . 6-1. . . . . . . . . . . . 3-11. . . . . . . . . .. . . 3-5. . . . . . . . . . .. . . . . . . . . . 3-6. . . . . . . . . . . . . . . . . . . . .. . . . . . . 5-1. . . . 2-4. . . . . .. . . . . . . Register Security Module Options. . . . . . . . . . 6-3. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .Configuration Tab . . . . . . . .Database Connection Tab . . . . . . . . . . . . . . . . . . . . . . 5-2. . . . . 26 . . . . . . . . . . . 2-3. . . . . . . . . Converting Special Characters in Repository License File Names . 3-3. . . . . . . . . Query Parameters and Values . .. . . . .. . . . . .. ... . . . . . . . . . . . 39 . . . . . . . . . .. . 8-1. . . LDAP Login Properties Options . . . . . . .. . . 4-3. . . . . . . . . . . . . . . . . . . . . . Repository Details . . . . . . . . . . . . . . . 3-4. . . . LDAP Login Properties Options . . . . . . . 5-7. . . . . . . . .. . . . . . . . .. . . . . 6-2. . . . . . . . . . .. . . . . . . . . . . 37 . . . . . . . . . . . 4-5. . . . . . . . . . . . . . . . . . . . 4-1. . .. . . . . . . . . . . . . . . ... . . . . . .. . . . . . .. . . . . . Folder Permissions . . . . 54 . . . . .. . . . . . . . . . . . . . . . .. . . . . Object Lock Properties . . . . . . . . . . . . . . . . . . . . . . 3-2. . . . . . . . . . . . . License File Compatibility Requirements . . . . ... . . 10-1. . Copy Folder Wizard Prompts (Copying a Folder) . . . .. . . . . . . . . Tasks Available in View Checkouts Window . . . . . . . . . New Repository . . . . . . . . . . . . . Object Lock Properties . . . . . . . . . . . . . . . . . . . . . 7-1. . . . . . . .. . . . . . . 3-9. . . . . . Folder Object Security Levels . . . ... . .. . . . . . . 5-3. . . . . . . . . . . . . . . . . . . . Compared Object Types and Attributes . . . . .. . .. . . . . . . . . . .. . . . . . . . Label Options and Description . .. . . . . . .. . . . . . . . 3-10.. . . . . . . . . . . . . . . . 2-5. Extended Repository Privileges . . . . . . . . . . . .. . . . . . . . 40 . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 8-2. . . . . . . . . . . . 4-6. . . . . . . . . . . . . . . . . .. . . . . . . . . . . 9-2. . .. . . . . . . . . . . . .General Tab . . . . . . .. . . . . . . . . . .. . . . . . . . Repositories Node Details . . . .. . . . . . . . . . . Tasks Available in Query Results Window . . . . . . . 54 . . . . . . . . . . . . . Validate Objects Properties. . . Compared Objects in Compare . . . . . . . . . . . .. . . . 3-1. . . . . . . . . . . .. . . . . 10-2. . . . . . . .. . . . . .. .. . . . . . . . . . . . . . . . . . 96 . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . LDAP Server Configuration Options . . . . . . . Dependencies Options . .Network Tab . . . . . 43 . . 2-2. .. . . . . 4-4. . . . 91 . . . . . . .. 9-1. .. . . . . 55 .. . Change In Object Status After Copying Deployment Group Objects .. . . . . . . . . . . .. . . . . . . Repository Log Codes . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . Versioning Object Security Levels . . . . . 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 . Repository User Connection Details . . .. . . . . . . . . . . .. . 9-3. . . . . 3-7. . . . . . . . . . . . . . . . . . Object Properties for View Dependencies Window . . . . . . . . Copying Global or Local Shortcuts .. . . . . . . . . . . 79 .. . .. . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . 93 . . . . Tasks Available in View History Window . . . . . . ... Repository Servers Node Details . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . New Repository . . . . . . . . . . . . . . . . . . . . . . . .

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

REP_DEPLOY_GROUP_DETAIL MX View . . .. . . . . . Security Views . . . . . . . . ... . and Task Views . . .. 15-54. . . . . . .. . . .. ... . .. . . . .. . . . . . . . . . .. .... .. . . . ... . . . . . .. . . . .. . 15-71. .. . . 15-66. REP_SESS_CONFIG_PARM MX View . . . . REP_LOAD_SESSIONS MX View . ... REP_WORKFLOWS MX View .. REP_USERS MX View .. . . . . . . .. . . . . ... ... . . . .. . . . REP_SERVER_INFO MX View . 15-75. . ... . .. REP_WFLOW_VAR MX View . .. . . . . .. . 15-50. . . . . . . 15-69. . .. . . . .. .. REP_WFLOW_RUN MX View . .. . . . . . . . . .. . . . . . . .. . REP_USER_GROUPS MX View .. . . . .. . . . ... . .. . . . . . .. . ... REP_REPOSIT_INFO MX View .. 15-64. . . . . . . . . . . . . . . .. . .. . .. . . . .. . . REP_SERVER_NET_REF MX View.. .. ... . . .. . ... 15-48. . . . . . . . . . . . . . . . . . . . . 15-34. . . . . . . 15-61. 15-60. . . . ... . . . . . . . .. . REP_WIDGET_FIELD MX View . . . .. .. . . . . . . . . . .. .. . .. . . . .. . . . . . . .. . 15-38. . . .. . .. .. . . . REP_SESSION_FILES MX View . . . .. . . . 15-62. .. . . . REP_CM_LABEL_REF MX View . . . .. . . 15-47. .. . . . . .. . . . . .. . . . .. .. .. . . 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 . . .. . . . . . .. . . . . PowerCenter Server Views . .. . . . . . . 15-68. 15-74. . ... . . . . . . . . .. . . .... .. . . . . . 15-63. . . .. . . . Workflow. . REP_ALL_SCHEDULERS MX View . . . . . . . .. . . .. .. .. .. . .. .. . . . .. .. . . . .. . . . . . . . . .. . . . . . . . . . . . . REP_SESS_LOG MX View . . .. . . ... .. . . .. . . . . . 15-56. . . . . . . . . REP_SESSION_CNXS MX View . . .. . . . . . . . . . . . . . . .. . .. . . REP_COMPONENT MX View .. . . 15-53. ... . .. . . REP_TASK_INST MX View . .. . . .. . . . .. . . . .. .. . . . . . .. . . . . .. .. 15-52. . . . .. ... . . . . .. . .. . .. . . .. . . . . . . .. . . REP_WORKFLOW_DEP MX View . . . . . . 15-57. . . . .. . . . . . .. . .. Change Management Views .. . REP_ALL_TASKS MX View . . . . . . . . . . . .. . 15-51.. . . . . . . .. . . . . REP_SESS_PARTITION_DEF MX View . . . .... . . . . . 15-70. .. . . . . . . . 15-44. . . . . .. . . Worklet. REP_EIDGET_ATTR MX View . . . . . . . .. . . .. . . . REP_WIDGET_DEP MX View . . . ... . . . .. 15-59.. . . . . 15-35.. . .. . REP_GROUPS MX View .. .. 15-55. 15-73. . . . . . . . .. .. .. . . . . .. .. . . .. . . . 15-42. .. . . . . . . . . . . . REP_TASK_INST_RUN MX View . . . . . .. . . . . . . . . . . . . . . . . .... . REP_EVENT MX View . . . . . . .. . . . . . REP_CM_LABEL MX View . . . ..... . . . . . . .. 15-43. . .. . . . . .. .. . . . . . . . . REP_SESS_TBL_LOG MX View . . . . . .. . . . . ... . . . . .. .. . .. . . .. . . REP_SESSION_INSTANCE_FILES MX View REP_SESS_WIDGET_CNXS MX View . . . . . . .. . . .. . .. .. .. . . . . .. .. ... .. .. .. . . . .. . . .. . . . . . ... . . . . .. . 15-37. .. . . . .. . ... . . .. . . . . . . . . . . . . . .. .. .. .. . . . . . REP_TASK_ATTR MX View .. .. . .. . . . REP_DEPLOY_GROUP MX View . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . ... . . .. . . . . . . . . 15-58. . . . 15-41. . . . .. . ... . . .. . .. . . ..... . . .. . .. 15-72. . ... . . ... . .. . .. . . ..... . 15-36. . . . . . . .. . .. . . . . . .. . . . ... . . . . .... . . . . . . . . . 15-49. . . . . . . . . . . . REP_SERVER_NET MX View . . . . . . . . ... . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 15-46. . Deployment Views . . . . .. . . . . . . . . . . . . 15-65. . . . . . . . . . . . . . . 15-39. . . . . . . . . . . .. . . . . . .. 15-40. .. . .. REP_VERSION_PROPS MX View . . . . .. . . . . . .. . . .. . . .. . . . .. . . . . REP_ALL_TRANSFORMS MX View .. . . 15-67.. . . .. .. . . . ... . . . . .. . . . .. .. . . .. . .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. ... REP_SESSION_INSTANCES MX View . . .. .. . . . . . .. . . .. . . . . . . . . .. . . . . . . .. .. .... . . . . . .. . .. . 15-45. . . . . .. . .. . . . . .. . . . . . ... . . .. .. . . . ... REP_WIDGET_INST MX View . .. . . . . . . .. . . . ... .. . . . . . . . . . . . . . . . ... . . . ... . .. . . . . . .

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

. . . . . ... . . . DeleteFolder Options and Arguments (pmrep) . .. . . . . .. .. . . . . .. . . . . FindCheckout Options and Arguments (pmrep) . . . ... . . .. . .. . . . Checkin Options and Arguments (pmrep) . . .. .. . 16-73. . . . . . . . . . . . . . .. . . . . .. . . . . . B-4. . . 16-75.. . . . .. . . . . Required Privileges and Permissions for Workflow Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . .. . . . . . . UndoCheckout Options and Arguments (pmrep) . . . . . . . . . . . . . . Registeruser Option and Argument (pmrep) . . . . . Required Permissions and Privileges for pmrep Tasks. . . . . . . . . . Bulkrestore Options and Arguments (pmrepagent) . ... 16-56. 16-74. . . . . 16-59.. . . . . . . . . .. . . . . . . Rmgroup Option and Argument (pmrep). . . 16-64. . . . . . .. . .. . . . .. . . . . . Create Options and Arguments (pmrepagent) . . ... .. . . . . . . . . . . . . . 16-62. . . . . . . . . . . . . . . . . . .. . . .. . . . . Edituser Options and Arguments (pmrep) . . . . . . .. . .. . . . . .. . . . . .. 16-65. . . 16-45. . . . . . .. .. . . . . . .. . . . . 16-68. . Rmuser Option and Argument (pmrep) . . . . . AddToDeploymentGroup Options and Arguments (pmrep) . . . .. 16-72. Validate Options and Arguments (pmrep) .. . .. . . . B-3. . Delete Options and Arguments (pmrepagent) . . . . . . .. . . .. . . .. .. . . . . . . . . . . . . . .... . ApplyLabel Options and Arguments (pmrep) . . . . . . . . . DeployFolder Options and Arguments (pmrep) . . . . . . . . Required Privileges and Permissions for Designer Tasks . .... . . . . . ... 16-54. . . . . . . . DeleteLabel Options and Arguments (pmrep) . ... . . . . . . . . . . .. . . . . . ... . . B-2. . . . Deployment Control File Elements and Attributes (pmrep) . . A-1. . . . .. .. . . . . . . . . . . . . . . . . . . DeleteDeploymentGroup Options and Arguments (pmrep) . . B-5.. . . . . . . . . . .. . . . . . . . . . . . .. . . 16-47. . . . 16-69. . . . . . .. . . ... . . . . . . .. . . .. . .. . 16-53. . . . . .. . .. . . . . 16-49. Registerplugin Options and Arguments (pmrepagent) . .. . . 16-63. . . .. . . . .. . 16-51.. . . . . . .. ExecuteQuery Options and Arguments (pmrep) . 16-50. . . . . . . . . .. . . . . . . . . . . . .. .. . ..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-52. . Backup Options and Arguments (pmrepagent) . . Object Import Control File Elements and Attributes (pmrep) . ... . . . . . . . . . . . . . . .. .. . . . . . .. . . . . . . . . . . . . . .. . . 16-48.. . . Required Privileges and Permissions for pmcmd Tasks . . . . pmrep Change Management Commands . . . 16-67. . . . . . ... . .. . . .. . Unregisterplugin Options and Arguments (pmrepagent) . .. . . . . .. . . . . A-2. . . . 16-61. . . pmrepagent Commands .. . . . . . . . 16-44. . . . . . . . . . . . . . . . . . .. . . 16-57. . . .. . . . . . . . . . B-1. CreateDeploymentGroup Options and Arguments (pmrep) . .. . . . . . . .. .. . . . ... . . . 16-71. . . . . . . . . . .. ClearDeploymentGroup Options and Arguments (pmrep) . . . . . . . .... . . . Required Permissions and Privileges for Repository Manager Tasks B-6. . . . . . . . . .. . 16-66. . . . . . . . . .. . 16-55. . . . .. . ModifyFolder Option and Argument (pmrep) . . . . . . . . . .. . .. . . . . . . . . ... . 16-46. . Createuser Options and Arguments (pmrep) . .. . . . . .. . . . . . . . . . . . Upgrade Options and Arguments (pmrepagent) .. . . . .. . . . . . . . . 16-70. Rmprivilege Options and Arguments (pmrep) .. .. . . .. . . . . . . . . . . . . . . . . . . Required Privileges and Permissions for Workflow Monitor Tasks . . .. . . . 16-60. . . . . . . .. . . 16-58. . . . DeployDeploymentGroup Options and Arguments (pmrep) . .. .. . . . . . . Rmuserfromgroup Options and Arguments (pmrep) .. . . CreateLabel Options and Arguments (pmrep) . . . Restore Options and Arguments (pmrepagent) . . .

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For more information on using pmrep for change management. Version Control 17 . You can also use pmrep to perform change management tasks. For more information on copying objects in a deployment group.repository. 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 automate the process for copying deployment groups. see “Using pmrep and pmrepagent” on page 403. This allows you to use pmrep scripts and files to automate change management tasks. For example. see “Copying Folders and Deployment Groups” on page 241.

18 Chapter 1: Understanding the Repository .

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

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

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

Progress Indicator 22 Chapter 2: Using the Repository Manager . 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 Windows The Repository Manager has a main window and a status bar for information on the operation you are performing. Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository.

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

you can view all tabs on the Properties dialog box. see “Viewing Version Properties” on page 203. Note: If you enable versioning when you create the repository. 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.Figure 2-2 shows the Navigator components: Figure 2-2. and then clicking the View Properties button in the toolbar. For more information about object properties. You can also right-click the object in the Navigator and select Properties from the shortcut menu. 24 Chapter 2: Using the Repository Manager .

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

Select a static deployment group to view details for deployment group objects. Displays properties for each workflow in the folder. Displays properties for each deployment group in the selected repository. The Source 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 task in the selected node. source connections and target connections nodes for the selected session. Displays the properties for each source within the selected 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. Displays the properties for each mapplet in the selected node. The Workflow Logs node displays under each workflow in the Workflows node. Displays workflow log information for the selected workflow. Displays connection properties for each source connection associated with the session. Displays the properties for each reusable transformation in the selected node. Displays properties for each worklet in the folder. Select a target in a mapping to view details for each port in the selected target definition.Table 2-1 shows the object details displayed in the Repository Manager Main window: Table 2-1. targets. Select a task to view the task details. Displays properties for each session in the folder. Displays properties for each source file associated with the session. and other objects associated with the worklet. Displays the properties for each target with the selected node. The Target Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. 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. Select a mapping to view sources. and transformation nodes that contain the sources. 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 mapping in the node. Select a transformation to view details for the specified transformation ports. Select a session to view session logs. Select a worklet to view the nodes for sessions. Select a workflow to view information for tasks and objects associated with the selected workflow. Select a source definition to view details for each port in the selected source definition. The Sessions Logs node displays under each session in the Sessions node. The Main window also displays information about pre. Select a target definition to view details for each target definition port. Displays connection properties for each target connection associated with the session. Select a mapplet to view the Transformations node containing the mapplet. tasks. and transformations used in the mapping. targets.and post-session email and commands. Displays session log information for the selected session.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Yes or No. The View Dependencies window also displays output. comments. and the Comments window displays text entered during object check in or check out.Table 2-4. Name of the user who purged the object. The Labels window displays labels associated with the object and information associated with the label object. To save the list of dependent objects as an HTML file. Object Dependencies Saved as HTML Viewing Object Dependencies 41 . Yes or No. Status of object deletion. and label information associated with the object. Type of checkout for object. The Output window displays validation information. User who created the object. Host name for the machine hosting 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. choose File-Save to File. Figure 2-8 shows an example of the HTML file saved from a View Dependencies window: Figure 2-8. Status of object as reusable. Repository hosting the object. Persistent or Non-Persistent.

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

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

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

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

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

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

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

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

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

or restore a repository. When you create. do not select an EBCDIC code page for the repository code page. see “Globalization Overview” in the Installation and Configuration Guide. you must choose a repository code page from a list of code pages that are compatible with the PowerCenter Client. The PowerCenter Client and Server code pages must be compatible with the repository code page. However.Repository Code Pages Every repository has an associated code page. For more information on code pages. 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. copy. Overview 51 .

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

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

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

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

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

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

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

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

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

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

Copying repositories provides a quick way to copy all metadata you want to use as a basis for a new repository. 2. You must back up and delete the existing repository from the target database before copying the repository. If you want to copy a repository managed by the same Repository Server. you must select a code page for the target repository that is compatible with the original repository. the copy operation fails. Choose Action-All Tasks-Copy From.Copying a Repository You can copy a repository from one database to another. set allow nulls by default to TRUE at the database level. choose Managed By the Same Repository Server. Note: If you want to copy a Sybase repository. The Copy From Another Repository dialog box appears. To copy a repository: 1. select the target repository configuration. For details. In the Console Tree. and select a repository from the repository list. You can also copy a repository when you want to move a repository from development into a production environment. If a repository exists in the target database. Copy a repository to preserve the original repository before upgrading. 62 Chapter 3: Managing the Repository . Setting this option changes the default null type of the column to null in compliance with the SQL standard. 3. When you copy a repository. see “Adding a Repository Configuration” on page 105 and “Importing a Repository Configuration” on page 115. you must add or import a repository configuration for the target repository. To copy a 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 skip workflow and session logs. For more details. see “Increasing Repository Copy. Click OK. and MX data. and Restore Performance” on page 60. and enter the repository name. deploy history. The Repository Server starts the repository when it finishes copying it. and Repository Server port number. 6. 5. Copying a Repository 63 . The Repository Server copies the repository from the source repository to the database specified in the destination repository configuration. click the Advanced button.4. If you want to copy a repository managed by a different Repository Server. select Managed By a Different Repository Server. 7. You can view the progress of the copy in the Activity Log. Backup. Enter the repository user name and password for the source repository. Repository Server host name.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. The port number the machine hosting the repository client application uses to communicate with the repository. Viewing User Connections and Locks 79 . Table 3-5 describes the repository user connection details: Table 3-5. 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. The time the user connected to the repository. To view user connection details: 1. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. The time of the last metadata transaction between the repository client application and 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. The TCP/IP address of the machine associated with the connection. The identification number assigned to the repository connection. The name of the machine running the application. The repository client application associated with the connection. Launch the Repository Manager and connect to the repository.

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

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

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

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

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

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

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

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

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

Reading the Repository Log Files 99 . INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information. 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. to ensure you are viewing the true message code. the file can grow to contain a large number of entries. 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. INFO : SF_34012 : (1324|1452) Opened Server Port [5001] to listen for client connections. 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. 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_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. INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. 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. since some message codes are embedded within other codes. However. the messages appear in the Application Log component of the Windows Event Viewer. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information.When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. you must view the text of the message.

Figure 3-4 shows a sample Windows Event Viewer: Figure 3-4. the Repository Agent writes messages to the file pmrepagent. You can specify a unique log file name for individual repositories by configuring the LogFileName option when you create or edit a repository configuration. You can view the repository log file using a text editor program such as Windows Notepad. 100 Chapter 3: Managing the Repository . You can write repository log messages from multiple repositories to the same log file. 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.log.

♦ ♦ When you configure the repository to write messages of a specific severity level to the log file. 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. Indicates the repository is performing an operation that may cause an error in a repository client application. Indicates the repository failed to perform an operation or respond to a request from a repository client application. Indicates the repository is performing an operation that does not indicate errors or problems with the repository.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. Information messages have the second lowest severity level. INFO : REP_51036 [Fri Jul 16 10:46:17 2004] : (2280|2256) Error logging enabled . if you configure the repository to write Warning severity level messages to the log file. the Repository Agent also writes Error severity level messages to the log file. the file can grow to contain a large number of entries. The Repository Agent also writes all messages of greater severity to the log file. This can cause repository inconsistencies or cause repository client applications to report errors. Error messages have the highest severity level. Reading the Repository Log Files 101 . Informatica recommends setting the ErrorSeverityLevel option in the repository configuration to Warning or Error unless you are troubleshooting a problem with the repository. INFO : REP_51006 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized configuration information. Trace messages are generally record message sizes and locking operations for specific objects in the repository. Warning messages have the second highest severity level. For example. INFO : REP_51008 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized request dispatcher. Indicates repository operations at a more specific level than Information. 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. 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. Warning. For example. Information. Trace.

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

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

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

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

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

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

Default is 3. 5. Default is 3. 108 Chapter 4: Configuring the Repository . New 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.4. Table 4-3 describes the options available on the Network tab: Table 4-3. Click the Network tab. Number of seconds the Repository Server waits while sending a message to a client application before timing out. Enter the network information.

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

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

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

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

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

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

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

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

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

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

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

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

the Repository Server verifies that the license file exists in the Repository Server installation directory. add them to the license file after you add the product license key. : / ? .Table 4-5. If the Repository Server cannot find the license file. Converting Special Characters in Repository License File Names Special Character in Repository Name ! % ^ & * ( ) [ ] { } ' " . < > \ | \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. or if the file contains an invalid or expired product license key. For more information on adding license keys to the repository license file. When you start a repository. Working with PowerCenter Licenses 121 . see “Adding a Repository Configuration” on page 105. it fails to start the repository. If you have option or connectivity license keys.

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Launch the Repository Manager and connect to the repository. The Repository Manager also allows you to terminate user connections. The time the user connected to the repository. The repository client application associated with the connection. 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. Choose Edit-Show 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. Table 5-5 describes the properties in the Repository Connections dialog box: Table 5-5. The name of the machine running the application. The TCP/IP address of the machine associated with the connection.Managing User Connections The Repository Manager allows you to view the connection details for users connected to the repository. The identification number assigned to the repository connection. 3. The time of the last metadata transaction between the repository client application and the repository. To view user connection details: 1. Managing User Connections 151 . 2. The Repository Connections dialog box appears. Click Close to return to the Repository Manager.

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

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

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

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

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

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

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

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

You have the tools to create a complex web of security. limit the ability of other repository users to perform unnecessary actions. Do not use shared accounts. Create groups with limited privileges. The more distinct your user groups. you can create appropriate user groups. 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. determine how many types of users access the repository. but the simpler the configuration. To avoid repository inconsistencies: ♦ Do not use shared accounts. limit privileges. 160 Chapter 5: Repository Security .Tips When setting up repository security. Using shared accounts negates the usefulness of the repository locking feature. across all folders? Before implementing security measures. assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. such as running sessions or administering the repository. Breaking a valid lock can cause repository and inconsistencies. The repository creates locks on objects in use. Then. Once you establish separate groups. To do this. answer the following questions: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ After you evaluate the needs of the repository users. the tighter your repository security. Then create separate user groups for each type. the easier it is to maintain. keep it simple. The simplest way to prevent security breaches is to limit the number of users accessing the repository. and limit folder permissions.

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

the Repository Manager uses the latest checked in version of an object for comparison. Compare objects between two folders in different repositories. You can specify the object types to compare and display between folders. You can specify either one-way or two-way comparisons. see “Comparing Objects” in the Designer Guide. A directional comparison checks the contents of one folder against the contents of the other. You must have read permission for each folder you want to compare. If you use a versioned repository. You can also compare two objects of the same type using Compare Objects. You must also have privileges to access the repositories containing the folders. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. 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 wizard performs directional comparisons. The wizard compares objects based on specific object attributes. The Compare Folders Wizard allows you to perform the following comparisons: ♦ ♦ Compare objects between two folders in the same repository. 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. Direction of comparison. See Table 6-2 on page 174 for a list of compared attributes for object types.Comparing Folders Before you copy or replace a folder in a repository. Table 6-2 lists the object types and attributes you can compare: Table 6-2. Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. you might want to verify the contents of a folder or compare it with other folders. Object types to compare. For more information on Compare Objects.

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. 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. regardless of whether you select the other objects to compare.Table 6-2.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

the shortcut becomes invalid. 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.

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

3. You can now use the shortcut in this folder. For details. Choose Repository-Save. or click Cancel to cancel the operation. see “Managing Business Components” in the Designer Guide. the folder in which you want the shortcut. 188 Chapter 7: Local and Global Shortcuts . expand the shared folder containing the object you want to use and drill down to locate the object. The shortcut now appears in the Navigator. save the object. choose the Source Analyzer or Mapping Designer tool. to create a shortcut for a source. 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. 2. the Designer creates a shortcut if the object does not already exist in the destination folder. cancel the operation. then create the shortcut. To create a shortcut for a target. To create a local shortcut in the workspace: 1. To create a local shortcut in the Navigator: 1. For example. the Designer displays a message asking if you want to create a copy of the object. 2. 4. 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. 3. Open the destination folder. Drag the object from the shared folder to the destination folder. choose the Warehouse Designer or Mapping Designer tool. click OK to create a shortcut. To create a shortcut. To create a local shortcut.Note: When you drag an object from a shared folder to a business component directory. In the Navigator. Select the appropriate Designer tool for the shortcut. 5. When prompted for confirmation. the folder in which you want the shortcut. Open the destination folder. After you drop the object.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. To include reusable and non-reusable dependencies. select both reusable and non-reusable dependency in Value 3: Working with Object Queries 235 .Finding Object Dependencies The following query returns sources and targets in the Vendors folder that are dependent on the mapping. To search for parent and child dependencies. Mapping_deploy.

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

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

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

Select to deploy all child dependencies.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. You manually add or delete objects from a static deployment group. right-click an object in the Navigator or in a detail window. No dependencies. choose Tools-Add to deployment group. You can specify the following conditions for adding child dependencies: ♦ ♦ ♦ All dependencies. 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. Select to skip deploying dependent objects. Figure 9-12 shows the Dependency for deployment group dialog box: Figure 9-12. choose Tools-Add to deployment group. select the group of objects in the Navigator and drag them into the 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. and choose Versioning-View History. To add objects from the Query Results or View History windows. Working with Deployment Groups 239 . see “Copying Folders and Deployment Groups” on page 241. In the Repository Manager. For information on deploying groups to a repository. In the View History window. To add several objects to a deployment group. For example. Dependency for Deployment Group Dialog Box When you select All Dependencies. You cannot add checked out objects to a deployment group. You can add checked in objects to a static deployment group from the Repository Manager. Select to deploy non-reusable dependent child objects. Non-reusable. you might group objects for deployment on a certain date and deploy all objects at once. you can also add child dependent objects to the deployment group. When you add objects to a static deployment group. you add all dependent objects to the static deployment group.

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

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

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

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

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

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

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

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

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

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

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

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

Copy dependency information for objects in mappings. Lists local shared folders in the target repository that you need to copy first. Allows you to select a PowerCenter Server to run all nonassociated workflows. 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 MQ connections in the folder. To preserve shortcuts and prevent invalid mappings. Copy persisted values for workflow variables. If the target repository contains less than two PowerCenter Servers. 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. Lists all application connections in the folder. To preserve shortcuts and prevent invalid mappings. Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder. Lists all external loader connections in the folder. indicating the connections for which you do not have read permission.Table 10-1. the wizard skips this step. click Cancel and copy all listed local shared folders before copying the folder. click Cancel and copy all listed local shared folders before copying the folder. Rename the target folder if a folder of the same name exists in the target repository. 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 . indicating the connections for which you do not have read permission. indicating the connections for which you do not have read permission. Choose to retain persisted values. 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 FTP connections in the folder. Lists all database connections in the folder. choose to retain persisted values for mapping variables. Lists global shared folders in the target repository that you need to copy first. it appends the date to the original folder name. if it exists. Choose to copy workflow logs if they exist. indicating the connections for which you do not have read permission. Otherwise.

If there are differences between the folders. Lists all dependent local and global shared folders. 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. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. 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. The wizard takes you back to Select Shared Folders dialog box. Displays objects that exist in the local shared folder but not in the global shared folder.Table 10-1. Lists folders you can select to establish shortcuts if you choose to override the default folder selection in the Select Shared Folders dialog box. click Cancel and copy all listed local shared folders before copying the folder. Select Shared Folders Advanced Override Shared Folder Advanced Compare Shared Folder Compare Results Advanced Advanced Copying or Replacing a Folder 253 . Lists the results from the folder compare. You can choose to accept or override the shared folder. a message warns you that shortcuts to missing objects will be removed. Also displays objects that are older or newer than matching objects in the global shared folder.

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

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

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

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

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

You can choose the shared folders to associate shortcuts. Copy dependency information for objects in mappings. Choose to retain persisted values. Select the deployment group to copy. if they exist. Choose to retain current values for Sequence Generator and Normalizer transformations. 4. Select a label in the source repository to apply to the copied object versions. 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 . The Copy Deployment Group Wizard appears. Table 10-3 lists the dialog boxes and prompts that you may see when you copy a deployment group: Table 10-3. 3. 5. Choose to retain persisted values for mapping variables. 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. Connect to the source and target repositories. Click Next. The Copy Deployment Group Wizard dialog box prompts you to select a mode: ♦ ♦ Typical. Choose to remove objects from the deployment group after the wizard completes the deployment operation. The Copy Wizard prompts you for more information based on the content of the folders and the copy mode you selected. Advanced. Click and drag or paste the deployment group to the target repository. To copy a deployment group: 1. and select a label in the target repository to apply to the newly created object versions. 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. The wizard uses the defaults for shortcuts to local and global shared folders. The wizard rolls back all changes. 2. displaying the folder name and target repository name. The wizard might have to determine how the folders are related before establishing shortcuts. Select the folders you want to compare. click Cancel. To stop the replacement. Override the default selections for deployment folders.

Lists all MQ connections in the folder. click Cancel and copy all listed local shared folders before copying the folder. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. To preserve shortcuts and prevent invalid mappings. 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 external loader connections in the folder. 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 FTP connections in the folder. indicating the connections for which you do not have read permission. indicating the connections for which you do not have read permission. Lists local shared folders in the target repository that you need to copy first. You can choose to accept or override the shared folder.Table 10-3. indicating the connections for which you do not have read permission. Lists all database connections in the folder. If the target repository contains less than two PowerCenter Servers. the wizard skips this step. 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 application connections in the folder. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. Allows you to select a PowerCenter Server to run all nonassociated workflows. indicating the connections for which you do not have read permission. Lists outdated folders in the target repository that you need to copy first. To preserve shortcuts and prevent invalid mappings. 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 . click Cancel and copy all listed local shared folders before copying the folder.

Table 10-3. Displays objects that exist in the local shared folder but not in the global shared folder. Also displays objects that are older or newer than matching objects in the global shared folder. Copying a Deployment Group 261 . The wizard takes you back to Select Shared Folders dialog box. 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. If there are differences between the folders. a message warns you that shortcuts to missing objects will be removed.

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

the default SQL used to extract data from the source defines the source as Shortcut_To_Employees. if the object is a source definition. the folder does not contain an object with the same name as the referenced object specified in the XML file. You can use the imported object as you would the original object. but you do not import the referenced object. Also in the Import Wizard. The PowerCenter Client does not find an object with the same name in the folder you specified. If the source table in the source database is named Employees. For example. you choose a folder in the destination repository to specify the location of an existing referenced object. you might need to rename the source definition. The Designer creates a new source definition in the destination folder named Shortcut_To_Employees. However. you export a shortcut named Shortcut_To_Employees and you also export the referenced object. This source definition is a copy of the original object. 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. In the Import Wizard. 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. When you use the source definition in a mapping. you choose to import the shortcut. and is not a shortcut. However. so it imports the actual object instead. The XML file defines the metadata for the object.Importing Shortcuts to Sources When the PowerCenter Client imports the object instead of the shortcut. Working with Shortcuts 275 .

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

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

you can modify for an exported object and then import. The Create New column indicates which objects you can define directly in the XML file and then import. Table 11-5. 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 .

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 .Table 11-5.

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

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

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

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

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

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

Click Close in the Exported Objects dialog box. 7.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. You can click View File to view the XML file the PowerCenter Client creates. 286 Chapter 11: Exporting and Importing Objects .

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

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

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

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

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

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

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

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

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

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

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

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

Identifies the current conflict and the name of the object with the conflict. Choices might be different. Allows you to choose additional options for session and workflow resolutions. For more information. target instance name. original instance name. 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. Displays the elected resolution or a list of choices for resolution. the message describes the resolution. if any. 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.Table 12-1 describes the areas of the Copy Wizard: Table 12-1. such as applying default connections or retaining server connections during the copy. and action taken to resolve the conflict. see “Viewing Object Dependencies” on page 305. Compares duplicate objects in the target folder to the objects you are copying. After you choose a resolution. 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.It displays a red icon next to each object with a conflict. Displays the items to copy. Displays object dependencies for the current object. Next Conflict/Option displays only with session or workflow conflicts that you resolve by renaming or replacing the target. For more information. depending on the conflict. existing conflicts. Overview 299 . see “Comparing Repository Objects” on page 45. Applies the resolution to all unresolved conflicts or just the conflicts for the same object type.

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

The selected resolution reuses the object. To apply the resolution to more objects. you can apply the resolution to all unresolved objects of the same type. Resolving Copy Conflicts 301 . Optionally. or to all conflicts in your copy. Figure 12-2. click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type.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.

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

You can import multiple source and target definitions at a time. you can export targets to some tools as dimensions.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. You cannot export shortcuts. When you export a source or target with a foreign key. Overview 315 . You cannot export source and target definitions at the same time. For more information on licenses. However. the Repository Agent also exports the source or target containing the corresponding primary key. see “Working with PowerCenter Licenses” on page 119. You can export multiple source definitions or multiple target definitions at a time. You must have a Metadata Exchange option license key to exchange metadata for a specific tool. You cannot export cubes and dimensions.

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. Choose a path and file name. You can click More Info to read about the tool requirements. and choose Repository-Export Metadata. The Metadata Export Wizard appears. In the Repository Manager Navigator. 316 Chapter 13: Exchanging Metadata . 2. select the object or objects you want to export. To export metadata: 1. Choose the target tool you want to export the object to.

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

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

Choose the target tool from which you want to import the object.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. The wizard uses the file name as the source database name for each object you import. The Metadata Import Wizard appears. select the folder into which you want to import metadata. Steps for Importing Metadata 319 . 2. In the Repository Manager. To import metadata: 1.

and click Next. 6. 4. Click Next. 5. Enter the PowerCenter options. 320 Chapter 13: Exchanging Metadata . The PowerCenter Options page of the wizard appears.3. 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. The Metadata Import Wizard displays options specific to the tool you select. such as IBM DB2 Cube Views.

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

For information on resolving conflicts in the Copy Wizard. The Metadata Import Wizard adds the objects to the folder in the repository. Click Next. and click Finish.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. The Conflict Resolution Wizard is similar to the Copy Wizard. 8. 322 Chapter 13: Exchanging Metadata . 9. In the Object Selection page. Use the Conflict Resolution Wizard to resolve specific object conflicts. the Metadata Import Wizard opens the Conflict Resolution Wizard. select which objects to import into the repository. If the folder contains objects with the same name as those you import. see “Copying Objects” on page 297.

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

324 Chapter 13: Exchanging Metadata .

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

♦ All metadata extensions exist within a domain. User-defined. Third-party application vendors create vendor-defined 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. delete. For example. You can also change the values of user-defined extensions. You can view and change the values of vendor-defined metadata extensions. You see the domains when you create. you can store your contact information with the mapping. You associate information with repository metadata using metadata extensions. edit. You create user-defined metadata extensions using PowerCenter. PowerCenter Client applications can contain the following types of metadata extensions: ♦ Vendor-defined. when you create a mapping. delete. 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 . If you are using third-party applications or other Informatica products. you may see domains such as Ariba or PowerCenter Connect for Siebel. or redefine them. Vendor-defined metadata extensions exist within a particular vendor domain. You cannot edit vendordefined domains or change the metadata extensions in them. you add them to this domain. You can create. but you cannot create. User-defined metadata extensions exist within the User Defined Metadata Domain. edit. and view user-defined metadata extensions. When you create metadata extensions for repository objects. or view metadata extensions.

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

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

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

the Repository Manager grants Client Visible permission as well. Click Done. Specifies whether the metadata extension is private to the domain in which it is created. The Repository Manager enables this option when third-party application vendors create vendor-defined metadata extensions only. 330 Chapter 14: Metadata Extensions . If you enable Share Write permission. Share Read Share Write Optional Optional Private Optional Description 6. 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.Table 14-1. Specifies whether the value of the metadata extension is editable across vendor domains. Optional Click Create. Specifies whether the metadata extension is visible in vendor domains. Specifies whether the metadata extension is visible in PowerCenter. Optional description of the metadata extension. If you select this option. the Repository Manager grants Share Read permission as well. Specifies whether the value of the metadata extension is editable in PowerCenter. 7.

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

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

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

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

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

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

The next generation of MX. vendors of popular query and reporting tools can quickly create a metadata link between their products and the PowerCenter repository.sq_ termxdrp. Software vendors can integrate Informatica metadata with their products through different methods. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories.Table 15-3. from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access. called Metadata Exchange SDK. Viewing the Repository Metadata 337 . Integrating MX Views with Third-Party Software With MX software and support from Informatica. 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.

Database Definition View The database definition view provides a list of all database definitions in the repository. REP_DATABASE_DEFS Table 15-4 lists database definition details: Table 15-4. MX provides the REP_DATABASE_DEFS view to help you analyze database definitions. Version ID of the source. Informatica recommends using the fields in bold to join views. 338 Chapter 15: Using Metadata Exchange (MX) Views . and the folder where the database definition resides. Folder name. Source of the definition. A database definition includes the source database names. 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. flat file or RDBMS.

Table 15-6 lists source information in the REP_ALL_SOURCES view: Table 15-6. Source definitions can be defined for both relational and nonrelational sources. see “REP_SRC_TBLS” on page 344. Source Views 339 . 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. Name of the parent source Business name of the parent source. 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. see “REP_ALL_SOURCES” on page 339. see “REP_ALL_SOURCE_FLDS” on page 341. Folder ID. For more information. description. and business name. Table 15-5 lists the different views that help you analyze source metadata: Table 15-5. column properties. This view provides access to the fields in relational sources. For more information. These views also show source properties such as shortcuts. Sources include both relational sources and non-relational sources such as XML files and flat files. and mappings and mapplets where these sources are used. see “REP_SRC_TBL_FLDS” on page 346. You can use the source name to retrieve all the fields belonging to the source. source metadata extensions. These views provide access to the fields in a non-relational source. They also provide information such as source columns. For more information. creation date. see “REP_SRC_FILES” on page 343. For more information. see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345.Source Views Source views provide a list of the latest version of all source definitions defined by folder of any PowerCenter 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. For more information. 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. This view provides a list of all file definitions in the repository. For more information. version. This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View.

Source name. Database name of the parent source. Source description. Folder name. ID of the first field in the source. Source ID. File organization information. Name of the source schema. UTC time when the source display was last saved. Physical size (compressed binary). Source version number. Parent source physical size (compressed binary). Folder ID. Specifies whether the source is a relational or a non-relational source. Specifies whether the source version is active or has been deleted. Time when the parent source was last modified. Time when the source was last saved. 340 Chapter 15: Using Metadata Exchange (MX) Views . UTC time when the parent source was last modified. Description of the parent source. Parent source version status. Name of the database type of the parent source. UTC time (Coordinated Universal Time) when the parent source was checked in. UTC time for source checkin. 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.Table 15-6. Source version number. Parent source display size (uncompressed binary).

Table 15-6. Source type such as relational database or flat file. 1 = shortcut. Database type of the parent source. For local shortcuts. 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. Parent source ID. the names of shortcut and the parent targets display. REP_ALL_SOURCE_FLDS This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. Specifies whether the source is a global shortcut. Business name of the parent source. 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. For global shortcuts. Informatica recommends using the fields in bold to join views. Description of the parent source. Status of the parent source version. The repository name. UTC time when the parent source was last saved. 0 = not a shortcut. Source Views 341 . Time when the parent source was last modified. 0 = not a shortcut. Parent folder ID. Database name of the parent source. Parent source name. Version number of the parent source. UTC time when the parent source was checked in. the name of the shortcut displays. 1 = shortcut. Table 15-7 lists source field information in the REP_ALL_SOURCE_FLDS view: Table 15-7. Specifies whether the source is a shortcut.

Source version number. ID of the field that follows the current field. ID of the source field (primary key). Physical field length. Identifies the field/record that this field/ record redefines. Number of time that the field (or record) occurs in the source. Time when the source was last saved. Null for relational sources. Source field name. Source description. Offset of this field within this FD. The next child. Source ID. Picture text that a COBOL source uses. Business name of the source field. Display field length. 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. Specifies whether the source version is active or has been deleted. UTC time when the source was last saved. Field level number for non-relational sources. Source field number. Description of the source field. Offset of this field within the source. Folder ID. Name of the database for the source. 342 Chapter 15: Using Metadata Exchange (MX) Views . UTC time when the source was last checked in. Source name. if any. for a non-relational COBOL source.Table 15-7.

1 = shortcut. REP_SRC_FILES This view provides a list of all file definitions in the repository. Scale for the field. Specifies whether the source is a shortcut. 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. Length or precision for the field. 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. Table 15-8 lists file information in the REP_SRC_FILES view: Table 15-8. Name of file definitions. File organization information. File from which schema was extracted. Type of database extracted from. Any flat file imported through the Source Analyzer has an entry. Field datatype. Name of database extracted from (DSN). 0= nulls allowed. Informatica recommends using the fields in bold to join views. Source field picture usage name. 1 = nulls not allowed. Minimum physical size (varying records). 0 = not a shortcut. 1 = shortcut. Specifies whether nulls are allows. Repository name. Source Views 343 .Table 15-7. Display size (uncompressed). Specifies whether the source is a global shortcut. 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). Folder name. 0 = not a shortcut. Physical size (compressed binary).

344 Chapter 15: Using Metadata Exchange (MX) Views . Name of schema extracted from. Source description. 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. Link to first field. Version ID. Source description. Type of database extracted from. Business name of the table.Table 15-8. Informatica recommends using the fields in bold to join views. Unique key. Informatica recommends using the fields in bold to join views. Folder version name. Folder version ID. 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. Name of database extracted from. Folder ID. Last time the source table was saved. Folder name. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9. Source version number. Source version number. 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.

Key type. Offset using display length. Informatica recommends using the fields in bold to join views.e. Field name. Comments for this field. 0 = not a key. 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). Display length. Link to next field at this level. 01. Link to child field if this is a group item.. Number of OCCURS. Each field is contained in the scanned tables listed in the REP_SEG_FLDS view. Decimal scale for numeric fields. Field level (i. Physical length. COMP type (binary compressed fields). Table 15-10 lists source field information in the REP_SRC_FILE_FLDS and REP_SEG_FLDS views: Table 15-10. Folder name. Source Views 345 . Version ID of the source. Decimal precision for numeric fields or field length for CHAR fields. Order number of the field. Physical offset. PIC clause. Source ID (primary key). 02). 1 = primary key.REP_SRC_FILE_FLDS and REP_SEG_FLDS These views provide access to the fields in a non-relational source. Redefines this field.

Table 15-11 lists relational source fields in the REP_SRC_TBL_FLDS view: Table 15-11. Folder ID. Field ID (primary key). Table name. Link to next field in source table. Decimal scale for numeric fields. Description of the column. Source version number. You can use the source name to retrieve all the fields belonging to the source.REP_SRC_TBL_FLDS This view provides access to the fields in relational sources. Order number of the column. Business name of the field. Source table ID. Folder name. 346 Chapter 15: Using Metadata Exchange (MX) Views . 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. Data type for this column. Folder version name. The columns in this view are part of the tables listed in the REP_SRC_TBLS views. Folder version ID. Key type for this column. Decimal precision for numeric fields or field length for CHAR fields. Business name of the table. Informatica recommends using the fields in bold to join views.

This view provides a list of targets in the repository. column properties. creation date. and mappings and mapplets where these target are used. the name of the shortcut displays.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. These views also show target properties such as shortcuts. This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Business name for the target. description. For more information. Folder ID. see “REP_TARG_TBL_COLS” on page 351. Table 15-13 lists target details in the REP_ALL_TARGETS view: Table 15-13. see “REP_TARG_TBLS” on page 350. target metadata extensions. 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. For local shortcuts. Targets include both relational and non-relational targets such as XML files and flat files. For global shortcuts. the names of shortcut and the parent targets display. 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. FIRST_COLUMN_ID is a link to the set of columns for this table. Table 15-12 lists the different views that help you analyze target metadata: Table 15-12. 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. For more information. Target Views 347 . Target description. see “REP_ALL_TARGET_FIELDS” on page 349. For more information. They also provide information such as target columns. Target name. Target version number. This view provides the properties of columns defined for the target tables in a data warehouse or data mart. see “REP_ALL_TARGETS” on page 347. and business name. For more information. Target ID (primary key).

Folder ID. UTC time when the target was last saved. Options for use when generating DDL. User-specified constraint string used when the DDL is generated. Repository name. 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 version number. 1 = shortcut. Specifies whether the target is a global shortcut. 0 = not a shortcut. Status of the target version. Target ID. 0 = not a shortcut. UTC time (Coordinated Universal Time) when the target was last checked in. Target description. Specifies whether the target is a shortcut. ID for the parent target file. UTC time when the target was last saved. Target name. Link to first field of this table. Informatica recommends using the fields in bold to join views. UTC time (Coordinated Universal Time) when the parent target was checked in. Link to first field of this table. Time when the target was last saved. Time when the target was last modified.Table 15-13. 1 = shortcut. Folder name. 348 Chapter 15: Using Metadata Exchange (MX) Views . Database type for the parent target.

Target version number. For global shortcuts. Parent target ID. Status of the parent target version. UTC time when the target was last saved. UTC time when the parent target was last saved. Time when the parent target was last modified. Table 15-14 lists target field data in the REP_ALL_TARGET_FIELDS view: Table 15-14. Time when target was last modified. Description of parent target. the names of the shortcut and the parent targets display.REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Folder ID. Target Views 349 . Target version number. Target description. Target ID. Status of the target version. For local shortcuts. ID of parent target file. Name of parent target. Folder name. ID of the first field of parent target. Folder ID. Database type of parent target. Target name. UTC time when the target was last checked in. 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. Business name of the parent target. the shortcut name displays. UTC time (Coordinated Universal Time) when the parent target was last checked in.

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. All tables contained in the target table model are part of this view. Description of target field. Money. String. Business name of target field. Text. Specifies whether the target is a global shortcut. It is the primary table list used to delineate a PowerCenter data model. 0 = Null. B = Binary and Bit C = Character. 1 = shortcut. Scale for target field. The tables are virtual. Therefore. and Byte D = Date N = Numeric. FIRST_COLUMN_ID is a link to the set of columns for this table. verify that the table exists before using this view. Link to source from which this field was created. Target field ID. 0 = not a shortcut. ID of the next field in target. Picture text that COBOL sources use. 1 = shortcut. Specifies whether the target is a shortcut. 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.Table 15-14. Specifies whether target field is null. Repository name. 350 Chapter 15: Using Metadata Exchange (MX) Views . Datatype group codes. Datatype of target field. REP_TARG_TBLS This view provides a list of targets in the repository. not physically created. Key type of target field. Target field number. 0 = not a shortcut. 1 = Not Null. and Bigint Precision for target field.

Table this column belongs to. Column ID (primary key). Table creation options specified in the Warehouse Designer. REP_TARG_TBL_COLS This view provides the properties of columns defined for the target tables in a data warehouse or data mart. Folder version ID. Order number of the column. Folder version name.Table 15-15 lists the columns in the REP_TARG_TBLS view: Table 15-15. Business name of the table. Link to first field of this 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. Folder ID. Informatica recommends using the fields in bold to join views. Table ID. Table 15-16 lists target table column properties for the REP_TARG_TBL_COLS view: Table 15-16. 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. Time target table was last saved. Table business name. Description of the table. Table constraint specified in Warehouse Designer. Business name of this column. Target Views 351 . Column name. Target version number. Table name.

C = Character D = Date N = Numeric Decimal precision for numeric fields or field length for CHAR fields. Native database datatype. 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. 352 Chapter 15: Using Metadata Exchange (MX) Views . Link to source this column was created from. Datatype group. Column description. Primary and Foreign Key. Decimal scale for numeric columns. Target version number.Table 15-16. Foreign Key. 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. Not a Key. Whether NULLs are accepted. Primary Key. Folder version name. Link to next column.

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

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. UTC time when the mapping was last saved. UTC time when the mapping was checked in. Parent mapping description. Name of mapping. the names of the shortcut and the parent mappings display. UTC time (Coordinated Universal Time) when the parent mapping was checked in. Mapping description. Parent mapping version number. Time when the mapping was last saved. Specifies whether the parent mapping is valid. Status of the mapping version. Repository name. Sequence ID of the parent mapping. the name of the shortcut displays. 0 = not a shortcut. Specifies whether the mapping is a global shortcut. 354 Chapter 15: Using Metadata Exchange (MX) Views . Folder name. Folder ID.REP_ALL_MAPPINGS This view provides a list of the latest version of all mappings defined in each folder of a repository. Parent folder ID. Name of the parent mapping. Date and time when parent mapping was last saved. The UTC time when mapping was last saved. For local shortcuts. Mapping version number. Table 15-18 lists mapping information in the REP_ALL_MAPPINGS view: Table 15-18. 1 = shortcut. For global shortcuts. Parent mapping version status. Sequence ID for mapping.

Table 15-19 lists mapplet metadata in the REP_ALL_MAPPLETS view: Table 15-19. For local shortcuts. Field ID (primary key). Time when the mapplet was last saved. Name of parent mapplet. Mapplet ID. Parent mapplet description. UTC time (Coordinated Universal Time) when the parent mapplet was checked in. For global shortcuts. Folder name. Sequence ID of parent mapplet. The UTC time when mapplet was last saved. UTC time when the mapplet was last saved. Folder ID. UTC time when the mapplet was checked in. 1 = shortcut. The date and time when parent mapplet was last saved. the name of the shortcut displays. Mapping and Mapplet Views 355 . 0 = not a shortcut. Status of the mapplet version. Name of mapplet. Informatica recommends using the fields in bold to join views. REP_ALL_MAPPLETS This view provides a list of the latest version of all mapplets defined in each folder of a repository. the names of the shortcut and the parent mapplets display. Mapplet version number. 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. Parent folder ID. Specifies whether the parent mapplet is valid. REP_ALL_MAPPINGS MX View Column Name IS_SHORTCUT Datatype NUMBER Description Specifies whether the mapping is a shortcut.Table 15-18. Parent mapplet version status.

Repository name. It does not contain information about sources. Specifies whether the mapplet is a shortcut. Folder version ID. REP_TARG_MAPPING This view provides access to the compound table-level transformation expressions for each target table. 1 = shortcut. Description of transformation expression.Table 15-19. 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. Compound conditional load. Target business name. Table 15-20 lists expression information in the REP_TARG_MAPPING view: Table 15-20. This view contains information about mappings defined for target tables only. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Note: Use the REP_TBL_MAPPING view to analyze source and target relationships. 0 = not a shortcut. 1 = shortcut. 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. Mapping name. Compound group by expression. Join REP_TBL_MAPPING and REP_TARG_MAPPING by MAPPING_NAME to include column-level mapping information in the REP_FLD_MAPPING view. Folder version name. Compound SQL override expression. 0 = not a shortcut. Compound source filter condition. Folder name. 356 Chapter 15: Using Metadata Exchange (MX) Views . This view pulls information from all the transformation objects that contribute to the target table in a valid mapping. Foreign key that points to generated mapplet transformation. Specifies whether the mapplet is a global shortcut. Description of mapping.

Administrator comment. REP_TARG_FLD_MAP This view shows compound field-level transformation expressions associated with a target. Table 15-21 lists expression metadata that you find in the REP_TARG_FLD_MAP view: Table 15-21. Informatica recommends using the fields in bold to join views. 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. Informatica recommends using the fields in bold to join views. Target version number. Mapping name. Target version number. The field-level expression contains all the source fields (both file definition/non-relational source) that make up the value of the target field. Name of target (table). There might be many mappings for a set of fields. see the Transformation Language Reference.Table 15-20. Mapping version number. Folder version ID. Mapping comment. This view pulls information from all transformation objects that contribute to the target table in a valid mapping. 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). For details on the syntax of the transformation expression. Time the mapping was saved last. Compound transformation expression. each distinguished by the MAPPING_NAME field. Business name of target table. Business name of target field. Mapping version number. End user comment. Mapping and Mapplet Views 357 . Folder version name. Folder name.

Folder name. Table 15-22 lists the source and target field metadata in the REP_FLD_MAPPING view: Table 15-22. Administrator comment. Target table ID. Name of the source table. Business name of the target. Time the mapping was saved last. Name of the target field. Source version number. This is the companion view for the REP_TBL_MAPPING view. Target name. Mapping comment. Informatica recommends using the fields in bold to join views. 358 Chapter 15: Using Metadata Exchange (MX) Views . Folder ID. 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. Target version number.REP_FLD_MAPPING This view shows the source fields used by the target fields in a mapping. End user comment. Business name of the target column. Mapping ID. Mapping version number. Name of the mapping. It contains both source and target column names and details. Business name of the source field. Target field transformation expression. Folder version name. Folder version ID. Source table ID. Business name of the source table.

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

Time the mapping was saved last. 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. Folder name. This view pulls information from all transformation objects that contribute to the target table in a valid mapping to provide the table-level expressions. Source ID. Folder ID. Folder version name. 360 Chapter 15: Using Metadata Exchange (MX) Views . Table 15-25 lists mapping target metadata in the REP_TBL_MAPPING view: Table 15-25. Informatica recommends using the fields in bold to join views. Business name of the source. 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. Field transformation expression. Target version number. Administrator comment. Target ID. Folder version ID. Target name. Compound target. Name of the mapping. End user comment. Business name of the target. REP_TBL_MAPPING This view shows all of the target tables used in a mapping and provides source to target mapping information. Source version number. Folder name. Business name of the source table. Mapping comment.Table 15-24. Mapping version number.

Business name of first table. or through primary key-foreign key relationships. Compound SQL override expression. Source version number. Description of transformation. Compound source filter condition. Folder version name. 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. Target version number. Table 15-26 lists target table join metadata in the REP_TARG_TBL_JOINS view: Table 15-26. Mapping ID. Mapping version number. Name of column in first table. Mapping and Mapplet Views 361 . Folder version ID. Informatica recommends using the fields in bold to join views. ID of first table in the join. It is populated when you link fields in the Warehouse Designer. Time the mapping was saved last. Business name of column in first table. REP_TARG_TBL_JOINS This view contains join information between target tables. Mapping comment. Folder version name. 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 conditional load. Use this view to query the PowerCenter defined joins for a target table model. Name of first table in the join. Compound group by clause. Folder version ID.Table 15-25.

362 Chapter 15: Using Metadata Exchange (MX) Views .Table 15-26. Business name of second table. 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. Name of the instance. targets. Folder ID (primary key). Object type. Mapping version number. ID of column in first table. ID of second table in the join. Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS view: Table 15-27. Source field name. Informatica recommends using the fields in bold to join views. Name of the mapping. Table1 version number. REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources. Source field ID (primary key). 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. ID of column in second table. Unique ID for the instance in a mapping. Name of second table in the join. Object type name. and transformations in a mapping. Table2 version number. Number of column in second table. Name of column in second table. Sequence ID for the mapping (primary key). Business name of column in second table.

Source object instance ID. or transformation. Target object type such as port. Sequence ID for the mapping (primary key). Source object type. target. Target object instance ID. Folder name. Source object version number. Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN view: Table 15-28. mapplet. REP_MAPPING_UNCONN_PORTS MX View Column Name OBJECT_VERSION_NUMBER Datatype NUMBER Description Version number of the source. Target object version number. and mapplets. Unconnected transformations are not included. Mapping name.Table 15-27. Informatica recommends using the fields in bold to join views. Target object type name. Mapping version number. REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a mapping. Name of the source object type. Source object name. Target object ID. Source object ID. targets. transformations. target. Objects include sources. and transformation. Mapping and Mapplet Views 363 . Source object field 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. Informatica recommends using the fields in bold to join views. Target object name. Target object field name.

364 Chapter 15: Using Metadata Exchange (MX) Views . Metadata Extension Views View REP_METADATA_EXTNS REP_METADATA_EXTN_DEFINES Description This view displays the details of all metadata extensions in the repository. Table 15-30 lists metadata extension information in the REP_METADATA_EXTNS view: Table 15-30. Metadata extension value. REP_METADATA_EXTNS This view displays the details of all metadata extensions in the repository. Metadata extension name. Globally unique domain identifier. Object type the metadata is associated with. Object version number. 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. Description of the metadata extension. For more information. Folder ID. Table 15-29 lists the different views that help you analyze metadata extensions metadata: Table 15-29. Unique name for a user-defined metadata domain. Object the metadata value is associated with. Permissions type. Datatype of the metadata extension value. For more information. Line number of the text when there are multiple lines of text. see “REP_METADATA_EXTN_DEFINES” on page 365.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_EXTNS” on page 364. Name of the object type. This view displays reusable metadata extensions defined for objects in metadata extension domains.

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

For local shortcuts. dependencies. Parent transformation ID (primary key). Folder ID. Parent folder ID. This view displays both reusable transformations defined in the Transformation Designer and transformation instances defined in mapping and mapplets. the name of the shortcut displays. Table 15-33 lists transformation metadata in the REP_ALL_TRANFORMS view: Table 15-33. instances. and field level details of transformations. see “REP_WIDGET_FIELD” on page 369. These views also display properties such as attributes. This view displays field level details for transformations. see “REP_WIDGET_DEP” on page 368. Name of the parent transformation. For more information. 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. It also shows all shortcut transformations in a folder. This view displays the details of dependencies between transformation instances in a mapping. This view displays attribute details for transformations. 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_WIDGET_INST” on page 368. This view displays the details of all transformation instances. Folder name. For more information. For more information. 366 Chapter 15: Using Metadata Exchange (MX) Views . For more information. Table 15-32 lists the different views that help you analyze transformation metadata: Table 15-32. the names of the shortcut and the parent transformation display. For global shortcuts. and sessions. see “REP_WIDGET_ATTR” on page 369. For more information. 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.Transformation Views Transformation views display details of all reusable and non-reusable transformation instances by folder in a PowerCenter repository. port-level connections. see “REP_ALL_TRANSFORMS” on page 366.

Transformation type name. Transformation Views 367 . 1 = shortcut. UTC time when the parent transformation was last saved. Status of the transformation version. Version number of the transformation. Specifies whether the transformation is reusable. Specifies whether the transformation is a global shortcut. 0 = not reusable. Time when the transformation was last saved. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Transformation ID. UTC time (Coordinated Universal Time) when the parent transformation was last checked in. Transformation description. Date and time when transformation was last saved. 0 = not a shortcut. Transformation type ID. 0 = not a shortcut. Status of the parent transformation version. 1 = shortcut. Name of the transformation. Specifies whether the transformation is a shortcut. UTC time when the transformation was checked in. 1= reusable.Table 15-33. UTC time when the transformation was last saved. Repository name. 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. Parent transformation description.

Transformation name. Informatica recommends using the fields in bold to join views. Version number of the transformation. Informatica recommends using the fields in bold to join views. 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. Table 15-35 lists transformation dependency information in the REP_WIDGET_DEP view: Table 15-35. 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.REP_WIDGET_INST This view displays the details of all transformation instances. ID of the transformation instance. Description of the transformation instance. Description of the transformation instance. Version number of the mapping. Table 15-34 list transformation metadata in the REP_WIDGET_INST view: Table 15-34. Field ID of the source transformation instance. Field ID of the target transformation instance. REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a mapping. Transformation type. Name of the transformation instance. 368 Chapter 15: Using Metadata Exchange (MX) Views . Name of the transformation instance. Target field ID.

Transformation field name. Attribute data type Attribute name. Transformation field ID. Attribute ID. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37. Partition ID. Mapping ID. Used to break up long strings into multiple rows. Instance ID. Object (session. REP_WIDGET_FIELD This view displays field level details for transformations. Transformation type.REP_WIDGET_ATTR This view displays attribute details for transformations. instances. and sessions. Informatica recommends using the fields in bold to join views. Description of the attribute. Attribute value. Transformation field precision. or transformation) version number. Attribute type. and sessions. Transformation Views 369 . Table 15-36. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID. 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. Object type ID. Table 15-36 lists attribute details for transformations. instances. mapping. Session task ID.

Informatica recommends using the fields in bold to join views. Datatype group code. Default value of the transformation field. Datatype number. Field-level property used by transformations. Comments on the field. Expression name. 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.Table 15-37. External database type. Source field ID for normalizer transformation. Transformation field data type. Transformation version number. Transformation port type. The ID of the corresponding instance in the mapplet's mapping. Expression type. Transformation datatype of the port. Transformation order. Comments on the expression. 370 Chapter 15: Using Metadata Exchange (MX) Views .

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

see “REP_SESS_PARTITION_DEF” on page 385. For more information. Workflow name.Table 15-38. see “REP_SESS_TBL_LOG” on page 388. For more information. see “REP_SESS_WIDGET_CNXS” on page 383. This view provides partition details of the sources. If the session overrides a parameter in the configured object. For more information. For more information. This view displays the attribute values and overridden values for session and workflow tasks. and transformations in a session. see “REP_SESSION_FILES” on page 382. Table 15-39 lists workflow and scheduling information in the REP_WORKFLOWS view: Table 15-39. see “REP_SESSION_INSTANCES” on page 381. see “REP_SESS_CONFIG_PARM” on page 385. For more information. 372 Chapter 15: Using Metadata Exchange (MX) Views . the view displays two rows. 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. For more information. see “REP_SESSION_INSTANCE_FILES” on page 383. 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. This view contains file connections associated with reusable sessions. see “REP_SESS_LOG” on page 387. 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. This view contains file connections associated with reusable sessions. Start time configured for the scheduler. End time configured for the scheduler. see “REP_COMPONENT” on page 384. For more information. This view contains information about the sources and targets used in a session. This view contains information about the status of an individual session run against a target. Workflow. This view displays the list of tasks such as a command or an email for each session. This view displays session configuration parameter details. Worklet. Scheduler associated with the workflow. For more information. see “REP_TASK_ATTR” on page 386 This view provides log information about sessions. For more information. targets.

1 = valid. Date and time when the workflow was last saved. 0 = invalid. Workflow version number. 8 = Customized repeat. Specifies whether the workflow is valid or not. Number of times the PowerCenter Server runs the workflow before stopping the workflow. Version number of the scheduler. Records the following values for each schedule type: 1 = Run on demand. Description of the workflow. Number of seconds the PowerCenter Server waits between successive workflow runs. 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. Scheduler description. 2 = Run forever.Table 15-39. PowerCenter Server ID. 16 = Run on server initialization. REP_WORKFLOWS MX View Column Name RUN_OPTIONS Datatype INTEGER Description The workflow schedule type. The stop condition option for the workflow schedule type. 1 = End after the number of runs stored in RUN_COUNT. and Task Views 373 . Workflow. Folder ID. 2 = Run once. 4 = Run every DELTA_VALUE seconds. Worklet. Workflow ID. Specifies if scheduler is reusable. Records the following values for each stop condition option: 0 = End on a date. Scheduler ID. Name of the PowerCenter server registered with the repository. 32 = Run continuously.

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. or session is valid. 0 = not reusable. Scheduler ID (primary key). Folder ID. Values are: 1 = reusable. 1 = enabled. UTC time when task was last saved. 374 Chapter 15: Using Metadata Exchange (MX) Views . 0 = invalid. worklet. Task ID. Version number of the task. Table 15-40 lists reusable and non-reusable task information in the REP_ALL_TASKS view: Table 15-40. Description of the task. 0 = disabled. Specifies whether the task is enabled or not. Start time configured for the object associated with the scheduler. REP_ALL_SCHEDULERS This view displays a list of schedulers by folder. Specifies whether the task is reusable or not. 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. Informatica recommends using the fields in bold to join views. Task name. Name of the scheduler. Task type name. UTC checkin time. Task type. 1 = valid. Table 15-41 lists information in the REP_ALL_SCHEDULERS view: Table 15-41. Specifies whether a workflow. 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.

UTC time (Coordinated Universal Time) when the scheduler was last saved. Number of workflow runs. 5 = Run on demand and Delta schedule. Delta between successive runs (stored as seconds). 18 = Run on server init and Run once schedule. Version number of the scheduler. The scheduler type.Table 15-41. 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. 40 = Run continuously and Custom repeat. 24 = Run on server init and Custom repeat. and Task Views 375 . UTC checkin time. Specifies when the task must stop running. 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. Workflow ID (primary key). 34 = Run continuously and Run once schedule. Unique ID for a variable within a workflow (primary key). 9 = Run on demand and Custom repeat. 3 = Run on demand and Run once schedule. Specifies whether the scheduler is reusable or not. 2 = Run once schedule. Worklet. REP_WFLOW_VAR This view displays a list of all variables declared within a workflow or worklet. Used by END_OPTIONS column. Date and time when this task was last saved. Records the following values for each schedule type: 1 = Run on demand. Workflow. 20 = Run on server init and Delta schedule. 36 = Run continuously and Delta schedule. Description of the scheduler. REP_WFLOW_VAR MX View Column Name SUBJECT_ID WORKFLOW_ID VARIABLE_ID Datatype NUMBER NUMBER NUMBER Description Folder ID. Figure 15-42 lists variable information in the REP_WFLOW_VAR view: Table 15-42.

Event description. Workflow ID (primary key). Date and time that this event was last saved. Event scope. 1 = user-defined. 3 = decimal 4 = integer 5 = small integer 7 = real 8 = double 11 = date/time 12 = string Default value of a variable. 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. REP_EVENT This view displays the details of events created at the workflow or worklet level. 0 = built in. Date and time that this task was last saved. Variable type.Table 15-42. Workflow version number. 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. 2 = workflow variable is NULL. 376 Chapter 15: Using Metadata Exchange (MX) Views . Name of the event. Event ID (primary key). Event type. 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. 0 = built in. Specifies whether the workflow variable is null or persistent. Datatype of a workflow variable. 1 = user-defined. Name of the task instance. Comments on the variable. ID of the instance where the variable is defined. Table 15-43 lists event information in the REP_EVENT view: Table 15-43. 1 = workflow variable is persistent.

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

Table 15-46 lists run statistics and folder reference information in the REP_TASK_INST_RUN view: Table 15-46. Version number. Object name. The value that identifies the condition associated with the link. Start time configured for task execution. Workflow name. Condition ID. Name of the task instance. ID of the parent workflow. Run ID of the parent workflow. Folder ID. 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. Version number. Task error message.Table 15-45. 378 Chapter 15: Using Metadata Exchange (MX) Views . Run ID of a worklet in a workflow. Task ID. Run ID of a child task in a worklet. 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. Informatica recommends using the fields in bold to join views. Task error code. REP_TASK_INST_RUN This view displays the run statistics and folder reference for tasks within a workflow or worklet. End time configured for task execution. ID of an instance within a workflow or a worklet. Task type.

Table 15-46. Name of the server. Workflow. Server name. 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. Full path and name of the log file. Workflow ID. 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. Start time configured for the workflow. Table 15-47 lists workflow run statistic information in the REP_WFLOW_RUN view: Table 15-47. Workflow name. and Task Views 379 . REP_TASK_INST_RUN MX View Column Name RUN_STATUS_CODE Datatype NUMBER Description Status code of the task. Error message code. ID of the PowerCenter Server. Task version number. 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. End time configured for the workflow. REP_WFLOW_RUN This view displays the run statistics for all workflows by folder. Workflow run ID. PowerCenter Server ID.

Name of the mapping this session uses. Name of the user who ran the workflow. Specifies how the workflow was run. Version number of the session. 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. Table 15-48 lists reusable session information in the REP_LOAD_SESSIONS view: Table 15-48. 380 Chapter 15: Using Metadata Exchange (MX) Views . Informatica recommends using the fields in bold to join views. REP_LOAD_SESSIONS This view provides information about reusable sessions in the repository. Session interval. 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. Name of the session. Version number of the mapping. Status code for the workflow run. Location of the reject file. 2 = Recovery. Session start time. 1 = Normal. Folder version ID. Workflow version number. Source ID. Folder version name. Session ID. Session log file name. Folder name. Repeat count. Specifies whether the session is active. Time the session was last saved.Table 15-47.

Name of the session. 1 = valid. If a session instance overrides the connection information in a reusable session. Session ID. Worklet. 1 = target connection. this view shows the connection in the session instance and the connection information in the reusable session. 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. 0 = invalid.Table 15-48. 0 = not reusable. This view does not show connection information for reusable sessions that are not associated with any workflows. Description of the session. Informatica recommends using the fields in bold to join views. 0 = source connection. Table 15-49 lists reusable session connection information in the REP_SESSION_CNXS view: Table 15-49. 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. Name of the connection. CONNECTION_NAME CONNECTION_ID SESSION_VERSION_NUMBER VARCHAR2 (240) INTEGER NUMBER Informatica recommends using the fields in bold to join views. and Task Views 381 . Workflow. Specifies whether the session is reusable or not. Folder ID. Version number of the session. REP_SESSION_INSTANCES This view contains connection information for session instances. Specifies whether the connection is the target or the source. Connection ID. Specifies whether the session is valid or not. 1= reusable. Sequence ID for the mapping associated with the session. REP_SESSION_CNXS This view contains information about connections associated with reusable sessions.

382 Chapter 15: Using Metadata Exchange (MX) Views . Name of the session. Workflow ID. Workflow version number. Session ID. Specifies the connection type. Directory where the source or target file is stored. 1 = target connection. Session version number. REP_SESSION_FILES This view contains file connections associated with reusable sessions. 0 = source connection. 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. Specifies the connection type. 0 =source file connection. Connection ID associated with the session instance. Name of the source or target file. Informatica recommends using the fields in bold to join views. Name of the workflow the session instance belongs to. Folder ID. Name of the connection 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 instance name. Session instance ID.Table 15-50 lists session instance connection information in the REP_SESSION_INSTANCES view: Table 15-50. 1 = target file connection. Table 15-51 lists reusable session file connection information in the REP_SESSION_FILES view: Table 15-51. Version number of the session.

Name of the source or target file. The reader and writer types and the connection name also display. Workflow. Directory where the source or target file is stored. or transformation. Name of the session instance. Workflow version number. Specifies the connection type. Name of the workflow to which the session instance belongs. If a reusable session is not associated with a workflow. 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. 1 = target file connection. and Task Views 383 . REP_SESSION_INSTANCE_FILES This view contains file connection information for session instances associated with workflows. REP_SESS_WIDGET_CNXS This view contains information about the sources and targets used in a session. Worklet. Code page associated with the source or target file. 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. target. Identifies a source. or transformation.Table 15-51. 0 = source file connection. this view does not show file connection information for the session. target. Instance name. REP_SESSION_FILES MX View Column CODE_PAGE Datatype VARCHAR2 (240) Description Code page associated with the source or target file. Table 15-52 lists session instance file connection information in the REP_SESSION_INSTANCE_FILES view: Table 15-52. Table 15-53 lists connection information in the REP_SESS_WIDGET_CNXS view: Table 15-53.

Type of referenced object. Name of the value. Indicates a specific reader or writer. Session ID. Session 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. ID of a task within a session. Identifies the referred object's sequence type. Component value. Informatica recommends using the fields in bold to join views. Object type. Connection name. REP_COMPONENT This view displays the list of tasks such as a command or an email for each session. ID of the referenced object. Informatica recommends using the fields in bold to join views. Transformation instance ID referenced by a session (primary key). Workflow ID. Indicates whether the object is a reader or a writer. Session instance ID. 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. Object version number. Indicates a specific object. 384 Chapter 15: Using Metadata Exchange (MX) Views . Session instance ID. Description of the value. Figure 15-54 lists session component information in the REP_COMPONENT view: Table 15-54.Table 15-53. Session version number. 78 = reader. 79 = writer.

Workflow. Identifies a source. Session configuration attribute ID. target. Worklet. Table 15-55 lists partition information in the REP_SESS_PARTITION_DEF view: Table 15-55. Session configuration ID. REP_SESS_CONFIG_PARM This view displays session configuration parameter details. target. or transformation. Session configuration attribute type. the view displays two rows. ID of a source. Instance name. target. Session version number. targets. and transformations in a session. Select the row which contains the session ID reference. and Task Views 385 . Table 15-56 lists session configuration information in the REP_SESS_CONFIG_PARM view: Table 15-56. 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.REP_SESS_PARTITION_DEF This view provides partition details of the sources. Partition ID Partition name. Session instance ID. Description of the partition. ID of the mapping used by the session. Session version number. Object type name. 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. Informatica recommends using the fields in bold to join views. or transformation in a session. Time when the partition was last modified. or transformation. Instance ID of a source. If the session overrides a parameter in the configured object.

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

Session log file name. Number of successfully loaded target rows.REP_SESS_LOG This view provides log information about sessions. Run status code. Number of successfully read source rows. Workflow version number. Last error message. Session instance name. First error code. Number of failed target rows. Worklet. Number of failed source rows. Time completed. Folder ID. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. Version number of the task. which might contain one or many target tables. 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. 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. Session ID. and Task Views 387 . Location of the reject file. This view supplies the status of the last session. Actual time session started. 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.

Target table ID. and error status based on a last update timestamp on a per target basis. Instance ID. Informatica recommends using the fields in bold to join views. Session instance ID. It provides the last update time. Session name. Run ID of a worklet in a workflow. Business name of the target. Table 15-59 lists individual session information in the REP_SESS_TBL_LOG view: Table 15-59. Total error code. Workflow ID. Workflow version number. Workflow ID. Name of the session instance. Name of the table for this log. Session name. 388 Chapter 15: Using Metadata Exchange (MX) Views . Version number of the target. Name of the workflow that contains the session instance.Table 15-58. Session ID. row counts. Folder ID. Mapping name. Target instance name for the session. 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. 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. REP_SESS_TBL_LOG This view contains information about the status of an individual session run against a target.

Mapplet instance name. Location of the reject file. Object unique type ID. Name of the partition. Performance numbers for the target. 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. Worklet.Table 15-59. Time the target load started. Time the target load ended. Version number of the session. Object name. Workflow. and Task Views 389 . Session timestamp. Number of affected target rows Number of failed target rows. Last error code. Informatica recommends using the fields in bold to join views. Group name. Last error message. Transformation name.

User contact information. REP_USERS This view provides a list of all PowerCenter users along with details on user privileges and contact information. For more information. This view provides association details between PowerCenter users and the group to which they belong. Specifies whether the user is system-created or usercreated. 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. Description of the user. Table 15-60 lists the different views that help you analyze security metadata: Table 15-60. Table 15-61 lists user information in the REP_USERS view: Table 15-61. User name.Security Views Security views allow you to see user and group information such as privileges and contact information. 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). This view provides a list of PowerCenter groups along with details on group privileges and contact information. Privileges granted to the user. Specifies whether user can log in. 1 = enabled. see “REP_USER_GROUPS” on page 391. 1 = valid. 0 = system-created. For more information. Informatica recommends using the fields in bold to join views. 0 = deleted. Unique global user ID. 0 = disabled. Specifies whether user is valid. 390 Chapter 15: Using Metadata Exchange (MX) Views . see “REP_GROUPS” on page 391. 1 = user-created. User login ID used by external authentication modules. For more information. see “REP_USERS” on page 390.

REP_USER_GROUPS This view provides an association between PowerCenter users and the group to which they belong. 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). Table 15-63 lists group information in the REP_GROUPS view: Table 15-63. Group name. 1 = user-created. Group description. Security Views 391 . Table 15-62 lists group association information in the REP_USER_GROUPS view: Table 15-62. Group ID. CONTACT_INFO VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. 0 = system-created. Specifies whether the group is system-created or usercreated. Group privileges. 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. REP_USER_GROUPS MX View Column USER_ID GROUP_ID Datatype NUMBER NUMBER Description User ID. Contact information for the group.

Last saved time. For more information. source and target repository names associated with deployment. 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. Query user. see “REP_DEPLOY_GROUP_DETAIL” on page 393. Deployment Views View REP_DEPLOY_GROUP REP_DEPLOY_GROUP_DETAIL Description This view provides information on deployment group in Change Management. 0 = static. Name of user who created the deployment group. Description of the group. REP_DEPLOY_GROUP This view provides information on deployment groups. User ID. Query ID associated with a dynamic group. Table 15-65 lists deployment group information in the REP_DEPLOY_GROUP view: Table 15-65. Creation time. Deployment group name. 392 Chapter 15: Using Metadata Exchange (MX) Views . For more information.Deployment Views Deployment views allow you to see deployment information such as deployment groups. deployment date. Name of user who created the query. and objects which were deployed from one repository to another. This view provides Change Management deployment details. Query group ID. Query name associated with a dynamic group. 1 = dynamic. see “REP_DEPLOY_GROUP” on page 392. Query description. Deployment group type. Table 15-64 lists the different views that help you analyze deployment metadata: Table 15-64. Group ID.

1 = deploy to. 1 = public. TARGET_REP_NAME REP_GID USER_ID VARCHAR2 (240) VARCHAR2 (240) NUMBER Deployment Views 393 . 0 = invalid. Deployment user ID. Folder name in the source repository. Global ID of the repository. 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. Folder name in the target repository. Target repository name. Table 15-66 lists deployment information in the REP_DEPLOY_GROUP_DETAIL view: Table 15-66. REP_DEPLOY_GROUP_DETAIL This view provides deployment details. Object type name. Informatica recommends using the fields in bold to join views. Query last saved time. Name of the object. 0 = not a shortcut Deployment group ID. 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 start time.Table 15-65. 1 = shortcut. Folder ID in the source repository. Object version number in the target repository. Query type. Object ID. 2 = personal. Object type. 2 = deploy from. Specifies whether the object is a shortcut. Deployment group name. Deployment type. Object version number in the source repository.

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. 2 = rollback failed.Table 15-66. 0 = deployed. Deployment user name. ROLLBACK_TIME NUMBER Informatica recommends using the fields in bold to join views. Deployment status. 394 Chapter 15: Using Metadata Exchange (MX) Views . 1 = rollback. Deployment rollback time. UTC deployment time.

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. Repository type. Description of the repository. 2 = standalone. REP_REPOSIT_INFO This view provides repository information such as repository name and 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. database type. Global domain name. Table 15-67 lists repository information in the REP_REPOSIT_INFO view: Table 15-67. Repository name. Repository ID. connection information on which the repository is created. Repository type. Repository View 395 . Port number of the Repository Server. MX provides the REP_REPOSIT_INFO view to help you analyze repository metadata. Database user name used to connect to the repository. 1 = global. 3 = local.Repository View The repository view allows you to see repository name. domain name. and database type. Name of the machine hosting the Repository Server. and whether the repository is local or global.

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

Table 15-71 lists PowerCenter Server identification and usage information within the grid in the REP_SERVER_NET_REF view: Table 15-71. PowerCenter Server Views 397 . 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. Description of the server. 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). Table 15-70 lists PowerCenter Server information in the REP_SERVER_NET view: Table 15-70. Use network = 1. PowerCenter Server job distribution options. PowerCenter Server ID (primary key). Time when the server was last saved. Use network and used by network = 3. REP_SERVER_NET_REF This view provides PowerCenter Server identification within the grid and usage information. Informatica recommends using the fields in bold to join views. 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). Server name.

transformations. Table 15-73 lists label information in the REP_VERSION_PROPS view: Table 15-73. REP_VERSION_PROPS This view provides the version history of all objects in a PowerCenter repository. Object version number. 398 Chapter 15: Using Metadata Exchange (MX) Views . mappings. see “REP_VERSION_PROPS” on page 398. Name of the object. Table 15-72 lists the different views that help you analyze version history of objects and label metadata: Table 15-72. Provides information on labels in Change Management. and tasks. Labels can be defined on all objects. workflows. Object type ID (primary key). Time when object was last saved. Provides information on label details in Change Management. Objects can be defined as tables. 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. mapplets. see “REP_CM_LABEL” on page 399. For more information. Description of the object. sessions. For more information. For more information. see “REP_CM_LABEL_REF” on page 399. Database name used by source objects. User who last modified this version of the object.Change Management Views Change Management views allow you to see the version history of all objects in a PowerCenter repository and label metadata. Folder ID. UTC time when the object was last modified. 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. worklets. Object subtype ID. Host machine name from which the version of the object is saved.

2 = label locked.Table 15-73. 1 = label unlocked. Time when label was last saved. Label creation time. Label status. REP_CM_LABEL_REF This view provides information on label details. Informatica recommends using the fields in bold to join views. 2 = Can apply label to only one version of the object. Informatica recommends using the fields in bold to join views. Name of user who created the label. Object version number. User ID. Object ID. 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. Folder ID. Label name. Label type. Object type ID. 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. Table 15-74 lists label information in the REP_CM_LABEL view: Table 15-74. Label description. Change Management Views 399 . Group 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. Table 15-75 lists label information in the REP_CM_LABEL_REF view: Table 15-75.

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

Folder description. Informatica recommends using the fields in bold to join views. Folder 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 The folder view allows you to see all the folders defined in the PowerCenter repository. ID. Table 15-76 lists folder information in the REP_SUBJECT view: Table 15-76. Folder View 401 . REP_SUBJECT MX View Column SUBJECT_AREA SUBJECT_ID DESCRIPTION Datatype VARCHAR2 (240) NUMBER VARCHAR2 (2000) Description Folder name. It describes the name. and description of each folder.

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

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

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

Table 16-1 lists the native connect string syntax for each supported database when you create or update connections: Table 16-1. Overview 405 .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.world sambrown@mydatabase TeradataODBC TeradataODBC@mydatabase TeradataODBC@jsmith *Use Teradata ODBC drivers to connect to source and target databases. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.

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

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

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

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

All commands require a connection to the repository. See “Connecting to a Repository (Connect)” on page 410. Exits from pmrep. See “Cleaning up Persistent Resources (Cleanup)” on page 411. Table 16-2 lists pmrep system commands: Table 16-2. but not both. 410 Chapter 16: Using pmrep and pmrepagent . pmrep System Commands pmrep Command Connect Help Cleanup Exit Command Description Connects to the repository. 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. Connecting to a Repository (Connect) The first time you use pmrep in either command line or interactive mode. Repository user name used to connect to the repository. Use the -x or -X option. The host name of the machine running the Repository Server. but not both. Cleans up persistent resources created by pmrep during a session.pmrep System Commands This section describes basic pmrep commands that you use in conjunction with other pmrep repository and security commands. See “Getting Help (Help)” on page 411. Displays help for all commands or for a specified command. The password environment variable for the repository. you must call the Connect command. “Exiting pmrep (Exit)” on page 411. Password for the repository user name. 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. The port number the Repository Server uses for connections. Use the -x or -X option.

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

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

parse the metadata. you can use ListObjects to list all Sequence Generator transformations in the repository. Use the -a or -A option. Tip: When you specify characters to separate records and columns and to indicate the end of the listing. parse the data ListObjects returns. The command might fail for the following reasons: ♦ ♦ ♦ You did not give the repository name in the argument.Table 16-14. You can specify the character or characters to use to separate records and columns. pmrep returns each object in a record and returns each object metadata in a column. When you list objects. This helps you use a shell script to parse the object metadata. you do not need read permission on the folders. 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. You can use ListObjects in a shell script to return the object metadata. You must connect to a repository to use this command. 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. pmrep Repository Commands 423 . It separates records by a new line by default. and then use the parsed data in another pmrep command. Name of the repository to enable. Create a shell script that uses ListObjects to return Sequence Generator transformation information. and use Updateseqgenvals to update the sequence values. To list objects. -r The command returns an “enablerepository completed successfully” or returns “Failed to execute enablerepository” message. For example. use characters that are not used in repository object names. Listing Repository Objects (ListObjects) The ListObjects command returns objects in the repository. You can also specify the character or characters to indicate the end of the listing. but not both. The Repository Server failed to enable the repository because the repository is not currently disabled. pmrep returns object metadata to the screen.

List labels in the repository. including shortcuts but excluding target instances. 424 Chapter 16: Using pmrep and pmrepagent .You can use the object_type option to define the objects you want to list. folder. List the session configurations with latest or checked out version in a folder. List mappings with latest or checked out version in a folder. The deploymentgroup. Folder. Mapplet. including shortcuts but excluding instances of reusable mapplets. List targets with latest or checked out version in a folder. The command lists the latest versions or checked out versions of objects. List reusable and non-reusable transformations with latest or checked out version in a folder. label. Task. ♦ ♦ 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. Source. List queries in the repository. Mapping. List reusable and non-reusable sessions with latest or checked out version in a folder. Workflow. List sources with latest or checked out version in a folder. including shortcuts. All other object types require the -f option. Scheduler. List reusable and non-reusable schedulers with latest or checked out version in a folder. but excluding objects according to the following rules for each object type: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Deploymentgroup. List deployment groups in the repository. including shortcuts and excluding instances of reusable transformations. Transformation. Query. List folders in the repository Label. excluding instances of reusable worklets. List mapplets with latest or checked out version in a folder. List reusable and non-reusable worklets with latest version or checked out version in a folder. Target. Sessionconfig. Worklet. List the workflows with latest version or checked out version in a folder. and query object types are not associated with folders. Session. including shortcuts but excluding instances of reusable mapplets. List reusable and non-reusable tasks with latest or checked out version in a folder. excluding instances of reusable sessions. including shortcuts but excluding source instances.

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

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 lists the transformation types and values to use with pmrep commands: Table 16-16.

pmrep does not include instances of reusable objects. to list all Stored Procedure transformations in a folder. 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. to list all transformation types in a folder. For a list of transformation or task return values. pmrep returns mapping_name. Or.sp_nsproc sequence non-reusable smallmapplet. to list all folders in the repository.transformation_name. For example. 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 ignores the subtype and folder name. when a transformation is in a mapping or mapplet.seqgen_empid .Table 16-16. enter the following text at the pmrep> prompt: listobjects -o folder Or.transformation_name or mapplet_name. When you list objects. For example.listobjects completed successfully. pmrep returns the name of the object with the path when applicable. 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. see Table 16-16 on page 426. 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. you must include the folder name for all objects that are associated with a folder.sp_nsproc pmrep Repository Commands 427 . When you specify folder for the object type.

wl_shirt_orders. 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. 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.source_name You must connect to a repository to use this command. enter the workflow name and the session name as workflow_name. You can specify a reusable or non-reusable session. To list sources or targets.session_name. When you list sources or targets. To list all sessions in a folder. you can create a shell script that uses Listtablesbysess to return source instance names and uses Updatesrcprefix to update the source owner name. if the mapping contains a mapplet with a source. pmrep returns source or target instance names to the screen.s_sales_Q3 session non-reusable wf_orders. For example. pmrep returns source and target instance names as they appear in the session properties. However. -t Required table_type 428 Chapter 16: Using pmrep and pmrepagent ..listobjects completed successfully. Specify source to list sources. You can use Listtablesbysess in a shell script with other pmrep commands. When you use Listtablesbysess. pmrep returns the source instance name in the following format: mapplet_name.listobjects completed successfully. To specify a non-reusable session in a workflow. Listing Tables by Session (Listtablesbysess) The Listtablesbysess command returns sources or targets used in a session. you cannot specify an instance of a reusable session. The name of the session containing the sources or targets. or specify target to list targets.s_shirt_orders . For example. 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.

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 . If you want to list dependencies for non-reusable objects. To list object dependencies. Listing Object Dependencies (ListObjectDependencies) Use the ListObjectDependencies command list dependency objects for reusable and nonreusable objects. or Validate pmrep commands.s_nrsess1 -t target pmrep returns the following information: target1_inst ORDERS_BY_CUSTID Shortcut_To_tgt2_inst listtablesbysess completed successfully. For example. see “Using the Persistent Input File” on page 494. Note: ListObjectDependencies accepts a persistent input file and it can create a persistent output file. For more information on using a persistent input file. You can create this file by running a query and choosing to create a text file. such as mapplet1. enter the following text at the pmrep> prompt: listtablesbysess -f myfolder -s s_reus_sess1 -t source pmrep returns the following information: ITEMS mapplet1.ORDERS Shortcut_To_ITEM_ID listtablesbysess completed successfully. pmrep includes the mapplet name with the source. you can use it as input to the ApplyLabel. If you create an output file. ListObjectDependencies returns the number of records if the command runs successfully.For example. you must use a persistent input file containing object IDs. AddToDeployment Group. to list all sources in a reusable session. you can list all targets in a non-reusable session in a workflow: listtablesbysess -f myfolder -s wf_workkflow1. These files are the same format. Note: When the mapping contains a mapplet with a source.ORDERS.

task. The type of dependent objects to list.parentobject_name. You can specify ALL or one or more object types. To specify multiple objects. session. -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 . Required if you do not use the -p option. Send the dependency result to a text file. Ignored for other object types. The text file of objects generated from ExecuteQuery or Validate commands. transformation. For valid subtypes. children. cube. scheduler.Note: ListObjectDependencies displays non-reusable objects as parent. You must use this file if you want to list dependencies for non-reusable objects. AddToDeployment Group. The object type to list dependencies for.nonreusableobject_name. worklet. then pmrep lists all supported dependent objects. and dimension. You can use the text file as input to the ApplyLabel. -f options to specify objects. You can specify parents. 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. session config. see Table 16-16 on page 426. The folder containing object_name. workflow. separate them by commas without spaces. Append the result to the persistent output file name file instead of overwriting it. mapping. see “Using the Persistent Input File” on page 494. Find object dependencies across repositories. session. or both. or Validate pmrep commands. Table 16-18 lists pmrep ListObjectDependencies options and arguments: Table 16-18. If ALL. If you choose one or more objects. List dependent objects for an object version other than the latest version. You can specify source. The default is ALL. For more information on using the persistent input file. The type of transformation or task. -o. The default sends the query result to stdout. then pmrep lists dependent objects only for these types. then you cannot use the -n. Folder is required if object type is not a folder and you are not using the -i option. Include the primary key-foreign key dependency object regardless of the direction of the dependency. The parents or children dependent objects to list. If you use this option. Required if you do not use the -s option. target.

The character or set of characters used to specify the end of the object list. If any repository object name contains spaces. Specify a character or set of characters that is not used in repository object names. Use a character or set of characters that is not used in repository object names. pmrep Repository Commands 431 . pmrep uses a period. you might want to avoid using a space as a column separator. The short format for versioning objects.Table 16-18. pmrep prints a shorter format including the object type. the object name and path. Use a character or set of characters that is not used in repository object names. pmrep uses a single space. If you omit this option. The character or set of characters used to specify the end of the object metadata. If you omit this option. -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 must have Administer Repository privilege. query. The number of the port where the Repository Server is running. the word reusable or nonreusable. deployment group. Verbose format includes the creator name and creation time. such as label. includes the object type and object name. If you omit this option. and connection. 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. To send notification messages. 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 default is newline /n. Verbose format includes the version number and folder name. Print more than the minimum information about the objects.

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

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

Note: The ObjectImport command does not automatically create a folder if the folder you specify does not exist in the repository. but not both. Use the -x or -X option. 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. The login password environment variable for the local target repository. The name of the control file that defines import options. The password you use to administer the global Repository Server. 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 -a or -A option. The login password for the local target repository. The local repository user name. you must have Administer Repository privilege. Use the -x or -X option. but not both. -a 434 Chapter 16: Using pmrep and pmrepagent . Registering Local Repositories (Register) Use the Register command to register a local repository with a connected global 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. 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. but not both. You must connect to the global repository before you register the local repository. To register a local repository.

Use the -a or -A option. If you use this option. The number of the port where the Repository Server is running. Use the -a or -A option. The hostname of the local repository. 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. If you use this option. 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 Repository Server failed to initialize information about the global repository. Use this option when the local repository is managed by a different Repository Server. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The login password for the repository. you must use the -o option as well. -h -o Optional local_repository_port_numb er The command returns “register successfully completed” or returns “failed to execute register” message. pmrep Repository Commands 435 . Removing Repositories From the Cache (Removerepository) The Removerepository command removes repositories from the Repository Server cache entry list.Table 16-22. Use this option when the local repository is managed by a different Repository Server. The Repository Server failed to register the local repository with the global repository. 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. You failed to connect to the Repository Server. but not both. but not both. you must use the -h option as well. The port number of the Repository Server.

The name of the output file. All repository users can run script files. The name of the repository to remove. The commands are echoed back to the script. 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. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. You failed to connect to the Repository Server. Stops the running of the script after a command returns an error. -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. 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.Table 16-23. but not both. The run might fail if the Repository Server cannot open the script file or output file. 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. Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. This option writes all messages generated by the commands in the script file into the output file. 436 Chapter 16: Using pmrep and pmrepagent . Use the -a or -A option.

server. When you connect to a repository in interactive mode. -o. pmrep Repository Commands 437 . and user information for the current connection. 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. and -r options. the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. You must be connected to a repository to use this command. pmrep does not keep connection information in command line mode. see “Connecting to a Repository (Connect)” on page 410. The ShowConnectioninfo command does not connect to the repository.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. the repository that you last connected to stops. However. port. When you use the StopRepository command. ShowConnectioninfo requires no parameters. When you use the ShowConnectioninfo command in command line mode. For example. StopRepository stops the repository you last connected to. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. For more information about connections in command line mode and interactive mode. the named repository stops. pmrep connects to the Repository Server and stops the Repository Agent. if you do not specify a repository. 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. a message indicating failure to execute the command is given. Otherwise.

The name of the repository to stop. When you use this option. The password environment variable you use to administer the Repository Server that manages the repository. you have a relational and an application source. 438 Chapter 16: Using pmrep and pmrepagent . The Repository Server port number. 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. you must also use the -h and -o options. When you use this option. you must also use the -h and -r options. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. Use the -a or -A option. you must also use the -o and -r options. but not both. -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. Use the -a or -A option. but not both. pmrep does not replace any relational connection in the repository because it cannot determine the connection type for the source connection entered as ITEMS. In a session. the Repository Server replaces the relational connection.Table 16-25 lists pmrep StopRepository option and argument: Table 16-25. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection. each called ITEMS. The hostname of the Repository Server that manages the repository to stop. For example. When you use this option. When you use SwitchConnection. 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. You must be connected to a repository to use this command.

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

Use the -x or -X option. The local repository user name.The command returns “truncatelog completed successfully” or returns “Failed to execute truncatelog” message. The truncation might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The workflow does not exist in the given folder. Use the -x or -X option. The password environment variable you use to administer the global Repository Server. but not both. 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 must connect to the global repository before you unregister the local repository. Unregistering Local Repositories (Unregister) Use the Unregister command to unregister a local repository from a connected global repository. The folder name is invalid. To unregister a local repository. but not both. The login password environment variable for the local target repository. 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. The password you use to administer the global Repository Server. The login password for the local target repository. Use the -a or -A option. you must have Administer Repository privilege. but not both. -a -A global_repserver_password_ environment_variable 440 Chapter 16: Using pmrep and pmrepagent . You specified a workflow. Use the -a or -A option. but not both. but no folder name.

The Repository Server failed to unregister the local repository to the global repository. Use this option when the local repository is managed by a different Repository Server. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The connection object does not exist. pmrep cannot acquire a lock on the object. 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. A failure might occur for the following reasons: ♦ ♦ ♦ ♦ ♦ The database type is not supported. Unregister Options and Arguments (pmrep) Option -h Required/ Optional Optional Argument Name local_repository_host_name Argument Description The hostname of the local repository. If you use this option. You failed to connect to the Repository Server. 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 . Updating a Database Connection (UpdateConnection) The UpdateConnection command updates the user name.Table 16-28. you must use the -h option as well. Use this option when the local repository is managed by a different Repository Server. The current user does not have the appropriate permissions. and attributes for a database connection. If you use this option. 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. The number of the port where the Repository Server is running. password. To update a connection. you must use the -o option as well. connect string. One of the required parameters is missing.

The name of the attribute. The new attribute value of the connection. but not both. The password used for authentication when you connect to the relational database.Table 16-29 lists pmrep UpdateConnection options and arguments: Table 16-29. For a list of valid database types. The user name used for authentication when you connect to the relational database. see Table 16-9 on page 418. 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. You can specify different addresses to receive either success or failure notifications. This command requires you to connect to a repository. Use the -p or -P option. If you did not previously specify a success or failure Email task for the session. The database connection name. 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 . The password environment variable used for authentication when you connect to the relational database. the command does not update the email addresses. but not both. -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. Use the -p or -P option. You can update the email notification addresses only for a non-reusable session with a unique name in the folder. see Table 16-1 on page 405. Enter “yes” or “no” for attributes you enable through a checkbox. For a list of native connect strings. The connect string the PowerCenter Server uses to connect to the relational database.

Select the code page identical to the PowerCenter Server operating system code page. The character set associated with the PowerCenter Server. you must have the Administer Repository privilege. Only the values that you specify update. Name of the session. For more information about PowerCenter Server details see “Registering the PowerCenter Server” in the Installation and Configuration Guide. The new name of the PowerCenter Server. Must be identical to or compatible with the repository code page. The number of seconds the Workflow Manager waits for a response from 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.Table 16-30 lists pmrep Updateemailaddr options and arguments: Table 16-30. The port number the PowerCenter Server. Email address to send session failure notifications. 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. The server host name or IP address of the server machine. 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. pmrep Repository Commands 443 . Updating Server Details (Updateserver) The Updateserver command updates PowerCenter Server details with the values that you specify in the command. Email address to send session success notifications. To update server details. The protocol the PowerCenter Server uses.

The mapping name. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . However. When you update values for a nonreusable Sequence Generator transformation.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 connect to a repository to use this command. You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. For more information on configuring Sequence Generator transformations. you must include the mapping name. see “Sequence Generator Transformation” in the Transformation Guide. To update sequence values. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations. 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. 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. The Sequence Generator transformation name.

the current value must be greater than or equal to the start value and less than the end value. If you designate an invalid value. pmrep gives an error message and does not update the Sequence Generator transformation.Table 16-32. 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 . -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. If you designate an invalid value. If you select Cycle in the transformation properties. Enter the value you want the PowerCenter Server to use as the first value in the sequence. If you designate an invalid value. the PowerCenter Server cycles back to this value when it reaches the end value. If you want to cycle through a series of values. pmrep gives an error message and does not update the Sequence Generator transformation. The maximum value the PowerCenter Server generates. 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. it fails the session. The difference between two consecutive values from the NEXTVAL port. If the PowerCenter Server reaches this value during the session and the sequence is not configured to cycle. 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. Updatesrcprefix updates the owner name for source tables at the session level. To update source table owner names. The current value of the sequence. You can update the owner name for one or all sources in a session. You must connect to a repository to use this command.

enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command.When you include the -n option. pmrep updates all source table owner names in the session. You can find the source dbd name in the Designer Navigator. such as worklet_name.When you omit the -n option. The name of the session containing the sources to update. If you omit this option. pmrep matches the source_name argument with the source table names. The name of the source to update. You cannot change default server variables. For non-reusable sessions. This command requires you to connect to a 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. but you can change the case of the default server variables. you must enter the dbd name and the source table name as dbd_name. see “Configuring the Workflow Manager” in the Workflow Administration Guide. For a list of server variables. When you do not include this option.source_name. The Designer generates the dbd name from the source type or data source name when you create a source definition in the repository. For reusable sessions. You can update any of the PowerCenter Server variables using Updatesrvvar.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. . pmrep matches the source_name argument with source instance names. Updatesrvvar uses the following command syntax: updatesrvvar -s server_name -v variable_name -u new_value 446 Chapter 16: Using pmrep and pmrepagent . specify session_name. When you include this option. 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.session_name or workflow_name. . This option has no argument. Informatica recommends you include the -n option. The owner name you want to update in the source table.session_name. you must also specify the session path.

For more information about updating statistics. Updating Repository Statistics (UpdateStatistics) The UpdateStatistics command updates statistics for repository tables and indexes. 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. The table name prefix specifies the owner of the table in the database. The command returns “updatestatistics successfully completed” or returns “updatestatistics failed” message. You can update the owner name for one or all targets specified in a session. Value of updated server variable.Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34. pmrep updates table name prefixes if you previously edited the table name prefix at the session level. Name of the server variable to update. pmrep Repository Commands 447 . 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 must have Administer Repository privilege. 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. The update fails if you do not have Administer Repository privilege. Updatetargprefix updates the target table name prefix at the session level. Updating the Target Table Name Prefix (Updatetargprefix) Use the Updatetargprefix command to update the table name prefix for session target tables. You must connect to a repository to use this command. see “Updating Repository Statistics” on page 60. To update repository statistics.

Informatica recommends you include the -n option. When you include this option. The name of the target to update. This option has no argument. specify session_name. If you omit this option. pmrep updates all target table name prefixes in the session. The name of the session containing the targets to update. When you include the -n option. you must enter the target table name instead of the target instance name. When you do not include this option. pmrep matches the target_name argument with the target table names. enter the name of the target instance as displayed in the session properties or as output by the Listtablesbysess command. such as worklet_name. The table name prefix you want to update in the target table. pmrep matches the target_name argument with target instance names. 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.To update target table name prefixes. 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. -t Optional target_name -p -n Required Optional prefix_name n/a 448 Chapter 16: Using pmrep and pmrepagent . When you omit the -n option. you must also specify the session path.session_name. For non-reusable sessions.session_name or workflow_name. For reusable sessions.

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

you cannot use the -g option. all users in the group inherit the privilege. you must enclose this argument in quotes. The name of the group to which you want to add the user. Note: You cannot use this command with an external security module. You must be connected to the repository to use this command.” The name of the user to whom you want to add the privilege. 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. You must connect to the repository to use this command. It cannot add a privilege to a user and a group at the same time. If you use this option. you cannot use the -u option. use the following syntax: addusertogroup -u username -g group_name Table 16-39 lists pmrep Addusertogroup options and arguments: Table 16-39. -u -g Required Required username group_name Adding a User to a Group (Addusertogroup) The Addusertogroup commands adds an existing user to a group. To add a privilege to a user or a group. 450 Chapter 16: Using pmrep and pmrepagent . If the privilege contains spaces. To add a user to a group. such as “Administer Repository. Addprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to add. If you use this option. use the following syntax: addprivilege -p privilege -u username -g group_name Table 16-38 lists pmrep Addprivilege options and arguments: Table 16-38. The user inherits all of the permissions and privileges associated with the group. If you add a privilege to a group. The name of the group to which you want to add the privilege. Changing the Repository Password (Changepasswd) The Changepasswd command changes the password of the user currently connected to the repository. 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 selected. This option confirms the new password. The password environment variable that replaces the existing password for the current user. you must have Administer Repository privilege. 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. makes the folder shared. If not specified. 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. -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. do not use the -c option. Access rights for the folder. but not both. Description of the folder that appears in the Repository Manager. The confirm_new_password argument must match the new_password argument. The owner of the folder. Any user in the repository can be the folder owner. Repository Server assigns default permissions. 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. but not both. Use the -p or -P option. When you use this option. Repository user group to receive Owner’s Group permissions. Only groups to which the owner belongs can be selected.To change the password of the user connected to the repository. you must use the -c option. To run CreateFolder. pmrep Security Commands 451 . 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. When you use this option. You must use this option when you use the -p option. The default owner is the user creating the folder. Use the -p or -P option.

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

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

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

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

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

the user is assigned to Public.The command returns “ModifyFolder successfully completed” or returns “ModifyFolder Failed” message. the privilege changes take effect the next time the user connects to the repository. Assigns the user to a group. Contact information about the user. users in the group lose the privileges inherited from the group. The new owner does not exist or does not belong to the group. When you remove a group. If you omit this option. Use this command if you use LDAP to authenticate repository users. 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 modification might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have the appropriate privilege. To remove a group. A description of the user. use the following syntax: rmgroup -g group_name pmrep Security Commands 457 . Note: You cannot remove the Public or Administrators group. 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. 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. 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. A folder with the new folder name already exists. The folder does not exist. The login name in the external directory. You must connect to the repository to use this command. If any user in the group is connected to the repository when you remove the group.

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

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

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

session. You cannot add checked out objects to a deployment group. For valid subtypes. task. The name of the object you are adding to the deployment group. and task objects. If AddToDeploymentGroup runs successfully. transformation. you must use a persistent input file that contains encoded object IDs. target. To add objects to a deployment group. you can specify only the deployment group name option. it either sends back no status information. or it returns a list of objects that already are in the deployment group. 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. For more information on adding to a deployment group. workflow. target. For more information on using a persistent input file. mapping. worklet. Required when adding a specific object. You cannot specify a checked out object. You can specify source. If the command fails. and dimension. You cannot specify an object if you use the -i option. Use AddToDeployment Group to add reusable input objects. scheduler. transformation. The type of object you are adding. The type of task or transformation you are adding. worklet. mapping. -o Required/ Optional object_type -t Required/ Optional object_subtype pmrep Change Management Commands 461 . see “Working with Deployment Groups” on page 236. session configuration. it displays the reason for failure. 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. You can specify objects using command options or you can use a persistent input file. You must use this parameter when you add a specific object. Use AddToDeploymentGroup to add source. see Table 16-16 on page 426. If you use a persistent input file. session. If you want to add non-reusable input objects. scheduler. see “Using the Persistent Input File” on page 494.Adding to a Deployment Group (AddToDeploymentGroup) The AddToDeploymentGroup command adds objects to a deployment group. cube. session configuration. workflow.

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

You can specify source. then this parameter is required. both. ListObjectDependency. target. see “Using the Persistent Input File” on page 494. If you use this option. If you specify a folder. or Validate. You can specify parents. If you are updating a specific object. object type. Required when applying a label to a specific object. then do not use the object name. The folder that contains the object(s). pmrep searches the folder for the object. If you specify an object type. The dependent parents or children to apply the label to. -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 . worklet. The command fails if the version is checked out. If you do not specify option -d. transformation. workflow. Contains a list of objects to receive the label. or dimension. The kind of task or transformation you are labeling. You cannot specify objects if you use the -i option. You cannot specify a folder if you use the -i option. scheduler. pmrep applies the label to all objects in the folder. If you do not specify this option. then the label applies to dependent objects of that object type. cube. Use this option with option -p. The type of object to apply the label to. The dependent objects to label. all dependent objects receive the label. but no object name. children. task. For valid subtypes. the label applies only to the specified object.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. see Table 16-16 on page 426. The name of a text file generated from ExecuteQuery. mapping. pmrep ignores other object types. session. The version of the object to apply the label to. or folder name to specify objects. The name of the object to receive the label. 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. For more information on using the persistent input file. If you specify a folder with an object name. Applies the label to the latest version of the object by default. session config.

scheduler. cube. -c Optional comments Checking In Objects (Checkin) Use the Checkin command to check in an object that you have checked out previously. workflow. When you check in an object. session config. the repository creates a new version of the object and assigns it a version number. Not required for other object types. 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. or dimension. You can use this argument only when the label type is one_per_object. The folder to contain the new object version. 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.Table 16-54. The version number is one number greater than the version number of the last checked-in version. Move a label from the current version to the latest version of an object. To check in objects. The type of task or transformation to check in. see Table 16-16 on page 426. target. For more information on checking in objects. 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. mapping. task. worklet. transformation. The name of the object that you are checking in. See “Creating a Label (CreateLabel)” on page 466. -t Optional object_subtype -n -f -c Required Required Optional object_name folder_name comments 464 Chapter 16: Using pmrep and pmrepagent . For valid subtypes. see “Checking In Objects” on page 213. session. Comments about the check in. Comments relating to ApplyLabel. Table 16-55 lists pmrep Checkin options and arguments: Table 16-55.

For more information on creating deployment groups. Create a static group or use a query to dynamically create the group. Remove objects without confirmation. you must have the Use Repository Manager privilege. You can use this command to retain the deployment group but remove the objects. To create a deployment group. you must supply a query name. see “Working with Deployment Groups” on page 236. 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. If you omit this argument. and indicate whether the query is private or public. Default is static. pmrep Change Management Commands 465 . the command prompts you for a confirmation before it clears the objects. You can specify static or dynamic. You can create a dynamic or static deployment group. To create a dynamic deployment group. 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. To clear a deployment group. 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. Creating a Deployment Group (CreateDeploymentGroup) Use the CreateDeploymentGroup command to create a deployment group.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.

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. see “Working with Deployment Groups” on page 236. The type of query to create a deployment group.Table 16-57. 466 Chapter 16: Using pmrep and pmrepagent . but ignored if the group is static. You can specify shared or personal. see “Creating and Editing Labels” on page 219. you can specify that the label can apply to multiple versions of an object (one per version). Required if the deployment group is dynamic. If you delete a static deployment group. If you omit this option. For more information on deleting deployment groups. Comments about the label. You can associate a label with any versioned object or group of objects in a repository. Allows multiple versions to have this label. To create a label. but ignored if the group is static. Required if the deployment group is dynamic. 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. For more information on creating labels. 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. or you can specify that a label can apply to only one version of an object (one per object). you must have the Administer Repository privilege. you also remove all objects from the deployment group. -c Optional n/a Deleting a Deployment Group (DeleteDeploymentGroup) Use the DeleteDeploymentGroup command to delete a deployment group. -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. Comments about the new deployment group. you can apply the label to only one version.

If you omit this argument. Delete the label without confirmation.To delete a deployment group. pmrep prompts you for a confirmation before it deletes the Deployment Group. To delete a label. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Write permission on the label For more information about deleting labels. 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. 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. see “Working with Labels” on page 219. the command prompts you for a confirmation before it deletes the label. If the label is locked. Deploying a Deployment Group (DeployDeploymentGroup) Use the DeployDeploymentGroup command to deploy a deployment group. the delete fails. If you omit this argument. 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. Deletes the Deployment Group without confirmation. You can optionally use this command to copy deployment groups to different repositories. Deleting a Label (DeleteLabel) Use the DeleteLabel command to delete a label and remove the label from all objects that use it. 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. pmrep Change Management Commands 467 .

The control file is required. see “Copying a Deployment Group” on page 254. Use the -x or -X option. For more details about the control file. For more information on deploying a deployment group. The login password environment variable for the target repository. Not required if you copy the deployment group to the same repository. see “Using the Deployment Control File” on page 504. The login password for the target repository. see “Using the Deployment Control File” on page 504. The login user name for the target repository. Use the -x or -X option. The control file is an XML file defined by the depcntl. For more information on using the control file. The host name of the Repository Server managing the target repository.dtd file. 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. The repository you are deploying the group to. Not required if you copy the deployment group to the same repository. but not both. Not required if you copy the deployment group to the same 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. but not both. To copy a deployment group. -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 . Not required if you are copying the deployment group to the same repository. 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.To use this command.

see “Using the Deployment Control File” on page 504. see “Using the Deployment Control File” on page 504. Use the -x or -X option. The repository name to deploy the group to. Not required if the target repository is the same as the source. 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. For more information on the control file. but not both. The login password for the target repository. It requires a control file containing specifications that the Copy Wizard requires. Not required if you are copying the deployment group to the same repository. it outputs to the screen. 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. If you omit this option. Not required if you are copying the deployment group to the same repository. -r Optional target_repository_name -u Optional target_repository_user_name -x Required/ Optional target_repository_user_passwo rd pmrep Change Management Commands 469 . The name of the XML file containing the copy wizard specifications. To copy a folder. The login user name for the target repository. -l Deploying a Folder (DeployFolder) The DeployFolder command allows you to deploy a folder. The log file that records each deployment step. The control file is an XML file defined by the depcntl. For more details about the control file.dtd file. 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.Table 16-61.

Table 16-62. but not both. To execute a query. Not required if you copy the deployment group to the same repository. and Validate commands. Use the -x or -X option. Not required if you are copying the deployment group to the same repository. The type of query to run. The port number of the Repository Server. 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. Not required if you copy the deployment group to the same repository. Then it searches the public queries. If not specified. You can specify public or private. You can use this file as input to the ApplyLabel. AddToDeploymentGroup. You can choose to display the result or write the result to a persistent input file. 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. see “Using the Persistent Input File” on page 494. 470 Chapter 16: Using pmrep and pmrepagent . For more details on using a persistent input file. The host name of the Repository Server managing the target repository. 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. 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. The log file that records each deployment step. If the query is successful. it returns the total number of qualifying records. If you omit this option. pmrep searches all the private queries first to find the matching query name.

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

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

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

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

dimension. task. Validate. session config. session. saved. The type of task or transformation. scheduler. Required if you use -s. 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. Do not use this option if you are using the -i argument. Contains a list of object records. workflow. For valid subtypes.To validate objects. save_failed. or -f arguments. cube. target. or invalid_after. see Table 16-16 on page 426. You cannot use this file if you are specifying objects using the -n. Save objects that change from invalid to valid to the repository. Add comments when you check in an object. worklet. invalid_before. You can specify source. 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. The text file from ExecuteQuery. Required if you use the -k option. mapping. -o. transformation. The name of the folder containing the object. The type of object to validate. Required if you are not using a persistent input file. or ListObjectDependencies commands. You can specify valid. skipped. separate them by commas. and the current repository requires checkin comments. To specify one or more options. -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 . Check in saved objects. The version of the object to validate. Ignored for other object types. The default is the latest or checked out version of the object. You should specify output_options when you use the persistent_output_file_name. The kind of object you want to output to the persistent output file or stdout after validation.

If any repository object name contains spaces. you might want to avoid using a space as a column separator. Print more than the minimum information about the objects. 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. If you omit this option. -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 . The default is newline /n. Verbose format includes the creator name and creation time.Table 16-66. query. pmrep uses a period. The short format for versioning objects such as label. pmrep prints a shorter format including the object type. pmrep uses a single space. includes the object type and object name. The character or set of characters used to specify the end of the object metadata. the word reusable or non-reusable. The character or set of characters used to specify the end of the object list. You should also specify output_options. If you omit this option. the object name and path. If you specify a file name. If you omit this option. The character or set of characters used to separate object metadata columns. and connection. Verbose format includes the version number and folder name. deployment group. the query writes the results to a file. Specify a character or set of characters that is not used in repository object names. Use a character or set of characters that is not used in repository object names. 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.

See “Deleting a Repository (Delete)” on page 481. to perform repository functions such as restoring and deleting repositories. See “Backing up a Repository (Backup)” on page 477. Restores a repository from a repository backup file. Unregisters a plug-in module from the repository. pmrepagent runs in command line mode only. Backing up a Repository (Backup) The Backup command backs up a repository to the file specified with the -o option. 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 . Specify pmrepagent options and arguments the same way you specify pmrep options and arguments.pmrepagent Commands You can use the Repository Agent command line program. Registers a new external module to the repository. Creates repository tables in the database. switch to the Repository Server \bin directory and enter pmrepagent followed by the command name and its required options and arguments. pmrepagent. Use this command when the repository is not running. Restores a Teradata repository from a repository backup file using Fastload. See “Unregistering Plug-ins (Unregisterplugin)” on page 487. See “Restoring a Repository (Restore)” on page 485. Table 16-67 describes pmrepagent commands: Table 16-67. See “Creating a Repository (Create)” on page 480. See “Upgrading a Repository (Upgrade)” on page 490. Deletes the repository tables from the database. You must provide the backup filename. See “Registering a Plug-in (Registerplugin)” on page 482. To run pmrepagent commands. pmrepagent Commands pmrepagent Command Backup Bulkrestore Create Delete Registerplugin Restore Unregisterplugin Upgrade Command Description Backs up a repository. See “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Upgrades an existing repository to the latest version.

but not both. For a list of connect string syntax. The repository database password. The repository database password. For details. Use the -p or -P option. but not both. Use the -p or -P option. Not required if you are using option -m. Use the -x or -X option. The type of database the repository resides on. 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. see “Backing up a Repository (Backup)” on page 416. This option has no argument. -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. The repository user name. Skips deployment group history during backup. The description of the repository you backup. The name and path of the file for the repository backup. see Table 16-1 on page 405. Include this option if you want to overwrite any existing file with the same name. You can use the pmrep Backup command when the repository is running. but not both. The connect string the Repository Agent uses to connect to the repository database. Skips tables related to workflow and session logs during backup. The repository password. The repository database user name. but not both.Table 16-68 lists pmrepagent Backup options and arguments: Table 16-68. Valid for Microsoft SQL Server only. Skips tables related to MX data during backup. Use a trusted connection to connect to the database. Use the -x or -X option. The repository password environment variable. 478 Chapter 16: Using pmrep and pmrepagent .

see Table 16-1 on page 405. The host name of the Repository Server that manages the repository. Use the -p or -P option. but not both. If you do not specify a path. Use this option if you want to promote the repository to a global repository. The name of the repository backup file. but not both. This option has no argument. The repository code page. The repository database password environment variable. Use the -p or -P option. The repository database user name. The name of the Teradata database server. The repository database password. The connect string the Repository Agent uses to connect to the repository database.Restoring Teradata Repositories using Fastload (Bulkrestore) The pmrepagent Bulkrestore command restores Teradata repositories using Fastload. The port number of the Repository Server that manages the repository. -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 . You can specify any file name and path local to the Repository Server. Enter “Teradata” to restore to a Teradata database. the Repository Server looks for the file in the Repository Server backup directory. For a list of connect string syntax. The Bulkrestore command can be faster than the Restore command when the repository backup file is greater than 100 MB. 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. 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. Enter “fastload” for Teradata.

but not both. Skips deployment group history during backup. The repository database user name. see “Creating a Repository” on page 116. Skips tables related to MX data during backup. -P database_password_environme nt_variable n/a database_connect_string -m -c 480 Chapter 16: Using pmrep and pmrepagent . Valid for Microsoft SQL Server only. 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. The repository database password. Use a trusted connection to connect to the database. see Table 16-1 on page 405. Use the -p or -P option. 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. Before you can create a repository. Creating a Repository (Create) The pmrepagent Create command creates a repository in the database. you must create and configure the database to contain the repository. Skips tables related to workflow and session logs during backup. For a list of connect string syntax. The connect string the Repository Agent uses to connect to the repository database. For more information on creating repositories. Not required if you are using option -m. 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. but not both. The repository database password environment variable. Enables object versioning. Not required if you are using option -m.Table 16-69. The type of database the repository resides on. Use the -p or -P option.

pmrepagent interprets the spaces as part of the tablespace name. The repository user name. The repository password environment variable. 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. see “Deleting a Repository” on page 64. Include this option if you want to enables object versioning for the repository. but not both. -a -v Required Optional license_file_name n/a The name of the license file. This option has no argument. but not both. Use this option to specify the tablespace name for IBM DB2 EEE databases. Include this option if you want to promote the repository to a global repository. Deleting a Repository (Delete) The pmrepagent Delete command deletes the repository tables from the repository database. The port number of the Repository Server that manages the repository. 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. For more information about deleting a repository.Table 16-70. The host name of the Repository Server that manages the repository. This option has no argument. Use the -x or -X option. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” Do not include spaces around the equals sign. The repository password. pmrepagent Commands 481 . 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. Use the -x or -X option.

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. but not both. -f Required/ Optional n/a Registering a Plug-in (Registerplugin) The pmrepagent Registerplugin command registers an external plug-in to a repository. Registering a plug-in adds its functionality to the repository. Use the -x or -X option. The repository password. Use this option to delete a global repository. For more information about registering a plug-in. You can use the Registerplugin command to update existing plug-ins. The connect string the Repository Agent uses to connect to the repository database. The repository database password. but not both. Use the -x or -X option. 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. 482 Chapter 16: Using pmrep and pmrepagent . The repository database user name. see “Registering a Repository Plug-in” on page 85. see Table 16-1 on page 405. The repository password environment variable. The repository database password environment variable. Use the -p or -P option. For a list of connect string syntax. but not both. Use the -p or -P option. 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. This option unregisters local repositories. The repository user name.Table 16-71. All registered local repositories must be running. 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. Use the -p or -P option. but not both. Do not use this option for other plug-ins. The external directory password of the user registering the module. -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 . This login becomes the administrator user name in the repository. Indicates to use a trusted connection to connect to the database. it generates an error. The repository database password. but not both.Table 16-72. If the plug-in exists. Do not use this option for other plug-ins. Valid for Microsoft SQL Server only. The name of the XML file describing the plug-in. The password is not required if you are using option -m. 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. Update an existing plug-in. The password is not required if you are using option -m. see Table 16-1 on page 405. or the registration fails. Not applicable for authentication modules. Not applicable for authentication modules. The connect string the Repository Agent uses to connect to the repository database. The NIS login of the user registering an external security module. but not both. Use the -w or -W option. Required if registering authentication module components. The repository database user name. For a list of connect string syntax. Indicates to unregister and re-register a plug-in if it already exists. Use the -p or -P option. If the plug-in contains an authentication module you must supply the external login name. The repository database password environment variable. and you do not specify this option.

You can use the Registerplugin command to register the security plug-in. the administrator user must use this login name and password to access the repository. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. The -i option contains the XML file name that describes the security module. see “Registering and Unregistering LDAP Security Modules” on page 88. Required if registering authentication module components. 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 upgrade installs the LDAP security module in the repository security folder. -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.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. Use the -w or -W option. Stores the CRC of the plug-in library in the repository. Note: The login name and password must be valid in the external directory. 484 Chapter 16: Using pmrep and pmrepagent . Example An administrator administers PowerCenter for a company that has a centralized LDAP NIS for user authentication.Table 16-72. After registration. 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. it checks the library against the CRC. you must register the security module with the repository. When he upgrades PowerCenter. but not both. Do not use this option for other plug-ins. For more information about this XML file. When the Repository Agent loads the module. he decides to use the LDAP for repository user authentication. or the administrator cannot access the repository using LDAP.

see Table 16-1 on page 405. 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. For a list of connect string syntax. When you restore a repository to a different system. 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. see “Restoring a Repository” on page 67. The target database must be empty. The connect string the Repository Agent uses to connect to the repository database. The type of database you want to restore to. If the repository you are restoring uses an external directory service. Use the -p or -P option. or if the password is incorrect. Valid for Microsoft SQL Server only. Use a trusted connection to connect to the database. but not both.” Note: If the repository uses repository authentication. The Repository Agent resets the Administrator’s password to “Administrator. the Repository Agent does not assume that the same user authentication module is on the new system. but not both.Restoring a Repository (Restore) The pmrepagent Restore command restores a repository backup file to a database. the Repository Agent unregisters the external module and resets the Administrator password after the restore. 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. Not required if you are using option -m. For more information about restoring a repository. Use the -p or -P option. The repository code page. The repository database password. The repository database user name. The repository database password environment variable. Not required if you are using option -m. -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. then the Administrator’s password does not change when you restore the repository.

You must use this option to retain the external module registration after the restore. Use this option only with a repository using an external security module. 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. administrator_username Specifies repository administrator user name. The Repository Agent verifies that this password is valid for the user name on the target server. Include this option if you want to promote the repository to a global repository. You must use either the -x or -X option when you want to retain an external security module. Verify password. Use the -x or -X option. Use this option to force the Repository Agent to verify that the administrator user is valid with the current authentication module. but not both. Use this option to specify the tablespace name for IBM DB2 EEE databases. The repository license file name. The name of the repository backup file. You can use any file name and path local to the Repository Server. -v Optional/ Required for retaining an external security module.Table 16-73. 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. pmrepagent interprets the spaces as part of the tablespace name. Use this option only with a repository using an external security module. This option has no argument. 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. -x Required/ Optional verify_password 486 Chapter 16: Using pmrep and pmrepagent .

Skips tables related to MX data during backup. 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. 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. Removes user name-login mapping. The Repository Agent verifies that this password is valid for the user name on the target server. For more information. Skips deployment group history during backup. Skips tables related to workflow and session logs during backup. Use this option with the -v option when you want to retain the external security module after restoring. You must use either the -x or -X option when you want to retain an external security module.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. For more information on unregistering plug-ins. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479.Table 16-73. see “Unregistering a Repository Plug-in” on page 86. 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 . -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. but not both. 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. Use this option only when unregistering an external module.

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

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

Valid for Microsoft SQL Server only. Not required if you are using option -m. but not both. 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. The repository database user name. see “Upgrading a Repository” in the Installation and Configuration Guide. see Table 16-1 on page 405. Use a trusted connection to connect to the database. 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 repository password. Not required if you are using option -m. The type of database you want to upgrade to. For a list of connect string syntax. but not both. The repository user name. but not both. The repository database password. The repository password environment variable. The repository database password environment variable. The connect string the Repository Agent uses to connect to the repository database. Use the -p or -P option. Use the -x or -X option. -P database_password_environment _variable n/a database_connect_string -m -c 490 Chapter 16: Using pmrep and pmrepagent .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. Use the -p or -P option. but not both. For more information on upgrading repositories. Use the -x or -X option.

rep You can run script files from the command interface. connects to and backs up a repository called Production on a server named Central: backupproduction. backupproduction. you might use some commands with specific options and arguments on a regular basis.bat. you might use pmrep to perform a daily backup of a production repository.. Scripting pmrep and pmrepagent Commands 491 . the following Windows batch file. Return code (1) indicates the command failed.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. Return code (0) indicates that the command succeeded. For example.. In this case. you can create a script file to call one or more pmrep commands including its options and arguments. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup. Tip: When you create script files using pmrep commands.. For instance. pmrep and pmrepagent indicate the success or failure of a command with a return code. You cannot run pmrep batch files while in pmrep interactive mode..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. 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. 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.

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

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

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

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

--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files .dtd. SOURCE. you must create an XML file defined by impcntl. TARGET and etc. you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard.dtd. TYPEFILTER*.Version 7. but you must include its location in the input XML file.Informatica Object Import Control DTD Grammar . 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*. The following is a sample of the impcntl. This should comforming to the element name in powermart. 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. The import control file installs with the PowerCenter Client. To create a control file.g. e.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.Using the Object Import Control File When you use the pmrep ObjectImport command.dtd 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.) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .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 .TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import.

Replace. Imports just the objects from a specific node. Copies SAP program information into the target repository. Normalizer. The default connection is the first connection from the sorted list of available connections. and XML Source Qualifier transformation current values in the destination. targets. Object type for this conflict resolution. Applies the default connection when a connection used by a session does not exist in the target repository.Object Import Control File Parameters Table A-1 lists pmrep Object Import control file parameters: Table A-1. Source DBD name to identify source object. Specifies the repository containing the target folder. Replace. Find the list of connections in the Workflow Manager. Replace. Identifies objects by type. Retains existing Sequence Generator. such as sources. Applies the label name on the imported objects. Specifies the repository containing the source folder. Reuse. or Rename. Applies the comments to the checked in objects. Specifies the import folder name to match to a folder in the target repository. Identifies objects from this query result for conflict resolution specification. Specifies the target folder name for matching. Allows you to specify conflict resolutions for objects. 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. or Rename. Rename. for conflict resolution specification. Identifies objects by label name for conflict resolution specification. or mappings. Reuse. Reuse. 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 . Specific object name for this conflict resolution.

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

You might create a control file with the following attributes: <?xml version="1.” However.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 . you want to replace all the duplicate objects labeled “Monthend. It specifies to check in the imported objects and label them. The file specifies the target folder and repository. you want to rename conflicting source objects that contain “Yr_End” in the object name. and specifying resolutions for specific objects. specifying resolutions for object types. You have a query called “yr_end_qry” that finds these objects. including specifying a resolution for query results. It lists what types of objects to import and shows several methods that you can use to resolve conflicts.0" encoding="UTF-8"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. In the target folder.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.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. <?xml version="1.Example Suppose you want to import only source objects.

e.<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.g.--> <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. SOURCE. This should conforming to the element name in powermart. TARGET and etc. 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 .dtd.

typename etc.) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .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 .<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.

<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 .

dtd file.Using the Deployment Control File When you use DeployDeploymentGroup or DeployFolder pmrep commands. To use pmrep deployment commands you must create an XML file that works with depcntl. 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 . you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard. The deployment control file installs with the PowerCenter Client.dtd. 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. but you should include its location in the input XML file. <!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?.

Creates a new folder with this name. Does not allow replacing of manually modified target folders. Copies SAP R/3 installed ABAP program. Retains workflow variable persistent values. Indicates local or global folder. Name the folder after replacing it. Copies workflow logs. 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. Retains workflow session logs in the target. Copies only the latest version. Copies dependency information for objects in mappings. Specifies the current folder that shortcuts point to. Keeps the current value for Sequence Generator or Normalizer transformations.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Using the Deployment Control File 505 . 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. Retains mapping variable persistent values in the target. Retains server network related values in tasks. Copies mapping variable persistent values. Copies workflow variable persistent values.

After you copy the folder. Moves the label from a different version of the object in the source group to the deployment group version of the object.0" encoding="ISO-8859-1"?> <!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl. and you need to point the shortcuts from the sc_folder to the new_sc_folder.Table A-2. Removes objects from source group after deploying. 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. Indicates local or global folder. TARGETLABELNAME TARGETMOVELABEL Example Suppose you want to deploy the latest version of a folder and include all dependencies. you want to rename it to “new_year. Applies a label to all the objects in the source group. Moves the label from a different version of the object in the target group to the deployment group version of the object. Applies a label to all the objects deployed to the target repository. You need to retain the current values in a Sequence Generator transformation. you can choose to move the label to the latest version of the object. If the Repository Agent detects the label is applied to another version of the same object.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 .” You might create a control file with following attributes: <?xml version="1. 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 selected version of the object.

c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup. you can create a script file to call one or more pmrep commands including options and arguments. For example.rep You can run script files from the command interface.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. Informatica recommends that you include a connect command as the first command called by the script file.. For instance. the following Windows batch file.bat.. you might use commands with specific options and arguments on a regular basis. Return code (-1) indicates the command failed. You cannot run pmrep batch files while in pmrep interactive mode. connects to and backs up a repository called Production on a server named Central: backupproduction. backupproduction. Return code (0) indicates that the command succeeded. In this case. you might use pmrep to perform a daily backup of a production repository..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.. pmrep and pmrepagent indicate the success or failure of a command with a return code. 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. This helps ensure you are performing tasks on the correct repository. Tip: When you create script files using pmrep commands. Scripting pmrep and pmrepagent Commands 507 .

508 Appendix A: Working with pmrep Files .

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

Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. Read permission in the originating folder. 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. and mappings Create/edit sources. 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.Designer Tasks To perform the following Designer tasks. you must have one of the listed sets of privileges and permissions. Read and write permission for the destination folder. Read and write permission in the destination folder. 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 . For example. targets. targets. transformations.

For example. Write permission and belong to the same group as the owner of the connection object. you must also have read permission for connection objects associated with the session. if you enabled enhanced security. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. 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.Workflow Manager Tasks To perform the following Workflow Manager tasks. 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. 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 .

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. FTP. and external loader connections in the Workflow Manager Edit database. 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 .Table B-2. FTP. 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.

For example.Workflow Monitor Tasks To perform the following Workflow Monitor tasks. 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. 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. Super User privilege Table B-3 lists the required privileges and permissions for 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-3.

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. 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.

For example. you can edit the properties of a folder if you have one of the following sets of permissions or privileges: ♦ ♦ ♦ Browse Repository privilege. 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 . 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.

groups. or remove the registry Manage users. 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. 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. 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 .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 .Table B-5.

pmrep Tasks To perform the following pmrep tasks. 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. For example. you must have one of the listed sets of privileges and permissions. 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 .

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

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. 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. 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 . 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.

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. 276 parent objects 271 permissions 266 524 Index . 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. 37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl.dtd 504 rolling back a deployment 238 deployment groups copying 254.dtd listing 504 dependencies source-target 27 viewing 27.

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. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182. 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. 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.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. 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. 192 creating 14 promoting 112.

462 applying when importing 280 526 Index creating 219. 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 .dtd 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart.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.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.

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.local repositories See also repositories code page 75. 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 . 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.

432 importing 280. 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 .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