A-Z Guide

The quick start guide demonstrates how to get started with WSO2 Private PaaS in 15 minutes using a demo AMI. The A-Z (A to Z) 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:

1. Ensure that the installation prerequisites have been met prior to the WSO2 Private PaaS installation.

2. 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/

3. Create a cartridge.

4. Configure the product using one of the following approaches:
   

   • Configure the product using the automated approach.

   • Configure the product using the manual approach.

5. Optionally, carryout the following steps:

   1. Manually configure a load balancer

   2. Configure WSO2 Private PaaS for high availability

6. Change your default super tenant admin password.

7. If you wish to use the CLI interface, configure the CLI tool.

8. Add tenants.
   Tenants can be added either via the CLI, UI or REST API. For more information, see Tenant Management.

9. Deploy partitions
   Partitions can be added either via the CLI, UI or REST API. For more information, see Working with Partitions.

10. Deploy deployment policies
    Deployment policies can be added either via the CLI, UI or REST API. For more information, see Working with Deployment Policies.

11. 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.

12. 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 A-Z Guide.

13. 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.
    

14. Subscribe to cartridges
    A user can subscribe to a cartridge via the CLI, UI or REST API. For more information, see Subscription Management.