Skip navigation
VMware
Up to Discussions in vSphere Web Services SDK

Developer: vSphere Web Services SDK

Develop management applications for VMware vSphere™
 

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
1,543 Views 5 Replies Last post: Mar 10, 2010 3:16 PM by akutz RSS
varun_tbd Enthusiast
varun_tbd
22 posts since
Jul 10, 2008
Currently Being Moderated

Aug 20, 2008 6:59 PM

Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

 

Hi,

 

 

I wanted to make my VI client communicate with ESX 3.5 and/or VCS 2.5 using HTTP instead of HTTPS. I have followed the instructions as given in the developers guide and changed the accessMode to httpAndHttps  for sdk and MOB in /etc/vmware/hostd/proxy.xml. I  did a service mgmt-vmware restart on the console after this. I also enabled connections from the ESX Server to the outside using "esxcfg-firewall -o 80,tcp,out,http". The Client in this case defaults to using https. I then switched to using httpOnly for the accessMode and then couldnt get in. I also tried changing the configuration of the local VI Client at C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe.config but had still was not able to connect using HTTP.

 

 

I am using WireShark on  my Desktop to find out what packets are being sent and the above three tries have either resulted in failed logins or HTTPS being used by the client.

 

 

Is it possible to force my VI Client to communicate with my ESX 3.5 or a VC 2.5 Server.If so, how can I do the same?

 

 

Thanks

 

 

Regards

 

 

Varun

 

 

 

 

 

njain Expert
njain
305 posts since
Jun 24, 2008
Currently Being Moderated
1. Aug 21, 2008 5:35 AM in response to: varun_tbd
Re: Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

 

Hi Varun,

 

 

The instructions given in the developers guide to change the access mode to enable HTTP for SDK and MOB, is to allow users to configure target servers (ESX/VC) to support regular (non-SSL) HTTP, to simplify the client-side setup, development, and testing. VI Client is the most secure access method and the target servers cannot be configured to communicate over non-SSL using VI Client.

 

 

Hope the above information helps.

 

 

Regards,

Neha

 

 

Jeff@VMTN Novice
Jeff@VMTN
14 posts since
Apr 5, 2006
Currently Being Moderated
2. Aug 21, 2008 6:17 AM in response to: njain
Re: Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

 

The VI Client has a line in its config file (VpxClient.exe.config):

 

add key = "protocolports" value = "https:443"

 

So I can use this to change the port number, but not the protocol?

 

 

It would be great to see the soap messages that the VI Client sends...it could help one figure out how data objects should be populated for certain tasks. Is there another way to do that?

 

 

Thanks.

 

 

varun_tbd Enthusiast
varun_tbd
22 posts since
Jul 10, 2008
Currently Being Moderated
3. Aug 21, 2008 8:37 PM in response to: njain
Re: Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

Hi Neha,

 

 

Thanks for the prompt response. It helps to know the target servers cannot be configured to communicate with the client using HTTP and saved me a few more hours of googling around.

 

 

Regards

 

 

Varun

varun_tbd Enthusiast
varun_tbd
22 posts since
Jul 10, 2008
Currently Being Moderated
4. Aug 21, 2008 8:35 PM in response to: Jeff@VMTN
Re: Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

Hi Jeff,

 

I had already tried changing the add key without much luck earlier. So the port number in VpxClient.exe.config can be changed but somehow not the protocol.

 

 

Thanks again.

 

 

Regards

 

 

Varun

akutz Hot Shot
akutz
337 posts since
Nov 9, 2005
Currently Being Moderated
5. Mar 10, 2010 3:16 PM in response to: varun_tbd
Re: Getting the VI Client to use HTTP to communicate with ESX3.5/VCS 2.5

Actually, this is quite possible.

Bookmarked By (0)

Communities