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 26, 2013

Enable secondary adapter functionality with both cross-container scope and isolation

In WMB V8, the secondary adapter functionality can only be used:
- With applications. However, due to the isolation level of applications, it is not possible to add support for additional IDOC types without interrupting support for those already taken in charge.
- With libraries. However, due to the fact that the deployment scope is the execution group in that case and that no isolation level exists between the library with the primary adapter and those with the secondary adapters, this leads to conflicts due to identical XSD files present in different libraries.

To recover the fine secondary adapter functionality which existed in V7, we need to be able to define primary/secondary adapters and XML files in containers (applications or libraries):
- Isolated enough so that no conflict occurs due to identical XSD files present in several containers.
- Permeable enough to let the message flows defined in one container use XSD files defined in another container linked by a common adapter.

Idea priority High
RFE ID 32900
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Nov 26, 2020

    A comment was posted within RFE 93446 - SAP Primary Adapters require a Message Flow to be stopped prior to redeployment, , linking it as a duplicate to this RFE.

    The two RFE's are not the same.

  • Guest
    Reply
    |
    Sep 22, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. It is likely that this requirement will end up being addressed through the support for adapter models in shared libraries. We have been in client discussions about potential implementation choices around this topic under NDA through our Early Experience Program, and whilst still competing with other features for priority, this remains on our radar and we will continue to monitor. Status of this RFE is updated to Uncommitted Candidate.

  • 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