Skip to Main Content

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Apr 25, 2012

Expose common transformation assets (e.g. xQuery and XSL files) in the WMB mapping node for integration with non IBM products

Expose common transformation assets (e.g. xQuery and XSL files) in the WMB mapping node for integration with other products including non-IBM products .

Currently MDM Server ASI tooling uses the same technology as the WMB mapping node and exposes an XSL file representing the transformation. This allows the XSL file to be used by other tools.

The WMB mapping node in the tooling uses xQuery at runtime but does not expose xQuery or xsl assets to the user. WMB appears to inefficiently generate the xQuery file at runtime and not store it..
Currently the WMB mapping node produces a map file (which is an IBM proprietary format) to represent the transformation.

If the WMB mapping node exposed common assets for transformations, these could be shared so that other IBM and non-IBM products could use these transformation assets. This would fit with IBM's strategy to promote open standards and compete on implementation.

I have raised this as a high priority as not being able to share assets leads to inefficient solutions with the same or similar transformations needing to authored in different systems. Having these common assets for transformations would give us a strong story to use WMB to author your transformations, in that we can generate files that comply to open standards that can be re-used across your solution.

Idea priority High
RFE ID 21883
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Oct 4, 2021

    Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. Our strong suspicion is that the need for this request has long since been satisfied through other means in any case, and for this reason coupled with the very low number of votes (2 votes over 9 years), we will not be moving forward with this suggestion. To expand on the reasoning here, the IIB/ACE graphical data mapping capability (GDM) has been made available as a common component within the company so that other parts of IBM can share it (in line with the open source style separable component idea), but this is a distinct issue from exposing the code in such a way that any alternative XSL or XQuery engine would be capable of executing the files in a non-proprietary context. As noted, the feature as currently designed and implemented deliberately chooses not to externalise the generated code. Any change from this strategy would obviously have commercial implications. Other points worth making in regard to this issue are that the ability to pre-compile maps and schemas into a BAR file prior to deployment has been made available in subsequent product releases, so there is no performance argument to be made in favour of changing the current operational model of this code component. Another factor worth considering is that the open-sourced JSONata mapping technology has also received higher levels of investment more recently than GDM, so in terms of long-term alternatives you may also wish to consider its capabilities too.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Jun 1, 2012

    Thanks for raising this requirement. At a high level, we think there are two phases to the solution: (1) Provide export capabilities from the mapper into XSL and/or xQuery, and (2) Improve the consumability of the mapper as a separable component. We'll look to start this work as a candidate for the second half of the year.