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 Mar 28, 2014

ALE IDoc Parsing inconsistency Inbound vs Outbound

Message Broker fails to parse ALE IDoc messages "outward" using the same message formatting characteristics that is used "inward" using the DataObject Parser (and MQ).

An EDIFACT standard is used for inbound messages whilst XML is used for outbound messages, for the same Parser and Message Set settings.

Info Center :
"Tip: If a message that belongs to the DataObject domain is written to a destination other than a WebSphere Adapter, the DataObject parser invokes the XMLNSC parser to write the message as XML"

Idea priority High
RFE ID 46806
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Sep 21, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. We agree that this enhancement suggestion would bring additional value to the product. Whilst the Data Object domain serialization to XML is helpful for many users, an additional ALE IDoc serialization format on outbound as another option would be helpful. Status of this RFE is updated to Uncommitted Candidate. Also noted is a separate RFE 31138 (which itself has 3 votes) which is being returned as a duplicate of this one.

  • 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, 2014

    In general, what about the ability to serialize an IDoc DataObject with message format "SAP ALE IDoc" as it is used by the generic IDoc adapter?