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 Future consideration
Workspace App Connect
Created by Guest
Created on Jul 31, 2015

Change mqsicreatebar command to include keywords.txt

You have a feature available to include a keywords.txt file to add comments to an application or library in a bar file that can be viewed in the IIB explorer when viewing the contents of an integration server. In order for the keywords.txt file to be included in the bar file, you must use the mqsipackagebar command as the mqsicreatebar command and the toolkit create process ignores the file since it ends in a .txt file extension. It would seem easy enough to do to include this file if it exists in the project when creating the bar file as you have specified it as an IIB object in your information center. The process to use the keywords.txt file today is very complicated and creates extra work to accomplish. We are trying to use the keywords.txt file to add the SVN version that was used to build the application so you can see which source code version is currently running in the production Integration Node in order to ensure that we have a stable environment.

Idea priority High
RFE ID 74868
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Jun 28, 2022

    Idea / RFE Review. Further to the last review and comment, we note that the product continues to evolve in the right direction with regard to this functional area. The ibmint package bar command now allows the keywords.txt file to be added as a parameter. This improvement helps utilise keywords more easily as part of a pipeline, but we note doesn't help with the BAR build process in Toolkit. Status is maintained as Future Consideration.

  • Guest
    Jul 6, 2016

    Thanks for raising this RFE. Glad to hear you were able to follow the documented instructions for mqsipackagebar, but we agree that improving the mqsicreatebar command to be sensitive to keywords.txt would be a great enhancement for the usability of the product. Status of the RFE is updated to Uncommitted Candidate.

  • 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