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 REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Configure and Synchronize a Model Repository After Changing Versioning Properties

Configure and Synchronize a Model Repository After Changing Versioning Properties

You can enable version control, configure versioning properties, and then synchronize the Model repository with the version control system. After you configure versioning and synchronize the Model repository with the version control system, the version control system begins to save version history.
The following image shows the process of configuring, synchronizing, and re-synchronizing the Model repository with a version control system: The image shows the flowchart to configure and synchronize the Model reposiotry after changing versioning properties.
  1. Configure the versioning properties and recycle the Model Repository Service.
  2. Synchronize the Model repository content with the version control system.
  3. Optionally, change the version control system type.
    1. For Perforce, you can change the host, port number, username, or password.
    2. For SVN, you can change the URL, port number, username, or password.
    3. For Git, you can change the file path of the local Git repository, URL of the remote Git repository, username, or password.
      After you change the versioning properties, you can choose to retain or discard the version control history:
      1. Retain version control history. Copy content from local repository to new local repository.
      2. Discard version control history.
  4. Recycle the Model Repository Service
  5. Re-synchronize the Model repository content with the version control system.
You can perform these tasks from the command line or from the Administrator tool.
When you change Model repository properties, you must recycle the Model Repository Service for your changes to take effect. When you enable version control system or change a versioning property, the Model repository remains unavailable until you synchronise the Model repository.