IBM Integration Bus & Transformation Extender: One Platform for Internal & External Integration HBB-2467

(1)

IBM Integration Bus & Transformation Extender:

One Platform for Internal & External Integration

HBB-2467

Brian E Wilson

IBM Cloud Middleware Connectivity & Integration Solution Architect

Member of the IBM Academy of Technology

(2)

Please Note:

1

• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole

discretion.

• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in

making a purchasing decision.

• The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any

material, code or functionality. Information about potential future products may not be incorporated into any contract.

• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

• Performance is based on measurements and projections 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 considerations such as the

amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed.

Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

(3)

Agenda

• IBM Integration Bus

• IBM Transformation Extender and IBM Transformation

Extender Advanced

• Using IBM Transformation Extender Advanced with IBM

Integration Bus

• Using IBM Integration Bus and IBM Transformation

Extender Advanced with IBM Business Monitor

(4)

(5)

Business

Problem

Business applications can not exist in isolation, they need to be able to exchange data with

other applications to maximise value.

• Enterprise IT consists of many systems; off‐the‐shelf applications, services, packaged

apps (SAP, Siebel etc.) Web apps, devices, appliances, bespoke software and many

more.

• Systems expose interfaces using different protocols such as APIs, MQ, TCP/IP, database,

HTTP, files, FTP etc. and with a myriad of standards based and custom data formats.

• Building connections Point‐to‐point quickly deteriorates into spaghetti chaos, an

inflexible architecture which is expensive to maintain and resistant to change.

Business

Need

Solution

Benefits

IBM Integration Bus connects these endpoints in meaningful ways

 Avoids rewrites

in response to new integration requirements

 Simplifies maintenance

by reducing expensive coupling

 Adds Flexibility

introducing anonymity between producers and consumers of data

 Provides

insight

into applications and business value they bring



A

proven, scalable and secure integration platform

that delivers rapid, secure, scalable

and reliable connectivity.



Largest breadth of

adapters, platforms and protocols

supported.



Industry relevant connectivity to solve domain specific problems.

Industry specific

nodes, solution‐oriented patterns & user‐oriented tooling.

(6)

Enterprise service bus technology for

rapid mobile-enablement of existing

applications and services

Universal Integration of applications, processes and data

IBM Integration Bus v10

Key Capabilities

Business Value

• Complete enterprise service bus

• Heterogeneous integration

• Rapid Pattern‐based integration

• Rapid API integration

• Built‐in application adapters

• Industry Packs

• Accelerate integration of

(decoupled) systems

• Increased IT flexibility

• Preserve integrity of transactions

IBM’s Strategic Integration

(7)

High

Value

Simple

_{Develop, deploy, manage and migrate integration solutions quickly and easily}

Easy to Learn and Use

Market leading performance

Highly scalable proven to handle high message volumes in simple and complex IT

environments

Universal & independent connectivity

Extensive support for open, and industry standards for transports and data, commercial

applications and more

Automate and Simplify

Minimize custom coding and reduce design, build and test costs by 40% to 60%

No vendor lock in

Open standards leadership for integration. A technology neutral platform that works

on the widest possible range of hardware, software and virtualized environments

Comprehensive, award-winning software

Built in features that simplify and extend value:

Global cache, WLM policies, decision services, monitoring and more

Fast

Integrated

Cost

Saving

Open

(8)

Easy to Create Solutions

• Built-in nodes encapsulate transports, technologies and applications

– Makes common tasks easy, and the complex ones possible!

– Use the built-in nodes to reduce the amount of custom code required

(9)

(10)

Universal Transformation

9

“Transformation is the hard, ugly part of integration”

-Ted Friedman, Research VP, Gartner

Key Challenges and Pain Points

–

Connecting all your assets to your SOA / ESB

–

Complying with industry and regulatory

standards in timely manner

–

Maintaining currency with standards

–

Mediating incompatible data formats

between applications and data stores

–

Maximizing previous investments in

packaged applications & enterprise

information systems

–

Deploying costly hardware capacity for elastic

transformation demand

"Organizations pursuing service-oriented

integration involving document-oriented,

proprietary, legacy or modern XML-oriented data

standards… should consider products capable of

automating complex data transformation as an

important building block of their integration

architecture."

Massimo Pezzini, VP and Distinguished Analyst,

