NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide

Introduction to NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
1-16
NSJSP Architecture
source of the request, such, the web client or the Apache Web Server. After sending
the response, the thread is free to process a new message.
NSJSP Architecture
This section discusses the NSJSP architecture.
HTTPD processes convert the HTTP or Hypertext Transfer Protocol Secure (HTTPS)
requests into a set of variables, including environment, HTTP header, and Pathway
variables, sets their values, and passes them to the NSJSP processes either through
Pathsends or the file system API. The NSJSP connector receives the request data
from the HTTPD processes through the NSJSP connector's $RECEIVE, which is an
Interprocess Communication (IPC) request queue through which NSJSP processes
receive messages. The NSJSP connector reads the message contents from
$RECEIVE, extracts the necessary HTTP request data from the message, and passes
the message contents to the Catalina container.
The Catalina container processes the requests it receives from the NSJSP connector,
and sends the response back to the NSJSP connector. The NSJSP connector builds a
message from the response data returned by Catalina, and returns it to HTTPD.
Subsequently, HTTPD sends the response to the originator of the request.
Figure 1-9 illustrates the NSJSP architecture.