1. WebSphere Transformation Extender 8.4.1
Sunil Dandamudi| Architect WebSphere TX
© IBM Corporation 2011

2. Agenda What’s new in 8.4.1 ? Productivity X* Technologies Connectivity
Reliability
Security
Expansion
Interoperability
What’s Gone

3. Productivity

4. Productivity : Auto Mapping
Reduction of repetitive mapping
Scope definition
Intelligent & interactive rule generation
Matching options & criteria

5. Design Studio : Auto Mapping
Defines mapping scope
Map only immediate items
Map only immediate items & groups
Map all descendants
Matching Criteria & Options
Case Sensitivity
Alpha-numeric
Rule creation based on matching %

6. Design Studio : Auto Mapping
Intelligent & Interactive rule generation
Allows to override existing rules
Generates functional maps & mappings
Provides suggestions to existing rules

7. Design Studio : Reports
Reports are generated from Type Trees files in HTML format. These reports includes
Information in the type tree includes type properties, components & restrictions

8. Design Studio : Reports
Reports are generated from Map Source files in HTML format. These reports includes
Information in the map source includes map properties, rules, card properties, remarks, & audits

9. Tasks Reports for Maps and Type Trees
Generate Reports for Type trees in combinations
All
Each and individual option
Combination of options
Generate Reports for maps in combinations

10. Design Studio : Java API
Java programs now can call the WTX design time java API
The design time java will allow customers :
Create , modify and analyze type trees
Modify type properties in a type trees
Create, modify components and restrictions in a type tree
Develop component rules
Create and modify maps
Build maps for each platform
Develop map rules for transformations
Develop Remarks, Audits for maps
Multiple examples shipped to demonstrate development of various features using JAVA API
Java Documentation shipped as part of the Design Studio

11. Design Studio : Java API
Java Archives (JARS) are available under tools directory
dtxxds.jar & wtxui.jar – CLASS PATH
WTX install directory – PATH
Examples are available under examples/dsgnstud/dtxds
Package naming conventions
com.ibm.websphere.dtx.ds.map.*
com.ibm.websphere.dtx.ds.typetree.*

12. Cobol Copy Book Importer
Cobol Copy Book Importer allows to create type trees from Copy books.
Existing Copy Book importer is too restrictive
New importer delivered by IBM Rational team and is used across other IBM products
Allows to generate type trees from a single or multiple copybooks.

13. Cobol Copy Book Importer
Supports
Double byte character sets
Using national clauses
Sync
Restrictions

14. Cobol Copy Book Importer
Copybooks are complied using windows compiler as part of Import process.

15. Cobol Copy Book Importer
A Detail error analysis is provided as part of the import process

16. Design Studio : JSON Importer
JSON (JavaScript Object Notation ) is a lightweight data-interchange format.
JSON importer allows creating type trees from JSON documents
The generated type tree from the importer allows to parse JSON files

17. Core Engine : Substitute Character
Allows to override default substitute character during ICU conversion from Data language to another
The substitute character can be overridden in Systems and WTX Run time API

18. Core Engine : Excess Trailing
Introduction of 'excess' trailing spaces property in Type Designer to capture spaces in the data to the right of the data element which are not necessary to satisfy minimum size requirements.
The property is available as part for type Padding when PAD is set to Fixed Size
When Property is enables, the engine would report an error if the data content was longer than the fixed padding size specified and the last justified character was the pad character

