|
|
| (49 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| == Documentation ==
| | The ParaViewWeb documentation related to the latest ParaView version (5+) can be found [https://kitware.github.io/paraviewweb/ here] |
| {| border="0" align="center" width="98%" valign="top" cellspacing="7" cellpadding="2"
| |
| |-
| |
| ! width="33%"|
| |
| ! |
| |
| ! width="33%"|
| |
| ! |
| |
| ! width="33%"|
| |
| |-
| |
| |valign="top"|
| |
|
| |
|
| ===Compile/Install===
| | On top of that additional informations on the applications are available here: |
| ----
| |
| * [[ParaViewWeb Building]]
| |
| : This section explain each step to build the ParaViewWeb framework. | |
|
| |
|
| ===Server Setup===
| | - [https://kitware.github.io/visualizer/ Visualizer] |
| ---- | | - [https://kitware.github.io/light-viz/ LightViz] |
| * aaaa
| | - [https://kitware.github.io/arctic-viewer/ ArcticViewer] |
| : bbbb
| |
|
| |
|
| ===Plugins===
| | Old documentation is still available [http://www.paraview.org/Wiki/index.php?title=ParaViewWeb&oldid=57949 here] |
| ----
| |
| * aaaa
| |
| : bbbb
| |
| | |
| |bgcolor="#CCCCCC"|
| |
| |valign="top"|
| |
| | |
| ===JavaScript===
| |
| ----
| |
| * [[ParaViewWeb JavaScript Introduction]]
| |
| : This section explain the first step in developing a web application based on ParaViewWeb.
| |
| | |
| * [[ParaViewWeb JavaScript Code sample]]
| |
| : This section provides some advanced JavaScript scenari which could be used as a tutorial on how to use the JavaScript API with some advanced features.
| |
| | |
| * [[ParaViewWeb JavaScript API]]
| |
| : This section provides the API of the Paraview and the Renderers objects used in ParaViewWeb. | |
| | |
| |bgcolor="#CCCCCC"|
| |
| |valign="top"|
| |
| | |
| ===Design & Implementation===
| |
| ----
| |
| * aaaa
| |
| : bbbb
| |
| | |
| | |
| ===Miscellaneous===
| |
| ----
| |
| * aaaa
| |
| : bbbb
| |
| |}
| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| == Introduction ==
| |
| | |
| ParaView web visualization aims to provide a collaborative remote web
| |
| interface for 3D visualization with ParaView as a server.
| |
| Moreover, this also provide a JavaScript API based on the ParaView scripting
| |
| features and capabilities. Some of the web samples are fully operational
| |
| clients that allow you to create remote web visualization as well as joining
| |
| previously created ones with fully interactive user interface for building
| |
| complex data processing and visualization.
| |
| | |
| == Deployment ==
| |
| | |
| === Prerequisites ===
| |
| | |
| The following software or files should be available on the computer that
| |
| will execute the application
| |
| | |
| * Applications:
| |
| ** Java : JDK 1.6 from sun and NOT the OpenJDK
| |
| ** ActiveMQ : Binary package
| |
| ** Tomcat 6 : Binary package
| |
| | |
| * Builded components:
| |
| ** PWServer : Builded executable with its dependency library. (ParaView, ActiveMQ-CPP, Python)
| |
| ** PWService.war : Web Service for remote visualization
| |
| ** pw-config.properties : Configuration file for the PWService
| |
| | |
| * Optional builded components:
| |
| ** PWApp.war : Complex Web application
| |
| ** PWConsole.war : Javascript command line console sample
| |
| ** PWSandbox.war : Sandbox sample application
| |
| ** PWSimple.war : Simple static Javascript code starting 2 concurrent visualization session with 6 renderer.
| |
| ** Sample Data : Some sample data are provided and used in the PWApp application. To allow the application to find them, you will need to copy the data directory from the source to the WORKING_DIR in order to get a file path like the following one. Beaware of the case ! > WORKING_DIR/data/cow.vtp
| |
| | |
| Tomcat need to be pre-configured in order to run the web components
| |
| properly. To do so, just copy the war file that you want to run into the
| |
| webapps directory of your tomcat.
| |
| Add a configured version of the pw-config.properties into the "lib"
| |
| directory of your tomcat.
| |
| | |
| === Starting the application ===
| |
| | |
| * If an OpenJDK is installed on the computer, you will need to set the JAVA_HOME system property before launching tomcat and the JMS brocker.
| |
| The following command line illustrate how to do it on linux:
| |
| > export JAVA_HOME=/opt/jdk1.6.0_18
| |
| | |
| * Start the JMS brocker
| |
| > cd apache-activemq-5.3.0/bin/
| |
| > ./activemq
| |
| * Start tomcat
| |
| > cd apache-tomcat-6.0.24/bin
| |
| > ./startup.sh
| |
| | |
| To quit the applications
| |
| > CTR-C in the terminal that start the activemq message broker
| |
| > cd apache-tomcat-6.0.24/bin
| |
| > ./shutdown.sh
| |
| | |
| === How to try it ! ===
| |
| | |
| * Make sure that ActiveMQ and Tomcat are running.
| |
| * Go with your browser to the PWService home page.
| |
| ** http://localhost:8080/PWService
| |
| * Try to login (admin/admin)
| |
| * Go to a sample web page
| |
| ** http://localhost:8080/PW
| |
| ** or http://localhost:8080/PWApp
| |
| ** or http://localhost:8080/PWConsole
| |
| ** or http://localhost:8080/PWSandbox
| |
| ** or http://localhost:8080/PWSimple
| |
| | |
| | |
| == URLs ==
| |
| | |
| Home page that show all available samples
| |
| * [WebServer/Samples] : http://localhost:8080/PW
| |
| | |
| All web applications and services
| |
| * [WebServer/PWService] : http://localhost:8080/PWService (Authentication: admin/admin)
| |
| * [WebServer/PWApp] : http://localhost:8080/PWApp
| |
| * [WebServer/Samples/InteractiveConsole]: http://localhost:8080/PWConsole
| |
| * [WebServer/Samples/Sandbox] : http://localhost:8080/PWSandbox
| |
| * [WebServer/Samples/SimpleJavaScript] : http://localhost:8080/PWSimple
| |
