I am trying to learn/use the Web Services SDK, but have quite a learning curve ahead of me. I want to use this for ESXi configuration for developing automaton to test our adapters.
Anyway, while I have found a lot of documentation, none of it is answering a basic question (at least for me). Where do I install the SDK? It appears that I need it on the workstation that will run the automation tests. However, does it also need to be installed on the ESXi5.5 host? Are the web APIs already on the ESXi host? The documentation uses example like this
https://your_host_ip/sdk , but that does not exist. Hence my question as to whether or not I need to install it on the host.
Thanks for any help.
Please do explore VIJAVA open source project: It is really easy to deploy and get started
1. Getting Started: http://vthinkbeyondvm.com/getting-started-with-vsphere-api-using-java/
2. Understanding Managed object Model:Using vSphere VI Java API - tutorial
3. Sample code: http://sourceforge.net/p/vijava/code/HEAD/tree/v5.1/src/com/vmware/vim25/mo/samples/
Let me know if you have any doubt or need help.
Anybody know where the SDK is installed? Does it need to be installed on ESXi host, or is it included with ESXi? The VMware documentation is clear as mud to me at this point.
For example, the manual states in Chapter 2:
"The vSphere API is a language‐neutral Web service that runs on ESX/ESXi and vCenter Server systems."
So, does that mean it is already installed? Or does it need to be installed?
I am referring to this manual.
vSphere Web Services SDK
Programming Guide
vSphere Web Services SDK 5.5
Thanks.
You're not alone. I have the same confusion reading their documentation. I suspect if somebody actually understands it, it has to be one of the authors.
If you haven't figured this out already, no, you don't need to install vSphere API. It's a web service running on the ESXi hosts. However, to use it, you need to install one of the bindings. There are ones in Java, C# and Perl, as well as Python and Ruby. The one in Perl is most developed, and the whole business of vSphere CLI is built on top of the Perl bindings.