Page Comparison

Follow the instructions below to download the WSO2 Elastic Load Balancer from the WSO2 middleware products stack.

Download for Windows

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

http://www.wso2.org

or

http://www.wso2.com

2. Click WSO2 Elastic Load Balancer from the "Products" menu to access its product page.

Image Removed

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

Image Removed

 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 many users.
• Source (SVN) - Includes the source code for both MS Windows and Linux operating systems, compressed into a single ZIP file, which can be used to build the binary files. Recommended for more advanced users. For instructions to download and build from source, refer to section Build From Source.

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

Download for Linux (Binary)

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 --user-agent command. WSO2 does not allow anonymous downloads. For example,

wget --user-agent="testuser" http://dist.wso2.org/products/elastic-load-balancer/2.0.0/wso2elb-2.0.0.zip

...

You can also download the source, build the ELB and also 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 ELB release 2.0.1 is based on Carbon 4.0.2.

Anonymous Checkout 

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

...

WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system using the following commands, building the product and making changes, and then committing your changes back to the source repository. For information on using Subversion, go to  http://svnbook.red-bean.com.

Building from the source involves the following steps:

Checking Out the Source

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 (replace x.x.x with the version of Carbon you want to build). The Carbon project comes in three sub projects that are namely, Orbit, Kernel and Platform. Download and build them in that particular order. 

Example: The following commands, shows the way in which you should checkout the source if you have developer access:

• To checkout Orbit: 

  Code Block
  $ svn checkout https://svn.wso2.org/repos/wso2/carbon/orbit/tags/x.x.x <local-folder-name>

  This <local-folder-name> will be replaces with a meaningful name, such as wso2carbon-orbit

   

• To checkout Kernel:

  Code Block
  $ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/tags/x.x.x <local-folder-name>

  This <local-folder-name> will be replaces with a meaningful name, such as wso2carbon-kernel

   

• To checkout Platform: 

  Code Block
  $ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/

...

• x.

...

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

Developer Access 

...

• x.x <local-folder-name>

  This <local-folder-name> will be replaces with a meaningful name, such as wso2carbon-platform

   

The following are the various checkout instances. You can checkout the source using the instance that is most relevant to you:

• Anonymous access
• Developer access
• Access through a Firewall
• Access through a Proxy

Anonymous Access

$ svn checkout http://svn.wso2.org/repos/wso2/carbon/kernel/branches/x.x.x <local-folder-name>

Developer Access

Committers must checkout the Subversion repository via HTTPS.

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

...

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 ELB specific ones. Therefore, you need to build just the set of components required by the ELB, using the following command:

...

kernel/branches/x.x.x <local-folder-name>

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

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

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

...

branches/x.x.x <local-folder-name>

Access Through a Proxy

...

...

...

...

...

...

...

...

...

...

...

...

...

...

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

Building the Product

The following are the commands you can run to create complete release artifacts of WSO2 IS, including the binary and source distributions. Before you start,

• Install Maven and JDK. See Installation Prerequisites for compatible versions. 
• Set the environment variable MAVEN_OPTS=”-Xms768m -Xmx3072m -XX:MaxPermSize=1200m” to avoid the maven OutOfMemoryError.
• Make sure the build server has an active Internet connection to download dependencies while building.

Building using Maven

The following are the commands you can run to create complete release artifacts of WSO2 Carbon, including the binary and source distributions.

• To build the binary and source distributions.

  Code Block
  mvn clean install

• To build the binary and source distributions, without running any of the unit tests.

  Code Block
  mvn clean install -Dmaven.test.skip=true

• To build the binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you have already built the source at least once.

  Code Block
  mvn clean install -Dmaven.test.skip=true -o

Setting up your Development Environment

You need to setup your development environment to be able to edit the source code according to your requirement. Setup the environment using one of the following commands:

• If you are using Eclipse use the following command:

  Code Block
  mvn eclipse:eclipse

• If you are using intelliJIDEA use the following command:

  Code Block
  mvn idea:idea

Committing your Changes

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

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