Installation Prerequisites

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

Memory	~ 2 GB minimum ~ 512 MB heap size. This is generally sufficient to process typical JMS messages but the requirements vary with larger message sizes and the number of messages processed concurrently.
Disk	Disk space will vary according to your requirements as messages are stored in the disk.

Environment compatibility

All WSO2 Carbon-based products are Java applications that can be run on any platform that is Oracle JDK 1.6.*/1.7.* compliant. JDK 1.8 is not supported yet. Also, We do not recommend OpenJDK as we do not support it or test our products with it.
All WSO2 Carbon-based products are generally compatible with most common DBMSs. The embedded H2 database is suitable for development, testing, and some production environments. For most enterprise production environments, however, we recommend you use an industry-standard RDBMS such as Oracle, PostgreSQL, MySQL, MS SQL, etc. For more information, see Working with Databases. Additionally, we do not recommend the H2 database as a user store.
It is not recommended to use Apache DS in a production environment due to scalability issues. Instead, use an LDAP like OpenLDAP for user management.
For environments that WSO2 products are tested with, see Compatibility of WSO2 Products.
If you have difficulty in setting up any WSO2 product in a specific platform or database, please contact us.

Required applications

The following applications are required for running the Message Broker and its samples or for building from the source code. Mandatory installs are marked with an asterisk *.

Application	Purpose	Version	Download Links
Oracle Java SE Development Kit (JDK)*	To launch the product as each product is a Java application. To build the product from the source distribution (both JDK and Apache Maven are required). To run Apache Ant.	1.6.24 or later / 1.7.* If you are using JDK 1.6, you might need to install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files to 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. If you are using JDK 1.7 on a Mac OS, install the snappy-java library using the following steps: Download the snappy-java JAR for Mac and extract it to a preferred location. This folder will be referred to as `<SNAPPY_HOME>`. Copy the appropriate snappy-java library file `i386.jnilib` (32bit) or `x86_64.jnilib` (64bit), which is in the `<SNAPPY_HOME>/org/xerial/snappy/native/Mac/`directory, to the `<MB_HOME>` directory. For more information on installing snappy-java library, see Snappy-java fails on Mac OS JDK 1.7.	http://java.sun.com/javase/downloads/index.jsp
Apache ActiveMQ JMS Provider	To enable the product's JMS transport and try out JMS samples if any. The ActiveMQ client libraries must be installed in the product's classpath before you can enable the JMS transport.	5.5.0 or later If you use any other JMS provider (e.g. Apache Qpid), install any necessary libraries and/or components.	http://activemq.apache.org/
Apache Ant	To compile and run the product samples.	1.7.0 or later	http://ant.apache.org/
SVN Client	To check out the code to build the product from the source distribution.		Linux - http://subversion.apache.org/packages.html Windows - http://tortoisesvn.net/downloads.html
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	http://maven.apache.org/
Web Browser	To access the product's Management Console. The Web Browser must be JavaScript enabled to take full advantage of the Management console. On Windows Server 2003, you must not go below the medium security level in Internet Explorer 6.x.