6.0

vSphere Web Services SDK Developer’s Setup Guide
30 VMware, Inc.
service mgmt-vmware restart
Example A-2. A proxy.xml File Modified To Support the SDK and the MOB
<config>
<EndpointList>
<_length>7</_length>
<_type>vim.ProxyService.EndpointSpec[]</_type>
<e id="0">
<_type>vim.Proxyservice.NamedPipeServiceSpec</_type>
<serverNamespace>/</serverNamespace>
<accessMode>httpsWithRedirect</accessMode>
<pipeName>\\.\pipe\vmware-vpxd-webserver-pipe</pipeName>
</e>
<e id="1">
<_type>vim.ProxyService.LocalServiceSpec</_type>
<serverNamespace>/sdk</serverNamespace>
<accessMode>httpAndHttps</accessMode>
<port>8085</port>
</e>
<e id="2">
<_type>vim.ProxyService.LocalServiceSpec</_type>
<serverNamespace>/ui</serverNamespace>
<accessMode>httpsWithRedirect</accessMode>
<port>8086</port>
</e>
<e id="3">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<serverNamespace>/mob</serverNamespace>
<accessMode>httpAndHttps</accessMode>
<pipeName>\\.\pipe\vmware-vpxd-mob-pipe</pipeName>
</e>
<e id="4">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<serverNamespace>/vod</serverNamespace>
<accessMode>httpsWithRedirect</accessMode>
<pipeName>\\.\pipe\vmware-vpxd-webserver-pipe</pipeName>
</e>
HTTP Configuration for vCenter Server
You can modify the reverse proxy configuration for vCenter Server using the following procedure. The
configuration file is the same as for ESX 5.0, but in a different location. For more detail about the file contents,
see “To modify the Web proxy service on ESX or ESXi 4.1 or 5.0 to support HTTP” on page 29.
N
OTE Your installation might have the configuration file in a different location, such as C:\Program
Data\VMware VirtualCenter\proxy.xml.
To modify the Web proxy service on vCenter Server 4.1 to support HTTP
1 Log in to the vCenter Server system as the Windows Administrator of the machine.
2 Change to the directory containing the proxy.xml file:
C:\Documents and Settings\AllUsers\Application Data\VMware VirtualCenter
3 Use a text editor to open the proxy.xml file.
4 Find the section of the file associated with the /sdk.
5 Change the accessMode to httpAndHttps.
6 Restart the service from a command line or from the Windows Services control panel.