Task overview: Developing and deploying Web applications

 

+

Search Tips   |   Advanced Search

 

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 WAS.

  2. Design the Web application and develop its code artifacts: Servlets, JavaServer Pages files, and static files, as for example, images and Hyper Text Markup Language (HTML) files. See the Web applications: Resources for learning topic for links to design documentation.

    JavaServer Pages programming tips:

    • Disable session state of JavaServer Pages files using <%@ page language="java" contentType="text/html" session="false" %> instead of <%@ page language="java" contentType="text/html" %>

    • Replace setProperties calls in your JavaServer Pages files with direct calls to the appropriate setxxx methods.

  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:

    • Configure servlet page lists.

    • Configure servlet filters.

    • Serve servlets by class name.

      Serving servlets by name or class name is triggered by setting the serveServletsbyclassnameEnabled property within IBM extensions. Use the invoker.patterns attribute to specify the patterns that trigger invocation of the server component and allows the serving of servlets by name or by class name. This value is a list separated by either a space, colon, or semicolon.

    • Enable file serving.

      In file serving, Web applications can serve static file types, such as HTML. File-serving attributes are used by the servlet that implements file-serving behavior.

  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 appserver in which you deployed the Web module or application module containing the Web application.

  8. (Optional) Manage the deployed Web application.


Web applications
web.xml file
Default Application
Servlets
Developing servlets with WAS extensions
Configure JSP engine parameters
JavaServer Pages
Developing Web applications
Web modules
Modifying the default Web container configuration
Assembling Web applications
Task overview: Assembling applications using remote request dispatcher
Securing applications during assembly and deployment
Defining an extension for the registry filter
Migrating Web application components from WAS V5.x
Tuning URL invocation cache
Web application deployment troubleshooting tips
Web applications: Resources for learning

 

Related concepts

Enterprise (J2EE) applications

 

Related Reference


JavaServer Pages troubleshooting tips