Introduction To WTX

IBM FSS
WebSphere Transformation Extender

WebSpheres Universal Transformation Engine for the Enterprise
Kimberly Drouot
WebSphere Transformation Extender Technical Lead SW IOT
kimberly.drouot@fr.ibm.com
2006 IBM Corporation
IBM Software Group | WebSphere software
What Does IBM WebSphere TX Do?

It takes any kinds of data from their native forms
ANY Data
Processes them together, natively, with NO CODE
Many-to-many Integration
And outputs them into their native target formats
ANY Data
Ex. - Hierarchical Data , Binary Data, Packed Data, Tabular Data, Relational Data, Nested Structures, Mixed-Type Data, and on and on
Transformation Vision - Simplified
Transform Anything
Transform Anywhere
Everyone Transforms
The Need for Transformation

Transformation is the hard, ugly part of integration
-Ted Friedman, Research VP, Gartner
"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
Two of the biggest and most significant challenges of dealing with data are
transformation and semantics.
Zapthink
There are many integration styles and challenges, each with their own unique
demands; what is consistent across every one of them is the need for data
transformation and mediation.
IBM
The Challenge and Transformation

About 35 percent of an enterprises software budget is
spent on maintaining the multitude of point-to-point
application links already in place.
Gartner Group
Resources
and IT Assets
(insurance company)
Legacy
Claims
Database
Auto
Claims
System
Home
Claims
System
Life
Insurance
Claims
Business
Partner
Claims
System
1.
Each system has its own data definitions, business rules and interfaces
2.
Providing granularity to applications business functions requires ability to maintain

contextual usage and data meaning across systems
3.
Interactions between applications expose data and business rule anomalies which
result in high maintenance costs and inflexibility to change
4.
The Validation and Use Rules must align with the Transformation needs and execute in
the same unit of work with Transformation
5.
Ever increasing integration logic points with duplicate or slightly modified templates
rob from anticipated benefits and efficiencies
Real World Transformation Demands

Demand a Broad Range of Capabilities
Hard/Complex
Processing
Interdependent
Data
Almost all projects that require these today, do

so via programming, even if they are using
middleware as the platform (ie Java, C++, etc)
Only WTX can provide all of these

AND DOES SO WITHOUT CODING ! .
Many
to
Many
Many
to
Any
Any to Any
Any
To
Many
Easy/Simple
What is the problem of Transformation

Processing Information with all the business rules and usage mechanisms in tact
BINARY
00011110010010011010010
10010010010010010000011
11010100101010110010010
10010010010010001010010
10010010101010101000100
11100010100010010001001
00100100100100101010010
01010100100010010010010
01001001110001010010101
01010101010010010101001
00100010010100101000010
10101010001001010001001
01001010100101010100101
01100101000000000001111
10010010010101110010010
01010101001010101101111
TABLE
COPYBOOK
Make
Model
PKG
Extended_Feature
s
Ford
Prefect
34890
2984782q,
93847920,
3438084
01
03
05
TP-API-CB.
TP-AGAPI-CB.
TP-AGAPI-REQUEST
PIC X(40).
TP-AGAPI-INITIALIZE-REQUEST
VALUE 'INITIALIZE-MAPPING'.
TP-AGAPI-PERFORM-MAPPING
VALUE 'PERFORM-MAPPING'.
88
TP-AGAPI-FINISH-MAPPING
VALUE 'FINISH-MAPPING'.
05
TP-AGAPI-VERSION
PIC X(04).
88
TP-AGAPI-VERSION-VALID
VALUES ARE '0100' '0200'.
88
TP-AGAPI-VERSION-0100
VALUE
'0100'.
88
VALUE
'0200'.
05
TP-AGAPI-RESPONSE.
10
TP-AGAPI-RESPONSE-CODE
PIC 9(04) COMP.
88 TP-AGAPI-ALL-OKAY
VALUE 0.
88 TP-AGAPI-REQUEST-ERROR
VALUE 1.
88 TP-AGAPI-INITIALIZE-ERROR
VALUE 2.
88 TP-AGAPI-MAP-ERROR
VALUE 3.
88 TP-AGAPI-FINISH-ERROR
VALUE 4.
88 TP-AGAPI-UNKNOWN-LOOP-ID
VALUE 5.
88 TP-AGAPI-NO-ALGORITHM
VALUE 6.
88 TP-AGAPI-NO-PARTNER
VALUES 7 15.
88 TP-AGAPI-NO-APPLICATION
VALUE 8.
88 TP-AGAPI-ALGORITHM-IO-ERROR VALUE 9.
88 TP-AGAPI-FATAL-GATEWAY-ERROR VALUE 10.
88 TP-AGAPI-GATEWAY-WRITE-ERROR VALUE 11.
88 TP-AGAPI-PARTNER-IO-ERROR
VALUE 12.
88 TP-AGAPI-BAD-VERSION
VALUE 13.
88 TP-AGAPI-BAD-NUMERIC-TYPE
VALUE 14.
88 TP-AGAPI-NO-ALIAS
VALUE 15.
88 TP-AGAPI-ACCESS-ERROR
VALUE 16.
10
TP-AGAPI-RESPONSE-MESSAGE
PIC X(80).
05
TP-AGAPI-APPLICATION-ID
PIC X(10).
88
Ford
Prefect
34890
2984782q,
93847920,
3438084
Ford
Prefect
34890
2984782q,
93847920,
3438084
Ford
Prefect
34890
2984782q,
93847920,
3438084
Ford
Prefect
34890
2984782q,
93847920,
3438084
Ford
Prefect
34890
2984782q,
93847920,
3438084
CASH RECONCILATION
27 files
88
10029847 - $100,000,000.00
13948589 - $679,495,094.98
13950967 - $588,345,058.00
13950968 - $000,000,000.00
14001321 - $098,957,038.12
AAA: HT4459
AAA: B33566
AAA: C4058G
AAB: 948409
AAB: 874931
03
01
DDA Application Updates

