Why use this deployment scenario?
- The Tomcat server is quick and easy to install.
- The Tomcat server can be restarted very quickly which makes it convenient for development.
- It allows you to test your models quickly running from Eclipse or RAD.
What are the drawbacks of using this deployment scenario?
- The Tomcat server should only be used for development, so this environment will never match your productions environment.
- The Tomcat server does not have a portlet container and so you cannot test portlets using this server.
Description of the scenario
- The development WAR is deployed to a local Tomcat server.
- A portlet WAR cannot be deployed to the Tomcat server.
- Create a new project.
- On the Project Name page of the wizard, enter a name for your project. Click Next.
- On the Add Feature Sets page of the wizard, check off the feature sets you want in your project. Click Next.
- On the Java Settings page of the wizard, accept the defaults. Click Next.
- On the Deployment Configuration screen, click the Add button for the Application Server Deployment Configuration.
- Enter a name for the configuration. Make it descriptive since you will be able to reuse this configuration for other projects.
- Enter a description for this configuration. Provide information about this configuration for future reference.
- Select Tomcat as the server type
- Installed Applications directory will default to C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps - Change this to match the webapps directory for your Tomcat server.
- Leave the host setting with the default of localhost. Since your server is on your local machine there isn't any reason to change this default.
- Enter a new port number only if you know it is different from the default.
- Click OK
- Click finish. The project will be created and ask if you want to deploy now. Click yes. This will build the dev WAR.