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, Subversion (SVN), or Git version control system. 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 the versioning properties, restart the Model repository, and run the

infacmd mrs PopulateVCS

command to synchronize the Model repository content with the version control system.

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, SVN, or Git.
Host	For Perforce, enter the URL, IP address, or host name of the machine where the Perforce version control system runs. This option is not available for SVN and Git version control system.
URL	For SVN, enter the URL of the SVN version control system repository or the subfolder. For Git, enter the URL for the remote Git repository. This option is not available for Perforce version control system.
Port	Required. For SVN and Perforce, enter the port number that the version control system host uses to listen for requests from the Model Repository Service. This option is not available for Git version control system.
Path to repository objects	For Perforce, enter the 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 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. This option is not available for SVN and Git version control system.
Username	For Perforce, SVN, or Git, enter the user account for the version control system user. For SVN, the account type must be a Subversion user and not Windows login or Linux login user and must have write permissions on the version control system. For Perforce, the account type for a Perforce version control system must be a Standard user. For Git, enter the user name for the remote Git repository.
Password	Password for the version control system user. For Git, enter the password of the remote Git repository user.
VCS Local Repository Path	For Git, enter the file path of the local Git repository. The directory must be accessible from the machine on which you installed the Model Repository Service and from other nodes if you configured high availability for Model Repository Service.