This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Follow the below instructions to download the WSO2 Governance Registry installer.



Download Governance Registry for Windows

1. Open a web browser and access the following URL:

http://wso2.org/downloads/governance-registry

2. Select WSO2 Governance Registry from the "Products" menu and click on it to access its product page. For example,


3. The product page opens. In the top, right-hand corner of the page, you can find download options.  

If you are a new user, please register and log in to view the download options.

The following distribution packages are available for download:

  • Binary Distribution - Includes binary files for both MS Windows and Linux operating systems, compressed into a single ZIP file. Recommended for most users.
  • Source (SVN) - Includes the source code, which you can use to build the binary files. Recommended for advanced usage. To download and build the source code, see Build From Source.

4. Click on any option to download the relevant distribution package.

Download for Linux (Binary)

1. Establish an SSH connection to the Linux machine or log in on the text Linux console.

2.  Download the binary distribution installation pack via the wget --user-agent command. Anonymous download is not permitted. For example,

wget --user-agent="testuser" http://dist.wso2.org/products/governance-registry/4.5.0/wso2greg-4.5.0.zip

Build From Source  

You can check-out the source from SVN and build the Governance Registry using the following commands. This project uses Subversion to manage its source code. Instructions on Subversion can be found at http://svnbook.red-bean.com.

Anonymous Checkout

You can download the complete WSO2 Carbon platform, which is recommended if you intend to modify the source. You can check out the complete source anonymously from SVN with the following commands. The Carbon project comes in three sub projects named as Orbit, Kernel, and Platform. Download and build them in that particular order.

Orbit:
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/orbit/tags/4.0.1 wso2carbon

Carbon kernel:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/tags/4.0.1 wso2carbon

Carbon platform:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/4.0.1 wso2carbon

Following are the commands you can run. If you only want to build the governance registry related artifacts, use the -Dproduct=greg option as shown. If you want to build the entire Carbon core project, omit the -Dproduct=greg option.

  
mvn clean install -Dproduct=gregTo create the complete release artifacts related to WSO2 Governance Registry including the binary and source distributions.
mvn clean install -Dmaven.test.skip=true -Dproduct=gregTo create the complete release artifacts related to WSO2 Governance Registry including the binary and source distributions, without running any of the unit tests.
mvn clean install -Dmaven.test.skip=true -Dproduct=greg-oTo create the complete release artifacts related to WSO2 Governance Registry including the binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you've already built the source at least once.

If you are a committer, you can commit your changes using the following command (SVN will prompt you for your password):

$ svn commit --username your-username -m "A message"

Access through a Firewall

If you are behind a corporate firewall that is blocking http access to the Subversion repository, you can try the developer connection:

$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbon

Access through a Proxy

The Subversion client can be configured to access through a proxy. Specify the proxy to use in the "servers" configuration file in: 

  • "~/.subversion" directory for Linux/Unix
  • "%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")

The comments in the file explain what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.

For example, edit the 'servers' file and add something similar to:

[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128
  • No labels