How can I run xTIMEcomposer Studio behind a proxy server? Topic is solved

If you have a simple question and just want an answer.
User avatar
sethu_jangala
XCore Expert
Posts: 589
Joined: Wed Feb 29, 2012 10:03 am

How can I run xTIMEcomposer Studio behind a proxy server?

Post by sethu_jangala »



View Solution
User avatar
kris
Experienced Member
Posts: 84
Joined: Mon Jan 18, 2010 2:52 pm

Post by kris »

It depends on the version of the tools you are running.

VERSION: 11.11.1
-------------------------

In this version registration is not compulsory, so when presented with the
registration dialog, just press cancel and you will be able to use the tools
offline. However, some aspects of the tools are delivered from xmos.com, so it
still might be beneficial to configure the tools to work from behind a proxy
server. See the 'Setting Manually' section below for details on how to do
this.

VERSION: 12.2.0
------------------------

If you are opening the tools for the first time and are behind a proxy server,
then you can use the 'Configure proxy server settings' link on the registration
dialog. However, if you have already registered your tools, but find yourself
behind a proxy server at a later date, then the settings can be found here:
Window->Preferences->General->Network Connections.

VERSION: 13.x.x and higher
-----------------------------------

If you are opening the tools for the first time and are behind a proxy server,
then you can use the 'Having problems registering' link on the registration
dialog. On the resulting popup, the 'Configure proxy server settings' link will
take you to the required configuration page. However, if you have already
registered your tools, but find yourself behind a proxy server at a later date,
then the settings can be found here: Window->Preferences->General->Network
Connections.

Setting Manually
---------------------

The proxy settings need to be set in 3 places:

1) In the JVM:
-------------------

At the end of the following file:

On windows: xtimecomposer_bin\xtimecomposer.ini
On mac:     xtimecomposer_bin/xtimecomposer.app/Contents/MacOS/xtimecomposer.ini
On linux:   xtimecomposer_bin/xtimecomposer.exe.ini

These lines need to be inserted.
(Note: it must be after the '-vmargs' line):

-Dhttp.proxyHost=<proxy server name>
-Dhttp.proxyPort=<proxy server port>
-Dhttps.proxyHost=<proxy server name>
-Dhttps.proxyPort=<proxy server port>

Where <proxy server name> and <proxy server port> are filled in as required.

Note: If authentication is required, the following 2 properties can also be
set in the same place:

-Dhttp.proxyUser=<username>
-Dhttp.proxyPassword=<password>

2) In the xTIMEcomposer:
-------------------

Locate the 'configuration' directory for the xTIMEcomposer installation.
In general, this directory can be found at '<tools install path>/xtimecomposer_bin',
where <tools install path> is the location where you installed the XMOS
development tools. However, on windows 7 and 8, the configuration directory will be
found inside a '.eclipse' folder in your user area, for example,
C:/Users/kris/.eclipse/org.eclipse.platform_3.6.1_972445210/configuration/

You'll need to put the following lines in the
'xtimecomposer_bin/configuration/.settings/org.eclipse.core.net.prefs' file:

systemProxiesEnabled=false
proxyData/HTTP/host=<host>
proxyData/HTTP/hasAuth=false
proxyData/HTTP/port=<port>
proxyData/HTTPS/host=<host>
proxyData/HTTPS/hasAuth=false
proxyData/HTTPS/port=<port>

Where <host> and <port> are replaced by the relevant settings.
(Just create the file if it doesn't already exist).

3) In the xTIMEcomposer developer column:
-----------------

Windows:
======
The browser in the Developer Column uses the Windows' global proxy settings.
These settings can be changed at any time in the Windows Control Panel.

OS X:
======
The browser in the Developer Column uses OS X's global proxy settings. These
settings can be changed at any time in the OS X System Preferences.

Linux:
======
Proxy information must be explicitly specified by setting
values for java properties network.proxy_host and network.proxy_port.
These can be set in the *.ini file, same as in case (1)

-Dnetwork.proxy_host=<host>
-Dnetwork.proxy_port=<port>