
Another point to not miss is the definition of the shared.loader in the catalina.properties: :$ cp tomcat/bin/setenv.sh tomcat-7.0.68/bin/setenv.sh This include the specific JVM parameters setup in the setenv.sh and usually, there is nothing more to do for the tomcat/bin folder. Once done, the idea is simply to transfer all specific customization from your old Tomcat version to the new one. So first of all, let’s download the software: :$ cd /opt/alfresco-4.2.c/
TOMCAT VERSION LATEST UPGRADE


TOMCAT VERSION LATEST PATCH
Now the question is then which version of the Apache Tomcat should be used for the Alfresco Community Edition? I would tend to say that it is probably best to always use the latest available patch of the Apache Tomcat version that is supported by Alfresco. You can find the list of supported versions for the Alfresco Enterprise software on the Alfresco Web Site and we can also use this as a base for the Community Edition even if there is no official support for the CE.

Usually, each version of Alfresco is officially supported for only one specific version of Apache Tomcat and that’s fine for some use cases but I think that most Alfresco administrators will not follow this specific recommendation, at least for the Community Edition.
TOMCAT VERSION LATEST INSTALL
Alfresco provide a default version with its installer but when installing Alfresco manually, an administrator can choose to install Alfresco using a different version of Apache Tomcat. Different versions of Alfresco can be installed with different versions of Tomcat.