Gartner

(11)

IBM Transformation Extender

10

The

evolution

of the IBM’s

Universal Transformation

strategy, providing a modular, comprehensive solution

for standards transformation

Transformation

Document Onboarding

WTX Maps

B2Bi

Maps

XSLT

Maps

Supply Chain Healthcare Financial Payments

Enveloping

De‐

Enveloping

Validation

Acknowledge

ments

Industry Standards

(12)

Name Change……

11

IBM Transformation Extender

(ITX)

WebSphere Transformation Extender

Standards Processing Engine

IBM Transformation Extender Advanced

(ITX Advanced)

(13)

New Packaging….V9

12

IBM Transformation Extender

(formerly WTX)

– Design Tools

• TX Design Studio, GDM (unlimited)

– Runtime

• TX (All editions: Launcher, Cmd Server, TX4AP, TX4IS), XSLT

IBM Transformation Extender Advanced

(formerly SPE)

– ITX + B2Bi translator, B2Bi Mapper

– Trading partner management

– Enveloping/de-enveloping

– Acknowledgements

IBM Transformation Extender Packs

– Healthcare (HIPAA)

– Supply Chain EDI (X12, EDIFACT, Tradacoms)

– Financial Payments (SWIFT, SEPA, ISO20022)

Trade up

ITX ITX Advanced ITX Pack ITX Pack ITX

Options

(14)

New Packaging….

13

WTX for Integration Servers

WTX for Application Programming

WTX with Command Server

WTX with Launcher

WTX Design Studio

ITX

IBM Integrations

3 rd

_Party

Integrations

Batch Mode

Orchestrator

(15)

Transformation Themes

14



Healthcare / HIPAA



ACA compliance: WEDI/SNIP 1-7



Ready-to-execute templates and compliance validation for HIPAA

standard



Consistent, reusable and scalable transformation & document

processing capability



Financial Payments



Capabilities targeting payment requirements



SWIFT, SEPA, Generic ISO 20022 messages



Consistent, reusable and scalable transformation & document

processing capability



Universal Transformation



Deploy a single, universal transformation solution that works across

all SOA / ESB assets



Systematically connect assets to messaging infrastructure, mediate

data formats between applications and data stores, and maximize

previous investments in applications & enterprise systems

(16)

What Does IBM Transformation Extender Do?

15

It takes any kinds of data

from it’s native form

Processes them together,

natively, with NO CODE

And outputs them into their

native target formats

(17)

16

• Code-free design and deployment

• Real time execution of complex transforms and

enhancements

• Ontological data model for all data types

• In-process data validation

• One engine, multiple deployment options

(18)

Components of an IBM TX solution

/

Destination Data Structure

Packs

Industry Standards

/

Importers

MetaData

Type

Desig

ner

Type

Desi

gner

Maps in

Design

Studio

Business

Rules

Web Services

Adapters

Sterling Database File Email JAXB Java …more

Type

Trees

In

Design

Studio

Type

Trees

In

Design

Studio

Source Data Structure

(19)

Adapter

Type Tree

• An IBM TX solution is composed of the following:

Rules

Type Tree

Adapter

Mapping

Source

Destination



In other words…



An adapter is a technical connector which can be

“plugged” into a source or destination - without parsing!



A Type Tree is a graphical representation of meta-data



Rules define how a Source structure is transformed to a

Destination structure



Together these components form an IBM TX Map



Now you can deploy to any environment you choose

(20)

19

IBM Transformation Extender Advanced is the next

evolution of the IBM

Universal Transformation

strategy,

providing a modular and more comprehensive solution

for transforming documents based on

industry standards

(21)

• A product, from the IBM Commerce portfolio and the same lab as WebSphere

Transformation Extender, that can run on top of IBM Integration Bus

• Can provide full EDI processing capability, including partner management

• EDI Validation and Acknowledge generation

• DeEnveloping and Enveloping support

• Is IBM’s MOST powerful HIPAA solution (HIPAA Level 1 through 7 support)

• This means that we can offer a single integration solution, IBM Integration Bus

with IBM Transformation Extender Advanced, for both internal integration and

B2B integration

• Takes advantage of IIB scalability and performance

• Still need a B2B gateway in this solution

(22)

(23)

Architecture: IBM’s Vision for B2B, Transformation & Standards

