Follow the instructions below to deploy WSO2 Private PaaS (PPaaS) on a preferred IaaS, i.e., Kubernetes, Amazon Elastic Compute Cloud (EC2), OpenStack and Google Compute Engine (GCE), in a single JVM:
Step 1 - Configure external databases for PPaaS...
| Note |
|---|
Skip this step if you wish to use PPaaS with the internal database, such as when you are using the PPaaS installer to install PPaaS. |
| Panel |
|---|
For testing purposes you can run your PPaaS setup on the internal database (DB), which is the H2 DB. In the latter mentioned scenario, you do not need to setup the internal DB. However, in a production environment it is recommend to use an external RDBMS (e.g., MySQL). | Expand |
|---|
| title | Click here to for instructions... |
|---|
| | Include Page |
|---|
| Configuring PPaaS with External Databases |
|---|
| Configuring PPaaS with External Databases |
|---|
|
|
|
...
Step 2 - Setup ActiveMQ
...
Skip this step if you are using the PPaaS installer, because the installer will configure and install ActiveMQ together with PPaaS and other components in a single Java Virtual Machine (JVM).
For more information, see Running the PPaaS Installer. |
| Panel |
|---|
PPaaS uses the Message Broker (MB) to handle the communication among all the components in a loosely coupled manner. Currently, PPaaS uses Apache ActiveMQ; however, PPaaS supports any Advanced Message Queuing Protocol (AMQP) Message Broker. | Expand |
|---|
| title | Click here to for instructions... |
|---|
| | Include Page |
|---|
| Configuring and Running Apache ActiveMQ with PPaaSConfiguring and |
|---|
| Running Apache ActiveMQ with PPaaS |
|---|
|
|
|
Step 3 - Setup and start WSO2 CEP
| Panel |
|---|
By default, PPaaS is shipped with an embedded WSO2 Complex Event Processor (CEP). It is recommended to use the embedded CEP only for testing purposes and to configure CEP externally in a production environment. Furthermore, the compatible CEP versions differ based on whether the CEP is internal or external. WSO2 CEP 3.0.0 is embedded into PPaaS. However, PPaaS uses CEP 3.1.0 when working with CEP externally. | Tip |
|---|
If you want to use CEP externally, prior to carrying out the steps below, download WSO2 CEP 3.1.0 and unzip the ZIP file. |
| Expand |
|---|
| title | Click here to for instructions... |
|---|
| | Include Page |
|---|
| Configuring WSO2 Complex Event Processor with PPaaS |
|---|
| Configuring WSO2 Complex Event Processor with PPaaS |
|---|
|
|
If you want to use CEP externally, after you have successfully configured CEP, start the CEP server: | Note |
|---|
This is only applicable if you have configured CEP 3.1.0 externally. |
| Code Block |
|---|
./wso2server.sh |
|
...
| Note |
|---|
Skip this step if you do not want to enable monitoring and metering in PPaaS using DAS. Even though this step is optional we recommend that you enable monitoring and metering in PPaaS. |
| Panel |
|---|
Optionally, you can configure PPaaS to work with WSO2 Data Analytics Server (DAS), so that it can handle the monitoring and metering aspect related to PPaaS. | Tip |
|---|
If you want to use DAS with PPaaS, prior to carrying out the steps below, download WSO2 DAS 3.0.0 and unzip the ZIP file. |
| Expand |
|---|
| title | Click here to for instructions... |
|---|
| | Include Page |
|---|
| Configuring WSO2 Data Analytics Server with PPaaS |
|---|
| Configuring WSO2 Data Analytics Server with PPaaS |
|---|
|
|
After you have successfully configured DAS in a separate host, start the DAS server: | Code Block |
|---|
./wso2server.sh |
|
...
Step 5 - Setup PPaaS
...
PPaaS
...
| Panel |
|---|
When using a VM setup or Kubernetes, you need to configure PPaaS accurately before attempting to deploy a WSO2 product on the PaaS. | Expand |
|---|
| title | Click here to instructions... |
|---|
| | Include Page |
|---|
| Configuring PPaaS |
|---|
| Configuring PPaaS |
|---|
|
|
|
...
Step 6 - Start the PPaaS server
| Panel |
|---|
Manually Starting PPaaSThe way in which you need to start the PPaaS server varies based on your settings as follows: | Note |
|---|
We recommend to start the PPaaS server in background mode, so that the instance will not |
If you want to use the internal database (H2) and the embedded CEP, start the PPaaS server as follows: | Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start |
If you want to use an external database, start the Private PaaS server with the -Dsetup option as follows:
This creates the database schemas in <PRIVATE_PAAS_HOME>/dbscripts directory. | Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start -Dsetup |
If you want to use an external CEP, disable the embedded CEP when starting the PPaaS server as follows: | Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start -Dprofile=cep-excluded |
If you want to use an external database, together with an external CEP, start the Private PaaS server as follows:
This creates the database schemas in <PRIVATE_PAAS_HOME>/dbscripts directory.
| Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start -Dsetup -Dprofile=cep-excluded |
Starting PPaaS with the Installer| Insert excerpt |
|---|
| Running the PPaaS Installer | Running the PPaaS Installer | nopanel | true
|---|
| Tip |
|---|
You can tail the log, to verify that the Private PaaS server starts without any issues. | Code Block |
|---|
tail -f <PRIVATE_PAAS_HOME>/repository/logs/wso2carbon.log |
|
...