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 Not under consideration
Workspace App Connect
Created by Guest
Created on Jun 20, 2024

RELATED IDEAS

Add optional comment when shutting down a node-owned server, and application, or message flow

During the normal course of operating a large number of applications, deployed to node owned servers, it is sometimes necessary to temporarily stop a server, application, or message flow. This might be to allow for maintenance of a backend system, or to resolve a issue causing failures, or any number of reasons.   The ask is to be able to optionally add a comment in the shutdown request that would set as a property of that resource.  When the UI displays the resource tile, for stopped resources, the comment would be displayed on the tile.  (Obviously this would likely be truncated, but the full comment would be available to view in the properties settings.)   The comment should also be included in any log messages generated by the shutdown. 

The ability to add a comment should be included as part of the UI (likely on the confirmation dialog), as an option in the REST API, and as a parameter on any relevant command line commands. 

The benefits of the enhancement would be:

  • to provide information for audit purposes, 
  • be able to communicate to other team members that might see the stopped resource and attempt to start it,
  • as a reminder as to why the resource was stopped in the first place. 

Other things to consider if this is implements:

  • Provide a means to make this mandatory either at the node or server level.  This would allow us to require a comment in production, but not in non-production.  
  • Also log the user id that requested the shut down and save as a property.  This should be done even if a comment is not provided. 



 

Idea priority Low
  • Admin
    Ben Thompson
    Reply
    |     Nov 21, 2024

    Thank you for taking the time to raise this suggestion. Unfortunately this is not something we will be pursuing as a priority right now. A similar behaviour could be achieved using a stored value in a message flow User Defined Property, which you could then edit using the ACE WebUI (under the covers this feature invokes the ACE REST API using the a method like this: /apiv2/servers/MyServer/applications/MyApp/messageflows/MyFlow/apply-global-udp-override). Message flow UDPs can also be configured to persist across server restarts if you have defined this behaviour in the server.conf.yaml as follows:


    UserVariables:

    udp-persist-global-overrides: 'true'


    We acknowledge that we could add formal description fields at multiple levels of the product's hierarchy (Node/Server/App/Flow) to carry the same information, but our fear is that different users would want many different styles of data to be stored and to make a generic solution would have high implementation cost for us and therefore not be a cost effective investment. Hopefully the suggested workaround above gives a method of meeting this use case with the product in its current form.

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.