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 Oct 24, 2022

Provide an option to perform a clean redeploy of a bar file using mqsibar command

As part of deployment automation, we have a requirement to deploy bars files to a set of active and passive nodes. For the deployment to nodes in running state(active), we have used the mqsideploy command to deploy the bar files For the deployment to nodes in stopped state(passive), we have used the mqsibar(unzip and go style) command to deploy the bar files It was observed that mqsibar command is unable to wipe out the contents of the unpacked application/library/policy under the Integration Server run directory when there is a change to the contents of the application/library/policy, hence, when an application/library/policy does change, the stale files in the Integration server run directory are causing the application start-up to fail
Idea priority Medium
  • Admin
    Ben Thompson
    Nov 25, 2022

    Idea Review. Thank you for taking the time to raise this enhancement request and also for the wider discussion of the other issues you have faced, which has occurred on the case you raised (TS010923894). For the benefit of clarity for other readers, we will restrict our commentary here to the specific enhancement asked for in the initial description of this idea (as opposed to the other aspects raised through TS010923894). This enhancement specifically asks for an alteration to the behaviour of the mqsibar command to inspect the contents of the provided BAR, and for each of the appzip files in the BAR, look in the existing run directory and delete the corresponding application directories first, before unzipping the new BAR file content. This has the impact of the command essentially "clearing" aspects of the existing deployed app as opposed to current behaviour which is essentially to "add" the contents of .appzip to what was previously deployed. This has been dealt with through our service channel and a fix has been provided.

    Description of the fix: "This fix is provided to address the issues that can arise when using mqsibar command to unpack a BAR directly into an Integration Server work directory that already contains a prior copy of the Application(s) or Libraries contained in the BAR. Before the fix the mqsibar command did not clear any existing contents of Application(s) or Libraries in the destination work directory it was unpacking from the BAR. This could result in old files being left that might cause issues such as duplicate ESQL, XML etc. With the fix, the mqsibar command now clears any existing Application or Library contents from the destination work directory as it unpacks the BAR so that the work directory contains only the new contents of the BAR file."

    This fix has been provided through the service channel, and it will also be included in the next release of App Connect Enterprise ( [For the benefit of IBM internal readers, useful background is provided on defect 92998]