Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. In Eclipse go to File -> New -> Server -> Next -> Next. If you have a server under "Server Runtime Environment" you can use it. If not, click "Add".
  2. Include Page
    WST:Giving Apache Tomcat Enough MemoryWST:
    Giving Apache Tomcat Enough Memory
  3. Now we have to add in your Apache Tomcat "Manager" webapp -- without it, the Survey Manager can't create surveys.
    1. Go to Window -> Show View -> Servers (if it's not in the list, click 'Other...' and add it
    2. In the Servers View, right click your Tomcat server and click "Open".
    3. At the bottom of the editor, click the "Modules" tab.
    4. Click "Add External Web Module..."
    5. Browse to your tomcat installation/webapps/manager and pick it.
  4. In your projects, notice your "Servers" project.
    1. Open that folder.
    2. Look for a folder named after your server that you picked in step 1. Go into that folder.
    3. Open "tomcat-users.xml" for editing.
      1. Just before </tomcat-users> at the end, add a line like this (you may choose any username or password that you want):
        <user username="tomcat" password="tomcat8675792pass" roles="manager"/>
      2. Why did we have to do this? In real deployments, WST edits this file automatically, but it requires a server reboot to take effect. But when the server reboots, Eclipse recopies this conf file back on top... So the program can never get access to it.
    4. Open up the "server.xml" file for editing.
      1.  Near the very end of the file, look for something that looks like "<Context ... path="/manager" ... />
      2. Just before that "/>" add this:
        privileged="true" antiResourceLocking="false" antiJARLocking="false"
      3. In my case, the final version looks like this but your docBase will have to be customized for your own installation:
        <Context docBase="/home/apowers/Programs/apache-tomcat/apache-tomcat-6.0.20/webapps/manager" path="/manager" reloadable="true" privileged="true" antiResourceLocking="false" antiJARLocking="false"/>
      4. We had to do this because without it, the manager wouldn't have the "privileged" controls it needs.

...