ChrSche's Posts

Hello, is there a long term (next 5 years) plan to deprecate the SOAP API (vSphere Web Services API) in future vCenter/ESXi versions? So if I have a new project, do I rather go straight to the REST API or can I confidently build on the latest SOAP API? In addition, in the medium term (next 2 years), will the oldest supported SOAP version 4.0 (declared in SOAPAction, listed in ...vimServiceVersions.xml) no longer be supported? The question arises whether an old project/code (which uses SOAP 4.0 calls) should be adapted to version 6.0 or it is still compatible with future vCenter/iESX versions. The aim of the project/code is to read out all existing vSphere entities very deeply for the purpose of inventory. I would be very grateful for a brief assessment from the community. Thanks a lot Christian

Please delete, wrong topic. Thanks, Christian Is there a long term (next 5 years) plan to deprecate the SOAP API (vSphere Web Services API) in future vCenter/ESXi versions? So if I have a new project, do I rather go straight to the REST API or can I confidently build on the latest SOAP API? In addition, in the medium term (next 2 years), will the oldest supported SOAP version 4.0 (declared in SOAPAction, listed in ...vimServiceVersions.xml) no longer be supported? The question arises whether an old project/code (which uses SOAP 4.0 calls) should be adapted to version 6.0 or it is still compatible with future vCenter/iESX versions. The aim of the project/code is to read out all existing vSphere entities very deeply for the purpose of inventory. I would be very grateful for a brief assessment from the community. Thanks a lot Christian