Versions Compared

Old Version 17

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 25

...

Info
iconfalse

The config-validation.xml file in the <PRODUCT_HOME>/repository/conf/etc directory contains a list of recommended system parameters, which are validated against your system when the server is started. See Configuring config-validation.xml for details.

System requirements

Memory

  • ~ 2 GB minimum
  • ~ 1 GB heap size. This is generally sufficient to process typical SOAP messages but the requirements vary with larger message sizes
and 
  • 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 JDK 1.6.*/1.7.* compliant.

...

  • JDK 1.8 is not supported yet. 
  • 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,

...

Required applications

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

Application

Purpose

Version

Download Links
Oracle

Java SE Development Kit (JDK)*

Required by all WSO2 products to:

  • To launch the product as each product is a Java application.

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
.We do not recommend OpenJDK
  • .
http://java.sun.com/javase/downloads/index.jsp
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 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

Required by all WSO2 products to

1.7.0 or later

http://ant.apache.org
SVN Client
 


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

Required by all WSO2 products to
  • To access each product's Management Console. The Web Browser must be JavaScript enabled to take full advantage of the Management console.
NOTE:
Note

On Windows Server 2003, you must not go below the medium security level in Internet Explorer 6.x.

 

 



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

...