iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Using NonStop Servlets for JavaServer Pages With
The iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
9-10
NonStop Servlets for JavaServer Pages in The iTP
WebServer Architecture
•
Add the context path in the iTP_server.xml file. Use the WAR file name, minus
the.war extension, eg:
<Context path="/chat" docbase = "webapps/myapp1"> <\Context>
•
Add the Filemap directive to the servlet.config file, eg:
Filemap /myapp1 $server_objectcode
•
Restart servlet.ssc and the iTPSecure WebServer to deploy the WAR file.
NonStop Servlets for JavaServer Pages in The iTP
WebServer Architecture
This section contains background information about the NonStop Servlets for
JavaServer Pages architecture. The iTP Secure WebServer implementation is a multi-
threaded out-of-process servlet container; a Java web container (with web applications)
that runs in a Java Virtual Machine (JVM) outside of the iTP Secure WebServer httpd
process.
This new architecture is shown in Figure 9-3, iTP WebServer Servlet Architecture
.
In essence, the iTP Secure WebServer provides the same JVM functionality as any other
J2EE implementation, but is unique in its ability to scale across multiple CPUs to
provide a NonStop
TM
computing environment.
The iTP Secure WebServer process can be installed across any number of CPUs. It is
recommended to have three httpd processes running in any one CPU; others in other
CPUs can be used for load balancing, scaling to meet required throughput, or backups
for fault tolerance.
Each web container can contain a number of applications, each with their own servlets,
JSP, and other resources. These containers are accessible by any httpd process running
on any CPU. The containers and the httpd processes are part of the Pathway TS/MP 2.0
environment.
The ITP Secure WebServer software, which is inherently scalable and reliable, enables
the creation of Java servlets that can take advantage of the database and transaction
services infrastructure of the Compaq NonStop
TM
Himalaya server. Java servlets are
implemented as Compaq NonStop TS/MP server processes that can be replicated and
automatically load balanced across multiple processor nodes for scalable throughput.
Consequently, large volumes of servlet-based web transactions can be executed
concurrently to maintain consistent response times.
The complete environment is further enhanced by the addition of Parallel Library
TCP/IP (TCP/IP/PL) support. The architecture introduced by the NonStop™ Himalaya
S-series servers allows all processors in a system to access an adapter. Parallel Library
TCP/IP takes advantage of this architecture by using the communications adapter and
the ServerNet™ cloud to route packets directly to the processor containing the
application. By directly routing packets to the correct processor from the adapter,
Parallel Library TCP/IP eliminates the message-system hop that occurred between
processes in the conventional TCP/IP architecture.