WTUI9 - Conversion from WebSphere Enterprise Service Bus to IBM Integration Bus

I9: WebSphere ESB conversion to

IBM Integration Bus

Alex Wood Developer IBM Integration Bus

IBM Hursley, UK

© 2014 IBM Corpora/on

Please Note IBM’s statements regarding its plans, direc/ons, and intent are subject to change or withdrawal without no/ce at IBM’s sole discre/on. Informa/on regarding poten/al future products is intended to outline our general product direc/on and it should not be relied on in making a purchasing decision.

The informa/on men/oned regarding poten/al future products is not a commitment, promise, or legal obliga/on to deliver any material, code or func/onality. Informa/on about poten/al future products may not be incorporated into any contract. The development, release, and /ming of any future features or func/onality described for our products remains at our sole discre/on

Performance is based on measurements and projec/ons using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considera/ons such as the amount of mul/programming in the user’s job stream, the I/O configura/on, the storage configura/on, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

2

Agenda • WESB convert roadmap •  Approaches to conversion • WESB Convert Tool

– What’s new in the open beta – WESB Convert Tool Demo – Extending the conversion tool

•  ESB Topology Considera/ons

© 2014 IBM Corpora/on 3

WESB Convert Roadmap

IBM's plans, directions, and intent are subject to change

or withdrawal

IBM Integra1on Bus v9 Q2 2013

WESB Convert Tool Added

IBM Integra1on Bus vNext

IBM Integra1on Bus v9.0.0.1 Q4 2013

IBM Integra1on Bus v9.0.0.2 Q2 2014

IBM Integra1on Bus open beta (current) WESB convert tool enhancements: •  New built-‐in converters for most primi/ves •  New built-‐in converters for most export bindings •  New mul/ple media/on components supported •  New media/on components with mul/ple interfaces supported •  New mul/ple exports supported

Further WESB convert function will be delivered regularly into the open-beta

between now and vNext. Find out what’s new in the latest beta here : https://ibm.biz/iibwesbconvert

EOS dates for WESB Announce Q1 2013

End of Marke/ng (EoM) and End of Support (EoS)

Product Version GA Date EoM Date EoS Date

WESB 6.2 7.0 7.5

Jan 2009 Jan 2010 Jun 2011

Jan 2013 Apr 2015 Apr 2015

30 Apr 2018 30 Apr 2018 30 Apr 2018

WESB Retail Store Edi1on

7.0 7.5

Apr 2010 Jun 2011

Apr 2015 Apr 2015

30 Apr 2018 30 Apr 2018

WESB Registry Edi1on 7.0 7.5

Oct 2010 Jun 2011

Jan 2014 Jan 2014

30 Apr 2018 30 Apr 2018

WESB for z/OS 6.2 7.0 7.5

Dec 2008 Oct 2010 Jun 2011

Apr 2013 TBD TBD

30 Apr 2014 30 Apr 2018 30 Apr 2018

Announcement: hUp://bit.ly/Of2Cb1

Transfer Licensing and Modes of Opera/on

IBM Integration Bus

Advanced license

Standard license

Express license

WESB Transfer license

Scale mode Express mode Standard mode Advanced mode

New

•  Express: A limited set of nodes are enabled for use within a single execu1on group. Message flows are unlimited.

•  Scale: A limited set of nodes are enabled for use within unlimited execu5on groups. Message flows are unlimited.

•  Standard: All features are enabled for use with a single execu1on group. The number of message flows that you can deploy are unlimited.

•  Advanced: All features are enabled and no restric1ons or limits are imposed. This mode is the default mode, unless you have the Developer Edi1on.

WebSphere ESB

Benefit from the IBM ESB strategy

REST Services

Web Services

Database MQ, JMS Files CICS/ IMS

ERP/ EIS/CRM

Security Transformation of well formed data XML, JSON, COBOL, Fixed Width & Delimited

Routing & Composition

Java

IBM Integration Bus

Transformation of any data XML, JSON, COBOL, C/C++, Fixed Width, Delimited,

EDIFACT, ISO8583, HL7, COBOL, NACHA, 4690-TLOG …

Java

Mobile

IoT

WebSockets

TCP/IP

Security Routing & Composition

Analytics

Workload Management

0

20

40

60

80

100

120

140

160

180

200

Audit Logging

Decision Services

Elastic Cache

Pattern- based Dev

No charge for developers Deployable full

active/active HTML5 web

admin/monitoring

Streamlined to ESB use case

High scale MQ events/messaging

