Build integrated solutions for XML transformations with WebSphere Transformation Extender, Part 2: Integrate with WebSphere Enterprise Service Bus

In this article, we will continue to use the transformation map that we created in Part 1 and demonstrate how to integrate it with WebSphere Enterprise Service Bus flow. This integration provides users a better solution between data transformation and business connectivity.

Share:

Elisa CY Su (elisasu@tw.ibm.com), Advisory Software Engineer, IBM

Photo of Elisa SuElisa Su is an advisory software engineer at China Software Development Lab, IBM Taiwan. She is the project manager of WebSphere Transformation Extender Performance Testing team. Prior to her current position she was a development leader for the IBM worldwide technical support site. Her areas of expertise include performance testing, J2SE/J2EE programming, web application development, content management, and project management.



Jervis Lee (jervisl@tw.ibm.com), Software Engineer, IBM

Photograph of Jervis LeeJervis Lee is a staff software engineer at the IBM Taiwan Software Development Lab. He is the technical leader of WebSphere Transformation Extender Performance Testing team. His areas of expertise include performance testing, J2SE/J2EE/J2ME programming, web application development, and information security solutions.



Roger Chang (changr@tw.ibm.com), Advisory I/T Specialist, IBM

Photo of Roger ChangRoger Chang is a software engineer at China Software Development Lab, IBM Taiwan. His areas of expertise include performance testing, J2SE/J2EE programming, web application development, and network system.



11 September 2012

Introduction

IBM WebSphere Transformation Extender primitive on IBM WebSphere Enterprise Service Bus is available with WebSphere Transformation Extender Version 8.3 and WebSphere Enterprise Service Bus Version 7. This integration provides users a better solution between data transformation and business connectivity. In this article, we will continue to use the transformation map that we created in Part 1 of this series and demonstrate how to integrate it with WebSphere Enterprise Service Bus flow.

You will learn about the capabilities of WebSphere Transformation Extender by integrating with SOA enterprise service bus solutions to create a business flow with complex data transformation quickly and reliably.


Prerequisite

To follow along with the examples in this article, you will need:

  • WebSphere Transformation Extender Design Studio Version 8.3 or higher
  • WebSphere Transformation Extender for Integration Servers Version 8.3 or higher
  • WebSphere MQ Version 7.0.1 or higher
  • WebSphere Enterprise Service Bus Version 7 or higher
  • WebSphere Integration Designer Version 7 or higher
  • DB2 Version 8 or higher

Scenarios

The scenario describes a business flow that is triggered by an external request with customer ID, then gets the customer data from database based on the ID, transforms it into XML, and puts it into a message queue for further operation. We will create a new WebSphere Transformation Extender map that uses the map from Part 1 to do the database data retrieving and data transformation. The map will then be integrated into a WebSphere Enterprise Service Bus mediation flow and connected to the WebSphere MQ queues. The flow is demonstrated in the diagram below.

Figure 1. Business flow overview
Graphic showing business flow overview

Prepare the environment

Prepare the message queues

Create a queue manager named QM_WESB in IBM WebSphere MQ. You can either use MQ Explorer or crtmqm command. But remember the user has to be in mqm group.

Define two local queues under QM_WESB named WTX_RECEIVE_0 (input queue) and WTX_SEND_0 (output queue) respectively.

Prepare the WebSphere Transformation Extender project

If you went through all the steps in the Part 1 to create the DB2XML map (including the advanced mapping section), you can continue to use the existing workspace. You may want to close WebSphere Transformation Extender Design Studio, and open WebSphere Integration Designer with the same workspace (in our test case, the workspace is in c:\temp\mywtx\workspace). Then you may start from Modify Database Query File section.

Or, you can download the WTX_XML_Example.zip file from Part 1 and extract it to C:\temp\mywtx to prepare database environment. Next, download the project interchange file, mywtx_pi.zip (see Download), and import into WebSphere Integration Designer by following these steps:

  1. Open the DB2 Command Window from Windows Start -> Program -> IBM DB2
  2. In the DB2 Command Window, change to the c:\temp\mywtx directory.
  3. Create a database named TESTDB using the db2 create db testdb command.

    Wait a short while, and you should see that the database was created successfully.

  4. Import create table, and insert data with the db2 -tvf db_creation.sql SQL command.

    Make sure all the SQL commands are executed successfully.

