WebSphere Application Server enables you to achieve "write once, use everywhere" for the development of Servlets. The product includes a Java-based Servlet engine that is independent of the WEB server and the operating system on which it is based. WebSphere Application Server provides the option of a server plug-in that is compatible with most popular application design interfaces (APIs). The supported WEB servers are:
IBM HTTP Server
Apache Server
Domino
Lotus Domino Go Webserver
Netscape Enterprise Server
Netscape FastTrack Server
Microsoft Internet Information Server
- In addition to the Servlet engine and plug-ins, WebSphere Application Server also provides:
1. JavaSoft Java Servlet API implementations, and extensions and additions to these APIs.
2. Examples and documentation, sample Servlets, and Web site applications demonstrate simple and advanced techniques. Online and printable documents for you to get started quickly and to help you master the use of server advanced features demonstrates the basic classes and their extended sample applications.
3. WebSphere Application Server Manager, using the graphical interface, easy to:
(1) Setting options for local and remote Servlet loading
(2) Setting initialization parameters
(3) Managing Servlets
(4) Specifying a Servlet alias
(5) Creating a Servlet chain and filtering
(6) Enable Lightweight Directory Access Protocol (LDAP) directory support
(7) Record Servlet messages
(8) Enable JVM debugging
(9) Monitoring resources used by WebSphere application servers
(10) Monitor mounted servlet, active servlet session, and JDBC connection
(11) Control errors, events, anomalies, and log output
(12) Creating dumps and data snapshots
(13) Dynamically enable and disable tracing
4. Cache and re-use connection management functions with jdbc-subordinate database connections. When a Servlet requires a database connection, it
Can be obtained from a buffer pool of available connections, eliminating the overhead required to open a new connection for each request.
5. Additional Java classes, followed by the JavaBeans specification, allow programmers to access the jdbc-subordinate database. When the number of relationships used is hidden
These data access beans provide enhanced functionality when it comes to the complexity of the library. They can be used in a visual integrated development environment.
6. JSP dynamic page content support. JSP technology enables you to generate dynamic Web pages from server-side scripting. The result is a
Rendering logic (for example, HTML code that defines the structure and appearance of the Web site) is separated from the business logic (for example, accessing the database for Java-encoded information to be displayed on the Web site). For flexibility, JSP files can include any combination of directly inserted Java:<servlet> tags, NCSA tags, and JavaBean.
7. Enable directory services supported by LDAP (Lightweight Directory Access Protocol).
8. For integrating WebSphere application servers and Web servers (such as Apache server) into the Tivoli Management Environment (Tivoli
Management environment) for distributed monitoring and operation of the module and command line interface. Tivoli modules are not distributed with WebSphere application servers, please visit the Web site (http://www.software.ibm.com/webservers/appserv/) for more information.
The support of WebSphere Application server to JSP is implemented by JSP processor. When you install a WebSphere application server on a Web server, the configuration of the Web server is set to pass the HTTP request to the WebSphere application server for the JSP file (that is, the. jsp file name extension). The WebSphere Application server configuration is set to pass the JSP file to its JSP processor (Pagecompile).
The JSP processor creates and compiles a Servlet for each JSP file. The processor also generates two files for each JSP file:
(1) Java file: Contains Java language code that can be used for servlets;
(2) class file: a compiled Servlet.
The JSP processor places the. Java and. class files under Directory Servlets\pagecompile\jsp_file_path, where Jsp_file_path is the directory path where the JSP source files reside. For example, if the JSP file is in the Websphere\appserver\samples\webbank directory, the. Java and. class files are in websphere\appserver\servlets\pagecompile\ Websphere\app Server\samples\webbank directory: Java and. class files have the same file name. The processor uses a naming convention that includes adding an underscore character and a suffix to the JSP file name. For example, if the JSP file name is login.jsp, the resulting file is _login_xjsp.java and _login_xjsp.class.
Like all Servlets, a servlet generated by a JSP file is a subclass or descendant of the Javax.servlet.http.HttpServlet class. If the Servlet class is part of a package, the servlet Java code contains import statements for some required classes and package statements. If the JSP file contains JSP syntax (such as directives and scriptlets), the JSP processor translates the JSP syntax into equivalent Java code. If the JSP file contains HTML tags, the processor adds Java code so that the Servlet can output HTML one character after another.
websphere--Basic Features
