Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 2: ENTERPRISE APPLICATION INTEGRATION (EAI) - Coggle Diagram
Chapter 2: ENTERPRISE APPLICATION INTEGRATION (EAI)
Enterprise Architecture Overview
Key Components:
Establishing architectural vision.
Understanding current and future IT systems and technology.
Identifying integration strategies and technologies.
Defining architectural standards.
Creating a robust, flexible, responsive, and trusted technical framework.
Purpose:
Helps achieve strategic goals of business management.
Supports creating competitive advantage, reducing risks, enhancing cost-efficiency, and scalability.
Definition:
Holistic, hierarchical, and abstract description of essential elements of an organization.
Aims to maximize shareholder value over time.
Enterprise Structure
Implementation Technologies
Application Connectivity
Bus/hub connects to applications through adapters/connectors.
Data Format and Transformation
EAI systems use application-independent data format to avoid data conversion.
Provides data transformation services between application-specific and common formats.
Bus/Hub
Implemented using middleware products (application
server, message bus) or standalone program (does not use any middleware), acting as its own middleware.
Integration Modules
EAI system handles multiple concurrent integration operations using different integration modules.
Modules subscribe to specific event types and process notifications.
Support for Transactions
Provides transactional consistency across applications for process integration.
Executes integration operations in a single overarching distributed transaction.
Communication Architectures
Independent Data Model
Based on a standard data structure (canonical data model).
Often implemented using XML and XML style sheets for a uniform business language.
Connector or Agent Model
Allows each vendor, application, or interface to build a single component.
Components can communicate natively with the application and centralized broker
Centralized Broker
Implemented through integration servers or enterprise service bus (ESB).
Manages security, access, and communication.
System Model
Defines APIs, data flow, and rules of engagement.
Enables standardized interfaces for components to interact with the system.
Integration Pattern
Federation (Inter-communication)
EAI system acts as an overarching facade across multiple applications.
All event calls from the outside world to any application are front-ended by the EAI system.
Exposes relevant information and interfaces of underlying applications to the outside world.
Performs all interactions with underlying applications on behalf of the requester.
Concurrent Usage
Both mediation and federation patterns are often used together.
EAI system can keep multiple applications in sync (mediation) while servicing requests from external users against these applications (federation).
Mediation (Intra-communication)
EAI system acts as a broker between multiple applications.
Integration module in the EAI system is notified of interesting events in an application.
Propagates changes to other relevant applications.
Enterprise Integration Patterns
Enterprise Application Integration (EAI):
Integration framework for systems and applications across an enterprise.
Enables data sharing without custom interfaces.
Example: Building an eCommerce portal integrating with legacy applications and external services.
Advantages of EAI:
Cost effectiveness
Time to market
Scalability
Ability to handle complex environments
Enterprise Integration Patterns (EIP):
Model integration as asynchronous messages.
Focus on communication between apps and edge components.
Stateless communication, often one-way.
Utilizes Message Broker for message delivery.
EIP Patterns:
Splitter
: Splits a message into pieces for individual processing.
Content-Based Router
: Routes messages based on content.
Message Filter:
Examines message content and forwards based on criteria.
Recipient List:
Forwards messages to channels associated with recipients.
Wire Tap
: Routes messages to a separate location during forwarding.
EIP Implementation:
Implemented in various open-source integration solutions:
Spring Integration
Apache Camel
Red Hat Fuse
Mule ESB
Guaraná DSL
Value and Risk
Benefits of Enterprise Architecture (EA):
Provides an overview of strategy, organization, technology, and business insights.
Focuses on enterprise-wide approach.
Risks of Creating EA:
Implementation may disrupt business operations.
Pulling organization members away from production for EA learning and delivery can be costly and time-consuming.
Value of EA:
Enhances resource planning capabilities and supports better decision-making.
Improves communication regarding current and future resources.
Speeds up idea conveyance and reduces differences in interpretation and misunderstanding.
Enterprise Architecture Components
Business Information Systems
Computer-based systems managed through the Metabase.
Database Domains
Hierarchically organized sets of noun-intensive descriptions associated with a mission leaf.
Database Object Classes
Collections of data and processes tied together for business reasons, existing as interrelated database tables or nested structures within a table.
Database Object Information Systems
Processes defined within the domain of the DBMS, often stored procedures transforming database objects.
Management Level
Named and defined levels of bureaucratic management within an organizational setting.
Missions
Hierarchically organized textual descriptions defining the enterprise's existence and ultimate goals.
Organizations Performing Missions
Associations of organizations with missions, with multiple organizations and missions possible.
Organizations Accomplishing Functions
Associations of organizations with functions supporting missions, with multiple associations possible.
Positions
Collections of work tasks performed by one or more persons, often assigned to organizations.
Positions Performing Missions
Assignments of positions to particular functions within organizations as they accomplish missions.
Resource Life Cycle Analysis Node
Life cycle states within resources, such as employee requisition, new hire, assigned, reviewed, and separated.
Resources
Enduring assets of value to the enterprise, including facilities, assets, staff, money, and reputation.