You should now have three tables: CUSTOMER, ADDRESS, and PHONE. You can validate the data are inserted correctly by selecting from each table. If there are four records inserted into the customer table, six records in the address table, and eight records in the phone table, your database environment is ready.

Import the project

  1. Open WebSphere Integration Designer, in the Workspace Launcher popup window, type in c:\temp\mywtx\workspace for the workspace.
  2. Select File -> Import. In the Import dialog, select Other -> "Project Interchange" and click next as shown in Figure 2 below.
    Figure 2. Import Project Interchange package
    Screen shot of how to import Project Interchange package
  3. Select mywtx_pi.zip, keep the default location for the "Project location root" field, click DB2XML package and click Finish. The DB2XML project will be imported into the Integration Designer.

Modify database query file

We need to modify the SQL statement stored in db2.mdq by adding the schema name in front of each table. By default, the schema name is the user's name that created the table. So when the user who created the table wants to access the table, the user can ignore the schema name in the SQL statement. This is how we used it in Part 1 of this series.

However, when the WebSphere Transformation Extender maps run under a WebSphere Entreprise Service Bus environment, the user will not be the same as the one who executes the WebSphere Transformation Extender command server, therefore we need to modify the SQL statement by specifying the schema name to identify tables.

To modify the SQL statement:

  1. Continue in the Integration Designer, open the WebSphere Transformation Extender perspective from the File Menu, under Windows -> Open Perspective -> Other -> Transformation Extender Development. On the Extender Navigator view on the left hand side, under DB2XML project -> Database Files directory, right click on db2.mdq and select Open With -> Text Editor.
  2. Search for following lines, which are SQL queries we composed in the Part 1.

    <SQLStmt>SELECT * FROM CUSTOMER</SQLStmt>
    <SQLStmt>SELECT * FROM CUSTOMER WHERE ID='#CID#'</SQLStmt>
    <SQLStmt>SELECT TYPE, NUMBER FROM PHONE WHERE CID ='#CID#'</SQLStmt>
    <SQLStmt>SELECT TYPE, STREET, CITY, COUNTRY FROM ADDRESS WHERE CID ='#CID#'</SQLStmt>
  3. Add the schema name in front of the table name. The schema name will be the user name that you used to create the table. In our example, the schema name is "ROOT". The revised queries are shown here:

    <SQLStmt>SELECT * FROM ROOT.CUSTOMER</SQLStmt>
    <SQLStmt>SELECT * FROM ROOT.CUSTOMER WHERE ID='#CID#'</SQLStmt>
    <SQLStmt>SELECT TYPE, NUMBER FROM ROOT.PHONE WHERE CID ='#CID#'</SQLStmt>
    <SQLStmt>SELECT TYPE, STREET, CITY, COUNTRY FROM ROOT.ADDRESS WHERE CID =
        '#CID#'</SQLStmt>
  4. Save and close the text editor.
  5. Return to the Extender Navigator view on the left hand side, under DB2XML project -> Map File directory, open DB2XMLMap.mms. In the Outline view on the bottom of left hand side, right click on DB2XML map and select Build to build the map. You should not see any errors after building the map.
  6. Follow the steps under Run the WebSphere Transformation Extender map section in Part 1 to verify the DB2XML map configuration. The steps and output should be exactly the same.

Configure the WebSphere Transformation Extender map

