Network Configuration

Certain network topologies and configurations require specific configuration in the server component.

Client Proxies

Code Collaborator optionally will connect to a licensing server hosted by Smart Bear via standard HTTP protocol in order to validate your license code. If you are installing Code Collaborator in an environment where outbound HTTP requests are required to use a proxy, you will need to configure Code Collaborator to use the proxy.

Proxy settings are configured in the installation-directory/ccollab-server.vmoptions file. To enable an HTTP proxy, you will need to add the following lines to that file:

-Dhttp.proxyHost=proxy_hostname

-Dhttp.proxyPort=proxy_port

-Dhttp.proxySet=true

Many proxies are configured to reject connections to internal URL's via the proxy, as these connections are supposed to be made directly. For this reason, it is also a good idea to configure internal hosts as non-proxied hosts. Specifically, it is important to configure localhost (including its resolvable name), the bug tracking system, and the version control server as non-proxied hosts. These URL's are configured in Code Collaborator for integration purposes and a connection is made to validate the URL's entered in the configuration screens. If the proxy rejects the connections, you may not be able to properly edit those fields. To configure non-proxied hosts, add the following line to the collab-server.vmoptions file:

-Dhttp.nonProxyHosts="localhost|collabserver|*.mydomain.com"

The format for the value is a list of hostnames delimited by "|" and using "*" for a wildcard.

Some newer firewalls have been known to cause additional problems with HTTP proxying. For instance, some firewalls periodically redirect HTTP requests to a firewall-generated web page requiring the user to log in. These firewalls are specifically designed to limit web access to users; preventing services (such as Code Collaborator) from accessing web services. Organizations with such firewalls will need to work with their network administrators to exempt Code Collaborator from this policy or otherwise allow access.