From Spaghetti to Lasagne
7 December 2009
K
What will you do in 5 years?
from spaghetti to lasagne
CTAC
• Ctac is present in Belgium (2004) and the Netherlands (1992): its
consulting force amounts up to 500+ consultants of which 120 in
Belgium, mainly in SAP & Business IT
• Ctac offers a full range SAP Services Portfolio
– Implementation (various predefined template solutions
available)
– Application Maintenance & Hosting
– Business Consulting, Improvement & Optimisation
• Ctac is SAP Partner in multiple areas & SAP AiO (VAR) Partner in
the Benelux
• The Ctac holding is noted on the Amsterdam stock market
(euronext).
CTAC Enterprise Technology Management
focusses on:
SAP NetWeaver, eSOA and integration with SAP-systems
•
Optimizes business processes with SAP NetWeaver as a basis
•
Raises productivity by using the SAP portal and composites
•
Integration of processes and applications using PI
•
Maintains qualitative Master Data with MDM
Agenda
• What is Enterprise SOA and why is
that important?
• What is Sap NetWeaver and where are
we now?
• Sap NetWeaver technology in some
more details
• The impact of eSOA on the IS
organisation
Objectives
• Obtain an understanding of:
– the rationale behind SAP’s SOA strategy;
– the role and components of a technology platform;
– NetWeaver as supporting technology platform for implementing
SOA;
– the challenges the technology brings and its impact on IS
organisations
Agenda
• What is Enterprise SOA and why is
that important?
• What is Sap NetWeaver and where are
we now?
• Sap NetWeaver technology in some
more details
• The impact of SOA on the IS
organisation
Strategic drivers for change
Past
Present : 2010
• Focus on Internal efficiency
• Focus on business networks
• Less users with special training
• Lots of “casual” users
• “One-size-fits-all” solution
• Industrial-specific processes
• Standardization, cost savings
• Business performance, grow!
Differentiation
Core
Support
Strategic importance of your processes
Differentiation Matrix
Identifying the Need for Change
Business Driver
• Strategic
differentiation
• Investment
Focus
IS Enabler
• Service
based
Platforms
• Agile
Development
• Assemble
/Build
Business Driver
• Internal Efficiency
• Cost Focus
IS Enabler
• Best Practice based packaged
application
(ERP, CRM, SCM,…)
• Buy
Process execution compared to your competitors
Under
perform
Market
perform
Out
perform
Application Development with SAP
Internal reflection
• SAP recognised that customers were asking more than only
ERP and dull GUI screens that nobody seemed to like
anymore.
• SAP recognised that customers were looking for application
platforms based upon open standards; applications that
could easily interoperate with other applications within the
company and with external systems.
• SAP recognised that Java and .Net were strong development
languages highly adopted by the development community.
• SAP recognised that Service Oriented Architectures would
be the next hype in techno land.
Service Oriented Architecture: a new
hype?!
SOA
SOA is the new Architecture for everyone
It is not invented by SAP
Some SOA misconception
• SOA is a new technology
• SOA is a marketing term
• Webservices = SOA
• Everything should be a webservice
• The more webservices, the better
• It is not possible to start with small projects
• SOA is still immature
The term “SOA” in wikipedia
•
Service Oriented Architecture (SOA) is an architectural style that guides all aspects of
creating and using business processes, packaged as services, throughout their
lifecycle, as well as defining and provisioning the IT infrastructure that allows different
applications to exchange data and participate in business processes regardless of the
operating systems or programming languages underlying those applications. SOA
represents a model in which functionality is decomposed into small, distinct units
(services), which can be distributed over a network and can be combined together
and reused to create business applications. These services communicate with each
other by passing data from one service to another, or by coordinating an activity
between one or more services.
1. SOA is an architectural model, not a technology
2. Enterprise Service Bus (ESB)
3. Services are often executed as Web Services
Lego and SOA
What is a Service
Definition :
“A callable software component that is self-contained
and self-describing and that is accessed via the
exchange of messages. A service has a clearly
defined interface.”
Web Services:
• Act as a blackbox with obligatory input and a fixed
result
• Can be published and called based on open
technology standards (HTTP, XML)
• Works in synchronous and asynchronous scenarios
• A Web Service allows simple communication
between different systems since it is using simple
text messages in stead of complex and costly to
maintain RPC.
Stand alone
No guarantee
No Governance
What is an Enterprise service?
Definition :
“An Enterprise Service is a service with the SAP
Business logic!”
eSOA is SAP specific
Business logic
Scalable
defined repository
https://www.sdn.sap.com/irj/sdn/esworkplace
Components of a Web Service
Yellow
Pages
HTTP(S)
Service
Discovery
UDDI
Service Directory
WSDL
HTTP(S)
Service
Publication
WSDL
Service
Execution
Web Service
Consumer
e.g. J2EE Web
Application
HTTP(S)
SOAP
e.g. ‘Create Order’
Web Service
Provider
e.g. R/3
Summary
•
SOA is an architectural model, not a technology
•
Services are often executed as webservices
•
Platform independent
•
Services and enterprise services (sap: eSOA)
•
Enables possibilities (www.webservices.nl , www.xmethods.com
,…)
Agenda
• What is Enterprise SOA and why is
that important?
• What is Sap NetWeaver and where are
we now?
• Sap NetWeaver technology in some
more details
• The impact of eSOA on the IS
organisation
Application Platforms
An Application Platform is an out-of-the-box integrated suite of
common infrastructure services to build, integrate and run
applications.
Process (Collaboration, Workflow, etc)
Integration
Application
Service
Application
Service
Application
Service
Common Data/Information
Application
Service
Lifecycle management &
Security
Solution modelling &
development
Channels (Portal, Kiosk, Smartphone, etc)
Netweaver History
• SAP NetWeaver™ technology platform is an integration, application
and business process platform which helps with:
– Reducing the total cost of ownership
– Facilitating integration and orchestrate Information, People and
processes across departments and technologies.
• SAP NetWeaver is the technical basis for mySAP™ Business Suite
and SAP® xApps™ and is a Webservices-based platform
A visual overview
SAP has transformed its SAP
proprietary Basis Platform into an
Application Platform “NetWeaver”
BI
…
SRM
CRM
R/3
SAP Basis / ABAP WB
SAP’s core business used to be
providing best practice functionality
for different business areas
And revolutionised its
business suites by making
functionality available as
enterprise services.
With NetWeaver 2004S, SAP has
realised :
A fully integrated and SOA based
Application Platform supported by a rich
repository of out-of-the-box application
services.
Putting all components together
The Strategic value of SAP NetWeaver as
Business Process Platform
The essence !
From Spaghetti to Lasagne
Swaps
Systems
Cash Flow
System
G/L
IRS
How does eSOA work in practice?
Presentation Platform
Portal , mobile, ..
Employees
Suppliers
Customers
Process orchestration
platform
ccBPM, CAF, ARiS
Integration platform
PI/XI
Data platform
SAP,…
SAP
Non SAP
APO
CRM
Non SAP
IT challenges are considerable
• Enable service of existing legacyapplications is difficult
• Spaghetti of GUI, workflow,
business logic and data
• Parallel use of new services and
old transactions
• How define services (granularity)?
• ESB is complex technology
• Qualified competencies needed
• ESB is very flexible: ‘create your
future mess…’
Swaps
Systems
Cash Flow
System
G/L
IRS
In practice
Its not simple:
• A lot of acronymes, standards and technologies
• Every vendor has SOA solutions
• How to justify IT-investments with the business?
• Is there a shot-term business value?
• Where to start?
Technical issues (to expect!)
•
•
•
•
Security
Performance
maintenance
….
Summarising: Cooking with many
ingredients
From Proprietary SAP Basis to an Open
Integration Platform
Agenda
• What is Enterprise SOA and why is
that important?
• What is Sap NetWeaver and where are
we now?
• Sap NetWeaver technology in some
more details
• The impact of eSOA on the IS
organisation
Application Development with NW
Java Stack
ABAP Stack
•
•
•
•
•
•
Java/JEE
Webdynpro Java
Visual Composer
Adobe (Interactive) Forms
Adobe Flex
Composite Application
Framework
• Guided procedures
• Portal iViews
•
•
•
•
•
•
• NetWeaver developer Studio
(NWDS)
• NetWeaver development
Infrastructure (NWDI)
• ABAP Workbench
ABAP
Webdynpro ABAP
BSP
Business Workflow
Adobe (Interactive) Forms
Adobe Flex
What does this mean in practice?
NWDS the toolbox for custom development
• NetWeaver Developer Studio (NWDS) is a development
environment similar to MS Visual Studio or IBM’s Rational
Application Developer.
• NWDS is build on Eclipse – an open source integrated
development environment and a standard in the Java
community.
• With NWDS developers can develop Java and J2EE
applications.
• NWDS has a number of plugins for creating:
–
–
–
–
Web services
Web applications
Java iViews for the SAP Portal
Composite services
With NWDS a Java developer can develop custom applications.
NetWeaver Developer Studio
How does it look like?
Eclipse based IDE
Model Driven Development
IT practices – IT scenarios
IT Scenarios
IT Practices
User Productivity
Enablement
Data Unification
Business Information
Management
Business Event
Management
End-to-End Process
Integration
Custom Development
Unified Life-Cycle
Management
Application Governance
& Security
Consolidation
Enterprise Service
Architecture – Design &
Deployment
Running an Enterprise
Portal
Master-Data Harmonization
Enabling User
Collboration
Business Task
Management
Master-Data Consolidation
Enterprise Reporting, Query, and
Analysis
Mobilizing Business
Processes
Central Master-Data
Management
Business Planning and Analytical
Services
Business Event Resolution
Enterprise Knowledge
Management
Enterprise Data Warehousing
Enterprise Data Warehousing
Business Task Management
Enabling Application-to- Enabling Business-toApplication Processes Business Processes
Business Process
Management
Enabling Platform
Interoperability
Business Task
Management
Developing, Configuring, and Adapting Applications
Enabling Platform Interoperability
Software Life-Cycle Management
SAP NetWeaver Operations
Authentication and Single Sign-On
Integrated User and Access Management
Enabling Platform
Interoperability
SAP NetWeaver Operations
Master-Data Consolidation
Enabling Enterprise Services
Enterprise Knowledge
Management
User Productivity
User Interfaces
Today
Future: service-oriented architecture
SAP GUI Family
User Clients & Access
SAP GUI for Java
SAP GUI for Win
SAP GUI for HTML
NW BC
NW Portal UI / Browser
SAP NetWeaver Portal
Browser
UI Services
UI Services
Roles
Navigation
App Help
Roles
Navigation
App Help
Page Builder
Work Center
Printing
Page Builder
Work Center
Printing
Rendering
Personaliz.
…
Rendering
Personaliz.
…
CE the toolbox for Composites
development
• The Composition Environment (CE) is an application
development environment for building composites.
• Composites are a new type of applications and are
characterised by
– Process driven through Guided Procedures
– An adapted user friendly UI for executing a task
– Invoking web services from the ERP backend
• Composites are build using Visual Tools (Visual Composer,
Adobe Forms) and Java for the more complex UI.
• Simple composites can be assembled without any coding.
With CE Java developers can automate processes across departments and
across companies. Simple composites can be assembled by Bus. Analysts.
A Sample Composite scenario
Maintenance order processing
SAP NetWeaver Composition Environment
How does it work?
SAP for Everyone
Duet - seamless access to SAP through Microsoft Office
www.duet.com
Leave
Management
Reports &
Analytics
Sales
Management
Organization
Management
Travel
Management
Time
Management
Budget
Monitoring
Demand
Planning
Purchasing
Management
IT Scenarios
IT Practices
User Productivity
Enablement
Data Unification
Business Information
Management
Business Event
Management
End-to-End Process
Integration
Custom Development
Unified Life-Cycle
Management
Application Governance
& Security
Consolidation
Enterprise Service
Architecture – Design &
Deployment
Running an Enterprise
Portal
Master-Data Harmonization
Enabling User
Collboration
Business Task
Management
Master-Data Consolidation
Enterprise Reporting, Query, and
Analysis
Mobilizing Business
Processes
Central Master-Data
Management
Business Planning and Analytical
Services
Business Event Resolution
Enterprise Knowledge
Management
Enterprise Data Warehousing
Enterprise Data Warehousing
Business Task Management
Enabling Application-to- Enabling Business-toApplication Processes Business Processes
Business Process
Management
Enabling Platform
Interoperability
Business Task
Management
Developing, Configuring, and Adapting Applications
Enabling Platform Interoperability
Software Life-Cycle Management
SAP NetWeaver Operations
Authentication and Single Sign-On
Integrated User and Access Management
Enabling Platform
Interoperability
SAP NetWeaver Operations
Master-Data Consolidation
Enabling Enterprise Services
Enterprise Knowledge
Management
Traditional integration = exponential
complexity
Complex Integration Landscapes
Point-to-Point Integration (‘spider-web’)
Different
integration
technologies and
middleware tools
Many direct 1-to-1
connections,
hardwired into
application
components or
mapping programs
SAP
SAP
Distributed
integration
knowledge, hidden
within the different
application or
middleware tools
used
SAP
3rd Party
SAP
EAI
DB
BPM
tool
B2B
Business
Partner
Application
B2B Tool
HardCoded
3rd Party
3rd Party
Heterogeneous system
landscape with SAP and nonSAP applications
Business Partners
Need for business
process
management to
control the many
manual processes
Other
integration
solution
SAP
MF
Adapter
Market
Place
Integration needs inside and
outside the corporate
boundaries for A2A and B2B
scenarios
Process Integration platform
Hub and Spoke Architecture
Less connections
SAP
SAP
SAP
DB
Integration
and
BPM
platform
Business
Partner
Application
B2B Tool
3rd Party
Business
Process
Management
facilities
3rd Party
SAP
SAP
3rd Party
Disadvantage:
Single Point of
Failure (SPOF)
MF
Market
Place
Business Partners
Centralized
storage of
integration
knowledge
Other
integration
solution
Process Integration Platform
Enterprise Service Bus
ESB
Service
ESB
Service
ESB
Service
SAP
SAP
DB
SAP
SAP
Other
integration
solution
Bus System - Integration and BPM platform
Business
Partner
Application
B2B Tool
3rd Party
3rd Party
MF
SAP
Market
Place
Business Partners
3rd Party
Positioning - Integration Product Checklist
Categories Courtesy Jess Thomson, Research Director, Gartner Research Functionality Coverage
Process Integration (PI)
The Enterprise Services Repository
IT Scenarios
IT Practices
User Productivity
Enablement
Data Unification
Business Information
Management
Business Event
Management
End-to-End Process
Integration
Custom Development
Unified Life-Cycle
Management
Application Governance
& Security
Consolidation
Enterprise Service
Architecture – Design &
Deployment
Running an Enterprise
Portal
Master-Data Harmonization
Enabling User
Collboration
Business Task
Management
Master-Data Consolidation
Enterprise Reporting, Query, and
Analysis
Mobilizing Business
Processes
Central Master-Data
Management
Business Planning and Analytical
Services
Business Event Resolution
Enterprise Knowledge
Management
Enterprise Data Warehousing
Enterprise Data Warehousing
Business Task Management
Enabling Application-to- Enabling Business-toApplication Processes Business Processes
Business Process
Management
Enabling Platform
Interoperability
Business Task
Management
Developing, Configuring, and Adapting Applications
Enabling Platform Interoperability
Software Life-Cycle Management
SAP NetWeaver Operations
Authentication and Single Sign-On
Integrated User and Access Management
Enabling Platform
Interoperability
SAP NetWeaver Operations
Master-Data Consolidation
Enabling Enterprise Services
Enterprise Knowledge
Management
Master data is crucial to the business…
…but every department has a different version of
it.
Master data is
data about
customers,
products,
suppliers, etc.
Business partner
data introduces
yet another
version of data.
Inaccurate data
leads to $ 30+
billion cost on
supply chains.
Why do we need Master Data
Management?
• To ensure optimized processes with data that is always upto-date (real-time enterprise)
• To reduce the costs of maintaining and correcting data
through standardized processes and central management
• As a prerequisite for service oriented architectures
– With true master data, Web services and the related business
processes will become more accurate, timely, and efficient,
leading to improved ROI on existing investments as well as
improved business intelligence.”
– Forrester Research, 2006
Role of MDM in the transition towards SOA
• Enabling the reuse of functions as enterprise services in order to
eliminate functional redundancy, which is one of the main
objectives of SOA, is only possible if these functions are based on
a single source of master data.
• Process steps can only be combined if the same master data
structure is used.
• Moving master data into a MDM system helps decouple data,
processes and user interface even further. Current systems don’t
effect a clear separation of data, processes and UI (e.g. data is
used for process management, or the UI affects the master data
structure).
• The ideal level of separation is achieved by having clearly defined
boundaries between mater data management, enterprise services
(process) and the user interface.
Summarising
Duet
Agenda
• What is Enterprise SOA and why is
that important?
• What is Sap NetWeaver and where are
we now?
• Sap NetWeaver technology in some
more details
• The impact of SOA on the IS
organisation
The impact of SOA on the IS organisation
In order to archive the main challenges that involves Enterprise SOA
solutions you need to define the following topics:
New Methods
New Roles
New Organisation
How we implemented SAP projects
Implementation based upon
•Standard SAP
•Custom Development
Fit/Gap assessment
with SAP standard
Business Requirements
How we will implement SOA projects
Implementation based upon:
•Services (business logic)
•User Interface
•Composite Applications
Functional Design
Business logic + User Interface
Functional Mapping
(ESR and SAP business suites)
Process optimisation
Business Requirements
What does this means for our functions
The new roles!
•
•
•
•
•
•
Basic consultant
Technical consultant
Functional consultant
Project manager
Business consultant
Management
Business process Experts
Enterprise architects
Service repository keeper
Business analysts
Disruptive innovators
x-apps composers
Consolidators
Role 3
Role 2
EP
MS IE
XI
Integration
Specialist
APPLICATIONS
Functional
consultant
Developer
mySAP Business Suite
Non SAP
…..
SAP GUI
Enterprise Architect
Role 1
UI Interface developer
CLIENTS
Landscapes and Roles
Today
…
BI
EP
XI
Disruptive
Innovator
Business
Process
Expert
WebAS
Repository
Keeper
Consolidator
Service Developer
mySAP Business Suite
Non SAP
….
Adobe
Enterprise Architect
MS IE
UI Interface Designer
SAP GUI
Role n
BACKEND
BACKEND
TECHNOLOGY /PROCESSES
CLIENTS
SOA Landscapes and Roles
Tomorrow
Role 1 Role 2
Questions?
K