Professional Documents
Culture Documents
Collaborate
Succeed
Network
WebSphere Transformation Extender ( formerly Datastage TX ) Integration with WAS, WPS and WESB
Shahryar Sedghi Senior Consulting IT Specialist ssedghi@us.ibm.com
2006 IBM Corporation Conference materials may not be reproduced in whole or in part without the prior written permission of IBM.
Objectives
Learn about WTX and How it solves Integration Problems Why we need to Integrate it with other WebSphere products Integration techniques Usage Patterns Best practices of Integration
WTX History
Formerly Mercator, 3-5% Market Share in the BI sector Unlike all the others, a major player on Z Apps (CICS, Batch) Acquired by Ascential to improve the ETL solutions Ascential was acquired by SWG DB2 Davison for Its ETL solutions WTX transferred to AIM to improve our WebSphere Integration story
3
Mapper
Converts from one tree or object to another XSLT is a standard mapper for XML Adapter Deals with different Source and Targets File , Database, MQ, JMS,.
Broker
Runs a flow of various activities, involve Adapters, Parsing, Mapping and Decision Making Brokers implement ESB (Enterprise Services Bus)
4
WTX Components
Parser for various Data Formats Tag Delimited Data (Industry standard, aka. X12, HL7, HIPPA), Already has many off the shelf formats Fixed Width (COBOL) XML (Basic and SOAP) Legacy Parsers implement lazy parsing Mapper Adapter File, Database, SAP, PeopleSoft,. Broker Event Server Tooling Windows Based (Not Eclipse)
5
Input Stream
WTX
WebSphere MQ
Pros
All adapter capabilities Better Performance for large Messages Cons MQ get and Put overhead Managing two environments
6
Pros
Map Designer
Create Maps between Input and Output Types
Testing, Debugging Optionally, Development Toolkit Java, RMI and JCA Adapter API
10
11
13
Map Designer
Submap
14
15
WPS/WESB + WTX ?
WPS/WESB natively support XML COBOL Copybook and C Header files( CICS and IMS adapter tooling) WTX is required for: Industry Standard Formats (aka. Tag Delimited Data) Content based routing for Non-XML data
16
Data Binding
SDO
POJO
SDO
17
SDO
Data Binding
Center
Java Component Bytes Stream Wrapped in SDO
SDO
POJO
18
JMS Import
JMSData Binding For WTX
Outbound
Inbound
WTX Medaition
SIBus
WTX Medaition
Input Queue
Incoming Data
Output Queue
Outgoing Data
Either JMS Data Binding for WTX or WTX Mediation Can be used not both together, on the same destination
WTX Mediation helps using WTX without modifying Existing Processes
and Mediations Non-JMS WMQ Applications can take advantage of the mediation
20
WTXJMSDataBinding - Outbound
WTXOutMap JMS Property
WPS Process
JMS
Export
Or WESB Mediation
JMS
Import
Legacy
SDO
XML Data
Map
Byte Stream
21
WTXJMSDataBinding - Inbound
WPS Process
WTXInMap JMS Property Legacy
JMS
Export
Or WESB Mediation
JMS
Import WTXInMap
JMS Property
Legacy
Byte Stream
Map
XML Data
SDO
22
Bus
WTXMedaition
Destination
Inspect Message
Byte Stream
Map
Byte Stream
Generate Message
23
WTXMedaition Code
SIMessageContext siCtx = (SIMessageContext)ctx; SIMessage message = siCtx.getSIMessage(); String messageFormat = (String)ctx.getProperty("Message Format"); String mapName = (String)ctx.getProperty("Map Name"); byte[] inBytes = message.getDataGraphAsBytes(); byte[] outBytes = new WTXMapRunner().runMap(mapName, inBytes); DataGraph newDataGraph = SIDataGraphFactory.getInstance().createDataGraph(outBytes, messageFormat); message.setDataGraph(newDataGraph, messageFormat); for(Iterator it = ctx.getPropertyNames();it.hasNext();) { String propName = (String) it.next(); message.setUserProperty(propName, (Serializable)ctx.getProperty(propName) ); // Optional }
24
SCA
Import
File
Byte Stream
Map
XML Data
SDO
25
SCA
Import
File
Extract Bytes
Bytes Stream
Map
XML Data
SDO
26
Or WESB Mediation
File
SDO
XML Data
Map
Byte Stream
27
File
SDO
28
Usage Patterns
ESB
Legacy to Web Service Data Integration Content Based Routing Process Integration Legacy to Business Processes
29
Mediation Module
JMS Export 6
In
Mediation
3
XSLT Out
5
Out XSLT In
WS Import
Internet
30
JMS Client
1 5
WPS Module
4 2 6 JMS Export
JMSInInterface
Interface Mediation
3
Data Map
JMSOutInterface
JMS Import
31
Component
Generic Interface
WTXJMSDatabinding
JMS Export
Router Component
Component
Event Agnostic
Event Aware
32
Generic Interface
33
BPEL
HTM
34
Deployment Prerequisites
Environment WPS/WESB interact with WTX Java API Java API invokes Shared Libraries through JNI layer WTX Jar (dstxpi.jar) must be in the classpath Shared Libraries (aka. DLLs) must be in the system PATH (Path for WAS user profile in UNIX/Linux) Complied Maps must be accessible to the code Compiled map needs XSDs for validation if: XML is inbound to the map Xerces parser is used (8.0 and above)
35
36
37
39
Links
Lab Docs (3MB):
ftp://pokgsa.ibm.com/pokgsah1/01/ssedghi/web/public/WTX/LabDocuments.zip
Solutions Folder without Workspaces (228 KB):
ftp://pokgsa.ibm.com/pokgsah1/01/ssedghi/web/public/WTX/Solutions_without_workspace.zip
Solutions Folder with workspaces (30 MB)
ftp://pokgsa.ibm.com/pokgsa-h1/01/ssedghi/web/public/WTX/Solutions.zip
VMWare (5.2 GB) ftp://pokgsa.ibm.com/pokgsa-h1/01/ssedghi/web/public/WTX/base_vm.zip
40
Questions
41