This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
  • Created by Former user, last modified by Former user on Nov 15, 2018
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

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 on DEV/QA with low number of users.
  • ~ 1 GB heap size. for PROD environment, supporting most common use cases(OAuth/SAML, Federation, etc.) with moderate traffic.

Disk

  • ~ 1 GB, excluding space allocated for log files and databases.

Environment compatibility

Operating Systems/Databases/User Stores

  • All WSO2 Carbon-based products are Java applications that can be run on any platform that is Oracle JDK 7/8 compliant. Also, we  do not recommend OpenJDK as we do not support it or test our products with it.
  • 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 for use as a user store.
  • WSO2 Identity Server is shipped with a default embedded Apache DS. However, in a production environment, it is recommended to use an LDAP like OpenLDAP, due to scalability issues that exist with Apache DS.
  • For environments that WSO2 products are tested with, see Environments Tested with WSO2 Products.  
    See the known incompatibilities section to find out if this version of the product has issues running on your OS due to the JDK version.
  • If you have difficulty in setting up any WSO2 product in 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. 

The applications marked with an asterisk * are mandatory.

Running the product

These applications are mandatory and are required to run the binary distribution of the WSO2 product. The binary distribution contains the binary files for both MS Windows, and Linux-based operating systems. It is recommended for most users.

Application

Purpose

Version

Download Links

Java SE Development Kit (JDK)*

  • Oracle JDK 7 or 8

    Important!

    Some updates of JDK 1.8 (for example, JDK1.8.0_151) are affected by a known issue related to GZIP decoding. Until this issue is fixed, we recommend one of the following approaches:

    • Use either JDK1.8.0_144 or JDK1.8.0_077 updates. We have verified that these versions are not affected by the known issue.
    • Alternatively, you can disable GZIP decoding for your product by following the steps given below. This will ensure that your product is not affected by the known issue.
      1. Open the catalina-server.xml file from the <IS_HOME>/repository/conf/tomcat/ directory.

      2. Set the compression parameter (under each of the connector configurations) to false as shown below:

        compression="off"
      3. Restart the server.

    Note

    If you are using an Oracle JDK version lower than 8u161, you need to download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files from here and add the files to the security directory of your Java installation to avoid illegal key size errors when you try to invoke a secured Web service.

  • Oracle and IBM JRE 1.7 are also supported when running (not building) WSO2 products.
  • We do not recommend OpenJDK.

Java downloads

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.





Running samples and building from source

These applications are required for building the product from the source distribution, and compiling and running product samples. 

Application


PurposeVersionDownload Links

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.

http://activemq.apache.org/

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 (as recommended for most users) instead of building from the source code, you do not need to install Maven.

3.0.x

http://maven.apache.org/

  • No labels