Scribd
Upload
133 views5 pages

IIB Notes

The document provides a comprehensive overview of IBM Integration Bus (IIB), detailing its features, architecture, message processing, and error handling capabilities. It outlines the components such as Integration Nodes, message flows, and various types of parsers and nodes used for processing messages. Additionally, it includes information on ESQL for message transformation and administrative commands for managing IIB.

Uploaded by

shamanthck.work
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
133 views5 pages

IIB Notes

The document provides a comprehensive overview of IBM Integration Bus (IIB), detailing its features, architecture, message processing, and error handling capabilities. It outlines the components such as Integration Nodes, message flows, and various types of parsers and nodes used for processing messages. Additionally, it includes information on ESQL for message transformation and administrative commands for managing IIB.

Uploaded by

shamanthck.work
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

IBM Integration Bus (IIB) - Notes

1. Introduction to IBM Integration Bus (IIB)


IBM Integration Bus (IIB), formerly known as WebSphere Message Broker (WMB), is an
Enterprise Service Bus (ESB) that enables application integration across different
platforms using message flows. It facilitates the transformation, routing, and
enhancement of data between various services and applications.

Key Features:

●​ Supports multiple protocols (MQ, HTTP, REST, SOAP, FTP, etc.)


●​ Provides message transformation using ESQL, Java, and Mapping nodes
●​ Enables both synchronous and asynchronous communication
●​ Offers built-in error handling and transaction management
●​ Supports integration with databases (ODBC & JDBC)
●​ Provides high availability and scalability

2. IBM Integration Bus Architecture


IIB consists of several components that work together to process messages efficiently.

Integration Node (Broker):

●​ A runtime component that processes messages.


●​ Can be associated with one or more Queue Managers (MQ).
●​ Can exist with or without an associated Queue Manager (from IIB v10 onwards).

Integration Server:

●​ Hosts message flows and resources.


●​ Runs as a separate process to enhance isolation and stability.

Message Flow:

●​ Defines the sequence of operations for message processing.


●​ Consists of interconnected nodes that perform transformations, routing, and logic.

Message Model:

●​ Defines the structure and format of messages using DFDL, XMLNSC, MRM, JSON.

Repositories & Resources:


●​ BAR (Broker Archive File): Deployable unit containing message flows, schemas,
and ESQL.
●​ Libraries (Shared & Static): Group related code and resources for reuse.

3. IIB MQ Topology & Message Handling


IIB v10 Flexible MQ Topology:

●​ MQ is optional on Windows, Linux, and UNIX platforms.


●​ Each Integration Node can:
○​ Exist without a Queue Manager.
○​ Be associated with a default Queue Manager.
○​ Connect with multiple Queue Managers (locally or remotely).
●​ Queue Managers can be shared across multiple Integration Nodes.

IIB v9 & Earlier MQ Topology:

●​ MQ was mandatory.
●​ Each Integration Node required a dedicated Queue Manager.
●​ Queue Managers could not be shared.

4. Message Processing in IIB


Message Flows:

●​ Define the processing steps in source-to-target application integration.


●​ Use nodes to specify logic (e.g., Compute Node, Route Node, MQInput, MQOutput).

Key Components:

●​ Input Nodes: Receive data from a source system.


●​ Processing Nodes: Apply logic, transformations, and business rules.
●​ Output Nodes: Deliver data to the target system.

Logical Trees:

●​ Internal representation of messages during processing.


●​ Types:
○​ Message Tree: Holds application data (Root, Properties, Body).
○​ Environment Tree: Stores internal processing variables.
○​ LocalEnvironment Tree: Contains routing & output node information.
○​ ExceptionList Tree: Captures error details.
5. Message Modeling & Parsers
Parsers in IIB:

●​ Responsible for parsing input messages into Logical Trees and serializing output
messages.

Types of Parsers:

●​ MRM Parser: Used for binary, fixed-width, delimited, XML data.


●​ DFDL Parser: Open-standard parser for text & binary formats.
●​ XMLNSC Parser: Optimized for XML, removes insignificant whitespace.
●​ JSON Parser: Handles JSON messages.

Message Modeling:

●​ Defines the structure of messages.


●​ Uses DFDL, XSD, MRM (deprecated in IIB v10).
●​ Created using Toolkit or CLI commands (mqsicreatemsgdefs,
mqsicreatemsgdefsfromwsdl).

6. IBM Integration Bus Nodes Overview


Processing Nodes:

●​ Compute Node: Executes ESQL transformations.


●​ JavaCompute Node: Performs transformations using Java.
●​ Mapping Node: Graphically maps elements from input to output.

Routing Nodes:

●​ Filter Node: Simple IF-ELSE condition-based routing.


●​ Route Node: Uses XPath for advanced message routing.
●​ RouteToLabel & Label Node: Similar to GOTO statements for condition-based
processing.

MQ Nodes:

●​ MQInput Node: Reads messages from an MQ queue.


●​ MQOutput Node: Sends messages to an MQ queue.
●​ MQGet Node: Retrieves messages mid-processing.

Database Nodes:
●​ Database Node: Executes SQL queries using ODBC.
●​ DatabaseInput Node: Triggers message flow based on database updates.
●​ DatabaseRetrieve Node: Fetches data from a database.

7. Error Handling in IIB


Exception Handling Techniques:

1.​ Failure Terminal: Handles errors occurring inside a node.


2.​ Catch Terminal: Catches exceptions beyond the node.
3.​ TryCatch Node: Used for structured exception handling.
4.​ Throw Node: Generates custom exceptions.

Dead Letter Queue (DLQ):

●​ Stores undeliverable messages at the Queue Manager level.


●​ Each Queue Manager has only one DLQ.

8. ESQL (Extended Structured Query Language)


●​ ESQL is used for message transformation and database interactions.
●​ Used in Compute, Filter, and Database Nodes.

ESQL Key Features:

●​ Can manipulate Logical Trees.


●​ Supports transactions and database queries.
●​ Provides string manipulation and conditional processing.

Common ESQL Commands:


DECLARE variable-name CHARACTER 'Hello';
SET OutputRoot.XMLNSC.Customer.Name = 'John Doe';
IF InputRoot.XMLNSC.Order.Amount > 1000 THEN
SET OutputRoot.XMLNSC.Order.Status = 'Approved';
ELSE
SET OutputRoot.XMLNSC.Order.Status = 'Pending';
END IF;

9. IBM Integration Bus Commands


Admin Commands:

●​ mqsistart – Start Integration Node


●​ mqsistop – Stop Integration Node
●​ mqsilist – List all Integration Nodes
●​ mqsisetdbparms – Set database connection parameters
●​ mqsichangeproperties – Modify Integration Node properties
●​ mqsicreatemsgdefs – Create message models from schemas
●​ mqsiformatlog – Process logs for debugging

10. Acronyms & Definitions


●​ SOA: Service Oriented Architecture
●​ API: Application Programming Interface
●​ ESB: Enterprise Service Bus
●​ JSON: JavaScript Object Notation
●​ SOAP: Simple Object Access Protocol
●​ WSDL: Web Services Description Language
●​ DFDL: Data Format Description Language
●​ ODBC: Open Database Connectivity
●​ JDBC: Java Database Connectivity
●​ MQ: Message Queue

🚀
This document covers all key topics needed for IBM Integration Bus (IIB). Use this as a
study guide for your test!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy