View
222
Download
5
Tags:
Embed Size (px)
Citation preview
Enterprise Integration ArchitectureIPMA Professional Development SeminarJune 29, 2006
Scott CameDirector, Enterprise Architecture ProgramWashington State Department of Information Services
EA Integration Architecture Initiative In December, the ISB EA Committee chartered
an initiative to look at integration architecture Team of architects, developers, IT managers,
and integration experts from agencies have been meeting to develop an architecture
Materials endorsed by EA Committee in June, out for CAB review now
Motivation Reduce costs and risks of integration Reuse system interfaces Leverage common infrastructure Improve agility and responsiveness of IT Accommodate different software platforms,
COTS/package application architectures
Approach: Service Oriented Architecture
SOA is an architectural approach for organizing and using services to support interoperability between enterprise data
assets and applications
Capabilities performed by one for another to achieve a
desired outcome
ServiceS
The fundamental organization of a system by its capabilities,
their interactions, and the enterprise environment
ArchitectureA
Aligning architecture to enable a collection of services to be
linked together to solve a business problem
OrientedO
Slid
e co
urte
sy B
ooz
Alle
n H
amilt
on
What is a service? An explicit, focused agreement between the
provider and the users of a capability as to how the interaction with the capability will take place
Services support integration by: Establishing an agreement as to the purpose of the
interaction and how the interaction will take place (e.g., agreement on meaning of data)
Hiding the implementation of one system from another, avoiding technical dependencies
Tight Coupling of Systems
System in Agency ASystem in Agency B(Capability)
Desires
Uses
Accesses
Causes
Effect
TechnologyDependency
How do we tightly-couple systems? Sharing databases Integrating user interfaces Integrating with technology specific/proprietary
to one system (versus open standard technologies)
Exchanging files
Loose Coupling of Systems
System in Agency ASystem in Agency B(Capability)
Desires
Uses
Accesses
Causes
Effect
Ser
vice
Accesses Inte
rfac
eTechnologyDependency(Standards)
How do we loosely-couple systems? Exchange messages specified by service
(explicit, focused agreement) Leverage open standards for message
structure Use infrastructure to route messages, rather
than direct addressing Asynchronous, reliable transport of messages
Natural Boundaries When systems are likely to change at the same
time, tight coupling is OK Performance Simplicity
A “natural boundary” identifies sets of features that are implemented as a unit (and change as a unit)
Integrate across natural boundaries; consolidate within natural boundaries
Benefits of SOA
AgilityAgility
Focus more on core competencies and missions by creating a network of producers-suppliers with intense interactions
Improve access to information to enable faster cycle times
Enable enterprises to be more agile and respond quickly to business needs
Focus more on core competencies and missions by creating a network of producers-suppliers with intense interactions
Improve access to information to enable faster cycle times
Enable enterprises to be more agile and respond quickly to business needs
ProcessProcess
Increase business flexibility through plug-and-play architecture and re-use of existing services
Ensure system change is not a constraint on business or mission change
Allow interoperation with other systems & partners without customization
Increase business flexibility through plug-and-play architecture and re-use of existing services
Ensure system change is not a constraint on business or mission change
Allow interoperation with other systems & partners without customization
InteroperabilityInteroperability
Facilitate integration with multiple solutions via open IT standards
Remain platform, language, and vendor independent to remove IT barriers for using best-of-breed software packages
Facilitate integration with multiple solutions via open IT standards
Remain platform, language, and vendor independent to remove IT barriers for using best-of-breed software packages
CostsCosts
Reduce development costs by acquiring pre-built capabilities
Leverage previous IT investments through re-use of assets
Lower maintenance costs and TCO through fewer “instances” of a function, and fewer software licenses
Reduce development costs by acquiring pre-built capabilities
Leverage previous IT investments through re-use of assets
Lower maintenance costs and TCO through fewer “instances” of a function, and fewer software licenses
IT alignment with an organization’s missionIT alignment with an organization’s mission
Improved agility, focus on core competencies, IT efficiencies, and ROI for IT assetsImproved agility, focus on core competencies, IT efficiencies, and ROI for IT assets
Slid
e co
urte
sy B
ooz
Alle
n H
amilt
on
Deliverables from EA initiative Integration Domain (principles, business
drivers, environmental trends) Conceptual Architecture Service Interaction Profiles (Web Services,
Websphere MQ, File Drop) Solution Integration Design Guidelines Service Modeling Guidelines
For more information… EA Committee Website (includes deliverables)
http://isb.wa.gov/committees/enterprise/index.aspx
EA Program Website and Contact http://dis.wa.gov/enterprise/enterprisearch/index.aspx Scott Came, EA Program Director [email protected], 360-902-3519