Provision to Choose Perimeter Server in SSH KEY GRABBER and SSL Certificate GRABBER in UI and Exposing this service via REST API

SSH KEY Gabber and SSL Certificate Gabber utilities are primarily used by connection analysts to grab the known host keys and certificate chain. These utilities are also used to test the connectivity with the trading partner servers. Depending on the server location (internal to the enterprise or external, on the internet) they would need to choose the respective perimeter server to grab the SSH KEY and SSL Certificates. Giving this selection to the user in the respective user interface would save a lot of time and effort. The process today is really cumbersome and multiple connection analysts cannot use it at the same time, on top of it additional permissions to deployment/services menu is necessary, sometimes adjusting the adapter configuration making the adapter to go to disable state and that is causing the ICC to send an unnecessary alert to operation groups.

Partner on-boarding automation is our and our customer vision, exposing this via REST API would helps that vision.

Also, one other observation after playing with these tools. If the grabber fails the underlying BP is going to "halted" state which is an additional work for operations team to clean them from the system. As a best practice we recommend our customers to code a BP to go to "completed" state even a step fails but we don't follow the same logic in the product?