Tuesday, 24 Mar, 2009 | 1 Comment alfresco-logo Recently I was evaluating the final Alfresco Labs 3 document management nifty program, inside my little, trusty (and quite overloaded...), Ubuntu home server. I experienced a lot of problems related to the 8080 port, because Zenoss defaults to that and Alfresco wants that too. I searched for some info on how to change alfresco's default 8080 apache tomcat port and here's what I found (from the alfresco wiki page): Edit those files and change 8080 to something else (like for example 8099): $ALF_HOME/tomcat/conf/server.xml $ALF_HOME/tomcat/webapps/share/WEB-INF/urlrewrite.xml $ALF_HOME/tomcat/webapps/share/WEB-INF/classes/alfresco/pagerenderer-config.xml $ALF_HOME/tomcat/webapps/share/WEB-INF/classes/alfresco/webscript-framework-config-test.xml $ALF_HOME/tomcat/webapps/share/WEB-INF/classes/alfresco/webscript-framework-config.xml $ALF_HOME/tomcat/webapps/share/WEB-INF/classes/alfresco/webscripts/org/alfresco/indexall.get.mediawiki.ftl $ALF_HOME/tomcat/shared/classes/alfresco/extension/custom-repository.properties and add an entry to overide the default: repo.remote.endpoint.url=http://localhost:8080/alfresco/service They say the following about this mess:"It is planned for future versions to allow for central configuration of the port. It is not fixed yet, when this will be included." I tried the modifications, but essentially I screwed my alfresco setup (more on this later maybe), so I removed and purged my alfresco. I then decided to search for some info on how to change the default Zenoss 8080 port, and so I found that editing /usr/local/zenoss/zenoss/etc/zope.conf and uncommenting line 840 with: port-base 1000 will move Zenoss Web UI to port 8080 + 1000, or 9080. I then rebooted my server and checked if zenoss was responding (you may simply restart its service by using /etc/init.d/zenoss-stack restart). In conclusion, by proceeding as per above, you can: Avoid changing Alfresco's port. Proceed with the Alfresco installation process. Keep Zenoss on the same webserver. Hope that helps! Rate this post Andrea MatesiSenior Professional Network and Computer Systems Engineer during work hours and father when home. Andrea strives to deliver outstanding customer service and heaps of love towards his family. In this Ad-sponsored space, Andrea shares his quest for "ultimate" IT knowledge, meticulously brought to you in an easy to read format. Share this:LinkedIn Related
Thanks for the heads up on avoiding the port mess in Afresco. I am currently trying to get Alfresco and Liferay running on a virtual machine. Since Liferay was already running on a preconfigured Tomcat instance I tried to change the other tomcat instance running Alfresco to run on a different port .... BIG MISTAKE. I am now going to try changing Liferay to run on a different port. And after reading your post I think it is a good idea. Cheers. Loading...