The following list describes the level of zones support for this release of Communications Suite:
Both whole root zones and sparse root zones are supported.
Communications Suite can be installed in the global zone when non-global zones already exist.
Non-global zones can be created after Communications Suite is installed in the global zone.
Communications Suite can be installed in the global zone even when Communications Suite has already been installed in the whole root non-global zone. Also, Communications Suite can be installed in a whole root non-global zone even if another Communications Suite installation is already installed in the global zone.
All shared components in a zone must be from the same release of Communications Suite. Shared components are automatically synchronized to match the most recent Communications Suite release.
Whole root and sparse root deployments of Communications Suite should not be mixed on a single computer.
Communications Suite can be installed into non-global 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 non-global zone.
Before Application Server can be installed into the non-global sparse root zone, any version of Application Server that is bundled with the operating system must be removed from the global zone.
The installer does not install shared components or Message Queue into sparse zones. If you attempt to do this, installation halts and you receive a message telling you that shared components and Message Queue must bed installed in the global zone.
The installer controls propagation of the packages it installs in the global zone:
Shared components always propagate.
Message Queue always propagates.
All other product components never propagate.
The Sun Java Web Console shared component can only be upgraded in the global zone.