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 SOAP messages but the requirements vary with larger message sizes and the number of messages processed concurrently.
Disk	~ 480 MB, excluding space allocated for log files and databases.

Environment compatibility

Operating Systems / Databases

All WSO2 Carbon-based products are Java applications that can be run on any platform that is JDK 7 or 8 compliant.
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 Directory (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 on a specific platform or database, please contact us.

Required applications

The following applications are required for running the product and its samples or for building from the source code.

Application	Purpose	Version	Mandatory	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). Due to a known issue dashboards do not load when using WSO2 DS with IBM JDK versions 1.7 and 1.8. Therefore, to overcome this issue navigate to the `<DS_HOME>/repository/deployment/server/jaggeryapps/portal/jaggery.conf` file and remove the forward slash in front of the `welcomeFiles` routers. Example "welcomeFiles": ["routers/tenant.jag"],	JDK 7 or 8 Do not use JDK1.8.0_151 due to a known issue. This issue is fixed in JDK 1.8.0_162-ea. However, use JDK 1.8.0_144 until the latter mentioned version is released. Oracle and IBM JRE 1.7 are also supported when running (not building) WSO2 products.	Yes	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.	No	http://activemq.apache.org/
Git	To check out the source for the purpose of building the product from the source distribution.	1.8.*	No	http://git-scm.com/
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.*	No	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. NOTE: On Windows Server 2003, you must not go below the medium security level in Internet Explorer 6.x.		Yes

You are now ready to install WSO2 DS. Click one of the following links for instructions: