Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Interactive Data Preparation Service
  11. Enterprise Data Preparation Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Version Control for the Model Repository Service

Version Control for the Model Repository Service

You can integrate a Model repository with a version control system. A version control system protects Model repository objects from overwriting objects on a team where multiple developers work on the same projects. A Model repository can use only one version control system instance.
You can integrate the Model repository with the Perforce, Subversion, or Git version control system. Perforce and Subversion are centralized version control systems. You might lose data if the Perforce or Subversion version control system server is not accessible or the server unexpectedly shuts down. Git is a distributed version control system. When you check in an object, a copy of the version is saved to the local repository and the Git server. If the Git server unexpectedly shuts down, the local repository retains all the versions of the object.
To integrate the Model repository with the Git version control system, you need the following repository details:
  • Global repository. The global repository is the Git server. You need the URL, user name, and password for the Git server. Use HTTPS protocol to create the global repository.
  • Local repository. The local repository is a directory on the node where you installed the Model Repository Service. The directory must be accessible by the client machines. If you have enabled high availability for Model repository, the directory must be accessible to the backup nodes in the domain. The local repository can support NFS, FAT32, and NTFS file systems. You can configure multiple Model Repository Services to use one local repository.
To enable version control for a Model Repository Service, perform the following tasks:
  1. Configure versioning properties. You can configure the versioning properties when you create or update a Model repository service. The versioning properties include a version control system user ID and password. The connection uses this single account to access the version control system for all actions related to versioned object management. For more information about versioning properties, see Versioning Properties for the Model Repository Service.
  2. Restart the Model repository. Before you restart the service, ask Model repository users to close all editable objects. When the Model repository restarts, it checks whether the version control system is in use by another Model repository. If the version control system is connected to a different Model repository, the Model Repository Service cannot restart. You must configure versioning properties to connect to a version control system that has not been integrated with another Model repository.
  3. Recycle the Model Repository Service.
  4. Synchronize Model repository content with the version control system. When you synchronize the content, the Model repository populates the local directory with Model repository objects.
When the Model repository is integrated with a version control system, you can check in revised objects, undo the checkout of objects, and reassign the checked-out state of objects to another user.