ZM665 Unit01 Script

ZM665 Unit 1 Transcript
Slide 1
Introduction to
IBM Integration Bus
Copyright IBM Corporation 2013

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
8.0
Introduction to IBM Integration Bus
1
Slide 2
Unit objectives
After completing this unit, you should be able to:
Explain the position of IBM Integration Bus within the IBM WebSphere
Reference Architecture
List the major functions of an enterprise service bus
Describe the features and functions of IBM Integration Bus
Describe the IBM Integration Bus architecture and components
This unit introduces the IBM Integration Bus. In this unit, you learn the position of IBM Integration
Bus in a service-oriented architecture and an enterprise service bus. You also learn about the
IBM Integration Bus components and functions.
After completing this unit, you should be able to:
Explain the position of IBM Integration Bus within the IBM WebSphere Reference
Architecture
2
Slide 3
IBM WebSphere reference architecture

Business services
WebSphere Business Monitor
Interaction
services
Development
Services
WebSphere
Business
Integration
Modeler
and
WebSphere
Integration
Developer
WebSphere
Portal Server
Process
services
IBM Business
Process Manager
Information
services
WebSphere
Information
Integrator
ESB
WebSphere Enterprise Service Bus
IBM Integration Bus
Management
services
Service registry
Partner
services
WebSphere
Partner Gateway
Business
application
services
WebSphere
Application Server
Access
services
WBI and
WebSphere
Adapters, HATS
Infrastructure services
IBM products provide the integration solutions for on-demand business. Integration solutions
typically begin with the fundamental requirement to interconnect multiple prepackaged or custom
applications. The IBM middleware products provide the functions that meet this fundamental
requirement.
The IBM middleware products are implemented as a service-oriented architecture, which IBM
calls the IBM WebSphere reference architecture.
There are three basic layers within the architecture:
The application connectivity layer provides integration middleware that allows information to
flow between the applications in a way that abstracts the details of the information flow from
the applications themselves. This layer provides information delivery management and
connectivity management. Information delivery management is the ability to determine the
appropriate destination for the information flow and ensure that it is in the form that the
destination requires. It centralizes the logic so that it is not repeated in each of the
interconnected applications. Connectivity management is the ability to attach applications to a
transport that isolates the details of the connection from the internals of the application.
Connectivity Management is provided through adapters.
The process integration layer provides integration middleware that manages the flow across
various heterogeneous, connected applications in a way that abstracts the details of the flow
of activity from the applications themselves. This layer provides functions that:
- Catch and handle application events that must be propagated to other applications
- Control the flow of actions that is required among the interconnected applications
- Allow the interaction of people and applications
- Provide control and state management that is required for long-running processes
3
The modeling and monitoring layer provides the runtime assets that implement a business
process and the tools to view, collect, analyze, and use data from the runtime system to
upgrade the processes. This layer provides the functions that are required for:
- Efficient implementation of business processes
- Analyzing and assessing process efficiency and effectiveness
- Continuous business improvement through process management and change
4
Slide 4
Enterprise service bus (ESB)

Flexible connectivity infrastructure for integrating applications and
services
Reduces the number, size, and complexity of interfaces
Acts between requester and service:
Routing messages between services
Converting transport protocols between a requester and a service
Transforming message content between a requester and a service
Handling business events from disparate sources
The enterprise service bus (ESB) provides the connectivity infrastructure for integrating
applications and services. As shown in the previous figure, it is a central component of a serviceoriented architecture that reduces the number, size, and complexity of interfaces.
An ESB is responsible for:
Routing messages between services
Converting transport protocols between a requester and a service
Transforming message formats between a requester and a service
Handling business events from disparate sources
5
Slide 5
IBM ESB products

IBM
Integration Bus
WebSphere
DataPower
Integration
Appliances
WebSphere
Enterprise
Service
Bus
Service visibility and governance

Service enrichment
Messaging
IBM Integration Bus

For environments that must
integrate multiple
heterogeneous applications,
including those environments
that require an SOA-enabled
infrastructure without
substantial rework.
WebSphere DataPower
A solution for companies that
have a high level of XML data
structures and a need for
speed, and must deploy an
ESB in a DMZ.
ESB
WebSphere Enterprise
Service Bus
Integrates environments with a
preponderance of
standards-based applications
and web services assets.
An ESB can be implemented in a service-oriented architecture by using various IBM products.

