<div dir="ltr">I'm not sure to follow everything here, but you should be able to call a method to refresh the pipeline.<div>In fact, you can exercise it by clicking on the "server" icon of the pipeline browser.</div>
<div><br></div><div>Seb</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 5, 2013 at 12:06 PM, Bogdan Daqui Herrera <span dir="ltr"><<a href="mailto:bdaqui@simscale.de" target="_blank">bdaqui@simscale.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Seb,<br>
<br>
Thanks for the reply.<br>
<br>
One new follow-up on the transition to the latest revision.<br>
<br>
I have written a new openFile method in protocols.py which uses some<br>
custom python code to get a reader object. This reader object is then<br>
returned by my new openFile method.<br>
<br>
The openFile method is subsequently called from within javascript code<br>
in a similar manner as vtk:getPipeline is called in the Visualizer demo app.<br>
<br>
The idea being that a file will be open depending on some parameters,<br>
without having to browse through a list. Also, the client most not know<br>
any information concerning the actual path of the file.<br>
<br>
The problem I currently have is that the proxy object is not being<br>
automatically added to the pipeline browser. I can print the contents to<br>
the browser console and seems fine.<br>
<br>
Could you give please give me some hints on how to proceed?<br>
<br>
Kind regards,<br>
Bogdan<br>
<div class="im HOEnZb"><br>
On 04.12.2013 02:19, Sebastien Jourdain wrote:<br>
> Sorry to catch up so late but the possible reason why it was not working<br>
> before was the file generated does not have the same format.<br>
><br>
> Seb<br>
><br>
><br>
> On Tue, Dec 3, 2013 at 1:07 PM, Bogdan Daqui Herrera <<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a><br>
</div><div class="im HOEnZb">> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>> wrote:<br>
><br>
> Hi Sebastian,<br>
><br>
> I have switched to Apache-2.4.7 and used the second configuration, as<br>
> you recommended. It works now exactly as expected.<br>
><br>
> Thanks for the help!<br>
> Bogdan<br>
><br>
> On 03.12.2013 15:55, Sebastien Jourdain wrote:<br>
> > Are you using Apache 2.4+ ? There is 2 ways to do web socket<br>
> forwarding<br>
> > with Apache.<br>
> ><br>
> ><br>
> <a href="http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup" target="_blank">http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup</a><br>
> ><br>
> > and<br>
> ><br>
> ><br>
> <a href="http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2" target="_blank">http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2</a><br>
> ><br>
> > But I would recommend the second one if you can choose.<br>
> ><br>
> > Seb<br>
> ><br>
> ><br>
> > On Tue, Dec 3, 2013 at 7:26 AM, Bogdan Daqui Herrera<br>
> <<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>><br>
</div><div class="HOEnZb"><div class="h5">> > <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>>> wrote:<br>
> ><br>
> > Hi Seb,<br>
> ><br>
> > A follow-up on this. The session map file is created and it is<br>
> written<br>
> > correctly, so I can say the original issue is solved. However<br>
> I am still<br>
> > having some problems with the rest of the setup for the following<br>
> > scenario:<br>
> ><br>
> > -Apache Front-end serving a page through an SSL secured<br>
> connection on<br>
> > port 443.<br>
> > -Jetty session manager working on the server on ports<br>
> 9000-9100 (which<br>
> > are of course not encrypted, but are behind the apache front-end).<br>
> > -The session url is specifiend in the<br>
> default-config.properties file as:<br>
> ><br>
> pw.factory.session.url.generator.pattern=ws://mydomain:443/proxy?sessionId=SESSION_ID<br>
> ><br>
> > This does not work, though. There is no reaction on the<br>
> browser and no<br>
> > visible error message in the server logs. Changing to wss,<br>
> yields a<br>
> > connection which is closed instantly.<br>
> ><br>
> > If however generate the sessionURL on port 9000 (unencrypted)<br>
> the remote<br>
> > browser-based paraview session works with most browsers,<br>
> except Firefox,<br>
> > which gives a security error due to the https-ws(unsecured socket)<br>
> > combination.<br>
> ><br>
> > My assumption is that with the Apache front-end all traffic<br>
> would be<br>
> > channelled through port 443 and the session manager would<br>
> interact only<br>
> > with it, not with the browser directly.<br>
> ><br>
> > Thanks again for the kind replies!<br>
> > Bogdan<br>
> ><br>
> > On 26.11.2013 17:31, Sebastien Jourdain wrote:<br>
> > > The answer is available in that online guide<br>
> > ><br>
> > ><br>
> ><br>
> <a href="http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2" target="_blank">http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2</a><br>
> > ><br>
> > > In this section:<br>
> > ><br>
> > ><br>
> ><br>
> |pw.factory.proxy.adapter=com.kitware.paraviewweb.external.ApacheModRewriteMapFileConnectionAdapter|<br>
> > ><br>
> > > |<br>
> > ><br>
> > ><br>
> ><br>
> |pw.factory.proxy.adapter.file=/opt/apache-2.4.6/pv-mapping-file/mapping.txt|<br>
> > ><br>
> > > |<br>
> > > Seb<br>
> > ><br>
> > > On Tue, Nov 26, 2013 at 9:22 AM, Bogdan Daqui Herrera<br>
> > > <<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>><br>
> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>><br>
> > <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>><br>
> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>>>> wrote:<br>
> > ><br>
> > > Hello all,<br>
> > ><br>
> > > I am also testing a deployment of ParaviewWeb with the<br>
> Apache<br>
> > front-end<br>
> > > and am encountering a problem with the configuration.<br>
> > ><br>
> > > The guide describing the process makes reference to the file<br>
> > > session.map, which should be generated by the session<br>
> manager.<br>
> > ><br>
> > > The session manager does not generate one by default and<br>
> have been<br>
> > > unable to find how and where in the settings its path can be<br>
> > written or<br>
> > > whether it has to be created.<br>
> > ><br>
> > > Looking through the source code of the session manager,<br>
> there<br>
> > are two<br>
> > > classes that should generate this file:<br>
> > JsonFileProxyConnectionAdapter<br>
> > > and ApacheModRewriteMapFileConnectionAdapter.<br>
> > ><br>
> > > Could you please help me with a quick explanation of how to<br>
> > configure<br>
> > > the session manager so the session.map file is generated?<br>
> > ><br>
> > > Kind regards,<br>
> > > Bogdan Daqui<br>
> > ><br>
> > > --<br>
> > > Bogdan Daqui<br>
> > > Software Development<br>
> > ><br>
> > > SimScale GmbH<br>
> > > Lichtenbergstraße 8<br>
> > > 85748 Garching bei München<br>
> > ><br>
> > > Phone: <a href="tel:%2B49%20%280%2989%203398%204078" value="+498933984078">+49 (0)89 3398 4078</a><br>
> <tel:%2B49%20%280%2989%203398%204078><br>
> > <tel:%2B49%20%280%2989%203398%204078><br>
> > <tel:%2B49%20%280%2989%203398%204078><br>
> > > Email: <a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>><br>
> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>><br>
> > <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>><br>
> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a> <mailto:<a href="mailto:bdaqui@simscale.de">bdaqui@simscale.de</a>>>><br>
> > ><br>
> > > Amtsgericht München, HRB 201813<br>
> > > Geschäftsführer: Vincenz Dölle & David Heiny<br>
> > ><br>
> > > <a href="http://www.simscale.de" target="_blank">http://www.simscale.de</a><br>
> > > _______________________________________________<br>
> > > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a> <<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>><br>
> <<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>><br>
> > <<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>><br>
> > ><br>
> > > Visit other Kitware open-source projects at<br>
> > > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> > ><br>
> > > Please keep messages on-topic and check the ParaView<br>
> Wiki at:<br>
> > > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
> > ><br>
> > > Follow this link to subscribe/unsubscribe:<br>
> > > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
><br>
</div></div></blockquote></div><br></div>