Managed File Transfer

Perimeter security

Industry Standards

Financial Services

Financial Services Supply ChainSupply Chain Healthcare

Healthcare Customer DefinedCustomer Defined

AdaptersAdapters Adapters Orchestration & Infrastructure Orchestration & Infrastructure Orchestration, Routing & Infrastructure

Community Management Visibility

Mailboxing Edge Communications Edge Communications Edge communications

• Modularize our approach to

address complex

integration challenges

• Address changing market

requirements including high

availability, real-time

processing, archival, and

standards processing

• Provide a best of breed, end

to end experience focused

on customer excellence

• Built on the strategic IBM

technologies enterprises

can use to grow their

business and improve

operational efficiencies

(24)

• Provides comprehensive transformation support including metadata, compliance

checking and related processing functions for key supply chain standards

• Helps enable organizations to:

– Add additional EDI transformation capabilities to an IIB infrastructure

– Rationalize multiple disparate EDI systems and scale to global EDI

– Maximize previous investments in packaged applications & enterprise information

systems

• The solution provides:

– A modular, scalable document processing capability for X12 up to version 6040 and

EDIFACT up to D.11A and D.11B

– Ready-to-execute templates and compliance validation for X12 and EDIFACT

– Tight integration with IBM's best-of-breed middleware solutions such as IBM Integration

Bus

(25)

ITX Pack for Healthcare Payer

• New US “Administrative

Simplification” mandates will

significantly increase

transaction complexity and

transaction volumes for

payers and providers.

24

Claim/Clinical Attachments: Additional Information to support a

Claim or Service. Expected to be mandated 2014

PACDR: Post Adjudicated Claim version for 837P, 837I, 837D –

new transactions possible mandate post 2014

Acknowledgments: partner based TA1, 999 and

WEDI/SNIP settings

Claim Level rejection and reporting capabilities

(277CA)

5010 Errata: incorporating most recent updates

WEDI/SNIP: types 1 to 5 (including external code

sets)

Configurable Rules : ability to disable WEDI/SNIP 3

& 4 rules

(26)

Modular: Universal Transformation and EDI Processing

• IBM Transformation Extender Advanced (Standards Processing Engine) is the next evolution of the

IBM Universal Transformation strategy, providing a modular and more comprehensive solution for

transforming documents based on industry standards

Validate and

Acknowledge

Debulking

Enrichment

Mapping

Addressing

Encoding

De-envelope Transform Envelope

(27)

Modular: Transformation Services

• Transformation maps define the structure of input and output data and the rules for

transformation between fields

• IBM Transformation Extender Advanced supports multiple strategic mappers: WebSphere

Transformation Extender, Sterling B2B Integrator and XSLT (using GDM) maps

• Maps may be persisted in the

provided map repository, on a

local file system or stored in an

external repository and passed

to the engine in memory

• A repository for XML schemas

and DTDs is provided and may

be used by the engine for

(28)

Modular: Universal Transformation and EDI Processing

• IBM Transformation Extender Advanced (Standards Processing Engine) is the next evolution of the

IBM Universal Transformation strategy, providing a modular and more comprehensive solution for

transforming documents based on industry standards

Validate and

Acknowledge

Debulking

Enrichment

Mapping

Addressing

Encoding

De-envelope Transform Envelope

Encoding

(29)

Modular: De-envelope Services

• Inbound envelope definitions

define the business meaning of

incoming messages

• Sender and Receiver and other

Standard IDs associate

incoming EDI data with

partners

• Control number sequence and

duplicate checking is optional

• Validation may be enabled,

disabled

• Acknowledgements may be

enabled and customized

• Data is de-bulked and optionally

transformed, allowing good

transactions to be handled

differently from transactions

which contain errors

(30)

Modular: Envelope Services

• Outbound envelope definitions instruct

the engine on how to process

outgoing data

• Sender and Receiver and other

Standard IDs associate outgoing EDI

data with partners

• Control numbers may be assigned,

either locally or globally

• Outgoing data may be transformed and

validated allowing valid transactions

to be handled differently from

transactions which contain errors

• Outgoing data may be enveloped and

delivered immediately or deferred for

later batch processing

(31)

Changing Requirements: Smarter Onboarding

correctly

with dynamic

forms

Configure

quickly

save as you go,

built in version

control

