Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX 

Chapter 11
Application Server

This chapter describes how to upgrade Application Server to Java ES 5 Update 1 (Release 5U1): Sun Java System Application Server Enterprise Edition 8.2 Patch 2. It covers both feature upgrades from previous Java ES release families and maintenance upgrades from Java ES 5. (For upgrades to Sun Java System Application Server 9.1, see the Sun Java System Application Server 9.1 Upgrade and Migration Guide, http://docs.sun.com/doc/819-3676.)

The chapter provides an overview of upgrade considerations for the different upgrade paths supported by Release 5U1. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Application Server Upgrades

This section describes the following general aspects of Application Server that impact upgrading to Java ES 5 Update 1 (Release 5U1):

About Release 5U1 Application Server

Release 5U1 Application Server is a maintenance release that fixes bugs in Release 5 Application Server. Release 5 Application Server was a maintenance release with respect to Release 4, including only selected bug fixes. Release 5U1 Application Server is functionally the same as Release 4.

Application Server Upgrade Roadmap

There are two sets of upgrade paths that apply to upgrade of Application Server to Release 5U1:

Application Server Data

The following table shows the type of data that could be impacted by an upgrade of Application Server software.

Table 11-4 Application Server Data Usage

Type of Data

Location

Usage

Environment variables

AppServer8-base/config/asenv.conf

Global variables

Configuration data

Release 3, Release 4, Release 5, & Release 5U1:
domain.xml and server.policy files in
AppServer8Config-base/domains/domainName/config

Release 2:
server.xml and server.policy files in
AppServer7Config-base/domains/domainName/
instanceName/config

Configuration of Application Server instances

Deployment data

Release 3, Release 4, Release 5, & Release 5U1:
AppServer8Config-base/domains/domainName/
applications

Release 2:
AppServer7Config-base/domains/domainName/
instanceName/applications

Configuration of J2EE container for specific J2EE components and applications

Access log files

Release 3, Release 4, Release 5, & Release 5U1:
AppServer8Config-base/domains/domainName/
logs/access/
Contains two files:
server_access_log and __asadmin_access_log

Release 2:
AppServer7Config-base/domains/domainName/
instanceName/logs/access

Access logging

Application Server Upgrade Strategy

Your strategy for upgrading Application Server generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.

This section is to particularize that general discussion to Application Server by presenting issues that might influence your Application Server upgrade plan.

Compatibility Issues

Release 5U1 Application Server does not introduce any interface changes with respect to Release 5, Release 4, or Release 3. However, there are major interface changes between Release 5U1 and Release 2, making Release 5U1 incompatible with Release 2.

Release 5U1 Application Server, however, does not support Release 4 Service Registry. If Application Server is upgraded to Release 5U1, the Service Registry must also be upgraded to Release 5U1.

Application Server Dependencies

Application Server dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Application Server software. Changes in Application Server interfaces or functions, for example, could require upgraded versions of components upon which Application Server depends. The need to upgrade such components depends upon the specific upgrade path.

Application Server has dependencies on the following Java ES components:

Dual Upgrade

Dual upgrades, in which both Application Server and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) can be performed in either of two ways:

Fresh Operating System Installation
  1. Back up existing Application Server data.

    2. See Application Server Data for the location of essential data.

  2. Install the new operating system.

    3. The operating system installation can only be on the same computer and will wipe out the existing file system.

  3. Restore the Application Server data that was backed up in Step 1.
  4. Install Release 5U1 Application Server.

    5. Use the procedure documented in the relevant upgrade section of this chapter, depending on the version of Application Server data that was backed up in Step 1.

In-place Operating System Upgrade
  1. Back up existing Application Server data.

    2. See Application Server Data for the location of essential data.

  2. Upgrade the operating system.

    3. The upgrade leaves the existing file system in place.

  3. Upgrade to Release 5U1 Application Server.

    4. See the relevant section of this chapter, depending on upgrade path.

Upgrading Application Server from Java ES 5

This section includes information about upgrading Application Server from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

When upgrading Release 5 Application Server to Release 5U1, consider the following aspects of the upgrade process:

Release 5 Application Server Upgrade

This section describes how to perform an upgrade of Application Server from Java ES Release 5 to Release 5U1 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Application Server software you should perform the following tasks:

Verify Current Version Information

You can verify the current version of Application Server by entering the following command:

Upgrade Application Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Release 5U1 Application Server has no hard upgrade dependencies, so upgrade of Application Server dependencies is optional.

Back Up Application Server Data

The Application Server upgrade to Release 5U1 does not modify Release 5 configuration data. There is no need to back up current data.

Obtain Required Configuration Information and Passwords

You should know the Application Server administrator user ID and password for your currently installed version.

Upgrading Release 5 Application Server (Solaris)

This section discusses considerations that impact the upgrade procedure for Application Server, followed by a description of the procedure itself.

Upgrade Considerations (Solaris)

The upgrade of Application Server software to Java ES Release 5U1 takes into account the following considerations:

Upgrade Procedure (Solaris)

The procedure documented below applies to Application Server instances residing locally on the computer where the upgrade is taking place.

  1. Log in as root or become superuser.

    2. su -

  2. Shut down all Application Server instances on the computer that is to be upgraded.
    1. Stop all running node agents.

      2. AppServer8-base/bin/asadmin stop-node-agent --user admin_ID
           nodeagentName

      where nodeagentName has the form hostName_domainName, but is simply hostName by default.

    2. Stop the Domain Administration Server (DAS).

      3. AppServer8-base/bin/asadmin stop-domain --user admin_ID
           domainName

    3. Stop the PointBase database server (if being used).

      4. AppServer8Config-base/appserver/pointbase/tools/stopserver.sh

  3. Make sure you have upgraded any Java ES components upon which Application Server has hard upgrade dependencies (see Upgrade Application Server Dependencies).
  4. Obtain the latest Application Server upgrade patches, based on Table 11-6.

    5. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  5. Apply the appropriate Application Server core and, if needed, localization patches in Table 11-6, in that order.

    6. patchadd /workingDirectory/patch_ID

    Be sure to consult the README.patch_ID file for additional patch installation instructions.

  6. Confirm that the patch upgrades were successful:

    7. showrev -p | grep patch_ID

    The output should return the versions of patch IDs applied in Step 5.

  7. Restart the Domain Administration Server (DAS).

    8. AppServer8-base/bin/asadmin start-domain --user admin_ID
         domainName

  8. Restart the Application Server instances.

    9. AppServer8-base/bin/asadmin start-node-agent --user admin_ID
         nodeagentName

    where nodeagentName has the form hostName_domainName, but is simply hostName by default.

Upgrading Release 5 Application Server (Linux)

This section discusses considerations that impact the upgrade procedure for Application Server, followed by a description of the procedure itself.

Upgrade Considerations (Linux)

The upgrade of Application Server software to Java ES Release 5U1 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 5U1 upgrade patches differ from the Solaris patches.

The Release 5U1 Application Server upgrade patches for Linux OS are shown in the following table:

Table 11-7 Patches1 to Upgrade Application Server on Linux 

Description

Patch ID and RPM names

Application Server core

124674-03

  • sun-asac-8.2.0-30.i386.rpm
  • sun-asacee-8.2.0-30.i386.rpm
  • sun-ascml-8.2.0-30.i386.rpm
  • sun-ascmn-8.2.0-30.i386.rpm
  • sun-ascmnse-8.2.0-30.i386.rpm
  • sun-asdem-8.2.0-30.i386.rpm
  • sun-ashdm-8.2.0-30.i386.rpm
  • sun-asJdbcDrivers-8.2.0-30.i386.rpm
  • sun-asjdoc-8.2.0-30.i386.rpm
  • sun-aslb-8.2.0-30.i386.rpm
  • sun-asman-8.2.0-30.i386.rpm
  • sun-asmanee-8.2.0-30.i386.rpm
  • sun-asu-8.2.0-30.i386.rpm
  • sun-asuee-8.2.0-30.i386.rpm
  • sun-asut-8.2.0-30.i386.rpm
  • sun-aswbcr-8.2.0-30.i386.rpm

Application Server localization

126285-03

  • sun-asacee-Locale-8.2.0-13.i386.rpm
  • sun-ascmnse-Locale-8.2.0-13.i386.rpm
  • sun-asu-Locale-8.2.0-13.i386.rpm
  • sun-asuee-Locale-8.2.0-13.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Release 5U1. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Linux)

The procedure documented below applies to Application Server instances residing locally on the computer where the upgrade is taking place.

Caution

An upgrade from Release 5 to Release 5U1 on Linux cannot easily be rolled back.

  1. Log in as root or become superuser.

    2. su -

  2. Shut down all Application Server instances on the computer that is to be upgraded.
    1. Stop all running node agents.

      2. AppServer8-base/bin/asadmin stop-node-agent --user admin_ID
           nodeagentName

      where nodeagentName has the form hostName_domainName, but is simply hostName by default.

    2. Stop the Domain Administration Server (DAS).

      3. AppServer8-base/bin/asadmin stop-domain --user admin_ID
           domainName

    3. Stop the PointBase database server (if being used).

      4. AppServer8Config-base/appserver/pointbase/tools/stopserver.sh

  3. Make sure you have upgraded any Java ES components upon which Application Server has hard upgrade dependencies (see Upgrade Application Server Dependencies).
  4. Obtain the latest Application Server upgrade patches, based on Table 11-7.

    5. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  5. Apply the core and, if needed, localization patch for Application Server in Table 11-7, in that order.
    1. Get the list of currently installed Application Server RPMs.

      2. rpm -qa | grep sun-as

    2. For each installed RPM, retrieve its install prefix.

      3. rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

      where rpmName is the RPM name listed in Step a.

    3. Install each RPM listed in Table 11-7.

      4. rpm -Uvh --prefix prefixValue rpmFileName

      where rpmFileName is the full file name (including the .rpm extension) of the RPM listed in Table 11-7 and prefixValue is its corresponding prefix as determined in Step b. Multiple RPM file names can be entered if they have the same prefixValue.

  6. Confirm that the patch upgrades were successful.

    7. rpm -qa | grep sun-as

    The new version numbers of the RPMs should be returned.

  7. Restart the Domain Administration Server (DAS).

    8. AppServer8-base/bin/asadmin start-domain --user admin_ID
         domainName

  8. Restart the Application Server instances.

    9. AppServer8-base/bin/asadmin start-node-agent --user admin_ID
         nodeagentName

    where nodeagentName has the form hostName_domainName, but is simply hostName by default.

Verifying the Upgrade

You can verify successful upgrade using the following command:

AppServer8-base/bin/asadmin version --verbose

See Table 11-5 for output values.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Considerations (Linux).

Rolling Back the Upgrade (Solaris)

This section describes the Release 5U1 upgrade rollback procedure for Application Server on the Solaris platform.

  1. Log in as root or become superuser.

    2. su -

  2. Stop all running instances of Application Server.
    1. Stop all running node agents.

      2. AppServer8-base/bin/asadmin stop-node-agent --user admin_ID
           nodeagentName

      where nodeagentName has the form hostName_domainName, but is simply hostName by default.

    2. Stop the Domain Administration Server (DAS).

      3. AppServer8-base/bin/asadmin stop-domain --user admin_ID
           domainName

    3. Stop the PointBase database server (if being used).

      4. AppServer8Config-base/appserver/pointbase/tools/stopserver.sh

  3. Remove the patches in Table 11-6.

    4. patchrm patch_ID

  4. Restart the Domain Administration Server (DAS).

    5. AppServer8-base/bin/asadmin start-domain --user admin_ID
         domainName

  5. Restart the Application Server instances that were stopped in Step 2.

    6. AppServer8-base/bin/asadmin start-node-agent --user admin_ID
         nodeagentName

    where nodeagentName has the form hostName_domainName, but is simply hostName by default.

Rolling Back the Upgrade (Linux)

This section describes the Release 5U1 upgrade rollback procedure for Application Server on the Linux platform. There is no automated rollback procedure for Linux patches, so the recommended approach is to manually overwrite the Release 5U1 RPMs with the Release 5 RPMs, as described below.

  1. Log in as root or become superuser.

    2. su -

  2. Stop all running instances of Application Server.
    1. Stop all running node agents.

      2. AppServer8-base/bin/asadmin stop-node-agent --user admin_ID
           nodeagentName

      where nodeagentName has the form hostName_domainName, but is simply hostName by default.

    2. Stop the Domain Administration Server (DAS).

      3. AppServer8-base/bin/asadmin stop-domain --user admin_ID
           domainName

    3. Stop the PointBase database server (if being used).

      4. AppServer8Config-base/appserver/pointbase/tools/stopserver.sh

  3. Check the revision numbers of Application Server RPMs.

    4. rpm -qa | grep sun-as

    The updated RPMs should be those listed in Table 11-7.

  4. Check to see if the RPMs have been relocated from their default location.

    5. rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

    where rpmName is the unique name of the RPM (for example, the values sun-as* shown in Table 11-7). The command returns a prefixValue as a path to the installed RPM.

  5. Reinstall Release 5 RPMs from the Java ES 5 distribution.

    6. (If you are rolling back to a post-Release 5 sustaining patch, rather than to Release 5, reinstall the RPMs from that patch.)

    rpm -Uvh --force [--prefix prefixValue] *.rpm

    The --force option will allow the command to overwrite later packages of the same name. The --prefix option is not required unless the RPMs have been relocated. (If only a subset of the RPMs had been relocated, use individual file names as command arguments rather than *.rpm.)

  6. Restart the Domain Administration Server (DAS).

    7. AppServer8-base/bin/asadmin start-domain --user admin_ID
         domainName

  7. Restart the Application Server instances that were stopped in Step 2.

    8. AppServer8-base/bin/asadmin start-node-agent --user admin_ID
         nodeagentName

    where nodeagentName has the form hostName_domainName, but is simply hostName by default.

Upgrading Application Server from Java ES Release 4

This section includes information about upgrading Application Server from Java ES 2005Q4 (Release 4) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

When upgrading Java ES Release 4 Application Server to Release 5U1, consider the following aspects of the upgrade process:

Release 4 Application Server Upgrade

This section describes how to perform an upgrade of Application Server from Java ES Release 4 to Release 5U1 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Application Server software you should perform the following tasks:

Verify Current Version Information

You can verify the current version of Application Server by entering the following command:

AppServer8-base/bin/asadmin version --verbose

See Table 11-5 for output values.

Upgrade Application Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Application Server has hard upgrade dependencies on the NSS shared component and on Message Queue, HADB, and Java DB product components.

When upgrading Application Server dependencies, you should do so in the order below (skipping any that might already have been upgraded), before you upgrade Application Server. However, upgrade of shared components as well as Message Queue, HADB, and Java DB is normally achieved automatically by the Java ES installer when upgrading Application Server.

  1. Shared Components.  Instructions for synchronizing Java ES shared components to Release 5U1 are provided in Upgrading Java ES Shared Components. However, all shared components required by Application Server are upgraded automatically by the Java ES installer when you perform an upgrade of Application Server to Release 5U1.
  2. Message Queue.  Instructions for upgrading Message Queue to Release 5U1 are provided in Chapter 10, "Message Queue".
  3. High Availability Session Store (HADB).  Instructions for upgrading HADB are provided in Chapter 9, "High Availability Session Store".
  4. Java DB.  Instructions for upgrading Java DB are provided in Chapter 8, "Java DB".
  5. Web Container Software (soft upgrade dependency).  Instructions for upgrading Web Server are provided in Chapter 7, "Web Server".
Back Up Application Server Data

The Application Server upgrade from Release 4 to Release 5U1 does not modify configuration data. There is therefore no need to back up current data.

Obtain Required Configuration Information and Passwords

You should know the Application Server administrator user ID and password for your currently installed version.

Upgrading Release 4 Application Server

This section discusses considerations that impact the upgrade procedure for Application Server followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Application Server software to Release 5U1 takes into account the following considerations:

Upgrade Procedure

The procedure documented below applies to Application Server instances residing locally on the computer where the upgrade is taking place.

  1. Log in as root or become superuser.

    2. su -

  2. Shut down all J2EE components running in the Application Server instances that are to be upgraded.
  3. Shut down all Application Server instances on the computer that is to be upgraded.
    1. Stop all running node agents.

      2. AppServer8-base/bin/asadmin stop-node-agent --user admin_ID
           nodeagentName

      where nodeagentName has the form hostName_domainName, but is simply hostName by default.

    2. Stop the Domain Administration Server (DAS).

      3. AppServer8-base/bin/asadmin stop-domain --user admin_ID
           domainName

    3. Stop the PointBase database server (if being used).

      4. AppServer8Config-base/appserver/pointbase/tools/stopserver.sh

  4. Launch the Java ES installer.

    5. cd Java ES Release 5U1 distribution/os_arch
    ./installer

    where os_arch matches your platform, such as Solaris_sparc. (Use the installer -nodisplay option for the command line interface.)

    After the Welcome and License Agreement pages are displayed, you will be presented with a component selection page. (When installed components are detected that can be directly upgraded by the Java ES installer, they are shown with a status of "upgradable.")

  5. Select Application Server in the component selection page.

    6. As hard upgrade dependencies, Message Queue, HADB, and Java DB will also be automatically selected for upgrade.

  6. Choose to Configure Now.
  7. Specify the configuration values requested.

    8. You will be presented with a number of configuration panels.

  8. Confirm your upgrade choice.

    9. Application Server packages (and, if necessary, those for Message Queue, HADB, and Java DB) will be upgraded and an upgrade summary displayed.

  9. Exit the Java ES installer.
  10. Apply the latest Application Server maintenance patches, if any.
    1. Check if there have been any Application Server point fixes subsequent to Release 5U1.

      2. Periodically obtain the latest patches as described in Accessing Java ES Patches and compare them to the Release 5U1 patch revision numbers shown in Table 11-6 (Solaris) or Table 11-7 (Linux).

      If you are using Sun Connection on the Solaris platform, you are automatically notified of new patches for Java ES components installed on your computer.

    2. Apply the appropriate Application Server core and, if needed, localization patches in that order.

      3. On Solaris:
      patchadd /workingDirectory/patch_ID

      If you are using the accumulated patch cluster on the Solaris platform, the install_cluster script will apply any Java ES patches needed on your computer.

      On Linux:
      See the instructions for applying Linux patches in Upgrading Release 5 Application Server (Linux).

      Be sure to consult the README.patch_ID file for additional patch installation instructions.

    3. Confirm that the patch upgrades were successful:

      4. On Solaris:
      showrev -p | grep patch_ID

      On Linux:
      rpm -qa | grep sun-as

      The output should return the appropriate patch IDs or version numbers.

  11. Restart the Domain Administration Server (DAS).

    12. AppServer8-base/bin/asadmin start-domain --user admin_ID
         domainName

  12. Restart the Application Server instances.

    13. AppServer8-base/bin/asadmin start-node-agent --user admin_ID
         nodeagentName

    where nodeagentName has the form hostName_domainName, but is simply hostName by default.

Verifying the Upgrade

You can verify successful upgrade using the following command:

AppServer8-base/bin/asadmin version --verbose

See Table 11-5 for output values.

Post-Upgrade Tasks

If you want to continue using the embedded Release 4 PointBase database instead of Java DB, a new Java ES product component, introduced in Release 5, you have to manually edit the upgraded AppServer8-base/config/asenv.conf file.

After upgrading Application Server from Release 4, the PointBase settings in asenv.conf are as follows:

Change these settings to the following values:

AS_POINTBASE="AppServer8-base/pointbase"
AS_POINTBASE_SAMPLESDB="AppServerConfig8-base/var/appserver/pointbase"

Rolling Back the Upgrade

Rollback of the Release 5U1 upgrade is not supported.

Upgrading Application Server from Java ES Release 3

The procedure for upgrading Java ES 2005Q1 (Release 3) Application Server to Release 5U1 is the same as that for upgrading Release 4 Application Server to Release 5U1.

To upgrade Release 3 Application Server to Release 5U1, use the instructions in Upgrading Application Server from Java ES Release 4, except substitute Release 3 wherever Release 4 is referenced.

Upgrading Application Server from Java ES Release 2

Direct upgrade of Java ES 2004Q2 (Release 2) Application Server to Release 5U1 Application Server is not supported.

However you can perform this upgrade by first upgrading Release 2 Application Server to Release 5 (as documented in the Java Enterprise System 5 Update 1 Upgrade Guide for UNIX, http://docs.sun.com/doc/819-6553) and then upgrading Release 5 Application Server to Release 5U1 (as documented in Upgrading Application Server from Java ES 5).

Upgrading the Solaris-bundled Application Server in a Solaris 10 Multi-zone Environment

Application Server (as well as Message Queue, upon which Application Server depends), is bundled with the Solaris 10 OS. Unless removed from the global zone, the bundled Application Server is propagated to non-global zones when such zones are created. The existence of the bundled Application Server in all zones impacts the subsequent upgrade of Application Server to Release 5:

The following example is provided to document some of the subtleties involved in upgrading Application Server in a Solaris 10 multi-zone environment. (For a more comprehensive discussion regarding Java ES and Solaris 10 zones, see Java ES 5 Update 1 Upgrade and Solaris 10 Zones.)

The objective in the example is to upgrade to Release 5 the Solaris-bundled Application Server (version 8.0.0_01) in a Solaris 10 sparse root zone.

You cannot simply upgrade Application Server in a sparse root zone because the Solaris-bundled Application Server is installed in a read-only directory mounted from the global zone. Hence, to upgrade Application Server to Release 5 in the sparse root zone, you must first remove the bundled version in the global zone.

In addition, Message Queue is installed in the global zone, representing a departure from the practice by which only shared components (not product components) are to be installed in the global zone. This is because Message Queue cannot be installed or upgraded in a sparse root zone because of the read-only directories.

The procedure for upgrading the Solaris-bundled Application Server (version 8.0.0_01) in a Solaris 10 sparse root zone to Release 5 is as follows:

  1. Verify the initial state of your system.

    2. This example assumes a version of Solaris 10 with a sparse root zone that has been configured, installed, and booted by the global administrator.

    The sparse root zone includes all Java ES components that are already installed in the global zone, namely the versions of Message Queue and Application Server bundled with Solaris 10.

    In addition, the example assumes that the user has previously used the bundled Application Server in the sparse root zone, having created administrative domain information that needs to be preserved.

  2. Upgrade the bundled version of Application Server in the global zone.

    3. This operation removes the bundled Application Server packages and replaces them with Release 5 packages. The removal of the bundled packages is propagated to the sparse root zone, effectively uninstalling Application Server packages in the sparse root zone, but the Release 5 packages are not propagated to non-global zones.

    1. Run the Java ES installer in the global zone.
    2. Select Application Server in the component selection page.

      3. Message Queue, HADB, and Java DB will automatically be selected, and Application Server and Message Queue will be marked as upgradable.

    3. Complete the upgrade.

      4. While Release 5 Message Queue will propagate to the sparse root zone, neither Application Server, HADB, nor Java DB will be propagated. In addition all shared components will be synchronized to Release 5 and propagated to the sparse root zone.

  3. 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 page.

      3. De-select Message Queue if it is automatically selected, and select HADB and Java DB if they are not automatically selected.

    3. Complete the installation of Application Server.

      4. Choose to Configure Later so that domain information is not overwritten by the installation process.

      In the case where no domains had been created, you can choose to Configure Now.c



Previous      Contents      Index      Next     

Part No: 820-2510-10
November 2007.   Copyright 2004 Sun Microsystems, Inc. All rights reserved.