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.
- ~ 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.
- ~ 1 GB minimum, excluding space allocated for log files and databases.
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.* or OpenJDK compliant. JDK 1.8 is not supported yet.
- All WSO2 Carbon-based products are generally compatible with most common DBMSs. For more information, see Working with Databases.
- If you have difficulty in setting up any WSO2 product in a specific platform or database, please contact us.
- 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.
- WSO2 CEP does not support SunOS 5.10 and IBM AIX. For environments that WSO2 products are tested with, see Compatibility of WSO2 Products.
The following applications are required for running the Complex Event Processor or for building from the source code. Mandatory installs are marked with *.
Oracle Java SE Development Kit (JDK)*
1.6.*/1.7.* or Open JDK
- 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.
- 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 supported when running (not building) WSO2 products.
If you are using JDK7 on Mac OS, follow the steps below to install the Snappy-java library
- Download the Snappy JAR file from here, and extract it to a preferred location. We will refer this extracted folder as
<SNAPPY_HOME>/org/xerial/snappy/native/Mac/ folder, you find the Snappy java library files (.jnilib files) as i386 (32bit) and x86_64 (64bit). Copy the appropriate one to
For more information on installing snappy-java library, see Snappy-java fails on Mac OS JDK 1.7.
|To enable the product's JMS transport and try out JMS samples.(preferably WSO2 Message Broker).|
2.0.0 or later
CEP supports other JMS providers such as Apache Active MQ & Apache Qpid. If you use any other JMS provider, install any necessary libraries and/or components.
|SVN Client||To check out the code to build the product from the source 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.|
|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.|
On Windows Server 2003, you must not go below the medium security level in Internet Explorer 6.x.
You are now ready to install. Click one of the following links for instructions: