Proxy Settings for XOG

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Question: 

We have a problem using XOG while we have a proxy enabled.  How can we configure XOG to take into account the proxy parameters? 
 

Environment:  

All versions of CA PPM/CA Clarity.

 

Answer: 

You need to set the following JVM parameters in the xog.bat file in the Xog Client folder:

" proxySet=true - Proxy is enabled.
" https.proxyHost=<proxy host> - If you are connecting to an HTTPS Clarity instance, this property is used.
" https.proxyPort=<proxy port, usually 443> - If you are connecting to an HTTPS Clarity instance, this property is used.
" http.proxyHost=<proxy host> - If you are connecting to an HTTP Clarity instance, this property is used.
" http.proxyPort=<proxy port, usually 80> - If you are connecting to an HTTP Clarity instance, this property is used.

1. Use a text editor like NotePad, Wordpad, Note Pad ++, ... to edit your xog.bat file.

2. Search for "-Dniku.home". This will take you to the write command lines to make these changes.

3. If your command line looks like this:

set PROGRAM_ARGS=%SSL_DEBUG_ARG% -Dfile.encoding=UTF-8 -Xmx512m -Dniku.home="%NIKU_HOME%" -Dforehead.conf.file="%NIKU_HOME%\bin\xog.forehead" com.werken.forehead.Forehead -installDir "%NIKU_HOME%"

NOTE: Depending on your version of Clarity/Xog Client, your command line may be slightly different. But, the idea is the same. Add the proxy information after the -Xmx setting and before the -Dniku.home setting.

Change it to this:

set PROGRAM_ARGS=%SSL_DEBUG_ARG% -Dfile.encoding=UTF-8 -Xmx512m -DproxySet=true -Dhttp.proxyHost=yourproxyhostname -Dhttp.proxyPort=80 -Dniku.home="$NIKU_HOME" -Dforehead.conf.file="$NIKU_HOME/bin/xog.forehead"  com.werken.forehead.Forehead -installDir "$NIKU_HOME"

NOTE: Change the proxy host name and ports to the correct ones for your network.

Environment

Release: ESPCLA99000-13.2-Clarity-Extended Support Plus
Component: