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

application runs in its target environment on the HP-UX server. Typical desktop
workstation operating systems include Windows, Linux, and Unix.
Develop on another platform and port to HP-UX. In this environment, the
development platform can be any machine that supports a compatible version of
the Java™ Runtime Environment, i.e., the Java™ Virtual Machine and associated
class libraries. If this option is chosen, the portions of this paper that will be of
special interest are those that deal with setting the HP-UX kernel parameters for
optimum server performance.
Developers have strong individual preferences for the choice of development platform
and development tools. Therefore, HP has established partnerships with a wide variety
of leading tool vendors in order to provide choices. Furthermore, no particular choice
is given preference over the others: all are supported equally by HP.
The fundamental differences have to do with where the development tool runs. If the
decision is to use EMACS or vi, then the recommended option will be to run the editor
directly on the server. If on the other hand an IDE will be used, then the recommended
option will be to run the tool on a desktop workstation with remote targeting of the
HP-UX server.
In the case of native development on HP-UX, the tool runs directly on the HP-UX server
and the editing of source code and the debugging information is displayed remotely
on an attached graphics terminal. The terminal can be a directly-connected graphics
terminal, an X-term, or an X-term emulator running on a Windows desktop.
Recommended tools for native development include EMACS, vi, and Simplicity by
Data Representations. When installing EMACS, it is recommended that you use an
HP-UX configuration file that is available for download from the EMACS page
referenced in this paragraph. Note that EMACS only provide code editing and
color-coding. Simplicity, on the other hand, is an inexpensive, full-featured Integrated
Development Environment that includes a debugger as well as support for the design
of web pages, applets, servlets, EJBs, etc. The best development performance with
Simplicity will be achieved if used with a directly-connect graphics terminal. This is
because Simplicity, like most IDEs, is written in Java™ and runs on a Java™ Virtual
Machine. There is a known graphics performance problem in the Java™ Software
Development Kit in releases 1.3 and below that causes slow performance when any
Java-based GUI is displayed by means of an X-term. This performance problem is also
the reason for the blanket statement (above) that IDEs are recommended for use only
on desktop workstations with remote targeting of the server. (The remote graphics
performance problem is repaired in SDK 1.4.)
In the case of development on a desktop workstation with remote targeting of an HP-UX
server, it is important to choose an IDE that supports a remote connection to HP-UX.
While most IDEs are known to support such a remote connection by means of the
Java-standard JPDA interface, HP has worked closely with specific IDE vendors to
ensure that their products function well with the HP Java™ Virtual Machine on HP-UX.
6 Introduction