If you want to create a content-based Web application that does not contain any dynamic content (such as servlets, JSP files, filters, and associated metadata) you might prefer to create a static Web project, as opposed to a dynamic Web project.
The folder that a static Web project is published to is modifiable, so that when you set the publishing "root" value (called a context root), such as /web1, for a static project, everything in the Web content folder will be published to the web1 folder under the Web server's doc root. This enables you to group Web resources on a Web server in folders that correspond to Web projects in the workbench. When projects defined in this way are ready for production, you can publish specific projects directly to the doc root by changing the value to / and all publishing, link fixing, and browsing will update automatically.
Alias /scripts/ "/var/www/scripts"In this example, in which the current static Web project will contain common JavaScript™ files, you can set the context root value to be "scripts". In order for the resources in the static Web project to be published to the correct location on the Web server, you must add this Alias mapping to the server tools instance of the static Web server, as follows.
Related concepts
Web application overview
Web development tools
Dynamic Web projects and applications
Web archive (WAR) files
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.