Page Comparison

...

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. If you have deployed a multi-tenant cartridge, deploy a multi-tenant service cluster.

    Info
    This step is not applicable if you have deployed a single cartridge.

15. If required, host artifacts in the Git repository. Ensure to maintain the required Git folder structure.
    Only framework cartridges require a Git repository. As data cartridges and application cartridges do not use artifacts, a Git repository does not have to be maintained for such cartridges.

    Info
    Stratos only supports artifacts which can be deployed at run-time in a cartridge. Therefore, artifacts that require the server to be restarted after deploying the artifact are not supported by Stratos.

16. Optionally, enable automatic deployment synchronization.
    Generally, the artifacts in the Git repository will need to be continuously developed. Automatic deployment synchronization will ensure that the changes that are made in the Git repository are seamlessly propagated into the respective cartridge.

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

    If the cartridge that has been subscribed to is a framework cartridge, Stratos will retrieve the respective artifacts from the Git repository and install them in the cartridge. Thereafter, the user will be able access and invoke their artifacts.

18. Optionally, enable manual deployment synchronization.
    Generally, the artifacts in the Git repository will need to be continuously developed. Manual deployment synchronization will enable you to manually propagate the Git repository changes into the respective cartridge.