STREAM
PROPRIETARY
OH,257*IN,142*MI,1
54*WI,80*MT,5*ID,8
*WY,3*CO,21*NM,8
*AZ,15*UT,13*NV,4*
MN,48*MO,67*ND,9
*SD,9*KS,27
DUNS 0123
F046000INV
for 2
months 120799
12 718-339-1700I43989D-2
120799999-b
003000010000
DUNS 4445
P55590
120799499QR
000004004000
EBCDIC
<MSG 19934749>
<ACCT BAL RPT>
@
z@
@@
@
<ACCTNUM><14001321>
<ENDBALANCE>< $098,957,038.12>
<DEBIT><103048382$394,394.00>
<DEBIT><103048383$001,293.65>
<CREDIT><987463921$928,943.67>
</ACCTNUM>
</MSG>
413 msgs
What Makes WebSphere TX so Different?

Code-Free Design and Deployment
In-Process Data Validation
High Throughput Execution of Complex
Transformations and Enhancements
One Engine, Multiple Deployment Options
Examples of Complex Transformation Challenges Addressed

by WebSphere TX
Data Enhancement
Lookups
Data Logic and Routing
Data Validation
Context Based Data and Usage Rules
Many to Many Transformation

Single-Transaction, interdependent data sets, conversions and logic
Mixed Data and Source/Target Types
Dependent Result Sets, Nested Structure Dependencies
Complex Data Transformation

Nested, Semi-structured And Hierachical Data Types
Dependent Inputs And Outputs
Binary, Packed, EBCDIC, ASCII, Mixed Character Data
One Engine, Multiple Deployment Options

WebSphere TX is the one transformation engine that can be reused
across all applications and infrastructures in the enterprise
Deploy the same WebSphere transformation asset across:
ESB
Unix
30+ Adapters
WebSphere Message Broker
SOA
Linux
ETL
WebSphere ESB
Web Services Windows Data quality
WebSphere Process Server
SOAP
Enterprise
Applications
WebSphere Partner Gateway
Application
Servers
WebSphere DataStage
z/OS
EJB
Batch
HTTP
CICS
Event driven
IMS
Batch
USS
WebSphere Application Server
Java
C/C++
COBOL
WebSphere TX is further enhanced by Vertical Product