Conversion Offerings from IBM SW Services and Partners ISSW Summary offerings Conversion Introduc1on (CI) GOAL: Client wishes to understand the IBM Integra/on so`ware strategy in more detail and what they might

need to consider to plan for a successful conversion from WESB. FORMAT: Remote presenta/ons and conference calls (<= 4 hours dura/on in total) Conversion Planning Workshop (CPW) GOAL: Client wishes to understand more detail on the implica/ons of conversion as it specifically relates to

their own deployment of WESB in order to build an ini/al conversion roadmap or plan. FORMAT: Conducted on site in IBM consultant led workshop (3-‐5 days) Conversion Quick-‐Start (CQS) GOAL: Client par/cipated in a CPW (or equivalent) which has resulted in selec/on of this offering, which is a

typical “Quick Start” style engagement to accelerate client adop/on. FORMAT: This ac/vity will be conducted at client loca/on by ISSW in IBM consultant led workshops and hands-‐

on mentoring. (typically 2-‐4 weeks). Conversion Quick-‐Win Pilot (CQWP) GOAL: Client par/cipated in a CPW (or equivalent) which has resulted in selec/on of this offering, for delivery

of a well-‐defined pilot project to accelerate conversion and build confidence FORMAT: On site pilot project within an agreed /me frame

Approaches to conversion

Possible approaches to conversion There are two key parts to the conversion: •  Future integra/on solu/ons •  Exis/ng integra/on solu/ons


Look to move future development of integra/on solu/ons to IBM Integra/on Bus.

Limi/ng future development on the WebSphere ESB plagorm

will minimise the poten/al conversion work. If future development is required on WebSphere ESB, then structuring this in a IIB friendly manner is sensible to allow straight forward conversion.


Understand the exis/ng WebSphere ESB estate and determine the best approach for conversion to IIB.

Conversion of exis/ng integra/ons is normally handled using a combina/on of the following strategies:

•  Run in parallel •  Gradual migra/on toward IIB •  Immediate migra/on towards IIB

• Run in parallel – Wait –  Move future development of integra/on solu/ons to IIB. –  Start training ac/vi/es to understand IIB as the target plagorm for future applica/ons –  Wait to convert exis/ng WebSphere ESB estate. –  Build long term plan for conversion to IIB. –  Consider the infrastructure and license requirements for running in parallel

• Gradual migra/on toward IIB –  Ini/ate conversion pilot to build skills and learn lessons. –  Phased conversion of integra/on solu/ons. –  Run in parallel un/l conversion complete. –  Consider the infrastructure and license requirements for running in parallel

• Immediate migra/on towards IIB –  Determine the sizing of the overall migra/on and the associated risk. –  Determine if a fall back strategy is required –  Generally only recommended for customers with a limited WebSphere ESB deployment or

at the early stages of deployment

13

Possible approaches to conversion

Considera/ons for conversion •  Topology

–  From WESB Golden Topology to.. –  The choice of topology depends on the customers specific needs. –  Star/ng point would an ac/ve – ac/ve topology with mul/ple parallel IIB nodes. More later..

•  Monitoring –  Similar granularity of monitoring. –  IBM or 3rd party external monitoring solu/ons. –  IIB built-‐in monitoring and sta/s/cs support.

•  Security –  WESB based on WAS security model. –  IIB supports LDAP, SSL, User Token, SAML etc. –  Security gateway..

•  Administra1on and opera1ons –  WESB based on WAS admin model –  IIB supports scrip/ng for administra/on and opera/ons.

•  Applica1ons –  Analyze your WESB applica/ons and categorize according to the ease and approach of conversion. ….

•  Architectural approach –  Consider your WESB architectural approach and plan an architectural approach in IIB. –  Similarity of approach will effect the conversion strategy for applica/ons.

14

•  Category 1: Tool accelerated –  The conversion tool is a sensible approach and the resul/ng applica/ons will require limited

customiza/on. –  Extensive use of the tool as-‐is for conversion.

•  Category 2: Tool assisted –  A standard template is used across mul/ple integra/on solu/ons and customiza/on of the

conversion tool or palern templates represent a sensible approach to accelerate the conversion. –  Extensive use of the tool with customiza/ons.

•  Category 3: Manual conversion –  The core func/onality is available within the product. –  The integra/on solu/on may contain extensive custom use of custom code. –  Due to the complexity of the solu/on a literal mapping of primi/ve to corresponding nodes

would provide a sub-‐standard solu/on. –  The customer may wish to combine conversion with a change of architectural approach. –  Some use of the tool to kick start conversions.

•  Category 4: Custom solu1on – –  Similar to category 3, custom coding need in addi/onal to core func/onality in the product.

15

Applica/on Conversion Categories

WESB to IIB Conversion tooling

Accelerate conversion of WebSphere ESB source artefacts to IIB.

•  Built-‐in conversion tools for WESB source assets –  Accelerate conversion of WESB source assets to IIB source assets. –  Tool improvements increase breadth and depth on conversion. Reducing further

work. –  Open framework for user and partner extensions to allow customiza/on of the tool.

Conversion from WebSphere Enterprise Service Bus

•  Simple workflow creates IIB resources 1.  Export WESB PI from IID 2.  Import media/ons into Eclipse Toolkit 3.  Right-‐click “convert” task to start conversion 4.  Follow guided editor to generate resources 5.  Task List will iden/fy remaining manual steps 6.  Iterate as necessary

Architectural Concepts

Web Service Client

IIB Service or Application

Web Service Provider 1


Flow

Mediation Flow Component Export

Binding

Function Selector

Import

Binding

Subflow: Operation 2 Request_Response

Subflow: Operation 1 Request_Response

Operation 1 Request

Operation 1 Response

Import

Binding Operation 2 Request

Operation 2 Response

Web Service Client



WebSphere ESB

IBM Integration Bus

What’s new in the tool .. •  At IIB v9 the tool offered some capability to convert web

services based integra/ons. –  Single export, single media/on component, single import. –  Web services binding only. –  Built-‐in converters for few mid-‐flow primi/ves

•  New capabili/es in IIB open-‐beta (current) expand the breadth and depth of conversion –  Convert mul/ple exports with any binding –  Convert mul/ple connected media/on components with mul/ple interfaces –  Built-‐in converters for most mid flow primi/ves –  WESB style encapsula/on of logic –  Enhanced Documenta/on

•  What next ? –  Look out for further enhancements as they appear in the IIB open-‐beta : hUps://ibm.biz/iibopenbeta hUps://ibm.biz/iibwesbconvert


or withdrawal

What’s new in the tool ..

New built-in primitive converters

New built-in binding converters New Multiple Export

New Multiple Mediation Component IIB open-beta (current)

IIB v9(GA)

+

Some built-in primitive converters

Built-in converter for WS binding only

Single Export Single MFC Single Import

Look out for further updates at : https://ibm.biz/iibopenbeta


or withdrawal

WESB Convert Tool

Demo

Example Media/on Module -‐ IID

Multiple Exports with different

bindings

Mediation Component with

multiple interfaces

Import with Webservices

binding

Example Media/on Module -‐ IID

Message Flow with wide variety of primitives and complex wiring

Import WESB source projects into IIB Studio

Import WebSphere ESB source projects into IBM Integration Studio

Launch Conversion tool directly from

import

Create WESB Conversion tool session

Create a new conversion session.

This will persist any state associated with the conversion, such as TODO tasks generated by the conversion.

WESB Conversion tool in IIB Studio

Select mediation projects and libraries

to include in the conversion.


Choose resources to convert. eg. By default only maps

referenced in the module will be converted.


Choose conversion options. Optionally replace Built-in converters

for primitives and bindings with custom converters.

Use the built-in converters And optionally Extend the tool with custom converters for specific primitives or Export/Import bindings



Final summary of conversion

Start the conversion process

Conversion Tool – IIB open-‐beta Example

Convert tool produces IIB services and applications and a list of documented follow-on tasks for the user.


Conversion Results


Conversion Results

Task list containing specific post tool conversion tasks.

Verbose description of the task with links to more detailed documentation

Export binding logic encapsulated in a export request and export response subflow


Import binding logic encapsulated in a subflow


Each mediation component request / response / error operation flow encapsulated in a separate subflow for easy correlation with the original source.


Original flow wiring preserved.

Built-in converters convert to equivalent IIB node set.


Customizing the Tool for your needs •  The conversion tool is designed to be extensible. – Users can author custom conversion logic for media/on primi/ves and import/export bindings whilst leveraging the capabili/es of the tool for everything else.

•  Conversion tool source code is open and available on gitHub. – Users can modify the tool to for their specific needs.

Extending the Conversion Tool •  Nearly all primi/ves and export/import bindings (as of current open-‐beta)

are handled by a Built-‐in Converter class out of the box. •  However user-‐defined converters may help a specific customer where

they have repeatable conversion logic they wish to include in the conversion.

•  Extension points allow re-‐usable customer specific customiza/ons of the tool.

•  You can create a Java converter class which extends AbstractMediationPrimitiveConverter, which will provides a primi/ve conversion capability specific to a customers needs.

•  You can create a Java converter class which extends AbstractBindingConverter, which will provides a export/import binding conversion capability specific to a customers needs.

Extending the Conversion Tool

Modify the tool. WESB to IIB Conversion Tool on GitHub open source community

hlps://github.com/ot4i/open-‐convert

System Topology

Hardware Load Balancer

WebSphere Enterprise Service Bus Golden Topology

43

Server

Physical Server

Server Server Server

Physical Server

Server Server

Server Server Server Server Server Server

Server Server Server Server Server Server

Application Cluster

Support Cluster

Messaging Cluster

IHS IHS


ME DB

Support DB

The Golden Topology is the standard produc/on template which is customized to meet a number of quality of service requirements. The par/cular setup used may remove the support cluster and load balancers but most customers use the below as a template.

Considera/ons •  High Availability of the solu/on •  Recover in-‐flight requests •  Applica/on isola/on •  Applica/on persistent requirements •  SIB JMS Bindings •  Asynchronous Bindings correla/on informa/on •  Long running integra/on logic •  Event Sequencing •  Target IIB Version

44

IBM Integra/on Bus Topology •  Build an IBM Integra/on Bus topology for your needs

–  Use the simplest topology and feature set that fits your needs –  No single ‘golden topology’ recommenda/on

•  The below represents a founda/on star/ng point –  Ac/ve-‐ac/ve infrastructure –  Complete for stateless HTTP workloads

Physical Server

Integration Node Integration Node

MQ Queue Manager

HTTP Listener



Physical Server


MQ Queue Manager

HTTP Listener

Integration Server

Integration Server

IIB V9 topology

Physical Server

Notable differences to WESB golden topology •  Not all nodes are created equal

–  Could choose to have a different set of servers on each node –  Could choose to have a different set of applica/ons (or ‘flows’) on the servers of each node –  Simple scrip/ng interface provided for roll-‐out across a set of nodes

•  HTTP distribu/on handled within the Integra/on Node –  IHS can also be layered into the solu/on

•  Ac/ve-‐ac/ve messaging run/me –  MQ is ac/ve on a par/cular machine (V9)

Integration Node Integration Node HTTP Listener



Physical Server

Integration Node Integration Node HTTP Listener

Integration Server

Integration Server

IIB V9 topology

MQ Queue Manager MQ Queue Manager

Physical Server

Stateful logic – overview •  State in WESB is commonly stored in the Messaging layer

–  A single highly available Messaging Engine that ‘floats’ across the servers (ac/ve-‐passive) –  A Database used under the covers to make that state available across the cluster

•  The equivalent in IIB –  Embedded Global Cache , State stored on MQ bound to a node for EDA nodes. –  No Database Required


MQ Queue Manager

HTTP Listener

Physical Server


MQ Queue Manager

HTTP Listener

Global cache

Integration Server

Integration Server

IIB V9 topology

Current In-production integration

WESB/IIB Combined Topologies Run In Parallel

Service Consumers Service Exposure Integration Hub Adaptation

New IIB-Based Integration

Service Providers

WESB

IIB


DataPower appliances frequently used with WESB for Security and QOS …this can easily be extended to exploit new IIB-‐based integra/on

Service Consumers Service Exposure Integration Hub Adaptation

New IIB-Based Integration

Service Providers

WESB

IIB

DataPower

WAS IHS configured to provide a uniform URL scheme

•  The IBM HTTP Server supplied as part of WAS can be configured to treat IIB and WESB-‐based services as part of a uniform URL scheme

Service Consumers Service Providers


WESB

New IIB-Based Integration IIB

WAS IHS

Summary •  WESB Conversion Tool Roadmap •  WESB distributed EoS dates in 2018 •  Transfer Licence from WESB to IIB Scale •  Plan your to approach to conversion depending on your exis/ng WESB estate and requirements.

•  New updated WESB to IIB conversion tooling to accelerate conversion of source artefacts. –  Regular updates in IIB open-‐beta.

•  WESB to IIB topology considera/ons

© 2014 IBM Corpora/on

For Addi1onal Informa1on •  IBM Integra/on Bus vNext open beta:

–  What’s new: hUps://ibm.biz/iibopenbetawhatsnew –  Download: hUps://ibm.biz/iibopenbeta –  Documenta1on: hUps://ibm.biz/iibopenbetadocs –  Discuss: hUps://ibm.biz/iibopenbetaforum

•  IBM Integra/on Community: –  IIB community hUps://ibm.biz/iibcommunity

–  WESB Convert Wiki hUps://ibm.biz/iibwesbconvert –  WESB Convert Topologies hUps://ibm.biz/iibwesbconvert_topologies

52

Thankyou Alex Wood

[email protected]

I9: WebSphere ESB conversion to IBM Integration Bus

Technology

WTUI9 - Conversion from WebSphere Enterprise Service Bus to IBM Integration Bus