System Integration and Architecture Reviewer PDF

Reviewer: System Integration and Architecture Middleware Definition: Software that facilitates communication between multiple systems, enabling data and logic sharing. Message-Oriented Middleware (MOM): o Uses messages to move information between applications....

Reviewer: System Integration and Architecture Middleware Definition: Software that facilitates communication between multiple systems, enabling data and logic sharing. Message-Oriented Middleware (MOM): o Uses messages to move information between applications. o Resolves tight coupling by providing loosely coupled communication. Tight Coupling vs. Loose Coupling Tight Coupling: o High interdependence between systems. o Requires: ▪ Same process/runtime environment (e.g., virtual machine). ▪ Specific data formats and parameter types. ▪ Immediate synchronous communication. Loose Coupling: o Reduces dependencies like location, platform, or timing. o Achieved through MOM: ▪ Common data format. ▪ Queuing channels. ▪ Platform-independent communication. Messaging Concepts 1. Message Types: o Command Message: Triggers a specific function. o Document Message: Transmits data structures. o Event Message: Notifies changes. 2. Message Features: o Request-Reply: Command requests and document-based replies.  o Message Sequence: Breaks large data into smaller chunks. o Message Expiration: Discards outdated messages. Channels Purpose: Transports data between sender and receiver. Types: 1. Point-to-Point: One-to-one communication. 2. Publish-Subscribe: One-to-many communication. 3. Data Type Channel: Ensures uniform data types. 4. Invalid Message Channel: Handles unexpected message types. 5. Dead Letter Channel: For undeliverable messages. 6. Guaranteed Delivery: Persistent storage for messages. 7. Channel Adapter: Connects applications to channels. 8. Messaging Bridge: Links two messaging systems. 9. Message Bus: Central hub for communication. Message Transformation Purpose: Converts data formats between systems. Mechanisms: o Envelope Wrapper: Wraps data in a compliant format. o Content Enricher: Adds missing data. o Content Filter: Removes irrelevant data. o Normalizer: Standardizes diverse formats. o Canonical Data Model: Uses a universal data format. Routing Sends messages to multiple systems. Applications specify target systems and routes for data distribution. Systems Management  Monitors and controls integration processes. Key Features: o Control Bus: Centralized management. o Wiretap: Inspects messages without disrupting flow. o Message History: Tracks message path. o Smart Proxy: Monitors request-reply interactions. o Test Message: Verifies messaging system health. o Channel Purger: Clears leftover messages. Endpoints Definition: Connects applications to the integration system. Components: o Messaging Gateway: Simplifies messaging calls. o Mapper: Translates between messaging infrastructure and domain objects. o Transactional Client: Enables transaction boundaries. o Polling Consumer: Actively fetches messages. o Event-Driven Consumer: Reacts to incoming messages. o Competing Consumers: Processes messages concurrently. Component Integration and Testing Plan 1. Objectives Ensure that individual components (middleware, channels, endpoints) work together seamlessly. Verify data exchange accuracy and communication protocols. Identify and resolve integration issues early. 2. Key Components for Integration 1. Middleware: o Message-Oriented Middleware (MOM) for loose coupling. o Services like message transformation and routing.  2. Channels: o Point-to-point, publish-subscribe, and data type channels. 3. Messaging Endpoints: o Gateways, mappers, and adapters for connecting applications. 4. System Management Tools: o Control bus, wiretap, and message history for monitoring. 3. Integration Steps 1. Preparation: o Define the data formats for communication. o Configure channels for message transport. o Set up endpoints to wrap and unwrap messages. 2. Component Assembly: o Connect middleware to applications via endpoints. o Establish communication through the chosen channels. 3. Data Routing and Transformation: o Test routing mechanisms to direct messages to correct destinations. o Verify data normalization and translation between applications. 4. System Monitoring: o Use control bus and wiretap tools to observe message flow. o Log errors and ensure all components are functioning. 4. Testing Process 1. Unit Testing: o Test individual components like channels and endpoints. 2. Integration Testing: o Verify that middleware, channels, and endpoints communicate as expected. o Simulate message exchanges (command, document, event). 3. Performance Testing: o Ensure the system can handle large amounts of data or slow messages.  4. Error Handling: o Test invalid message channels and dead letter channels. 5. Success Criteria All messages are delivered and processed correctly. No data loss or corruption during exchanges. All components operate within performance benchmarks. 6. Tools and Resources Middleware platforms (e.g., MOM software). Monitoring tools for logs and message tracking. Testing frameworks for message validation. JSON Reviewer Basic Concepts 1. What does JSON stand for? o JavaScript Object Notation 2. JSON is based on the syntax of which programming language? o JavaScript 3. Who popularized the JSON format? o Douglas Crockford Usage and Applications 4. JSON is widely used in which types of applications? o Web and Mobile Applications 5. Why is JSON beneficial for students and beginners in programming? o It simplifies data management and is readable. 6. JSON is commonly used in collaborative projects because: o It allows easy data sharing across systems.  7. JSON is widely compatible with other programming languages. This helps students by: o Enabling cross-platform application development Structure and Syntax 8. JSON’s structure primarily consists of which two elements? o Objects and Arrays 9. In JSON, what symbol is used to represent an object? o {} (curly braces) 10. What is an example of a key-value pair in JSON? o "name": "John" 11. JSON keys must always be enclosed in: o Double quotes (" ") 12. In JSON, arrays are represented by: o [] (square brackets) Features and Limitations 13. Which of the following data types is NOT supported by JSON? o Function 14. Which of the following statements about JSON is TRUE? o JSON is lightweight and easy to read. 15. In JSON, what happens if you try to add a comment? o The JSON file will display an error. Example Syntax { "name": "Elpie", "age": 21, "skills": ["Graphics Design", "Game Development"], "university": "Marinduque State University" } Middleware and Integration Concepts Reviewer Basics of Middleware 1. What is middleware? o Software that facilitates communication between systems. 2. What does MOM stand for? o Message-Oriented Middleware. Coupling in Systems 3. What is tight coupling? o A direct dependency between two systems. 4. Example of tight coupling: o Invoking a local method in the same application. 5. Which is NOT an assumption of a tightly coupled system? o Systems are available at different times. 6. What does MOM resolve? o Tight coupling between applications. 7. Primary benefit of loose coupling in integration solutions: o Makes systems more tolerant to changes. Communication Protocols 8. Simplest method to link two computers for communication: o TCP/IP Protocol. 9. Which messaging channel is used for one-to-one communication? o Point-to-Point Channel. 10. What channel handles undeliverable messages? o Dead Letter Channel. Messaging and Events 11. What type of message notifies the receiver of a change in the sender? o Event message. 12. What happens if a message expires before it is delivered?  o It is discarded. 13. Which pattern is used to notify systems of an update (e.g., customer address change)? o Publish-Subscribe Channel. Middleware Components 14. What does a Channel Adapter do? o Connects channels to applications. 15. What ensures all data on a channel is of the same type? o Data Type Channel. 16. What is a Detour in middleware? o Both a bypass mechanism and a means to reroute messages. 17. Feature that inspects message content without affecting its flow: o Wiretap. 18. Component that connects two different messaging systems: o Messaging Bridge. 19. Middleware mechanism to wrap a message payload into a compliant structure: o Envelope Wrapper. Data Processing and Transformation 20. What is the purpose of a Content Filter? o Removes unnecessary data from a message. 21. What middleware mechanism translates different message formats into one common format? o Normalizer. 22. Method to create a standard independent data model for communication: o Canonical Data Model. Messaging Patterns and Consumers 23. What type of consumer explicitly makes a call to receive messages? o Polling Consumer. 24. Which pattern enables messages to be processed concurrently by multiple consumers? o Competing Consumers. Monitoring and Management 25. What ensures all components of an integration solution are functioning? o Systems Management. 26. Primary goal of systems management in middleware: o Monitor and manage data flow across systems. 27. What is a Control Bus? o Provides a single point of management. 28. What middleware feature tracks the flow of a specific message? o Message History. 29. Mechanism that verifies message system functionality during operation: o Test Message. 30. What is an Endpoint in an integration solution? o A special code or adapter connecting a system.