Java Enterprise System Zones Limitations

The components that make up the Java Enterprise System depend on some shared components; this creates some limitations in working with zones. In a zones environment, shared components are governed by the following rules.

• All shared components within a zone must be of the same JES version. This requirement has three consequences.

  • If you want to install different versions of shared components, each version must reside in a separate zone.

  • Within a zone, if a shared component is upgraded or a later version is installed then all shared components must be upgraded.

  • When you install shared components in the global zone, you must take care that shared components in non global zones are upgraded if necessary.

• Shared components cannot be installed in sparse root zones because of the read/only file system in sparse root zones. Instead, they must be installed in the global zone. Those product components that depend on shared components must first be installed in the global zone and then propagated into non-global zones.

These requirements affect the installation of Message Queue because it is a component product of Java Enterprise System and, as such, is limited in its use of zones.

The Message Queue product is installed into the /usr directory and must therefore be installed or upgraded in the global zone first.