Add disconnect option to ACE11 Toolkit's Integration Explorer view

Further to a new separate request being made, we have allowed https://integration-development.ideas.ibm.com/ideas/APPC-I-819 to remain open. Posting here for info for any future readers.

Thanks a lot for your quick and complete reply and the explanation regarding ressource consumption! Although there is an option to remove existing connections I don't really feel the need to either remove a connection or restart the Toolkit whenever I want to disconnect from a remote Integration Node. The disconnect will be important to me and my colleagues as I use only one workspace to administer several different environments. Disconnecting from one environment after I completed my manual administrative tasks will reduce the risk of working at an incorrect environment just because of human error. Therefore it would be nice to reconsider the button once more. Thanks a lot!

Idea / RFE Review. Thank you for taking the time to raise this enhancement request. The way in which the Toolkit communicates with the ACE runtime is significantly different in v11 (and v12) compared to earlier releases of the product. IIBv10 and earlier releases utilised the CMP API in order to communicate with the runtime, but from v11 all our admin interfaces (Toolkit, Web UI and commands ... both remotely executed and locally executed) utilise our REST API. This consistency in our architectural approach has really helped us to unify the behaviours of these different options. Local connections can use the admin REST API across a local unix domain socket / windows named pipes connection and remote connections use the admin REST API across HTTP/S. We have also found this new approach to communication does not lead to excessive resource usage, either where the toolkit is running or remotely where the runtime resides. As mentioned in the idea text, the Toolkit does offer the option for administration of remote integration servers and nodes ... but what is not mentioned (and may not be relevant to you, but could be for other readers) is that if you have local integration nodes then these are also shown in the Toolkit without the user needing to provide connection information. This is something we feel has usability benefits for users. Also of note, is that there are already options to remove remote connections which the user no longer requires (perhaps because they only needed to connect temporarily, or maybe because a mistake was made when typing in the connection info for example). Given these options, and also the fact that connections to remote servers and nodes are typically only needed when items need refreshing due to something being stopped, started or redeployed... we don't feel a separate "disconnect" option is needed in addition to the existing option to "remove" the connection, so unfortunately on this occasion we won't be pursuing this suggestion further.