Forum Problems Installing LAMS: author module and localhost

Back to Problems Installing LAMS
You may request notification for author module and localhost.	Search:

	1: author module and localhost By: Manolis Mavrikis		06/14/08 10:04 AM	[ Reply \| Forward ]
Hi there. the way to redirect apache to jboss and lams has been discussed a lot but can't sort it out. I am a bit confused so any help will be appreciated. I am using mod_proxy.c to proxy pass /lams to http://myserver.ac.uk:8180/lams In order to bypass some security problems and that I cannot open port 8180 for some admin reasons beyond my control. So although it seems that http://myserver.ac.uk/lams works when I am outside the network and trying to access the author module I get nothing. In fact I get the popup window but it is empty. The flash window seems to be loading and then I see nothing. Is this because lams is still trying to access things in 8180 but it can't? I changed the web-based configuration settings to say http://myserver.ac.uk/lams/ instead of the 8180. Any thoughts, help, links will be greatly appreciated. Cheers, Manolis ps. I also changed the lams.properties file but I am not sure it has an effect anyway. Posted by Manolis Mavrikis

	2: Re: author module and localhost By: Jun-Dir Liew	In response to 1	06/15/08 04:57 AM	[ Reply \| Forward ]
Hi Manolis, It's common for non-80 web ports not to be open in firewalls. It's also nice to have webapps available on port 80 so you don't have to type the port in your browser. For both these reasons there are a few solutions to make a tomcat app like lams available on port 80, using proxy pass on apache is one of them - I like to use mod_jk myself... Loading author involves a few javascript and flash calls back to the lams server - for this it uses the ServerURL value in the lams sysadmin configuration. If the URL in your browser and the ServerURL domains don't match, then javascript (or is it flash? or both?) won't complete its work and author won't load. It's not a configuration or network issue, just a security measure of javascript/flash. Quick fix is to simply access LAMS via the URL used in your value for ServerURL. Longer term, just put the URL you want your server to be known by as your value for ServerURL in the lams sysadmin interface. Hope some of this is helpful! ps changing lams.properties won't have an effect, it's a kind of caveat that we only use this file at installer/updater time, not run time... Posted by Jun-Dir Liew

Reply to first post on this page

Back to Problems Installing LAMS