Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Mar 13, 2023

RELATED IDEAS

Integration servers' startup order

The integration servers are started in the order they appear in the <workpath>/components/<broker>/repository/brokeraaeg.dat file.

The integration nodes are also started in the background (the integration node does not wait for an integration server to start completely when starting the next one).

It would be a good idea if one could specify the startup order of each integration server in an integration node, and also configure dependencies between integration nodes, for example: integration server B starting after integration server A has completely started.

The shutdown order should also be configurable, but by default, it can be the same as the startup order in reverse.
If using integration servers' dependencies, the shutdown order would be one that would stop dependent integration servers before the ones they are dependent on.

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |     May 23, 2023

    Idea review. Thank you for taking the time to raise this idea for enhancement, which we have discussed and on balance of our considerations we are placing into the status of Future Consideration. On this occasion, this decision indicates that we would not necessarily be against the idea in conceptual terms, and also empathise that for a small proportion of our users we understand this suggestion could bring some fringe benefits for particular scenarios ... However we would also note that currently this topic would be of a low business priority for us and so is unlikely to receive attention soon. We would be particularly keen to hear from our users to better understand the specific use cases where this potential feature could be of value. We're aware of historical situations regarding port conflicts and the global cache which have in the past led to similar suggestions, but we weigh this kind of situation against the general trend of the desirability of container architectures where there is no burned-in dependency between separate runtime processes which can bring agile advantages to not have this kind of cross-dependency baked into their behaviours.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.