5/18/2007 SOA evolution a high level Business Architecture View Page 1 SOA evolution A high level Business Architecture View Rudi Chati Senior Integration Architect Unisys APLA – Enterprise Solution Services This session will discuss the technology and strategic steps for IT modernisation and integration with/without transformational approaches for the ClearPath system. The technology building blocks and their positioning on the "road" to SOA will be shown embedded in the strategic steps of the application modernisation. This should allow high level conclusions on the business value and versatility of the ClearPath systems in the SOA environment. Unisys Technology Forum Queenstown – New Zealand May 1417, 2007
24
Embed
Rejuvenate the application environment · Senior Integration Architect ... important for performance, agility, scalability, resource usage, etc. ... EIS (SAP, PeopleSoft, etc.) Legacy
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
5/18/2007 SOA evolution a high level Business Architecture View Page 1
SOA evolution A high level Business Architecture View
This session will discuss the technology and strategic steps for IT modernisation and integration with/without transformational approaches for the ClearPath system. The technology building blocks and their positioning on the "road" to SOA will be shown embedded in the strategic steps of the application modernisation. This should allow high level conclusions on the business value and versatility of the ClearPath systems in the SOA environment.
Unisys Technology Forum Queenstown – New Zealand May 1417, 2007
5/18/2007 SOA evolution a high level Business Architecture View Page 2
Rejuvenate the application environment Services enable composite applications
Portals
Packaged Apps
BPM Lack process automation
Hard coded Functional silos
Not for collaborative Or ad hoc activity
Flexibility Business focus
Packaged processes
Composite Applications
Manageability: Governance Provisioning Tooling Documentation Quality of Service
We add:
Process automation ITAutomation
We add:
5/18/2007 SOA evolution a high level Business Architecture View Page 3
“Organizations committed to providing vital utility and transactional business functions are increasingly evaluating serviceoriented architectures to modernize their mainframe systems. This new interest is driving vendors to provide solutions to extend and reuse mainframe systems.”
“Organizations with a strategic commitment to this platform are increasingly evaluating a serviceoriented architecture (SOA) as a modernization strategy for their mainframe systems. This growing interest has also driven renewed interest in providing these services directly on the mainframe platform.”
“These mainframe resident integration solutions are increasingly focused on wrapping current transactions or data as a Web service, publishing mainframe based business events or providing the capability to consume any Web service within current mainframe transactions.”
Gartner – Excerpts from research report published 10/26/2005 “Mainframe Integration Emerges as a Growing Market Opportunity”
5/18/2007 SOA evolution a high level Business Architecture View Page 4
ServiceOriented Architecture
SOA Principles & Guidelines
SOA Methods & Tools
SOA Governance Policies & Processes
Approved Products, Technologies and Facilities BPM Client UI Data Transform
5/18/2007 SOA evolution a high level Business Architecture View Page 5
Analysts on Mainframe integration
5/18/2007 SOA evolution a high level Business Architecture View Page 6
The top SOA considerations 1. Don't throw everything out. 2. Don't bite off big projects all at once. 3. Don't forget to set expectations. 4. Don't just do technology it is a transformation of the way you do business. 5. Don‘t just „wrap“ with standards –
1. achieve reuse and integration quickly 2. embed in real life business scenario mitigate risk of experiencing problems at the
application level
6. incremental process – 1. wrap services that are working well and deliver value to the business now 2. rebuild/redeploy other services at your pace and depending on new requirements
7. focus on reuse – 1. reduces complexity within the IT system 2. segregate set of core mission critical application services reusable or globally used across
applications and business processes 3. better operating efficiency and reduced maintenance cost
5/18/2007 SOA evolution a high level Business Architecture View Page 7
Excerpts: “Mainframe organizations have faced a decade of negative perception, predictions of obsolescence and general market derision.” “The market hype surrounding serviceoriented architecture (SOA), as well as the growing awareness of the limitations of alternative hardware/software platforms, is leading many mainframe organizations to reevaluate their decision to abandon, or at least marginalize, the mainframe platform.” “Gartner recommends that every mainframe organization begin the strategic process of determining the longterm role of this platform in its overall application architecture.” “For those organizations uneasy about incurring the cost and risks of migration from mainframe platforms, SOA may provide a tactical modernization solution … “ “Furthermore, we recommend an immediate tactical approach to reuse established applications as "pseudoservices." …
Gartner – research report published 10/25/2005 “Leverage your Mainframe Applications with SOA”
5/18/2007 SOA evolution a high level Business Architecture View Page 8
Achieving reusable services via “segregation” of common business supporting functions Modernisation by creating reusable services
Application
Monolithic applications
Application
1
5/18/2007 SOA evolution a high level Business Architecture View Page 9
• Services are “Selfcontained” functional units taking care of their own state • Process steps are interactions not multiple atomic system transactions • Process steps are not an individual sequence of transaction executions • Service domains should be created to be reused from different processes • Business services can include multiple technical services
5/18/2007 SOA evolution a high level Business Architecture View Page 10
From the “groundwork” a SOA “bus”
Orchestration, Routing, Transformation, BAM
Intermediate stage: Individual services broken out
Application
Application
service
service
2
Application
Application
service
Serviceoriented architecture “groundwork”
service
service
service
service
3 4
Application
Application
service
service
service
service
service
(GRIDs)
interfaces
Monolithic application a SOA transition
ESB/BPM/SOA “bus”
interfaces
5/18/2007 SOA evolution a high level Business Architecture View Page 11
Some basic characteristics and patterns for identifying “reusable” services Types of Services
• Process oriented services • services handling:
• one business process (e.g. order placement) but • contain multiple steps (functional or data oriented services)
• Data access oriented services • data access one or 1n data sources across the application architecture oriented – services handling:
• presenting data mappings • maintain data quality and business logical integrity • integration with other applications – e.g. logical replication
• Function oriented services • services handling both business and systems functions:
• one business process (e.g. price calculation for an order) • common error handling, special authentication, etc.
5/18/2007 SOA evolution a high level Business Architecture View Page 12
Some basic characteristics and patterns for identifying “reusable” services Implementation Granularity level
• Business services – coarsest level of granulrity • services handling – at this level business metrics will be applied:
• logical functions – opening account/customer profile for an order, prepare invoice • processes placing an order
important for performance, agility, scalability, resource usage, etc.
• Resource provider services – finest level of granularity • services mapping to and accessing application logic or data access:
• business process (e.g. price calculation for an order) • common error handling, special authentication • raw data base access
• Intermediary services – layer of system function oriented services •services that define the interfaces for interacting between the business services and the provider services:
• invocation transparency • presenting unique view mapping of data from different resources • integrating logic from different backend mission critical applications
5/18/2007 SOA evolution a high level Business Architecture View Page 13
Some basic characteristics and patterns for identifying “reusable” services Other important aspects
! all the above will become architecture buildingblocks .see next slide!
• Communication pattern s • Synchronous & coupled • Asynchronous & coupled • Asynchronous & decoupled Requestreply with various patterns pointto point, publish and subscribe
• Behaviour patterns • worker or state change, monitor observes behaviour, acting agent • stateful or stateless • transaction longevity (shortlived, longlived)
Data Logic
Business Logic
Presentation Logic
Serviceoriented Application
Physically Monolithic Application
Data
Browser or Dumb Terminal
Typical Twotier Client/server Application
Business Logic
Presentation Logic
Data
Data Logic
Presentation Logic
Multitier Application
Data
Business Logic
Presentation Logic
Data
Data Data
Data Logic
Busi ness Logic
Data
Data Logic
Busi ness Logic
Data
Data
Busi ness Logic
Browser Browser
PC
Business Components
Evolve to “Business Components” Foundation for Service oriented and Eventdriven Architectures
(“Web enabling) (“Web services) Browser
5/18/2007 SOA evolution a high level Business Architecture View Page 15
Service interfacing a core of SOA
5/18/2007 SOA evolution a high level Business Architecture View Page 16
why prototype ??
Sample view of the integration centric journey to ESB/BPM/SOA
infrastructure must allow amongst others: Ø simultaneous deployment of both old and new services Ø smooth and gradual conversion to the new versions of services, data bases when deemed appropriate Ø risk mitigation and fallback Ø contents management and governance
5/18/2007 SOA evolution a high level Business Architecture View Page 17
SOA Layers & Basic Middleware Bus OLTP, MQS, J2EE, .NET adapters, connectors – MWBus
ESB
EAI Security
Application Adapters
Service Bus/Broker
Translation/ Transformation Routing
Database Interface
Legacy Interfaces
Process Management/Orchestration
Firewall
Firewall
B2B Server Portals
UDDI Directory
B2B
Security
Man
agem
ent
Mobile Server
Web Service
Enterprise Information Integration & Management
Web Services Directory
Web Service Web Service
Web Service Web Service Web Service
Web Service
Mainframe Applications Minicomputer IBM AS/400
PP
PP
PP
PP PP PP
PP
PP PP
PP
PP
PP
BPM
MW Bus
BP
BP BP
BP
BP
BP
Monitoring
Job Scheduling
HOLISTIC APPROACH !!
5/18/2007 SOA evolution a high level Business Architecture View Page 18
Distributed & Composite applications THE JOURNEY TO A SOA RTE – we can help you
• Distributed applications: “placement of application logic into different layers of abstraction” – the basis for composite applications
• Composite applications: “development of new application systems by combining brandnew logic and transactions exposed by preexisting, legacy applications.”