1. Develop, Test and
Deploy your SOA
Application through a
Single Platform
Chathuri Wimalasena
Senior Software Engineer
WSO2 Inc

2. WSO2 Carbon Platform

3. How WSO2 Carbon Studio connects
with the Carbon platform

4. Platform Capabilities
● WSO2 Carbon is a complete platform that
provides,
– Service Hosting
– Message Mediation
– Managing Data Sources and Data Access
– Authentication and Access Control
– Repository for managing WSDL, Schemas,
Policies, Life Cycles and Versioning
– Composing, Orchestrating Business
Processes
– Portal Services

5. How Platform Capabilities are
supported by Carbon Studio
● What Carbon Studio provides
– Service Hosting
● Apache Axis2 Services
● JAX-WS Services
● Web Apps
– Message Mediation
● Sequences, Proxy Services, Endpoints,
Local Entries
● Data Transformations
● Custom Mediators

6. How Platform Capabilities are
supported by Carbon Studio
● Managing Data Sources and Data Access
– Data Services
– Data Services Validators
● Repository Management
– Registry Resources
– Managing Repository
– Registry Handlers, Filters, Aspects

7. How Platform Capabilities are
supported by Carbon Studio
● Composing, Orchestrating Business
Processes
– Creating Complex Business Processes
● Portal Services
– Creating Gadgets
– UI Bundles

8. Carbon Application (C-App)
● Carbon Application is a container for
deployable items such as axis2 services,
ESB configurations, web apps etc.
● Analogy – Java project

9. Carbon Application (C-App)

10. C-App Artifact

11. C-App Artifact

12. C-App Artifacts

13. WSO2 Carbon Studio - One Stop
Tooling Platform
● Develop
● Deploy
● Debug
● Test
Both on Premise and on Cloud

14. Develop
● Can create all kinds of SOA Applications
● Being a Java IDE
– Content Assist
– Rich Editors and Views

15. Develop

16. Deploy
● Support for all the servers in product stack
– Local Servers
– Remote Servers
– StratosLive
● Provide unified way to add servers and
deploy C-Apps

17. Deploy

18. Deploy

19. Deploy

20. Deploy

21. Debug & Test
● Server Hot Update
● Start Servers with OSGi console enabled
● Redeploy
● Debug Applications

22. Debug & Test

23. Debug & Test

24. Debug & Test

25. Debug & Test

26. Deployment Model
● Packaging
– As a Carbon Application Archive (CAR)

27. Deployment Model
● Server Types
– Server Roles

28. Life Cycle Management
● Dev
● QA
● Staging/Prod

29. Life Cycle Management
● Suppose we have a multi user project

30. Life Cycle Management
● Dev Environment
– Collaborative Development
– Use SVN
– Develop the application
– Create the CAR which can be used by all
the devs
– Test the application with test data and in
local set-ups
– After dev testing, application will hand
over to QA

31. Life Cycle Management
● QA Environment
– Application can be given
● Manually
● Using G-Reg
– Dev and QA will get notifications
– Create the CAR file using Maven, if the
application is given as a C-App
– Application will be tested using Real Data
and Real Traffic

32. Life Cycle Management
● Staging/Prod Environment
– Option 1 : Manual Deployment
● Registry Configuration
– Check out from QA/ Check in to Prod
● Axis2 Repository
– Copy from QA
– Option 2 : Usage of CAR
● Use the same CAR as QA

33. Samples

34. Licensing
● Apache 2.0 Software License

35. Wrap-Up
● One Stop Tooling Platform
● Support to develop End to End SOA
Applications on Premise and on Cloud
● Easy to Use
● Support as an Eclipse Plugin
– Eclipse + CS + 3rd Party Plugins
● Application Life Cycle Management

36. Q/A