Handle

interruptions

Gauge the

Impact

of changes,

always show

dependant artifacts

(32)

Document Onboarding

31

• Inbound envelope definitions define the business meaning

of incoming messages; Outbound definitions instruct the

engine on how to process outgoing data

• Sender and Receiver and other Standard IDs associate

incoming data with partners

• Control number sequence and duplicate checking is

optional

• Validation may be enabled, disabled or delegated for both

inbound and outbound data

• Acknowledgements may be enabled and customized

• Data is de‐bulked optionally allowing good transactions to

be handled differently from transactions which are contain

errors

• Outgoing data may be enveloped and delivered

immediately or deferred for later batch processing

Import sample

documents to

create in/out

bound envelopes!

(33)

Trading Partner Management

32

• In a Dynamic User Interface:

• Only the fields that are used

by the envelope are shown

• Makes for a simpler, cleaner

interface with no confusing

array of options that don't

apply

• Mandatory fields always

default values when

applicable

• Produces consistent and

correct results

(34)

Smarter Onboarding – Version Control

 Smarter Onboarding uses a save-as-you-go strategy

 This allows you to stop and come back later to finish

 Mandatory fields always default values when applicable

 Artifacts are automatically versioned each time you save a form

 Editing and switching between versions is easy

(35)

Changing Requirements: Smarter Onboarding – Impact Analysis

 Smarter

Onboarding

provides..

– Visibility of

dependencies

– Quick links to

related artifacts

(36)

Changing Requirements: Clustering

Use a simple

properties

file to

point an ITX

Advanced node to a

database

Simply point each

node at the same

database, and they

will work together in

a

cluster

, sharing

partner

management and

state information

Transaction

volumes are

growing

and it is

becoming common

to be asked to

process single files

100s of GB in size,

containing millions

of transactions

Multiple ITX

Advanced nodes

can

scale

to meet

throughput needs

(37)

Host

App 4

Host

App 3

Clustering with Host Application

ITX

Advanced

Library

ITX

Database

Host

App 1

Host

App 2

Web

Server

Administrator

HA ITX

Database

(38)

Multiple Runtime Environments

 Sterling File Gateway (SFG)

 IBM Integration Bus (IIB)

 ITX Launcher

(39)

SPE Architectural Diagram with Different Hosts

ITX

Advanced

Library

SFG

ITX

Database

IIB

Java

Application

IIB

Web

Server

Administrator

HA ITX

Database

(40)

Using IBM Transformation Extender

with IBM Integration Bus

(41)

Strategic Technology: IBM Integration Bus

• The IBM Transformation Extender

Advanced engine has been

designed to leverage the

connectivity and orchestration

capabilities provided by IBM

Integration Bus

• Patterns are provided to quick start

the development of inbound,

outbound or transformation

Message Flows

• Events generated by the engine

may be published to a WebSphere

MQ queue for consumption by

external visibility and analytics tools

• Note:



SPE Requires IBM Integration Bus v9



ITX Advanced requires IBM Integration Bus v10

Transform Node

Wraps calls to the

Standards Processing

Engine’s transform

function to run a

WebSphere TX, Sterling

B2B Integrator or XSLT

map

Envelope Node

Encodes input data and

either prepares

documents for deferred

enveloping, envelopes

previously prepared

documents or envelopes

documents immediately

De‐envelope Node

De-envelopes input data

and returns

de-enveloped transactions,

acknowledgements and

transactions in error

(42)

Strategic Technology: IBM Integration Bus – De-envelope Node

• Use the De-envelope Node to de-envelope input

data

• Send enveloped data to the in terminal

• There are three output terminals and a failure

terminal

• Transactions which pass validation are sent, one

at a time, to the out terminal

• Transactions which fail validation are sent, one at

a time, to the error terminal

• Acknowledgements are sent to the ack terminal

• Exceptions are routed to the failure terminal

• The De-envelope Node has no basic properties,

but it can be configured to output intermediate

documents and a storage payload threshold can

be optionally specified

• Correlations and ProcessData are written to the LocalEnvironment

• An Interchange Compliance Report may be written to the LocalEnvironment for

transactions that are in error

(43)

De-envelope example – inbound X12 document

There are 4 terminals:

• Terminal 1 – OUT writes the translated output to queue Output and then is written to a

