The following list describes the level of zones support for this release of Java ES:
Both whole root zones and sparse root zones are supported.
Java ES can be installed in the global zone when non-global zones already exist.
Non-global zones can be created after Java ES is installed in the global zone.
All shared components in a zone must be from the same release of Java ES.
Whole root and sparse root deployments of Java ES should not be mixed on a single computer.
The Java ES installer can install Java ES components in sparse root zones with the following exceptions:
Sun Cluster software, Sun Cluster Geographic Edition, and Sun Cluster Agents can only be installed in the global zone.
Message Queue can only be installed or upgraded in the global zone, or in a whole root zone.
Shared components can only be installed or upgraded in the global zone, or in a whole root zone.
Before Application Server can be installed into the sparse root zone, any version of Application Server that is bundled with the operating system must be manually removed from the global zone.
The Java ES installer controls propagation of the packages it installs in the global zone:
Shared components are always propagated.
Message Queue and Java DB are always propagated.
All other product components are never propagated.
If you have a previous version of Java ES installed in a whole root zone, you should not install Java ES in the global zone.