Configure and implement page lists

You can define PageListServlet configuration information in the IBM Web Extensions file. The IBM Web Extensions file is created and stored in the Web Applications archive (WAR) file by the IBM WebSphere application assembly tool (AAT).

To configure and implement page lists, perform these steps:

1. Start the Application Assembly Tool.

2. Open your WAR file.

3. Click the PageList Extensions tab to configure page list information.

4. Add the callPage() method to your servlet to invoke a JavaServer Page (JSP) file in response to a client request.

   The callPage() method can be invoked in one of these ways:

     callPage(String pageName,
              HttpServletRequest request,
              HttpServletResponse response)

   or

     callPage(String mlName,
              String pageName,
              HttpServletRequest request,
              HttpServletResponse response)

   where the method arguments are:

   • mlName is a markup language type
   • pageName is a page name defined in the PageListServlet configuration
   • request is the HttpServletRequest object
   • response is the HttpServletResponse object

5. Use the PageList Servlet client type detection support to determine the markup language type a calling client requires for the response.

   In addition to providing the page list mapping capability, the PageListServlet also provides Client Type Detection support. A servlet determines the markup language type that a calling client needs in the response, using the configuration information in the client_types.xml file. For more information, see client_types.xml.

   Client type detection support allows a servlet, extending the PageListServlet, to call an appropriate JSP file. The servlet invokes the callPage() method, which calls a JSP file based on the markup-language type of the request.