This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.