Skip to Main Content
Integration


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 7, 2012

XQuery support requested within WebSphere Message broker

We currently have a lot of integration code written using XQuery. We would like to implement WMB as our Integration Engine. How can we retain all our investment in XQuery ?

Ideally - provide an "XQuery node" within WMB. Alternatively, provide some way of migrating ZQuery code so that it can be used inside existing WMB nodes - eg XSLT / ESQL / GDM ?

Idea priority Medium
RFE ID 28256
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Reply
    |
    Feb 3, 2022

    Idea / RFE Review. Apologies for the length of time this suggestion has been held in the status of Future Consideration. Whilst the previously noted workaround of utilising a JavaCompute node certainly provides a worthy mechanism of achieving the use case presented, we acknowledge that having a built in XQuery node available out of the box would be advantageous to the product. Whilst the relatively moderate voting on this item has not yet enabled us to prioritize this suggestion, it provides sufficient evidence of interest for us to continue to monitor this idea and maintain the status as Future Consideration.

  • Guest
    Reply
    |
    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
    Reply
    |
    Nov 4, 2013

    Our Graphical Data Mapper does have an embedded XQuery processor, however, at the moment we do not expose it to end users. It has been designed so that we could expose it as a general purpose XQuery node in the future, but that is not available at present. We would like to do this in the future, so thanks for raising this requirement as it will help us prioritise this work.
    Today, embedding in a JavaCompute node is your only option.  There are a number of  XQuery 1.0 processors that you could choose from, some of them open source (e.g. Saxon, Zorba).  These could be invoked from a Java Compute node.

  • Guest
    Reply
    |
    May 15, 2013

    This feature is critical in order for us to speak to customers who are running WebLogic Integration - which uses XQuery as the primary technology for message mapping and transformation.