Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Metadata Manager Service
  10. Model Repository Service
  11. PowerCenter Integration Service
  12. PowerCenter Integration Service Architecture
  13. High Availability for the PowerCenter Integration Service
  14. PowerCenter Repository Service
  15. PowerCenter Repository Management
  16. PowerExchange Listener Service
  17. PowerExchange Logger Service
  18. SAP BW Service
  19. Search Service
  20. System Services
  21. Test Data Manager Service
  22. Test Data Warehouse Service
  23. Web Services Hub
  24. Application Service Upgrade
  25. Application Service Databases
  26. Connecting to Databases from Windows
  27. Connecting to Databases from UNIX
  28. Updating the DynamicSections Parameter of a DB2 Database

Versioning Properties for the Model Repository Service

Versioning Properties for the Model Repository Service

To connect to a version control system, you must configure versioning properties in the Model Repository Service.
You can configure versioning properties for the Perforce or Subversion version control systems. Subversion is abbreviated "SVN".
Some of the properties refer to the version control system host machine and user accounts. Contact the version control system administrator for this information.
After you configure versioning properties, you restart the Model repository, and then run infacmd mrs PopulateVCS to synchronize Model repository contents to the version control system.
While the Model repository synchronizes its contents with the version control system for the first time, the Model repository is unavailable. Model repository users must close all editable objects before the process starts.
The following table describes the versioning properties for the Model Repository Service:
Property
Description
Version control system type
The supported version control system that you want to connect to. You can choose Perforce or SVN.
Host
The URL, IP address, or host name of the machine where the Perforce version control system runs.
Not available when you configure SVN as the version control system.
URL
The URL of the SVN version control system repository or the subfolder.
Not available when you configure Perforce as the version control system.
Port
Required. Port number that the version control system host uses to listen for requests from the Model Repository Service.
Path to repository objects
Path to the root directory of the version control system that stores the Model repository objects.
When you complete editing Versioning properties, the Model repository connects to the version control system and generates the specified directory if the directory does not exist yet.
Only one Model Repository Service can use this directory.
For Perforce, use the syntax:
//directory/path
where
directory
is the Perforce directory root, and
path
is the remainder of the path to the root directory of Model repository objects.
Example:
//depot/Informatica/repository_copy
When you configure SVN as the version control system, this option is not available.
If you change the depot path after you synchronize the Model repository with the version control system, version history for objects in the Model repository is lost.
Username
User account for the version control system user.
The account type for a Subversion version control system must be a Subversion user and not Windows login user.
This account must have write permissions on the version control system.
The account type for a Perforce version control system must be a Standard user.
Password
Password for the version control system user.