Page Comparison

Governance Registry can interact directly with external file systems and a variety of version control systems that support Maven through the Maven SCM plugin. With the SCM support in Governance Registry, users can fulfill the following scenarios: 

• Directly manage a resource that resides in a version control system from the registry. The user can browse Resources/Collections and perform operations such as adding, updating or deleting resources from the registry so it will affect the version control system as well. 
• A user can add WSDLs and other schema-like artifacts to the registry and store all their dependency structures in the mounted version control system. This would allow the user to use those dependencies with some other third-party product as well, such as build systems.
• If a user works with different types of multiple corporate repositories such as SVN, GIT, Perforce, and VSS, and if the user wants to create a single view that allows you to browse and manage the resources, it is possible to use the registry for this aspect by enabling SCM support.

The Governance Registry can be easily mounted with an external version control system by following the steps given below.

Configuration to enable SCM support 

In order to create an SCM mounting in Governance Registry, stop the Governance Registry server, uncomment the following configuration in the  $GREG_HOME/repository/conf/registry.xml  and properly configure it by providing correct values for the parameters, and then restart the server.  

...

After the server is started, the resources from the version repository control system would will be there in the specified location of the registry in the same hierarchical order. 

...