VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
2 Replies Last post: Aug 31, 2009 12:52 AM by storm27  

Difference between APIs / SDKs and their purpose posted: Aug 18, 2009 3:09 AM

Click to view d0se's profile Novice 4 posts since
Mar 10, 2009
Hi!
I have a vSphere environment running and i'm just starting out with the vSphere APIs and SDKs in C#. So i startet reading with Getting Started with vSphere SDKs and downloaded the SDK and API packages.

First i got PowerCLI with the vSphere SDK for .NET and read through the vSphere SDK for .NET developer's guide. Then i downloaded the vSphere web services SDK package, compiled the samples and dlls and am now reading through the programming guide.
But still the overview which API/SDK is best for what and how to use it is missing.

Am i right in the assumption, that both vSphere SDK and vSphere Web Services SDK depend on vSphere API which is available on each ESX host?
I found the vSphere API reference but it seems to me that both, samples from webservices SDK and vSphere SDK, use the same objects and methods from vSphere API directly.
The only difference i found out is, that the web services examples use AppUtil which again uses vSphere API but vSphere SDK doesn't. Is that right and where is the advantage in using one of the SDKs instead of vSphere API? In case of using web services SDK, have i to use the AppUtil out of the samples?

So you see, i'm a bit confused by the possibilities and usage. Especially the difference between vSphere SDK and vSphere Web Services SDK is not clear to me.
Can you help me by summarizing briefly the differences and purposes of those packages? Or is there a good document which treats that topic?

Thanks and regards
Patrick

Re: Difference between APIs / SDKs and their purpose

1. Aug 20, 2009 10:55 PM in response to: d0se
Click to view tos2k's profile Expert 307 posts since
May 11, 2007
Hi!

I agree on that these SDKs provide similar functionality. The might have some (dis-)advantages concerning usability and programming (dis-)likes.
Concerning the question according to ESX: VimSDK gives you access to both, functionality provided by ESX and provided by vCenter. It is the same SOAP based interface.
Connecting to an ESX will give you access to functionality provided by ESX, which is less functionality than found on vCenter. A single ESC does f.e. not provide Cluster or Clone functionality, but vCenter does.

Tos2k

Re: Difference between APIs / SDKs and their purpose

2. Aug 31, 2009 12:52 AM in response to: d0se
Click to view storm27's profile Enthusiast 41 posts since
May 4, 2009

Hi,

You are absolutely right in saying that both vSphere SDK and vSphere Web Services SDK depend on vSphere API.

Just to clear out your confusion, both vSphere SDK and vSphere Web Services SDK are logically same, there's no difference between them.

vSphere SDK uses Web Services as the underlying technology/channel to manage the whole virtual infrastructure.This management is achieved by using vSphere APIs,formerly called VI APIs, which are exposed as web services, running on each ESX system.

For better understanding of vSphere Web Services SDK, refer to the readme html doc shipped with the SDK package.

Hope this will help to clear out your confusion!

Thanks.

Angela

Developer Social Media

Communities