Hi jack
We always have been told by our internal DataPower expertise that you can only configure « isam » objects from DataPower UI, and not unconfigure them.
( In ISAM 7, it forced us to cleanup traces of DataPower objects in ISAM master authz db in a non trivial way involving exporting it, delete DataPower objects and then re-import, followed by deamons dn entries cleanup as well in the user registry. Very chirurgical and worrying so we would not always do it, recreating DataPower ISAM new objects using new service names each time ).
But you provide good insight that yes, the delete button is meant to be enabled only when the remote objects are not reachable (showing as red).
Thanks
Sylvain
Sylvain Gilbert, p. ing., Conseiller Technique Infrastructures Securité/Security Infrastructures Technical Advisor
Intact Corporation Financière | 1935 des Cascades, Saint-Hyacinthe, QC J2S 8K9
(T) 855.646.8228, x 86667 | (M) 450.223.9537
------Original Message------
Hello Sylvain,
So in my lab I had a Reverse Proxy instance that was started.
I went to the 'Server Cleanup' menu and when it shows green the delete button was greyed out.
Then, when I stopped my server it showed 'red' and I had the ability to delete.
The determining factor is whether the Policy Server can reach the Administration port.
You can see the administration port by running `server show <servername>`
The issue with deleting the server definition as opposed to performing an unconfigure and reconfigure is that if there are artifacts left on the Client the Certificate or other important 'Server' related objects may not be created as expected.
Is there any reason why you cannot use the Datapower interface to perform an unconfiguration and reconfiguration?
------------------------------
JACK YARBOROUGH
------------------------------