Packs
Financial Services
Health Care
SWIFTNet
SWIFTNet Funds
SEPA*
Many Services Based Solutions
FIX
FedWire, CHIPs
NACHA
BAI, BAI2
AL3
ACORD
Etc.
HIPAA
NCPDP
HL7
HealthCare Hub
Payment Processing
Clearing House Processing
CPG, Manufacturing
Embedded Software
ERP/CRM Integration
EDI (ANSI X12)
TRADACOMS
ODETTE
EDIFACT
Integration to the Enterprise as

an embedded service
Telecom
Enterprise Apps
Shop Floor Systems, etc
WebSphere TX
A Long And Storied Road
V8.1
V8.0
V7.5
Proven
V6.7
Q3 2006
V6.5
July 2005
V6.0
Reliable
June 2004
V5.0
Jan 2003
V2.1
Jan 2002
V1.4
Sept 2001
V1.3
V1.2
Innovative
June 2000
V1.1
Dec 1999
V1.0
Aug 1997
June 1996
Nov 1995
June 1995
Jan 1994
Mature
Global Financial Institutions rely on

Fortune 1000 Coverage

Significant Impact on Capital

Markets:

9 of Top 10 Commercial Banks

6 of Top 15 Diversified Financials
4 of Top 12 Life and Health Insurance
Companies
8 of Top 14 Property and Casualty
Insurance
$3 Trillion of transactions flow through

WebSphere TX daily
40% of London securities transactions are
powered by WebSphere TX
WebSphere TX for STP:

100 international banks

70 investment managers
40 broker dealers
10 global custodians
Major Stock Exchanges
European Clearing Houses
WebSphere TX is widely used in all industries

FINANCIAL SERVICES
MANUFACTURING,
RETAIL & DISTRIBUTION
HEALTHCARE /
INSURANCE
WebSphere TX: Universal Transformation & Reuse

Transform, validate, and enrich any document, message or complex data
Deliver trustworthy information for critical business initiatives

Meet regulatory compliance requirements
Codeless development; universal reuse and deployment
J2EE
Standalone
System z (native)
Windows, UNIX, Linux
Embedded
Standalone
Event driven
App. Server
Process Server
Multi-In
Advanced ESB
ESB
Make Advanced ESB

More Advanced
MAP
TRANSFORM
Multi-Out
WebSphere TX: A Unified Transformation

Environment across the WebSphere portfolio
ONE Transformation
Engine for the
Enterprise!
Powerful transform
capabilities without
coding
Natively handles any
data type
Solves really hard
transformation
problems
Complements
existing portfolio of
products
Delivers new sales
opportunities
For batch
environments
WebSphere
WebSphere
TX
TX
MAP
TRANSFORM
Unifying
Unifying
Enterprise
Enterprise Data
Data
Transformation
Transformation
(as a standalone engine)
For WebSphere
Message Broker
For WebSphere
Process Server
For WebSphere
ESB
For WebSphere
Partner Gateway
For 3rd Party
Integration Products
(as an embeddable engine)
IBM Software Group
Developing a WebSphere TX Solution
The Components of a WebSphere TX Solution

A WebSphere TX solution is composed of the following:
Adapter
Source
Type Tree
Rules
Mapping
Type Tree
Adapter
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 a WebSphere TX Map
The Components of a WebSphere TX Solution

Howevermany to many mapping is also possible:
Adapter
Type Tree
Adapter
Type Tree
Adapter
Type Tree
Sources
Type Tree
Adapter
Type Tree
Adapter
Rules
Mapping
A Map can perform many tasks :

Validation
Enrichment,
Content Based Routing
etc. SOURCE FILE
Destinations
DATABASE UPDATE
TRANSFORMED MESSAGE
ON OUTPUT
CROSS-REFERENCE
TABLE
Orchestrating Transformations
10
Developing a WebSphere TX Solution

We usually talk about three simple steps:
Describe the data...
Data that is handled by IBM WebSphere TX, are described in "Type Trees
that define the data structure and semantics.
Transform the data...
Data is mapped between the source and destination using drag-and-drop.
Deploy the and execute the transformation
Multiple deployment models
Batch
Event Driven
Tightly-coupled (through APIs)
Loosely-coupled (RMI)
WebSphere TX Design Environment

Describe the Data
Properties
Structure
Validation Rules
Type Designer
Database Interface
Designer
Define Transformation Rules

Interfaces
Structure
Formats
Semantics
Resources
Communication
Adapters
Deploy and Manage

Flows
Events
Monitoring
Map Designer
Message Launcher
Broker
Batch / JCL
IMS
CICS
11
Describe the Data...

IBM WebSphere TX Type Trees
The Type Trees defines the structure of the data to be handled in IBM WebSphere TX.
This XML structure is then represented as an IBM WebSphere TX Type Tree.
WebSphere TX Design Environment

Describe the Data
Properties
Structure
Validation Rules
Type Designer
Database Interface
Designer
Define Transformation Rules

Interfaces
Structure
Formats
Semantics
Resources
Communication
Adapters
Deploy and Manage

Flows
Events
Monitoring
Map Designer
Message Launcher
Broker
Batch / JCL
IMS
CICS
12
Map Designer
Create maps to:
Validate data from data sources
Identify data targets
Specify data transformation logic (rules)
Identifying Data
Sources and Targets
Identify
Identify type
type tree
tree and
and type
type
tree
tree components
components that
that define
define
data
data target
target
Identify
Identify type
type of
of data
data and
and
location
location of
of data
data
13
WebSphere TX Adapters
Communication
CICS *
COM
CORBA
E-MAIL *
FTP/FTPS *
HTTP/HTTPS
JAVA Class
JCA Gateway
SOAP
SOCKET
VAN
Messaging
BEA MessageQ & Tuxedo
Candle Roma
IBM WebSphere MQ *
(MQSeries)
JMS
Microsoft MSMQ
Oracle AQ
TIBCO Rendezvous
Applications
Siebel
- BIM, EIM, OI COM
SAP R/3 & BW
- ALE, BDC, DMI, DXOB
- BW, EDI, BAPI
PeopleSoft
- Message Agent API,
- Open Query, EDI
QualityStage
WebSphere
TX
Design Studio
Utility
Archive (ZIP/TAR)
Base 64
Batch
File *
GZIP/ZLIB
JNDI
LDAP
MIME
Quoted-Printable
Shell Script
Sink *
SNMP
XML *
Database
DB2 *
Informix
ODBC *
OLE-DB
Oracle *
Microsoft SQL Server
Sybase
HP NonStop SQL/MX &
SQL/MP
Security
S/MIME
OpenPGP
SSL Module
* Adapters supported on z/OS, varies by execution method
Step 1 Define the data structures

Pre-defined Importers for automatic generation
Pre-defined libraries (Packs)
XML Schema, DTDs
EDIFACT
COBOL Copybooks
SWIFT
Database (Tables, Vues, Procdures Stockes)
SEPA*
3rd Party Applications
ACORD
SAP: BAPI, Idoc, DXOB, BDC
HIPAA
PeopleSoft 7: Business Document, Message

Agent
HL7
PeopleSoft 8: Application Messaging,

Component Interface
Siebel: COM Business Object, EAI, EIM
WSDL (Web Services)
EJB API
Java Class
Java Messaging Service
* En cours
Others: Tuxedo, Flat File, PL1,
14
Built-in Validation (Restrictions)

Items have
extensive validation
options
Enumerations
Exclusions
(with substitution)
Patterns
Ranges
Additional Built-in Validation

Component Rules allow cross-field validation
Incorporates semantic validation directly into the parsing process
15
Additional Built-in Validation

Component Rules support aggregate functions
Use component rules to specify conditions (business rules) that must
be met for a particular component to be valid
Step 2 - Creating transformation rules
Pre-defined
Mapping
Functions
Drag and Drop
No Procedural Coding!!
Easily represent complex business rules
16
Calling external functions and programs
Rejecting Errors
17
Step 3 Deploy and execute the transformation map

Option Build creates a
compiled map
For the execution server
Automatically accounts for
byte-order and code page
differences
Example Developing a WebSphere TX Map

Multiple Execution Methods
1. Define the Data Structures
Serveur WTX
(moteur)
2. Define the transformation rules

