A presentation from the Butler Group event by ISIS Papyrus on Mashups.

1. Enterprise
2.0
meets
SOA
Max
J.
Pucher
–
Chief
Architect
ISIS
Papyrus
Copyright 2009 – Max J. Pucher

2. Wikipedia
on
Mashups
 A
Mashup
is
a
web
page
or
application
that
combines
data
or
functionality
from
two
or
more
external
sources
to
create
a
new
service.
 The
term
mashup
implies
easy,
fast
integration,
frequently
using
SOA
and
data
sources
to
produce
results
from
other
original
source
data.
 An
example
of
a
mashup
is
the
use
of
cartographic
data
to
add
location
information
to
real
estate
data,
thereby
creating
a
new
app.
 Many
see
mashups
just
for
consolidated
access.

3. Enterprise
2.0
 Enterprise
2.0
uses
web
based
technology
to
provide
collaboration,
information
sharing,
emergence
and
integration
capabilities
in
the
extended
enterprise.
 It
is
basically
Web
2.0
social
networking
and
user
interfaces
for
businesses.
 Enterprise
2.0
strategies
are
about
collaboration.
 LinkedIn
is
an
example
of
an
Enterprise
2.0
solution.
 Google
Wave
can
be
embedded
in
Mashups
for
creating
live,
social
communication
documents
that
can
be
edited
by
multiple
users
in
near
real-­‐time.

4. Different
Approaches
designed emergent
STP BPM APPS COLL. E2.0
planned ad-hoc
PROCESS
Mashup?
PEOPLE
flow oriented event driven

5. Different
Op:ons
 Mashups
expand
on
the
idea
of
end
user
portals
 Client
or
server
side
Mashup
concept
 Mashups
are
Rapid
Application
Development
 Creation
by
users
or
professionals
 Orchestration
by
means
of
flows
or
event-­‐driven
 Global
data
storage
or
only
data
passing
 Common
or
unique
page
creation
 Presentation
through
HTML,
Ajax
or
Flash
 Hosted
(SaaS)
or
non-­‐hosted
Mashup

6. Real-­‐Time
Consolida:on
HTTP
Security?
RSS
SOA
Mashup
to
Decision?
USER
Application?

7. Mashups
for
Business
 Integrate
backend
business
and
data
services.
 Employ
security
and
access
control
features,
 Uses
lifecycle
management
and
Mashup
editors.
 Business
Mashups
in
commercial
(SaaS)
offerings.
 Adopt
SOA
to
integrate
discrete
Web
service.
 Secure
versions
of
Webservices
must
be
used.
 Mashups
should
be
seen
and
managed
from
a
process
perspective
and
can
offer
more
agility
than
BPM.
 Ease
of
use
and
dynamics
for
user
empowerment.

8. 80%
of
processes
change
frequently
Survey
ques:on:
Thinking
of
the
most
impac*ul
BPM
project
your
organiza:on
is
implemen:ng
or
will
undertake,
how
frequently
will
you
need
to
change
the
process
flows
in
the
solu:on
that
supports
the
business
processes
in
your
organiza:on?
Percentage
of
Respondents
40
50%
think
that
35
changes
occur
30
30%
think
that
monthly
to
several
25
changes
occur
ad-­‐hoc
20
times
a
year.
to
weekly.
15
10
5
0
Several
Monthly
Ad
Hoc
Weekly
Once
a
Less
Than
Daily
Rarely
Don't
Know
Times
a
Basis
Year
Once
a
(Less
Than
Year
20%
think
that
Year
Once
Every
changes
once
a
year
or
Years)
Two
 Source:
2008
Gartner
Group
less
often.
Copyright 2009 - Max J. Pucher

9. One
View
of
Mashups

10. Achieving
the
dynamics
of
Mashups
without
loosing
the
manageability
of
a
business
application.

11. Mashup
Lifecycle?
End User
Requirements
Mashup
Editor
SOA,
RSS
Services
Execution
Infrastructure
system needs business needs

12. How
to
Reuse
Mashups?
Mashup
Implementation
Business
Needs Business
Process
Entities
Rules
Organisation Repository
Security/LDAP Lifecycle SOA/RSS
Interfaces
Presentation
Production
Deployment
Content
In/Out Archive
Auditing
Februar 10 Copyright 2007 - Max J. Pucher 12

13. Mashup
Role/Policy
Security
Monitoring
Logging SOA
Information
Access
User Owner
attributes Policy
Access
rights
in
a
virtual
Mashup
application
Policy
Authorization and
delegation
Service Policy Policy enforcement
Copyright 2009 - Max J. Pucher

14. Empower
Users
with
Widgets
Toolbar
 Assign
roles
to
queues
 Create
tasks/activities
 Define
states
&
events
Queue
Widget
List
Widget
 Create
perspective
Perspective
 Select
SOA
backends
 Map
to
widget
Detail/Chart
Widget
 Select
content
 Activity
recorder
 Define
boundary
rules
 Group
test
and
signoff
Repository
 Publish
task
 Automatic
deployment
Copyright 2009 - Max J. Pucher

15. Portal Services
Inbound
Outbound
GUI
Content
Mashup Widgets
Archive
Repository
GUI OO-Messaging
MOD
XDO MQ SOAP
WSDL
SERV Adapter Adapter Adapter
PROC
ERP or legacy Third-Party
DOCS Databases MQ Adapter WebServices
Copyright 2007 - Max J. Pucher

16. Mashup
Enterprise
Checklist
 Version-­‐controlled,
central
repository
of
model
templates
that
enables
definition
changes
to
be
deployed
using
a
change
management
life-­‐cycle.
 Assembled
from
predefined
template
elements,
including
content
and
business
entities
that
are
real-­‐
time
linked
to
business
applications.
 Controls
user
access
based
on
role/policy,
not
dependent
of
organization
or
GUI/forms
definitions.
 Performance
Monitoring
and
Tuning
 Embedding
inbound/outbound
business
content
 Businesses
require
archiving
and
auditing

17. Conclusion
 Mashups
were
very
hot
in
2006/7.
Recently
cooled
…
 They
showed
a
clear
need
for
very
dynamic
user
empowered
applications
that
linked
various
backends.
 Most
Mashups
lack
enterprise
level
features.
 With
the
introduction
of
Papyrus
EYE
Widgets
in
1Q2010
business
administrators
can
create
Mashups.
 These
have
however
the
complete
enterprise
management
layer
of
the
Papyrus
Platform
available.
 It
allows
the
consolidation
of
BPM,
Case
Mgmt,
and
Mashup
style
RAD
application
development.

18. A
one
minute
demo
of
how
to
create
a
Mashup
user
interface
with
Papyrus
EYE
Widgets.
Any
questions?