Each product is tailored to suit various deployment needs. Each product has its strengths for
specific integration project types, and deployment environments.
IBM WebSphere Enterprise Service Bus provides web services connectivity, JMS messaging,
and service-oriented integration.
IBM Integration Bus is an integration product for Java, Microsoft .NET, and heterogeneous
integration scenarios. It represents a significant evolution of the WebSphere Message Broker
technology base, and includes new features such as policy-based workload management,
business rules, and integration with Business Process Management (BPM) and Microsoft .NET.
IBM Integration Bus is IBMs strategic ESB offering and is the successor product for existing
clients of WebSphere Enterprise Service Bus and WebSphere Message Broker.
IBM WebSphere DataPower SOA Appliances are purpose-built, easy-to-deploy network
appliances that help simplify, secure, and accelerate your XML and web service deployments
while extending your SOA infrastructure. They can do XML schema validation, XML style sheet
transformations, web service security, transformations between disparate message formats, and
more.
The IBM ESBs can be deployed separately to meet individual requirements or in combination to
meet sets of different business connectivity requirements that span an entire infrastructure. The
focus of this course is IBM Integration Bus.
6
Slide 6
Introducing IBM Integration Bus

A single product for Windows .NET, Java, and fully heterogeneous
integration scenarios
Integration
gateway
IBM
Integration
IBM
Integration
BusBus
ERP, EIS,
CRM
Files
Web
services
Devices
Microsoft
.NET
Mobile
Databases
Messaging
middleware
Mainframe
CICS/IMS
A natural evolution for WebSphere Message Broker applications

Significant innovation and evolution of the WebSphere Message Broker
technology base
New features for policy-based workload management, business process
management integration, business rules, and .NET
Incorporates WebSphere Enterprise Service Bus use cases

IBM Integration Bus connects a wide range of applications, services, and systems across
heterogeneous IT environments. It provides the visibility and control capabilities that are needed
to support critical business activities such as monitoring, auditing, process management, and
analytics.
IBM Integration Bus can help to:
Rapidly enable business insight to be applied to in-flight data
Accelerate creation of integration services for business process management (BPM)
Increase operational awareness and control over workload
Gain visibility and insight of integration in application environments
Locate web services through registries such as IBM WebSphere Service Registry and
Repository and build new web service front-end interfaces to existing applications.
IBM Integration Bus is a natural evolution for WebSphere Message Broker applications and
includes new features for policy-based workload management, business process management,
business rules, and .NET support.
IBM Integration Bus represents IBM's strategic ESB offering. IBM Integration Bus provides tools
that helps convert WebSphere Enterprise Service Bus assets and so they can run on IBM
Integration Bus.
7
Slide 7
IBM Integration Bus as an ESB

Extends the value of SOA to both standard and non-standard
applications
Plugs into the IBM SOA environment and also uses IBM Business Process
Manager Advanced (formerly WebSphere Process Server) for orchestration
Mediates XML and non-XML data formats
Enables non-SOA applications to behave as services
Provides exceptionally high-speed data movement and scalability
Integration without bounds with universal connectivity and

transformation
Single-click installation
Single-click administration roll-back
Broad hardware and operating system support
Powerful product tools for enhanced developer productivity
IBM Integration Bus can act as a part of a wider ESB. It is fully customizable, but it also offers
many built-in integration components.
Integration Bus can use WebSphere MQ for its transport layer to send and receive messages, or
it can read and write from the file system or databases. It can even send and receive email
messages and take advantage of other methods of connectivity to provide the most complete
integration possible.
IBM Integration Bus includes tools and programs to help simplify installation and administration
on a broad range of hardware and operating systems. It also includes powerful design, testing,
and deployment tools for enhanced developer productivity.
8
Slide 8
IBM Integration Bus architecture

IBM Integration Bus
HTTP
and Java
administration
clients
IBM
Integration
web user
interface
WebSphere
Application
Server
administrative
console
IBM
Integration
Explorer
Integration node (broker)

