The quick start guide demonstrates how to get started with WSO2 Private PaaS in 15 minutes using a demo AMI. The detailed guide sequentially lists all the steps that need to be followed when working with WSO2 Private PaaS. This guide also acts as a navigator by pointing the readers to more detailed instructions whenever applicable.
Follow the instructions below to be able to smoothly work with Apache Stratos:
- Ensure that the installation prerequisites have been met prior to the WSO2 Private PaaS installation.
Download WSO2 Private PaaS Installer, load balancer, Cartridge Agent and Stratos binary distributions from the following location or build from source.
The installer archive comprises of the Private PaaS Git repository contents, excluding the source code. In the context of this documentation,<PRIVATE_PAAS_HOME>refers to either the unzipped contents of this installer, or the checked out contents from the Git repository.
http://wso2.com/cloud/private-paas/Configure the product using one of the following approaches:
Optionally, carryout the following steps:
If you are going to use the CLI interface, configure the CLI tool.
Add tenants.
Tenants can be added either via the CLI, UI or REST API. For more information, see Tenant Management.Deploy partitions
Partitions can be added either via the CLI, UI or REST API. For more information, see Working with Partitions.Deploy deployment policies
Deployment policies can be added either via the CLI, UI or REST API. For more information, see Working with Deployment Policies.Deploy auto-scaling policies
Auto-scaling policies can be added either via the CLI, UI or REST API. For more information, see Working with Auto-scaling Policies.Optionally, deploy a Load Balancer as a cartridge.
A Load Balancer can be deployed as a cartridge via the CLI, UI or REST API. For more information, see Working with Cartridges and Customization based on Load Balancer.Deploy a cartridge.
A cartridge can be deployed as a cartridge via the CLI, UI or REST API. For more information, see Working with Cartridges.
If you have deployed a multi-tenant cartridge, deploy a multi-tenant service cluster; otherwise, skip this step.
If required, host artifacts in the Git repository. Ensure to maintain the required Git folder structure.
Data cartridges and application cartridges do not use artifacts; therefore, only framework cartridges require a Git repository.WSO2 Private PaaS only supports artifacts that can be deployed at run-time in a cartridge. Therefore, artifacts that require the server to be restarted after being deployed are not supported.
Optionally, enable automated deployment synchronization.
There may be instances where the artifacts in the Git repository need to be continuously developed. Automated deployment synchronization will ensure that the changes made in the Git repository are seamlessly propagated into the respective cartridge.Subscribe to cartridges
If you subscribe a single tenant framework cartridge, Stratos will retrieve the respective artifacts from the Git repository and install it in the cartridge. Thereafter, you will be able access and invoke the artifacts.
You can subscribe to a cartridge via the CLI, UI or REST API. For more information, see Subscription Management.Optionally, enable manual deployment synchronization.
There may be instances where the artifacts in the Git repository need to be updated. Manual deployment synchronization will enable you to manually propagate the Git repository changes into the respective cartridge.