Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
This documentation is for WSO2 Message Broker version 3.2.0. For the latest documentation, see the documentation for WSO2 Enterprise Integrator.
Skip to end of metadata
Go to start of metadata

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 JMS messages but the requirements vary with larger message sizes and the number of messages processed concurrently.

Disk

  • Disk space (for the database being used) will vary according to your requirements as messages are stored in the database.

Environment compatibility

Operating Systems / Databases

  • All WSO2 Carbon-based products are Java applications that can be run on any platform that is Oracle/IBM JDK 7/8 or OpenJDK compliant. See the section on compatibility of WSO2 products for more information. 

    If you are using IBM JDK, the default configurations in the product has to be changed as follows:

      • Open the Owasp.CsrfGuard.Carbon.properties file (stored in the <MB_HOME>/repository/conf/security directory) and change the org.owasp.csrfguard.PRNG.Provider property to IBMJCE as shown below.

        org.owasp.csrfguard.PRNG.Provider=IBMJCE
      • Open the broker.xml file (stored in the <MB_HOME>/repository/conf directory) and set the <certType> property to IbmX509 as shown below.

        <certType>IbmX509</certType>
  • 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 Compatibility of WSO2 Products.
  • 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 Message Broker and its samples or for building from the source code. Mandatory installs are marked with an asterisk *.

Application

Purpose

Version

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).
  • To run Apache Ant.

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 <MB_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.

http://java.sun.com/javase/downloads/index.jsp

Apache Ant

  • To compile and run the product samples.

1.7.0 or later

http://ant.apache.org/ 

Git


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.

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.

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



  • No labels