Application Server and Message Queue components are bundled and pre-installed as part of Solaris 10. These packages are installed under /usr directory.
Global zone installation:
Before installing, make sure you remove the version of application server that is bundled in Solaris 10. Refer the Java ES installation guide for instructions.
If Application Server 8.2 has been installed through Java ES 5 Update 1, it is automatically upgraded by the Application Server installation along with shared components. Refer to Java ES Update 1 Installation Planning guide for information about shared components
Sparse zone installation:
If global zone has a version of application server bundled in Solaris, remove this application server installation. Refer to Java ES 5 Update 1 Installation guide for instructions on how to uninstall this application server installation.
If there is a version of Application Server 8.2 installed through Java ES 5 Update 1, it is automatically upgraded to Application 9.1 installation along with shared components. Refer to Java ES Update 1 Installation Planning guide for information about shared components.
The version of Message Queue (MQ) that is bundled as part of Java ES 5 Update 1 is 3.7 UR1 and the one bundled with Application Server 9.1 is 4.1.
If you do not have MQ installed or if you have a version of MQ lower than 4.1 on the global zone, the Application Server 9.1 installer (running on sparse local zone) will not be able to automatically install or upgrade MQ on global zone. Before you run the Application Server 9.1 installer in sparse local zone, you need to download Message Queue 4.1 standalone package-based installation from and install it in global zone. Alternatively, you can install Sample Applications from Application Server 9.1 installer, which will install MQ 4.1 in global zone or upgrade the existing MQ in global zone.
If global zone has a version of application server installed through Java ES or through Application Server 9.1 installation, they are set not to propagate to local zones. You can have another copy of the installation in sparse zone. If a sparse zone already has an application server installation through Java ES, you can upgrade that version.
Installations on whole root local zones are much simpler because all components of Application Server (including shared components, MQ, HADB) can be installed and they do not interfere with packages in other global and sparse zones.