You can change the security configuration so that individual services are directly accessible through HTTP connections.

1

Use the vifs command to get a copy of the proxy.xml file to edit.

For Linux systems, use this command.

vifs --server <hostname> --username <username> --get /host/proxy.xml <directory>/proxy.xml

For Windows systems, use this command.

vifs --server <hostname> --username <username> --get /host/proxy.xml <directory>\proxy.xml
Caution

If this file is changed to an incorrect configuration, the system might enter an unmanageable state. You might be required to perform a factory reset using the direct console.

2

Use a text editor to open the proxy.xml file.

The contents of the file typically appears as follows.

<ConfigRoot>
<EndpointList>
<_length>6</_length>
<_type>vim.ProxyService.EndpointSpec[]</_type>
<e id="0">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<accessMode>httpsWithRedirect</accessMode>
<pipeName>/var/run/vmware/proxy-webserver</pipeName>
<serverNamespace>/</serverNamespace>
</e>
<e id="1">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<accessMode>httpsWithRedirect</accessMode>
<pipeName>/var/run/vmware/proxy-sdk</pipeName>
<serverNamespace>/sdk</serverNamespace>
</e>
<e id="2">
<_type>vim.ProxyService.LocalServiceSpec</_type>
<accessMode>httpsWithRedirect</accessMode>
<port>8080</port>
<serverNamespace>/ui</serverNamespace>
</e>
<e id="3">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<accessMode>httpsOnly</accessMode>
<pipeName>/var/run/vmware/proxy-vpxa</pipeName>
<serverNamespace>/vpxa</serverNamespace>
</e>
<e id="4">
<_type>vim.ProxyService.NamedPipeServiceSpec</_type>
<accessMode>httpsWithRedirect</accessMode>
<pipeName>/var/run/vmware/proxy-mob</pipeName>
<serverNamespace>/mob</serverNamespace>
</e>
<e id="5">
<_type>vim.ProxyService.LocalServiceSpec</_type>
<!-- Use this mode for "secure" deployment -->
<!-- <accessMode>httpsWithRedirect</accessMode> -->
<!-- Use this mode for "insecure" deployment -->
<accessMode>httpAndHttps</accessMode>
<port>8889</port>
<serverNamespace>/wsman</serverNamespace>
</e>
</EndpointList>
</ConfigRoot>
3

Change the security settings as required.

For example, you might want to modify entries for services that use HTTPS to add the option of HTTP access.

<e id> is an ID number for the server ID XML tag. ID numbers must be unique within the HTTP area.

<_type> is the name of the service you are moving.

<accessmode> is the forms of communication the service permits. Acceptable values include:

httpOnly – The service is accessible only over plain-text HTTP connections.

httpsOnly – The service is accessible only over HTTPS connections.

httpsWithRedirect – The service is accessible only over HTTPS connections. Requests over HTTP are redirected to the appropriate HTTPS URL.

httpAndHttps – The service is accessible both over HTTP and HTTPS connections.

<port> is the port number assigned to the service. You can assign a different port number to the service.

<serverNamespace> is the namespace for the server that provides this service, for example /sdk or /mob.

4

Save your changes and close the file.

5

Use the vifs command to put a copy of the proxy.xml file on the ESXi host.

For Linux, use this command.

vifs --server <hostname> --username <username> --put <directory>/proxy.xml /host/proxy.xml

For Windows, use this command.

vifs --server <hostname> --username <username> --put <directory>\proxy.xml /host/proxy.xml
6

Use the Restart Management Agents operation through the direct console to have the settings take effect.