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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Idea / RFE Review. Apologies for the length of time this suggestion has been held in the status of Future Consideration. Whilst attention is increasingly applied to container based architectures (where typically the power of the container platform is utilised in tearing down and restarting containers without interrupting service using a blue-green deployment model) we still very much also acknowledge the importance for non-container environments, of being able to change configuration dynamically without requiring a restart. There are several examples of changes in these areas, which also take note of some of the comments on this idea ...
ACE v11.0.0.9 introduced new operations in the administrative REST API for the dynamic reload of certificates for the HTTPS Listener. When receiving secured inbound connections over HTTPS, integration servers use one of their components called the HTTPS Connector resource manager. Several HTTPS Connector resource manager properties can now be updated without requiring a restart, using these new REST API methods: KeyAlias, KeystoreFile, KeystorePassword, KeystoreType, TruststoreFile, TruststorePassword, TruststoreType
Being able to dynamically update these properties, and the KeystoreFile property in particular, is useful in the situation where you are using certificate authorities that refresh their certificates on a frequent basis but you do not want to restart the integration server whenever the refresh occurs. You can also reuse the same keystore file but with a different value for the server security certificate to refresh the server certificate to be used by the integration server without having to restart the integration server.
Another example in this area was ACE v12.0.2.0 which introduced the ability to apply mqsichangefileauth changes dynamically without needing a restart. In previous versions of App Connect Enterprise, it was necessary to restart the integration node in order for authorization changes to be applied. For example adding new permissions for a particular integration server required the whole integration node to be restarted in order to pick up changes, which had a much wider operational impact than necessary. To rectify this situation, with ACE 12.0.2.0 a new property was added to the node.conf.yaml file to drive an integration node's behaviour to be dynamic in this regard.
Given this progress, and the length of time this RFE has been open, we feel justified in marking this one as delivered, but if there are specific properties or further areas of ACE behaviour which readers feel would benefit from being made more dynamic then please feel free to raise a new specific idea for consideration.
Equally true for keystore changes, these also need int.node or int.server restart.
Thanks for raising this RFE, which we agree would make a good enhancment for the product. Status of the RFE is updated to Uncommitted Candidate.
This is a common issue and need urgent attention from Hursley