HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

Table 3 Comparison of transition using stand-alone ARIES and HP 9000 Containers
HP 9000 Containers transitionStand-alone ARIES transition
All dependencies are included in the HP 9000 file image
that is used to create a container
Must identify and transfer application dependencies
manually
The container has PA-RISC virtualized user-space
environment
There is no PA-RISC environment on the Integrity server
except for system libraries and applications
PA-RISC development environment comes along with the
HP 9000 file image
Must use a separate product called XPADE for PA-RISC
C/C++ code development
Installation and patching of applications do not need
workarounds
Direct installation and patching of applications might need
some workarounds (for example, if the HP-UX version and
platform information are verified)
System management and resource monitoring related
applications generally do not run inside the container
Non kernel intrusive system management applications can
be run on ARIES
Might need to switch to native shells and commands in
script intensive environments
Better performance compared to containers if applications
are highly script intensive
There are some additional management tasks related to
containers
Does not introduce any new manageability aspects
Changes to SG packages are required to integrate with
containers
No changes to SG packages other than that required for
SG version upgrade
1.9 ISV software license and support
ISV product license and support issues must be discussed directly with the respective application
vendors. HP does not own issues related to software license (LTU or RTU) migration during
application transition to a new platform. If licensing policy explicitly prohibits copying applications
to a new server, HP recommends that you apply for fresh licenses before using HP 9000 Containers.
1.9 ISV software license and support 13