Apache Tomcat 9 Download [UPD]
Leida Haury
I have tomcat 5.5 installed, running and verifiable at :8080/. The Tomcat menu option appears in the Eclipse menu bar and I can start and stop Tomcat from there. In Eclipse, it does not show as a Server Runtime Environment in Window - Preferences - Server - Runtime Environments, nor does it appear in the list of environments that can be added when I click the "Add" button. All I see is the J2EE Runtime Library.
You need to go to Help>Eclipse Marketplace . Then type server in the search box it will display Eclipse JST Server Adapters (Apache Tomcat,...) .Select that one and install it .Then go back to Window>Preferences>Server>Runtime Environnement, click add choose Apache tomcat version then add the installation directory .
You may get more success if you do a "search" for the runtime env from the preferences screen instead of hitting "add" - see this demo on youtube. =EOkN5IPoJVs&playnext_from=TL&videos=rVnITzSU2Z8 - When you hit search, you are prompted to point to the tomcat directory and then it SHOULD add it as a server runtime environment. Unfortunately for me, that is not the case (I get "no new server runtime environments were found") But you might have more success.
Grant write permissions on /opt/tomcat to the group (that would be 570) and set the sticky bit so that they can remove only the files they own (chmod 1570). Grant the server write permission to the logs, and read permissions to the developers (0740 for the folder, 0640 for the files, the sticky bit is probably not necessary, and never grant it to a file, only the folders, as it has a different meaning (execute with the permissions of the owner when the file is executable)).
I think @intropedro's accepted answer is a good one. It's worth pointing out that using a package installer can save a lot of headaches -- at least for Tomcat 7 on Ubuntu apt-get install tomcat7 produces a more "standard" set of installation directories are:
All permissions are set up correctly with the principle of least privilege, such that adding users to the group tomcat7 is sufficient to allow deployment. Further, the tomcat server is set up as a service that can be started and stopped as others (e.g. sudo service tomcat start or alternatively /etc/init.d/tomcat start). Tomcat starts on reboot automatically, and there's a "restart" command. I am sure there's an equivalent yum package for RHEL/CentOS users. (And yes, there's a homebrew installer for local OSX installations).
Firewall - Allow an app or feature through Windows Firewall - Another program - browse Tomcat7.exe (i.e. c:\xampp\tomcat\bin\Tomcat7.exe) if you enabled it as a service or Tomcat7w.exe when it is not a service...
I used tomcat 6, ODKAggregate1.4.4 , JDK 7, MySQL server 5.6.
When I try to start the /ODKAggregate in manager.html , i get FAIL- application at context /ODKAggregate could not be started . Though I added my mysqlconnector,jar I get this error. and not able to access the ODKAggregate page, I get 404 error.
Although I was able to get past this issue and have Aggregate load up in my browser, more bugs appeared and this time it was complaining something about XSRF Tokens in the tomcat logs, or Cross Site Scripting Attack, which would cause the browser to keep refreshing, or prevent the ability to save any changes, enable or disable forms, add users, change passwords etc... I put detailed instructions on my other post.
At this point I have problem connecting my ODK collect app and ODK Aggregate installed on tomcat.
I have added my XML form in the ODK site after logging in. I keep the XML form for data collection in my device's internal storage.I am able to fill the form, edit it etc. When I try to select the filled form and upload it to server ( SELECT THE REQUIRED FORM AND CLICK 'send selected') , I get Error : client Protocol Exception
If you have set the org.apache.catalina.STRICT_SERVLET_COMPLIANCE Tomcat property to true, add the org.apache.tomcat.util.http.ServerCookie.ALWAYS_ADD_EXPIRE property in the $CATALINA_BASE/bin/setenv.sh file, to add the Expires attribute to the headers:
In development environments, a possible workaround is to configure Tomcat to allow encoded slash characters by adding the org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true property to the CATALINA_OPTS variable; for example:
configuration elements are found in the configuration file, /path/to/tomcat/conf/server.xml. The following excerpt shows an example with the URIEncoding and sslProtocol attributes set appropriately:
For example, to monitor your Tomcat application servers, add the zone directive to the tomcat upstream group (if you followed the instructions in Configuring Application Health Checks, you already made this change).
df19127ead