HP-UX Containers (SRP) A.03.01 Administrator's Guide

94
16.6 Deploying applications
In order to determine how to deploy applications for use by workload containers, you must first
determine if the application is supported for single or multi-instance deployment.
16.6.1 Single instance applications
While nearly all applications can be executed within a container environment, some applications do
not support multiple instances of the same application executing on the same system concurrently. For
these applications, HP recommends that you do not run multiple instances of these applications, even
when the instances are located in separate containers, HP recommends that you install the application
under the /var/hpsrp/container_name/ directory if user-specified installation location is
supported by the vendor.
If you need to execute single instance applications in more than one container, consider using system
containers.
16.6.2 Multi-instance applications
There are two models to deploy multi-instance applications within a container environment:
• Shared executable: In this model, the application is installed once per system in a shared
location. The application can require a set of files to be replicated and configured per
instance. HP recommends that you locate per instance files under the
/var/hpsrp/container_name/ directory when supported by the vendor.
• Per-container installation: For applications that support multiple installations per system,
you can install the application for each container in which it will be executed. HP
recommends that you install the application under the /var/hpsrp/container_name/
directory.
16.6.3 Deploying applications with the application templates
HP-UX Containers includes special templates for deploying key applications that use the shared
executable model. The ssh, apache, and tomcat templates fully deploy these applications within
the container using the shared executable model. The oracledb template configures the container
for shared executable Oracle usage; however you must first install the Oracle database product on
the system in the desired location. Optionally, you may also use the custom template to help deploy
an Oracle database for your container. If you are installing an Oracle database under the
/var/hpsrp/container_name directory, the oracledb or custom templates are not required.
16.6.4 Ensuring access to application files located outside the container home directory
If the application files are not all located under /var/hpsrp/container_name/, you must ensure
that the compartment rules definition for the container includes sufficient capability to allow execution.
For executable files, READ capability is generally sufficient, while configuration and data files will
typically require READ and WRITE capability. See 15.8 System templates and 16.8.6 Custom
template for information on using the custom template to define application specific compartment
access rules for your container. In addition to any installed files, the application can also create files
and directories during execution time. See 18 Verifying and troubleshooting for instructions on using
Discover Mode if you are unable to determine the access rules required by the application.
16.6.5 Best bractices for application deployment with workload containers
Follow these best practices when deploying application with workload containers:
• Deploy as much of the application as possible under the container home
directory.
This minimizes the need to customize compartment access rules. When the application is