Embotics® vCommander® allows administrators to manage both local hypervisors and public clouds. When managing public clouds, vCommander must be able to reach the Internet, so additional configuration is required if a proxy server is in use on the network.


vCommander 5.3 and later includes a native setting for configuring connections to Amazon Web Services via a proxy server, but for older versions or Azure connections Java system properties are used to specify the details about the proxy server. You will also have to replace one of the java archives before the system properties will function correctly. This article provides the details on how to accomplish this.


Updating the Java Archive 


 Follow the procedure below to update the java archive.

  1. On the vCommander application server, stop the vCommander Windows service.
  2. Make a backup of the file \<Install Directory>\Embotics\vCommander\tomcat\lib\aws-sdk-java-1.9.2.jar.

    in another location. Overwrite the original with a copy you extract from the zip you download here.

  3. Restart the vCommander Windows service.


System Properties Related to Proxy Servers


The following system properties are available to modify how Embotics vCommander connects to the Internet via a proxy server. Refer to the section appropriate for your proxy server, or contact support@embotics.com.


HTTP

The following proxy settings are used by the HTTP protocol handler.

  • http.proxyUsername The account username used to connect to the proxy server, if required.
  • http.proxyPassword The account password used to connect to the proxy server, if required.
  • http.proxyDomain The account Domain used to connect to the proxy server, if required (when using NTLM authentication).
  • http.proxyWorkstation The hostname or address of the vCommander server, if required (when using NTLM authentication).
  • http.proxyHost Defines the hostname or address of the proxy server.
  • http.proxyPort (default: 80) Defines the TCP port used to establish HTTP connections to the proxy server.
  • http.nonProxyHosts Defines the hosts that should be accessed without going through the proxy. Typically you will use this to define internal hosts, which is important because vCommander will make connections to local hypervisors and integration systems that you don’t want going through your proxy. The value of this property is a list of hosts, separated by the pipe “|” character. For example: -Dhttp.nonProxyHosts="*.embotics.com|localhost" indicates that every host in the embotics.com domain and localhost should be accessed directly, even if a proxy server is specified. You must make sure that you are using the same host name for connections that were used when connecting them to vCommander.

HTTPS

This is HTTP over SSL, a secure version of HTTP mainly used when confidentiality (like on payment sites) is needed. Most public cloud connections will occur over HTTPS.

  • https.proxyUsername The account username used to connect to the proxy server, if required.
  • https.proxyPassword The account password used to connect to the proxy server, if required.
  • https.proxyDomain The account Domain used to connect to the proxy server, if required (when using NTLM authentication).
  • https.proxyWorkstation The hostname or address of the vCommander server, if required (when using NTLM authentication).
  • https.proxyHost Defines the hostname or address of the proxy server.
  • https.proxyPort (default: 443) Defines the TCP port used to establish HTTP connections to the proxy server.

SOCKS

This is another type of proxy. It allows for lower level type of tunneling since it works at the TCP level. In effect, in the Java™ platform setting a SOCKS proxy server will result in all TCP connections to go through that proxy, unless other proxies are specified. If SOCKS is supported by a Java SE implementation, the following properties will be used:

  • socksProxyHost The hostname, or address, of the proxy server.
  • socksProxyPort (default: 1080) The port number of the proxy server.
  • socksProxyVersion The version of the SOCKS protocol supported by the server. The default is 5 indicating SOCKS V5, alternatively 4 can be specified for SOCKS V4. Setting the property to values other than these leads to unspecified behavior.
  • java.net.socks.username Username to use if the SOCKSv5 server asks for authentication and no java.net.Authenticator instance was found.
  • java.net.socks.password Password to use if the SOCKSv5 server asks for authentication and no java.net.Authenticator instance was found.

 

Setting System Properties


To configure one or more of the system properties listed above, follow the procedure below.

  1. Login to the Embotics vCommander server and browse to <INSTALL_DIR>\Embotics\vCommander\tomcat\bin\.
  2. Launch vlmw.exe as an Administrator.

  3. If prompted by Windows, choose to allow this program to make changes to the computer by clicking Yes.


  4. On the General tab, click Stop to to stop the vCommander Windows service.

  5. Switch to the Java tab, and add lines for each selected system property you want to configure to the Java Options field. Each line is begun with -D, then the system property, then an equals sign followed by the value. No spaces are used, and none can trail. To set 10.10.10.59 as the address for the HTTP proxy server,  the line to add would be:

    -Dhttp.proxyHost=10.10.10.59

  6. Click Apply.
  7. Switch back to the General tab and click Start to start the vCommander Windows service.

Troubleshooting


If you encounter any issues, please turn up the logging for AWS connections using this debug line:


log4j.logger.com.amazonaws.request=INFO


along with the instructions you find in the article Controlling Embotics vCommander Logging Level.