InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.9: Administering servlets (overview) >
6.6.9.1: Administering servlets with the Java administrative console >
6.6.9.1.1: Configuring new servlets with the Java administrative console

6.6.9.1.1: Configuring new servlets with the Java administrative console

The product offers several ways to configure new servlets:

  • By clicking Console -> Tasks -> Add a Servlet from the console menu bar.
  • By clicking Add a Servlet from the drop-down list on the Wizards toolbar button.
  • Using menus on resources in the Topology and Type trees (see Related information)

The first two methods lead to the Add a Servlet task wizard, for which detailed help is provided here.

  1. Follow the wizard instructions. On the first page, specify whether you want to browse for servlet files or configure a servlet without really having its class files in place yet.

    If you are adding a WebSphere internal servlet to a Web application, then specify that you do not want to browse for files.

  2. Click Next to proceed. On the second page, specify the Web application to which the servlet will belong.

  3. Click Next to proceed. On the third page, specify the type of servlet to configure.

    If this is your own servlet code, specify Create User-Defined Servlet. Otherwise, specify to add one of the "internal servlets" that ship with WebSphere Application Server to support various functions:

    • File servlet
    • Enable Serving Servlets by Classname (adds invoker servlet)
    • JSP enabler (adds the JSP processor servlets)
    • Chainer servlet
    See article 4.2.1.2.3 for a detailed description of each internal servlet.

  4. If you selected an internal servlet other than the Chainer servlet, you can finish the wizard now. Otherwise, click Next to proceed and specify:

    • A name by which to administer the servlet.

    • The Web application to which it will belong.

    • An optional description of the servlet.

    • The class name of the servlet.

    • The Web Paths by which the servlet can be accessed. For example, if the servlet can be accessed by http://myhostname/myServlet, specify /myServlet.

    If you are configuring a Chainer servlet, name it, supply any initial parameters, and specify the Web paths by which it can be accessed (see above).

  5. Click Next to proceed. Specify additional servlet properties or accept the default values.

  6. Click Finish.

The product offers several ways to configure new servlets:

  • By clicking Console -> Wizards -> Add a Servlet from the console menu bar.
  • By clicking Add a Servlet from the drop-down list on the Wizards toolbar button.
  • Using menus on resources in the tree view (see Related information)

The first two methods lead to the Add a Servlet task wizard, for which detailed help is provided here.

  1. Follow the wizard instructions. On the first page, specify whether you want to browse for servlet files or configure a servlet without really having its class files in place yet.

    If you are adding a WebSphere internal servlet to a Web application, then specify that you do not want to browse for files.

  2. Click Next to proceed. On the second page, specify the Web application to which the servlet will belong.

  3. Click Next to proceed. On the third page, specify the type of servlet to configure.

    If this is your own servlet code, specify Create User-Defined Servlet. Otherwise, specify to add one of the "internal servlets" that ship with WebSphere Application Server to support various functions:

    • File servlet
    • Enable Serving Servlets by Classname (adds invoker servlet)
    • JSP enabler (adds the JSP processor servlets)
    • Chainer servlet
    See article 4.2.1.2.3 for a detailed description of each internal servlet.

  4. If you selected an internal servlet other than the Chainer servlet, you can finish the wizard now. Otherwise, click Next to proceed and specify:

    • A name by which to administer the servlet.

    • The Web application to which it will belong.

    • An optional description of the servlet.

    • The class name of the servlet.

    • The Web Paths by which the servlet can be accessed. For example, if the servlet can be accessed by http://myhostname/myServlet, specify /myServlet.

    If you are configuring a Chainer servlet, name it, supply any initial parameters, and specify the Web paths by which it can be accessed (see above).

  5. Click Next to proceed. Specify additional servlet properties or accept the default values.

  6. Click Finish.

Go to previous article: Administering servlets with the Java administrative console Go to next article: Administering servlets with the Web console

 

 
Go to previous article: Administering servlets with the Java administrative console Go to next article: Administering servlets with the Web console