The following are the recommended prerequisites when running WSO2 Private PaaS in a single node. Please note that for production deployment the prerequisites will vary based on the scalability requirements.Prior to installing Private PaaS, verify that you have met the prerequisites described in the following sections on this page:
...
System Requirements
| Memory | Minimum 8GB RAM is recommended for a POC level project and 16GB AM is recommended for production environments. For example: m3.large for a POC level project and m3.xlarge for production environments, if EC2 is used. |
| Processor | 2.8GHz CPU |
| Disk | ~ 40GB hard disk space |
| Excerpt |
|---|
Software requirements Install the following software requirements to run Private PaaS successfully: General software requirements| Note |
|---|
The applications marked with an asterisk * are mandatory. |
| Application | Purpose | Version | Minimum Requirements | Download Links |
|---|
Development/
Testing
Environment | Production
Environment |
|---|
Oracle Java SE Development Kit (JDK)* | Required by all the products: - 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).
|
|
...
...
- 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.
| √ | √ | | Html |
|---|
<a target="_blank" href=http://java.sun.com/javase/downloads/index.jsp> http://java.sun.com/javase/downloads/index. |
|
|
...
| Info |
|---|
If you wish to get support for 32 bits in |
|
|
...
Private PaaS, download the Java 32 bits distribution. |
| MySQL |
|
...
...
| to manage database connections. |
|
...
...
...
| X | √ | | Html |
|---|
<a target="_blank" href=http://dev.mysql.com/downloads/ |
|
|
...
Required to check out the source from the Git repository.
...
...
dev.mysql.com/downloads/</ |
|
|
...
Required to build the product from the source distribution.
...
| MySQL Connector for Java | Required as a standardized database driver for Java platforms and development. | 5.1.x | X | √ | | Html |
|---|
<a target="_blank" href=http:// |
|
|
...
...
| Code Block |
|---|
sudo apt-get update
sudo apt-get install maven |
...
mysql.com/downloads/connector/j/5.1.html/> http://dev.mysql.com/downloads/connector/j/5.1.html</a> |
| | Zip Utility | Required to compress and unzip |
|
...
the packages. NOTE: This is not required when using the manual approach to configure and start Private PaaS. | Any | X | √ | Choose a zip utility that is compatible with the OS. |
|
...
| Cartridge Base Image | Required as a prerequisite for cartridges. | 2.6.0 or later |
|
...
If an AMQP message broker is not already installed in your machine, Apache ActiveMQ will get installed when the boot.sh script is executed during the product configuration .
| Info |
|---|
Currently Apache ActiveMQ is used as the default Message Broker . However, other AMQP Message Brokers (e.g., WSO2 Message Broker and RabbitMQ) are supported as well. |
...
Required to manage and automate system configurations.
...
If Puppet, is not already installed in your machine,it will get installed when the boot.sh script is executed during the product configuration.
| Info |
|---|
Install Puppet Master in the same machine. |
Environment Compatibility
- All WSO2 Carbon-based products are Java applications that can be run on any platform that is Oracle JDK 1.6.*/1.7.* compliant. JDK 1.8 is not supported yet. Also, we do not recommend or support OpenJDK.
- 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.
...
| √ | √ | The cartridge base image will vary based on the setup that you are using. For example, If you are using OpenStack, you need to have an OpenStack base image. Whereas, if you are using Docker, you need to have a Docker base image. | Apache ActiveMQ*
| Required for Private PaaS runtime. The Private PaaS components communicate to each other via the Message Broker using the AMQP and MQTT protocols. | ActiveMQ 5.10.0 | √ | √ | | Html |
|---|
<a target="_blank" href=https://activemq.apache.org/download.html>https://activemq.apache.org/download.html</a> |
| Info |
|---|
Currently, ActiveMQ 5.10.0 is used by default in the Private PaaS installation. However, Private PaaS also supports other AMQP Message Brokers such as, WSO2 Message Broker and RabbitMQ. Currently, ActiveMQ is used by default in the Private PaaS installation.
|
| | WSO2 CEP | - Required to analyze & process events of a cartridge.
- PPaaS is shipped with CEP 3.0.0. However, it is recommend to configure CEP externally in a production environment.
| 3.1.0 | | √ | | Html |
|---|
<a target="_blank" href=http://wso2.com/products/complex-event-processor/> http://wso2.com/products/complex-event-processor</a> |
| | WSO2 DAS | To handle the monitoring and metering in PPaaS. | 3.0.0 | √ | √ | | Html |
|---|
<a target="_blank" href=http://wso2.com/products/data-analytics-server/> http://wso2.com/products/data-analytics-server</a> |
|
Building from sourceInstall the following software requirements to build Private PaaS from source: | Note |
|---|
The applications marked with an asterisk * are mandatory. |
| Application | Purpose | Version | Minimum Requirements | Download Links |
|---|
Development/
Testing
Environment | Production
Environment |
|---|
Apache Maven* | Required to build the product from the source distribution. | 3.1.1 or later | √ | √ | | Html |
|---|
<a target="_blank" href=http://maven.apache.org> http://maven.apache.org</a> |
| Oracle Java SE Development Kit (JDK)* | Required by all the products: - 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).
| 1.7.* | √ | √ | | Html |
|---|
<a target="_blank" href=http://java.sun.com/javase/downloads/index.jsp> http://java.sun.com/javase/downloads/index.jsp</a> |
| Info |
|---|
If you wish to get support for 32 bits in Private PaaS, download the Java 32 bits distribution. |
| | Git Client* | Required to check out the source from the Git repository. | 2.2.1 or later | √ | √ | | Html |
|---|
<a target="_blank" href=http://git-scm.com/downloads/> http://git-scm.com/downloads/</a> |
|
Working with Kubernetes
Install the following software requirements only when working with Kubernetes: | Application | Purpose | Version | Minimum Requirements | Download Links |
|---|
Development/
Testing
Environment | Production
Environment |
|---|
| Oracle VM VirtualBox Manager | Used as the provider for Vagrant. | 4.3.20 or later | √ | X | | Html |
|---|
<a target="_blank" href=http://git-scm.com/downloads/> https://www.virtualbox.org/</a> |
| | Vagrant | Used to set up one or more virtual machine. | Info |
|---|
- As VirtualBox will be used as the provider for Vagrant, VirtualBox needs to be installed prior to installing Vagrant.
|
| 1.7.2 or later | √ | X | | Html |
|---|
<a target="_blank" href=http://git-scm.com/downloads/> http://www.vagrantup.com/downloads.html</a> |
| | Wget | To install applications when running PPaaS on Kubernetes, which is in-turn run on EC2. | any | √ | | | Html |
|---|
<a target="_blank" href=http://www.gnu.org/software/wget/> http://www.gnu.org/software/wget/</a> |
|
System requirements| System Requirements | - Memory - 4GB
- Disk - 40GB hard disk space
- Processor - 2.8GHz and 2 Core CPU
| | Environment Compatibility | |
|
...
Private PaaS, download the Java 32 bits distribution. |
|
| Note |
|---|
The minimum system requirement for each component, i.e. ActiveMQ, Private PaaS and CEP, when deploying Private PaaS on a distributed set up, is shown above. If you are deploying Private Paas in a single Java Virtual Machine setup, you will need to meet the following system requirements: - Memory - 8GB
- Disk - 40GB hard disk space
- Processor - 2.8GHz and 4 Core CPU
|
|