Sun Java Enterprise System Zone Limitations

The components that make up the Sun Java Enterprise System (JES) depend on some shared components; this creates some limitations in working with zones. As a JES component, Message Queue is subject to these limitations. In a zone 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 nonglobal zones are upgraded if necessary.

• Shared components cannot be installed in sparse-root zones because of the read/only file system. 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 to nonglobal zones. In particular, since Message Queue is installed in the /usr directory, it must be installed or upgraded in the global zone first.

For more information on zones and their use in JES, see the following sources:

• Sun Java Enterprise System Installation Guide for UNIX, Chapter 2 (“Example Installation Sequences”), section “Solaris 10 Zones Examples”

• Sun Java Enterprise System Installation Planning Guide, Appendix A (“Java ES and Solaris 10 Zones”)