Integration server
IBM
Integration
Toolkit
Version
control
Application
Message flows
Libraries
Application
Message flows
External
system
Libraries
External
system
The runtime engine of IBM Integration Bus is the integration node, also known as the integration
broker.
The integration node processes in-flight messages that are based on message flows and
messages. The message flow controls the type and sequence of operations on the incoming
messages. Message flows are run on integration servers to provide isolation and scalability.
Message flows can interact with external systems such as web services and databases.
An application is a container for all the resources that are required to create a solution. A library is
typically, a reusable, logical grouping of related code, data, or both that an application references.
As shown in the figure, various tools can be used to manage the integration node, and develop
and monitor message flows and message content. IBM Integration Explorer and the IBM
Integration web user interface are the main administration interfaces. IBM Integration Explorer is
based on WebSphere MQ Explorer and allows administrators to manage IBM Integration Bus and
WebSphere MQ from the same administration console. IBM Integration web user interface
provides a subset of administration functions by using a web browser such as Mozilla Firefox.
You create message flows in the IBM Integration Toolkit, which is an integrated development and
administration console. It can connect with external source control applications for team
development.
The components of the IBM Integration Bus architecture are described in more detail in this
course.
9
Slide 9
IBM Integration Bus as a message broker

App A
QM A
Queue manager
Integration
node (broker)
Input
App B
COBOL
QM B
CWF
Compute
Output
Compute
Output
Filter
Message flow
QM C
XML
App C
Receives and routes messages
XML
Transforms messages to an alternative representation

Selects messages for further processing, which is based on the
message content
Interacts with an external database to augment a message, or to store
the whole or part of a message
Responds to events and errors
A message broker is required to provide more application connectivity services to implement an

efficient and effective system as the number of applications that are being interconnected
increases.
As shown in the figure, a message broker centralizes routing and transformation functions. In IBM
Integration Bus, the message broker is referred to as an integration broker or integration node.
IBM Integration Bus builds on WebSphere MQ, which provides assured, once-only delivery of
messages between the applications. The integration node runs under the control of a WebSphere
MQ queue manager.
A message flow defines the sequence of operations on a message by a series of message
processing nodes. The actions are defined in terms of the message format, its content, and the
results of individual actions along the message flow.
A message flow can route messages from sender to recipient based on the content of the
message. The direction of the flow is from the source application to the destination application. In
other words, it is assumed that the destination wants, expects, and handles all messages sent to
it.
Messages can also be transformed from one format to another before being delivered, perhaps to
accommodate the different requirements of the sender and the recipient.
The message flow can also transform messages by modifying, combining, adding, or removing
data fields. Information can be mapped between messages and databases. More complex
manipulation of message data can be achieved by writing code, for example in Extended SQL
(ESQL) or Java, within configurable nodes.
These components are described in more detail in the next unit.
10
Slide 10
IBM Integration Bus features

Universal connectivity provides a flexible and dynamic infrastructure
WebSphere Enterprise Services Bus conversion

WebSphere MQ service discovery
Database discovery and analysis tools
Data Format Description Language (DFDL) data modeling
Service mapping
Transforms and routes messages from anywhere, to anywhere

Supports a wide range of protocols and data formats
Includes comprehensive operations to route, filter, transform, enrich, monitor,
distribute, decompose, sequence, correlate, and detect
Operational management and performance

Extensive administration and systems management facilities for developed
solutions
Offers performance of traditional transaction processing environments
Web tools for real-time performance statistics
IBM Integration Bus simplifies application connectivity, routes, and transforms messages, and
simplifies programming. IBM Integration Bus includes many features for application connectivity
and message transformation and routing. It also provides operational management and
performance tools.
IBM Integration Bus includes features for universal connectivity to provide a flexible and dynamic
infrastructure. These features include tools to help with the conversion of WebSphere Enterprise
Service Bus assets so they can run on Integration Bus.
Integration Bus processes messages in two ways: message routing and message transformation.
Integration Bus includes comprehensive operations and supports a wide range of protocols so
that messages can be transformed and routed from anywhere, to anywhere. In Integration Bus,
messages can be transformed by modifying, combining, adding, or removing data fields, perhaps
involving the use of information that is stored in a database. Information can be mapped between
messages and databases. More complex manipulation of message data can be achieved by
writing code within configurable nodes
Integration Bus has extensive administration and systems management facilities, which include
web tools for real-time performance statistics.
11
Slide 11
IBM Integration Bus benefits

Simple and productive
Patterns for top-down, parameterized connectivity of common use cases

Construction tools for the bottom-up assembly of connectivity logic
IBM Graphical Data Mapping editor for consistent mapping across IBM products
Rapidly create integration services to meet the needs of process designers
Dynamic and intelligent

Manage integration workload to prioritize resources and prevent outages
Manage unresponsive integration flows for improved overall system reliability
Apply business insight to make near-real-time decisions to influence processing
flow
Monitor and visualize performance statistics in real time
High performing and scalable

