1

Lab: IBM WebSphere®

Transformation Extender V8.2 Design Studio for IBM WebSphere DataPower®

Bill Hines – IBM Software Services for WebSphere

#1103

Non-XML Transforms

� You *can* set the output as ‘text’ in a normal XSLT transform

– Limited usages here (XML must be input), you really need more – a standard way to

describe the layout of the non-XML data (see below)

� Current choices

– XSL-FO – really for things like converting XML to PDF, layout based, takes into account the

target medium, for paginating XML, etc.

– DFDL (“daffodil”) - The Data Format Description Language (DFDL or "daffodil") is emerging

as a notation for describing mappings between data in formatted files (text as well as binary)

and a corresponding XML representation. A DFDL specification takes the form of an XML

Schema with "application annotations" that make the correspondence between file

characters (or bytes or even bits) and XML data values precise. See http://forge.gridforum.org/projects/dfdl-wg/

– FFD – Proprietary notation (as described above for DFDL) invented by Contivo for use by

their products, and understood by DataPower. NOT for use without a Contivo license!

– DPA – Proprietary binary format used by IBM WebSphere TX as shown in these slides.

– These are *XML* documents that describe the format of non-XML data!

DataGlue Format Descriptors: How it works

DataGlue™Engine

DataGlue

translator

Application

Message A

Application

Message B

Input FD

• Text or XML file

• Defines message

format (“A” here)

•Can be multiple

inputs

• Examples: XML

Schema XSD, Corba

IDL, ASN.1, COBOL

copy book, etc.

Map

• Created using visual tool or

• Derived from existing maps

• Defines mappings between

different messages

Output FD

• Text or XML file

• Defines message

format (“B” here)

•Can be multiple

outputs

• Examples: XML

Schema XSD, Corba

IDL, ASN.1, COBOL

copy book, etc.

WebSphere TX Design Studio supports DataPower• Design Studio now provides support for developing maps that can be run on

the DataPower SOA Appliance. Version 8.2+ built on the Eclipse framework.• It provides an IBM alternative to Contivo Analyst, a third party software used

with DataPower appliances• This enhancement enables the same skill sets to be deployed at design time

for data transformation across your SOA with WebSphere TX and DataPower

WebSphere TX Design Studio Type Designer• Type Designer is similar to Contivo

Interface Modeler

• A type tree describes the syntax,

structure, and semantics of data.

• The syntax of data refers to its format

including tags, delimiters, and

terminators.

• The structure of data refers to its

composition including repeating

substructures and nested groupings.

• The semantics of data refer to the

meaning of the data including rules for

data values, relationships among parts

of a large data object, and error

detection and recovery.

• Can be created by importing CPY,

XSD, WSDL, etc.

WebSphere TX Design Studio : Map Designer• Map Designer similar to Contivo Mapping Studio

• The Map Designer is used use to develop maps that define input and output specifications and mapping rules for data transformation

• Type trees are used to describe the input and output formats.

Enhancements for IBM DataPower SOA Appliances

• A new Map Property will allow

Design Studio users to choose

the target runtime of their Map.

• This option will only be

presented in Map Designer –

not the Command Server, IFD,

SDK or any other environment.

• Selecting the DataPower

Runtime will disable some

WebSphere TX features.

• There is also a “DataPower

Local Mode” for when

DataPower is not accessible

(approximates DP, map must be

set to DP runtime)

Enhancements for DataPower SOA Appliances• The Options dialog has been enhanced for providing support for DataPower

SOA Appliances in the Map Designer.

• A new section ‘DataPower Maps’ has been added for this purpose. To invoke this dialog, user has to select ‘Windows’ Main menu and then select ‘Preferences’ menu item in the Map Designer.

• The Connectivity’section allows the user to define connectivity to the Appliance.

• The ‘Save Messages’section allows the user to choose whether Request and Response messages be saved in the map source file directory.

Enhancements for IBM DataPower SOA Appliances• Running DataPower maps is no different from running WTX maps.

• When you hit the ‘Run’ button on a DataPower map, the Run dialog for DataPower SOA Appliances appears.

• A new Run dialog has been introduced and is similar to that of Command Server window.

• The Run dialog initiates the

communication between Map Designer

and the DataPower appliance by sending

a request message to the Appliance and

waits on the response from the

DataPower appliance.

• After the map finishes execution, the

results/outputs can be viewed using Run

Results dialog and Run Results views.

Enhancements for IBM DataPower SOA Appliances• The mcompile.exe

command line utility will also allow you to compile

maps for the DataPower

appliance.

WTX Design Studio in DP modeWTX Design Studio in DP mode

User chooses to

compile/test on DP

Windows

1

2

3

7

Developing with WTX Design Studio and DataPower XI501. Client chooses DP mode and develops transformations

using WTX Design Studio

2. Client chooses compile or execute from WTX Design Studio

3. WTX Map Designer calls a DataPower module to transmit the transformations to the XI50 appliance with compile/run instructions (transparent to user)

