WAS v8.5 > Develop applications > Develop web applications > Assemble web applications

Assemble web applications

Assemble a web module to contain servlets, JSP (JSP) files, and related code artifacts. (Group enterprise beans, client code, and resource adapter code in separate modules). After assembling a web module, we can install it as a stand-alone application or combine it with other modules into an enterprise application.

This topic assumes that we have created and unit tested Servlets and JSP files and other web components to assemble in an enterprise application and deploy onto an application server. Use an assembly tool to assemble a web module in any of the following ways:

• Import an existing web module (WAR file).

• Create a new web module.
• Copy code artifacts (such as servlets) from one web module into a new web module.

Although we can input various properties for web archives, available properties are specific to the Servlet, JSP, and Java EE specification level.

1. Start an assembly tool.

2. If we have not done so already, configure the assembly tool for work on Java EE modules. Ensure that J2EE and Web capabilities are enabled.
3. Migrate WAR files created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to an assembly tool. To migrate files, import your WAR files to the assembly tool.

4. Create a new web module.
5. Copy code artifacts (such as servlets) from one web module into a new web module.

Results

A web project is migrated or created. Files for the Web project are shown in the Project Explorer view under Enterprise Applications and Web Projects.

We can now deploy the web project to an application server.

Subtopics

• Web component security
  A web module consists of servlets, JSP files, server-side utility classes, static web content, which includes HTML, images, sound files, cascading style sheets (CSS), and client-side classes or applets. We can use development tools such as Rational Application Developer to develop a web module and enforce security at the method level of each web resource.
• Secure web applications using an assembly tool
  We can use three types of web login authentication mechanisms to configure a web application: basic authentication, form-based authentication and client certificate-based authentication. Protect web resources in a web application by assigning security roles to those resources.
• Security constraints in web applications
  Security constraints determine how web content is to be protected.
• Security settings
  Use the dmgr console to modify the security settings for all applications.
• 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.
• web.xml file
  The web.xml file provides configuration and deployment information for the web components that comprise a web application.
• 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.

Related concepts:

Web modules
Web applications
JSP
Page lists
Application life cycle listeners and events
Servlet filtering
Servlets
Client type detection support
Global tag libraries (deprecated)

Related

Install enterprise application files
Assemble applications

Reference:

Web applications: Resources for learning

Related information:

Importing WAR files
Create a dynamic web project

+

Search Tips   |   Advanced Search