Improve elasticity and response times by using flexible caching capabilities
Flexibly provision solutions across a range of physical and cloud environments
Integration Bus connects a wide range of applications, services, and systems across
heterogeneous IT environments. It provides the visibility and control capabilities that are needed
to support critical business activities such as monitoring, auditing, process management, and
analytics.
Design tools and aids such as application patterns and the IBM Graphical Data Mapping editor
accelerate the creation of business applications. Other tools help to:
Rapidly enable business insight to be applied to in-flight data
Increase operational awareness and control over workload
Gain visibility and insight of integration in application environments
Business-critical integration products must react quickly to changing technical and business
requirements through rules and policy-based configurations, and they must also provide insight
into data that flows through various IT systems. Key features in IBM Integration Bus V9 enable
the dynamic operational control of key configuration parameters, and they can help provide
valuable business intelligence.
Other features, such as integrated workload traffic policies extend the powerful productivity
features of IBM Integration Bus to develop and manage integration solution deployments, and
extend its industry-leading performance and scalability.
Integration Bus is optimized for high data throughput and linear scaling. New V9 features ensure
that it can perform exceptionally fast and scale in a wide variety of deployment scenarios.
12
Slide 12
Supported hardware and software environments

Broad range of operating systems and hardware
AIX, Windows (including Windows 8 and Windows Server 2012), z/OS, HP-UX,
Linux (xSeries, pSeries, zSeries), Solaris (x86-64 and SPARC), and Ubuntu
Optimized 64-bit support on all environments
32-bit option for development environments (Windows and Linux for System x)
Virtual images for efficient use and simple provisioning
Virtualized environments such as VMWare and AIX Hypervisor

IBM Workload Deployer for Linux for System x and AIX
Support for Pure on POWER hardware to complement Linux for System x
SmartCloud and IBM Workload Deployer images for simplified solution
provisioning
Access to full range of industry standard databases and ERP systems
DB2, Oracle, Sybase, SQL Server, Informix, and solidDB

Open Driver Manager support enables new ODBC databases to be accessed
JDBC Type 4 for supported databases
SAP, Siebel, PeopleSoft, and JD Edwards
IBM Integration Bus is supported on a broad range of hardware and operating systems such as
AIX, z/OS, Windows, and Linux. It is optimized for 64-bit operation in all environments.
Integration Bus also supports virtual images for efficient use and simple provisioning. It provides
access to many industry standard databases and enterprise resource planning systems.
This figure lists the supported hardware and software environments.
For a complete list of supported operating systems, hardware, virtual images, databases, and
ERP systems, refer to the IBM Integration Bus key prerequisites on the IBM website. You should
always check the IBM Integration Bus product page for the latest product information.
13
Slide 13
Technology components and prerequisites

WebSphere MQ V7.5 prerequisite (V7.1 on z/OS)
Java 7 on all environments
Other prerequisites are determined by operating system and hardware
Detailed system requirements are on www.ibm.com/integration-bus
IBM Integration Bus relies on WebSphere MQ for message management and transport.
WebSphere MQ is required in all environments.
A Java runtime environment is required on all platforms. On distributed platforms, Java Runtime
Environment (JRE) Version 7 is embedded in product components. On z/OS, you must acquire
and install a JRE. Integration Bus also relies on Java for JMS transport
For more information about prerequisites, see the IBM Integration Bus product page.
14
Slide 14
IBM Integration Bus components

IBM
Integration
Toolkit
IBM
Integration
Explorer
IBM Integration
web user interface
Integration node
Integration API
applications
Integration server
Application
Message flow
Libraries
Command-line
utilities
This figure shows the components of IBM Integration Bus. These components include the IBM
Integration Toolkit, IBM Integration Explorer, IBM Integration web user interface, Integration API,
and command-line utilities. These components communicate directly to one or more integration
nodes. Each integration node can contain one or more integration servers, which can run one or
more message flows.
Message flows and associated libraries can be packaged into applications. An application is a
collection of all IBM Integration Bus resources that are needed for a complete solution.
The IBM Integration Toolkit is the development environment for applications, libraries, and
message flows. The IBM Integration Explorer is the administration interface. IBM Integration
Toolkit and IBM Integration Explorer use a WebSphere MQ server connection to connect to the
integration node. The server connection is defined to the integration node queue manager when
you create the integration node.
The IBM Integration Toolkit and IBM Integration Explorer can run only on Windows and Linux
x86. They can manage integration nodes on other operating systems if a connection is
configured. In some cases, it might be necessary or preferred to use a command interface. IBM
Integration Bus supports IBM Integration administration and runtime commands.
With the IBM Integration Bus web user interface, you can view and manage Integration Bus
resources without any additional management software. It connects to a single port on the
integration node, provides a view of all deployed integration solutions, and gives you access to
important operational features such as the built-in data record and replay tool.
The Integration API is a programming interface that your applications can use to control
integration nodes and their resources through a remote interface. The Integration API classes
and methods can also be used to develop custom applications.
Each component is described more detail in the following figures.
15
Slide 15
IBM Integration Toolkit

