Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Open a Web browser and access one of the following URLs:

...

Follow the instructions below to download WSO2 API Manager from the WSO2 middleware products stack.

...

the product. You can also download and build the source code.

  1. In your Web browser, go to http://

...

  1. wso2.

...

2. Click "API Manager" from the "Products" menu.  

Image Removed

3. You will be navigated to the product page. On the right-hand side of the page, you can find download options. For example,

Image Removed

The following distribution packages are available for download:

...

  1. 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 binary files for both MS Windows and Linux-based operating systems, compressed into a single ZIP file.

...

This distribution is recommended for many users.

...

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

...

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

2. Download the binary distribution installation pack via the wget command. For example,

Code Block
wget http://dist.wso2.org/products/api-manager/1.2.0/wso2am-1.2.0.zip

...

WSO2 invites you to contribute by checking out the source from SVN 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.

The WSO2 API Manager release 1.2.0 is based on Carbon 4.0.3.

Anonymous Checkout

The complete source including the Carbon platform can be checked out anonymously from SVN with this command:

 

Code Block
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/platform/tags/4.0.3/products/apimgt/1.2.0 wso2carbon

The list of commands that can be run are as follows. If you only want to build the API Manager, you have to always use the option "-Dproduct=apimgt".

  
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.

Developer Access

Everyone can access the Subversion repository via HTTPS, but Committers must checkout via HTTPS. The Carbon framework related source code can be checked out using the following commands.

 

Code Block
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon

The Carbon core project is the root project of the OSGi platform on which the Java product stack is built. The Carbon components contain all the components not just the API Manager specific ones. Therefore, you need to build just the set of components required by the API Manager, using the following command:

 

Code Block
$ mvn clean install -Dproduct=apimgt

Execute the following command to commit your changes (SVN will prompt you for password).

 

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

Access through a Firewall

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

 

Code Block
$ 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:

Code Block
[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128

...

hiddentrue

...

After downloading the binary distribution, go to Installation Prerequisites for instructions on installing the necessary supporting applications.