Installation Prerequisites

Prior to installing Private PaaS, verify that you have met the prerequisites described in the following sections on this page:

Software requirements

Install the following software requirements to run Private PaaS successfully:

General software requirements

The applications marked with an asterisk * are mandatory.

Application	Purpose	Version	Minimum Requirements		Download Links
Application	Purpose	Version	Development/ Testing Environment	Production Environment	Download Links
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.*	√	√	If you wish to get support for 32 bits in Private PaaS, download the Java 32 bits distribution.
MySQL Server	Required to manage database connections.	5.6.0	`X`	√
MySQL Connector for Java	Required as a standardized database driver for Java platforms and development.	5.1.x	`X`	√
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	√	√	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	√	√	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		√
WSO2 DAS	To handle the monitoring and metering in PPaaS.	3.0.0	√	√

Building from source

Install the following software requirements to build Private PaaS from source:

The applications marked with an asterisk * are mandatory.

Application	Purpose	Version	Minimum Requirements		Download Links
Application	Purpose	Version	Development/ Testing Environment	Production Environment	Download Links
Apache Maven*	Required to build the product from the source distribution.	3.1.1 or later	√	√
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.*	√	√	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	√	√

Working with Kubernetes

Install the following software requirements only when working with Kubernetes:

Application	Purpose	Version	Minimum Requirements		Download Links
Application	Purpose	Version	Development/ Testing Environment	Production Environment	Download Links
Oracle VM VirtualBox Manager	Used as the provider for Vagrant.	4.3.20 or later	√	`X`
Vagrant	Used to set up one or more virtual machine. 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`
Wget	To install applications when running PPaaS on Kubernetes, which is in-turn run on EC2.	any	√

System requirements

System Requirements	Memory - 4GB Disk - 40GB hard disk space Processor - 2.8GHz and 2 Core CPU
Environment Compatibility	Operating Systems - Linux (Ubuntu 12.04 64bit server or SUSE Linux Enterprise 11 SP2) If you wish to get support for 32 bits in Private PaaS, download the Java 32 bits distribution.

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