An integrated development environment and graphical user interface
that is based on Eclipse
A single perspective for compiling, testing, deploying, and fixing
message flows
Connects to one or more integration nodes to which the message flows
are deployed
Comprehensive samples and patterns galleries for getting started
quickly
Runs on Microsoft Windows and Linux on x86
The IBM Integration Toolkit is an integrated development environment and graphical user
interface that is based on Eclipse. Application developers work in separate instances of the IBM
Integration Toolkit to develop applications, libraries, message models, and message flows. The
IBM Integration Toolkit also provides some administration functions; however, the primary
administration application for Integration Bus is the IBM Integration Explorer.
The IBM Integration Toolkit also communicates with one or more integration nodes. The basic
installation includes a wizard that can be used to create a development queue manager,
integration node, and integration server.
In the Toolkit, you can:
Define applications, message flows, and message flow components
Define and import message definitions
Deploy message flows and message models to integration nodes
Control log entries that are written during deployment
Start, stop, and trace message flows that are running in integration nodes
The IBM Integration Toolkit includes an extensive samples and patterns gallery to help you get
started with your application development.
The IBM Integration Toolkit runs on Windows and Linux and uses the local file system for artifact
storage.
16
Slide 16
IBM Integration Explorer

Single administrative explorer for IBM
Integration Bus and WebSphere MQ
operations
Full function, small footprint, stand-alone
tools for operational staff
Allows WebSphere MQ and IBM
Integration Bus artifacts to be managed in
a single console
Compliments compile, test, and fix
capabilities in IBM Integration Toolkit
Can be run as a stand-alone application

Contains a full stand-alone information
center
Runs on Microsoft Windows and Linux
on x86
IBM Integration Explorer is a WebSphere MQ Explorer plug-in that allows you to manage
integration nodes and queue managers from within a single interface. Most administrators are
already using WebSphere MQ Explorer for queue management. So, this single console manages
queue managers, queues, and integration nodes; it is not necessary to learn another interface to
manage integration nodes.
On Windows, IBM Integration Explorer is started by selecting IBM Integration Bus > IBM
Integration Explorer from the Windows Programs menu. You can also access IBM Integration
Bus administration from WebSphere MQ Explorer.
IBM Integration Explorer runs on Microsoft Windows and Linux on X86. It is possible to use IBM
Integration Explorer to remotely administer IBM Integration Bus on other operating systems,
however.
17
Slide 17
IBM Integration Bus web user interface
View and manage IBM Integration Bus resources without any

additional management software
Access operational features such as the built-in data record and
replay tool
Configure policy-based workload management
The IBM Integration Bus web user interface lets you view and manage Integration Bus resources
without any extra management software. It provides a view of all deployed integration solutions,
and gives you access to important operational features such as the built-in data record and replay
tool.
The web user interface includes a set of performance monitoring tools that visually portray current
server throughput rates. The rates show various metrics such as elapsed and CPU time in ways
that immediately draw attention to performance problems and increases in demand. You can also
get more detail, such as the rates for individual connectors. Tools let you correlate performance
information with configuration changes so that you can quickly determine the performance impact
of specific configuration changes.
For audit or problem determination purposes, you can also use the web user interface to
configure the IBM Integration Bus to record message data in an external database and then view
and replay it. By using the web interface, you can view a list of recorded messages, or you can
view details of a specific message.
IBM Integration Bus web user interface includes features to control the rate at which these
systems are loaded in order to improve overall system reliability. In a workload management
policy, you can define a threshold at which an integration is considered unresponsive, and then
define an action when that threshold is crossed, such as to restart the integration server.
18
Slide 18
Command-line utilities
IBM Integration Explorer and IBM Integration Toolkit runtime
commands
Have dependencies on WebSphere MQ
Requires a special command environment
Might require extra security configuration
Available on operating systems that IBM Integration Bus supports