FTP server. It also writes out the Correlation and Process Data

• Terminal 2 – ACK writes out the acknowledgement (997, 999)

• Terminal 3 – ERROR writes out the error along with the Compliance Report which is then

formatted by a WTX map to remove some characters that interrupts the XML output

(44)

Strategic Technology: IBM Integration Bus – Envelope Node

• Use the Envelope Node to encode input data

• Send enveloped data to the in terminal

• Documents may be sent individually or sent together using a Collector Node

• There are two output terminals and a failure terminal

• Enveloped transactions which pass validation are sent to the out terminal

• Transactions which fail validation are sent, one at a time, to the error terminal

• Exceptions are routed to the failure terminal

• A SenderID, ReceiverID, AccepterLookupAlias and optionally an InterchangeID must

be specified in the LocalEnvironment before the Envelope Node is invoked

• The Envelope Node has only one basic property which controls whether it prepares

documents for deferred enveloping, envelopes previously prepared documents or

envelopes documents immediately

• It can also be configured to output intermediate documents, halt on error and a storage

payload threshold can be optionally specified

(45)

Strategic Technology: IBM Integration Bus – Envelope Node

• Prepare documents for later

enveloping

• Envelope previously prepared

documents (batching)

(46)

Strategic Technology: IBM Integration Bus – Transform Node

• Use the Transform Node to call the ITX Advanced engine’s transform function and run

a IBM TX, Sterling B2B Integrator or XSLT map

• Send input data to the in terminal

• Documents may be sent individually or sent together using a Collector Node when an IBM TX map is used • Messages in the MessageCollection are routed to similarly named input cards (in1, in2, etc.)

• There is always one failure terminal, but output terminals can be created as needed

• Sterling and XSLT maps only produce one output, sent to the default out1 terminal

• Output cards from WebSphere TX maps are routed to similarly numbered out terminals (out1, out2, etc.) • Exceptions are routed to the failure terminal along with a Translation Report in the ExceptionList

• The Transform Node has one basic property – the map name

• It can be configured with a storage payload threshold

• The map may be specified in the

LocalEnvironment

• MapName – specifies a map in the SPE repository

• MapServerLocation – specifies the path to a map on a local file system

• DynamicMap – passes a map to

SPE as an array of bytes

• Correlations and ProcessData are written to

the LocalEnvironment

(47)

(48)

47

• Healthcare Payer Pack examples

– HIPAA Envelope example

– HIPAA Deenvelope example

– C:\IBM\Standards Processing Engine 2.0.1\Healthcare_Payer_v8.5.1\examples

• Supply Chain EDI Pack examples

– EDIFACT Envelope example

– EDIFACT Deenvelope example

– X12 Envelope example

– X12 Deenvelope example

– C:\IBM\Standards Processing Engine 2.0.1\Supplychain_EDI_v8.5.1\examples

• Same Java program and script is used for both Packs

– Java source code included: .\examples\common\src\com\ibm\spe\sample

(49)

48

• Transform example – TX, SI and XSLT maps are called different ways:

– Dynamic Map (map read in as bytes)

– Map Server Location (file system location)

– SPE / TXA database repository (map in repository)

– C:\IBM\Standards Processing Engine 2.0.1\examples\translation

• Custom Translator example – Uses a custom mapping Java program

– C:\IBM\Standards Processing Engine 2.0.1\examples\custom_tx

• Java source code included for each example

– C:\IBM\Standards Processing Engine 2.0.1\examples\custom_tx\ACMEEngine.jar

– C:\IBM\Standards Processing Engine 2.0.1\examples\translation\src\com\ibm\spe\sample\transform

(50)

49

• Transform example – TX, SI and XSLT maps are called different ways:

– Dynamic Map (map read in as bytes)

– Map Server Location (file system location)

– SPE / TXA database repository (map in repository)

– C:\IBM\Standards Processing Engine 2.0.1\examples\translation

• Custom Translator example – Uses a custom mapping Java program

– C:\IBM\Standards Processing Engine 2.0.1\examples\custom_tx

• Java source code included for each example

– C:\IBM\Standards Processing Engine 2.0.1\examples\custom_tx\ACMEEngine.jar

– C:\IBM\Standards Processing Engine 2.0.1\examples\translation\src\com\ibm\spe\sample\transform

(51)

50

References

