| Info | ||
|---|---|---|
| ||
SCM Connections are one of many well-defined extension points supported by the WSO2 Governance Registry. Read more on Supported Extension Points for a complete list of extension points supported by WSO2 Governance Registry. |
Governance Registry contains the capability of interacting directly with external file systems and a variety of version control systems which supports Maven. Enabling support on Maven SCM plugin has fulfilled the mentioned aspect in GREG. Now a user can integrate Governance Registry with over 10 version control systems which are listed out at http://maven.apache.org/scm-1.7/matrix.html.
With the SCM support on Governance Registry users are able to fulfill following scenarios.
- Capability of directly managing a resource resides at a version control system from the Registry. The user can browse Resources/Collections and do operations such as add,update or delete resources from Registry end so it will get reflected on the version control system as well.
- A user can add WSDL,Schemas like artifacts from the Registry end and store all its 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 e.g. - Build Systems.
- If a user works with different types of multiple corporate repositories such as SVN, GIT, Perforce, VSS, and if the user wants to create a single view which allows to browse and manage the resources it is possible to use the registry for this aspect by enabling SCM support.
...
| Info |
|---|
As the resources are maintained in the file system, it is not possible to add properties to any of the checked out resources; therefore, operations such as Mounting, Symbolic Links, and Governance will not work on resources within an SCM mount. |
The Governance Registry can be easily mount with an external version control system by following the steps given below.
Configuration to enable SCM support
In order to create a SCM mounting in Governance Registry user has to uncomment the following configuration from the $GREG_HOME/repository/conf/registry.xml and properly configure by providing correct values for the parameters. This has to be done while the server is in shutdown mode, and has to restart after enabling the following configuration.
| Tip |
|---|
If you want to view the content from another mounted node, you must configure SCM support in that node, too. |
| Code Block |
|---|
<scm>
<connection checkOutURL="scm:svn:http://svn.wso2.org/repos/wso2" workingDir="/valid/filesystem/path" mountPoint="/_system/foo" checkInURL="" readOnly="" updateFrequency="">
<username>admin</username>
<password>admin</password>
</connection>
</scm> |
...
After the server is started, the resources from the version repository control system would be there in the specified location of the registry in the same hierarchical order.
| Warning |
|---|
It is not possible to add properties to any of the checked out resources since the resources are maintained in file system, and therefore operations such as Mounting, Symbolic Links, Life Cycles and Retention would not work on resources within an SCM mount. |
...
| Excerpt | ||
|---|---|---|
| ||
Description of SCM mount configuration details. |