z/OS requires a product such as SDSF to allow mixed case on the command line
On Windows, components are services and can be started automatically
Most of the administration tasks that you can complete in IBM Integration Explorer and the IBM
Integration Toolkit can be achieved programmatically by using the command interface. In some
environments, it might be necessary to use commands to configure and manage IBM Integration
Bus.
You might also want to use commands to automate specific tasks. For example, you can write
scripts to deploy applications to production integration servers on a schedule.
Some commands access the local components directly, others, need access to IBM Integration
Toolkit resources and can run only on Windows or Linux.
Some commands require extra authorization. For example, on some operating systems,
administrators must be a member of the mqbrkrs group to run administrative commands.
An overview of some commands is provided in this course; however commands are not covered
in detail in this course. IBM Integration Bus commands and security are covered in detail in
course WM645, IBM Integration Bus System Administration.
19
Slide 19
Integration API
Administration application programming interface (API) for IBM
Integration Bus
Applications can use the API to control integration nodes and their
resources through a remote interface
Requires WebSphere MQ Classes for Java
You can create your own administration interface by using the Integration API.
The Integration API is a set of lightweight Java classes that sit logically between the user
application and the integration node. It is an alternative interface for administering integration
nodes. All IBM Integration Bus applications, such as the IBM Integration Toolkit, use the API to
communicate with the integration node environment.
IBM Integration Bus includes samples to learn the basic features that the Integration API
provides.
20
Slide 20
Connectivity with adapters, bridges, and clients

IMS bridge
IMS MQI within IMS application

CICS DPL/3270 bridge
MQI within CICS application
CICS CICS client node
Enterprise
(WebSphere MQ)
WBI Adapter for JDBC
Batch WBI Adapter for JText
Files (FTP)
IBM
WebSphere MQ
transports
Web services
(HTTP)
Message flow
JCA adapters
EIS
JMS
Various WBI adapters
Email
Other Various third-party adapters

There are many different ways to connect into an IBM Integration Bus flow. Some of these
connection methods include WebSphere MQ, JMS, FTP, HTTP, and web services.
Some connectivity, such as FTP, web services, JMS, and email, is built in.
Some connectivity, like connections to enterprise information systems such as SAP, Siebel, JD
Edwards, or PeopleSoft, requires adapters.
IBM Information Management System (IMS) is a message-based transaction manager and
hierarchical-database manager for z/OS. You can use IBM Integration Bus to interact with
applications that run inside IMS. Open Transaction Manager Access (OTMA) is used to provide
access to IMS from Integration Bus. You can also use the WebSphere MQ-IMS bridge
component of WebSphere MQ for z/OS and the IMS SOAP Gateway to connect to IMS.
CICS Transaction Server for z/OS provides general-purpose transaction processing software for
z/OS. CICS is a powerful application server that meets the transaction-processing needs of both
large and small enterprises. By using the CICS support that is provided in Integration Bus, you
can deploy CICS applications into a service-oriented architecture. IBM Integration Bus includes a
node that supports connectivity to CICS by using the IP InterCommunications (IPIC) protocol.
CICS also has several components that support integration with WebSphere MQ such as the
CICS-WebSphere MQ adapter and the CICS-WebSphere MQ bridge, also known as the CICS
3270 and DPL bridges.
21
Slide 21
IBM Integration Bus web services

WebSphere
DataPower Appliances
Service
provider
Other
service provider
Service
provider
Web
service provider
WS-Security
processing
Application
connectivity
services
Lookup
Message flow
HTTP
SOAP-XML
SOAP
client
WebSphere Service
Registry and Repository
Service
requester
IBM Integration Bus can be used for connectivity to web services and web service appliances.
As shown in the figure, SOAP messages contain the data that is passed between the web service
provider and the requester. SOAP messages are expressed in XML and can be delivered over
HTTP or JMS transport. IBM Integration Bus supports both protocols. So, in a message flow, web
services can be requested and aggregated. A message flow can be deployed as a web service,
listening to incoming SOAP requests on HTTP or JMS.
IBM Integration Bus can use the IBM DataPower appliance to handle its web services security
processing by providing HTTP/HTTPS encryption and decryption. Web Services Security (WSSecurity) describes enhancements to SOAP messaging to provide quality of protection through
message integrity, message confidentiality, and single message authentication.
Web services can be looked up dynamically in IBM WebSphere Service Registry and Repository.
WebSphere Service Registry and Repository is a central repository of documents. These
documents describe services, service interfaces (for example, SOAP over HTTP), and associated
policies that control access.
.
More information about WebSphere Service Registry and Repository, DataPower, and their use
with IBM Integration Bus is provided in a later unit.
Web service support with IBM Integration Bus is described in detail in WM675, IBM Integration
Bus V9 Application Development II.
22
Slide 22
IBM Integration Bus integration services for SOA
Well-defined containers of integration logic that are created

