Features Not Exposed in vSphere Client but vSphere APIs

If you think vSphere Client exposes everything, you are wrong. The vSphere APIs actually expose more features than the vSphere Client, which is a great product. This is one reason why system administrators should learn vSphere APIs.

While writing my book, for example, I noticed that vSphere APIs actually allow you to change guest OS screen size with a simple call setScreenResolution(int width, int height).

Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.

Given the time pressure, I didn’t summarize these API only features at that time. To be honest, even if I tried, there would be a big chance that I had missed quite some due to the size of vSphere APIs.

Days ago when reading the vSphere Web Service SDK Programming Guide, I found yet another good sample. On the page 116, it says:

Linked children gives better flexibility. In particular, you can create virtual applications that span clusters. The vSphere Client does not support adding or removing links, though it does show links.

To give you a little context, the linked children of a virtual application are like the linked files in Linux or shortcut files in Windows. You can use updateLinkedChildren() to change them.

I think you may also know more such features that are exposed only via APIs. Please feel free to add them in the comments.

This entry was posted in vSphere API and tagged , , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.


  1. Posted April 6, 2011 at 6:59 am | Permalink

    I used the HostNicFailureCriteria sample in several sessions. You can trigger NIC failovers on many criteria that are not available in the vSphere Client afaik.

  2. Posted April 6, 2011 at 10:49 am | Permalink

    Thanks LucD, This is a good example of partial vs. full exposure of features.

  3. Posted April 10, 2011 at 1:04 pm | Permalink

    To name a few:
    1) Custom fields for folders, networks and other objects
    2) Ability to take screenshot of VM console
    3) Timezone of ESX server

  4. Posted April 11, 2011 at 10:40 pm | Permalink

    Thanks Michael!

  5. Tejaswi
    Posted January 7, 2013 at 1:15 am | Permalink

    hey!!,i m trying to execute sample programs of vijava, but the programs containing commandline parsers are not working,
    for eg getVirtualDiskFile program is not running,its showing me

    “Exception in thread “main” java.lang.IllegalArgumentException: Exception running : java.lang.IllegalArgumentException: usage
    at com.vmware.vim25.mo.util.CommandLineParser.parseInput(CommandLineParser.java:118)
    at com.vmware.vim25.mo.util.CommandLineParser.(CommandLineParser.java:53)
    at com.vmware.vim25.mo.samples.GetVirtualDiskFiles.main(GetVirtualDiskFiles.java:28)

  6. Tejaswi
    Posted January 7, 2013 at 1:21 am | Permalink

    although its showing error at ‘task.waitForMe();’ why this is so?? i have vsphere client 5.0..

  7. Posted January 7, 2013 at 6:42 pm | Permalink

    Hi Tejaswi,
    The commandline parser is not really a key part of the APIs but for samples illustrating the usage of the APIs. Please remove it and fill in with real values in the sample code.

  8. Tejaswi
    Posted January 8, 2013 at 3:27 am | Permalink

    ok,thanx…. :)

  9. amogh
    Posted January 11, 2013 at 2:05 am | Permalink

    how to get vCenter name? uuid via vijava?

  10. amogh
    Posted January 11, 2013 at 5:33 am | Permalink

    i want to retrieve vcenter uuid, name through vijava… plz help me..:(
    what is the code for it?

Post a Comment

Your email is never published nor shared. Required fields are marked *


You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


    My company has created products like vSearch ("Super vCenter"), vijavaNG APIs, EAM APIs, ICE tool. We also help clients with virtualization and cloud computing on customized development, training. Should you, or someone you know, need these products and services, please feel free to contact me: steve __AT__ doublecloud.org.

    Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.