Migrating Web application components from WebSphere Application Server Version 5.x

About this task

Migration of Web applications deployed in WebSphere Application Server Version 5.x is usually not necessary; version 2.2 and 2.3 of the Java Servlet specification and version 1.2 and 1.4 of the JavaServer Pages (JSP) specification are still supported unless the behavior was changed in Servlet 2.4 or JSP 2.0 Specifications.

Servlet migration might be a concern if your application:

JSP migration might be a concern if your application references JSP page implementation classes in unnamed packages, or if you install WebSphere Application Server Version 4.x EAR files (deployed in Version 4.x with the JSP Precompile option), in Version 5.x. You need to recompile all JSP pages when migrating from WebSphere Application Server Version 5.x.

JSP migration might be a concern if your application references JSP page implementation classes in unnamed packages, or if you install WebSphere Application Server Version 4.0.1 EAR files (deployed in Version 4.0.1 with the JSP Precompile option), in Version 5.x. You need to recompile all JSP pages when migrating from WebSphere Application Server Version 5.x.

Follow these steps if migration issues apply to your Web application:

Procedure

  1. If a migrated application references internal servlets, enabled or disabled the functionality through the IBM WebSphere Extensions XMI file, ibm-web-ext.xmi, located in each Web module WEB-INF directory or by using assembly tools. Examples of this are fileServing and serveServletsByClassName.
  2. Use WebSphere Application Server Version 5.x package names for any WebSphere Application Server Version 4.x internal servlets, which are implemented in your application.

    To bypass the errors, and to enable the serving of static files from the root context, WebSphere Application Server Version 4.x users are advised to open a Web deployment descriptor editor using an assembly tool and select File serving enabled on the Extensions tab.

  3. Migrate servlets that extend PageListServlet and rely on configuration information in the associated XML servlet configuration file. In Version 4.0.1, the XML servlet configuration file provides configuration data for page lists and augments servlet configuration information. This file is named as either servlet_class_name.servlet or servlet_name.servlet, and is stored in the same directory as the servlet class file.
  4. Add the Web container custom property, com.ibm.ws.webcontainer.contenttypecompatibility, with a value of V4, V5, or V6. The value is determined by which version the application is dependant on. See Modifying the default Web container configuration for details on how to modify this custom property. Because this property is a global setting, you must consider the effect on other applications.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tweb_migrate2
File name: tweb_migrate2.html