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 22, 2012

All all Configurable Services + Security Identities to be reloaded without Execution Group restart.

Currently, if a security identity (i.e. something set via mqsisetdbparms) is created or modified, it requires an Execution Group restart to pick up the changes. I believe this is also true for modifications to some configurable services.

I would like to request a facility to reload all of these settings (particularly security identities) without having to restart the Execution group.

Idea priority High
RFE ID 25791
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Feb 1, 2022

    Idea / RFE Review. Support in this area has evolved further since the last update. In ACE ( you can redeploy non-dynamic policies by using the --restart-all-applications parameter on the mqsideploy or ibmint deploy command. This parameter restarts all applications on the integration server as part of the deploy operation.

  • Guest
    Oct 6, 2020

    RFE Review. Since the time when this RFE was initially raised, the IIB/ACE product architecture has evolved considerably. Configurable services have been replaced with Policies in ACEv11. Policies follow "normal" deployment rules. Most are re-deployable, but some policy changes require a server restart. We document which policies require restart, and over time we are increasing this number with an expectation that eventually all policies will be redeployable without requiring server restart. Additionally, security identities are still used as an abstraction for credential information away from the flow and / or policy. Credentials can be supplied via mqsisetdbparms still, or you can use the new v11 feature known as the credential vault, for encryption of credentials when stored. Using these new capabilities, the use case is achievable:

    1. Create vault
    2. Create credential
    3. Start integration node
    4. Deploy FTP Policy (which points at credential)
    5. Deploy Application+Flow (which points at policy)
    6. You cannot update a credential or delete a credential without reloading the integration server ... however without stopping the server you can ...
    7. Create new credential
    8. Update FTP Policy (to point at a new credential)
    9. Redeploy FTP Policy
    10. Redeploy Application+Flow (which did point at old policy, and therefore had old credential cached, but on redeploy will go to new policy and cache new credential)

    It is noted that this is only possible in this use case due to the FTP policy being redeployable, so this wouldn't work for the wider problem as posed of allowing security identities to be selectively reloaded. It is also noted that some users prefer to still use mqsisetdbparms rather than credentials. So - this requirement is still valid as a future suggestion regardless of the workaround posted above. For now, status of RFE is maintained as Uncommmitted 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

  • Guest
    Dec 21, 2012

    Thanks for raising this requirement. We spent a significant amount of time making a wide range of configurable services dynamic in V8 (including, crucially the User-Defined Configurable Service). The issue we have is that Configurable Services are fundamentally a data storage mechanism for endpoint information, and the usage of configured properties - i.e. when properties get used - is dependent on the implementation of the nodes using them, so to make all configurable services dynamic requires engineering in every underlying node. We do recognise that having these properties dynamically modifiable is desirable, and newer configurable services do tend to be completely dynamic, but there is still effort required to make these improvements across the board; but it is something we are very keen to do.
    I also understand the point that a commenter makes on refreshing properties once they have been reviewed, which I also think is a good requirement; certainly, having the option to do both - choosing when to make the property changes active - is the ideal situation.

  • Guest
    Oct 26, 2012

    All changes need to be effective only when explicitly activated and not when simply updated. This is so that co-dependent changes can be activated together as an atomic operation.

    This applies both to configurable services and credential changes. Personally I don't have a problem with mqsireload being used to perform this activation, but if another command was added which refreshed fewer things (e.g. only config services and credentials) that would be a non-disruptive enhancement.

    What I don't want to see is changes being effective immediately when made, before any opportunity to review them (list them) and check for correctness, and before other co-dependent changes are also ready.