3. Deploy and execute
WTX Adapters
Z/OS
API
Batch / JCL
Event-Driven / ESB
WebSphere ESB
WebSphere Process Server
WebSphere Partner Gateway
WebSphere Application Server
WebSphere DataStage, etc.
Deploy
XML Schema
000520****************************************************************
000530 01
TP-API-CB.
000540 03
TP-AGAPI-CB.
000550
000560 05
TP-AGAPI-REQUEST
PIC X(40).
000570
88 TP-AGAPI-INITIALIZE-REQUEST
000580
VALUE 'INITIALIZE-MAPPING'.
000590
88 TP-AGAPI-PERFORM-MAPPING
000600
VALUE 'PERFORM-MAPPING'.
000610
88 TP-AGAPI-FINISH-MAPPING
000620
VALUE 'FINISH-MAPPING'.
000640
000650
000660
000670
000680
05
88
88
88
Importer
Map
Importer
TP-AGAPI-VERSION
PIC X(04).
TP-AGAPI-VERSION-VALID
VALUES ARE '0100'
'0200'.
VALUE '0100'.
VALUE '0200'.
COBOL
Copybook
Design Studio
Windows
18
WebSphere TX General Architecture

Design Studio
Type
Designer
Map
Integration Flow
Designer
Designer Importaters
Unit Test Engine

Database
Interface
Designer
WebSphere TX Server
WTX Core Engine

WTX Adapters
WTX Compiled Maps (.mmc)
Server A
IBM Software Group
WTX for z/OS
19
WTX for z
Transformation and execution on z/OS
Product Offering
Execution Method

with Command Server
Batch / JCL
CICS
IMS TM
IMS/DC

with Launcher USS Edition
Event-driven,
multi-threaded,
multi-process transformation
engine

(embedded edition)
APIs & Interfaces for: Cobol,

Java, C, EJB
For use with WAS, WPS,
Cobol programs, etc.
WebSphere Transformation Extender for

Message Broker USS Edition
WTX Parser
WTX Map Node
WTX for Z/OS - Batch

Pure Batch execution mode invoked through JCL
// SET WTXLIB=L333703.WTX.REL8.XPL.LOAD <= WTX LOAD LIB
//DSTX EXEC PGM=DSTX,REGION=0M,
//
PARM='SEPA2APP /IF1 INPTSEPA'
//STEPLIB DD DISP=SHR,DSN=&WTXLIB
SMP/E installation
Supports the following sources/targets natively
Files (QSAM, VSAM)
DB2
FTP
MQ
EXIT function allows existing COBOL and C programs to be called from a

WTX Map
20
WTX for Z/OS Batch - continued

Administration through standard z tools (ISPF, etc.)
No need to learn a new monitoring tool
No permanent active processes

WTX is only active when called by the JCL
When map transformation ends
WTX is no longer active
Integrates seamlessly into existing

production procedures
Does not require changes to customer
job and system administration processes
WTX for Z/OS - CICS
Z/OS
Transactional execution mode through a CICS transaction

Runs natively in CICS inline and batch modes supported
SMP/E installation
Supports the following sources/targets natively
VSAM Files
key-sequenced
entry-sequenced
relative-record data sets
d
CICS tee n
n tio
a
r c
ua a
G ans
Tr
CICS
Appli
WTX
CICS
WTX Map
DB2
MQ
Transient data queues
Temporary storage queues
Storage buffers (COMMAREA)
EXIT function allows existing COBOL and C programs to be

called from a WTX Map
21
WTX for Z/OS CICS - continued

WTX z/OS CICS can be invoked:
From a clear terminal by using the DSTX transaction
i.e. DSTX MYMAP IF1 INPUTF
From a user program by starting the DSTX transaction in the EXEC

CICS START command
From a trigger transient data queue by initiating the DSTX transaction
By calling the DSTXCICS program through an EXEC CICS LINK
Administration through standard z tools (CEBR, etc.)

Integrates seamlessly into existing production procedures
WTX for Z/OS IMS TM & IMS/DC

Allows WTX Maps to be programmatically executed through IMS
Z/OS
Relies on WTX Platform APIs and high-level language programs

C/C++ and COBOL programs can invoke WTX through the IMS
execution option
IMS
WTX Maps participate in the IMS transaction

Cobol/C
Application
EXIT function allows existing COBOL and C programs to be called

