Page Comparison

Memory

• ~ 1 2 GB minimum
  
• 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 Databases.
  More space will be utilized at runtime for temporary files, server logs etcdatabases.

Operating Systems / Databases / Application Servers

• As 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 Tested with WSO2 Products.

• that can be run on any platform that is JDK 1.6.*/1.7.* compliant.  
• All WSO2 Carbon-based products are generally compatible with most common DBMSs.
  

Oracle Java SE Development Kit (JDK)*

• To launch the product as each product is a Java application.
• To To build the product from the Source source distribution (both JDK and Apache Maven are required).
• To run Apache Ant.

1.6.x 24 or higher (later / 1.6.0_24 onwards recommended for production)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.

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

Apache Ant

• To Required by all WSO2 products to compile and run the sample clients product samples.

1.7.0 or later

Required by all WSO2 products to run product samples

Apache Maven

• To check out the code to build the product from the source

2.1.0 to 3.0.0

Required by all WSO2 products when installing from source distribution

• To checkout WSO2 Carbon source from http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon.

• 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 - http://subversion.apache.org/packages.html
• Windows - http://tortoisesvn.net/downloads.htmlLinux -

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.3 or later

Web Browser

• Required by all WSO2 products

Web Browser

• To access the to access each product's Management Console. The Web Browser must be JavaScript enabled to take full advantage of the Management console.

NOTE: On Windows Server 2003,

you must not

go below the medium security level in Internet Explorer 6.x.

Required by all WSO2 products