B nonstop specific configurations, Nonstop platform configurations, Determining the application parameters – HP Integrity NonStop J-Series User Manual
Page 320: Determining the maximum capacity of nsjsp instance, Appendix b: nonstop specific configurations
![background image](/manuals/397993/320/background.png)
B NonStop Specific Configurations
This section provides the general information about NonStop Platform configurations required for
the Spring, Hibernate, MyFaces, or Axis2/Java frameworks.
•
“NonStop Platform Configurations” (page 320)
•
“Module File Caching Configurations” (page 330)
For Spring, Hibernate, and Axis2/Java framework specific configurations, see:
•
“Spring Framework Configurations” (page 34)
•
“Hibernate Framework Configurations for NonStop Systems” (page 106)
•
“Axis2/Java Framework Configurations for NonStop Systems” (page 195)
NOTE:
There is no specific configuration for MyFaces framework.
NonStop Platform Configurations
On a NonStop system, an application developed using the Spring, Hibernate, MyFaces, or
Axis2/Java frameworks is deployed as a web application under the NSJSP container. Thus, it
inherits all the NSJSP properties and configurations, and runs like any other NSJSP web application
running on a NonStop system. This section discusses the following tasks:
•
“Determining the Application Parameters” (page 320)
•
“Determining the Maximum Capacity of NSJSP Instance” (page 320)
•
“Configuring iTP WebServer for Spring, Hibernate, MyFaces, and Axis2/Java Applications”
(page 321)
•
“Configuring NSJSP for Spring, Hibernate, MyFaces, and Axis2/Java Applications” (page 325)
Determining the Application Parameters
You need to determine the following parameters for your application:
•
Average Response Time
•
Average Load
•
Maximum Load
For a unit response time, the number of active requests to the iTP WebServer is a maximum of its
static capacity during the average load conditions and during peak load conditions, it is a maximum
of its dynamic capacity.
For example,
If the average response time of your application is 1 second and the iTP WebServer is configured
to handle 100 requests statically and 50 requests dynamically, then during average load conditions,
the number of active requests to the iTP WebServer can be a maximum of 100. During peak load
conditions, 50 more requests can be served dynamically and hence, the active requests to the iTP
WebServer can be a maximum of 150. Further requests are queued up and remain inactive until
started by httpd.
The other parameters, Average Load and Maximum Load, help you decide the configuration of
the static and dynamic httpd processes of the iTP WebServer.
Determining the Maximum Capacity of NSJSP Instance
Before configuring NSJSP parameters, you must determine the capacity of a single instance of
NSJSP. To determine the maximum load for a single instance of NSJSP, it is important to first
configure the relevant TS/MP and server parameters of NSJSP to their maximum limit in the following
way:
320 NonStop Specific Configurations