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
| Application | Purpose | Version | Minimum Requirements | Download Links | |
|---|---|---|---|---|---|
| Development/ Testing Environment | Production Environment | ||||
Oracle Java SE Development Kit (JDK) | Required by all the products:
| 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. Oracle and IBM JRE 1.7 are also supported.
| √ | √ | 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.5.0 or later | X | √ | |
MySQL Connector for Java | Required as a standardized database driver for Java platforms and development. | 1.7.0 or later | 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. |
| ActiveMQ | Required for Private PaaS runtime. The Private PaaS components communicate to each other via the Message Broker using the AMQP AND mqttp PROTOCOLS. | ActiveMQ 5.10.0 | √ | √ |
|
| WSO2 CEP | Required to analyze & process events of a cartridge. | 3.0.0 | √ | √ | |
Building from source
The following software are required to build Private PaaS from source:
For more information, see Building from Source.
| 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 | √ | √ | |
Oracle Java SE Development Kit (JDK) | Required by all the products:
| 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. Oracle and IBM JRE 1.7 are also supported.
| √ | √ | 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
The following software are required 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 | |
| Vagrant | Used to set up one or more virtual machine.
| 1.7.2 or later | √ | X | |
System requirements
| System Requirements |
|
| Environment Compatibility |
|
The minimum system requirement for each component, i.e. AtiveMQ, Private PaaS and CEP, when deploying Private PaaS on a distributed set up, is shown above.
If you are deploying Private Paas on a single set up, you will need to meet the following system requirements:
- Memory - 8GB
- Disk - 40GB hard disk space
- Processor - 2.8GHz and 4 Core CPU