HP-UX Java™ - How To Develop Java Applications for HP-UX

For a collection of techniques, tuning guidelines, tips and general information about
Java™ performance tuning, go to the Java™ performance tuning website on DSPP.
Testing for Performance and Reliability
Stress testing is normally done by using tools that simulate a larger number of clients
simultaneously accessing the web server and the back-end parts of the application.
There are several excellent tools available that provide this load from a client platform
(usually a Windows-based platform). Some highly-rated product for this task are Astra
LoadTest from Mercury Interactive, SilkPerformer by Segue Software, e-Load from
Empirix, and WebLoad from Rad View.
During the testing, the server-side performance can be analyzed by means the tools
described in the section above and the performance bottlenecks can be identified.
Special considerations for cross-platform development
100% pure Java™ applications do not require a rebuild on every target platform.
However, there may be other reasons why a development team may have a need to
do cross-platform builds. A common reason is that a build on the target platform serves
as a simple acceptance test for the target platform JDK. Another typical reason is that
nightly builds in the source code management systems may be run on a platform
different from the development platform. Finally, if the application has JNI code, at
least the native portion needs to be built separately on each target platform. Thus, most
large Java™ projects end up with a requirement of cross-platform build tools.
Traditionally, teams doing cross-platform development have been required to port
their build infrastructure to each target platform. For Unix systems, this meant that the
developers had to customize their make files to ensure that they worked well with the
indigenous version of the make.
In recent years, gnumake has become a popular option that ensures cross-platform
portability of make files. Some development teams have switched to shell or perl-based
build scripts to ensure such portability.
One of the most recent entrants in the arena of customization is Apache Ant, an initiative
of the Apache Software Foundation. Apache Ant uses an XML based configuration file
that defines a target tree where various tasks get executed. Instead of using shell
commands for customization of dependencies, Apache Ant can be extended using
Java™ classes.
While Apache Ant is not the ultimate solution for all build issues, it has advantages
that some projects might find compelling. The tool is 100% Java, so the tool and the
customizations can be easily carried over to the target platform. The use of XML based
configuration files is a definite improvement over the somewhat arcane syntax of make.
Testing for Performance and Reliability 9