Transcript Informatica_Template_Sep2003 “Turning integration into

Software architecture
adjustments for a
changing business
1
Business is Changing
2
Observations
• Business:
•
•
•
•
•
Outsourcing Business Processes
Outsourcing IT
Integrating Internal and External Processes
Focus on Core Competence and Compliance
Mergers and Acquisition
• IT
•
•
•
•
Architecture Innovation (SOA)
Consolidation of Applications
Focus on Integration and Flexibility
Offshore activities
3
Pressure on IT
4
The CIO Challenge
Pressure from various angles
CEO
Lines of
Business
CFO
Auditors
5
Requirements
• Business Agility requires IT Flexibility
• IT Flexibility requires Flexible infrastructure
• Flexible infrastructure require SOA
• Successfull SOA requires
• Standards
• Application Integration Platform
• Data Integration Platform
6
The 3 adjustments for Success
Integration and Innovation Projects
Architecture
Technology
Long Term
Blueprint
(SOA, EDA)
Scalable and
Flexible Platform
Approach
Integration
Competency
Center
(ICC)
7
The Evolution of Integration
• Legacy Applications
• Key applications functioned independently
• Data and application logic lumped together on isolated systems
• The mainframe era
• Integration not a priority
• ERP Applications
• Core back office functionality packaged into customizable modules
• Single-vendor providing tightly coupled applications
• Integration restricted to a few applications (CRM with Financials, etc.)
• Application and Data Integration
• Multiple vendors providing different critical application components
• Information assets distributed across heterogeneous systems
• Application and Data Integration become TOP priority
8
Process Outsourcing:
Increases Integration Complexity
Sales Force
Automation
In-House
Data Integration
for the Virtual Enterprise
Composite
Apps
Consolidated View
PLM
Legacy Migration
Consolidation
CRM
Synchronization
Master Data
Management
Payroll
SCM
Receivables
Payables
Single View of Business
HR
ERP
Other
Data Warehouse
Query & Reporting,
Dashboards
Custom
9
Strategic Value of Information
Automation of Transactions & Operations
Service
Provider
Silo based architectures of the past
Biz
Logic
Biz
Logic
OE
CRM
DB
DB
HR
DB
Fin
DB
Mainframe
10
Dependencies between systems grew
Biz
Logic
Biz
Logic
OE
CRM
DB
DB
HR
DB
Fin
DB
Mainframe
11
Resulting in the Accidental Architecture
Biz
Logic
Biz
Logic
OE
CRM
DB
DB
HR
DB
Fin
DB
Mainframe
12
Technology confusion
• Vendors have delivered functionality in various forms and
packages to meet these Integration needs over time:
• ETL (Extract, Transform and Load)
• MOM (Message Oriented Middleware)
• EAI (Enterprise Application Integration
• B2B (Business to Business)
• Workflow
• BPM (Business Process Management)
• BAM (Business Activity Management)
• EII (Enterprise Information Integration)
• ESB (Enterprise Service Bus)
What technology or combination of technologies is right for my project?
13
Service-Oriented Architecture
• An integrated software infrastructure and design
approach to expose business relevant data and
application services in a loosely coupled, standards
based form. SOA • Leverages web computing standards (XML, SOAP, etc.)
• Promotes wrap and reuse of existing IT assets
• Metadata-driven to maximize portability
14
Two Types of Integration
• Enterprises have two major type of IT assets
they need to integrate
Business Logic
Data
• These are two different integration problems
which require different technologies &
approaches
Application &
Process
Integration
Data Integration
15
Complex integration environment increases costs and
impedes flexibility
Business
Initiatives
IT Initiatives
Requirements
for Accessing,
Integrating &
Moving Data
Regulatory
Compliance
Upgrade
Risk Mgmt
System
App
vendor
tool
Reduce
Lending
Risk & Fraud
Migrate Legacy
Finance App.
Consolidate
Risk Systems
Increase
Customer
Cross-sell &
Loyalty
Integrate
Customer
Analytics Data
Integrate
New Merger
Consolidate
Customer
Systems
• Incomplete,
inconsistent view of
data
BI ETL
Hand
EAI
Tool EAI
coding one-off
SQL • Costly,
SQL
development
efforts
Scripting App Scripting
Custom
• vendor
High
maintenance
&
administration costs
code
Data
FTP
tool
• Integration
No reuse of code or skill sets
• Brittle infrastructure hard to change
Outsource
HR
Upgrade Sales
Comp
Systems
Integrate with
Hewitt
BI ETL
Tool
Custom
code
SQL
Scripting
Enterprise
Data
Applications
Databases
Messages
Flat files
XML
Unstructured Data
Mainframe
16
The Importance of
Data Integration in SOA
AMR Research
“Data Integration, Foundation
for SOA”,
September 2005
• “Companies must build a solid data services layer; Otherwise
SOA benefits will NEVER be realized”
• “The vast majority of companies must have a data integration
strategy to accommodate change.”
• “SOA’s success is contingent on a data integration strategy”
Gartner
“Data Integration Is Key to
Successful Service-Oriented
Architecture
Implementations”, October
2005
Nucleus Research
“SOA: The Two Biggest
Mistakes to Avoid”,
November 2005
• “SOA will fail if long-standing data quality, data redundancy
and semantic inconsistency issues are not addressed.”
• “Organizations must address data integration issues during
their SOA implementations.”
• “In utilizing service-oriented architectures (SOA) for integration
projects, IT departments should seek to avoid two commonly
made mistakes: giving insufficient attention to how data will
flow over the underlying architecture, and insufficient use of
metadata.”
17
Service-Oriented Enterprise Integration
Portal
Business Processes
(orchestration)
Reusable Data Services
Reusable Application Services
(complex transformation, data quality check)
(pub/sub channels, transaction monitor)
Application Integration
(Access, Reliable Messaging, Transactions)
Data and Metadata Integration
(Data Access, Profiling, Cleansing, Aggregation, Transformation)
DB
Biz Logic
Fin
SAP
DB
DB
Backend
IT
Assets
Mainframe
18
Conclusion
• Business forces IT to innovate
• Outsourcing increases complexity
• Adjustments in IT focus on SOA
• Regulations will push IT even more
19