Special Cases or Exceptions

There are a number of special cases that arise mostly from the fact that some Java ES shared components and some Java ES product components are bundled with Solaris 10. By virtue of this bundling, these Java ES components exist in the global zone, and therefore in any non-global zone that is created from the global zone.

Product Component Special Cases

• Message Queue is bundled with Solaris 10, and, as a result, is automatically propagated when non-global zones are created (unless you have first removed Message Queue from the global zone). Message Queue cannot be installed in a sparse root zone. When installed or upgraded in a global zone by the Java ES installer, Message Queue, by default, is propagated to non-global zones, unlike other product components.

• Application Server is bundled with Solaris 10, and, as a result, is automatically propagated when non-global zones are created (unless you have first removed Application Server from the global zone). When propagated in this way, the bundled Application Server, which is installed in /usr, cannot be upgraded by the Java ES installer in a sparse root zone (by default /usr is read-only). To address this problem, the bundled Application Server must be manually removed from the global zone before installing the Release 5 Application Server in a sparse root zone.

• Sun Cluster can only be installed in a global zone. Sun Cluster is not supported in non-global zones.

Shared Component Special Cases

• SJWC packages that are bundled with Solaris 10 (Update 1 and Update 2) cannot be removed by the Java ES installer. These older SJWC packages have had the SUNW_PKG_ALLZONES set to True, which means the package must be identical in all zones and can only be managed by the global administrator. As a result these packages must be manually removed in the global zone to be replaced by the correct packages.

  If the Java ES installer is attempting to install a selected component in a non-global zone and detects that SJWC needs to be upgraded, the installer will block. This happens when installing on Solaris 10, Update 1 and 2.

  As a workaround, a special script has been developed that will remove the old packages of SJWC from the global zone and replace them with SJWC 2.2.6, which has the correct zones propagation attribute setting. As a result SJWC 2 2.6 is propagated to all non-global zones.

• Common Agent Container. Version 1.1 is installed only when Sun Cluster, Sun Cluster GE, or Sun Cluster Agents are installed. It is not installed when the Synchronize All Shared Components option is selected. Only version 2.0 is installed in that case.

• Sun Explorer Data Collector. This shared component is installed only when Sun Cluster, Sun Cluster GE, or Sun Cluster Agents are installed. It is not installed when the All Shared Components option is selected.