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 Aug 23, 2022

Remove dependency of imbint command on Eclipse .project file

At the moment, if we want to deploy a Policy project directly, that project must contain a .project file.

The .project file is Eclipse specific. The ibmint command should work without any knowledge of Eclipse. Better to use the ACE specific policy.descriptor.

This problem became apparent when deploying policies in a release pipeline. Release artifacts are stripped of development specific parts such as the .project and .svn files and files specific to unittests.

Idea priority Medium
  • Guest
    Sep 13, 2022

    Hi Ben,

    We don't (can't) add the policies in the bar file as the property values are environment dependent (test, acceptance, production have different values). The environment dependent properties are variables that are substituted in the release pipeline before being deployed. During the release the policy projects are copied to a temporary parent directory and deployed with ibmint deploy input-path. The policy.descriptor is already needed if the project only contains a monitoring profile, otherwise it is not recognized as a policy project by the runtime.

    With this setup we no longer have the need for policies per environment at build time, the environment specific properties are set in the release pipeline.

    BTW, that is great with the ibmin command, we can specify both a bar file and a directory with deployable artifacts in a single deploy command.



  • Admin
    Ben Thompson
    Sep 12, 2022

    Hi Jan, Could you please supply a detailed description of the artifacts you were using (just one policy in the policy project? Which type? Any other applications, libraries etc in the same workspace / BAR?), or an example project interchange file. Could you also specify the exact ibmint command you were executing please? The reason for requiring these details is to better understand the part of the release pipeline where you feel things are constrained by the built time file ... If you have a BAR file containing a policy then there is no need for the .project file, so my suspicion is that this use case somehow involved going direct from source to server perhaps? Or some other complicating factor? Having a more detailed specific description would enable us to comment directly on whether an enhancement is needed here.