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 Delivered
Workspace App Connect
Created by Guest
Created on Aug 15, 2013

Provide tool in tool kit to import all previous releases of source

We have been using IIB since it was MQSI 1.2. So we have a large amount of legacy code. Like legacy code on the mainframe, once tested and in production, the code can be left untouched for years since the basic functions do not change. As the use of IIB increases, it makes sense for IBM to provide a way to migrate object code from any prior release. There by making upgrades easy. It should also make it easy to modify source code in the current release, no matter what release if was developed in

Idea priority Urgent
RFE ID 38136
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Aug 11, 2021

    Idea / RFE Review. Apologies for the length of time this suggestion has been in the status of Uncommitted Candidate / Future Consideration, during which time the product has evolved considerably. Noting that this particular suggestion for enhancement was initially raised in 2013, the subsequent major engineering releases 10, 11 and 12 have moved the product architecture in the same direction as specified and requested here ... This started with the introduction of the "source deploy" feature in WMBv8 simplified deployments by carrying source files to the runtime in the BAR file and avoiding the need for compiled message flows (.cmf extension). We encourage all users to adopt source deploy these days, and group their artifacts in applications and libraries (another innovation from v8, extended further with the advent of shared libraries in v10) too, but following our long history of back compatability we also allow BAR files with .cmf content to be carried forward in to the currently in-service releases of the product.

    To further assist in the porting of artifacts back and forth between "source" and "server" (ie the file system of the runtime, which stores knowledge of all deployed artifacts in the server's "work directory") we made further significant changes to the way in which we store configuration for the product as part of the ACEv11 release which transformed the product for suitability in container-native architectures. These improvements included defining node and server configuration properties in yaml files, policy files (which can be copied to an override directory on the product runtime or carried in a BAR as part of a traditional deploy) to replace configurable services, and most significantly the removal of UUIDs from the directories and files which underpin the runtime file stores. This latter point is highly significant when considering this enhancement suggestion ... we now have a file system underpinning the product runtime which makes it trivial to clone servers by simply copy and pasting files, and also for retrieving deployed artifacts in order to edit them back in the Toolkit.

    Given these advances, we are updating the status of this idea to delivered, but if you feel further specific changes are needed in this area please feel free to report them to us through a new idea submission.

  • Guest
    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
    Aug 30, 2013

    Thanks for raising this requirement. Just to clarify, are you looking for a way of extracting the live source from a running broker so that it can be reconstituted in the Toolkit? That's my reading of this requirement, but if I've missed the point please let me know through the RFE!