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, 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.
While the Model repository synchronizes its contents with the version control system for the first time, the Model repository remains 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, 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 of the global repository for Git.
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 global repository.
Password
Password for the version control system user.
For Git, enter the password for the global repository.
Test Connection
Validates the URL, host, and user credentials.
This option is not available for Git version control system. If you choose Git version system, the validation of URL and user credentials happens during Model repository recycle process.
To configure a local repository for Git version control system, you need to configure the
git_local_repository_path
custom property to add the local repository path for the Model Repository Service. 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. To add the custom property, navigate to the
Manage
Services and Nodes
Model Repository Service
Properties
section, and click the
Edit
icon in the
Custom Properties
section.