NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide Abstract NonStop™ Servlets for JavaServer Pages (NSJSP) is a container that runs Java servlets and JavaServer Pages (JSPs) that are platform-independent server-side programs, which programmatically extend the functionality of web-based applications by providing dynamic content from a web server to a client browser over the HTTP protocol. Product Version NonStop Servlets for JavaServer Pages 6.
Document History Part Number Product Version Published 596210-001 NonStop Servlets for JavaServer Pages 6.1 (T1222H60^AAN) June 2010 596210-002 NonStop Servlets for JavaServer Pages 6.1 (T1222H60^AAN) November 2011 596210-005 NonStop Servlets for JavaServer Pages 6.1 (T1222H60^AAN) March 2012 596210-006 NonStop Servlets for JavaServer Pages 6.
Legal Notices Copyright 2012 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide Glossary Index Examples Figures Legal Notices What’s New in This Manual xv Manual Information xv New and Changed Information xv About This Manual xvii Who Should Read This Guide xvii Organization of This Guide xviii Related Manuals xix Online Resources xxi Notation Conventions xxii Abbreviations xxvii HP Encourages Your Comments xxx 1.
Contents 3. Configuring NSJSP Running the setup Script 2-14 Creating an NSJSP Installation 2-16 Verifying the NSJSP Installation 2-18 NSJSP Installation Directory Structure 2-20 Creating an NSJSP Manager Installation 2-21 Verifying the NSJSP Manager Application Installation 2-23 Updating an NSJSP Installation 2-24 Removing an NSJSP Configuration 2-25 Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment 2-26 3.
5.
Contents 6. Debugging NSJSP Log Rollover 5-6 Logging Configuration 5-9 Configuring Handlers 5-10 Configuring Loggers 5-13 Configuring the NSJSP Formatter Class 5-14 Configuring for Log Rollover 5-15 Configuring the logging.properties File 5-20 Configuring Logging for the NSJSP Container and Web Applications Log Files Related to NSJSP 5-27 The out and err Log Files 5-27 Log File Created by JULI 5-28 Programming Considerations for Logging 5-28 LogFactory 5-28 Log 5-29 Commons Logging 5-30 5-24 6.
A.
Contents Example 3-4. Example 3-5. Example 3-6. Example 3-7. Example 3-8. Example 3-9. Example 3-10. Example 3-11. Example 3-12. Example 3-13. Example 3-14. Example 3-15. Example 3-16. Example 3-17. Example 3-18. Example 3-19. Example 3-20. Example 3-21. Example 3-22. Example 3-23. Example 3-24. Example 3-25. Example 3-26. Example 3-27. Example 3-28. Example 3-29. Example 3-30. Example 3-31. Example 3-32. Example 3-33. Example 3-34. Example 3-35. Example 3-36. Example 3-37.
Contents Example 3-38. Example 3-39. Example 3-40. Example 3-41. Example 3-42. Example 3-43. Example 3-44. Example 3-45. Example 3-46. Example 3-47. Example 3-48. Example 3-49. Example 3-50. Example 3-51. Example 3-52. Example 3-53. Example 3-54. Example 3-55. Example 3-56. Example 3-57. Example 3-58. Example 3-59. Example 3-60. Example 3-61. Example 3-62. Example 3-63. Example 3-64. Example 3-65. Example 3-66. Example 3-67. Example 3-68. Example 3-69.
Contents Example 3-70. Example 3-71. Example 3-72. Example 3-73. Example 3-74. Example 3-75. Example 3-76. Example 3-77. Example 3-78. Example 3-79. Example 8-1. Example 8-2. Example 8-3. Example 8-4. Example 8-5. Example 8-6. Example 8-7. Example 8-8. Example 8-9. Example 8-10. Example 8-11. Example 8-12. Example 8-13. Figures An Arglist from a servlet.
Contents Figure 1-6. Figure 1-7. Figure 1-8. Figure 1-9. Figure 2-1. Figure 2-2. Figure 2-3. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Figure 4-10. Figure 4-11. Figure 4-12. Figure 4-13. Figure 4-14. Figure 4-15. Figure 4-16. Figure 4-17. Figure 4-18. Figure 4-19. Figure 4-20. Figure 4-21. Figure 4-22. Figure 4-23.
Contents Figure 4-24. Figure 4-25. Figure 4-26. Figure 4-27. Figure 4-28. Figure 4-29. Figure 4-30. Figure 4-31. Figure 4-32. Figure 4-33. Figure 4-34. Figure 4-35. Figure 4-36. Figure 4-37. Figure 4-38. Figure 4-39. Figure 4-40. Figure 4-41. Figure 4-42. Figure 4-43. Figure 4-44. Figure 4-45. Figure 4-46. Figure 4-47. Figure 4-48. Figure 4-49. Figure 4-50. Figure 4-51. Figure 4-52. Figure 4-53. Figure 4-54. Figure 4-55. Figure 4-56. Figure 4-57. Figure 4-58. Figure 5-1. Figure 7-1.
Tables Contents Figure 7-2. Figure 7-3. Figure 8-1. Figure 8-2. Figure 8-3. Figure 8-4. Figure A-1. Figure A-2. Figure A-3. Figure A-4. Figure A-5. Figure A-6. Sample conf Directory Contents After NSJSP 6.1 Installation NSJSP 6.0 and NSJSP 6.
Tables Contents Table 4-3. Table 4-4. Table 4-5. Table 4-6. Table 4-7. Table 4-8. Table 4-9. Table 4-10. Table 4-11. Table 4-12. Table 4-13. Table 4-14. Table 4-15. Table 4-16. Table 4-17. Table 4-18. Table 4-19. Table 4-20. Table 4-21. Table 4-22. Table 4-23. Table 4-24. Table 4-25. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 5-7. Table 5-8. Table 5-9. Table 7-1. Table 7-2. Table 7-3. Table 7-4.
Contents Table 7-5. Table 7-6. Table 7-7. Table 7-8. Table 7-9. Table 7-10. Table 7-11. Table 7-12. Table 8-1. Table 8-2. Table 8-3. Table 8-4. Table 8-5. Table 8-6. Table 8-7. Table 8-8. Table 8-9. Table 8-10. Table A-1. Table A-2. Table A-3. Table A-4. Table A-5. Differences in the NSJSP 6.0 and NSJSP 6.1 servlet.
Contents NonStop Servlets for JavaServer Pages (NSJSP) 6.
What’s New in This Manual Manual Information NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide Abstract NonStop™ Servlets for JavaServer Pages (NSJSP) is a container that runs Java servlets and JavaServer Pages (JSPs) that are platform-independent server-side programs, which programmatically extend the functionality of web-based applications by providing dynamic content from a web server to a client browser over the HTTP protocol.
What’s New in This Manual New and Changed Information Changes to 596210-002 Manual: Added Debugging NSJSP chapter. NonStop Servlets for JavaServer Pages (NSJSP) 6.
About This Manual This guide describes the architecture of NSJSP 6.1, procedures for installing, updating, and removing NSJSP 6.1 and NSJSP Manager, the management tasks you can perform using the NSJSP Manager and Admin Web applications, how to configure NSJSP, logging functionality in NSJSP, a comparison of NSJSP 5.0, 6.0, and 6.1, considerations before migrating user applications from NSJSP 5.0 or NSJSP 6.0 to NSJSP 6.
Organization of This Guide About This Manual Organization of This Guide Chapter Description 1, Introduction to NSJSP Provides an overview of the NSJSP product. This chapter also describes the NSJSP architecture and its features. 2, Installing NSJSP Provides the procedures to install, verify, and remove NSJSP and the NSJSP Manager. This chapter also lists the modifications made to support multiple NSJSP installations. 3, Configuring NSJSP Describes the files for configuring NSJSP in detail.
Related Manuals About This Manual Related Manuals NonStop Servlets for JavaServer Pages (NSJSP) Manuals For information about the features of the NonStop Servlets for JavaServer Pages (NSJSP) 6.0, see NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide. iTP manuals For more information specific to the iTP Secure WebServer environment, see: iTP Secure WebServer System Administrator’s Guide describes how to install, configure, and manage the iTP Secure WebServer.
Open System Services (OSS) Manuals About This Manual Open System Services (OSS) Manuals For information specific to the OSS environment, see: Open System Services User’s Guide describes the Open System Services (OSS) environment: the shell, file-system, and user commands. Open System Services Installation Guide describes how to install and configure the HP NonStop Kernel OSS environment.
NonStop SQL Manuals About This Manual NonStop SQL Manuals For information specific to the NonStop SQL environment, see: SQL/MP Reference Manual describes NonStop SQL/MP, the HP relational database management system that uses SQL to describe and manipulate data in a NonStop SQL/MP database. The manual includes information about SQLCI, the conversational interface to NonStop SQL/MP.
About This Manual Notation Conventions JavaServer Pages API Specification Version 2.1: http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described in Backup DAM Volumes and Physical Disk Drives on page 3-2.
About This Manual General Syntax Notation each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o.
About This Manual Notation for Messages lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
About This Manual Notation for Management Programming Interfaces Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters.
About This Manual Abbreviations Abbreviations This list defines abbreviations and acronyms used in this guide. Both industry-standard terms and HP terms are included. AWT. Abstract Windowing Toolkit ARPA. Advanced Research Project Agency ATP. Active Transaction Pages BSD. Berkeley Software Distribution C. Country CA. Certificate Authority CBC. Cipher Block Chaining CCITT. Consultative Committee for International Telegraph and Telephone CGI. Common Gateway Interface CN. Common Name CWD.
About This Manual Abbreviations HTML. HyperText Markup Language HTTP. HyperText Transfer Protocol HTTPD. HyperText Transfer Protocol Daemon IEEE. Institute of Electrical and Electronics Engineers IEN. Internet Engineering Note IP. Internet Protocol ISV. installation subvolume J2EE. Java 2 Enterprise Edition JAR. Java Archive Tool JDBC. Java DataBase Connectivity JDK. Java Development Kit JIT. Just-In-Time (Java compiler) JNDI. Java Naming and Directory Interface JNI. Java Native Interface JSP.
About This Manual Abbreviations NCSA. National Center for Supercomputing Applications NSJ. NonStop Java NSJSP. NonStop Servlets for JavaServer Pages O. Organization OLTP. Online Transaction Processing OSS. Open System Services OU. Organizational Unit PAID. Process Accessor ID PCT. Private Communication Technology PDF. Portable Document Format PEM. Privacy Enhanced Message PKS. Public Key Certificate Standard PPP. Point to Point Protocol QIO. Queued Input Output RFC. Request for Comments RLS.
About This Manual HP Encourages Your Comments SSI. Server Side Include SSL. Secure Sockets Layer ST. State TACL. Tandem Advanced Command Language TAL. Transaction Application Language Tcl. Tool Command Language Tcl/CGI. Tool Command Language/Common Gateway Interface TCP/IP. Transmission Control Protocol/Internet Protocol TS/MP. Transaction Services/Massively Parallel URI. Uniform Resource Identifier URL. Uniform Resource Locator WAR. Web Application Archive WID. WebSafe2 Interface Driver WISP.
1 Introduction to NSJSP This chapter describes NonStop Servlets for JavaServer Pages (NSJSP), its components, and its architecture. To understand NSJSP, prior knowledge of the following topics is required: Java Servlets and JavaServer Pages (JSP) A Java Servlet is a programming object that runs in a server application. It receives client requests, processes them, and generates responses. For more information on the Java Servlet 2.5 specification, see http://jcp.
Introduction to NSJSP Overview Overview NSJSP is a Java Servlets and JavaServer Pages (JSP) container available on HP NonStop operating systems. A servlet container provides an environment in which you can deploy, execute, and manage web applications based on servlets or JSPs. NSJSP is written in Java, and it offers a standards-based environment to host Java Servlet and JSP applications. NSJSP Product The NSJSP architecture is derived from the Apache Tomcat servlet container.
Introduction to NSJSP Installing NSJSP An implementation of the Java Servlets 2.5 and JSP 2.1 specifications. A platform to host applications developed using the Java Open Source frameworks, including: MyFaces - An Apache implementation of JavaServer Faces (JSF) Hibernate - A popular (Object Relational Mapping) ORM solution for database access. Apache Axis2 - An open source web services engine and framework.
Installing NSJSP Introduction to NSJSP Remove an NSJSP installation and optionally delete the installation directories and files. The following section describes the various installation scenarios.
Installing NSJSP Introduction to NSJSP An iTP Secure WebServer Environment Containing Older NSJSP Installations NSJSP 6.1 can coexist with other NSJSP 6.1 installations, and either an NSJSP 5.0 or an NSJSP 6.0 installation. As a result, you can install NSJSP 6.1 in an iTP Secure WebServer environment that includes one or more NSJSP 6.1 installations, and either an NSJSP 5.0 or an NSJSP 6.0 installation. However, you must install each NSJSP installation in a unique directory location. Note.
Installing NSJSP Introduction to NSJSP Figure 1-3. Multiple NSJSP Installations in an iTP Secure WebServer Environment HTTP Requests iTP Secure WebServer HTTPD HTTPD HTTPD $zweb Environment NSJSP 6.1 NSJSP 6.1 NSJSP 5.0/NSJSP 6.0 An iTP Secure WebServer Environment Configured for Online-Upgrade You can install NSJSP 6.1 in an iTP Secure WebServer environment that is configured for online-upgrade. Note. iTP Secure WebServer 7.0 and later versions provide the capability of online-upgrades.
Installing NSJSP Introduction to NSJSP Figure 1-4. NSJSP 6.1 in an iTP Secure WebServer Environment Configured for Online-Upgrade HTTP Requests PATHWAY DOMAIN iTP Secure WebServer HTTPD HTTPD HTTPD $zweb Environment HTTPD HTTPD HTTPD NSJSP 6.1 $yweb Environment You can also create multiple NSJSP 6.1 installations in this iTP Secure WebServer environment. However, each NSJSP installation requires a unique directory location.
Configuring NSJSP Introduction to NSJSP Figure 1-5. Multiple NSJSP Installations in an iTP Secure WebServer Environment Configured for Online-Upgrade HTTP Requests PATHWAY DOMAIN iTP Secure WebServer HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD NSJSP 6.1 $yweb Environment $zweb Environment NSJSP 6.1 NSJSP 6.1 For more information on installing NSJSP, see Chapter 2, Installing NSJSP. Configuring NSJSP An NSJSP installation includes a conf directory, which contains a servlet.config file.
Introduction to NSJSP Management in NSJSP An NSJSP installation also includes a server class for the NSJSP Admin Web application and the old Manager application (Manager Web Application). The configuration file for this server class is located in the conf directory within the NSJSP installation, and is called nsjspadmin.config.
Introduction to NSJSP Securing Web Applications Starting, Stopping, and Restarting the iTP Secure WebServer Because NSJSP installations are created in an iTP Secure WebServer environment, when the iTP Secure WebServer environment is stopped, started, or restarted, all the NSJSP installations in the iTP Secure WebServer environment are also stopped, started, or restarted respectively.
Introduction to NSJSP NSJSP Features NSJSP Features NSJSP is distinguished by the following key features: Scalability Scalability in NSJSP refers to its ability to increase its capacity to process a large number of servlet and JSP requests simultaneously, by adding resources, such as additional processes and logical processors, to a system.
NSJSP Features Introduction to NSJSP Starting with the NSJSP 6.1 release, you can install and manage NSJSP in an iTP Secure WebServer 7.0 environment that is configured for online-upgrade. For more information on the online-upgrade feature, see An iTP Secure WebServer Environment Configured for Online-Upgrade on page 1-6. Figure 1-6 illustrates NSJSP in an iTP Secure Webserver environment that is configured for online-upgrade. Figure 1-6.
Introduction to NSJSP Architecture Architecture This section discusses the relevant components of Apache Tomcat that will help describe how Apache Tomcat was ported onto the HP NonStop platform as NSJSP, and the NSJSP architecture. Apache Tomcat Components The connector component of Apache Tomcat provides the capabilities of a web server and the container component provides a servlets and JSP container. The connector and the container components are called Coyote and Catalina respectively.
Apache Tomcat Components Introduction to NSJSP Figure 1-7. Standalone Apache Tomcat Using the HTTP Connector HTTP/1.1 Network HTTP/1.1 HTTP Connector Connector threads Apache Tomcat Catalina Container (Servlet/JSP Container) Figure 1-8 illustrates the Apache Tomcat servlet container with the Apache Web Server. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Apache Tomcat Components Introduction to NSJSP Figure 1-8. Apache Tomcat with the Apache Web Server HTTP/1.1 Network HTTP/1.1 AJP 1.3 Apache Web Server AJP Connector Connector threads Catalina Container (Servlet/JSP Container) AJP 1.3 AJP Connector Apache Tomcat Connector threads Apache Tomcat Catalina Container (Servlet/JSP Container) The connector validates an incoming message from the web client or the web server for compliance with the respective protocol, such as, HTTP /1.1 or AJP1.3.
Introduction to NSJSP 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.
NSJSP Architecture Introduction to NSJSP Figure 1-9. NSJSP Architecture Network TCP/IP v6 CPU 0 1 CPU 1 2 CPU CPU23 CPU CPU 4 3 $zweb HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD HTTPD iTP Secure WebServer TS/MP or File Pathsend or File system system callsAPI NSJSP NSJSP NSJSP NSJSP NSJSP Installation In Figure 1-9, NSJSP architecture shows the following: An iTP Secure WebServer installation in a TS/MP environment with a PATHMON, called $zweb.
Introduction to NSJSP NSJSP Architecture 1. NonStop TCP/IPv6 distributes the HTTP(S) user requests across the HTTPD processes. 2. The HTTPD processes map the HTTP requests into a set of variables with values. This information is passed in a message to the NSJSP Server Class through a Pathsend or the File system API. 3. The NSJSP connector receives the request information from an HTTPD process and extracts the required HTTP request data from the message.
2 Installing NSJSP This chapter discusses the NonStop Servlets for JavaServer Pages (NSJSP) installation script and the prerequisites for NSJSP. This chapter also describes the procedures to install, update, and remove NSJSP and the NSJSP Manager. Note. NSJSP operates with both iTP Secure WebServer and iTP WebServer. Although this chapter primarily mentions the iTP Secure WebServer, those references apply to the basic iTP WebServer as well. You can install NSJSP in either version of the iTP WebServer.
Installing NSJSP Installing NSJSP from the CD JDBC/MX T2 or T4 driver Note. To run the sample Bank application, which is integrated with the NSJSP PAX, you must have the JDBC T2 or JDBC T4 driver installed on your system. Installing NSJSP from the CD This section describes the procedure to run the IPSetup program and the NSJSP 6.1 setup script.
Installing NSJSP Running the IPSetup Program The Welcome screen appears. Note. HP strongly recommends that you exit all Windows applications before running the IPSetup program. 5. Do one of the following: a. Click Cancel to exit the IPSetup program and close any other programs that are running. b. Click Next > to continue with the IPSetup program. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Installing NSJSP Running the IPSetup Program The Software License Agreement screen appears. 6. Review the License Agreement and do one of the following: a. If you do not want to accept the terms of the agreement, select I do not agree to the above conditions and click Cancel to exit the IPSetup program. b. To accept all the terms of the agreement, select I agree to the above conditions and click Next >. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Installing NSJSP Running the IPSetup Program The Placement Options screen appears. 7. Select one of the following as a target platform for your IP software: a. TNS/E for H-series and J-series. b. Workstation to install the IP on your workstation. 8. Do one of the following and click Next >: a. Select the Use DSM/SCM to complete installation on the host check box to launch the DSM/SCM planner interface after completing the IPSetup program. b.
Installing NSJSP Running the IPSetup Program The Product Selection screen appears. 9. From the Available Products: list, select NonStop Servlet for JavaServer Pages as the product you want to install. 10. Click Add->. The selected product moves to the Selected Products list. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Installing NSJSP Running the IPSetup Program 11. Click Next >. The Host Information screen appears. 12. Log on to the Host by performing the following steps: a. From the Host name: list, select the IP address of a host system where you want to place the selected product. Note. If the IP address of a Host system is not available in the Host name: list, type the IP address. b. Enter a user name and password. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Running the IPSetup Program Installing NSJSP c. Select the communication mode. Note. Starting with T0316H01^AAK (version 4.1.00.0), IPSetup supports two modes of communication: Telnet and Secure SHell (SSH). To use the SSH mode of communication, ensure that the SSH server is configured correctly and is running on the NonStop server. If the SSH server is not configured or not running on the NonStop server, you will not be allowed to proceed with this mode of communication.
Installing NSJSP Running the IPSetup Program The Host Target Settings screen appears. 1. Do one of the following: a. Accept the default location for the work subvolume and the subvolume where the existing files will be backed up from the work subvolume. b. Browse the location for a work subvolume and backup of your choice. Note. If you want to back up the existing files in the work subvolume to another subvolume, select the Back up existing host files to: check box. 2.
Installing NSJSP Running the IPSetup Program The Host File Placement screen appears. 3. Verify the location where the product files will be placed on the Host system and click Next >. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Installing NSJSP Running the IPSetup Program The Placement Manifest screen appears. 4. Verify the details displayed on the Placement Manifest screen and click Next >. If you select the Back up existing host files to: check box in the Host Target Settings screen, IPSetup backs up any existing files to the backup subvolume.
Installing NSJSP Running the IPSetup Program IPSetup then transfers the installation files to the work subvolume and creates DSVs and ISVs. It displays the Placement Status screen, which shows the progress throughout the entire placement process. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Installing NSJSP Running the IPSetup Program After transferring the installation files, the Placement Complete screen appears. 5. Complete your IPSetup program: a. Select the View the Readme File check box. b. Click Finish. The IPSetup program completes and opens the readme.txt file. The program saves the contents of the T1222PAX file in the version-specific OSS directory located at /, where: is the /usr/tandem/nsjsp directory.
Running the setup Script Installing NSJSP Note. The /usr/tandem/nsjsp directory is referred to as the directory throughout this chapter. After the NSJSP files are transferred to a NonStop system using the IPSetup program, complete the Running the setup Script on page 2-14 procedure to install NSJSP 6.1. Running the setup Script Run the setup script to complete the NSJSP 6.1 installation. By default, the script is located in the directory: / Note.
Running the setup Script Installing NSJSP in a Pathway domain that includes one or both of the following types of installations: one or more NSJSP 6.1 installations an NSJSP 5.0 installation or an NSJSP 6.0 installation For more information on these environments, see Installing NSJSP in Different Environments Using the setup Script on page 1-4. For more information on installing NSJSP, see Creating an NSJSP Installation on page 2-16.
Installing NSJSP Creating an NSJSP Installation Creating an NSJSP Installation After running the setup script at the OSS prompt, you must select the Create an NSJSP installation option to install NSJSP 6.1. Starting with the NSJSP 6.1 release, the setup script can be used to create multiple NSJSP 6.1 installations. To create an NSJSP installation, complete the following steps: 1. Run the setup script, as described in Running the setup Script on page 2-14. 2. To install NSJSP 6.
Installing NSJSP Creating an NSJSP Installation 9. Enter the NSJSP server class name for this installation or press Enter to use the displayed default. Note. The NSJSP server class name must start with a letter and must contain 1 to 11 alphanumeric or hyphen characters. 10. Enter the uniform resource identifier (URI) name for mapping requests to this installation or press Enter to use the displayed default.
Installing NSJSP Verifying the NSJSP Installation After you install NSJSP 6.1, the setup script prompts you to install the NSJSP Manager application, if it is not installed in the iTP Secure WebServer. If you have already installed the NSJSP Manager application, the script exits. To create an NSJSP Manager installation, complete the steps described in Creating an NSJSP Manager Installation on page 2-21. Verifying the NSJSP Installation After you have installed NSJSP 6.
Installing NSJSP Verifying the NSJSP Installation Figure 2-1 shows the NSJSP home page for a successful NSJSP 6.1 installation. Figure 2-1. The NSJSP 6.1 Home Page You can also verify the NSJSP 6.1 installation by accessing the NSJSP Admin Web application. To access the NSJSP Admin Web application, enter a URL in the following format: http://IP address:Port number//admin The NSJSP Admin login page appears. Note.
NSJSP Installation Directory Structure Installing NSJSP Figure 2-2. The NSJSP Admin Web Application Login Page NSJSP Installation Directory Structure Table 2-1 describes the NSJSP 6.1 installation directories located in the NSJSP home directory. Table 2-1. NSJSP 6.1 Installation Directories and Files (page 1 of 2) Directory Description README Contains information that will help you to set up an NSJSP environment. bin/ Contains JAR files that will be included in the classpath.
Creating an NSJSP Manager Installation Installing NSJSP Table 2-1. NSJSP 6.1 Installation Directories and Files (page 2 of 2) Directory Description temp/ Stores temporary working files. This directory is for NSJSP internal use. webapps/ Contains web applications included within NSJSP and user written web applications. work/ It is for internal use by the NSJSP servlet container. Creating an NSJSP Manager Installation NSJSP 6.1 introduces a new management application, called the NSJSP Manager.
Installing NSJSP Creating an NSJSP Manager Installation The script then displays the following message: The initial user name for the Admin and Manager applications is ‘admin’. Note. If you continue to install the NSJSP Manager application after the NSJSP 6.1 installation is complete, the setup script uses the same iTP Secure WebServer installation, JDBC/MX library, and NSJ directories that you specified during the NSJSP 6.1 installation. 8. Enter the password for the admin user.
Installing NSJSP Verifying the NSJSP Manager Application Installation Verifying the NSJSP Manager Application Installation After you have installed the NSJSP Manager application, the iTP Secure WebServer must be cold started for the changes to take effect. You can verify the installation by accessing the NSJSP Manager application login page. The setup script displays the URL of the login page after completing the installation. To access the NSJSP Manager application, complete the following steps: 1.
Installing NSJSP Updating an NSJSP Installation Figure 2-3. The NSJSP Manager Application Login Page Updating an NSJSP Installation The setup script includes an option to update an NSJSP installation with a later NSJSP version. Note. You must copy the new version of NSJSP to the directory. To update an existing NSJSP 6.1 installation, complete the following steps: 1. Run the setup script, as described in Running the setup Script on page 2-14. 2.
Installing NSJSP Removing an NSJSP Configuration Update successful. The iTP Secure Webserver needs to be restarted for the upgrade to take effect. Removing an NSJSP Configuration The setup script enables you to remove an NSJSP 6.1 configuration or an NSJSP Manager configuration from the iTP Secure WebServer installation using the Remove an NSJSP Configuration option. The setup script also provides the option to delete the NSJSP installation files and directories.
Installing NSJSP Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment The script then displays the following message: Before deleting ensure that this installation was not linked to another webserver. Do you want to delete the directory and its contents : 6. To remove the NSJSP 6.1 installation directory or the NSJSP Manager installation directory, and its contents, type y and press Enter. The NSJSP 6.
Installing NSJSP Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment Instead, the files are present in the conf directory within each NSJSP installation. The location of these NSJSP 6.1 installation-specific configuration files is /conf. Note. Within the same iTP Secure WebServer environment, configuration files for NSJSP versions earlier than NSJSP 6.1 will be present in the /conf directory.
Installing NSJSP Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment NonStop Servlets for JavaServer Pages (NSJSP) 6.
3 Configuring NSJSP This chapter describes how to configure NSJSP. This chapter assumes that you have installed NSJSP 6.1. For more information on Installing NSJSP, see Chapter 2, Installing NSJSP. This chapter discusses the following topics: Overview Configuration Files for the Server Classes Configuration Files for the Servlet Container Virtual Hosts Session Management Table 3-1 lists the terms and definitions used in this chapter. Table 3-1.
Overview Configuring NSJSP Table 3-1. Terms and Definition (page 2 of 2) Term Definition Admin Server Class Refers to one of the server classes configured with an installation of NSJSP. Each installation of NSJSP results in 2 server classes. One server class will host web applications and process requests for user applications and the other contains the Admin application and the old Manager Web Application. The server class that is used by the Admin application is referred to as the Admin Server Class.
Overview Configuring NSJSP Table 3-2. Configuration Files for Server Classes Configuration File Description Generic servlet.config Provides an iTP Secure WebServer with links to the installation-specific servlet.config files. It is common to all NSJSP installations. Installation-specific servlet.config Contains the server class specific information used to configure a servlet server class. For more information, see the definition for Servlet Server Class in Table 3-1. nsjspadmin.
Overview Configuring NSJSP Figure 3-1. Files used to Configure NSJSP 6.1 TS/MP Environment httpd.config iTP Secure Webserver NSJSP 5.0 or 6.0 NSJSP Environment servlet.config Generic servlet.config jdbc.config Installation specific servlet.config nsjspadmin.config NSJSP 6.1 A server.xml context.xml jdbc.config nsjspadmin.config Installation specific servlet.config NSJSP 6.1 B filemaps.config web.xml server.xml context.xml filemaps.config web.xml Figure 3-1 shows two NSJSP 6.
Configuring NSJSP Configuration Files for the Server Classes Note. You can use the default NSJSP configuration settings for development activities without making any changes. However, when deploying NSJSP in a production environment, the configuration might have to be modified to address the load, degree of fault tolerance in the production environment and other considerations.
The Generic servlet.config File Configuring NSJSP The Generic servlet.config File Table 3-4 provides an overview of the generic servlet.config file. Table 3-4. The Generic servlet.config File Location /conf Description Contains references to all the active NSJSP installations in an iTP Secure WebServer environment. A source directive is included for each active NSJSP installation in the iTP Secure WebServer environment.
The Installation-Specific servlet.config File Configuring NSJSP installation that was removed using the setup script may still be present, including its servlet.config file. However, the source directive for the installation would have been removed from the generic servlet.config file. That would be an example of an inactive NSJSP installation. The httpd.config file uses the source directive to access the generic servlet.config file as shown in the following example. Note.
The Installation-Specific servlet.config File Configuring NSJSP Example 3-3. An Installation-Specific servlet.config File # # # VERSION=6.1.0 # # The server_objectcode represents a SYMBOLIC LINK to your installed # copy of the JVM (default /usr/tandem/java/bin/java) # set server_objectcode $root/bin/instA.ssc # # The NSJSP installation directory. # set env(NSJSP_HOME) /usr/tandem/java/ ################################################################# # # Security Manager options.
The Installation-Specific servlet.config File Configuring NSJSP ################################################################# # # Set the JAVA_HOME and GUARDIAN_SUBVOL # set env(JAVA_HOME) /nsjsp/software/java6.0/java if {![info exists env(GUARDIAN_SUBVOL)]} { set env(GUARDIAN_SUBVOL) /G/system/zweb } ################################################################# # # The following code sets up the Java Specific class PATH variables into # a Tcl variable called JVCP.
The Installation-Specific servlet.config File Configuring NSJSP if {[info exists jdbcMx_LIB_PATH]} { if {[info exists jdbcMp_LIB_PATH]} { set NSJSP_DLL_PATH $env(NSJSP_HOME)/lib:$jdbcMx_LIB_PATH:$jdbcMp_LIB_PATH } else { set NSJSP_DLL_PATH $env(NSJSP_HOME)/lib:$jdbcMx_LIB_PATH } # # # # # Any custom classpaths can be added by uncommenting and modifying the next statement ("append USRCP ..."). append USRCP ":": # # Add region commands to deny access to internal Catalina Servlets.
The Installation-Specific servlet.config File Configuring NSJSP -Djava.io.tmpdir=$env(NSJSP_HOME)/temp \ org.apache.catalina.startup.Bootstrap start } ################################################################# # # Do an existence check on the nsjspadmin configuration # file (nsjspadmin.config). If it exists, source it in. # if { [file exists $env(NSJSP_HOME)/conf/nsjspadmin.config] } { source $env(NSJSP_HOME)/conf/nsjspadmin.
Configuring NSJSP The Installation-Specific servlet.config File Secure WebServer. In NSJSP, the server_objectcode is a symbolic link to the Java executable. For example, /usr/tandem/java/bin/java. Note. The value for this variable is set by the setup script. Do not modify this value. Example 3-4 shows a sample configuration of the server_objectcode variable. Example 3-4.
The Installation-Specific servlet.config File Configuring NSJSP Example 3-6 shows the default value of the JVM_POLICY_FILE variable. Example 3-6. The Default Value of the JVM_POLICY_FILE Variable set env(JVM_POLICY_FILE) $env(NSJSP_HOME)/conf/iTP_catalina.policy NSJSP_SECMGR_POLICY The value of this variable is the Java command-line argument that is used to indicate a security policy file. The value reads -Djava.security.policy==$env(JVM_POLICY_FILE).
Configuring NSJSP The Installation-Specific servlet.config File obtain the location of the JAAS configuration file. For more information on JAAS, see http://java.sun.com/javase/6/docs/guide/security/jaas/JAASRefGuide.html. Example 3-9 shows the default value of the JAAS_CONFIG_FILE variable. Example 3-9. The Default Value of the JAAS_CONFIG_FILE Variable # # NSJSP JAAS NonStopLoginModule configuration file. # set env(JAAS_CONFIG_FILE) $env(NSJSP_HOME)/conf/iTP_jaas.
The Installation-Specific servlet.config File Configuring NSJSP Example 3-11 shows the default value of the JAVA_HOME variable. Example 3-11. The Default Value of the JAVA_HOME Variable ################################################################# # # Set the JAVA_HOME and GUARDIAN_SUBVOL # set env(JAVA_HOME) /nsjsp/software/java6.
The Installation-Specific servlet.config File Configuring NSJSP Example 3-13 shows the default value of the USRCP variable. Example 3-13. The Default Value of the USRCP Variable # # # set Set the default value of the User ClassPath blank USRCP "" SERVLET_BANK The SERVLET_BANK variable is used to specify the name of the required database table in the format .. used in example bank application distributed with NSJSP.
Configuring NSJSP The Installation-Specific servlet.config File Example 3-14 shows the default value of the SERVLET_BANK variable. Example 3-14. Default Value of the SERVLET_BANK Variable ################################################################# # # Related to the BankDemo example application provided with NSJSP # # The value of SERVLET_BANK should be .. # Catalog and schema should have been created.
Configuring NSJSP The Installation-Specific servlet.config File JAVA_HOME The JAVA_HOME variable is mandatory and specifies the directory where NonStop Server for Java (NSJ) is installed. Example 3-17 shows the default value of the JAVA_HOME variable. Example 3-17. The Default Value of the JAVA_HOME Variable Env JAVA_HOME=$env(JAVA_HOME) JREHOME The JREHOME variable is mandatory and specifies the location of the Java Runtime Environment (JRE). Note. This variable is not mandatory in NSJ 6.
Configuring NSJSP The Installation-Specific servlet.config File BANK_CATALOG The BANK_CATALOG variable is set to the value of the $SERVLET_BANK variable. For more information, see SERVLET_BANK on page 3-16. Example 3-21 shows the default value of the BANK_CATALOG variable. Example 3-21. The Default Value of the BANK_CATALOG Variable Env BANK_CATALOG=$SERVLET_BANK NSJSP_CONFIG_FILE Specifies the NSJSP configuration file that is used by the NSJSP Manager.
Configuring NSJSP The Installation-Specific servlet.config File Xms Specifies the initial memory allocation pool (also called the heap) size that is allocated when NSJSP starts up. This value is set to the same value as Xmx. Xss Specifies the stack size. The default value is 128k.This value should be sufficient for most applications hosted on NSJSP. If you experience stack overflow exceptions in your application, consider increasing this value. Xnoclassgc Disables the class garbage collection.
Configuring NSJSP The Installation-Specific servlet.config File Example 3-25 shows the default value of the java.util.logging.manager variable. Example 3-25. The Default Value of the java.util.logging.manager Variable -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager java.util.logging.config.file Specifies the configuration file used by the LogManager. For more information about the logging configuration file, see Chapter 5, Logging in NSJSP.
Configuring NSJSP The Installation-Specific servlet.config File Example 3-28 shows the default value of the java.io.tmpdir variable. Example 3-28. The Default Value of the java.io.tmpdir Variable -Djava.io.tmpdir=$env(NSJSP_HOME)/temp catalina.home and catalina.base The catalina.home and catalina.base arguments are mandatory and specify the installation directory for NSJSP. The values for these variables must be the same. The catalina.
The Installation-Specific servlet.config File Configuring NSJSP browser as long as the browser is open. If sessions are configured to be persistent and to expire with short durations, then setting this attribute to true might improve performance. When setting this value to true, it is important that the date and time on the browser workstation match or is very close to that of the NonStop server where NSJSP is running.
Configuring NSJSP The Installation-Specific servlet.config File It is recommended that the com.tandem.servlet.nsjsp variable is set to true. Setting the variable to false might require additional changes to the configuration files, such as server.xml, because the default Tomcat behavior might require different configuration parameters than NSJSP. Note. To get pure Tomcat behavior, you can install Apache Tomcat on a NonStop server.
Configuring NSJSP The Installation-Specific servlet.config File Servlet is enabled by default. The JMXProxy is defined in the old manager application’s deployment descriptor (web.xml). Example 3-33 shows the configuration for JMX Proxy Servlet in the web.xml file. Example 3-33. Configuration for JMXProxyServlet in the web.xml file …. …. JMXProxy org.apache.catalina.manager.JMXProxyServlet …. ….
Configuring NSJSP The Installation-Specific servlet.config File Example 3-34 shows the default value of the SaveSessionOnCreation variable. Example 3-34. The Default Value of the SaveSessionOnCreation Variable -DSaveSessionOnCreation=false com.tandem.servlet.CONTEXT_PREFIXES This is the URI name that is specified during installation when you run the setup script. The value must begin with / followed by the URI name, which is made up of alphanumeric characters.
The Installation-Specific servlet.config File Configuring NSJSP Note. HP recommends that you set this value to a value greater than or equal to the ScriptTimeout value specified in the iTP Secure WebServer configuration. Note. If a negative value is set, and if there are multiple message exchanges between NSJSP and HTTPD, the NSJSP Connector aborts the message exchange if HTTPD does not respond to the message exchange immediately.
Configuring NSJSP The Installation-Specific servlet.config File The following are the configuration parameters defined by TS/MP for server classes. For more information on these parameters, see the NonStop TS/MP System Management Manual. The following descriptions are applicable to NSJSP only. NUMSTATIC and MAXSERVERS In the default configuration, both these parameters have the same value. This means there are no dynamic servers are configured for NSJSP.
The Installation-Specific servlet.config File Configuring NSJSP Example 3-35 shows the default configuration of the Region directive. Example 3-35. The Default Configuration of the Region Directive # # Add region commands to deny access to internal Catalina Servlets. # Region */servlet/org.apache.catalina.servlets.* { DenyHost * } Region */servlet/jsp/* DenyHost * } { The Filemap Directive The Filemap directive at the end of the servlet.
The nsjspadmin.config File Configuring NSJSP The nsjspadmin.config File Table 3-6 provides an overview of the nsjspadmin.config file. Table 3-6. Overview of the nsjspadmin.config File Location /conf Description Contains the configuration attributes for the Admin Server Class. The name of this server class is created by adding -adm to the servlet server class name, which is specified during the installation process.
The nsjspadmin.config File Configuring NSJSP Example 3-37. The nsjspadmin.config File # # VERSION=6.1.0 # # # The nsjspadmin_objectcode represents a SYMBOLIC LINK to your installed # copy of the JVM (default /usr/tandem/java/bin/java) # set nsjspadmin_objectcode $root/bin/instA.
Configuring NSJSP The nsjspadmin.config File Example 3-38 shows the installation-specific servlet.config file checking for the presence of the nsjspadmin.config file and sourcing the filemaps.config file, if available. Example 3-38. Checking for the presence of the nsjspadmin.config file and sourcing the nsjspadmin.config file in the servlet.config file ################################################################# # # Do an existence check on the nsjspadmin configuration # file (nsjspadmin.config).
The filemaps.config File Configuring NSJSP Filemaps The Filemap directives at the end of the nsjspadmin.config file indicate that all requests to both the admin and the old manager are also directed to the admin server class. Note. The manager application mentioned here is different from the new NSJSP Manager. For more information on the manager applications, see Chapter 4, Managing NSJSP. The filemaps.
Configuring NSJSP The filemaps.config File The filemaps.config file is only meant to contain Filemap definitions for specific user applications. The default Filemap definitions for the overall NSJSP installation are in the servlet.config and nsjspadmin.config files. Example 3-41 illustrates the usage of the filemaps.config file for specific user application Filemap definitions. Example 3-41.
The jdbc.config File Configuring NSJSP The jdbc.config File Table 3-8 provides an overview of the jdbc.config file. Table 3-8. The jdbc.config File Location /conf Description The file is source in, if present, by the servlet.config file and is used to configure certain variables to include the JDBC/MX and/or JDBC/MP configuration. One variable that is modified in the jdbc.config file is USRCP. For more information on USRCP, see The Installation-Specific servlet.config File on page 3-7).
Configuring NSJSP The jdbc.config File Example 3-42. The jdbc.config File # # VERSION=6.1.0 # ####################################################################### # # This file contains the JDBC/MP and JDBC/MX configuration. # # # # If the CLASSPATH contains sqlmp.jar and/or jdbcMx.jar, then first # add those to the User ClassPath TCL variable USRCP. # if { [info exists env(CLASSPATH)] } { foreach i [split $env(CLASSPATH) ":"] { if {[string first "sqlmp.
Configuration Files for the Servlet Container Configuring NSJSP Configuration Files for the Servlet Container This section describes the following configuration files: The server.xml File The context.xml File The web.xml File The server.xml File This section discusses only the elements that are used in the default server.xml file. Although the behavior of some of these components is the same as in Apache Tomcat, some components behave differently in NSJSP.
The server.xml File Configuring NSJSP Figure 3-3. The Element Hierarchy and Relationships in the server.xml file Server 1 n 1 Service GlobalNamingResource 1 1 1 1 Server Lifecycle Listener 1 Global Resources Lifecycle Listener 1 Store Config Lifecycle Listener 1 NSJSP Lifecycle Listener n Connector n Resources Jasper Listener 1 Listener Engine 1 1 1 n Realm Host n Valve In Figure 3-3, n represents one or more elements and 1 represents one element.
Configuring NSJSP The server.xml File Example 3-43. The server.xml File (page 1 of 2) PAGE 120The server.xml File Configuring NSJSP Example 3-43. The server.xml File (page 2 of 2)
The server.xml File Configuring NSJSP Table 3-10. Attribute List for the Server element Attribute Description Default value className Java class name for the implementation to use. This class must implement the org.apache.catalina.Server interface. If no class name is specified, the standard implementation will be used. org.apache.catalin a.core.StandardSer ver HP recommends that you do not change the value of this attribute.
The server.xml File Configuring NSJSP Table 3-11. Descriptions of Listeners configured as child elements of the Server element Listener Description Jasper Listener The Jasper Listener initializes the Jasper2 JSP engine before loading any web applications. The Jasper2 JSP engine is an implementation of the Java Server Pages 2.1 specification. The class name of the listener is org.apache.catalina.core.JasperListener. Server Lifecycle Listener The Server Lifecycle Listener initializes the MBeanServer.
Configuring NSJSP The server.xml File The GlobalNamingResources element in the default server.xml file defines a resource of type org.apache.catalina.UserDatabase. This resource is used by the UserDatabaseRealm that is nested in the Engine element. Example 3-44 shows the default value for the GlobalNamingResources element. Example 3-44. The Default Value for the GlobalNamingResources Element PAGE 124The server.xml File Configuring NSJSP Example 3-45. The Default Values for the Service Element PAGE 125The server.xml File Configuring NSJSP Table 3-12. Attribute List of the Service Element Attribute Description className The Java class name of the implementation to use. This class must Implement the org.apache.catalina.Service interface. If no class name is specified, the standard implementation will be used. Default value org.apache .catalina. core.Stand ardService HP recommends that this attribute not be modified.
The server.xml File Configuring NSJSP $RECEIVE file. The HTTPD component acts as the front-end web server and handles all the protocol validation and translation. After the protocol is validated, HTTPD extracts the necessary information and converts the information to a set of name value pairs. The name value pairs are then sent in messages to the NSJSP connector. The NSJSP connector assembles the request data from the messages with the name value pairs and continues with processing the request.
The server.xml File Configuring NSJSP Table 3-13. Attribute List for the Connector Element in NSJSP (page 1 of 2) Attribute Description allowTrace A Boolean value that can be used to enable or disable the TRACE HTTP method. If this attribute is not specified, it is set to false. emptySessionPath If set to true, all paths for session cookies will be set to /. If this attribute is not specified, it is set to false.
The server.xml File Configuring NSJSP Table 3-13. Attribute List for the Connector Element in NSJSP (page 2 of 2) Attribute Description maxHttpHeaderSize The maximum size of the request and response HTTP header, specified in bytes. If this attribute is not specified, it is set to 8192 (8 KB). maxThreads The maximum number of request processing threads to be created by this Connector. It also determines the maximum number of simultaneous requests that can be handled.
The server.
The server.xml File Configuring NSJSP JMX Connection Listener The com.tandem.servlet.JMXConnectionListener (JMX Connection Listener) has to be configured to accept JMX requests (over NonStop IPC) from the NSJSP manager application. The NSJSP manager communicates with server class instances using JMX and without this listener the NSJSP JMX components that accept JMX requests are not configured. Example 3-47 shows the default value for the JMX Connection Listener. Example 3-47.
The server.xml File Configuring NSJSP Example 3-48 shows the default values for the Engine element. Example 3-48. The Default Values for the Engine Element PAGE 132The server.xml File Configuring NSJSP Table 3-14. Attribute List for the Engine Element Attribute Description backgroundPro cessorDelay Represents the delay in seconds between the invocation of the backgroundProcess method on this engine and on its child containers, including all the hosts and contexts. Child containers methods will not be invoked if their delay value is not negative. This means that the child containers are using their own processing thread.
The server.xml File Configuring NSJSP The Context container backgroundProcess is invoked to perform session expiration and class monitoring. The backgroundProcess method for a container is invoked in a separate thread called the background processing thread. It is possible to have a separate thread for each of the containers. A backgroundProcessor thread is spawned if the container's backgroundProcessorDelay attribute has a positive value.
The server.xml File Configuring NSJSP Host The Host element represents a virtual host. One or more Host elements are nested inside an Engine element. One of the Host elements under an Engine must have a name matching the defaultHost attribute of that Engine. In the default server.xml file the value of the defaultHost attribute of the Engine element is localhost and there is only one Host configured with the name localhost. For more information on virtual hosts, see Virtual Hosts on page 3-73.
The server.xml File Configuring NSJSP Table 3-15 shows the attribute list for the Host element. Table 3-15. Attribute List for the Host Element (page 1 of 2) Attribute Description Default Value appBase The Application Base directory for this virtual host. This is the pathname of a directory that might contain web applications to be deployed on this virtual host. You may specify an absolute pathname for this directory, or a pathname that is relative to the directory.
The server.xml File Configuring NSJSP Table 3-15. Attribute List for the Host Element (page 2 of 2) Attribute Description Default Value name The network name for this virtual host. Regardless of the case used to specify the hostname, NSJSP will convert it to lower case internally. localhost One of the Hosts nested within an Engine must have a name that matches the defaultHost setting for that Engine. deployXML For a description of this attribute, see deployXML on page 3-58.
Configuring NSJSP The server.xml File Considerations for Configuring the Attributes of the Host Element It is important to understand the effect of the autoDeploy, unpackWARs and deployXML attributes with regard to the security of the NSJSP servlet container and application resources. autoDeploy Setting autoDeploy to true could result in the redeployment of an entire application, if any changes are made to watched application resources.
Configuring NSJSP The server.xml File There is a potential drawback to setting unpackWARs to false. A web application's static content will be read from the WAR file directly, instead of from the otherwise exploded directory. It is recommended that all static content be served by the iTP Secure WebServer and not by NSJSP. deployXML Set this attribute to false, if you want to disable parsing the context.xml file embedded inside the application (located at /META-INF/context.xml).
Configuring NSJSP The context.xml File must be configured for every configured Host element. The valve tracks all the requests flowing to the applications in that Host. This information is used for displaying application statistics in the new NSJSP Manager application. There is no overhead incurred in configuring this valve. Example 3-51 shows the default values for the RequestTrackerValve. Example 3-51.
The context.xml File Configuring NSJSP the application-specific context.xml file does not define its own manager element then the one defined in the /conf/context.xml file will be used. Table 3-16 provides an overview of the default context.xml file. Table 3-16. The default context.xml File Location /conf/context.xml Description The default context.xml file is the context definition loaded by all web applications. Example 3-52 shows the default context.xml file. Example 3-52.
The context.xml File Configuring NSJSP Table 3-17. Attribute List for the Context Element (page 1 of 5) Attribute Description backgroundProcessor Delay Represents the delay in seconds between the invocation of the backgroundProcess method on this context and its child containers, including all wrappers. Setting this to a positive value causes a thread to spawn. After waiting the specified amount of time, the thread invokes the backgroundProcess method on this context.
The context.xml File Configuring NSJSP Table 3-17. Attribute List for the Context Element (page 2 of 5) Attribute Description override Overrides the setting of either the global or Host default contexts. Set to true to have explicit settings in this Context element override any corresponding settings in either the global or Host default contexts. By default, settings from a default context are used.
The context.xml File Configuring NSJSP Table 3-17. Attribute List for the Context Element (page 3 of 5) Attribute Description useHttpOnly Indicates if the HttpOnly flag is included in the HTTP response header. If the HttpOnly flag is included in the HTTP response header, a cookie cannot be accessed through a client side script when the browser supports this flag.
The context.xml File Configuring NSJSP Table 3-17. Attribute List for the Context Element (page 4 of 5) Attribute Description cacheObjectMaxSize Maximum size of a static resource that will be placed in the cache. If not specified, the default value is 512 (512 kilobytes). If this value is greater than cacheMaxSize/20 it will be reduced to cacheMaxSize/20. Note. It is suggested that web application static resources be serviced by the iTP Secure WebServer.
The context.xml File Configuring NSJSP Table 3-17. Attribute List for the Context Element (page 5 of 5) Attribute Description unpackWAR If true, NSJSP unpacks all compressed web applications before running them. If this attribute is not specified, the default value is true. useNaming Set to true (the default) to have Catalina enable a JNDI InitialContext for this web application that is compatible with Java2 Enterprise Edition (J2EE) platform conventions.
Configuring NSJSP The web.xml File The web.xml File The web.xml file in the /conf directory defines the default values for all web applications loaded into each instance of the NSJSP Servlet Server Class. As each application is deployed, this web.xml file is processed, followed by the /WEBINF/web.xml deployment descriptors from individual. This file contains built in servlet definitions and servlet mappings, filters and filter mappings, session parameters, and MIME mappings.
Configuring NSJSP The web.xml File Example 3-53 shows the configuration of the default Servlet. Example 3-53. Configuration of the Default Servlet default org.apache.catalina.servlets.DefaultServlet debug 0 listings false 1 . . .
Configuring NSJSP The web.xml File Example 3-54. Configuration of the Invoker Servlet invoker org.apache.catalina.servlets.InvokerServlet debug 0 2 --> . . .
Configuring NSJSP The web.xml File Example 3-55. Configuration of the JSP Page Compiler and Execution Servlet jsp org.apache.jasper.servlet.JspServlet fork false xpoweredBy false 3 . . .
Configuring NSJSP The web.xml File Example 3-56. Configuration of the SSI Servlet ssi org.apache.catalina.ssi.
Configuring NSJSP The web.xml File Example 3-57. Configuration of the CGI processing Servlet cgi org.apache.catalina.servlets.CGIServlet debug 0 cgiPathPrefix WEB-INF/cgi 5 --> . . .
Configuring NSJSP The web.xml File not perform the database operations on the session object thus eliminating unnecessary database operation. HP recommends that all the static content of an application be served directly by the iTP Secure WebServer. Example 3-58 shows the configuration of the static content filter. Example 3-58. Configuration of the Static Content Filter StaticContentFilter com.hp.tandem.nsjsp.filters.
Virtual Hosts Configuring NSJSP Virtual Hosts Assume that a NonStop server has two network names, hp.com, and internal.hp.com and that NSJSP is required to run applications which use both of these network names. The applications for both these network names could be configured to run with the default configuration of NSJSP, which has only one Host element. However, such a configuration is not flexible enough to separate the two sets of applications.
Configuring NSJSP Configuring Virtual Hosts Configuring Virtual Hosts To configure virtual hosts, you must configure multiple Host elements nested as child elements in the Engine element. The value of the name attribute of each Host is used by the Engine element to identify where requests should be routed. When configuring multiple Host elements, it is necessary to have a different appBase for each Host element and to configure the RequestTrackerValve for each Host. Note.
Configuring NSJSP Session Management Session Management This section describes the different strategies for session management and the related manager configuration details and also explains how to configure any manager element.
In-Memory Sessions (SessionBasedLoadBalancing = true) Configuring NSJSP Figure 3-5.
Configuring NSJSP In-Memory Sessions (SessionBasedLoadBalancing = true) Example 3-61. Arglist from a servlet.config file with SessionBasedLoadBalancing Enabled Arglist -Xmx64m -Xss128k -Xnoclassgc \ -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \ -Djava.util.logging.config.file=$env(NSJSP_HOME)/conf/logging.properties \ Djavax.management.builder.initial=com.tandem.servlet.jmx.NSJSPMBeanServerB iilder \ $NSJSP_SECMGR \ $NSJSP_SECMGR_POLICY \ $NSJSP_JAAS_CONFIG \ -Dcom.tandem.servlet.
In-Memory Sessions (SessionBasedLoadBalancing = true) Configuring NSJSP Table 3-18. Attribute List for the NSJSPStandardManager (page 1 of 2) Attribute Description Default value className Java class name of the implementation to use. This class must implement the org.apache.catalina.Manager interface. The value must be com.tandem.servlet.catalina.session. NSJSPStandardManager. com.tandem. servlet. catalina. session.
In-Memory Sessions (SessionBasedLoadBalancing = true) Configuring NSJSP Table 3-18. Attribute List for the NSJSPStandardManager (page 2 of 2) Attribute Description maxInactiveInt erval The maximum time interval, in seconds, between client requests before a session is invalidated. Default value This attribute provides the initial value whenever a new session is created, but the interval may be dynamically altered by a servlet via the setMaxInactiveInterval method of the HttpSession object.
Configuring NSJSP Persistent Manager Sessions (SessionBasedLoadBalancing = false) This variable is used to set the maximum time interval, in seconds, between client requests before a session is invalidated. However, it should be noted that in the current version of NSJSP, during a context start or restart this variable is always overridden by the value specified in the session-timeout element in the application’s deployment descriptor (web.xml).
Persistent Manager Sessions (SessionBasedLoadBalancing = false) Configuring NSJSP configured. Figure 3-6.
Configuring NSJSP Persistent Manager Sessions (SessionBasedLoadBalancing = false) 2. Configure the Manager Element 3. Create the Persistent Store 4. Configure the Persistent Store Set SessionBasedLoadBalancing to false Set the SessionBasedLoadBalancing parameter in the installation-specific servlet.config file in /conf directory to false. Example 3-64 shows an Arglist from an installation-specific servlet.config file with SessionBasedLoadBalancing set to false. Example 3-64.
Persistent Manager Sessions (SessionBasedLoadBalancing = false) Configuring NSJSP Table 3-19. Attribute List for the Manager element (page 1 of 2) Attribute Description algorithm Name of the Message Digest algorithm used to calculate session identifiers produced by this Manager. This value must be supported by the java.security.MessageDigest class. If the algorithm attribute is not specified, the default value is MD5. className Java class name of the implementation to use.
Persistent Manager Sessions (SessionBasedLoadBalancing = false) Configuring NSJSP Table 3-19. Attribute List for the Manager element (page 2 of 2) Attribute Description randomClass Java class name of the java.util.Random implementation class to use. If randomClass attribute is not specified, the default value is java.security.SecureRandom. saveOnRestart Sessions are not kept in memory, so this attribute has no significance for the Persistent Manager.
Configuring NSJSP Persistent Manager Sessions (SessionBasedLoadBalancing = false) To create the NonStop SQL database for storing the persistent session data, perform the task for the database product that will be used to create and access the persistent store table: For the NonStop SQL/MP database: Make a copy of the nsjsp_createSessionStore_mp.sql file and replace all occurrences of =TheT1222SessionCatalog with the Guardian location (of the form $Volume.
Configuring NSJSP Persistent Manager Sessions (SessionBasedLoadBalancing = false) Example 3-68. SQL/MX script to create a Persistent Store create catalog nsjspcat; set catalog nsjspcat; create schema nsjspsch; set schema nsjspsch; --- Create the NonStop(tm) SQL Table in the above catalog for storing the -- NonStop(tm) Servlets for JavaServer Pages(tm) persistent session data.
Persistent Manager Sessions (SessionBasedLoadBalancing = false) Configuring NSJSP Table 3-20 lists the attributes for the Store element. Table 3-20. Attribute List for the Store Element (page 1 of 2) Attribute Description Default value checkInterval Not applicable to NSJSP. className Java class name of the implementation to use. This class must implement the org.apache.catalina.Store interface. This must be com.tandem.servlet.catalina.sessi on.NonStopSQLJDBCStore. com.tandem.serv let.catalina.
Mixed-Mode Sessions Configuring NSJSP Table 3-20. Attribute List for the Store Element (page 2 of 2) Attribute Description Default value sessionValidCol Name of the database column, contained in the specified session table, that contains a flag indicating whether this swapped out session is still valid or not. valid sessionMaxInact iveCol Name of the database column, contained in the specified session table, that contains the maxInactiveInterval property of this session.
Configuring NSJSP Mixed-Mode Sessions session is persisted, it is removed from process memory. Sessions are persisted till the number of active sessions is less than maxActiveSessions. For more information on maxActiveSessions and minIdleSwap, see Table 3-21. 3. All the remaining in-memory sessions are checked to see if the time since they were last accessed is greater than maxIdleBackup. If so, the session is written to the persistent store, but is not removed from process memory.
Configuring NSJSP Mixed-Mode Sessions Example 3-71 shows the sample configuration of the Manager Element. Example 3-71. The Sample Configuration of the Manager Element PAGE 171Mixed-Mode Sessions Configuring NSJSP Table 3-21. Attribute List of the Manager Element. Attribute Description maxActiveSess ions Maximum number sessions that can be kept in-memory. If this attribute is not specified, it is set to -1. maxIdleBackup The time interval (in seconds) since the last access to a session before it is eligible for being persisted to the session store, or -1 to disable this feature. By default, this feature is disabled.
Configuring NSJSP Determining the Storage Capacity of the Persistent Store It is possible to set the value of this variable at run time using the modify MBeans feature of the NSJSP Manager. The value set at run time will take effect immediately but will not be persisted and will not be available across web application context restarts.
Configuring NSJSP Determining the Storage Capacity of the Persistent Store shows the sample output of a showddl command. Example 3-73. The Sample Output of a showddl Command >>showddl nsjspcat.nsjspsch.sessdata; CREATE TABLE NSJSPCAT.NSJSPSCH.
Configuring NSJSP Determining the Storage Capacity of the Persistent Store Example 3-74. The Sample Output of a fup info ,detail Command 3> fup info $DATA00.ZSDG8WWM.X8BXVN00 ,detail $DATA00.ZSDG8WWM.X8BXVN00 26 Apr 2010, 10:44 SQL ANSI TABLE ANSI NAME NSJSPCAT.NSJSPSCH.SESSDATA RESOURCE FORK \POS02.$DATA00.ZSDG8WWM.X8BXVN01 SYSTEM METADATA \POS02.$OSS03.
Configuring NSJSP Determining the Storage Capacity of the Persistent Store Example 3-75 shows the SQL session data cleanup script. Example 3-75. SQL Session Data Cleanup Script Usage: nsjsp_cleanSessionData nDays where nDays: Number of days for which session data is to be preserved/saved. Sessions that have expired more than 'nDays' ago will be deleted. A value of zero (0) will delete all the expired sessions. Example 3-76 shows an invocation of the nsjsp_cleanSessionData script. Example 3-76.
Configuring NSJSP Configuring the Manager Element Example 3-77.
Configuring NSJSP Configuring the Manager Element Example 3-78. Sample Context Configured with a Persistent Manager PAGE 178Configuring NSJSP Configuring the Manager Element Example 3-79. Default Configuration of the Manager Element WEB-INF/web.xml PAGE 1794 Managing NSJSP This chapter describes the tools that are used to manage NSJSP installations and the web applications deployed in those NSJSP installations.
NSJSP Manager Features Managing NSJSP The NSJSP Manager also enables you to deploy and manage web applications running in the default localhost or in any additional virtual Hosts specified within the server.xml file in an NSJSP 6.1 installation directory. NSJSP Manager Features The NSJSP Manager application enables you to do the following: Manage NSJSP 6.1 Server Classes Start, freeze, thaw, and stop NSJSP 6.1 Server Classes Display NSJSP 6.
Managing NSJSP NSJSP Security Compare MBean attributes across processes Modify MBean attributes For more information on how to use the NSJSP Manager application, see the NSJSP Manager Operations on page 4-3. NSJSP Security To log in to the NSJSP Manager application, you require a user name and password. By default, a user called admin is used to log in to the NSJSP Manager application. The password assigned during the NSJSP Manager installation is the password for the admin user.
Managing NSJSP NSJSP Manager Operations Logging in to the NSJSP Manager Application To manage the NSJSP Server Classes that are created using the setup script, log in to the NSJSP Manager application. To log in to the NSJSP Manager application, complete the following steps: 1. Enter the following URL: http://IP address:Port number/manager/ For example: http://15.148.2.1:1088/manager/ where, 15.148.2.1 specifies the IP address of the system on which the NSJSP Manager application is deployed.
Managing NSJSP NSJSP Manager Operations The NSJSP Manager Scope page appears. By default, the Scope tab is enabled. To enable all the NSJSP Manager functions for a specific server class, you must select and set the server class and the Host. Note. The NSJSP Manager application can only manage server classes that belong to NSJSP 6.1 installations. Selecting the Server Class and Host You must select the server class from the list of configured server classes.
Managing NSJSP NSJSP Manager Operations For example, Host (in server.xml) set to "localhost", with server class "SERVLETS". where, localhost specifies the host name. SERVLETS specifies the server class name. The Applications, MBeans, and Deployment tabs are now enabled. Note. When you select the server class, only the Server Class tab that manages the server class is enabled. All other tabs, such as, Applications and Deployment are disabled.
Managing NSJSP NSJSP Manager Operations Server Class – Enables display of the server class process information including status, connector and server class statistics, and configuration parameters. Also, provides TS/MP operations (for example, starting, freezing, thawing, and stopping a server class) for the server class in the selected scope. For information on how to view the server class details, see Viewing Server Class Information on page 4-30.
Managing NSJSP NSJSP Manager Operations 03/19/10 12:49 PM represents the time when the reset operation was performed. 6 23:07:20 represents the time elapsed since the last reset (6 = # of days, 23 = # hours, 07=mins, 20 seconds). Help – Includes brief information about the displayed page. Note. The Refresh Stats, Reset Stats, and Help are displayed on each screen. Note. You can sort the order of contents displayed in many tables by clicking the column heading for the column that will be sorted.
Managing NSJSP NSJSP Manager Operations Details of the applications for each NSJSP process, such as, name of the NSJSP process on which the application is running and rate at which requests are received by the application. Session details, such as its ID, the duration for which the session is idle. URI statistics, such as, the URI of an application and the time taken to process the URI.
NSJSP Manager Operations Managing NSJSP Click the request count value of an application to view the distribution of requests based on the URI. Click the session count value of an application to view all the in-memory sessions for the application across the processes in the selected server class. Click Reset Stats to reset the values of the Request Count column in the table. Table 4-1 lists the attributes displayed in the Applications page. Table 4-1.
Managing NSJSP NSJSP Manager Operations Figure 4-4 shows a sample Application Summary page for the application, /sca6url/examples. Figure 4-4. Application Summary Page You can perform the following operations on the Application Summary page: Stop an application on all the processes in the selected server class using the Stop Application option. For more information on stopping the application, see Stopping a Web Application on page 4-26.
NSJSP Manager Operations Managing NSJSP Click the value corresponding to the Servlet Count: field to view the list of servlet mappings configured for an application. Note. A servlet can have multiple servlet mappings configured for it. Click a value from the In Memory Sessions column of the table to view all the sessions currently in memory for an application. Click Reset Stats to reset the value of the Requests, Request Arrival Rate, Average Service Time, Min. Time, and Max.
NSJSP Manager Operations Managing NSJSP Table 4-3. Attributes in the Application Summary Page Attribute Description Application Information Application Name: The context name of the application. Servlet Count: Number of servlets configured for the application. Doc. base: The root directory that contains all the application resources. It is relative to the application base (appBase) of the Host in which this application is deployed. Session Timeout: Maximum idle time allowed for a session.
NSJSP Manager Operations Managing NSJSP Table 4-4. Submenu Items Under the Applications Tab (page 2 of 2) Submenu Item Description URI Statistics Uniform Resource Identifier (URI) access statistics for the application, such as, the list of application URIs accessed by users and the number of user requests received by the application. For more information, see Viewing the URI Statistics for an Application on page 4-18.
Managing NSJSP NSJSP Manager Operations The details of the application for each NSJSP process are displayed on the Process View page. You can perform the following operations on the Process View page: Click the value corresponding to the Servlet Count: field to view the list of servlet mappings configured for an application. Note. A servlet can have multiple servlet mappings configured for it.
NSJSP Manager Operations Managing NSJSP Table 4-5 lists the attributes displayed in the Process View page. Table 4-5. Attributes in the Process View Page Attribute Description Application Information Application Name: The context name of the application. Servlet Count: Number of servlets configured in the application. Doc. base: The root directory that contains all the application resources. It is relative to the application base (appBase) of the Host in which this application is deployed.
Managing NSJSP NSJSP Manager Operations The In-Memory Sessions page for the selected application appears. Figure 4-6 shows a sample In-Memory Sessions page for the application, /sca6url/examples. Figure 4-6. In-Memory Sessions Page You can perform the following operations using the In-Memory Sessions page: Select or clear the check box corresponding to a session by clicking Toggle.
NSJSP Manager Operations Managing NSJSP Age (sec): It is similar to the Idle Time except that this option filters the sessions based on the age. The age of a session indicates how long ago the session was created. You can also use the Apply search option to search the sessions. This option appears only when you search for a session. Use the Clear search option to clear the search screen and return to the session list screen.
NSJSP Manager Operations Managing NSJSP To view the URI statistics for the application, complete the following steps: 1. Complete the steps described in Viewing Application Summary on page 4-10. 2. Click URI Statistics. The URI Statistics page appears. It displays access statistics of the application resources. Note. The reset operation on the URI Statistics page resets the value of all the columns in the table. Figure 4-7 shows a sample URI Statistics page. Figure 4-7.
NSJSP Manager Operations Managing NSJSP Table 4-8. Attributes in the URI Statistics Page (page 2 of 2) Attribute Description Average Service Time (in ms) Average time taken (in milliseconds) to process user requests for a URI. Min. Time (in ms) Minimum time taken (in milliseconds) to process a user request for a URI. Max. Time (in ms) Maximum time taken (in milliseconds) to process a user request for a URI.
NSJSP Manager Operations Managing NSJSP Table 4-9. Attributes in the HTTP Method Statistics Page Attribute Description HTTP Method Name of the HTTP method. Request Count Number of requests processed for the HTTP method. Request Arrival Rate (in last min.) Number of requests processed for the HTTP method in the last minute. Average Service Time (in ms) Average time taken to process user requests for the HTTP method of the application. Min.
Managing NSJSP NSJSP Manager Operations You can use the download option to download the context definition file. Viewing Deployment Descriptor Details The Deployment Descriptor page displays the deployment descriptor for the selected application. The deployment descriptor is always in the web.xml file in the WEB-INF directory of the application. Note. There cannot be any application without a deployment descriptor.
Managing NSJSP NSJSP Manager Operations You can use the download option to download the deployment descriptor file. Viewing Servlet Mappings The deployment descriptor contains elements that define which servlet must process a request URL. The mapping between the URL and the servlet (configured to process the requests matching that URL) is called servlet mapping. To view servlet mapping details for the applications, complete the following steps: 1.
NSJSP Manager Operations Managing NSJSP Table 4-10. Attributes in the Servlet Mappings Page Attribute Description URL Pattern Pattern of the Uniform Resource Locators (URLs), which will be serviced by the servlet. Servlet Name Logical name associated with the servlet. Servlet Class Fully qualified class name of the servlet. Startup Order The order in which the servlet initializes. Number 1 indicates that the servlet initializes first. No value indicates that a startup order is not specified.
NSJSP Manager Operations Managing NSJSP Table 4-11 lists the attributes displayed in the Filters page. Table 4-11. Attributes in the Filters Page Attribute Description Filter Name Logical name of the filter. Filter Class Fully qualified class name of the filter. Description Filter description as defined in the Deployment Descriptor. Viewing Initialization Parameters The Java servlet specification enables you to define the initialization parameters for each application.
Managing NSJSP NSJSP Manager Operations Managing Web Applications Upon successful deployment of a web application, all the instances of that application on a Host are in the running state, by default.
Managing NSJSP NSJSP Manager Operations Figure 4-14. Application Summary Page Showing the Down Status If you click the Application tab again, the status of the application is displayed as None. After the application is stopped, it is no longer accessible to the users. Starting a Web Application The Start Application option of the NSJSP Manager application interface enables you to start the previously stopped application. To start the web application, complete the following steps: 1.
Managing NSJSP NSJSP Manager Operations Figure 4-15. Application Summary Page Showing the Running Status If you click the Applications tab again, the status of the application is displayed as All NSJSPs. You can now access the application. Reloading a Web Application The Reload Application option of the NSJSP Manager application interface reloads the entire context. It is used to reload all the application resources while the application is available to the users. Note.
Managing NSJSP NSJSP Manager Operations The application restarts. Figure 4-16 shows the messages that are displayed after an application is reloaded. Figure 4-16. Application Summary Page Showing the Reloaded Status Undeploying a Web Application The Undeploy Application option of the NSJSP Manager application interface removes the context and deletes all the application-related resources from the file system. To undeploy the web application, complete the following steps: 1.
Managing NSJSP NSJSP Manager Operations Viewing Server Class Information To view the details of an NSJSP Server Class, select the Server Class tab in the NSJSP Manager application. You can view the following information under the Server Class tab: NSJSP information Server class processes NSJSP connector statistics Configuration parameters Server class statistics Sever class operations To view information about a server class, click the Server Class tab. The NSJSP Information page appears.
Managing NSJSP 4 Managing NSJSP The NSJSP Information page displays static information about the environment in which NSJSP is running. Table 4-13 lists attributes displayed in the NSJSP Information page. Table 4-13. Attributes in the NSJSP Information Page Attribute Description NSJSP Information Version: NSJSP version installed on the system. NSJSP Home: Open System Services (OSS) path where the NSJSP installation is created. Last Start Time: Date and time at which the server class last started.
Managing NSJSP Table 4-14. Submenu Items Under the Server Class (page 2 of 2) Submenu Item Description Configuration Parameters TS/MP parameters that are used to deploy NSJSP processes. For more information, see Viewing Configuration Parameters on page 4-34. Server Class Statistics Aggregate Linkmon Statistics for the NSJSP Server Class. You can use the values displayed in this page for performance analysis and troubleshooting. For more information, see Viewing Server Class Statistics on page 4-36.
Managing NSJSP Table 4-15. Attributes in the Server Class Processes Page Attribute Description Pathmon Name Identifies in which PATHMON a particular NSJSP process is running. Process Name Name of the NSJSP process. CPU, PIN CPU and PIN of the process. Request Not Read Number of requests that are yet to be read. These requests are currently in the $RECEIVE queue. Request Not Replied Number of requests that are currently being processed. Request Open Depth It is also called the receive depth.
Managing NSJSP Figure 4-19. NSJSP Connector Stats Page This page displays the activities of the NSJSP connector component. The connector activities indicate the incoming request workload for individual NSJSP processes. Table 4-16 lists the attributes in the NSJSP Connector Stats page. Table 4-16. Attributes in the NSJSP Connector Statistics page Attribute Description Process Name Name of the NSJSP process.
Managing NSJSP the servlet.config file. For more information on the server class configuration parameters and their values, see the TS/MP System Management Manual. To view the parameters that are used to deploy NSJSP processes, complete the following steps: 1. Click the Server Class tab. 2. Click Configuration Parameters. The Configuration Parameters page appears. Figure 4-20 shows a sample Configuration Parameters page. Figure 4-20.
Managing NSJSP Figure 4-20. Configuration Parameters Page Table 4-17 lists the GUI server class configuration parameters. Table 4-17. Server Class Configuration Parameters Attribute Description Server Class Configuration Parameters Lists the configuration parameters. Environment Variables Name Name of the environment variable set for the NSJSP process. Value Value of the environment variable set for the NSJSP process.
Managing NSJSP Figure 4-21. Server Class Statistics Page The Server Class Statistics page provides the following information: Server class link wait queue (Queue Info) The link manager sends requests to the server class process through links. A request is placed in a link queue if it is not possible to immediately send the request to a server class process due to unavailability of a link.
Managing NSJSP It is the information about I/O operations to and from a server class. A send operation is a message sent from the link manager to a server class process. A reply operation is a message received by the link manager from a server class process. When an HTTPD process communicates with NSJSP, a single HTTPD message sent to an NSJSP process results in multiple send operations from the link manager to the process.
Managing NSJSP Note. Clicking Reset on this page does not reset the statistics displayed on this page. For information on how to reset these statistics, see the TS/MP System Management Manual. Performing Server Class Operations Under the Server Class tab, you can view the current status of the server class by clicking the Server Class Operations option.
Managing NSJSP 3. Perform one of the following steps depending on the number of PATHMONs configured: a. If the server class is configured on only one PATHMON, click Stop. The following message is displayed: The operation will make the server class unavailable for the user. Do you still want to stop the server class? Click OK. b. If the server class is configured in a TS/MP Pathway domain, complete the following steps: 1. Select the Pathmon Name, which has the server class to be stopped. 2. Click Stop.
Managing NSJSP WARNING. Wait for a minute or two for the operation to complete before performing any other operation on the NSJSP Manager application interface. The time required for an operation to complete depends on the number of requests serviced by the server class at the time of the stop operation and the number of server class processes that are running. Start the NSJSP Server Class Using the NSJSP Manager application, you can start an NSJSP Server Class that is in the STOPPED or THAWED state.
Managing NSJSP The server class starts and you can access only those applications that are running on the server class. Freeze the NSJSP Server Class Using the NSJSP Manager application, you can freeze an NSJSP Server Class that is in the RUNNING or THAWED state. After performing a FREEZE operation, no new links will be assigned to the link manager, and the link manager will stop using the current links. To freeze the NSJSP Server Class, complete the following steps: 1. Click the Server Class tab.
Managing NSJSP Figure 4-24. Server Class with the $ZSB6 PATHMON in the FROZEN State Thaw the NSJSP Server Class Using the NSJSP Manager application, you can thaw an NSJSP Server Class that is in the FROZEN or STOPPED state. To thaw the NSJSP Server Class, complete the following steps: 1. Click the Server Class tab. The System Information page appears. 2. Click the Server Class Operations. 3. Perform one of the following steps depending on the number of PATHMONs configured: a.
Managing NSJSP Figure 4-25. Server Class with the $ZSB6 PATHMON in the RUNNING State After changing the PATHMON status to THAWED, select the same PATHMON name and click Start to restart the server class. Viewing MBeans The NSJSP resources, such as, server, connector, and engine are instrumented by MBeans. For more information on MBeans, see Appendix A, MBeans in the NSJSP Container. You can view the list of MBeans running in each NSJSP process within an NSJSP Server Class.
Managing NSJSP Figure 4-26. NSJSP MBeans Page You can perform the following operations using the NSJSP MBeans page: List the MBeans tree by selecting an NSJSP process from the list and clicking Load. List the attributes of an MBean by clicking a leaf node from the MBean tree. Compare the attributes of the MBean across NSJSP processes by clicking the Compare across Processes link. After clicking the link, the Compare - NSJSP MBeans page appears.
Managing NSJSP Table 4-19. Parameters for Viewing MBeans and their Attributes (page 2 of 2) Parameter Description MBeans Left window A navigation tree that lists all the MBeans running in the selected NSJSP process. Right window Following are the fields displayed for a selected MBean: Object Name - Object name of the MBean. Description - Description of the MBean. Compare Across Processes - A link to compare the attributes of the displayed MBean across processes.
Managing NSJSP 3. In the MBean Object Name: field, type the object name of the MBean whose attribute values you want to compare. For example, if you enter the following string in the MBean Object Name: field and click Compare All Attributes: NSJSP:j2eeType=Servlet,* All MBeans of type Servlet that are configured in the NSJSP domain are displayed, as shown in Figure 4-27. Figure 4-27. List of MBeans 4. Click the MBean name that you want to compare.
Managing NSJSP Figure 4-28. Compare - NSJSP MBeans Page If you only want to compare a few attributes across all the NSJSP processes, select the attribute names from the MBean Attribute Names: field and click Compare. Figure 4-29 shows the comparison result for the modelerType attribute across all the NSJSP processes. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Figure 4-29. Comparison Result for the modelerType Attribute Note. If you navigate the Compare - NSJSP MBeans page by clicking the MBeans List option and then clicking the Compare across Processes link, the object name and the attribute values for that MBean, across the NSJSP processes, are displayed on the page.
Managing NSJSP To list all MBeans under the domain NSJSP, enter the following string in the MBean Object Name: field and click Compare All Attributes: NSJSP:* To list all the session managers configured in the application running in the host=localhost, enter the following string in the MBean Object Name: field and click Compare All Attributes: NSJSP:type=Manager,host=localhost,*" Modify an MBean.
Managing NSJSP 3. In the MBean Object Name: field, type the object name of the MBean whose attribute values you want to modify. 4. Click Load Attribute list. The following fields are displayed on the Modify MBean page that must be set to modify an MBean attribute: NSJSP Process Name: Attribute Name: New Attribute Value: The Set New Attribute Value button and the actual attribute values across NSJSP processes are also displayed on the Modify MBean page. 5.
Managing NSJSP Figure 4-30. Modify MBean Page Table 4-21 lists the parameters displayed in the Modify MBean page. Table 4-21. Parameters in the Modify MBean Page Parameter Description MBean Object Name: Name of the MBean with the attribute that you want to modify. NSJSP Process Name: A list of NSJSP processes to which you may apply the new attribute value. You can select one or more NSJSP processes to have the selected attribute modified. Attribute Name: A list of MBean attributes.
Managing NSJSP Deployment from a server Deployment from a desktop Note. NSJSP does not support context names, such as, /my/context, that include multiple ‘/’ characters. Deploying Web Applications from the Server If an application resource already exists on the server in which NSJSP is running, use the server deployment option. To deploy an application from the server, complete the following steps: 1. Click the Deployment tab. The Application Deployment page appears. 2.
Managing NSJSP Figure 4-31. Web Application Deployment from Server Table 4-22 lists the attributes displayed under Web Application Deployment from Server on the Application Deployment page. Table 4-22. Attributes on the Web Application Deployment from Server Page (page 1 of 2) Attribute Description Context name The context name to use for the application. Context Configuration File Location Absolute path of the application context file.
Managing NSJSP Table 4-22. Attributes on the Web Application Deployment from Server Page (page 2 of 2) Attribute Description Automatically Add Filemap Check box to enable the creation of a Filemap file entry for the application. The entries in the filemaps.config file are used by the Servlet Server Class during startup to determine the path to the application. Applications require a Filemap file entry. For more information on the context prefix for an application, see Chapter 3, Configuring NSJSP.
Admin Web Application Managing NSJSP Figure 4-32 shows the Web Application Deployment from Desktop window. Figure 4-32. Web Application Deployment from Desktop Table 4-23 lists the attributes displayed under Web Application Deployment from Desktop on the Application Deployment page. Table 4-23. Attributes on the Web Application Deployment from Desktop Page Attribute Description Select a .war file to upload The Browse... button by this field must be used to select the .war file that you want to deploy.
Managing NSJSP Overview and Architecture 4 Managing NSJSP Note. HP recommends that you perform the Commit Changes operation only after making all changes to the configuration. The Admin Web application can manage an NSJSP Server Class in only one PATHMON when NSJSP 6.1 is installed in an iTP Secure WebServer environment that is configured for online-upgrade.
Overview and Architecture Managing NSJSP Server Class, as shown in Figure 4-34. As a result, any NSJSP processes subsequently created have the same configuration as the currently running processes. Figure 4-33. Admin Operations followed by SAVE Object browses, update, and “SAVE” nsjspdmin -adm httpd server Figure 4-34.
Managing NSJSP Admin Web Application Features Admin Web Application Features The Admin Web application includes a User Interface (UI) to perform the operations related to the NSJSP servlet container components, such as, Service and Host. The Admin Web application enables you to do the following: Modify the configuration files. Create new NSJSP servlet container components. Delete existing NSJSP servlet container components. Create users, groups, and roles for the users.
Managing NSJSP Login and Security Considerations Figure 4-35. Admin Login page Note. To log in to the Admin Web application, enter the user name as admin and use the same password that you provided when the setup script was run. An error message is displayed if you are not authorized to access the Admin Web application or if the authentication process fails. After completing the authentication and authorization processes, the Admin Web Application home page is displayed as shown in Figure 4-36.
Managing NSJSP Login and Security Considerations Figure 4-36. Admin Web Application Home Page The Admin Web application home page is divided into two panes: the left pane and the right pane. The left pane includes elements to manage the servlet container components and to perform tasks, such as, adding users and groups. These elements are displayed in a tree structure.
Managing NSJSP Managing Admin Web Application Operations Commit Changes – This operation commits all the previously saved changes, notifies the running NSJSP processes of the changes and updates the configuration files. Log Out – Ends the current user session and requires a new login to access the Admin Web application. Managing Admin Web Application Operations This section lists all the actions that you can perform using the Admin Web application.
Managing NSJSP Administering the Server Figure 4-37. The Tomcat Server Element You can select one of the following actions from the Server Actions list: Create New Service NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Administering a Service Delete Existing Services Caution. Although you can add more than one Service element, HP recommends that you retain only one Service element due to the following reasons: Each Service element requires a Connector element and NSJSP provides only one Connector implementation, which processes messages from the $RECEIVE file. Two Connector definitions cannot use the same connector implementation.
Managing NSJSP Administering a Service Figure 4-38. The Service Element You can select one of the following actions from the Service Actions list: Create New Connector Delete Existing Connectors Create New Host Delete Existing Hosts Create New Valve NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Administering a Connector Delete Existing Valves Caution. HP recommends that you always have only one Connector element. Therefore, do not use the following actions: Create New Connector Delete Existing Connectors For more information, see the Caution on page 4-64. Do not use the NSJSP Manager to manage Hosts, that are added using the Admin Web application, unless the Host is configured with a Request Tracker Valve in the server.xml file.
Managing NSJSP Administering a Host Figure 4-39. The Connector Element For more information on the Connector element, see the Connector Element on page 3-45. Note. The Connector Actions list includes the Delete This Connector action. If you perform this action, the NSJSP Server Class and the Admin Web application will become non functional. Administering a Host The Host represents a virtual Host. One or more Hosts are nested inside an Engine.
Managing NSJSP Administering a Host Figure 4-40 displays the Host Actions list and the properties of the Host element in the right pane. Figure 4-40. The Host Element The following actions are available under the Host Actions list: Create New Aliases Delete Aliases Create New Context Delete Existing Contexts Create New Valve Delete Existing Valves Delete This host NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Administering a Context Note. An alias is the alias of a Host. A Host can have multiple aliases. NSJSP 6.1 does not support the Create New Context and Delete Existing Contexts actions. Use the NSJSP Manager or the Manager Web application to create or delete a new context. For more information on the Host element, see the Host on page 3-54. Administering a Context A context represents a web application.
Managing NSJSP Administering a Context Figure 4-41. The Context Element You can perform one of the following actions using the Context Actions list: Create New User Realm Delete User Realms Create New Valve Delete Existing Valves Delete This Context For more information on the Context element, see Table 3-17, Attribute List for the Context Element. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Administering a Realm The context is also associated with the NSJSP-specific loader and a Session Manager. Therefore, some attributes of the loader and the Session Manager are displayed along with the attributes of the Context element, as shown in Figure 4-41. Note. The Session ID Initializer attribute of the Session Manager will change the entropy of the context and not the Manager class.
Managing NSJSP Administering a Valve Figure 4-42. The Properties of MemoryRealm The attribute list varies for each type of Realm. For more information on Realms and their attributes, see http://tomcat.apache.org/tomcat-6.0-doc/config/realm.html. Administering a Valve A Valve has distinct processing capabilities, such as, providing access, logging and request filtering. NSJSP supports the following types of valves: AccessLogValve RemoteAddrValve NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP Administering a Valve RemoteHostValve RequestDumperValve SingleSignOn For information on valves, see the Valve Element on page 3-58. You can create a new valve by clicking one of the following elements in the left pane and selecting Create New Valve from the actions list: Service – A valve created at the Service level will be applicable to all the applications in the Engine. Host – A valve created at the Host level will be applicable to all the applications under that Host.
Managing NSJSP Administering Resources Administering Resources Resources can be defined either globally or per web application under the Context element. The globally defined resources can be accessed using web applications by specifying links to the global resource in the web application itself. The following are the types of resources: Data Sources (of type javax.sql.DataSource) Mail Sessions (of type javax.mail.Session) Environment Entries (of various Java language types such as java.lang.
Managing NSJSP 4 Managing NSJSP Figure 4-44. The Data Sources Element You can perform one of the following actions using the Data Source Actions list: Create New Data Source Delete Data Sources For more information on data sources, see http://java.sun.com/javase/6/docs/technotes/guides/jdbc/getstart/datasource.html. Mail Sessions A Mail Session represents a Resource (under the child element of the Server called GlobalNamingResources) in the server.xml file.
Managing NSJSP The following sample code shows how the Mail Session is added as Resource in the server.xml file: Figure 4-45 displays the properties after selecting the Create New Mail Session action from the Mail Session Actions list. Figure 4-45.
Managing NSJSP value="true" /> Figure 4-46 displays the properties after selecting the Create New Env Entry action from the Environment Entry Actions list. Figure 4-46. The Properties Displayed After Selecting the Create New Env Entry Action The following are the actions available under the Environment Entry Actions list: Create New Env Entry Delete Environment Entries User Databases A user database is a database that contains user information, such as user names, passwords, groups, and roles.
Managing NSJSP type="org.apache.catalina.UserDatabase" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/nsjsp-users1.xml" /> Figure 4-47 displays the properties of the default User Database. Figure 4-47.
Managing NSJSP Administering User Definitions Figure 4-48. The Properties Displayed After Selecting the Create New Resource Link Action You can perform one of the following actions using the Resource Link Actions list: Create New Resource Link Delete Resource Link For more information on resource link, see http://tomcat.apache.org/tomcat-6.0-doc/config/globalresources.html.
Managing NSJSP Administering User Definitions Roles Users A user is an entity that can be used to log in to user applications. A user can be assigned multiple roles. Figure 4-49 displays the properties of a selected user. Figure 4-49.
Managing NSJSP Administering User Definitions The Realm is configured to expect encrypted passwords. Therefore, while creating a new user, you must encrypt the password as per the Realm definition. The Admin Web application itself does not encrypt the password. Note. For a new user, password must be encrypted using the CLI. For information on setting a user password in the nsjsp-users.xml file, see Chapter 7, Migrating to NSJSP 6.1.
Managing NSJSP Administering User Definitions Roles List Roles are used to control access to applications and resources. They may be directly assigned to users or roles can be assigned to groups, which in turn can be assigned to users. Figure 4-51 displays a Roles List. Figure 4-51.
Managing NSJSP Access Security Considerations Access Security Considerations The NSJSP installation setup script prompts the user (with name admin) for a password. The admin user ID and password can be used to log on to the Admin Web application. For information on how to change the admin user ID and password, see Users on page 4-80 and Chapter 7, Migrating to NSJSP 6.1. Persisting Changes to the server.
Managing NSJSP Persisting Changes to the server.xml File and Context Files Contents of the server.xml File When the Admin Server Class serializes its configuration back to the server.xml file, the following changes occur in addition to the configuration changes: All comments are removed. All contexts are serialized except those that were deployed using the context.xml file or those providing the context.xml file inside the .war or the docBase directory.
Managing NSJSP Manager Web Application 5. Start the server class that is in the STOPPED state. Note. After each commit operation, the web applications that define an explicit context will be restarted because the context file is updated. This happens irrespective of whether the application’s context was modified or not. Manager Web Application The Manager Web application was included in releases prior to NSJSP 6.1 to manage web applications hosted by NSJSP.
Managing NSJSP Server Class Operations configuration, you must cold start the iTP Secure WebServer. The iTP Secure WebServer must be cold started to create and add the NSJSP Server Class definitions to the iTP Secure WebServer TS/MP configuration. Note. The HTTPD object in the /bin directory can be used both as a command-line utility and as the object file for the HTTPD Server Class.
Managing NSJSP Server Class Operations Stopping NSJSP Following are the two ways to stop the NSJSP Server Class: Graceful Shutdown Forced Shutdown Graceful Shutdown To stop the NSJSP Server Class gracefully, complete the following steps: 1. Obtain the PATHMON name from the httpd.config file located in the /conf directory. 2.
Server Class Operations Managing NSJSP The STATUS SERVER command displays the following output for the SCP1 Server Class: SERVER #RUNNING SCP1 ERROR 0 INFO FROZEN The processes of the SCP1 Server Class are stopped as indicated by the 0 in the #RUNNING column and the status of the SCP1 Server Class changes to FROZEN. Note. Stop the NSJSP Server Class gracefully, to allow the server class processes to complete outstanding requests and to perform shutdown operations, before exiting.
Server Class Operations Managing NSJSP After you enter the STOP SERVER command, the SCP1 Server Class’s processes running under the $zweb PATHMON are stopped. To view the status of the SCP1 Server Class, enter the following commands: PDMI 1>> OPEN $zweb,$yweb PDMI 2>> STATUS SERVER SCP1 The following output is displayed: PATHMON : \POS02.$ZWEB SERVER SCP1 #RUNNING ERROR INFO ERROR INFO 0 PATHMON : \POS02.
Manual Deployment and Undeployment of Web Applications Managing NSJSP To start an NSJSP Server Class, complete the following steps: 1. Obtain the PATHMON name from the httpd.config file located in the /conf directory. 2. At the TACL prompt, run the following commands: TACL> PATHCOM $ = START SERVER Note. The THAW SERVER command only needs to be entered when a status show that the server class was frozen.
Managing NSJSP Deploying Applications on a Running NSJSP Server To deploy a web application at startup, you must set the value of the Host's deployOnStartup attribute to true. If the deployOnStartup attribute is set to false, applications will not deploy at startup. Even though applications are not deployed during startup (if deployOnStartup is set to false), the applications will get deployed when the auto deployer of the Host runs. You can control the auto deployer by using the autoDeploy attribute.
Managing NSJSP Comparison of the Management Applications Deletion of a directory – Deleting a directory causes the application to undeploy, and any associated context file and work directory are removed. Current user sessions will not be persisted. Any associated .war file will not be deleted, and the application will be redeployed from the .war file when the auto deployer checks for changes.
Comparison of Architectures Managing NSJSP Old Manager Application The old Manager application supports management of web applications on a Host. You can perform tasks, such as, deploy, start, and stop web applications on the Host where the old Manager application is running. If there are two or more Hosts within an NSJSP servlet container, an instance of the old Manager application is required on each Host. Figure 4-52 illustrates the architecture of the old Manager application. Figure 4-52.
Managing NSJSP Comparison of Architectures applications on www.foo.com, and the old Manager application on www.foo.com cannot manage web applications on localhost, as indicated by the red arrows. Note. The Manager Web application that was included in releases prior to NSJSP 6.1 is referred to as the old Manager application to differentiate it from the NSJSP Manager application that is introduced in the NSJSP 6.1 release.
Comparison of Architectures Managing NSJSP Figure 4-53. Architecture of the Admin Web Application HTTP Requests iTP Secure WebServer HTTPD HTTPD HTTPD $zweb Environment Admin Web NSJSPADMIN Admin Web NSJSPADMIN NSJSP Installation NSJSP Installation NSJSP A NSJSP B In Figure 4-53, the $zweb environment contains two NSJSP installations.
Comparison of Architectures Managing NSJSP Management of multiple NSJSP 6.1 installations within an iTP Secure WebServer environment. Management of NSJSP installations that are configured in a Pathway domain. The use of a Pathway domain implies that the iTP Secure WebServer was installed in an online-upgrade configuration, which has two PATHMONs. Figure 4-54 illustrates the architecture of the NSJSP Manager application. Figure 4-54.
Managing NSJSP Comparison of Architectures Differences in Architectures The differences in the architectures of the three applications are as follows: Using the old Manager application, you can manage web applications running on only one Host. Using the Admin Web application, you can manage the servlet container and its objects within the same installation as the Admin Web application, but only within one PATHMON. Using the NSJSP Manager application, you can manage multiple NSJSP 6.
Comparison of Features Managing NSJSP Comparison of Features Table 4-24 compares the features of the NSJSP Manager, the Old Manager, and the Admin Web applications. Table 4-24. Comparison of Features of NSJSP Manager, Old Manager, and Admin Web Applications (page 1 of 2) NSJSP Manager Application Old Manager Application Admin Web Application Category Feature Application Management Displays the current applications running on the selected server class and Host.
Comparison of Features Managing NSJSP Table 4-24. Comparison of Features of NSJSP Manager, Old Manager, and Admin Web Applications (page 2 of 2) NSJSP Manager Application Old Manager Application Admin Web Application Category Feature Server Class Information Displays NSJSP processes and their status, such as, the processor on which the application is running and the amount of memory used. Yes No No Displays the configuration parameters for the selected server class.
Comparison of Management Application Access Roles Managing NSJSP Comparison of Management Application Access Roles Table 4-25 compares the roles that must be assigned to users to authorize them to access the management applications. Table 4-25. Comparing Roles Management Application Role Required to Access the Management Application Admin Web Application admin – role for users who need to configure NSJSP.
Single Point of Management Using the NSJSP Manager Managing NSJSP Figure 4-55. NSJSP Manager Supporting Multiple Hosts HTTP Requests iTP Secure WebServer HTTPD HTTPD HTTPD $zweb Environment Manager NSJSP Manager www.foo.com www.doo.com localhost NSJSP Servlet Container User applications running on the Hosts In Figure 4-55, using a single instance of the NSJSP Manager, you can manage all the web applications running on the three Hosts: localhost, www.foo.com, and www.doo.
Single Point of Management Using the NSJSP Manager Managing NSJSP Figure 4-56. Multiple NSJSP Installations HTTP Requests iTP Secure WebServer HTTPD HTTPD HTTPD $zweb Environment Manager NSJSP Manager NSJSP 6.1 NSJSP 6.1 NSJSP 5.0/NSJSP 6.0 In Figure 4-56, a single instance of the NSJSP Manager application enables the management of all NSJSP 6.1 installations within an iTP Secure WebServer environment, as indicated by the green arrows.
Single Point of Management Using the NSJSP Manager Managing NSJSP domain configuration. You can configure an NSJSP installation in a Pathway domain for online upgrades of web applications and servlet containers. For more information on Pathway domain configuration, see the TS/MP Release Supplement Manual. For more information on configuring for online-upgrade, see the iTP Secure WebServer System Administrator’s Guide. Figure 4-57 illustrates NSJSP installations configured in a Pathway domain. Figure 4-57.
The Architecture of the NSJSP Manager Managing NSJSP You can install the NSJSP Manager by selecting Create an NSJSP Manager installation when running the NSJSP setup script. Each iTP Secure WebServer environment can include one instance of the NSJSP Manager. The Architecture of the NSJSP Manager Upon successful installation of the NSJSP Manager, the NSJSP Manager runs in its own server class in the iTP Secure WebServer environment. You can use the NSJSP Manager application to manage all the NSJSP 6.
Managing NSJSP The Architecture of the NSJSP Manager manage the two NSJSP 6.1 installations and the web applications running in their respective Hosts, as indicated by the green arrows. However, you can manage only one NSJSP Server Class at a time. You cannot manage the NSJSP 5.0 installation with the NSJSP Manager, as indicated by the red arrows. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Managing NSJSP The Architecture of the NSJSP Manager NonStop Servlets for JavaServer Pages (NSJSP) 6.
5 Logging in NSJSP This chapter addresses the following topics: Logging Architecture Apache Tomcat Enhancements to the Logging Architecture NSJSP Enhancements to the Logging Architecture Logging Configuration Log Files Related to NSJSP Programming Considerations for Logging Commons Logging Logging Architecture The logging architecture of NSJSP is based on the Java Platform, Standard Edition logging architecture.
Handlers Logging in NSJSP Additionally, com.foo.bar1 and com.foo.bar2 are also child loggers of com.foo, and are peer loggers of com.foo.bar. Each log message is associated with a log level, which denotes the severity of the log. Similar to the log messages, a logger is associated with a log level. If no log level is associated with a logger, the logger inherits the log level from its nearest parent that is associated with a log level. Each logger can be configured with a set of handlers.
Logging in NSJSP Log Manager Log Manager The Log Manager tracks the global logging information. The Log Manager manages the following: The hierarchical namespace of logger objects. All named loggers are stored in this namespace. The logging control properties, which are simple key-value pairs that can be used by handlers and other logging objects. The following is the sequence of events that occur when an application attempts to write a log message: 1.
Apache Tomcat Enhancements to the Logging Architecture Logging in NSJSP Figure 5-1.
Logging in NSJSP NSJSP Enhancements to the Logging Architecture To overcome these inabilities, Tomcat replaces the java.util.logging implementation with a container-friendly implementation, called JULI. JULI allows a logging configuration file for each class loader. Because each web application hosted on the servlet container has its own class loader, allowing a configuration file per class loader leads to each web application having its own logging configuration file.
Logging in NSJSP Log Rollover NSJSPLogHandler. This class is an extension of the java.util.logging.Handler class. In addition, the NSJSP Log Handler class offers a logging feature, called Log Rollover. For information on configuring the NSJSP Log Handler, see Configuring Handlers on page 5-10. Log Rollover The log rollover feature enables you to archive log files based on predefined criteria. The log rollover feature is introduced in the T1222^AAL SPR of the NSJSP 6.0 release.
Logging in NSJSP Log Rollover datePattern Log rollover based on the datePattern attribute is called timestamp-based rollover. The datePattern attribute enables you to configure the timestampbased rollover. You can set the log files to roll over at regular recurring intervals, such as, after an hour, after a day, and after a week. Note. The end of an hour is marked by the change in hour of the clock and not at the completion of 60 minutes.
Logging in NSJSP Log Rollover Log Rollover Based on File Size Log Rollover Based on Timestamp The archiveDirectory Attribute Log Rollover Based on File Size The maxFileSize attribute governs the size-based rollover of log files. You can configure a threshold file size for log rollover. This value must be greater than zero. If the file size exceeds the specified threshold, the log file rolls over. The base threshold, which is the lower limit to archive the log files, is 10 MB.
Logging in NSJSP Logging Configuration Using the datePattern attribute in the logging.properties file, if you configure the log file to roll over on a daily basis, nsjsp.log.2008.08.30 rolls over to the specified directory when the date changes to August 31st 2008. Subsequently, a new log file is created, called nsjsp.log.2008.08.31, and the logs are written in this file.
Configuring Handlers Logging in NSJSP Configuring Handlers You can configure each handler using the configuration properties that are specific to the handler. NSJSP supports the following implementation classes: FileHandler NSJSPLogHandler FileHandler Table 5-2 lists the FileHandler configuration properties. Table 5-2. Configuration Properties of FileHandler Configuration Property level Description Default Value Specifies the log level.
Configuring Handlers Logging in NSJSP prefix Following is an example of the FileHandler: #4admin.org.apache.juli.FileHandler.level = INFO #4admin.org.apache.juli.FileHandler.directory = ${catalina.base}/logs #4admin.org.apache.juli.FileHandler.prefix = admin. NSJSPLogHandler Table 5-3 lists the configuration properties that can be specified for the NSJSPLogHandler. Table 5-3.
Configuring Handlers Logging in NSJSP Table 5-3. Configuration Properties of NSJSPLogHandler (page 2 of 2) Configuration Property datePattern Description Default Value Specifies the time interval at which the log file must roll over. '.'yyyy-MM-dd For the complete list of options to enable rollover, see Configuring for Log Rollover Based on Timestamp on page 5-17. archiveDirect ory Specifies the directory location where the rolled over log files reside. You can assign any directory location.
Logging in NSJSP Configuring Loggers In the given example, ${catalina.base}/logs/abc is the destination of the log messages where, abc is the name of the server class. The name of the log file will be abc..log. Multiple Handler Definitions Using the same Handler Class JULI allows multiple handler definitions using the same handler class. You must configure multiple handlers as follows: The handler name must begin with a number and a prefix string. The prefix string must end with ".".
Logging in NSJSP Configuring the NSJSP Formatter Class where, sample.bank - is the logger. level - is the log level property. INFO - is the log level value. - are the associated handlers. The following is an example of a child logger configuration whose parent logger is sample.bank: sample.bank.servlet.level = INFO sample.bank.servlet.useParentHandlers=true sample.bank.servlet.handlers = 1bankapp.com.tandem.servlet.logging.NSJSPLogHandler where, sample.bank.
Configuring for Log Rollover Logging in NSJSP Table 5-4. Literals in the Format Attribute Literal Data Type Description MESSAGE String The text message to be published. LEVEL String The message severity as indicated by the application. PROCESSNAME String The name of the JVM process. PIN Short The PIN of the JVM process. CPU Short The CPU in which the JVM process is running. SOURCE String The class and method from where the message originates.
Configuring for Log Rollover Logging in NSJSP Configuring the archiveDirectory Attribute Configuring for Log Rollover Based on File Size This section includes the syntax and examples that describe how to configure for rollover based on file size. The following is the syntax to configure maxFileSize-based rollover: com.tandem.servlet.logging.NSJSPLogHandler.maxFileSize = file size where, file size is the threshold size of the log file that triggers the rollover.
Configuring for Log Rollover Logging in NSJSP Configuring for Log Rollover Based on Timestamp This section includes the syntax and examples that describe how to configure for rollover based on timestamp. The following is the syntax to configure the datePattern-based rollover: com.tandem.servlet.logging.NSJSPLogHandler.datePattern = '.'datePattern value where, datePattern value is the time interval at which the rollover occurs and '.' improves the readability of the file name.
Configuring for Log Rollover Logging in NSJSP Table 5-7 describes the different time intervals at which rollover occurs. Table 5-7. Time Intervals for Rollover Attribute Description "yyyy" Rollover occurs after every year from the time the log file is created. The change in the value of yyyy triggers the rollover. "yyyy.MM" Rollover occurs after every month from the time the log file is created. The change in the value of MM triggers the rollover. "yyyy.MM.
Configuring for Log Rollover Logging in NSJSP Table 5-8. Behavior of Log Files in datepattern-based Rollover Log File Destination Complete Path of Log File archiveDi rectory New Location After Rollover abc.log (Default location) / abc.log.
Logging in NSJSP Configuring the logging.properties File Configuring the logging.properties File This section describes the contents of the logging.properties file. You can use the logging.properties file to configure log-related settings, such as, which logs must be written, where the logs must be written, and when the logs must rollover. The file contains java.util.logging elements, such as loggers and handlers, and various attributes to which you can assign values to control the logs.
Logging in NSJSP Configuring the logging.properties File The following list describes the settings of 1nsjsp.com.tandem.servlet.logging.NSJSPLogHandler: Destination - ${catalina.base}/logs/nsjsp Log level - INFO Rollover interval - '.'yyyy-MM-dd Archive directory for the logs that rollover - ${catalina.base}/logs/archive The following lines denote the configuration settings of the handler, called 1catalina.org.apache.juli.FileHandler: 1catalina.org.apache.juli.FileHandler.
Logging in NSJSP Configuring the logging.properties File The following lines denote the configuration settings of the handler, called 3manager.org.apache.juli.FileHandler: 3manager.org.apache.juli.FileHandler.level = INFO 3manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs 3manager.org.apache.juli.FileHandler.prefix = manager The following list describes the settings of 3manager.org.apache.juli.FileHandler: Log level - INFO Log directory - ${catalina.
Logging in NSJSP Configuring the logging.properties File The following lines denote the configuration settings of the handler, called 2console.com.tandem.servlet.logging.NSJSPLogHandler: 2console.com.tandem.servlet.logging.NSJSPLogHandler.level = INFO 2console.com.tandem.servlet.logging.NSJSPLogHandler.destination = STDOUT The following list describes the settings of 2console.com.tandem.servlet.logging.
Logging in NSJSP Configuring Logging for the NSJSP Container and Web Applications The logger writes log messages about the context component, /servletsj/admin. The context component, which refers to the Admin Web application, is located within the Host component, localhost. The localhost component, in turn, is located within the engine component, NSJSP. The following lines denote the log level and handler properties of the logger, called org.apache.catalina.core.ContainerBase.[NSJSP].[localhost].
Logging in NSJSP Configuring Logging for the NSJSP Container and Web Applications configure logging that is specific to the application. If an application-specific logging.properties file is not present, the settings in the generic logging.properties file, located in /conf apply. The settings in the web application-specific logging.properties file override the settings in the generic logging.properties file, which is located in /conf.
Logging in NSJSP Configuring Logging for the NSJSP Container and Web Applications The following example illustrates logging configuration for a web application: handlers = 1bankapp.com.tandem.servlet.logging.NSJSPLogHandler #This is the default handler .handlers = 1bankapp.com.tandem.servlet.logging.NSJSPLogHandler ############################################################ # Handler specific properties. # Describes specific configuration info for Handlers.
Logging in NSJSP Log Files Related to NSJSP sample.bank.servlet.level = INFO sample.bank.servlet.handler = 1bankapp.com.tandem.servlet.logging.NSJSPLogHandler sample.bank.util.level = SEVERE sample.bank.util.handler = 1bankapp.com.tandem.servlet.logging.NSJSPLogHandler Log Files Related to NSJSP This section describes the log files related to NSJSP. The default configuration of NSJSP creates five log files in the /logs directory per NSJSP installation.
Logging in NSJSP Log File Created by JULI Log File Created by JULI When the NSJSP server is running and the JULI framework is initialized, all log messages are written in the log file created by the JULI logging framework. Note. Under certain conditions, log messages are also written to the err file. For example, when the internal buffers of the NSJSP JNI library are full, log messages are written in the log file created by the JULI logging framework and in the err file.
Log Logging in NSJSP the Log interface (org.apache.juli.logging.Log) for the NSJSPInputBuffer.class: protected static org.apache.juli.logging.Log log = org.apache.juli.logging.LogFactory.getLog(NSJSPInternalInputBuff er.class); Log In JULI, the implementation of the Log interface is for the underlying logging implementation of java.util.logging. JULI implements the Log interface of Commons logging for the java.util.logging logging framework.
Logging in NSJSP Commons Logging .... public class SampleLoggingClass { private static Log _logger = LogFactory.getLog(SampleLoggingClass.class); .... .... public void sampleMethod() { ..... ..... if(_logger.isDebugEnabled()) { // Compose the message _logger.debug(message); } _logger.error(error message); } } Commons Logging The applications use different logging implementations, such as, log4j and java.util.logging. The logging implementations do not follow any particular standard.
6 Debugging NSJSP This chapter discusses the various ways of debugging applications deployed in NSJSP. Debugging using Java Debugger tool and Eclipse platform have been described elaborately in this chapter. This chapter discusses the following topics: Debugging using Java Debugger tool Debugging using Eclipse platform Debugging using Java Debugger tool Use the jdb command to start the Java Debugger tool and communicate with the web application to be debugged.
Debugging using Eclipse platform Debugging NSJSP 218431829 is the process ID (PID) of the NSJSP process to be debugged. Note: 1. You can open multiple jdb sessions and connect to any NSJSP processes in separate jdb sessions. 2. There is no limit for the Numstatic value for this option. 3. jdb provides all debug options like setting breakpoints, watch a field value, continue, step in, step out and so on.
Debugging using Eclipse platform Debugging NSJSP Add the following arguments in the Arglist of servlet.config file: -Xdebug -Xnoagent -Djava.compiler=none -Xrunjdwp:server=y,transport=dt_socket,suspend=n Set the Numstatic and Maxservers values to greater than or equal to 1 During NSJSP startup, when the port number is not specified in the servlet.config file, the debug ports are dynamically allocated to individual NSJSP processes. These allocated ports are captured in .
Debugging using Eclipse platform Debugging NSJSP 1. Go to Guardian shell and execute the following commands: scf assume $zztcp listopen mon * This lists all the NSJSP processes and their respective debug port numbers. For example: 2122 is the debug port for nsjsp process $Y1BX: \HEMAN.$Y1BX 0,732 8 2 TCP 2122 4. In Eclipse, set the necessary breakpoints. For more info, see the Eclipse website http://www.eclipse.org/ for more details. 5. Open the web application from the browser.
7 Migrating to NSJSP 6.1 This chapter compares the migration-related characteristics of NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1. This chapter also provides the considerations before migrating user applications from NSJSP 5.0 or NSJSP 6.0 to NSJSP 6.1. You can migrate your applications after you have installed and configured NSJSP 6.1. This chapter addresses the following topics: Comparison of NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.
Comparing Installation Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-1. Comparison of Installation Properties of NSJSP Versions (page 1 of 3) Factors NSJSP 5.0 NSJSP 6.0 NSJSP 6.1 NSJSP installation directory By default, NSJSP is installed in the /servlet_jsp directory. By default, NSJSP is installed in the /servlet_jsp directory. You can install NSJSP in a directory location of your choice.
Comparing Installation Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-1. Comparison of Installation Properties of NSJSP Versions (page 2 of 3) Factors NSJSP 5.0 NSJSP 6.0 NSJSP 6.1 Ability to contain multiple NSJSP installations in an iTP Secure WebServer environment No No Yes Allows single installation of NSJSP 5.0. If NSJSP 5.0 is already installed and you try to install NSJSP again, the script overwrites the existing installation.
Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-1. Comparison of Installation Properties of NSJSP Versions (page 3 of 3) Factors NSJSP 5.0 NSJSP 6.0 NSJSP 6.1 Online-upgrade feature in iTP Secure WebServer Not aware of the online-upgrade feature of the iTP Secure WebServer Same as in NSJSP 5.0 The setup script identifies the online-upgrade feature and configures NSJSP accordingly. For more information, see Chapter 1, Introduction to NSJSP.
Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-5 discusses the differences in the NSJSP 6.0 and NSJSP 6.1 servlet.config files. The Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 section discusses the conf/context.xml file that is included in NSJSP 6.0. Table 7-2 lists the differences in the NSJSP 5.0 and NSJSP 6.1 server.xml files. Table 7-2. Differences in the NSJSP 5.0 and NSJSP 6.1 server.
Migrating to NSJSP 6.1 Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Table 7-2. Differences in the NSJSP 5.0 and NSJSP 6.1 server.xml Files Element/Attribute Default Value in NSJSP 5.0 Default Value in NSJSP 6.1 Environment name="simpleValue" type="java.lang.Integer" value="30" PAGE 325Migrating to NSJSP 6.1 Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Table 7-2. Differences in the NSJSP 5.0 and NSJSP 6.1 server.xml Files Element/Attribute Default Value in NSJSP 5.0 Default Value in NSJSP 6.1 com.tandem.servlet.JMXCon nectionListener Engine name="NSJSP" defaultHost="localhost" debug="0" name="NSJSP" backgroundProcessorDelay= "60" defaultHost="localhost” Realm className="org.apache.cat alina.realm.
Migrating to NSJSP 6.1 Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 For more information on logging severity in NSJSP 6.1, see Chapter 5, Logging in NSJSP. port – Although the behavior of the server component with respect to the port attributes has not changed between NSJSP 5.0 and NSJSP 6.1, NSJSP 6.1 requires the port attribute to be explicitly set to -1. Listeners – The NSJSPServerLifeCycleListener is replaced by the ServerLifeCycleListener.
Migrating to NSJSP 6.1 Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Table 7-3. Differences in the NSJSP 6.0 and NSJSP 6.1 server.xml Files (page 1 of 2) Element/Attribute Default Value in NSJSP 6.0 Default Value in NSJSP 6.1 PAGE 328Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-3. Differences in the NSJSP 6.0 and NSJSP 6.1 server.xml Files (page 2 of 2) Element/Attribute Default Value in NSJSP 6.0 Default Value in NSJSP 6.1 Connector protocol="HTTP/1.1" connectionTimeout="0" acceptCount="25" maxThreads="75" protocol="HTTP/1.1" maxThreads="75" Note: The acceptCount property has no relevance in NSJSP 6.1 as the messages are obtained through the $RECEIVE file.
Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Note. Valve className is a new attribute introduced in NSJSP 6.1. Table 7-4 lists the differences in the NSJSP 5.0 and NSJSP 6.1 servlet.config files. Table 7-4. Differences in the NSJSP 5.0 and NSJSP 6.1 servlet.config Files (page 1 of 2) NSJSP 5.0 NSJSP 6.
Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-4. Differences in the NSJSP 5.0 and NSJSP 6.1 servlet.config Files (page 2 of 2) NSJSP 5.0 NSJSP 6.1 Xbootclasspath /a:$env(JAVA_H OME)/lib/tools .jar Not applicable in NSJ 1.5 and NSJ 6.0 Not available Dcom.tandem.s ervlet.CONTEX T_PREFIXES=/u rlB For more info, see Chapter 3, Configuring NSJSP.
Comparing Configuration Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-5. Differences in the NSJSP 6.0 and NSJSP 6.1 servlet.config Files NSJSP 6.0 NSJSP 6.1 Maxservers 12 4 Maxlinks 250 50 Linkdepth 25 50 TANDEM_RECEIVE_ DEPTH 25 50 Effect For more information on the properties, see The Installation-Specific servlet.config File on page 3-7.
Comparing Management Properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Difference in the NSJSP 6.0 and NSJSP 6.1 conf/context.xml files The conf/context.xml file in NSJSP 6.0 and NSJSP 6.1 are similar. However, the NSJSP 6.1 conf/context.xml file includes a sample configuration of the persistent session manager. Note. NSJSP 5.0 does not include the conf/context.xml file. However, in NSJSP 5.0, contexts were handled differently.
Comparing Logging Infrastructure in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Migrating to NSJSP 6.1 Comparing Logging Infrastructure in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1 Table 7-7 compares the logging properties in NSJSP 5.0, NSJSP 6.0, and NSJSP 6.1. Table 7-7. Differences and Similarities in NSJSP Versions Factors NSJSP 5.0 NSJSP 6.0 NSJSP 6.1 How is Logging achieved? Uses elements to configure application-specific logging. Uses the JULI logging framework with log rollover feature.
Migrating to NSJSP 6.1 Logging Configuration of Servlet Container Components This configuration creates a log file called NSJSP_catalina..log in the /logs folder. Note. In the default configuration of NSJSP 5.
Migrating to NSJSP 6.1 Logging Configuration of Servlet Container Components org.apache.catalina.core.ContainerBase.[NSJSP].[localhost].[/ser vlet_jsp/admin].level = INFO org.apache.catalina.core.ContainerBase.[NSJSP].[localhost].[/ser vlet_jsp/admin].handlers = 4admin.org.apache.juli.FileHandler According to the 4admin.org.apache.juli.FileHandler configuration, all the Admin-related logs are published in the admin..log file in the /logs folder. NSJSP 6.
Comparing Miscellaneous Properties Migrating to NSJSP 6.1 There is no explicit logging definition for the Engine component. Because the root logger is associated with 1nsjsp.com.tandem.servlet.logging.NSJSPLogHandler, the root logger publishes all messages to the same log file as the localhost. The following is the root logger configuration: .handlers = 1nsjsp.com.tandem.servlet.logging.NSJSPLogHandler For example, the logs are created in /logs/SC1.2010-0503.log.
Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 Table 7-9 lists the prerequisites of NSJSP 5.0 and NSJSP 6.1. Table 7-9. Prerequisites of NSJSP 5.0 and NSJSP 6.1 Operating System/Product NSJSP 5.0 NSJSP 6.1 NonStop operating system H06.03 or later J06.04 or later J-series, or H06.15 or later H-series iTP Secure WebServer 6.0 SPR ACA or later iTP Secure Webserver 7.
Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 In NSJSP 5.0, the default context definition for applications in a host is defined using the DefaultContext child element of either the Engine or the Host, in the iTP_server.xml file. In NSJSP 6.1, the default context for applications hosted in the entire NSJSP servlet container is defined in the conf/context.xml file. Note. The default configuration does not define any DefaultContext.
Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 Migrating to NSJSP 6.1 Table 7-10. Context Definition Attributes in NSJSP 5.0 and NSJSP 6.1 Attribute NSJSP 5.0 NSJSP 6.1 managerChecksFr equency Frequency of session expiry and related manager operations. Not Applicable ResourceParams Used to define the configuration parameters for the resource specified in the definition.
Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 Migrating to NSJSP 6.1 Session Manager Configuration In NSJSP 5.0, you can configure the session manager either in the Default Context or in the application-specific context definition, in the META-INF/context.xml file. In NSJSP 6.1, you can configure the Manager either in the conf/context.xml, which is the equivalent of Default Context, or in the application-specific context in the METAINF/context.xml file of the application.
Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 migration. Also, the Admin Web and Manager Web applications provide the same functionality in NSJSP 5.0 and in NSJSP 6.1. As a result, there is no need to migrate these applications from NSJSP 5.0 to NSJSP 6.1. Application Modifications This section discusses the modifications related to applications that you must consider while migrating from NSJSP 5.0 to NSJSP 6.1.
Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 Compiling the Application NSJSP 5.0 implements the Java Servlets 2.4 specifications whereas NSJSP 6.1 implements the Java Servlet 2.5 specifications. You must compile the application with the NSJSP 6.1 library jar files to ensure that the Java Servlet API used in the application is supported in NSJSP 6.1. The library files are located in the lib folder of the installation.
Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 5.0 to NSJSP 6.1 /usr/webmstr/webapps/myapp.xml, the NSJSP Manager copies the myapp.xml file to the appropriate location in NSJSP 6.1 with the name foo.xml and then deploys the application based on the contents of foo.xml. The directory where the context definition file is copied will always be /conf//. In this example, foo.xml is copied to the above location. Note. In NSJSP 5.
Considerations for Migrating Web Applications from NSJSP 6.0 to NSJSP 6.1 Migrating to NSJSP 6.1 Considerations for Migrating Web Applications from NSJSP 6.0 to NSJSP 6.1 Table 7-12 lists the prerequisites of NSJSP 6.0 and NSJSP 6.1. Table 7-12. Prerequisites of NSJSP 6.0 and NSJSP 6.1 Operating System/Product NSJSP 6.0 NSJSP 6.1 NonStop operating system H06.04 or later J06.04 or later J-series, or H06.15 or later H-series iTP Secure WebServer 6.0 SPR ACA or later iTP Secure Webserver 7.
Migrating to NSJSP 6.1 Migrating the Session Store Migrating the Session Store The session store configured in NSJSP 5.0 does not work in NSJSP 6.1, because there are differences in the field sizes in the table definition of the JDBC store. However, behavior of the session store in NSJSP 6.0 and NSJSP 6.1 is the same. To migrate sessions from NSJSP 5.0 or NSJSP 6.0 to NSJSP 6.1, complete the following steps: 1. Run one of the following commands to create the NSJSP 6.
Migrating to NSJSP 6.1 Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment In releases prior to NSJSP 6.1, NSJSP is installed in the default path (/servlet_jsp). This default NSJSP location is derived from the location of the iTP Secure WebServer, and it cannot be modified. A directory location can include only one NSJSP installation. As a result, you can have only one NSJSP installation in an iTP Secure WebServer environment.
Migrating to NSJSP 6.1 Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment This example shows how the new generic servlet.config file is created and how the existing servlet.config that includes NSJSP 6.0 specific information is renamed: Figure 7-1 shows the contents of the sample /conf directory contents after installing NSJSP 6.0. Figure 7-1. Sample conf Directory Created After NSJSP 6.0 Installation The servlet.
Migrating to NSJSP 6.1 Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment configuration details is modified and renamed to servlet-6.0.13.config. Additionally, the existing NSJSP 6.0 servlet.config file is backed up in a file, called servlet.config.2009-11-05:12.02.42. The sequence of events is as follows: 1. The NSJSP 6.0 servlet.config file is modified and renamed to servlet-6.0.13.config, and it continues to exist in the same location. 2. A new file, called servlet.
Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment Migrating to NSJSP 6.1 Figure 7-3. NSJSP 6.0 and NSJSP 6.1 Installation Locations httpd.config NSJSP 6.0 servlet.config NSJSP 6.0 Installation Default NSJSP 6.0 Installation location TS/MP Generic servlet.config httpd.config Webserver Renamed NSJSP 6.0 servlet.config NSJSP 6.0 NSJSP 6.1 servlet.config Environment A TS/MP NSJSP 6.0 Installation location NSJSP 6.0 Webserver NSJSP 6.
Migrating to NSJSP 6.1 Support for Multiple NSJSP Installations in a Single iTP Secure WebServer Environment NonStop Servlets for JavaServer Pages (NSJSP) 6.
8 Security Considerations This chapter discusses security considerations to secure data transfer from a web browser to the web server. The process includes validating a user, verifying whether a user has access to a particular web resource, and preventing malicious code from disrupting the NSJSP servlet container.
Establishing a Secure Link Security Considerations This chapter also discusses how security can be implemented in Web applications (Admin Web, Manager Web, and NSJSP Manager Web applications) that are used for administration and monitoring purposes. For more information on securing these Web applications, see Manager Web Application and NSJSP Manager Security on page 8-41. Figure 8-1 illustrates the security considerations discussed in this section. Figure 8-1.
Security Considerations Authenticating a User Authenticating a User The process of authentication involves obtaining user credentials and validating them against a database of user credentials. In NSJSP, this database is called a Realm. A web application need not always authenticate a user using a password. The user can also be authenticated using a certificate presented by the user. Because iTP Secure WebServer supports X.509 certificates, a user can also be authenticated in NSJSP using the X.
Security Considerations HTTP Digest Authentication where, Realm_Name is the name of the Realm. For more information on Realms, see Realms on page 8-7. When a user attempts to access a web application that is configured for the HTTP basic authentication, a logon page as shown in Figure 8-2 appears and the user is prompted to enter the username and password. Figure 8-2.
Security Considerations Form-Based Authentication where, Realm_Name is the name of the Realm. For more information on Realms, see Realms on page 8-7. When a user attempts to access a web application that is configured for the HTTP digest authentication, the logon page as shown in Figure 8-3 appears and the user is prompted to enter the username and password. Figure 8-3.
Security Considerations Form-Based Authentication The login form must contain HTML fields for entering a username and a password, and these fields must be named as j_username and j_password, respectively. For the form-based authentication to function properly, you must always set the action attribute in the login form to j_security_check.
Security Considerations HTTPS Client Authentication Figure 8-4. Logon Page for a Form-Based Authentication HTTPS Client Authentication The end user authentication using HTTPS (HTTP over SSL) requires the client to possess a Public Key Certificate (PKC). Both NSJSP and the iTP Secure WebServer support X.509 version 3 certificates. A web application can be configured for HTTPS client authentication by setting the type of authentication in the web.xml file to CLIENT-CERT.
Security Considerations Realms application resources is granted to all users possessing a particular role. There can be any number of roles associated with a username. Note. The Java Servlet specification defines declarative elements, such as securityconstraint, auth-constraint, user-data-constraint as part of the deployment descriptor to define an application's security requirements.
Security Considerations Realms contexts (web applications) configured in the Host. Any Realm definition in the Context overrides the Host definition. The Context element: Realms can be defined as child elements of a context (web application) in the context.xml file. The context.xml file for each application is located in the META-INF folder of the web application base directory, which will be located in the /webapps directory.
Security Considerations Realms Connecting to the Directory The connectionURL configuration attribute in the JNDIRealm defines the Realm’s connection to the directory server and the JNDI provider defines the format for this URL. Usually, an LDAP URL specifies the domain name of the directory server to connect, and optionally the port number and distinguished name (DN) of the required root naming context.
Security Considerations Realms By default, the Realm authenticates a user by binding to the directory with the DN of the entry for a user and the password provided by the user. If this bind succeeds, the user is considered to be authenticated For security reasons, a directory may store a digest of the user's password rather than the plain text version.
Realms Security Considerations roleSearch - Specifies the LDAP search filter for selecting role entries. It optionally includes pattern replacements for either the distinguished name ({0}) or the username ({1}) of the authenticated user, or both of them. roleName - Specifies the attribute in a role entry containing the name of that role. Roles as an attribute of the user entry You can specify role names as the values of an attribute in the user's directory entry.
Realms Security Considerations Table 8-1. Attributes in the JNDIRealm (page 2 of 3) Attribute Description connectionURL Specifies the connection URL that is passed to the JNDI driver while establishing a connection to the directory. contextFactory Specifies the fully qualified Java class name of the factory class that is used to acquire the JNDI InitialContext. By default, JNDIRealm considers that the standard JNDI LDAP provider is utilized.
Realms Security Considerations Table 8-1. Attributes in the JNDIRealm (page 3 of 3) Attribute Description roleSubtree Specifies whether multiple levels under the node specified by roleBase must be searched. You can set this attribute to true to search the entire subtree of the element specified by the roleBase property, for role entries associated with the user. The default value (false) results in searches of the top level subtree.
Realms Security Considerations MemoryRealm The MemoryRealm is a simple demonstration implementation of the Realm interface and is not intended for production use. During startup, the MemoryRealm loads information about all users, and their corresponding roles, from an XML document (by default, this document is loaded from /conf/nsjsp-users.xml). Changes made to the /conf/nsjsp-users.xml file will be effective only after NSJSP is restarted.
Realms Security Considerations JDBCRealm provides substantial configuration flexibility to adapt to existing table and column names, if your database structure conforms to the following requirements: Users table: There must be a table that contains one row for every user that the JDBCRealm must validate. The users table must contain at least the following two columns (it might contain more if applications require them): Username: The username to be validated by NSJSP when the user logs in.
Realms Security Considerations Table 8-3. JDBCRealm Attributes (page 2 of 2) Attribute Description digest Specifies the name of the MessageDigest algorithm used to encrypt user passwords stored in the database. If this attribute is not specified, user passwords are by default stored in plain text. For more information on digest passwords, see Digested Passwords on page 8-28. digestEncoding Specifies the character set for encoding digests.
Security Considerations Realms Example 8-1.
Security Considerations Realms Example 8-2. Sample Realm Configuration PAGE 370Realms Security Considerations Example 8-3 shows the UserDatabase resource definition in the GlobalNamingResources section. It also shows a UserDatabaseRealm definition that uses the UserDatabase resource in the Engine element. Example 8-3. Sample UserDataBase Definition … … PAGE 371Realms Security Considerations more information on JAAS, see http://java.sun.com/javase/6/docs/technotes/guides/security/jaas/JAASRefGuide.html NSJSP provides the required JAAS infrastructure to accept NonStop usernames and to authenticate users in the Safeguard subsystem. This means NonStop usernames and passwords can be used to authenticate users and groups in the Safeguard subsystem that can be used as user roles to authorize access to application resources.
Realms Security Considerations Attributes in the JAASRealm Table 8-5 lists the attributes that can be used in the JAASRealm. Table 8-5. JAASRealm Attributes Attribute Description appName Specifies the name of the application as configured in your login configuration file. userClassNames Specifies a comma-separated list of the names of classes that you have created for your user Principals.
Security Considerations Realms NonStop groups.
Realms Security Considerations The DataSourceRealm queries the database each time it attempts to authenticate a user. Therefore, changes made to the database will be immediately reflected in the information used to authenticate users. After a user has been authenticated, the user (and the user's associated roles) information is cached within NSJSP for the duration of a user login session.
Security Considerations Realms Example 8-4 shows how to define a JNDI datasource to connect to SQL/MX using the JDBC Type 2 driver. The JNDI resource can either be configured in server.xml or in the application-specific context.xml file. For more information on configuring JNDI resources, see http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html. Example 8-4. Defining a Global JNDI Datasource PAGE 376Security Considerations Realms The CombinedRealm provides the ability to combine multiple Realms of the same or different types. The CombinedRealm can be used to authenticate against different sources, provide fallback in case one Realm fails or for any other purpose that requires multiple Realms. Sub-Realms are defined by nesting Realm elements inside the Realm element that defines the CombinedRealm. Authentication will be attempted against each Realm in the order they are listed.
Realms Security Considerations even users that do not exist could result in a large number of user records getting cached, especially when the authentication of invalid users is deliberate, such as in a denial of service attack. To prevent unlimited growth of the cache, use the cacheSize attribute to indicate the maximum number of user records that may be cached. Sub-Realms are defined by nesting the Realm elements inside the Realm element that defines the LockOutRealm.
Security Considerations Digested Passwords Digested Passwords For each standard Realm implementation, the user's password (by default) is stored in plain text. In most environments, this situation is not acceptable because casual observers of the authentication data can collect enough information to log on successfully and impersonate other users. To avoid this problem, the standard Realm implementations support the concept of digesting user passwords.
Security Considerations Authorizing a User surrounding Engine element), but not inside a Context element for one of the involved web applications. If users access only unprotected resources in any of the web applications on this virtual host, they will not be challenged to authenticate themselves.
Web Resource Collection Security Considerations The security constraint, which is represented by the security-constraint element in a deployment descriptor, consists of the following elements that are used to secure a resource: web-resource-collection auth-constraint user-data-constraint While the web-resource-collection is a required element, auth-constraint and user-data-constraint elements are optional elements.
Security Considerations Authorization Constraint ... ... ... Authorization Constraint An authorization constraint establishes a requirement for authentication and specifies the authorization roles permitted to perform constrained requests. A user must be a member of at least one of the specified roles to be permitted to perform the constrained requests. The special role name * specifies all the role names defined in the deployment descriptor. Note.
User Data Constraint Security Considerations the strength of the transport layer protection. By default, the transport-guarantee element is not defined in the web.xml file. Table 8-8 lists the types of transport guarantee that can be defined in the web.xml file. Table 8-8. Types of Transport Guarantee Type Description INTEGRAL CONFIDENTIAL NONE Establishes a requirement for content integrity. Establishes a requirement for confidentiality.
Security Considerations Validating the Sender Validating the Sender While NSJSP uses the user’s credentials to authenticate and authorize a user, it also provides valve elements to validate the origin of a client request before the request is serviced. The valve element allows or denies requests originating from certain client’s hosts based on the client’s host name or IP address.
Remote Address Filter Security Considerations Table 8-9. Remote Host Filter Attributes Attribute Description classname Specifies the Java class name for this valve. You must set this attribute to org.apache.catalina.valves.RemoteHostValve. allow Specifies a comma-separated list of regular expression patterns with which the remote hostname is compared. If you specify this attribute, the hostname from an incoming request must match an expression for the request to be accepted.
Security Considerations Java Security Manager Java Security Manager The Java security manager can be used to restrict access to system resources, such as Java Virtual Machine (JVM) properties, methods, and sockets, thus safeguarding application data and services, and ensuring the security and reliability of NSJSP. This section explains some of the features of the Java security manager that are used in NSJSP. Note. The complete details of the Java security manager are beyond the scope of this section.
Security Considerations Configuring the Java Security Manager Example 8-9. Policy File Entry for the NSJSP Container (page 1 of 2) // These permissions apply to the nsjsp-logging code grant codeBase "file:${catalina.home}/bin/nsjsp-logging.jar" { permission java.security.AllPermission; }; grant codeBase "file:${catalina.home}/bin/nsjsp_bootstrap.jar" { permission java.security.AllPermission; }; ...
Security Considerations Starting NSJSP with the Java Security Manager Example 8-9. Policy File Entry for the NSJSP Container (page 2 of 2) // These permissions are granted to the NSJSP balancer web // application. grant codeBase "file:${catalina.home}/webapps/balancer/WEBINF/lib/catalina-balancer.jar" { permission java.lang.reflect.ReflectPermission "suppressAccessChecks"; }; // These permissions are granted by default to all web // applications.
Securing NSJSP Resources Using the permissions Directive Security Considerations Example 8-10. Starting NSJSP with the Java Security Manager # # NSJSP Java2 System policy file and Java2 VM option. # # Note: the "double" equalto signs "==" is not a typo!! This informs the JVM # to use this file exclusively and that all others are to be ignored. # set env(JVM_POLICY_FILE) $env(NSJSP_HOME)/conf/iTP_catalina.policy set NSJSP_SECMGR_POLICY -Djava.security.
Security Considerations Securing NSJSP Resources Using the permissions Directive By default, all web applications are granted read permission to all the file resources under the web application’s base directory. This enables the application to read the static resources. Permissions are granted to access the resources either through JNDI or through classes in the java.io package. The following sample iTP_catalina.
Security Considerations Package Protection in NSJSP permission java.lang.RuntimePermission "accessDeclaredMembers"; You must be careful before granting the accessDeclaredMembers permission to any codeBase. Note. HP recommends that you understand the impact of providing certain security permissions. You can find a list of all security permissions provided by Java at http://java.sun.com/javase/6/docs/technotes/guides/security/permissions.html.
Security Considerations Troubleshooting the Java Security Manager Troubleshooting the Java Security Manager The security manager can be configured to write debug logs by using the java.security.debug property. This can be useful in identifying the call and permission that caused a security exception from being thrown. All logs are written to the STDOUT file. By default, the file referenced by the STDOUT server class attribute is located in the /logs directory. For more information on the java.
Security Considerations Using Realms to Implement Security The Admin and Manager Web Applications are security-sensitive applications and proper security constraints must be implemented so that only authorized users are allowed access to these Web Applications. For more information on the Admin and Manager Web Applications, see Chapter 4, Managing NSJSP.
Security Considerations Monitoring Server Classes and Hosts Example 8-13.
A MBeans in the NSJSP Container This appendix describes NSJSP MBeans, how the MBeans are represented in the NSJSP Manager application, and lists the MBeans that are commonly used in NSJSP.
MBeans in the NSJSP Container Object Names and Attributes of MBeans The following are typical uses of MBeans in NSJSP: You can use MBeans to obtain the state of the component it instruments. The information obtained using MBeans can be of the following types: Information that is constant and does not change with time. For example, the MBean that instruments the Host component has the appBase attribute, which represents the directory where the web applications are placed.
MBeans in the NSJSP Container Object Names and Attributes of MBeans type=Manager, path=/sca6url/examples, and host=localhost represent the property-value pairs. Catalina:type=NamingResources,resourcetype=Context,path=/sca6ur l,host=localhost where, Catalina represents the domain. type=NamingResources, resourcetype=Context, path=/sca6url, and host=localhost represent the property-value pairs. JMImplementation:type=MBeanServerDelegate where, JMImplementation represents the domain.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager MBeans Representation in NSJSP Manager For ease of navigation, MBeans are organized in a tree structure comprising multiple tree nodes. A tree structure begins with a root node and ends with a leaf node. The root node of the tree denotes the process name and the first level child nodes denote the different domains registered with the MBean server. Each domain can contain multiple tree nodes.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager same domain, the properties (j2eeType for Servlet and type for Valve) of the key-properties list are not the same. Figure A-2 shows a tree view of the following MBean under the Servlet node: NSJSP:j2eeType=Servlet,name=HTMLManager,WebModule=//localhost/sc a6url/manager,J2EEApplication=none,J2EEServer=none where, NSJSP is the domain.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager Figure A-2. Tree View of an MBean Under the Servlet Node Figure A-3 shows a tree view of the following MBean under the Valve node: NSJSP:type=Valve,name=RequestTrackerValve,host=localhost where, NSJSP is the domain. type=Valve, name=RequestTrackerValve, and host=localhost are the property-value pairs. NonStop Servlets for JavaServer Pages (NSJSP) 6.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager Figure A-3. Tree View of an MBean Under the Valve Node As an exception, some MBeans might have properties with value none.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager Figure A-4. Node with Value none The leaf node is a hyperlink. Clicking the leaf node displays the values of the MBean attributes. Figure A-5 displays the MBean attributes and their associated values. NonStop Servlets for JavaServer Pages (NSJSP) 6.
MBeans in the NSJSP Container MBeans Representation in NSJSP Manager Figure A-5. Values of the MBean Attributes To view the description of the attributes, click Display Attribute Description link. Figure A-6 shows the description of the MBean attributes. NonStop Servlets for JavaServer Pages (NSJSP) 6.
Commonly Used MBeans in NSJSP MBeans in the NSJSP Container Figure A-6. Description of the MBean Attributes Commonly Used MBeans in NSJSP This section lists the important MBeans and their attributes. You can use the following MBeans to manage the Java resources that are deployed on a JVM: Thread Pool - Represents the connector thread pool. The object name is: NSJSP:name=http-0,type=ThreadPool Table A-1 lists only the important attributes associated with Thread Pool.
Commonly Used MBeans in NSJSP MBeans in the NSJSP Container Note. The NSJSP Manager application does not display the contents in the columns Type and Writable as shown in Table A-1. The values for the writable parameter are true or false. The default value is true. The attributes, which can be changed, do not have the writable parameter included. Host - Represents the configuration parameters of a Host called localhost.
Commonly Used MBeans in NSJSP MBeans in the NSJSP Container The object name is: NSJSP:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule ,name=//localhost/first (application name) Table A-4 lists only the important attributes associated Application Context. For more information about the Application Context attributes, see Table 3-17, Attribute List for the Context Element, on page 3-61. Table A-4.
Glossary This glossary defines terms used both in this manual and in other HP manuals. Both industry-standard terms and HP-specific terms are included. Admin Server Class. Refers to one of the server classes configured with an installation of NSJSP. Each installation of NSJSP results in 2 server classes. One server class will host and process requests for user application and the other is used by the Admin application.
Glossary CommerceNet CommerceNet. A consortium that was formed in Silicon Valley to promote electronic commerce over the Internet. Common Gateway Interface (CGI). A standard protocol used as the interface between web servers and the programs these servers use to process requests from web clients. Commons Logging. A component of Apache Commons project that provides a layer of abstraction over many popular logging implementations. connection.
Glossary domain domain. Namespace used to group MBeans that are registered with an MBean server. DTD. ISee Document Type Definition (DTD). EJB. ISee Enterprise JavaBeans (EJB) Enterprise JavaBeans (EJB). Enterprise JavaBeans (EJB) is a Java API developed by Sun Microsystems that defines a component architecture for multi-tier client/server systems.
GESA Glossary GESA. See Gigabit Ethernet ServerNet Adapter (GESA). Gigabit Ethernet ServerNet Adapter (GESA). A A single-port ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ systems and Ethernet LANs. A GESA can be directly installed in slots 51 through 54 of an I/O enclosure and slots 53 and 54 of a processor enclosure.
Glossary Internet Internet. Physically, a collection of packet-switching networks interconnected by gateways, along with protocols that allow them to function logically as a single, large, virtual network. When written in uppercase, INTERNET refers specifically to the DARPA Internet and the TCP/IP protocols it uses. interoperability. The ability of software and hardware on multiple machines from multiple vendors to communicate meaningfully. IP. See Internet Protocol (IP). IPSetup.
Glossary JDBC. JDBC. See Java Database Connectivity (JDBC). Java Management Extensions (JMX). Java technology that offers tools to manage and monitor different types of resources such as an application. JNDI. See Java Naming and Directory Interface (JNDI). Joint Photographic Expert Group (JPEG). An image format used to transmit graphics on the World Wide Web (WWW). JPEG. See Joint Photographic Expert Group (JPEG). JSP. See JavaServer Page (JSP) JULI.
Glossary Log Record. Log Record. Used to pass logging requests between the logging framework and individual log handlers. MBean attributes. A pattern in which an MBean provides the state and details of the managed resource. MBean object name. It is a unique identifier of an MBean. MBean server. A repository that stores all the MBeans in a JVM. Migration. Transitioning the web applications from one NSJSP version to another NSJSP version. Netscape. See browser. NonStop Kernel.
Glossary OSS applications OSS applications. POSIX compliant applications. OSS. See Open System Services (OSS). packet. The unit of data sent across a packet-switching network. While some Internet literature uses it to refer specifically to data sent across a physical network, other literature views the Internet as a packet-switching network and describes IP datagrams as packets. PATHMON process. The central controlling process for a NonStop TS/MP application. Pathway.
Glossary scalability scalability. The ability to increase the size and processing power of an online transaction processing system by adding processors and devices to a system, systems to a network, and so on. Secure Sockets Layer (SSL). A protocol for private communication on the World Wide Web and authentication of a web server by a web client. servlet mapping. It is the mapping between the URL and the servlet (configured to process the requests matching that URL). server.
Glossary Simple Mail Transfer Protocol (SMTP) Simple Mail Transfer Protocol (SMTP). The Internet standard protocol for transferring e-mail messages from one machine to another. SMTP specifies how two mail systems interact, and specifies the format of control messages the two mail systems exchange to transfer mail. Single Point Management. Ability to manage multiple NSJSP server classes and user applications using a single management application. SSL. See Secure Sockets Layer (SSL). STDERR.
TLD Glossary TLD. See Top-Level Domain (TLD) Top-Level Domain (TLD). Refers to the suffix attached to Internet domain names. There are a limited number of predefined suffixes, and each one represent a top-level domain. Current top-level domains include: com – Commercial businesses; this is the most common TLD gov – U.S. government agencies edu – Educational institutions, such as universities org – Organizations (mostly nonprofit) mil – Military net – Network organizations Unicode.
Glossary WWW hardware-independent documents that not only contained ASCII text but that also contained pictures, graphics, and voice and video elements. In addition to accessing documents, the WWW protocols can also be used to provide document searching facilities and also interaction with user-written or vendor-provided servers. WWW. See World Wide Web (WWW) protocols. XML. Short for Extensible Markup Language, a specification developed by the W3C.
Index A accessDeclaredMembers permission 8-39 access,failure value 8-41 Admin Server Class 3-2 Admin Web Application administering user definitions 4-79 groups 4-81 roles 4-82 users 4-80 architecture of 4-57 features of 4-59 login and security of 4-59 Admin Web Application operations administering Host 4-67 administering Realm 4-71 administering resources 4-74 data sources 4-74 enviornment entry 4-76 mail session 4-75 resource link 4-79 user database 4-77 administering server 4-62 administering valve 4-72 A
F Index F FileHandler 5-10 Filemap 3-33 Filemap Directive 3-29 filemaps.config 3-33 formatter 5-2 form-based authentication accessing a web resource 8-6 G Generic servlet.config 3-6 H handler 5-2 Hibernate 1-3 High-availability 1-11 HTTP/1.0 specification 8-3 I Installation directories 2-20 Installation-Specific servlet.
M Index login form action attribute 8-6 HTML fields 8-6 M Manager Web Application 4-85 managing web application 4-26 reloading 4-28 starting 4-27 stopping 4-26 undeploying 4-29 maxFileSize 5-6 MAXLINKS 3-28 MAXSERVERS 3-28, 3-32 maxWaitTimeSecs 3-26 MBeans domain A-2 in NSJSP container A-10 object name A-2 parameters in the NSJSP MBeans page 4-45 Multiple NSJSP installations 2-26 MyFaces 1-3 N NonStop SQL database 3-84 NSJSP 1-2 ServerClass 3-3 NSJSP Formatter 5-5 NSJSP installation directory structure
O Index in the HTTP Method Statistics page 4-20 in the NSJSP Connector Stats page 4-34 in the NSJSP Information page 4-31 in the Process View page 4-16 in the Server Class Processes page 4-32 in the Server Class Statistics page 4-38 in the Servlet Mappings page 4-23 in the URI Statistics page 4-19 in the Web Application Deployment from Desktop page 4-56 in the Web Application Deployment from Server page 4-54 using the Application Summary page 4-12 using the In-Memory Sessions page 4-18 operations using th
T Index server.xml 3-37 server_objectcode 3-11 Servlet server class 3-1 SERVLET_BANK 3-16 Session 3-2 Session object 3-2 SessionBasedCookieExpiry 3-22 SessionBasedLoadBalancing 3-22 setup script 1-4 signedBy entry 8-35 Spring 1-3 SSL 8-2, 8-3 StaticContentFilter 7-13 STDERR 5-27 Stderr 3-28 STDOUT 5-27 Stdout 3-28 W web.xml 7-13 X Xms 3-20 Xmx 3-19 Xss 3-20 X.509 certificate 8-2 Special Characters ${catalina.home} property 8-35 ${java.home} property 8-35 -Djava.security.
