Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Sep 1, 2022

Deploy individual components to Integration server

We were in process of migrating IIB v10.0.0.24 to ACE, could see integration server migrating with default application,

Integration server -> SAP adapter as library (one adapter for per SAP) & multiple idoc definitions as library

Adapter and idoc definitions library have reference to convert from IDOC format to XML, Which was designed by IBM Developer in 2016 with WMB8 and later migrated to IIB with same.

As Idoc definitions changes timely based on business changes or SAP upgrades, we have to redeploy idoc definitions with out disturbing adapter, which is not the case if we use as application, we can not delete a single idoc definition library from application, that's the reason we won't want to use Defaultapplication .

Please provide option to disable generating <IntegrationServerName>_DefaultApplication while using mqsiextractcomponents command.

Please refer attached screenshot.

Idea priority Urgent
  • Admin
    Ben Thompson
    Sep 19, 2022

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request, but on this occasion this is not an idea we intend to take forward. Thank you for the email and direct webex conversation we have had on this matter, which seemed to provide you the options which you require to move forward with the migration. I'll include below some notes for the potential benefit of other readers.

    We initially discussed the architectural background to the way in which we deploy artifacts to the runtime. Applications and libraries as groupings for artifacts which are deployed have been a core part of our architectural strategy since they were first introduced ten years ago as part of WMBv8. Since that time, we have tried to encourage the use and adoption of applications by all users who have previously used independent resources defined in integration projects. Applications allow users to isolate the requirements of different flows deployed to the same integration server. In ACEv11 and ACEv12 you can still deploy older BAR files that contain independent resources, but these are deliberately placed into the default application - whose name you can control through the server.conf.yaml file. We believe there are many advantages for the adoption of applications and libraries. Some of these are outlined in this topic from the IIBv10 documentation:

    Regarding the specific SAP Adapter use case, we discussed a popular design pattern ( which enables the distribution of IDocs from a single message flow, which is resident in an application alongside an inbound SAP adapter component. This message flow can distribute the IDocs to other applications, which each can be separately deployed with their required data model. Redeploying a data model only impacts the subsequent application and does not require the redeployment of the main "distributing" message flow.

  • Guest
    Sep 5, 2022

    this decoupling of idoc definition is necessary