NonStop Servlets for JSP System Administrator's Guide

Programming and Management Features
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-001
4-8
Reserved Cookie Name
Reserved Cookie Name
The cookie names JSESSIONID, JSESSIONIDSSO, and iTPWebSessionId are
reserved for internal use. According to the Servlet API 2.3 the name of the session
tracking cookie must be JSESSIONID and the name of the session tracking parameter
used in the URL rewriting must be jsessionid.
javax.servlet.request.X509Certificate
javax.servlet.request.X509Certificate returns an array of one object of
type java.security.cert.X509Certificate that is the leaf certificate of the
client certificate chain for all secure requests (via the HTTPS protocol) with client-side
certificates passed to the server.
The NSJSP Manager Web Application
NSJSP provides a command-line utility, nsjsp_manager, to manage NSJSP in the
iTP WebServer multi-process environment. The nsjsp_manager provides a text-
based menu in a script-based interface for an administrator user to manage
applications from the OSS shell environment.
You need to configure a user name and password entry with the manager role in the
realm being used with the NSJSP container. For security reasons, there is no pre-
configured entry with the manager role in any of the realms. You must manually add an
entry with the manager role into the realm being used in your NSJSP environment. See
Configuring Realms on page 3-19 for more details on how to configure realms.
The default Realm configuration in the iTP_server.xml file uses a MemoryRealm
which reads the username, password and role information from the
iTPWS_INSTALL_DIR/servlet_jsp/conf/tomcat-users.xml file.
To run the nsjsp_manager program, run the commands under OSS as shown in
Example 4-2:
Note. The nsjsp_manager utility only manages the currently running SERVLET ServerClass
processes. It does not modify configuration information. It should therefore be used only as an
aid in your deployment process and NOT as a deployment tool. So if you make any changes
via the nsjsp_manager utility to a running NSJSP environment, ensure that the configuration
files are changed accordingly. Otherwise your NSJSP environment could become inconsistent
if you have Dynamic SERVLET ServerClass processes (NumStatic < MaxProcesses) or if a
new SERVLET ServerClass process gets started, as in the case of an error and auto-restart
via NonStop TS/MP (PathWay).
Example 4-2. Running the nsjsp_manager Program Using OSS
osh> cd /usr/tandem/webserver/bin
osh> ./nsjsp_manager