test

Sun Java Enterprise System 5 Installation Planning Guide

An Illustrative Example: Install Application Server in a Sparse Root Zone

The following example is provided to draw out some of the complexities involved in Java ES zones support. In this example, the objective is to install Application Server in a Solaris 10 sparse root zone. This installation is complicated by the fact that Application Server (as well as Message Queue, upon which Application Server depends), is bundled with Solaris 10, and therefore the bundled version is installed in all non-global zones. For more information, see Product Component Special Cases.

To install Application Server in a sparse root zone, you must first remove the bundled version. (You cannot simply upgrade the bundled version in the sparse root zone because it is installed in a read-only directory). To remove the bundled version from the sparse root zone, you must remove it in the global zone.

In addition, Message Queue is installed in the global zone, representing a departure from Scenario 3 of Table A–2, in which only shared components (not product components) are installed in the global zone. However, Message Queue cannot be installed in a sparse root zone, because it installs in a read-only directory, so it must be installed and upgraded in the global zone.

The procedure is as follows:

  1. Verify Solaris 10 is running on your system.

    This example assumes a clean version of Solaris 10 with no Java ES components having been explicitly installed in the global zone.

  2. Create a sparse root zone (configure, install, and boot it).

    This zone will include any Java ES components that are already installed in the global zone, namely the versions of Message Queue and Application Server bundled with Solaris 10.

  3. Remove the bundled version of Application Server from the global zone.

    This must be performed by manually removing Application Server packages:

    pkgrm SUNWascmnse SUNWaslb SUNWasut ...

    Where the full set of packages can be obtained using the following command:

    pkginfo -I|grep -I application server

    The results would include packages such as:

    SUNWascmnse, SUNWaslb, SUNWasut, SUNWasac, SUNWasdem, SUNWasman, SUNWaswbcr, SUNWasacee, SUNWashdm, SUNWasmanee, SUNWascml, SUNWasJdbcDrivers, SUNWasu, SUNWascmn, SUNWasjdoc, SUNWasuee

    And might include localization packages as well:

    SUNWLocaleasacee, SUNWLocaleascmnse, SUNWLocaleasu, SUNWLocaleasuee

    The removal of Application Server from the global zone is propagated to the sparse root zone that was created in Step 2. (This step and Step 2 can be performed in reverse order.)

  4. Install Java ES 5 Shared Components in the global zone.

    1. Run the Java ES installer in the global zone.

    2. Select All Shared Components from the component selection panel. Do not select any other component.

    3. Complete the synchronization of shared components. All of the shared components are now synchronized in the global zone and propagated to all non-global zones.

  5. Upgrade Message Queue in the global zone.

    The version of Message Queue bundled with Solaris 10 is already installed in the sparse root zone by virtue of Step 2. To upgrade Message Queue in the sparse root zone, simply upgrade it in the global zone; the upgrade will propagate to the sparse root zone. (Message Queue is the only product component which cannot be installed in a sparse root zone, but when installed in the global zone, will propagate to non-global zones.)

    1. Run the Java ES installer in the global zone.

    2. Select Message Queue in the component selection panel. Do not select any other component.

    3. Complete the upgrade of Message Queue.

  6. Install Application Server in the sparse root zone.

    1. Run the Java ES installer in the sparse root zone.

    2. Select Application Server in the component selection panel. Do not select any other component for upgrade. De-select Message Queue if it is selected.

    3. Complete the installation of Application Server.