This document discusses building and deploying software as a service (SaaS) applications using the WSO2 Application Server as-a-Service. It begins with an overview of WSO2 Stratos and why to choose it over other platforms as a service vendors. It then describes the key features of the WSO2 Application Server as-a-Service and what is needed to build SaaS applications, including identity management, billing, logging, caching, and data services. A demo is outlined showcasing tenant creation, building a web app, hosting it on the platform, securing it, and exposing apps as SaaS.

1. Building and Deploying SaaS
Applications with the WSO2
Application Server as-a-Service
Kishanthan Thangarajah
Software Engineer

2. Agenda
• What is WSO2 Stratos?
-Key Features
• Why choose WSO2 over other PaaS vendors?
• What is WSO2 Application Server as a Service?
-Key Features
• What is needed when buiding and deploying
SaaS?

3. Demo
• Creating a tenant and having it up and running
with all SOA features
• Building a web application and hosting it in
WSO2 Application Server as-a-Service.
• Using WSO2 Developer Studio to build and host
the web application
• Securing the web application
• Exposing web applications as a SaaS

4. What is Platform as a Service?

5. WSO2 Stratos
WSO2 Stratos is WSO2’s Cloud Middleware Platform(CMP)
• A complete SOA platform
• In private cloud or public cloud
• 100% Open Source under Apache licence
• Can run on top of any Cloud IaaS
WSO2 StratosLive is the PaaS offering by WSO2
Significantly ahead of the competition
• Stratos is the only 100% Open Source, Open Standards option
Based on OSGi - modular, componentized, standard

6. Cloud Native features supported in
Stratos
• Elasticity
• Multi-tenancy
• Billing and Metering
• Self Provisioning
• Incremental Testing

7. Why choose WSO2 over other
PaaS vendors?
• Private and public offering
• Architecture
• Free of lock-in

8. WSO2 Application Server
• Enterprise ready Web Services and Web Application
container
• Successor of the WSO2 Web Services Application
Server(WSAS)
• Powered by Apache Axis2 and Apache Tomcat
• Open source (Apache Software License v2.0)
• Supports almost all WS-* standards
• Runs standalone or on top of Tomcat, WebSphere,
WebLogic and Jboss
• High performance

9. Key Features
• Web Services deployment and management
• Web Application deployment and management
• Full support for WS-Security, WS-RM, WS-Trust etc.
• Clustering support for High Availability and Scalability
• Tooling support from WSO2 Developer Studio
• Easy to use management console
• Hot Deployment/Hot Update of services
• Highly extensible architecture
• WSDL2Java, Java2WSDL, WSDL Validator and Try-It tools
• User management
• Ability to install any Carbon feature

10. New features included from next
release
JAX-WS and JAX-RS support with Apache CXF
Support forJaggery apps
Support for Mashup/Gadget services

11. WSO2 Appication Server as-a-Service
• Multitenanted WSO2 AS running on the cloud
• Support for multitenant tomcat
• In built support for cloud native features
• Integration with WSO2 Identity Server as-a-
Service
• Lazyloading support for tenants and artifacts
-Services
-Webapps

12. Lazy loading of artifacts - webapps

13. Things needed to build a SaaS
• If you are software vendor, you may wish to
create SaaS applications
• You need :
 Easy way to build and deploy applications
 Identity (multi-tenant)
 Billing + metering
 Logging
 Cache
 Data
• WSO2 offers all of these

14. Demo
• Creating a tenant and having it up and running
with all SOA features
• Building a web application and hosting it in WSO2
Application Server as-a-Service.
• Using WSO2 Developer Studio to build and host
the web application
• Securing the web application
• Exposing web applications as a SaaS

15. Using WSO2 Carbon features with Webapps
• WSO2 Carbon is the base platform on which all WSO2
products are developed
• Standalone Carbon server runs on top of an embedded Tomcat
instance
• Carbon itself is a single Webapp which is running on Tomcat
• Other webapps are also deployed in parallel with the Carbon
Webapp
• Some API’s are shared across all Webapps to make important
Carbon features available for external Webapps as well
• Authentication
• Registry (Metadata Repository)
• Carbon Caching

16. Using Carbon
UserManagement/Authentication API
Demo

17. Things to Consider when writing
applications in StratosLive
• Can’t access file system
• Can’t listen in a socket, port
• No changes to server states
• Restrictions in using threads
• Don’t assume there will be only one instance

18. Questions?

19. Thank You !