for and are inside the bus
Defined through standard resources
WSDL (port type) defines the service interface
Service interface defines one or more operations
Service Descriptor (XML) ties the service interface with the
implementation
Simple lifecycle for services creation and management

Simple creation of new integration services
Deployment is the same as standard integration applications
In Integration Bus, an integration service is a specialized application with a defined interface that
acts as a container for a web services solution. It contains message flows to implement the
specified web service operations. The interface is defined through a WSDL file.
In Integration Bus, you can create an integration service by using any of the following methods:
You can create an integration service from scratch.
You can create an integration service by selecting an existing WSDL
You can create an integration service from a Business Process Manager integration
service
When you implement an integration service, you can deploy it to an Integration Bus integration
server. You can start and stop the deployed service as you would an application. A web service
consumer can interrogate the deployed service to return its interface.
23
Slide 23
IBM Integration Bus publish/subscribe

Subscriber B
Publisher A
Data
Queue manager
QM A
SB Q
Integration node
Control Q
Data
Input
QM B
Publish
XmitQ
Data
QM C
SC Q
Subscriber C
Shared common publish/subscribe domain with WebSphere MQ for

topic and content-based operations
IBM Integration Bus connectivity can be published as a WebSphere MQ
publication
WebSphere MQ queue manager delivers the publication to all subscribing
applications that match the topic, and other options that are specified on their
subscriptions
Integration Bus and WebSphere MQ share a common publish/subscribe domain for topic and
content-based operations. A common publish/subscribe domain connects the Integration Bus
comprehensive transport and format support to the WebSphere MQ messaging backbone.
There are two situations where you can use publish/subscribe in Integration Bus:
To provide more transformation or routing function, or both, at publication time.
To filter messages based on the content of the body of the message.
As shown in the figure, messages are supplied to the message flow by applications that publish
messages. These applications are referred to as publishers. Messages are retrieved from the
message flow by applications that registered a subscription with an integration node. Those
applications are referred to as subscribers. A subscription defines the interest that a subscriber
has in published messages.
Publish/subscribe is described in detail in course WM675, IBM Integration Bus V9 Application
Development II, which is a continuation of this course.
24
Slide 24
IBM Integration Bus runtime security

Identifies who is authorized to submit a message to a message flow
IBM Integration Bus Runtime Security Manager controls
Allows end-to-end processing on behalf of the identity in the message
Specifies identity authentication, mapping, authorization, and propagation
Administrator configures by using security profiles
Uses centralized security provider

LDAP for authentication and authorization
IBM Tivoli Federated Identity Manager for authentication, authorization, and
mapping
Can be delegated to the transport (WebSphere MQ Object Authority

Manager)
Can be offloaded to a WebSphere DataPower appliance
Specifies resources that are accessible to that message flow
It is important to secure access to IBM Integration Bus applications and, in many cases, it is also
necessary to secure the message data.
When you are designing an IBM Integration Bus application, it is important to consider the
security measures that are needed to protect the information in the system. When a message
arrives at an input node, a security profile is used to indicate whether runtime security is
configured. The security profile specifies the combination of authentication, authorization, and
mapping that is done with the identity of the message, and by what external security provider.
The security manager of the integration node is called to read the security profile.
The security manager can control access to message flows on a per-message basis by using the
identity of the message. The integration node can:
Extract the identity from an inbound message.
Authenticate it (using an external security provider).
Map the identity to an alternative identity (by using an external security provider).
Check that the alternative identity or the original identity is authorized to access the message
flow (by using an external security provider).
Propagate the alternative identity or the original identity with an outbound message. The
actions to take for a message flow are controlled by using new security profiles. The
integration node administrator creates security profiles; the security manager accesses them
at run time.
At subsequent processing nodes in the message flow, it might be necessary for an identity to be
used to access a resource such as a database. The identity that is used to access such a
resource continues to be a proxy identity, either the identity of the integration nodes or an identity
that is configured by using a command. The resource is accessed by using the appropriate proxy
identity.
25
Two external security providers are supported so that the integration node can participate in a
centralized security framework: LDAP for authentication and authorization and Tivoli Federated
Identity Manager for authentication, mapping, and authorization
Security is described in detail in course WM675, IBM Integration Bus V9 Application Development
II and WM645, IBM Integration Bus V9 System Administration.
26
Slide 25
Migration from WebSphere Message Broker

