optionfile usage doesn't install tomcat

[habitual]

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-community-3.4.c-installer-linux-x32.bin does the same thing?

This varies from what is installed if just using ./alfresco-community-3.4.[bc]-installer-linux-x32.bin and answering all the Qs interactively.

Needless to say, tomcat did not get installed.

Here's the myoptionfile contents if it helps.

mode=unattended
enable-components=mysql,java,alfresco,alfrescosharepoint,alfrescorm,alfrescowcmqs,alfrescowcm,alfrescoquickr,openofficecomponent
prefix=/opt/alfresco
mysql_password=areyoukidding
mysql_database_name=alfresco
mysql_database_username=alfresco
mysql_database_password=alfresco
tomcat_installation_type=default
tomcat_server_port=8080
tomcat_server_shutdown_port=8005
tomcat_server_ssl_port=8443
tomcat_server_ajp_port=8009
alfresco_admin_password=hoosierdaddy
baseunixservice_install_as_service=1
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

running /etc/init.d/alfresco start only starts only MySQL :
101227 13:16:34 mysqld_safe Logging to '/opt/alfresco/mysql/data/mysqld.log'.
101227 13:16:34 mysqld_safe Starting mysqld.bin daemon with databases from /opt/alfresco/mysql/data
/opt/alfresco/mysql/scripts/ctl.sh : mysql  started at port 3306

alfresco/alfresco.sh start is the same thing.
101227 13:18:51 mysqld_safe Logging to '/opt/alfresco/mysql/data/mysqld.log'.
101227 13:18:51 mysqld_safe Starting mysqld.bin daemon with databases from /opt/alfresco/mysql/data
/opt/alfresco/mysql/scripts/ctl.sh : mysql  started at port 3306

Reboot same thing.

Strangely, there are NO catalina.out nor alfresco.log files.

Please tell me what I am doing incorrectly, so that I can utilize my optionfile for automated installs.

Thank you for your time.

[dangruhn]

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.

[resplin]

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.