Developing and deploying Web applications

 

Overview

A developer creates the files comprising a Web application, and then assembles the Web application components into a Web module. Next, the deployer (typically the developer in a unit-testing environment or the administrator in a production environment) installs the Web application on the server.

 

Procedure

  1. (Optional) Migrate existing Web applications to run in the new version of WebSphere.

  2. Design the Web application and develop its code artifacts: Servlets, JSP files, and static files, as for example, images and Hyper Text Markup Language (HTML) files.

  3. Develop the Web application, using WAS extensions to enhance its functionality.

  4. Assemble the Web application into a Web module using an assembly tool. Web module assembly properties might include the ability to:

  5. Deploy the Web module or application module that contains the Web application.

    Following deployment, you might find it handy to use the tool that enables batch compiling of the JSP files for quicker initial response times.

  6. (Optional) Troubleshoot your Web application.

  7. (Optional) Modify the default Web container configuration in the application server in which you deployed the Web module or application module containing the Web application.

  8. (Optional) Manage the deployed Web application.

 

See also


Web applications
web.xml file
Migrating Web application components from WebSphere Application Server V4.x
Migrating Web application components from WebSphere Application Server V5.x
Default Application
Servlets
Developing servlets with WAS extensions
JavaServer Pages
Developing Web applications
Web modules
Assembling Web applications
Troubleshooting tips for Web application deployment
Modifying the default Web container configuration
Web applications: Resources for learning

 

See Also


Web container
Enterprise (J2EE) applications

 

See Also


JavaServer Pages engine troubleshooting tips