from a WTX Map
WTX
22
IBM Software Group
WTX for WebSphere Message Broker
WebSphere Transformation Extender for WMB USS Edition

WebSphere TX is an additional Node on the Message Broker design palette
XSLT
transformation
Compute
ESQL
Compute
Java
transformation
transformation
Mapping
transformation
WebSphere
TX
Universal
Transformation
Industry
Packs
(SWIFT, EDI,
HIPAA)
optional
The most powerful

Any-to-Any
Broker on the Market
Embed WebSphere TX transformations within Message Broker Message Flows

Interoperates with Message Broker V5.x or 6.0
Fully compatible with Message Broker transaction control
Takes full advantage of Message Broker scalability
Full support for multiple sources and multiple targets within a single transaction
scope
Installs in minutes
23
WTX for WebSphere Message Broker Components

Parser
Transforms bit streams to Message Trees (MQInput)
and Message Trees to bit streams (MQOutput)
Transforms Message Trees to Message Trees (RCD)
Plug-in node
Transforms anything to anything
Icon installs into Message Flow palette
Easy configuration
WTX for WebSphere Message Broker Plug-In Node

The Plugin node can be used in message flow like any
other node
Any to Any Transformations

EDI Transformations
SWIFT Transformations
24
Chief Value Differentiators of WebSphere TX to

alternative transformation methods
Powerful Transform capabilities with No Coding
Lowers cost to implement, maintain and re-use
High-Throughput, Complex Transformations
Cost per transaction very low
Natively Handles Any Data Type

Never resort to flattening or re-structuring data
Data integrity and meaning are never lost
In Process Data Validation

Greatly reduces development efforts and implementation costs
Solve Really Hard problems, in less time, with one

common design method
Grazie
Italian
Thai
Traditional Chinese
Obrigado
Russian
Merci
Brazilian Portuguese
French
Gracias
Arabic
Spanish
Danke
German
Simplified Chinese
Japanese
25

Introduction To WTX

Uploaded by

Document Information

Original Title

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

Introduction To WTX

Uploaded by

Copyright:

Available Formats

IBM FSS

WebSphere Transformation Extender

2006 IBM Corporation

IBM Software Group | WebSphere software

What Does IBM WebSphere TX Do?

Processes them together, natively, with NO CODE

And outputs them into their native target formats

IBM Software Group | WebSphere software

Transformation Vision - Simplified

IBM Software Group | WebSphere software

The Need for Transformation

"Organizations pursuing service-oriented integration involving document-oriented,

IBM Software Group | WebSphere software

The Challenge and Transformation

Providing granularity to applications business functions requires ability to maintain

IBM Software Group | WebSphere software

Real World Transformation Demands

Almost all projects that require these today, do

Only WTX can provide all of these

IBM Software Group | WebSphere software

What is the problem of Transformation

DDA Application Updates

IBM Software Group | WebSphere software

What Makes WebSphere TX so Different?

IBM Software Group | WebSphere software

Examples of Complex Transformation Challenges Addressed

Many to Many Transformation

Complex Data Transformation

IBM Software Group | WebSphere software

One Engine, Multiple Deployment Options

WebSphere Message Broker

Web Services Windows Data quality

WebSphere Process Server

WebSphere Partner Gateway

WebSphere Application Server

IBM Software Group | WebSphere software

WebSphere TX is further enhanced by Vertical Product

Integration to the Enterprise as

IBM Software Group | WebSphere software

IBM Software Group | WebSphere software

Global Financial Institutions rely on

Fortune 1000 Coverage

Significant Impact on Capital

9 of Top 10 Commercial Banks

$3 Trillion of transactions flow through

WebSphere TX for STP:

100 international banks

IBM Software Group | WebSphere software

WebSphere TX is widely used in all industries

IBM Software Group | WebSphere software

WebSphere TX: Universal Transformation & Reuse

Deliver trustworthy information for critical business initiatives

Make Advanced ESB

IBM Software Group | WebSphere software

WebSphere TX: A Unified Transformation

(as a standalone engine)

IBM Software Group

Developing a WebSphere TX Solution

2004 IBM Corporation

IBM Software Group | WebSphere software

The Components of a WebSphere TX Solution

IBM Software Group | WebSphere software

The Components of a WebSphere TX Solution