This document discusses increasing development velocity in a connected business environment using WSO2 tooling. It describes how a connected business requires APIs, events, services, and easy connections. It also requires mobile access, developer portals, integration with social forums, collaborative features, and business activity monitoring. WSO2 tooling can improve velocity by providing a single interface for products, handling complexity, being intuitive, adhering to standards, and promoting reuse. The tooling supports products like ESB, BPEL, and Jaggery with graphical editors and seamless deployment. Future plans include strategic development tools for the platform and artifact distribution servers.

1. Increasing
Development
Velocity
in
a
Connected
Business
Environment
with
WSO2
Tooling
PlaAorm
Shiroshica
Kula-lake
Architect
WSO2

2. Agenda
• Connected
business
in
a
nutshell
• Development
requirements
in
a
connected
business
environment
• Using
WSO2’s
tooling
op-ons
in
a
connected
business
environment
• Future
roadmap
for
WSO2
tooling

3. Connected
Business

5. In
order
to
build
a
connected
business
..
• API
centric,
event
driven,
service
oriented,
easy
connec-on
interfaces
amongst
different
products,
self
service
• Mobile
access
and
user
engagement
plaKorms,
developer
portals
and
developer
self
service,
integra-on
with
social
forums
• Collabora-ve
features
such
as
stores
&
dashboards,
enable
devops
prac-ces,
ac-vity
based,
tenant
aware
• Business
ac-vity
capture,
monitor,
store
&
analyze,
adapta-on
based
on
ac-vity
to
deliver
automated
no-fica-ons,
business
process
execu-on

6. In
order
to
build
a
connected
business
..

7. Connected
Business
Reference
Architecture

8. Developing
in
a
Connected
Business
Environment

9. Development
Requirements
in
a
Connected
Business
Environment
• Support
all
core
products
used
within
the
business
Provide
the
capability
to
create
product
configura-on
Provide
the
capability
to
create
product
ar-facts
• Handle
ar-fact
deployment
seamlessly
• Provide
developer
velocity
through
tooling

10. Improving
Development
Velocity
with
Tooling
• Providing
a
single
tool
with
similar
interfaces
for
a
variety
of
products
• Allowing
the
tooling
to
handle
most
of
the
complexity
• Adop-ng
a
tool
which
is
intui-ve
to
use
• Using
a
tool
which
is
widely
accepted
and
adheres
to
industry
standards
• Connec-ng
to
industry
wide
accepted
build
tools
• Promo-ng
reuse
of
ar-facts
• Providing
facility
to
debug
and
deploy
ar-facts

11. WSO2
On
Premise
Tooling
in
Ac-on

12. Sample
Connected
Business
Applica-on

13. Providing
Tooling
Support
for
Core
Products

14. Seamless
Ar-fact
Deployment

15. ESB
Graphical
Editor

16. ESB
Graphical
Editor
–
With
connectors

17. BPEL
Graphical
Editor

18. Jaggery
Editor

19. WSO2
Cloud
Tooling
in
Ac-on

20. Sample
Cloud
development
Applica-on

21. WSO2
tooling
for
App
Cloud
with
Codenvy

22. WSO2
tooling
for
App
Cloud
with
Codenvy

23. What
Next

24. Roadmap
ahead
• Improvement
for
tooling
in
exis-ng
products
and
scenarios
• Strategic
on
premise
Development
tool
for
the
en-re
plaKorm
Deprecate
development
features
from
management
console
• Ar-fact
Distribu-on
Server
for
deployment
ease
• Tooling
for
the
integra-on
cloud

25. Ques-ons
?

26. Thank
you
!