The following are some recommendations that you need to follow in a production environment:
| Table of Contents |
|---|
Database
PPaaS is shipped with the H2 database (DB). However, in a production environment it is recommend to setup an external DB. For more information, see Configuring PPaaS with External Databases.
When using an external DB, you need to start PPaaS in the following manner, so that the respective database schemas are created:
| Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start -Dsetup |
When the database schemas are created, it will get saved in the <PRIVATE_PAAS_HOME>/dbscripts directory.
Health Statistic Monitoring
By default, PPaaS is shipped with an
...
embedded health statistics monitor, namely WSO2 Complex Event Processor (CEP)
...
. However, it is recommended 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. For more information, see Configuring WSO2 Complex Event Processor with PPaaS.
When using the external CEP,
...
you need to disable the CEP that is embedded in PPaaS to avoid any errors that would arise whilst running PPaaS with the externally configured CEP. Disabling the internal CEP can be done at the time of starting the PPaaS server as follows:
| Code Block |
|---|
sh <PRIVATE_PAAS_HOME>/bin/wso2server.sh start -Dprofile=cep-excluded |
Metering and Monitoring
It is recommend to configure WSO2 Data Analytics Server (DAS) externally to handle the monitoring and metering aspect related to PPaaS in a production environment. For more information, see Configuring WSO2 Data Analytics Server with PPaaS.