The current 3.0x WebSphere deployment is very similiar to the Java Servlet API 2.2 technique except that .war files are not supported. You have to create an application path (or use the default application path). You then have to put the class file in a subdirectory structure that mirrors the package structure. You can then use the WebSphere Administrative Console to configure the servlet. Alternatively, you can use a file named
in the application directory to describe the servlet and parameters; this is similiar to the Java Servlet 2.2 deployment descriptor and is described further in the WebSphere XML configuration manual.
|Last updated 12/27/1999 10:16:10 PM|