First we need to make a WebSphere Transformation Extender map that can take a customer ID from a file input card and generate an XML to a file output card. We decided to use file as the input and output source because it will be easier to verify the map. The input and output card of the map will be overwritten by WebSphere MQ when WebSphere Transformation Extender is integrated into the WebSphere Enterprise Service Bus mediation flow later on.

  1. Continue in the Integration Designer where DB2XMLMap.mms is opened. In the outline view, right click on DB2XMLMap -> New as shown in Figure 3. In the pop-up window, enter ID2XML as the new map name.
    Figure 3. Configure a new executable map
    Screen shot of how to configure a new executable map
  2. On the Outline view, under ID2XML map, right click on the Input Cards -> New. Input the following information for the input card:

    CardName => IdIn
    TypeTree => OutputString.mtt
    Type      => Output Root
    Source: 	 => File
    FilPath	 => in.txt

    as shown in Figure 4. Leave the remaining fields populated with default information.
    Figure 4. Input Card configured for ID2XML map
    Screen shot of input card configured for ID2XML map
  3. Right click on Output Cards and select New. Enter the following information for the output card:

    CardName: XmlOut
    TypeTree: OutputString.mtt
    Type: Output Root
    Source: File
    FilePath: customer.txt

    Leave the defaults in the other fields, as shown in Figure 5. Note that we do not use the customer.xsd as the TypeTree, but a simple string type for the output. You will see why in the next step
    Figure 5. Output card configured for ID2XML map
    Screen shot of output card configured for ID2XML map
  4. After you've created the input and output card, you can see the cards in the Map view on the right. Click on the Output Card and enter the following information in the XmlOut item:

    =RUN("DB2XML.mmc", "-ID1 '-VAR CID="+IdIn+"' -ID2 ' -VAR CID="+IdIn+"' -ID3 
    '-VAR CID="+IdIn+"' -OE1")
    Figure 6 illustrates how.
    Figure 6. Mapping in ID2XML map
    Screen shot of mapping in the ID2XML map

    This rule calls the RUN function to run the DB2XML map we built in the first article and set "IdIn" from the input card as the parameter CID. The ECHO option "-OE1" will pass the output content generated by DB2XML map back to the XmlOut field in the ID2XML map output card as a TEXT. This is why we specified a simple string as the output type in step 16.

  5. Return to the Outline view, right click on the ID2MXL map and select Map Setting as shown in Figure 7.
    Figure 7. Configure map settings
    Screen shot of configuring map settings
  6. In the map settings, set MapAudit and MapTrace to OFF (this can be turned on for troubleshooting as needed), and set WorkSpace to Memory (to improve performance) as shown in Figure 8.
    Figure 8. WebSphere Transformation Externder map settings
    Screen shot of the WTX map settings
  7. Save the map.
  8. Right click on ID2XML and select Build to build the map. You should not see any errors after building the map.
  9. In the File menu, select File -> New -> Other. In the New wizard, select Untitled Text File under the General folder and click Finish. Input "000001" in the text content and save the file as "in.txt".
  10. Right click on ID2XML and select Run to run the map. You should see the Command Server window showing "Map completed successfully," as shown in Figure 9.
    Figure 9. Figure 9. Successfully run the map
    Successfully run the map
  11. You should be able to find the output file, customer.txt, from the Extender Navigator view, under DB2XML -> Misc folder. If not, try to refresh it. If you have successfully created the WebSphere Transformation Extender map, the content of the customer.txt will look like the following:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <customer userid="000001">
    <first_name>Bob</first_name>
    <middle_name>JK</middle_name>
    <last_name>Smith</last_name>
    <id>AAAAAAAAAA</id>
    <gender>M</gender>
    <birthdate>1977-01-01</birthdate>
    <occupation>Engineer</occupation>
    <phone_number type="office">111-1111</phone_number>
    <phone_number type="mobile">0911-123456</phone_number>
    <address type="home">
    <street>1 Park Street</street>
    <city>New York</city>
    <country>U.S.</country>
    </address>
    <address type="office">
    <street>1 Lakewood Street</street>
    <city>New York</city>
    <country>U.S.</country>
    </address>
    </customer>

Configure the WebSphere Enterprise Service Bus mediation flow

Now that we completed the WebSphere Transformation Extender map, let's integrate it into a WebSphere Enterprise Service Bus mediation flow.

Create a new mediation flow

  1. Continuing in the Integration Designer, create a new mediation module by File -> New -> Others -> Mediation Module. Enter MyWTXFlow as the module name. Select WebSphere ESB Server v7.5 for the target runtime environment and click Finish, as illustrated in Figure 10.
    Figure 10. Create a new mediation module
    Screen shot showing how to create a new mediation module

Generate predefined data types

  1. By creating the mediation module, you are now in working from a business integration perspective. In the Business Integration view on the left hand side, double click on the Dependencies to open Dependencies Editor. (If you didn't see the Dependencies item on the left hand side, right click on MyWTXFlow and refresh it.) In the MyWTXFlow Dependencies editor, expand the Predefined Resources section, select Native Body schema for Native Body DataHandler item from the list and save it.
    Figure 11. Select Predefined Resources
    Screen shot showing how to select Predefined Resources
  2. After you save the Dependencies Editor, there will be several data types generated in the Business Integration view, see Figure 12.
    Figure 12. Predefined data types
    Screen shot showing predefined data types

Create the interface

  1. Create a simple interface from File -> New -> Interface. You may leave the "Folder" field empty, and enter OneWayBlob for the interface name. Click Finish.
  2. On the OneWayBlob Interface Editor, click on Add One Way operation icon to add one way operation, as shown in Figure 13.
    Figure 13. Configure interface
    Screen shot showing how to configure the interface.
  3. Enter doMQ as the operation name. Leave input1 as the default input name but select TextBody for the input type, as illustrated in Figure 14.
    Figure 14. Add an operation in the interface
    Screen shot showing how to add an operation in the interface.
  4. Save and close the interface editor.

Configure the mediation flow

  1. Next we need to create the WebSphere MQ inbound node. In the Business Integration view on the left, double click on Assembly Diagram to open Assembly Diagram Editor. In the Assembly Diagram Editor, on the left Palette, select MQ node under Inbound Exports category (see Figure 15).
    Figure 15. Select MQ Inbound node from Palette
    Screen shot showing selecting MQ Inbound node.
    Drag and drop the node icon onto the canvas to the right. When you drag and drop the MQ node to the canvas, the "New MQ Export Service" creation wizard will popup to guide you complete the configuration. Select OneWayBlob for the interface (see Figure 16) and click Next.
    Figure 16. Select OneWayBlob Interface
    Screen shot showing selecting onewayblob interface.
  2. Input the MQ input queue detail based on your MQ configuration. In this example, input QM_WESB as the Queue Manager, WTX_RECEIVE_0 as the receive queue, and then select Binding as the transport. See Figure 17.
    Figure 17. Configure MQ Export Binding
    Screen shot showing how to configure MQ Export Binding
  3. For the "Function selector", also shown in Figure 17, click Select button to bring up another wizard, as shown in Figure 18. Select One Operation Function Selector under "Use existing function selector from the list" category. Click Finish to complete the wizard.
    Figure 18. Function Selector Configuration.
    Screen shot showing function selector configuration
    Then click Finish on the Create New MQ Export Service wizard to complete the MQ Export node configuration. Rename the node as MQIn in the canvas.

Create MQ Outbound Import

  1. Continue in the Assembly Diagram Editor, on the left hand side Palette, select MQ node under Outbound Imports category, as shown in Figure 19. Drag and drop the icon to the node onto the canvas to the right.
    Figure 19. Select MQ outbound node from Palette
    Screen shot showing how to select MQ outbound node from Palette
    When you drag and drop the MQ node to the canvas, the "New MQ Import Service" creation wizard will popup to help you complete the configuration. Select OneWayBlob for the interface and click Next.
  2. Next, input the MQ output queue detail based on your MQ configuration. In this example, input QM_WESB as the Queue Manager, WTX_SEND_0 as the receive queue, and select Binding as the transport, as shown in Figure 20. Then click Finish to complete the MQ Import Node configuration. Rename the node as MQOut in the canvas.
    Figure 20. Configure MQ Import Binding
    Screen shot showing how to configure MQ import binding

Wire the node

  1. On the Canvas, connect the link between MQIn, MyMQFlow, and MQOut nodes. See Figure 21.
    Figure 21. Connect between nodes
    Screen shot showing connecting nodes
  2. Next generate implementation of mediation flow. Right click on the MyWTXFlow node on the canvas, and select Generate Implementation, as shown in Figure 22.
    Figure 22. Select Generate Implementation
    Screen shot showing selecting generate implementation
  3. On the Generate Implementation wizard, keep the default selection of "MyWTXFlow" folder and click OK to generate implementation.
  4. This takes you to the Mediation Flow Editor. Click on doMQ and select Operation Map as shown in Figure 23.
    Figure 23. Mediation Flow Editor
    Screen shot showing selection of mediation flow editor
  5. In the "Select Reference Operation" wizard, keep the default selection, as shown in Figure 24, click OK to complete it.
    Figure 24. Select Reference Operation
    Screen shot showing select reference option
    You should see the request flow been created in the Request Mediation Flow Editor, as shown in Figure 25.
    Figure 25. Request Flow
    Screen shotshowing request flow has been created
  6. Delete the connection between the Input and Callout node. From the Palette on the left side, drag and drop WTX node to the canvas, now identified as WTX1. See Figure 26.
    Figure 26. Add WTX node
    Screen shot showing addition of the WTX node
  7. Right click on the WTX1 node and select Add Output Terminal, as shown in Figure 27.
    Figure 27. Add output terminal
    Screen shot showing how to add output terminal
  8. On the "Create Terminal" pop-up window, leave the default values and click OK.
  9. Wire OneWayBlob to WTX1 node, and wire WTX1 node to OneWayBlobPartner. Note that when you wire WTX1 node to OneWayBlobPartner, you need to choose to be wired from outputCard1 terminal as highlighted in red in Figure 28.
    Figure 28. Connect the node in Request flow
    Screen shot showing how to connect the node in the request flow
  10. Under the "Properties" tab, click on the WTX node icon, select Details to configure WTX Map Source. Select Use map from project. In the map source field, click Browse to choose appropriate map. See Figure 29.
    Figure 29. WTX Map properties configuration
    Screen shot showing WTX map properties configuration
    On the popup dialog, select ID2XML map under DB2XMLMap and click OK.
  11. Click the Map Cards tab beside the Map Source tab, click Add beside Input Card list to add Input Card. On the pop-up dialog, enter 1 for the Input Card Number, and click Edit, select Input Data Path. On the "Select Data Path" dialog, select Data Types -> ServiceMessageObject -> body:doMQRequestMsg -> doMQ -> input1:TextBody -> value:String, as shown in Figure 30. Click OK to complete the configuration.
    Figure 30. Select Data Path for InputCard
    Screen shot showing how to select data path
  12. Follow the same steps to add output card. Enter 1 for Output Card Number, select Data Types -> ServiceMessageObject -> body:doMQRequestMsg -> doMQ -> input1:TextBody -> value:String for the "Output Data Path" field. Click OK to complete the configuration. You should see the input and output card configuration been added, as shown in Figure 31.
    Figure 31. Map cards configurations
    Screen shot showing map cards configurations
  13. Save the flow.

Generate ear file for deployment

  1. Now you are ready to generate the ear file for deployment. On the Project Navigation view, right click on the MyMQFlow and select Export, as shown in Figure 32.
    Figure 32. Export for deployment
    Screen shot showing exporting for deployment
  2. On the Export wizard, select EAR file under Java™ EE category and click Next, as shown in Figure 33.
    Figure 33. Select EAR file
    Screen shot showing selction of ear file
  3. Next, provide the location where you want to export the ear file. In this example, we will generate the ear file under C:\temp. Select WebSphere ESB Server v7.5 for the target runtime, as illustrated in Figure 34. Then click Finish to generate the ear file for deployment.
    Figure 34. EAR export configuration
    Screen shot showing EAR export configuration

Deployment

Now we will briefly show you how to deploy the ear file onto WebSphere Enterprise Service Bus server. We will assume that it is on the same machine as the Integration Designer such that DB2 tables and WebSphere MQ queue manager are well configured as explained in the previous steps. Make sure DB2 and QM_WESB queue manager are both started.

Additionally, we assume that you know how to create a new profile on WebSphere ESB server or that you may use any existing profile. You may create a new profile on WebSphere ESB server named Test01 by either Profile Management Tool (if the system is 32 bit) or manageprofiles.bat command (for both 32 and 64 bit system). We provide the command that we used as an example. Remember to replace correct database user ID and password in the example command below. Find more detailed information in the WebSphere ESB Information Center.

"C:\Program Files\IBM\WebSphere\AppServer\bin\manageprofiles.bat" -create -templatePath 
"C:\Program Files\IBM\WebSphere\AppServer\profileTemplates\default.esbserver" 
-profileName TEST01 -dbType DB2_UNIVERSAL -dbUserId DB_USER_ID -dbPassword DB_PASSWORD

If you have already created at least one profile on that WebSphere ESB server and you would like to create an additional new profile for testing, you may use the above command with one additional argument, dbDelayConfig true to avoid a "dbType: CWMCF0021E: The database CMNDB already exists." error.

  1. Start server TEST01 from Windows Start -> Programs -> IBM WebSphere -> Enterprise Service Bus -> Profiles -> TEST01 -> Start the server.
  2. Enter the administrative console of TEST01, Windows Start -> Programs -> IBM WebSphere -> Enterprise Service Bus -> Profiles -> TEST01 -> Administrative console. On the left, click Applications -> Application Types -> WebSphere Enterprise Applications. On the right pane, click Install on the top section to install the ear file. Follow the wizard to select the MyWTXFlowApp.ear file under c:\temp that we just exported. Leave everything as default in the first part. In the second part, remember to select MyWTXFlowWeb. In the last part, leave everything as default and click Finish to complete the ear installation. If the installation is successful, click Save. You should be able to see MyWTXFlowApp application listed on the Enterprise Application list. The deployment is completed. Click MyWTXFlowApp from the list, then click Start. After the start process is successful, you will see the green arrow beside the application, as shown in Figure 35.

    Note: If you encountered problems and you are not able to start the application server, you can check the log from SystemOut.log and SystemErr.log under {WTX_Installed_Dir}\profiles\TEST01\logs\server1 directory.

    Figure 35. Successfully deployed MyWTXFlowApp ear
    Screen shot showing a successfully deployed MyWTXFlowApp ear

Verification

Now let's put test messages from MQ Explorer to verify the flow is started correctly.

  1. Start MQ Explorer. Open the Queue lists by QM_WESB -> Queues. Right click on WTX_RECEIVE_0 and select Put Test Message… item from the list.
  2. On the "Put message" pop up dialog, enter 000001 in the "Message data" field and click Put message to put the message, as shown in Figure 36. Close the dialog.
    Figure 36. Put test message
    Screen shot showing how to put the test message
  3. If the flow is successful, you should be able to see "Current Queue Depth" of the WTX_SEND_0 queue becomes 1 from MQ Explorer.
  4. Verify the output message content by right clicking on the WTX_SEND_0 queue and select the Browse messages… item. On the Message browser pop up window, double click on the only message in the list. You should be able to get the message content from the Message properties pop up window, as shown in Figure 37. You can copy the content from Data -> Message data field and pasted to a text editor.
    Figure 37. Viewing message content
    Screen shot showing viewing message content
  5. Verify the message content is exactly the same as the customer.txt that been listed in step 24 under Configure the WebSphere Transformation Extender map section. Now you should learn the knowledge of how to enhance WebSphere Transformation Extender transformation capabilities by integrating with IBM SOA business flow.

Download

DescriptionNameSize
project interchange filemywtx_pi.zip18KB

Resources

Learn

  • WebSphere Transformation Extender: Get product descriptions, news, training information, support information, and more. Specifically:
    • Documentation: Use the Information Center for all WebSphere Transformation Extender documentation, with conceptual, task, and reference information on installation, configuration, and usage.
    • Library: Get all the WebSphere Transformation Extender information, including books, and release notes for recent versions.
    • Requirements: Learn about the hardware and software requirements.
    • Support: Start here to search a database of problems and solutions, plus downloads, fixes, and problem tracking.
  • developerWorks WebSphere site: Get technical information and resources, product downloads, how-to information, support resources, and a free technical library of more than 2000 technical articles, tutorials, best practices, IBM Redbooks, and online product manuals.
  • WebSphere downloads: Access WebSphere downloads, including product trials, emerging technologies, updates, fixes, utilities and drivers.
  • developerWorks WebSphere weekly newsletter: Connect to the latest and greatest developer resources. Get the latest articles and information on topics that interest you.
  • WebSphere-related books from IBM Press: Peruse the latest literature and link to convenient online ordering.
  • WebSphere-related events: Learn about conferences, trade shows, Webcasts, and other events around the world of interest to WebSphere developers.
  • developerWorks on Twitter: Join today to follow developerWorks tweets.
  • developerWorks podcasts: Listen to interesting interviews and discussions for software developers.

Get products and technologies

  • Evaluation software: Find more trial software. Download a trial version, work with product in an online, sandbox environment, or access it in the cloud.

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere, XML
ArticleID=831271
ArticleTitle=Build integrated solutions for XML transformations with WebSphere Transformation Extender, Part 2: Integrate with WebSphere Enterprise Service Bus
publish-date=09112012