Follow the instructions below to download WSO2 BPS from the WSO2 middleware products stack.
...
1. Open a Web browser and access one of the following URLs:
...
the product from the product web page. You can also download and build the source code.
- In your Web browser, go to http://
...
...
2. Pick WSO2 BPS from the "Products" menu and click on it to access its product page. For example,
3. You will be navigated to the product page. On the right-hand side of the page, you can find download options.
...
| title | Note |
|---|
- com/products/business-process-server.
- If you are a new user
...
- downloading WSO2 products for the first time,
...
- register and log
...
- in.
- Once you are logged in, click the Binary button in the upper right corner of the page.
The following distribution packages are typically available for download:
...
binary distribution contains the Carbon binary files for both MS Windows and Linux operating systems, compressed into a single ZIP file.
...
4. Click on any option to download the relevant distribution package.
...
You can also download the source and build the BPS. The source can be checked out 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 BPS release 3.0.0 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:
| Code Block |
|---|
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/platform/tags/4.0.2/products/bps/3.0.0 wso2carbon |
Building the product
- Install Maven and JDK. See Installation Prerequisites for compatible versions.
- Set the environment variable
MAVEN_OPTS=”-Xms768m -Xmx3072m -XX:MaxPermSize=1200m” to avoid the mavenOutOfMemoryError. - Make sure the build server has an active Internet connection to download dependencies while building.
The list of commands that can be run are as follows. If you only want to build the BPS, you have to always use the option "-Dproduct=bps".
| mvn clean install -Dproduct=bps | To create the complete release artifacts of WSO2 BPS including the binary and source distributions. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bps | To create the complete release artifacts of WSO2 BPS including the binary and source distributions, without running any of the unit tests. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bps -o | To create the complete release artifacts of WSO2 BPS 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 (trunk) can be checked out using the following commands.
| Code Block |
|---|
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/trunk 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 BPS specific ones. Therefore, you need to build just the set of components required by the BPS, using the following command:
| Code Block |
|---|
$ mvn clean install -Dproduct=bps |
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/carbon/platform/trunk 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 |
...
| hidden | true |
|---|
...
This distribution is recommended for many users.