From WebSphere Message Broker V7 and V8
All development assets are imported directly, such as message flows, ESQL,
models, and maps
Migrate brokers with a single command, or create new integration nodes for
phased migration
No broker redeployment necessary when using a built-in migrate command
All existing broker archive files can be deployed to IBM Integration Bus
integration nodes without change
Flexible co-existence options remove the need for extra hardware when
migrating
For an in-place migration for WebSphere Message Broker V6.1, you

must upgrade the broker and its queue manager at the same time
because there is no common WebSphere MQ version to support both
WebSphere Message Broker V6.1 and IBM Integration Bus
Migration commands for in-place migration include the migration of
configuration data
IBM Integration Bus makes it simple to move applications from WebSphere Message Broker. All
development assets such as message flows, ESQL and Java code, message models, and maps
import directly into IBM Integration Bus.
You can migrate brokers with a single command. No broker redeployment is necessary when you
use the built-in migrate command.
You also have many options for moving your brokers and execution groups to integration nodes
and integrations servers, including flexible co-existence options.
27
Slide 26
Conversion from WebSphere Enterprise Service Bus

Built-in conversion tools for WebSphere Enterprise Service Bus source
Initial emphasis is on web services use cases

No minimum version requirement of WebSphere Enterprise Service Bus source
Builds directly into WebSphere Enterprise Service Bus conversion editor
Remaining manual tasks are provided in a task list
IBM Integration Bus provides tools that help to convert existing WebSphere Enterprise Service
Bus assets so that they can run on IBM Integration Bus. The tools enable:
WebSphere Enterprise Service Bus Project Interchange files to be imported and viewed
Common flow primitives to be converted automatically while maintaining the flow structure
An understanding of remaining manual tasks through a task list
Resulting flows to be modified and deployed
The conversion tool is built upon an extensible framework, enabling further enhancements that
reduce the number of manual tasks required.
The support for all WebSphere Enterprise Service Bus primitives is a staged implementation.
New primitives will be added in subsequent releases of IBM Integration Bus.
28
Slide 27
Unit summary
Having completed this unit, you should be able to:
Explain the position of IBM Integration Bus within the IBM WebSphere
Reference Architecture
You have now completed this unit.

Having completed this unit, you should be able to:
Explain the position of IBM Integration Bus within the IBM WebSphere Reference
Architecture
29

ZM665 Unit01 Script

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZM665 Unit01 Script

Uploaded by

Copyright:

Available Formats

ZM665 Unit 1 Transcript

Copyright IBM Corporation 2013

Introduction to IBM Integration Bus

ZM665 Unit 1 Transcript

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM WebSphere reference architecture

ZM665 Unit 1 Transcript

ZM665 Unit 1 Transcript

Enterprise service bus (ESB)

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM ESB products

Service visibility and governance

IBM Integration Bus

Copyright IBM Corporation 2013

An ESB can be implemented in a service-oriented architecture by using various IBM products.

ZM665 Unit 1 Transcript

Introducing IBM Integration Bus

A natural evolution for WebSphere Message Broker applications

Incorporates WebSphere Enterprise Service Bus use cases

ZM665 Unit 1 Transcript

IBM Integration Bus as an ESB

Integration without bounds with universal connectivity and

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM Integration Bus architecture

Integration node (broker)

ZM665 Unit 1 Transcript

IBM Integration Bus as a message broker

Receives and routes messages

Transforms messages to an alternative representation

A message broker is required to provide more application connectivity services to implement an

ZM665 Unit 1 Transcript

IBM Integration Bus features

WebSphere Enterprise Services Bus conversion

Transforms and routes messages from anywhere, to anywhere

Operational management and performance

ZM665 Unit 1 Transcript

IBM Integration Bus benefits

Patterns for top-down, parameterized connectivity of common use cases

Dynamic and intelligent

High performing and scalable

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

Supported hardware and software environments

Virtual images for efficient use and simple provisioning

Virtualized environments such as VMWare and AIX Hypervisor

Access to full range of industry standard databases and ERP systems

DB2, Oracle, Sybase, SQL Server, Informix, and solidDB

ZM665 Unit 1 Transcript

Technology components and prerequisites

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM Integration Bus components

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM Integration Toolkit

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript

IBM Integration Explorer

Can be run as a stand-alone application

Copyright IBM Corporation 2013

ZM665 Unit 1 Transcript