[Paraview] Session Manager with Apache front-end - session.map

[Bogdan Daqui Herrera]

Hi Seb,

A follow-up on this. The session map file is created and it is written
correctly, so I can say the original issue is solved. However I am still
having some problems with the rest of the setup for the following scenario:

-Apache Front-end serving a page through an SSL secured connection on
port 443.
-Jetty session manager working on the server on ports 9000-9100 (which
are of course not encrypted, but are behind the apache front-end).
-The session url is specifiend in the default-config.properties file as:
pw.factory.session.url.generator.pattern=ws://mydomain:443/proxy?sessionId=SESSION_ID

This does not work, though. There is no reaction on the browser and no
visible error message in the server logs. Changing to wss, yields a
connection which is closed instantly.

If however generate the sessionURL on port 9000 (unencrypted) the remote
browser-based paraview session works with most browsers, except Firefox,
which gives a security error due to the https-ws(unsecured socket)
combination.

My assumption is that with the Apache front-end all traffic would be
channelled through port 443 and the session manager would interact only
with it, not with the browser directly.

Thanks again for the kind replies!
Bogdan

On 26.11.2013 17:31, Sebastien Jourdain wrote:
> The answer is available in that online guide
> 
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
> 
> In this section:
> 
> |pw.factory.proxy.adapter=com.kitware.paraviewweb.external.ApacheModRewriteMapFileConnectionAdapter|
> 
> |
> 
> |pw.factory.proxy.adapter.file=/opt/apache-2.4.6/pv-mapping-file/mapping.txt|
> 
> |
> Seb
> 
> On Tue, Nov 26, 2013 at 9:22 AM, Bogdan Daqui Herrera
> <bdaqui at simscale.de <mailto:bdaqui at simscale.de>> wrote:
> 
>     Hello all,
> 
>     I am also testing a deployment of ParaviewWeb with the Apache front-end
>     and am encountering a problem with the configuration.
> 
>     The guide describing the process makes reference to the file
>     session.map, which should be generated by the session manager.
> 
>     The session manager does not generate one by default and have been
>     unable to find how and where in the settings its path can be written or
>     whether it has to be created.
> 
>     Looking through the source code of the session manager, there are two
>     classes that should generate this file: JsonFileProxyConnectionAdapter
>     and ApacheModRewriteMapFileConnectionAdapter.
> 
>     Could you please help me with a quick explanation of how to configure
>     the session manager so the session.map file is generated?
> 
>     Kind regards,
>     Bogdan Daqui
> 
>     --
>     Bogdan Daqui
>     Software Development
> 
>     SimScale GmbH
>     Lichtenbergstraße 8
>     85748 Garching bei München
> 
>     Phone: +49 (0)89 3398 4078 <tel:%2B49%20%280%2989%203398%204078>
>     Email: bdaqui at simscale.de <mailto:bdaqui at simscale.de>
> 
>     Amtsgericht München, HRB 201813
>     Geschäftsführer: Vincenz Dölle & David Heiny
> 
>     http://www.simscale.de
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
> 
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
> 
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
> 
>     Follow this link to subscribe/unsubscribe:
>     http://www.paraview.org/mailman/listinfo/paraview
> 
>