Prerequisites

Prior to installing or deploying WSO2 EMM, 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	~ 1 GB, 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 Oracle JDK 1.6.* / 1.7.* compliant.
All WSO2 Carbon-based products are generally compatible with most common DBMSs. For more information, see Working with Databases.
It is not recommended to use Apache DS in a production environment due to issues with scalability. Instead, it is recommended to use an LDAP like OpenLDAP for user management.
For environments that WSO2 products are tested with, see Environments Tested with WSO2 Products.
If you have difficulty in setting up any WSO2 product in a specific platform or database, please contact us.

Device OS prerequisites

Platform	Supported Versions
iOS	6.0 - 7.0
Android	Ice Cream Sandwich (4.0.3 – 4.0.4) Jelly Bean (4.1 – 4.3.1) KitKat (4.4 – 4.4.4) Lollipop (5.0)

Feature prerequisites

To enable encryption, the battery level should be 80% or more.

Required applications

The following applications are required for running the product and when building WSO2 EMM from the source code. Mandatory installs are marked with an asterisk *.

Application	Purpose	Version	Download Links
Oracle Java SE Development Kit (JDK) / **Oracle Java SE JRE***	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 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://www.oracle.com/technetwork/java/javase/archive-139210.html
MySQL*	Used as the WSO2 EMM DB.	5.6.*	http://www.mysql.com/
MySQL Connector/J*	Used for WSO2 EMM DB connectivity.	5.1.*	http://dev.mysql.com/downloads/connector/j/
Git*	To checkout the source, in order to build the product from the source distribution. To get a the Git repository of the EMM Android Agent application.	1.8.*	http://git-scm.com/
Eclipse*	To build the Android client application.	Juno and upwards (4.2.1 upwards)	http://www.eclipse.org/
Android SDK*	To build the Android client application.	Level 8 to 17	http://developer.android.com/sdk/index.html
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.
Apache Ant	To compile and run the product samples.	1.7.0 or later	http://ant.apache.org/
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.*	http://maven.apache.org/