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

Programming and Management Features
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-003
4-8
Reserved Cookie Names
Reserved Cookie Names
The cookie names JSESSIONID, JSESSIONIDSSO, NSJSPADMINSSO, and
iTPWebSessionId are reserved for internal use. According to the servlet API the
name of the 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 (using the HTTPS protocol) with client-
side certificates passed to the server.
JMX Based Administration
NSJSP allows administering container objects using JMX technology to manage
internal objects (for example, Servers, Services, Hosts, Contexts, Loggers, and other
resource entities).These objects are administered using the admin web application
which is described in admin Web Application on page 4-9.
In prior releases, you were required to bring down the entire NSJSP container and
change the configuration file (iTP_server.xml) to modify container objects. With the
support of JMX MBeans for manageability you can modify objects while the container
is running. Modifying objects online enhances the NSJSP container's availability.
The container objects you can administer online using JMX technology are:
•
Server Object on page C-1
•
Service Object on page C-2
•
Connector Object on page C-2
•
Engine Object on page C-5
•
Host Object on page C-6
•
Context and Default Context Objects on page C-8
•
Loader Object on page C-11
•
Logger Object on page C-12
•
Manager Object on page C-13
•
Resources on page C-16
•
Realm Object on page C-21
•
Valve Object on page C-27
For detailed information about the objects, see Appendix C, NSJSP Container Objects.