Prior to installing any WSO2 Carbon-based product, it is necessary to have the appropriate prerequisite software installed on your system. Verify that the computer has the supported operating system and development platforms before starting the installation.
System
...
requirements
1 Heap size around 512MB - ~ 512 MB heap size. This is generally sufficient to process typical SOAP messages
|
.Requirements may - but the requirements vary with larger message sizes
|
and on - and the number of messages processed concurrently.
|
Disk | - ~ 180 MB, excluding space allocated for log files and
|
DatabasesMore space will be utilized at runtime for temporary files, server logs etc.
...
Environment compatibility
Operating Systems / Databases |
/ Application ServersAs all - All WSO2 Carbon-based products are Java applications
|
, it is generally possible to run them on most operating systems. These include Windows, Linux, Solaris, Ubuntu, Fedora, Mac OS X, Gentoo, SUSE, Debian etc. with a JDK 1.6.x runtime.However, Linux/Solaris are recommended for a production deployment.For detailed information on the Operating Systems, Databases and Application Servers each WSO2 product is compatible with, refer to the following WIKI space: Environments Compatible with the WSO2 Products....
- that can be run on any platform that is JDK 1.6.*/1.7.* or OpenJDK compliant.
- All WSO2 Carbon-based products are generally compatible with most common DBMSs.
- For environments that WSO2 products are tested with, see Environments Tested with WSO2 Products.
|
Required applications
The following applications are required for running the BRS and its samples or for building from the source code. Mandatory installs are marked with *.
Application | Purpose | Version |
|---|
Notes| Download Links |
|---|
Oracle Java SE Development Kit (JDK)* | - To launch the product as each product is a Java application.
|
To Source x or higher (1.6.0_24 onwards recommended for production)Required by all WSO2 products | 24 or later / 1.7.* - If you are using JDK 1.6, you might need to replace the Java Cryptography Extension (JCE) policy files in your JDK with the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files. This will avoid "illegal key size" errors when you try to invoke a secured web service.
- If you want to build the product from the source distribution, you must use JDK 1.6 instead of JDK 1.7.
- Oracle and IBM JRE 1.7 are also supported when running (not building) WSO2 products.
| http://java.sun.com/javase/downloads/index.jsp |
Apache ActiveMQ
JMS Provider | - To enable the product's JMS transport and try out JMS samples. The ActiveMQ client libraries must be installed in the product's classpath before you can enable the JMS transport.
| 5.5.0 or |
higher later
If you use any other JMS provider (e.g. Apache Qpid), install any necessary libraries and/or components. |
Currently needed by WSO2 ESB to run its JMS samples sample clientsTo Required by all WSO2 products to run product samples | Apache Maven | (both JDK and Apache Maven are required).2.1.0 to 3.0.0 | Required by all WSO2 products when installing from source distribution | SVN Client | - To checkout WSO2 Carbon source from
http:.
| Can be downloaded form,- distribution. If you are installing by downloading and extracting the binary distribution instead of building from the source code, you do not need to install SVN.
|
| |
Linux - |
Apache Maven | - To build the product from the source distribution (both JDK and Apache Maven are required). If you are installing by downloading and extracting the binary distribution instead of building from the source code, you do not need to install Maven.
| 3.0.x | |
subversion/packages.htmlRequired by all WSO2 products | the - each product's Management Console. The Web Browser must be JavaScript enabled to take full advantage of the Management console.
|
NOTE: | Note |
|---|
On Windows Server 2003, |
|
it is allowed to go below the medium security level in Internet Explorer 6.x. |
|
| Required by all WSO2 products | ...
...
You are now ready to install WSO2 ESB. Click one of the following links for instructions: