Chapter 1 Installing Application Server Software

This chapter provides instructions for installing the Sun Java System Application Server software. The following topics are discussed:

• Distribution Types and Their Components

• Installing GlassFish v2

• Application Server 9.1 with Java ES 5 Update 1

• Installing Application Server 9.1

• Application Server and Solaris 10 Zones

Distribution Types and Their Components

You can download GlassFish Application Server from https://glassfish.dev.java.net/public/downloadsindex.html. The GlassFish v2 distribution includes the Application Server software, the Sun Java System Message Queue 4.1, Java DB, and ant 1.6.5. You can run GlassFish on Solaris SPARC, Solaris x86, Linux, Windows, and Mac OS.

Application Server 9.1 product distribution is available as: Application Server 9.1 with HADB and Application Server 9.1 without HADB. The standalone Application Server 9.1 is available at http://www.sun.com/download.

Application Server 9.1 without HADB includes the load balancing plug-in, Java DB, and Sun Java System Message Queue 4.1. Application Server 9.1 with HADB includes the load balancing plug-in, Java SE Development Kit (JDK) 5, Java DB, Sun Java System Message Queue 4.1, and HADB.

The Java ES 5 Update 1 distribution includes a Application Server 9.1 distribution as an optional download. This distribution includes HADB in addition to the load balancing plug-in, Java Development Kit (JDK) 5, Java DB, and the Sun Java System Message Queue 4.1.

Application Server 9.1 is also part of the Java EE SDK and the Java Application Platform SDK. You can download these distributions from http://java.sun.com/javaee/downloads/index.jsp.

You can download the latest version of Sun Java System Access Manager Policy Agent 2.2 from http://www.sun.com/download. For more information on how the Access Manager Policy Agent works with the Application Server 9.1, see Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Application Server 9.0/9.1 on docs.sun.com.

Installing GlassFish v2

This section provides instructions for installing GlassFish v2 distribution and for installing the load balancing plug-in for GlassFish v2. This distribution does not support upgrades or patching.

• To Install GlassFish Application Server

• To Install the Load Balancing Plug-in (standalone)

To Install GlassFish Application Server

Before You Begin

Get JDK (Java SE Developerment Kit) 5 or higher from http://java.sun.com/javase/, if you are using Solaris, Linux, or Windows..

If you are using Mac OS X, you need to download JDK 5 (supported on Mac OS X 1.4 or later) from http://www.apple.com/support/downloads/java2se50release3.html and make JDK 5 the default JVM.

1. Download the GlassFish v2 distribution https://glassfish.dev.java.net/public/downloadsindex.html.

2. Set the environment variable JAVA_HOME to point to the directory in which JDK 5 is installed.

3. Run the following command:

   java -Xmx256m -jar <filename>.jar

4. Set ANT_HOME to point to the ant 1.6.5 installation, which is at <downloaded-dir>/glassfish/lib/ant directory.

5. Navigate to the glassfish directory:

   cd glassfish

6. If you do not want clustering capabilities, run the following command:

   ant -f setup.xml

   • If you want to use GlassFish with clustering, change the command to:

     ant -f setup-cluster.xml

To Install the Load Balancing Plug-in (standalone)

Use the procedures in this section if the load balancing plug-in is not part of the Application Server distribution you are using. If you are using the Sun Java System Application Server 9.1 (bundle with HADB), see To Install Application Server 9.1 with HADB for instructions for installing the load balancing plug-in.

The load balancing plug-in is not currently bundled with the GlassFish v2Application Server. If you want load balancing capabilities, you can download the load balancing plug-in from the following locations:

• Solaris (SPARC): http://download.java.net/javaee5/external/SunOS/aslb/jars/

• Solaris (x86): http://download.java.net/javaee5/external/SunOS_X86/aslb/jars/

• Linux: http://download.java.net/javaee5/external/Linux/aslb/jars/

• Windows: http://download.java.net/javaee5/external/WINNT/aslb/jars/

• Mac OS: http://download.java.net/javaee5/external/Darwin/aslb/jars/

1. Before you install the load balancer plug-in, ensure that you have installed a supported web server. For a list of supported web servers, see Web Servers in Sun Java System Application Server 9.1 Release Notes.

2. Create the lbplugin directory within <glassfish_install_dir>/lib.

3. Unjar this file in the lbplugin directory. Run the following command: jar -xvf <lbplugin>.jar.

4. Unzip the following two files: SUNWaslb.zip and SUNWaspx.zip in the same directory. Delete the zip files.

5. Change permissions on all shared libraries within lbplugin directory. Run the following command: chmod -R 755 ${glassfish.home}/lib/lbplugin/lib.

6. Create a configuration for the load balancer. See Setting up Load Balancing in Sun Java System Application Server 9.1 Quick Start Guide.

7. Restart the Web Server after creating a configuration for the load balancer.

Next Steps

You need to configure Web Server for load balancing. For detailed instructions on manually configuring Web Server for load balancing, see Configuring Sun Java System Web Server in Sun Java System Application Server 9.1 High Availability Administration Guide.

Application Server 9.1 with Java ES 5 Update 1

If you are using the Sun Java System Application Server 9.1 distributed as an optional download with the Java Enterprise System 5 Update 1 (Java ES 5 Update 1) release, use the following procedure:

1. Install Sun Java System Application Server 9.1. For instructions on how to install Application Server 9.1, see Installing Application Server 9.1.

2. After the installation is complete, start the domain.

   On Solaris or Linux, Application Server 9.1 installer detects earlier versions of Application Server or other Java ES Components installed in native package format and automatically performs the upgrade of the binaries.

3. Start the Java ES 5 Update 1 installation.

The Java ES Update 1 installer could report that conflict were detected in Application Server components. Ignore these conflict messages and proceed with the installation.

Java ES 5 Update 1 installer validates the Application Server installation and then installs the selected Java ES components.

Application Server 9.1 is not supported with Java ES 5 and needs the Java ES 5 Update 1 Portal Server. Portal Server for Java ES 5 Update 1 is not supported on Windows.

If you run into problems with using the Portal Server database while using Application Server 9.1 with Java ES 5 Update 1 Portal Server, see the Portal Database Not Found After Java DB Restart in the Java ES 5 Update 1 Installation Guide.

To Perform a Cleanup after Partial Installation

This procedure describes how to perform a cleanup on your machine after a partial, failed installation of the package-based Application Server 9.1 distribution. You can use this procedure for preparing your machine for installing Application Server.

1. Remove the partly installed Application Server by running the following commands:

   On Solaris:

   cd /var/sadm/pkg

   ls -ltr

   pkgrm <Application Server packages>

   On Linux:

   rpm -qa|grep -i sun

   rpm -e <Application Server rpm>

2. If you have removed packages manually, you need to delete the correspondent entries from the productregistry file or delete the productregistry file.

   The location of productregistry file: /var/sadm/install directory on Solaris, /var/tmp/ directory on Linux.

3. Kill any running Application Server processes.

4. Remove the Application Server installation directory.

To Configure Registry Server with Application Server 9.1

Before You Begin

If you are using Application Server 9.1 with Java ES 5 Update 1, you need to install Registry Server manually from the Java ES 5 Update 1 distribution directory from <JavaES_ditribution_dir>/<OS>/Products/registry-svr/Packages directory.

The following procedure describes how to Configure Registry Server from Java ES 5 Update 1 to work with Application Server 9.1.

1. Run the following command:

   cd <registry_server_install_dir>/install

   On Solaris, <registry_server_install_dir> is /opt/SUNWsrvc-registry, by default. On Linux, the default install location is /opt/sun/srvc-registry.

2. Run the following command:

   <Ant-base_dir>/ant -f build-install.xml -Dinstall.properties=./install.properties install

   Where <Ant-base_dir> is /usr/sfw/bin on Solaris and /opt/sun/share/bin on Linux.

3. Run the following command:

   <Ant-base_dir>/ant -f build-install.xml appserver.deploy.as9

4. Run the following command:

   <Ant-base_dir>/ant -f build-install.xml appserver.domain.stop

5. Run the following command:

   <Ant-base_dir>/ant -f build-install.xml appserver.domain.start

Installing Application Server 9.1

If you are using the Sun Java System Application Server 9.1 file-based installation, use one of the following procedures:

• To Install Application Server 9.1 without HADB

• To Install Application Server 9.1 with HADB

• To Install Application Server 9.1 in Silent Mode

To Install Application Server 9.1 without HADB

Before You Begin

Use this procedure if you are using the Sun Java System Application Server file—based installer. Verify that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server 9.1 Release Notes.

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, you must have read-write access to the following directories:

• The installation directory you select

• The home directory of the installation user

• The /var/tmp directory

• The /tmp directory

• The web server installation directory and the web server instance directory, if applicable.

1. Navigate to the directory where you downloaded the distribution file.

2. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

3. Run the installation program.

   • If you are installing from a .bin file, use the following command to run the installation program :

     ./distribution_filename

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from a .zip file, unzip the file, navigate to the extracted folder, and run the following command:

     ./setup

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from an .exe file on Windows, double-click the file.

4. Specify the directory where you want to install the software or accept the default installation directory.

5. Choose to install JDK 5 or use a pre-installed JDK 5.

6. In the Administration Configuration page (or when prompted at the command line), enter the following:

   • Admin User Name – Name of the user who administers the server.

   • Password – Admin user’s password to access the Admin Server (8-character minimum).

   • Master Password — The master password (8-character minimum).

   • Admin Port – Administration port number for initial server instance. The default value is 4848.

   • HTTP Port - Port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • HTTPS Port - Secure port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • ---

     Note –

     The installation program automatically detects ports in use and suggests unused ports for the default settings.

     The default ports are:

     • Administration Server - The default is 4848

     • HTTP server - The default is 8080

     • HTTPS sever - The default is 8181

     In addition, five other ports are automatically assigned. You can change the automatically assigned values after installation using the Admin Console. The default ports assigned are:

     • Sun Java System Message Queue - The default is 7676

     • IIOP - The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL

     • JMX - The default is 8686

     If these default port numbers are in use, the installation program assigns random port numbers from the dynamic port range. This number may not be the next available port number.

     ---

7. In the Installation Options page, select the options that you want. Installation Options are:

   • Register Application Server: Select this option to register your installation of Application Server.

   • Upgrade from Previous Version: Select this option to upgrade from configuration data from an earlier installation of Application Server.

   • Enable Updatecenter Client: Select this option to enable Updatecenter to check for available updates and collect system data.

   ---

   Note –

   If you are running the installer in command-line mode, you need to run the asupgrade command manually.

   ---

8. On the Ready to Install page, click Install Now.

   ---

   Note –

   To create a Windows service, the sc.exe utility must be available on the system. Windows 2000 users may need to install the Windows 2000 Resource Kit to get this utility. For other supported Windows versions, the utility is included in the operating system.

   ---

9. After the installation completes, set the PATH environment variable to include the Application Server install-dir/bin directory.

10. Verify the installation by following the procedures in the Sun Java System Application Server 9.1 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.

    If you have problems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Release Notes.

See Also

The Application Server 9.1 bundle without HADB does not include the load balancing plug-in. You can download and install the load balancing plug-in separately. For instructions, see To Install the Load Balancing Plug-in (standalone).

To Install Application Server 9.1 with HADB

Before You Begin

Use this procedure if you are using the Sun Java System Application Server file—based installer. Verify that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server 9.1 Release Notes.

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, you must have read-write access to the following directories:

• The installation directory you select

• The home directory of the installation user

• The /var/tmp directory

• The /tmp directory

• The web server installation directory and the web server instance directory, if applicable.

1. Navigate to the directory where you downloaded the distribution file.

2. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

3. Run the installation program.

   • If you are installing from a .bin file, use the following command to run the installation program :

     ./distribution_filename

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from a .zip file, unzip the file, navigate to the extracted folder, and run the following command:

     ./setup

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from an .exe file on Windows, double-click the file.

4. Specify the directory where you want to install the software or accept the default installation directory.

5. Select the components to install. If you are using a Application Server bundle without HADB, you will not see this screen.

   The following components are available for installation:

   • Node Agent – All machines that contain application server instances should have a node agent installed.

   • High Availability Database Server -This component stores session information so requests can be failed over if you are using the load balancing plug-in.

   • Load Balancing Plug-in - Install the load balancing plug-in on the machine where a web server is installed. If you do not already have a web server installed on the machine where you are installing the load balancing plug-in, you cannot continue to install the load balancer plug-in. Supported web servers are Sun Java System Web Server 6.1 and above (including 7.0), Apache 2.0.x, and IIS 5.0 and above.

   • Domain Administration Server and Administration Tool - The Domain Administration Server (DAS) acts as a central repository for applications and configuration information for server instances, even if the instances are located on a remote machine. It includes graphical and command-line administration tools.

   • Command Line Administration Tool Only - Install the Command Line Administration tool on machines which do not contain a DAS, but from which you want to communicate with the DAS or a node agent. For example, install the command-line administration tool on machines from which you plan to remotely administer the Application Server using the command-line administration tools.

   • No Administration Tools - Use this option when installing components on a machine that already contains the administration tools, or on which no administration tools are required. For example, when installing the load balancing plug-in on a machine with a web server, but no Application Server, no Application Server administration tools are required.

   • Sample Applications - Samples come with the source, schema, Ant build scripts, and EAR files. Any existing data associated with the database-related samples is available in the included Java DB database.

   ---

   Note –

   Before you run incremental installation of Application Server 9.1 components, ensure that server processes are stopped if Domain Administration Server or Node Agent component is pre-installed on the machine

   ---

6. Choose to install JDK 5 or use a pre-installed JDK 5.

7. If you selected the load balancing plug-in component:

   1. Select the Web Server you have installed. Ensure that you have installed a supported web server. For a list of supported web servers, see Web Servers in Sun Java System Application Server 9.1 Release Notes.

   2. If you have Sun Java System Web Server, provide the install-dir and the instance-dir. If you have Apache web server or IIS, provide the install-dir.

   3. If you have created a DAS certificate for the Apache web server , automatically import the certificate by providing the Certificate file location.

      The Certificate file location is the location of the DAS certificate file. Ensure that you provide the path to certificate file inclusive of the name of the certificate file.

      Automatic import of DAS certificate is supported only for Apache web server. If you are using Apache web server, install Application Server without the load balancing plug-in. After installing Application Server, create and export a DAS certificate by using the certutil utility, and run the Application Server installer again to install the load balancing plug-in. For instructions on how to create and export DAS certificate for Apache web server, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide

      If you are using Sun Java System Web Server or IIS, you will need to manually import the DAS certificate. You need to install load balancer without a DAS certificate. After installing the load balancing plug-in, you can create a DAS certificate and manually import it. For instructions, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide.

8. If you are installing the load balancing plug-in on Web Server 7.0, the installer displays the Sun Java System Web Server 7.0 information page. Enter the following:

   • Web Server Administrator User - Name of the user who administers the web server.

   • Web Server Administrator Password - Password to access the Web Server administration server.

   • Web Server Host Name - Name of the web server host.

   • Web Server Administration Port - Port number to access the Web Server administration server. The default port is 8989.

   ---

   Note –

   • Ensure that you enter valid values for these fields related to Web Server 7.0 administration server. The installer does not validate these values.

   • After you install load balancing plug-in on Windows for Sun Java Systems Web Server 7.0, you need to reboot the machine, so that the installer updates the system PATH environment variable to add the path to the plug-in libraries.

   ---

   The Installation Summary page is displayed indicating the installation status.

9. In the Administration Configuration page (or when prompted at the command line), enter the following:

   • Admin User Name – Name of the user who administers the server.

   • Password – Admin user’s password to access the Admin Server (8-character minimum).

   • Master Password — The master password (8-character minimum).

   • Admin Port – Administration port number for initial server instance. The default value is 4848.

   • HTTP Port - Port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • HTTPS Port - Secure port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • Node agent name — A name for the node agent. You need to provide this value only if you had selected the Node Agent option.

   • ---

     Note –

     The installation program automatically detects ports in use and suggests unused ports for the default settings.

     The default ports are:

     • Administration Server - The default is 4848

     • HTTP server - The default is 8080

     • HTTPS sever - The default is 8181

     In addition, five other ports are automatically assigned. You can change the automatically assigned values after installation using the Admin Console. The default ports assigned are:

     • Sun Java System Message Queue - The default is 7676

     • IIOP - The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL

     • JMX - The default is 8686

     If these default port numbers are in use, the installation program assigns random port numbers from the dynamic port range. This number may not be the next available port number.

     ---

10. In the Installation Options page, select the options that you want. Installation Options are:

    • Register Application Server: Select this option to register your installation of Application Server.

    • Upgrade from Previous Version: Select this option to upgrade from configuration data from an earlier installation of Application Server.

    • Enable Updatecenter Client: Select this option to enable Updatecenter to check for available updates and collect system data.

    ---

    Note –

    If you are running the installer in command-line mode, you need to run the asupgrade command manually.

    ---

11. On the Ready to Install page, click Install Now.

    ---

    Note –

    To create a Windows service, the sc.exe utility must be available on the system. Windows 2000 users may need to install the Windows 2000 Resource Kit to get this utility. For other supported Windows versions, the utility is included in the operating system.

    ---

12. After the installation completes, set the PATH environment variable to include the Application Server install-dir/bin directory.

13. Verify the installation by following the procedures in the Sun Java System Application Server 9.1 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.

    If you have problems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Release Notes.

Next Steps

If you have installed load balancing plug-in, you need to configure Web Server for load balancing. For detailed instructions on configuring Web Server for load balancing, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide.

To Install Application Server 9.1 in Silent Mode

You can use this procedure only with the Sun Java System Application Server 9.1 installer. GlassFish v2 does not offer Silent Mode installation. Silent mode installation is non-interactive. You cannot use the Silent Mode if you are installing the load balancing plug-in on Web Server 7.0. You must first provide a configuration file for information that the installer needs. The following topics are discussed:

• Creating the Installation Configuration File

• Modifying the Installation Configuration File

• Using the Installation Configuration File to Install in Silent Mode

Creating the Installation Configuration File

The installation configuration file is created when you use the savestate option when starting an interactive installation. During the interactive installation, your input is collected and stored in the configuration file you specified. This file forms the template for silent installation, which you can use later to install the product on one or more machines. If needed, you can modify the installation configuration file.

On Solaris and Linux, for the graphical interface the syntax is:

./distribution_filename -savestate configuration_filename

On Solaris and Linux, for the command-line interface, the syntax is:

./distribution_filename -console -savestate configuration_filename

To create the installation configuration file on the Windows platform, start the installation program from the command line. Change to the directory where the executable file resides. For the graphical method the syntax is:

distribution_filename -savestate configuration_filename

On Windows, for the command-line method, the syntax is:

distribution_filename -console -savestate configuration_filename.

If you do not include a path to the installation configuration file, the file is created in the directory where you are running the installation program.

Example 1–1 Installation Configuration File Example

The following example shows an installation configuration file created by running the installation program with the savestate option.

#
# Wizard Statefile created: Mon Apr 30 11:42:36 IST 2007
#              Wizard path: /var/tmp/sjsasAAAvXaW4p/appserv.class
#

#
# Install Wizard Statefile section for Sun Java System Application Server
#
#
[STATE_BEGIN Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]
defaultInstallDirectory = /SUNWappserver
currentInstallDirectory = /space/programs/as9ee/temp
JDK_LOCATION = /space/programs/as9/jdk5/jdk
INST_ASADMIN_USERNAME = admin1
INST_ASADMIN_PASSWORD = ngghybgbednrreyatoqzvanqzva
INST_MASTER_PASSWORD = pgyrcyuakieqyuqlkurvunatrvg
INST_ASADMIN_PORT = 44517
INST_ASWEB_PORT = 44514
INST_HTTPS_PORT = 44520
STORE_ADMIN_AUTH = TRUE
ADMIN_PASSWORD_ENCRYPTED = TRUE
INST_JMS_PORT = 44532
INST_ORB_PORT = 44529
INST_ORB_SSL_PORT = 44535
INST_ORB_MUTUALAUTH_PORT = 44538
INST_JMX_PORT = 44541
CREATE_DESKTOP_SHORTCUT = FALSE
UPDATE_PATH = FALSE
CREATE_UPDATE_ICON = 
CREATE_WINDOWS_SERVICE = FALSE
CREATE_DAS = TRUE
[STATE_DONE Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]

Modifying the Installation Configuration File

You can modify the installation configuration file by editing the variables and values described in the following table. This table has four columns showing variable names, valid values (if applicable), contents, and comments.

Using the Installation Configuration File to Install in Silent Mode

After creating the configuration file, use it to install Application Server in silent mode as many times as needed. Use the following procedure:

To Install in Silent Mode

1. Review the installation configuration file and verify that it contains the values to use for your silent installation.

2. Copy your installation configuration file to each machine where you plan to install the software.

3. Copy the Application Server distribution file to each machine where you plan to install the software.

4. Navigate to the directory where you copied the distribution file and your installation configuration file.

5. Start silent installation at the command line using one of the following command formats:

   • On Solaris or Linux:

     ./distribution_filename -silent configuration_filename

   • On Windows:

     distribution_filename -silent configuration_filename

   The installation program reads the specified configuration_filename, checks for adequate disk space, then installs the product based on the data in configuration_filename.

   When the prompt is returned, the silent installation is complete and the installation components are installed on your systems.

6. Start the Application Server software by using the instructions in the Sun Java System Application Server 9.1 Administration Guide.

Application Server and Solaris 10 Zones

You can install Application Server on local or global zones.

Consider the following before you install Application Server on a Solaris zone:

• Application Server and MQ bundled with Solaris 10

• Propagation Levels of Components Installed Through Java ES 5 Update 1

Application Server and MQ bundled with Solaris 10

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.

Propagation Levels of Components Installed Through Java ES 5 Update 1

The propagation levels of components installed through Application Server 9.1 installation (with Java ES 5 Update 1) are:

• Bundled Application Server packages have propagation set to TRUE to all zones.

• Application Server packages that are part of Java ES Update 1 and Application Server 9.1 installation do not propagate to local zones.

• Message Queue and shared components that are part of Java ES Update 1 and Application Server 9.1 installation are set to propagate to all zones from the global zone.

• HADB packages are not set to propagate to local zones.