You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Kometter, Helmut" <He...@bitmedia.cc> on 2010/03/08 16:25:58 UTC

Problem installing wookie behind Proxy

Hi!

 

Our problem is, that our wookie-server (0.8) is running behind a proxy,
so calls to our webservices have to go through this proxy.

 

1.       To achieve this goal we modified java-vm-settings -> nothing
changed.

2.       Then we tried to modify proxy-settings in
widgetserver.properties (widget.proxy.hostname and widget.proxy.port). 
But this did not help, too.

 

Was (2.)  the right way or do we have to modify the class
ProxyClient.java like

 

Helmut

 

 


bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz

bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 147857m | ATU58011225 | Gerichtsstand Graz 

bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien

Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz


Re: AW: AW: Problem installing wookie behind Proxy

Posted by Scott Wilson <sc...@gmail.com>.
On 9 Mar 2010, at 08:43, Kometter, Helmut wrote:

> Hi,
>
> Unfortunately, I have to say that yesterday's solution was not  
> correct!
>
> Setting widget.proxy.hostname and widget.proxy.port in  
> widgetserver.properties only changes the URL that the client  
> (widget) uses for calling services on wookie.
>
> But in our case it is necessary that wookie itself uses a proxy for  
> outgoing calls.

OK, so is it that when a widget makes (say) an AJAX call, this goes to  
the Wookie proxy service, and then you need the call from the Wookie  
proxy service to the external API to go via your proxy?

If so I think you would need to edit the Wookie ProxyClient  class and  
add set the proxy address and port for the HttpClient, e.g.:

							(org.apache.wookie.proxy.ProxyClient.java, line 126)

			HttpClient client = new HttpClient();
			client.getHostConfiguration().setProxy("http://192.168.3.5", 443);

S


>
> Helmut
>
> -----Ursprüngliche Nachricht-----
> Von: Scott Wilson [mailto:scott.bradley.wilson@gmail.com]
> Gesendet: Montag, 08. März 2010 17:39
> An: wookie-dev@incubator.apache.org
> Betreff: Re: AW: Problem installing wookie behind Proxy
>
> On 8 Mar 2010, at 16:19, Kometter, Helmut wrote:
>
>> Hi,
>>
>> we recognized, that after the first start of wookie-server,
>> properties-files (widgetserver, feature...) are copied into tomcat/
>> bin-folder with names local.widgetserver.properties and so on.
>> And after this, wookie uses these copied property-files.
>> Changes in these files help us solving the problem!
>
> Great! I'm glad you got it working.
>
> Incidentally, where did you look first to find information to help you
> solve the problem? I'm wondering if I should write an FAQ entry or add
> something in one of the other documentation wiki pages about it.
>
>>
>>
>> Helmut
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Kometter, Helmut [mailto:Helmut.Kometter@bitmedia.cc]
>> Gesendet: Montag, 08. März 2010 16:26
>> An: wookie-dev@incubator.apache.org
>> Betreff: Problem installing wookie behind Proxy
>>
>> Hi!
>>
>>
>>
>> Our problem is, that our wookie-server (0.8) is running behind a
>> proxy,
>> so calls to our webservices have to go through this proxy.
>>
>>
>>
>> 1.       To achieve this goal we modified java-vm-settings -> nothing
>> changed.
>>
>> 2.       Then we tried to modify proxy-settings in
>> widgetserver.properties (widget.proxy.hostname and  
>> widget.proxy.port).
>> But this did not help, too.
>>
>>
>>
>> Was (2.)  the right way or do we have to modify the class
>> ProxyClient.java like
>>
>>
>>
>> Helmut
>>
>>
>>
>>
>>
>>
>> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054
>> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>>
>> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |
>> FN 147857m | ATU58011225 | Gerichtsstand Graz
>>
>> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,
>> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>>
>> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,
>> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz
>>
>> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054
>> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>>
>> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |
>> FN 147857m | ATU58011225 | Gerichtsstand Graz
>>
>> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,
>> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>>
>> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,
>> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz
>
> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054  
> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>
> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |  
> FN 147857m | ATU58011225 | Gerichtsstand Graz
>
> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,  
> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>
> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,  
> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz


AW: AW: Problem installing wookie behind Proxy

Posted by "Kometter, Helmut" <He...@bitmedia.cc>.
Hi,

Unfortunately, I have to say that yesterday's solution was not correct!

Setting widget.proxy.hostname and widget.proxy.port in widgetserver.properties only changes the URL that the client (widget) uses for calling services on wookie.

But in our case it is necessary that wookie itself uses a proxy for outgoing calls.

Helmut

-----Ursprüngliche Nachricht-----
Von: Scott Wilson [mailto:scott.bradley.wilson@gmail.com] 
Gesendet: Montag, 08. März 2010 17:39
An: wookie-dev@incubator.apache.org
Betreff: Re: AW: Problem installing wookie behind Proxy

On 8 Mar 2010, at 16:19, Kometter, Helmut wrote:

