Default Application

 

WAS provides a default configuration that administrators can use to verify that the Application Server is running. When the product is installed, it includes an appserver called server1 and an enterprise application called Default Application.

Default Application contains a Web module called DefaultWebApplication and an enterprise bean Java archive (JAR) file called Increment. The Default Application provides a number of servlets, described below. These servlets are available in the product.

For additional code examples, visit the Samples Gallery. Learn how to locate and install the Samples Gallery by viewing the Samples Gallery reference page.

 

Snoop servlet

Use the Snoop servlet to retrieve information about a servlet request. This servlet returns the following information:

• Servlet initialization parameters
• Servlet context initialization parameters
• URL invocation request parameters
• Preferred client locale
• Context path
• User principal
• Request headers and their values
• Request parameter names and their values
• HTTPS protocol information
• Servlet request attributes and their values
• HTTP session information
• Session attributes and their values

The Snoop servlet includes security configuration so that when WebSphere Security is enabled, clients must supply a user ID and password to initiate the servlet.

The URL for the Snoop servlet is: http://localhost:9080/snoop/.

 

HelloHTML servlet

Use the HelloHTML pervasive servlet to exercise the PageList support provided by the WebSphere Web container. This servlet extends the PageListServlet, which provides APIs that allow servlets to call other Web resources by name or, when using the Client Type detection support, by type.

You can invoke the Hello servlet from an HTML browser, speech client, or most Wireless Application Protocol (WAP) enabled browsers using the URL: http://localhost:9080/HelloHTML.jsp.

For transitioning users: The PageList Servlet custom extension is deprecated in WAS V6.1 and will be removed in a future release. Re-architect your legacy applications to use javax.servlet.filter classes instead of com.ibm.servlet classes. Starting from the Servlet 2.3 specification, javax.servlet.filter classes you can intercept requests and examine responses. You can also use javax.servlet.filter classes to achieve chaining functionality, as well as embellishing or truncating responses.trns

 

HitCount application

Use the HitCount demonstration application to demonstrate how to increment a counter using a variety of methods, including:

• A servlet instance variable

• An HTTP session

• An enterprise bean

You can instruct the servlet to execute any of these methods within a transaction that you can commit or roll back. If the transaction is committed, the counter is incremented. If the transaction is rolled back, the counter is not incremented.

The enterprise bean method uses a container-managed persistence enterprise bean that persists the counter value to a Cloudscape database. This enterprise bean is configured to use the Default Datasource, which is set to the DefaultDB database.

When using the enterprise bean method, you can instruct the servlet to look up the enterprise bean, either in the WebSphere global namespace, or in the namespace local to the application.

The URL for the HitCount application is: http://localhost:9080/HitCount.jsp.

---

 

Related concepts

Web applications
Web modules
Class loaders

 

Related tasks

Task overview: Developing and deploying Web applications

 

Related Reference

Web applications: Resources for learning

 

Related information

Servlets

 

Reference topic