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

to use than JDB. However, JDB is free. For further information on JDB visit the
web site www.java.sun.com/products/jdk/1.1/docs/tooldocs/solaris/jdb.html
• All of the IDEs contain sophisticated debuggers with graphical interfaces. They
tie directly into the source code and provide excellent symbolic debugging
capability. This makes them the easiest and most efficient means of debugging a
Java™ program. Any of the IDEs recommended above will provide good
debuggers. Remember that the choice of which IDE to use depends on whether
the development is being done directly on HP-UX or with remote targeting (as
described above).
• For debugging JNI problems (i.e., mixed Java™ and C/C++), HP provides an
enhanced version of the popular Gnu Debugger (GDB, also called the Wildebeast
Debugger or WDB). The HP enhancements to WDB (version 3.0.01 or later) allow
it to examine backtraces containing mixed language frames in Java™ thread stacks
of an application that is running on the HP Java™ Virtual Machine. For more
information, refer to the SDK release notes for your Java™ version. A word of
caution: the support for EJBs will probably only be found in the more expensive
versions of the individual products (i.e., the "Professional" or the "Enterprise"
editions of the products). Check the product feature lists before purchasing.
Developing a web service
The HP-UX server platform is ideally suited for hosting Web Services. Typically these
services are hosted by an application server, such as BEA's WebLogic Server, a
fully-featured, standards-based application server that provides the foundation on
which an enterprise can build reliable, scalable, and manageable applications.
Tuning a Java™ application for optimum performance
Performance tuning first requires the determination of the cause of the poor
performance. The problem could be due to lack of system resources and this will require
changes to the kernel parameters or to the system components (memory, number of
CPUs, etc.). Alternatively, it could be due to programming practices that cause
unnecessary system activities (like unnecessary garbage collection). This could require
changes to the program source code.
HP provides a number of tools to analyze performance. These tools start at the overall
application level and work progressively towards the root cause. HP OpenView
Transaction Analyzer provides a comprehensive understanding of current application
performance measured against service level requirements with detailed data for problem
analysis. Then, the system level tools to analyze individual machine and portions of
applications include GlancePlus, Prospect, top, netstat, and many others. The lower
level tools include HPjmeter (-Xeprof option). For a good description of the complete
list of performance tools and the appropriate usage of each of them, refer to the technical
paper entitled "Java™ Profiling on HP-UX".
8 Introduction