Solaris 10 Zones

This section contains a brief description of Solaris 10 zones support for the current release of Java ES. An installation sequence example is included.

Overview of Solaris Zones

The Solaris 10 zones (also known as Solaris containers) feature provides a means of creating virtualized operating system environments within an instance of Solaris OS. This allows one or more processes to run in isolation from other activities on the host. For example, a process running in a zone will only be able to send signals to other processes in the same zone, regardless of user ID and other credential information.

Every Solaris 10 host contains a single global zone. The global zone is both the default zone for the host and the zone used for system-wide administrative control. All processes run in the global zone if no non-global zones are created by the global administrator. Some Java ES components, such as Sun Cluster software can only be installed in the global zone.

A non-global zone can be thought of as a box. One or more applications can run in this box without interacting with the rest of the host. Each non-global zone has what appears to be its own instance of an installed Solaris 10 operating system with configuration and other information unique to that non-global zone. The default configuration for a non-global zone is to share portions of its file system with the global zone (as a read-only loopback file system mount). For Java ES, all non-global zones must be created as “whole root” zones, meaning that there are no inherited file systems.

Zones Support for This Release of Java ES

The following list describes the level of Java ES zones support for this release of Java ES:

1. Java ES can be installed in the Global zone when non-global zones already exist.

2. Non-global zones can be created after Java ES is installed in the global zone.

3. Java ES can be installed in a whole root non-global zone even if another Java ES installation is already installed in the global zone.

4. Installing Java ES into the default sparse root non-global zone is not supported. The Java ES installer cannot proceed if a sparse root file system is encountered.

5. Java ES can be installed in the global zone even when Java ES has already been installed in the whole root non-global zone.

Solaris 10 Zones Example

This example installs Java ES software in a Solaris 10 non-global zone.

To Develop a Sequence for Solaris 10 Zones

The following high-level tasks are required:

Steps

1. Verifying that Solaris 10 is installed on your host

   The global zone is automatically created.

2. Verifying that all the non-global zones specified in your implementation plan have been created by the global zone administrator as “whole root” zones

   For information on creating non-global zones, refer to Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

3. Starting the Java ES installer in the desired non-global zone

4. At component selection, choosing the components you want

   Some components cannot be installed in a non-global zone because they require access to global zone capabilities. These components are unavailable at component selection.

5. Running the installation

6. Viewing the Installation Summary and Log

7. Completing postinstallation configuration as needed

   Chapter 6, Configuring Components After Installation provides post-installation configuration instructions.

8. Starting components

   Chapter 7, Verifying Installed Components provides procedures for starting and stopping the Java ES components.

9. Repeating this process in additional non-global zones as needed