Difference between revisions of "ParaViewWeb with Apache as front-end"

From KitwarePublic
Jump to navigationJump to search
Line 8: Line 8:
 
In order to allow better performance and streaming in image delivery, we use the '''ajp''' protocol, otherwise the default '''http''' protocol can work but will prevent the Java renderer from working due to data streaming issue.
 
In order to allow better performance and streaming in image delivery, we use the '''ajp''' protocol, otherwise the default '''http''' protocol can work but will prevent the Java renderer from working due to data streaming issue.
  
=== Apache ===
+
== Apache ==
  
==== Enable required modules ====
+
=== Enable required modules ===
  
==== Define a new Virtual host ====
+
=== Define a new Virtual host ===
  
==== Enable Virtual host ====
+
=== Enable Virtual host ===
  
=== Tomcat ===
+
== Tomcat ==
  
 
In that case we supposed that tomcat has been download and installed in a user home directory and the tomcat used is not from the system package as that one already listen on port 80.
 
In that case we supposed that tomcat has been download and installed in a user home directory and the tomcat used is not from the system package as that one already listen on port 80.
Line 23: Line 23:
 
- YOUR_SERVER_HOSTNAME: name used for your server when accessed by the web clients.
 
- YOUR_SERVER_HOSTNAME: name used for your server when accessed by the web clients.
  
==== Add an AJP connector ====
+
=== Add an AJP connector ===
  
 
Edit the file TOMCAT_HOME/conf/server.xml
 
Edit the file TOMCAT_HOME/conf/server.xml

Revision as of 12:22, 1 June 2011

ParaViewWeb


Introduction

ParaViewWeb is a Web application written in Java that requires a Java based web server such as Tomcat or Jetty. Those servers tends to run on high port number such as 8080 or 9000 and if they are started from a regular user, they have not the right to listen on port 80 like the default HTTP usage expect. Moreover, if you want to integrate ParaViewWeb inside another web content that is served by another server technology such as Ruby, Python or PHP, you will need an Apache server on the front of all your servers to dispatch all the client requests to the proper server.

This wiki page explain how to setup a virtual host in between Tomcat and Apache2 inside an Ubuntu. For other systems, the paths may slightly vary, but the logic should be pretty close. In order to allow better performance and streaming in image delivery, we use the ajp protocol, otherwise the default http protocol can work but will prevent the Java renderer from working due to data streaming issue.

Apache

Enable required modules

Define a new Virtual host

Enable Virtual host

Tomcat

In that case we supposed that tomcat has been download and installed in a user home directory and the tomcat used is not from the system package as that one already listen on port 80. In the following explanation, we will use file path that you will need to adjust based on your local setting. Here is the list of the variable name with their meaning that will need some adjustments: - TOMCAT_HOME: Directory that contains tomcat when you uncompressed it. - YOUR_SERVER_HOSTNAME: name used for your server when accessed by the web clients.

Add an AJP connector

Edit the file TOMCAT_HOME/conf/server.xml