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

mqsipackagebar includes unnecessary files - bloats bar size

Problem title
mqsipackagebar includes unnecessary files - bloats bar size
Problem description

We had some Ant build scripts written to include specified files into a
bar. These scripts have been working for a few months now, no problems.
We explicitly did not create an 'Application' from our project. We
simply built the bar by including all the needed files, file-by-file,
and used command line like:

mqsipackagebar -w xyz -a zyx -o file1 file2 ... file49 file50 file51

Someone down the line in the source code control system converted the
Message Flows into an Application. Now, the mqsipackagebar fails with

BIP1868W: Ignoring 'file1.esql', which is in application
''. Use the -k option to include the application.

We have thousands of xml files that make up test case payloads located
in a subdirectory of the project. We never want to include these xml
files in the bar files.

When putting the -k option in the mqsipackagebar command, the
mqsipackagebar scans the project and includes all files specified by

By default files with only the following extensions are included in the
BAR file: .xsdzip, .tblxmi, .xsd, .wsdl, .dictionary, .xsl, .xslt, .
xml, .jar, .inadapter, .outadapter, .insca, .outsca, .descriptor, .php,
.idl, .map, .esql, .msgflow, and .subflow. You can specify the -i
option to include files with any extension.

which is incorrectly including also all the thousands of xml payload

How to change the default behavior of mqsipackagebar so that xml files
in specific directories are not included, or specified subdirectories
are ignored?

This is a request for an APAR to mqsipackagebar that enables the
commandline tool to exclude certain failed or directories when using
the -k option on the commandline.

We need a way to scope the file inclusion. Simply including all files
inside the project filesystem is not desirable. There are files we want
to be included in the project filesystem so that they get recorded into
the version control on that project but we don't want to deploy those
thousands of XML files to the Broker.

We do not want to use mqsicreatebar. We must use mqsipackagebar and
need to deplouythe resulting bar file without manually breaking it
apart to remove the unnecessary files.

We realize that mqsipackagebar is operating as it is designed and are
asking for an APAR to assist us in scoping the file inclusion to the
right level.

Idea priority Medium
RFE ID 36740
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Oct 6, 2020

    RFE Review. We continue to monitor this RFE. With mqsibar (ACEv11) to add to the pre-existing build commands mqsicreatebar and mqsipackagebar, we acknowledge that it would be good to consolidate the various options of these commands, whilst also addressing some of their inconsistencies such as the file inclusion situation documented here. Some users will no doubt find it helpful for the BAR file and deploy process to assist them moving configuration files of their own choice to the runtime system, so it is likely that more options to allow different behaviours will ultimately be the way forward. Status of the RFE is maintained as 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