4. DataGlue engine runs, returning any errors back to WTX Design Studio (transparent to user unless compile errors)

5. Loads the transformations into DataGlue (transparent to user)

6. Executes (transparent to user)

7. Logs and output are transferred back to WTX Design Studio for examination, if requested

DataGlue™Engine

DataGlue translator

Application

Message A

Application

Message B

Transform Action

XI50

4

6

5

7

SOAP with

attachments to communicate with

the XI50

DataPower Design Time Configuration

1. Log in as admin (or similar)2. Import WTX configuration3. Save Configuration4. Test Configuration

This creates XML Firewalls that respond to the SOAP with Attachment bundles created by Map Designer during design-time testing.

The configuration files are found on the Resource CD & website.

Notice the local address has been changed – the 0.0.0.0 default is not recommended.

The deployed-tx-test domainhas useful examples!

For https – generate certificate/key per the technote.

Import Configuration

Verify

WTX Design Studio in DP modeWTX Design Studio in DP mode

User chooses to

save/export transformation in

DP format

Windows

1

2

3

Deploying with WTX Design Studio and DataPower XI50

1. Client develops and tests as described on previous slide

2. Client saves as DataPower format from WTX Design Studio

3. Client manually uses the DataPower web base interface to transfer the transformations saved in 2.

4. Client chooses to compile and deploy the transformations

5. Client deploys DataPower XI50 as normal

DataGlue™Engine

DataGlue translator

Application

Message A

Application

Message B

Transform Action

XI50

4

5DataPower web interface

Exporting Map Designer Maps for DataPower

To export completed maps for useon the DataPower device, selectMap – Build (or Build-All). The mapfile may contain more than one map.

For WTX 8.1, this generates files ending in .MTSand the map file mapname.xml. Thesefiles must be moved to the DataPowerdevice for production use.

For WTX 8.2+, one file projectname.dpa

DataPower Production Configuration

Upload the necessary map file(s) to thedevice.

Create a Processing Policy containinga Binary Transform (xformbin) action.Configure the action to Use XSLT on a non-XML message.

Supply the location of the uploaded mapname.dpa file (local:///filename).

Maps containing only one input andonly one output can use the defaultInput and Output processing contexts.

Recent DataPower Firmware Enhancements

DataPower 3.7.1 added:

Two read-only variables to determine the size of non-XML messages:var://service/mpgw/request-size - Gets the size of a request message.var://service/mpgw/response-size - Gets the size of a response message.

DataPower 3.7.2 added:

DPA mode for faster processing, cleaner deployment

Support for WTX 8.2 (WTX 8.2.0.3 with DataPower patch)

Deprecated older (XML/MTS) map mode and “Mapping Logic Disabled” switchThere is a migration process in the DataPower/WTX doc

New in 3.7.1/3.7.2

Further Information� New IBM Press DataPower Handbook

– http://www.amazon.com/gp/product/0137148194?ie=UTF8&tag=dph-

20&link_code=as3&camp=211189&creative=373489&creativeASIN=0137148194

� WebSphere DataPower

– www.ibm.com/software/integration/datapower

� WebSphere Transformation Extender

– www.ibm.com/software/integration/wtx

Lab Notes� Type Tree Importer

– Lots of choices, very powerful

• Java, JMS, CORBA IDL, Text, WSDL, DTD, Schema

• WSDL was a limitation in prior versions (< 8.2.0.2)

� Still has some kinks to be worked out

– Sometimes touch up is needed after importing

– Some schema definitions don’t work well (WPS, WID)

� Map Designer

– Can directly place XSD on the input card (and avoid building a Type Tree)

– Map Source vs Map file confusion

– Command macros, functional maps are powerful concepts

� DataPower

– Select the DPA file from the correct dropdown!

� Doing initial development against TX runtime provides more tools to debug

We love your Feedback!

� Don’t forget to submit your Impact session and speaker feedback! Your feedback is very important to us, we use it to improve our conference for you next year.

� Go to www.impact09guide.com on a smartphone device or a loaner device� From the Impact 2009 Online Conference Guide;

– Select Agenda

– Navigate to the session you want to give feedback on

– Select the session or speaker feedback links

– Submit your feedback

© IBM Corporation 2009. All Rights Reserved.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for

informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While

efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS IS without warranty of any

kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other

materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its

suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.

Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities

or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is

intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other

results.

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.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have

achieved. Actual environmental costs and performance characteristics may vary by customer.

The following are trademarks of the International Business Machines Corporation in the United States and/or other countries:

ibm.com/legal/copytrade.shtmlAIX, CICS, CICSPlex, DataPower, DB2, DB2 Universal Database, i5/OS, IBM, the IBM logo, IMS/ESA, Power Systems, Lotus,

OMEGAMON, OS/390, Parallel Sysplex, pureXML, Rational, Redbooks, Sametime, SMART SOA, System z , Tivoli, WebSphere, and z/OS.

A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United

States, and/or other countries.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of

Government Commerce

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and

Trademark Office

Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.