[Paraview] headless paraview installation

Wed May 2 13:29:24 EDT 2012

Thank Cagatay for your feedback,

I'll update the wiki.
For the point 4: we do have a super build now that automate all that
process and the point of that documentation was to illustrate each
pieces independently from each other instead of explaining the setup
for a monolithic system. But I agree this can be confusing, that's why
I finally wrote the super build that basically build everything for
you as well as fetching the third party.

Seb

On Wed, May 2, 2012 at 12:43 PM, Cagatay Bilgin <bilgincc at gmail.com> wrote:
> http://paraview.org/Wiki/ParaViewWeb_Building
>
> 1) There is no field CORE_SERVICE_URL
>  CORE_SERVICE_URL           http://localhost:8080/PWService     <---- Use
> the deployment address otherwise the sample
>
> 2) The following fields have different names. This was not that hard to
> figure anyway.
>
> JAVA_ARCHIVE               /opt/jdk1.6.0_18/bin/jar
>   JAVA_RUNTIME               /opt/jdk1.6.0_18/bin/java
>   JAVA_COMPILE               /opt/jdk1.6.0_18/bin/javac
>
>
> 3) ParaviewAdapter and PWServer used interchangeable, which confused me.
>
> 4) All the components (PWAdapter, PWService, PWApp, PWConsole) are being
> installed to the same directory install-pw. I am not sure why one
> needs to do these one by one, when we have cmake. This process could
> possiblly be automated.
>
>
>
> http://paraview.org/Wiki/ParaViewWeb_with_system_tomcat_package
>
> 5) The following fields should be filled as well
> OPENGL_INCLUDE_DIR
> OPENGL_glu_LIBRARY
> OPENGL_xmesa_INCLUDE_DIR   OPENGL_xmesa_INCLUDE_DIR-NOTFOUND
>
> however OPENGL_gl_LIBRARY should be left empty. This is reported in
> one of the kitware forums. I guess it was vtk issue tracker.
>
> The last issue that I remember is that, Paraview was trying to run
> PWServer from / directory. Not sure why, but we had to put a link
> there.
>
> Cagatay
>
> On Tue, May 1, 2012 at 7:15 PM, Sebastien Jourdain
> <sebastien.jourdain at kitware.com> wrote:
>>
>> Glad to hear that you solved your problem.
>>
>> And please share your "hacks" if you think they could be useful to
>> other or if something can be improved in ParaViewWeb itself...
>>
>> Thanks,
>>
>> Seb
>>
>> On Tue, May 1, 2012 at 8:49 PM, Cagatay Bilgin <bilgincc at gmail.com> wrote:
>> > Using the latest ParaView solved the problem.
>> > We were using 3.12 before. There were quite
>> > a few hacks that we had to do to get things working.
>> >
>> > It is a joy to watch once things start rolling :)
>> >
>> > Cagatay
>> >
>> >
>> > On Tue, May 1, 2012 at 3:39 PM, Sebastien Jourdain
>> > <sebastien.jourdain at kitware.com> wrote:
>> >>
>> >> I've posted it on the mailing list, but as I followed the thread,
>> >> Goodwin end-up being in the to: and not you...
>> >>
>> >>
>> >> ---------- Forwarded message ----------
>> >> From: Sebastien Jourdain <sebastien.jourdain at kitware.com>
>> >> Date: Tue, May 1, 2012 at 6:37 PM
>> >> Subject: Re: [Paraview] headless paraview installation
>> >> To: Goodwin Lawlor <goodwin.lawlor.lists at gmail.com>
>> >> Cc: paraview at paraview.org
>> >>
>> >>
>> >> Hi guys,
>> >>
>> >> the WebGL export need to be requested by the client. Is the issue
>> >> happening with the sample applications or with a custom one ?
>> >> Do you know if switching back to another render just work or as
>> >> Goodwin suggested a segfault occurred ?
>> >> You can look at the log files in the working.dir/logs/pw-xxxx.log
>> >>
>> >> Moreover, which version of ParaView are you using ? 3.14.1 ?
>> >>
>> >> Seb
>> >>
>> >> On Tue, May 1, 2012 at 4:52 PM, Goodwin Lawlor
>> >> <goodwin.lawlor.lists at gmail.com> wrote:
>> >> > Hi Cagatay,
>> >> >
>> >> > What version of PVW are you using?
>> >> >
>> >> > I installed PVW on a headless AWS server last Aug and WebGL rendering
>> >> > wouldn't work because of a bug
>> >> > in  vtkPVSynchronizedRenderWindows::GetIsInCave()
>> >> >
>> >> > To fix the bug, just replace the method body with "return false;"
>> >> >
>> >> > I would think that the bug has been fixed in a release version since
>> >> > then
>> >> > though.
>> >> >
>> >> > Goodwin
>> >> >
>> >> > On Tue, May 1, 2012 at 7:55 PM, Cagatay Bilgin <bilgincc at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> We are interested in using paraviewweb in
>> >> >> our lab and integrate it with the segmentation
>> >> >> tools we are developing.
>> >> >>
>> >> >> We were able to install and use paraviewweb on my
>> >> >> local machine. All the examples, shuttle, service etc
>> >> >> worked as expected.
>> >> >>
>> >> >> Our second installation was on a server without X.
>> >> >> The installation went fine but webgl does not
>> >> >> seem to work for this installation however JS, Java, Flex are
>> >> >> all working. Could this be related to the graphics card of
>> >> >> the machine ? I am not a paraview or GL expert but if
>> >> >> paraview is doing server side rendering and the graphics
>> >> >> card is not compatible for webgl, then this would be a
>> >> >> problem I guess ?
>> >> >>
>> >> >> Any clues are greatly appreciated.
>> >> >>
>> >> >> Cagatay
>> >> >>
>> >> >> _______________________________________________
>> >> >> Powered by 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
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Powered by 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
>> >> >
>> >
>> >
>
>