topic optionfile usage doesn't install tomcat in Alfresco Archive

optionfile usage doesn't install tomcat

habitual — Mon, 27 Dec 2010 21:27:32 GMT

Hello:I installed alfresco-community-3.4.b-installer-linux-x32.bin using this option as root on an Ubuntu 10.04 LTS Server:alfresco-community-3.4.b-installer-linux-x32.bin –optionfile myoptionfile and the tomcat directory only had 3 directories in it and they are lib, shared, and webapps.alfresco-co

Re: optionfile usage doesn't install tomcat

dangruhn — Tue, 18 Jan 2011 14:39:02 GMT

It would be nice if the Alfresco folks would chime in here.

You should find that, if you have the right permissions, tomcat is being installed but in /tomcat. Somehow the installer is forgetting the install root when the command line or config file is being used. I've played around with changing the position of the parameter or leaving it out but could find no change.

It appears that, when the command line or config file is used, the prefix is not being set for the tomcat install.

Re: optionfile usage doesn't install tomcat

resplin — Thu, 20 Jan 2011 07:14:57 GMT

I recently blogged about using the option file. It looks like you already have it pretty well figured out, but a link to my post might help others that come across this thread:

http://richard.esplins.org/siwi/2011/01/12/automating-new-alfresco-installers/

I have not seen the behavior you are describing, and I am installing in a very similar environment. A few thoughts:

* Perhaps the problem is with the tomcat_installation_type setting. I have left the line out completely to get the behavior of the embedded tomcat being installed (and it is correctly placed as a subdirectory in my Alfresco install), and I have set it to "=existing" to get the behavior of no tomcat being installed. Perhaps your "=default" setting is triggering the bug?

* Though I started playing with 3.3.3 Enterprise, I have spent most of my time testing with the betas and release candidates for 3.4 Enterprise. The Bitrock installers are new, and are receiving a lot of testing. Each release has lots of installer bugs fixed. Perhaps this behavior was fixed and that is why I am not seeing it.

* My blog post has an example option file that works for me. Perhaps you can see how it works in your environment.

* If you are able to isolate the behavior, please log a JIRA in our issue tracker.

Good luck.