1. IST421: Advanced Systems and Enterprise Integration
Week4

2. EI Roadmap
Source: GBR, 2005, p. 18

3. Enterprise Integration Architecture
Enterprise as a System
Environment
Subsystem A
Subsystem B
Subsystem C
Blueprint for strategic as well as tactical integration projects
Fits within the overall framework of enterprise architecture
Acts as a glue that ties various entities in an organization together to share information (Case study 4.1)
Defines how new solutions plug into the enterprise resources so that individual projects do not need to figure this out.
Enterprise Integration Architecture
Enterprise Architecture

4. Components of Enterprise Integration Architecture
Technical Integration Architecture
Service Integration Architecture
Information Integration Architecture
Business Process Integration Architecture
Source: GBR p. 69
Enterprise Integration Architecture Domains
Enterprise Architecture
Business process layer, e.g. ERP, CRM
Application layer, e.g. SOA
Data layer, e.g. Database, Data warehouse, etc.
Infrastructure layer, e.g. LAN, Internet, VPN, etc.

5. Strategic enterprise approach
Tactical approach leads to multiple technologies
High implementation cost
Increased maintenance costs
High cost of change
Strategic approach
Accelerates tactical solutions
Lowers maintenance costs
Lowers TCO
Individual projects do not reinvent the wheel

6. Integration Competency Center
Provides integration expertise
Defines Enterprise Integration Architecture
Maximizes reuse
Ensures compliance with standards
Resolves conflicts
Sponsor
Data steward
Architect
Business / IT Analyst
Source: GBR, p. 71

7. Where to start? Current Integration Environment Assessment
Investments and reuse
What works and what doesn’t
Documentation
Current Environment Assessment Specification …
Integration technologies (how integration is being done)
Application and data source interfaces (what is available for integration)
Integration matrix (what is integrated to what)
Integration diagram (graphic representation of integration matrix)
Security

8. Integration Technologies
Messaging systems
IBM MQ Series, Tibco Rendezvous
Integration brokers / servers
IBM Integration bus (earlier WebSphere integration broker)
Application Servers
IBM WebSphere, Oracle WebLogic (J2EE)
Packaged Applications
SAP, Oracle PeopleSoft, etc.
Data Integration
Informatics, Teradata, etc.
B2B
EDI, ebXML solutions, etc.
IBM WebSphere MQ. Source:
Webmethods integration platform
Source:
Ref: GBR. p.81

9. Technical Integration Architecture
Provides building codes
Ensures consistency, reusability, economic benefit
Technical Integration Architecture Specifications …
Integration architecture requirements (what are you integrating)
Integration architecture description (how are you integrating)*
Standards profile
Service level requirements
Security
Capacity planning view
Design constraints and guidance
* Enterprise Integration Patterns:

10. Conceptual Architecture Description
The big picture ….
Interface Layer
Core Processing Layer
Interface Layer
Server Layer
Middleware Layer
Proprietary Networks
Web
Server
Message
Unix Servers
Application Server
Distributed Object
DBMS
Cell Networks
Commerce Server
TP Monitor
Packaged Apps
Internet
Portal Server
Services
IBM Mainframes
Source: GBR p. 98

11. Conceptual Architecture Description
The big picture ….
Source: Modi, S., & Mabert, V. (2011). The Enterprise Systems Industry Landscape. Handbook of Research in Enterprise Systems: New Directions & Cutting Edge Applications, edited by S. Kumar, J. Esteves, and E. Bendoly,

12. Service Level Requirements
Service Level Metric
<Application type or name 1>
<Application type or name 2> …
Availability
<Real time or batch> <8x5 or 24 x 7> … …
Integrity and delivery service
<Guaranteed> <Message stores>
Scalability
<Connections> <Data volumes>
Maintainability and manageability
<Level1, Level2, Level 3>
Usability
<Role-wise>
Performance
<Response time, throughput, simultaneous users>
Transaction services
<Distributed transactions, XA compliance, HIPAA compliance>
Persistence
<Data storage, recovery>
Directory services
< Information about all components of integration infrastructure>

13. SLA Example
Source:

14. Conclusions Think long-term Organizational support is critical
Bring some method to madness !

15. Enterprise Architecture
Describes the structure of an enterprise, its decomposition into subsystems, the relationship between subsystems, the relationship with the external environment, the terminology to use, and the guiding principles for the design and evolution of an enterprise
Benefits
Communicates shared vision: Provide a model that lets all stakeholders understand and communicate the overall business design
Provide a high-level, holistic design of the business indicating how all the subsystems will interoperate and coordinate their work
Express the architectural principles of a long-term vision of the enterprise, and the governing principles of the enterprise to guide all other projects
Ensure legal and regulatory compliance (1996 Clinger- Cohen act in US)
NIST Enterprise Architecture Model
NIST: National Institute of Standards and Technologies