Changes between Version 7 and Version 8 of CaTissue HowTo Build & Deploying CaTissue from the source code?

Timestamp:

05/14/13 16:27:43 (11 years ago)

Author:

Nick Holden

Comment:

--

CaTissue HowTo Build & Deploying CaTissue from the source code?

@@ -169 +169 @@
 == Update for CaTissue Plus deployed on LAMP servers ==
 
-The user accesses a 'load balancer' by means of an alias:
+The default version of Java installed on the LAMP servers is OpenJDK 1.5 - this doesn't play well with JBoss. So we've additionally installed OpenJDK 1.7. This seems to work better, but requires that JBoss is started thus:
+
+> JAVA_HOME=/usr/java/jdk1.7.0_21/ /local/jboss/bin/run.sh &
+
+This doesn't need to be done as root.
+
+The end user accesses a 'load balancer' by means of an alias:
 
 https://lcbru-catissue-dev.rcs.le.ac.uk
 
 which routes the request to the server itself at lamp-api-15.rcs.le.ac.uk:80 - this machine only has port 80 accessible, so Apache is listening on port 80 and using mod_proxy and mod_proxy_http to reverse proxy to port 8080 for JBoss to pick up the request.
+
+{{{
+From http.conf:
+# Proxy to provide access to the JBoss Application Server
+ProxyPass / http://localhost:8080/
+ProxyPassReverse / http://localhost:8080/
+}}}
 
 It works sufficiently to show the JBoss interface and the caTissue index page.
@@ -205 +218 @@
 There is a known security vulnerability in JBoss, the JMX console to be precise, in certain versions of JBoss, including the one which CaTissue uses. It is imperative that when setting up JBoss on a server to deploy CaTissue, the JMX console is removed from the server, or patched as per http://java.dzone.com/articles/jboss-jmx-console
 
+Using the 'BRISSkit' package for JBoss, stored in the LCBRU artifact repository, will ensure the JBoss jmx console is not installed.