• Samples overview

–

http://www.ibm.com/support/knowledgecenter/SSDF7K_8.5.1/com.ibm.help.

spe_samp.doc/c_samplesOverview.html

• SPE Pack for Supply Chain EDI examples

–

http://www.ibm.com/support/knowledgecenter/SSDF7K_8.5.1/com.ibm.help.

spe_edi_pk.doc/topics/g_pack_sc_spe_pack_for_supply_chain_edi_exampl

es.html

• SPE Pack for Healthcare Payer examples

–

http://www.ibm.com/support/knowledgecenter/SSDF7K_8.5.1/com.ibm.help.

(52)

Benefits of IBM Transformation Extender Advanced

• Easy onboarding of Trading Partner

• Version Control

• Impact Analysis

• Available to run in different platforms

• EDI Validation and Acknowledge generation

• DeEnveloping and Enveloping simplified

• Ability to process ITX/WTX map and XSLT

• High performance throughput

(53)

Using IIB and ITX with IBM

Business Monitor

(54)

(55)

Transaction count Dashboard

Showing counts

with Bar Graph

Showing Total transaction counts

Pending ACK transactions counts

Showing Inbound and

Outbound counts

By Partner with table

(56)

(57)

(58)

(59)

(60)

(61)

(62)

(63)

(64)

(65)

IBM Transformation Extender

Advanced Updates

(66)

65

• Healthcare Pack

• HIPAA enhancements

• Type 7 support

• Easier administration for customized rules

• ICD-10 code lists used as default

• NCPDP

• WTX maps, trees included for use with Transform

• No enveloping/deenveloping support

• EDI Pack

• Updated Standards support

• X12 7020

• EDIFACT 14A, 14B

• TRADACOMS Support

• Enveloping/Deenveloping

• WTX TRADACOMS maps, trees included for use with Transform

(67)

66

• Bulking/Debulking support for:

• SWIFT (MT & MX)

• SEPA

• Generic ISO 20022

• For MX, SEPA, and ISO20022:

• Can envelope/deenvelope data with or without business header

• Supports transaction splitting for inbound data

• SPE Code lists used to validate BIC, IBAN, Country code, Currency code, etc.

• WTX NACHA maps and trees included for Transform only

• No NACHA enveloping/deenveloping support

(68)

REST API’s – ITX ADVANCED

67

• Allows you to invoke SPE functions as a Restful services

• Onboarding:

• Import/Export/Delete

• Read (Get) function to list existing resources

• Envelopes, Control numbers, Maps, Schemas, Code lists

• Run-time:

• Envelope

• Deenvelope

• Transform

• Monitoring/Reporting

• Overdue Ack Status

(69)

REST API’s – ITX ADVANCED

(70)

REST API’s – ITX ADVANCED

69

• IBM Design Language – new look and feel

• Pending/Overdue Ack reporting, management

• Download XML report

• View/Filter pending/overdue acks interactively

• Delete records that you want to remove from the report

• Updates for new standards and functions

• New envelope types for additional standards

(71)

70

ITX ADVANCED – Miscellaneous



Shared SPE install & DB for B2Bi, other host applications



Previously required separate install, DB for each



Multi tenancy support



User Data envelope parameters



Can add user-defined name/value pairs as envelope parms



SPE returns as Process Data for use in later user-specified steps

(72)

71



Generic envelopes for generated acknowledgements



No need to create outbound ack (997, 999, CONTRL) envelopes for each TP



Use wildcards, so can apply to all partners



Use correlation overrides from input headers to replace wildcard fields



Loaded into DB as part of pack deployment

(73)

Platform currency

• Updates to other applications that SPE integrates with

– WTX 9.0.0

– IIB 10

– B2Bi 5.2.6.1

• Java

– Java 8 included

– Requires at least Java 7 (IBM) to run

• Updated versions included:

– WAS Liberty

– 10x

– Derby

(74)

Where can I get more information?

IBM Integration developerWorks

https://developer.ibm.com/integration/

IBM Integration YouTube

https://www.youtube.com/user/IBMintegrationMedia

LinkedIn

https://uk.linkedin.com/topic/ibm-integration-bus

Twitter

(75)

Notices and Disclaimers

74

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS

DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and

interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

(76)

Notices and Disclaimers Con’t.

75

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,

PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.