Changes between Version 13 and Version 14 of CaTissue HowTo Build & Deploying CaTissue from the source code?

Timestamp:

07/19/13 10:49:39 (11 years ago)

Author:

Nick Holden

Comment:

--

CaTissue HowTo Build & Deploying CaTissue from the source code?

@@ -171 +171 @@
 1. The default version of Java installed on the LAMP v1 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 &
+> JAVA_HOME=/usr/java/jdk1.7.0_21/ /local/jboss/bin/run.sh -b 0.0.0.0 &
 
 This doesn't need to be done as root.
@@ -256 +256 @@
 -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false"
 
-Additionally, the security vulnerability (as below) must be addressed.
+Additionally, the security vulnerability (as below) must be addressed by deleting the admin console and the jmx console packages. We don't need them.
+
+
+== Comment out the LabelGenerator ==
+
+By default CaTissue automatically assigns specimen labels and barcodes - this causes a problem with the BRICCS API client. Following deployment of CaTissue, check that the jboss/server/default/catissuecore-properties/LabelGenerator.Properties file doesn't have the extra definitions which force barcode generation (i.e. comment out 'specimenLabelGeneratorClass' and 'specimenBarcodeGeneratorClass') before running JBoss.
+
 
 == Update: Security vulnerability in JBoss ==
@@ -262 +268 @@
 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 at http://lcbru-data.rcs.le.ac.uk/jboss/jboss-4.2.3.GA-brisskit-development.zip - will ensure the JBoss jmx console is not installed.
+Using the 'BRISSkit' package for JBoss - stored in the LCBRU artifact repository at http://lcbru-data.rcs.le.ac.uk/jboss/jboss-4.2.3.GA-brisskit-development.zip - will ensure the JBoss jmx console is not installed. Alternatively delete from the server/default/deploy directory the directories which deliver the jmx console and the admin console.
 
 == Ant optional jar ==