19. Core Engine : Functional Map
Functional maps will return data as other WTX functions do for Items
For item, If the invoking rule does something with the functional map output (which didn't work in prior releases), the result of the functional map is simply written to the output of the invoking map
If a functional map returns a group, there will be no change to the behavior of the functional map.

20. X* Technologies

21. Design Studio : GDM
IBM Graphical Data Mapper (GDM) allows to map XML to XML transformations.
Supports building and testing transformations in XSLT Engine
GDM is integrated with WTX Design Studio
Allow users to build XML to XML Transformations within the Studio

22. Design Studio : GDM
GDM is invoked through File  New  XML  Data Map

23. XML : Native XML Customizations
Introducing support for
mixed content
xsi:type extensions
Global elements
MTX generated with a unique identifier based on customizations (schema_identifier.mtx)
Use context menu to reset customizations

24. XML : Mixed Content
Introducing support for mixed content in Native XML solution
Mixed content allows character data between child elements in xml document
Native XML solution now allows to parse or generate mixed content data
Support for Mixed content is available through UI selection while building the card
Mixed content is disabled by default

25. XML : xsi:type
Extending support for xsi:type for schema extensions in Native XML solution
Allows the Native XML solution to process type definitions that are defined at run time in a XML document
Enhancing the xsi:type support to store all user selections as part of map source files for enhanced user experience
<intladdress>  <address>
schema document can define a concrete element address, but the instance document can change the definition to intladdress using xsi:type
extends

26. XML : Build As Root
Allows users to select Global Elements during the type tree generation process.
Build As Root feature is supported both for Xerces Type Tree and Native XML solution
Allows to create smaller type trees and enhanced user experience while dealing with bigger schemas
User provided with an options to select the Global elements during the type tree generation process
User selections stored in Map source (.mms) for Native XML solution for enhanced user experience

27. XSLT Function
XSLT (Extensible Style sheet Language Transformations ) function for transforming XML documents into other XML documents
Supports FILE , HTTP and BLOB formats for
Inputs
XSLT files
Examples
VALID(XSLT(Input, xpath_file), LASTERRORMSG())
VALID(XSLT(file:///ipo.xml, xpath_file), LASTERRORMSG())
VALID(XSLT( xpath_file), LASTERRORMSG())
VALID(XSLT(input, current:///convert.xml), LASTERRORMSG())

28. XPATH
XPATH (XML Path Language ) is a query language for selecting nodes from an XML document.
Supports FILE , HTTP and BLOB formats for Inputs.
Supports Namespaces.
Examples
VALID(XPATH(Input, LASTERRORMSG())
VALID(XPATH(file:///ipo.xml, LASTERRORMSG())
VALID(XPATH(“ LASTERRORMSG())
VALID(XPATH(input, “ipo& LASTERRORMSG())

29. XVALIDATE
XVALIDATE function validates XML input, given as a text stream or uniform resource locator (URL), against the provided XML Schema
Validation Errors retrieved from LastErrorMessage / LastErrorCode function
Supports FILE , HTTP and BLOB formats for
XML Documents
Schema Documents
Examples
VALID(XVALIDATE(Input, schema_file), LASTERRORMSG())
VALID(XVALIDATE(file:///ipo.xml, file://ipo.xsd), LASTERRORMSG())

30. Connectivity

31. Connect Direct Adapter
C:D (Connect Direct) is the point-to-point file transfer software optimized for high-volume, secure, assured delivery of files within and among enterprises.
Introducing WTX C:D Adapter to interact with C:D for accessing files during inbound or sending files to C:D at output bound
Allows a WTX map to initiate a file transfer during map executions
Allows WTX launcher to process map transformations when a C:D event occurs.

32. Connect Direct Adapter
Windows
32 bit only
Uses C:D C SDK interface
Unix / Linux
32 bit Linux (x86)
64 bit AIX, Linux (x64), HP Itanium, Solaris (SPARC), Linux on Z (no Linux on Power)
Uses C:D C API interface
z/OS
Support for BATCH, USS
Uses C:D interface
IBM Confidential 32

33. Connect Direct Adapter
Adapter options
IBM Confidential 33

34. Connect Direct Adapter
Directory Restrictions in C:D
Property in C:D - if used, requires the –DIRRESTRICT (-DR) option on the adapter command line
Configured in C:D Select (windows) or userfile.cfg (Unix / Linux)
For input cards and GET: -DR <download_location>
For output cards and PUT: -DR <upload_location>
Valid when C:D Directory Restriction property is set
IBM Confidential 34

35. Connect Direct Adapter
Configuration notes (C:D):
C:D netmap must be configured for primary (PNODE) and secondary (SNODE) nodes.
Users must be configured for primary and secondary nodes.
If you can’t transfer a file between two C:D nodes outside of WTX with specific credentials / parameters, it won’t work running under WTX with the C:D adapter with the same credentials / parameters.
Linux / Unix requires setting NDMAPICFG environment variable:
export NDMAPICFG=/opt/cdunix/ndm/cfg/cliapi/ndmapi.cfg
Running Windows launcher requires launcher service to be run as PNODE user – not Local System account.
Linux / Unix login credentials are used for C:D on those platforms – cannot use PPASS or SPASS
IBM Confidential 35

36. Connect Direct Adapter
Command line examples
Writing a file from Aix to Linux
-PNODE aix71a -SNODE rhel564 -F /opt/cdunix/download/myfile.txt -P aixTest -ckpt 1k –te
Reading a file from the same Linux node
-PN rhel564 -SN rhel564 -F /opt/cdunix/upload/country.txt -P card1 - CKPT 1K –T
IBM Confidential 36

37. Connect Direct Adapter
Command line examples -- used for Demo
Writing a file from a Windows node to another Windows node - PNODE has upload directory restriction
-WI 5 -SN lewsx -PUSER lewiss -PP ******** -PNODE vwtxw8ke64l -SU lewiss -SPASS ******** -dr c:\temp\up -F c:\connectDirect\map\trigger\vm1.txt -P vwtxWrite -CKPT 1K –T
Writing a file on the same Windows node
-WI 5 -PN lewsx -PUSER lewiss -PP ******** -SN lewsx -SU lewiss - SPASS ******** -F c:\connectDirect\map\trigger\test1.txt -P LewsxWrite -CKPT 1K -TE c:\cd.log
Using it as a Launcher source event on a Windows node, triggering from the above two command lines
-PUSER lewiss -SNODE lewsx -PP ******** -SU lewiss -SPASS ******** -F C:\connectDirect\map\trigger\*.txt -P cdLauncher -T c:\m4cd.log
IBM Confidential 37

38. Adapters : HL7/MLLP Adapter
MLLP (Minimal Lower Layer Protocol ) is a protocol used to transport large portion of HL7 documents through TCP/IP
Introducing WTX MLLP Adapter to process HL7 documents
The Adapter strips the leading byte and trailing 2 bytes on a inbound document
The Adapters adds the leading byte and trailing bytes to the HL7 document at the outbound
The adapter also validates the presence of a configurable delimiter and fails if not present or incorrect

39. Adapters : JAXB Adapter
Java Architecture for XML Binding (JAXB) allows to map Java classes to XML representations.
Introducing JAXB Adapter to process java objects
The adapter can be used with any XML based solution , WTX supports (classic, Xerces or Native Schema)
The adapter supports URL format for serializing and de- serializing java objects.

40. Adapters : JAXB Adapter

41. Adapters : JAXB Adapter

42. Adapters : JAXB Adapter
CLASS (-C) Use the Class adapter command (-DS) to provide the JAXB adapter the class that represents the XML object.
URL (-U) Use the URL adapter command (-S) to serialize or deserilaize the input object. This is either a file or http location. For files relative to input directory, there is no need to provide the full URL notation.
OBJECT ID (-ID) Use the Class adapter command (-DS) to provide the JAXB adapter the class that represents the XML object
JAXB.XXX properties are specific to JAXB marshaller and un-marshaller. Refer to JAXB documentation for more details on these properties.

43. Adapters : JAXB Adapter
PUT : VALID(PUT("JAXB", "-C com.ibm.websphere.dtx.m4jaxb.test.Sample -U output_jaxb.ser", TEXT(Input)), LASTERRORMSG())
PUT : VALID(PUT("JAXB", "-C com.ibm.websphere.dtx.m4jaxb.test.Sample -U output_jaxb.ser", TEXT(Input)), LASTERRORMSG())
GET : =VALID(GET("JAXB", "-C com.ibm.websphere.dtx.m4jaxb.test.Sample -U output_jaxb.ser"), LASTERRORMSG())
GET : =VALID(GET("JAXB", "-C com.ibm.websphere.dtx.m4jaxb.test.Sample -U output_jaxb.ser"), LASTERRORMSG())
INPUT (Adapter): -C com.ibm.websphere.dtx.m4jaxb.test.Sample -URL output.ser
OUTPUT (Adapter): -C com.ibm.websphere.dtx.m4jaxb.test.Sample -URL output.ser

44. Adapters : JAXB Adapter
/* the map instance number should be unique for thread safety */
int uniqueInstanceNumber = 5;
map.setIntegerProperty( MConstants.MPIP_MAP_INSTANCE, 0, uniqueInstanceNumber );
String key = MObjectPool.getInstance().generateNewReferenceValue(sample);
MObjectPool.getInstance().storeObjectToThePool(uniqueInstanceNumber, key, sample);
adapter.setTextProperty(MConstants.MPIP_ADAPTER_COMMANDLINE, 0, "-C com.ibm.websphere.dtx.m4jaxb.test.Sample -ID " + key);
map.run();
/* we need to remove the object from the object pool */
MObjectPool.getInstance().removeObjectFromThePool(uniqueInstanceNumber, key);

45. Reliability

46. Launch er : Auto Restart
Allows users to configure the launcher to restart automatically, when launcher self-destructs
By default enabled
Retry attempts and Time outs will control the behavior
Support in distributed environments only

47. Launch er : Circular Logging
Allows client with option to enable circular logging
Two new dtx.ini configuration parameters in [Launcher] section
CircularLogSize, default set to 100M
If set to 0, then disable circular logging (current behavior)
CircularLogFileNum – How many logs to keep. default set to 5

48. Security

49. Security : NIST
Enhancing WTX product to be compliant with National Institute of Standards and Technology (NIST) standard as mandated by software group
Introducing support for Java 1.6 SR13
Introducing support for TLS 1.2 as default for HTTP adapter and Launcher Agent
Introducing SHA2 digital signature support for Encoding Adapter
Enhancing the security solution to generate certificates using RSA or DSA keys with 2048 bit or higher

50. Expansion

51. Platforms: Microsoft Windows
64 bit – runtime only
32 bit design tools
XP, Vista, 7, 2003, 2003 R2, 2008, 2008 R2, Win 8, 2012 Server
Virtualization – XP Mode*, VmWare ESX, Citrix

52. Platforms : Cloud Transformation
Launcher is an important part of the WebSphere TX portfolio
Launcher is the offering of choice when you need a lightweight host for WTX maps
When a server runtime is required
When using an ESB that has limitations on the kinds of maps that can run on it (run Launcher side by side)
Datapower
WESB can’t run large maps/data, long running maps
In a file-based world, (especially large files)

53. Platforms: Cloud Transformation
WebSphere TX Hypervisor Edition support for:
Launcher instance provisioning
Launcher configuration
System administration
Managed by IBM Workload Deployer & Pure Systems
Intel support available in 8.4.0
Introducing POWER (AIX) support in 8.4.1
Adding WMQ and DB2 client to WTX launcher hypervisor solution

54. Platforms: UNIX and Linux
Redhat Intel (32/64) – 5, 6*
Redhat Power (64) – 5, 6*
Redhat Z (64) – 5, 6*
Suse Intel (32/64) – 10, 11*
Suse Power (64) – 10, 11*
Suse Z (64) – 10, 11*
Virtualization – VmWare ESX
AIX (64*) 6.1, 7.1*
Virtualization – LPAR, Power VM
Solaris (64*) 10, 11
Virtualization – Dynamic System Domains
HP-UX Itanium (64*) – 11i V2, 11i V3
Virtualization – Integrity VM, nPar & vPar

55. Platforms: Miscellaneous Currency
DB2 v10.1
Informix v11.7
SQL Server v2012
Sybase SQL Server v15.7 (Enterprise)
SAP R/3 Enterprise v5.5
MySAP ERP v2007
SAP ECC v6.5
Java v1.6 SR13

56. Interoperability

57. Interoperability Sterling Integrator 5.4.2.1 or later
No specific enhancements
Websphere Message Broker 8.x & 9.x
Business Process Manager Advanced 8.x
8.5 support will be included at release
Data Power
No support for yet..

58. Evaporated…

59. What’s Gone? Red Hat Enterprise Linux AS v4 for Intel
Red Hat Enterprise Linux AS v4 for System z
AIX 5.3
Solaris 9
Platform API on Distributed Platforms
Support for WESB
Suse10

60. Questions?