> Hi,
>
> we recognized, that after the first start of wookie-server,  
> properties-files (widgetserver, feature...) are copied into tomcat/ 
> bin-folder with names local.widgetserver.properties and so on.
> And after this, wookie uses these copied property-files.
> Changes in these files help us solving the problem!

Great! I'm glad you got it working.

Incidentally, where did you look first to find information to help you  
solve the problem? I'm wondering if I should write an FAQ entry or add  
something in one of the other documentation wiki pages about it.

>
>
> Helmut
>
> -----Ursprüngliche Nachricht-----
> Von: Kometter, Helmut [mailto:Helmut.Kometter@bitmedia.cc]
> Gesendet: Montag, 08. März 2010 16:26
> An: wookie-dev@incubator.apache.org
> Betreff: Problem installing wookie behind Proxy
>
> Hi!
>
>
>
> Our problem is, that our wookie-server (0.8) is running behind a  
> proxy,
> so calls to our webservices have to go through this proxy.
>
>
>
> 1.       To achieve this goal we modified java-vm-settings -> nothing
> changed.
>
> 2.       Then we tried to modify proxy-settings in
> widgetserver.properties (widget.proxy.hostname and widget.proxy.port).
> But this did not help, too.
>
>
>
> Was (2.)  the right way or do we have to modify the class
> ProxyClient.java like
>
>
>
> Helmut
>
>
>
>
>
>
> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054  
> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>
> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |  
> FN 147857m | ATU58011225 | Gerichtsstand Graz
>
> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,  
> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>
> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,  
> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz
>
> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054  
> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>
> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |  
> FN 147857m | ATU58011225 | Gerichtsstand Graz
>
> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,  
> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>
> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,  
> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz

bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz

bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 147857m | ATU58011225 | Gerichtsstand Graz 

bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien

Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz

Re: AW: Problem installing wookie behind Proxy

Posted by Scott Wilson <sc...@gmail.com>.
On 8 Mar 2010, at 16:19, Kometter, Helmut wrote:

> Hi,
>
> we recognized, that after the first start of wookie-server,  
> properties-files (widgetserver, feature...) are copied into tomcat/ 
> bin-folder with names local.widgetserver.properties and so on.
> And after this, wookie uses these copied property-files.
> Changes in these files help us solving the problem!

Great! I'm glad you got it working.

Incidentally, where did you look first to find information to help you  
solve the problem? I'm wondering if I should write an FAQ entry or add  
something in one of the other documentation wiki pages about it.

>
>
> Helmut
>
> -----Ursprüngliche Nachricht-----
> Von: Kometter, Helmut [mailto:Helmut.Kometter@bitmedia.cc]
> Gesendet: Montag, 08. März 2010 16:26
> An: wookie-dev@incubator.apache.org
> Betreff: Problem installing wookie behind Proxy
>
> Hi!
>
>
>
> Our problem is, that our wookie-server (0.8) is running behind a  
> proxy,
> so calls to our webservices have to go through this proxy.
>
>
>
> 1.       To achieve this goal we modified java-vm-settings -> nothing
> changed.
>
> 2.       Then we tried to modify proxy-settings in
> widgetserver.properties (widget.proxy.hostname and widget.proxy.port).
> But this did not help, too.
>
>
>
> Was (2.)  the right way or do we have to modify the class
> ProxyClient.java like
>
>
>
> Helmut
>
>
>
>
>
>
> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054  
> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>
> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |  
> FN 147857m | ATU58011225 | Gerichtsstand Graz
>
> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,  
> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>
> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,  
> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz
>
> bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054  
> Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz
>
> bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz |  
> FN 147857m | ATU58011225 | Gerichtsstand Graz
>
> bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311,  
> 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien
>
> Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311,  
> 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz


AW: Problem installing wookie behind Proxy

Posted by "Kometter, Helmut" <He...@bitmedia.cc>.
Hi,

we recognized, that after the first start of wookie-server, properties-files (widgetserver, feature...) are copied into tomcat/bin-folder with names local.widgetserver.properties and so on.
And after this, wookie uses these copied property-files.
Changes in these files help us solving the problem!


Helmut

-----Ursprüngliche Nachricht-----
Von: Kometter, Helmut [mailto:Helmut.Kometter@bitmedia.cc] 
Gesendet: Montag, 08. März 2010 16:26
An: wookie-dev@incubator.apache.org
Betreff: Problem installing wookie behind Proxy

Hi!

 

Our problem is, that our wookie-server (0.8) is running behind a proxy,
so calls to our webservices have to go through this proxy.

 

1.       To achieve this goal we modified java-vm-settings -> nothing
changed.

2.       Then we tried to modify proxy-settings in
widgetserver.properties (widget.proxy.hostname and widget.proxy.port). 
But this did not help, too.

 

Was (2.)  the right way or do we have to modify the class
ProxyClient.java like

 

Helmut

 

 


bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz

bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 147857m | ATU58011225 | Gerichtsstand Graz 

bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien

Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz

bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz

bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 147857m | ATU58011225 | Gerichtsstand Graz 

bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426d | ATU49978207 | Gerichtsstand Wien

Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz