Unknown macro: {next_previous_links}
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 15 Next »

Follow the instructions below to download WSO2 API Manager. You can download the binary distribution from the API Manager Web page or download and build the source code.

Downloading from the Web page 

  1. In your Web browser, go to http://wso2.com/products/api-manager.
  2. If you are a new user downloading WSO2 products for the first time, register and log in.
  3. Once you are logged in, click the Binary button in the upper right corner of the page.

The binary distribution contains the API Manager binary files for both MS Windows and Linux operating systems, compressed into a single ZIP file. This distribution is recommended for most users.

Build from source

WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system using the following commands. For information on using Subversion, see http://svnbook.red-bean.com .

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 (note that this version of the API Manager is based on Carbon 4.1.2). The Carbon project comes in three sub projects: Orbit, Kernel, and Platform. Download and build them in that particular order.

Orbit:

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

Kernel:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/tags/x.x.x Kernel

Platform:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/x.x.x Platform

Following are the commands you can run to create complete release artifacts of WSO2 API Manager, including the binary and source distributions. If you only want to build the API Manager, use the -Dproduct=apimgt option as shown. If you want to build the entire Carbon core project, omit the -Dproduct=apimgt option.

  
mvn clean install -Dproduct=apimgt
To create the complete release artifacts of the product including the binary and source distributions.
mvn clean install -Dmaven.test.skip=true -Dproduct=apimgtTo create the complete release artifacts of the product including the binary and source distributions, without running any of the unit tests.
mvn clean install -Dmaven.test.skip=true -Dproduct=apimgt -oTo create the complete release artifacts of the product 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.

  1. 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%)
  2. There are comments in the file explaining 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.

    Example : Edit the servers file and add something similar to:

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