Quantcast
Channel: VMware Communities : Discussion List - VMware {code}
Viewing all articles
Browse latest Browse all 2738

How can I control the vSphere API version?

$
0
0

We have recently upgraded to vSphere 6.0

I failed to access the vSphere 6.0 specific API calls.

According to the documentation, the property that we need to configure for enabling/disabling vSphere HA VM Component Protection service is:

ClusterDasConfigInfo.vmComponentProtecting (disabled/enabled)

This property does exist in the vSphere web services SDK/API version 6.0.2 API, however when we run the code we get an exception that says:

Method not found: 'System.String Vim25Api.ClusterDasConfigInfo.get_vmComponentProtecting()'.

After running the code with a debugger I’ve realized that dynamically the ClusterDasConfigInfo object doesn’t have the vmComponentProtecting property.

However, it does contains the vmMonitoring property and other properties of older versions of vSphere API.

 

I've suspected that, from some reason I'm using a lower API version, so I've checked the AboutInfo object.

This is what I found:

AboutInfo.apiVersion="6.0"

AboutInfo.build="5112529"

AboutInfo.sessioninfo.fullName=VMware vCenter Server 6.0.0 build-5112529

 

I've continued investigating this and I've used Fiddler tool in order to check the actual SOAP requests sent to the server.

 

This is what I came up with:

SOAPAction: "urn:vim25/5.1"

 

This means that although I'm using the vSphere 6.0 API, the actual SOAP request is of version 5.1.

 

The question is how could it be?

How can I control this?

 

This is what I've expected:

SOAPAction:urn:vim25/6.0

 

Many thanks,

Dudi.


Viewing all articles
Browse latest Browse all 2738

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>