Changes between Version 4 and Version 5 of CaTissue HowTo Build & Deploying CaTissue from the source code?

Timestamp:

12/11/12 16:40:10 (12 years ago)

Author:

Nick Holden

Comment:

--

CaTissue HowTo Build & Deploying CaTissue from the source code?

@@ -162 +162 @@
 csm.database.username=[[BR]]
 csm.database.password=[[BR]]
+
+
+----
+
+
+== Update for CaTissue Plus deployed on LAMP servers ==
+
+The 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.
+
+It works sufficiently to show the JBoss interface and the caTissue index page.
+
+Originally I tried with jboss.server.host set to 'lcbru-catissue-dev.rcs.le.ac.uk' - this caused infinite redirect loops, and is bad. It isn't clear what this config setting is used for, and if it is used for building page URLs then the full alias is needed. I've changed this now to the actual IP address of the server itself (but this will not work if supplied to a browser as a link to a resource). It is now possible to log in to CaTissue.
+
+There remains an issue with flex / caused by the fact that https is used to connect to the load balancer, but the JBoss connection itself is not securely piped. That isn't a problem because it is all behind the firewall of the load balancer, but flex doesn't like it. The solution as documented on a number of websites is:
+
+
+{{{
+I changed my-secure-amf definition in services-config.xml to use a SecureAMFChannel but point 
+to a non-secure AMFEndpoint. A re-compile and deploy solved the issue. 
+
+<channel-definition id="my-secure-amf" 
+class="mx.messaging.channels.SecureAMFChannel"> 
+             <endpoint 
+url="https://{server.name}:{server.port}/{context.root}/messagebroker/am\ 
+fsecure" class="flex.messaging.endpoints.AMFEndpoint"/> 
+             <properties> 
+                <add-no-cache-headers>false</add-no-cache-headers> 
+             </properties> 
+  </channel-definition> 
+
+}}}
+