...
- 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 which can be used to build the binary files. Recommended for more advanced users. For instructions, refer to Build From Source.
4. Click on any option to download the relevant distribution package.
Download for Linux
...
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/business-activity-monitor/2.0.0/wso2bam-2.0.0.zip |
Build From Source
| Anchor | ||||
|---|---|---|---|---|
|
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 BAM 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 with this command:
| Code Block |
|---|
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon |
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=as".
| mvn clean install -Dproduct=bam | To create the complete release artifacts of WSO2 BAM including the binary and source distributions. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bam | To create the complete release artifacts of WSO2 BAM including the binary and source distributions, without running any of the unit tests. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bam -o | To create the complete release artifacts of WSO2 BAM 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 |
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 Application Server specific ones. Therefore, you need to build just the set of components required by the Application Server, using the following command:
| Code Block |
|---|
$ mvn clean install -Dproduct=bam |
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 |
| Excerpt | ||
|---|---|---|
| ||
How to download WSO2 middleware products for installation. |