Upgrading from Express to the WebSphere Application Server product

This topic describes how to upgrade an Express product to the base WebSphere® Application Server product.

Before you begin

This topic describes one of the available installation procedures.

If this topic does not describe the procedure that you meant to select, click the link to the description of the appropriate installation procedure before you issue the install command.

Knowing which components to install and in what order to install them is important. Before starting this installation, see Planning the WebSphere Application Server product installation. The planning diagrams show typical topologies for the product. The solutions are also available through the Installation solution diagrams link in the launchpad. See Using the launchpad to start installations. You cannot run the launchpad remotely to install a product. Only local use of the launchpad is supported.

About this task

Perform the following installation to upgrade an Express installation to the WebSphere Application Server product.

Procedure

  1. Log on to the operating system. If you are installing as a non-root or non-administrative user, then there are certain limitations.
    [AIX] [HP-UX] [Linux] [Solaris] In addition, select a umask that allows the owner to read/write to the files, and allows others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users, a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command:
    umask
    To set the umask setting to 022, issue the following command:
    umask 022
    [Windows] When installing as an administrative user on a Windows® operating system, a Windows service is automatically created to autostart the application server. The installer user account must have the following advanced user rights:
    • Act as part of the operating system
    • Log on as a service
    For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See your Windows operating system documentation for more information.

    [Windows] If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this restriction, install with a user ID that does not contain spaces.

  2. Access the root directory of your installation image on your hard disk, or insert the disk labeled WebSphere Application Server into the disk drive.
    The application server product installer is spanned across multiple CDs. If you are installing the product from CD, you will be prompted during the installation for the next CD.
    Best practice: Use the following procedure to avoid being prompted for subsequent CDs:
    1. Copy both installation CDs into the same parent directory (for example, WebSphere7) on your hard disk
    2. Name the directories DISC1 and DISC2 (for example, WebSphere7/DISC1 and WebSphere7/DISC2)
    3. If your system's language is not set to English, set the language to English for the duration of the installation.
      Note: If your language is set to something other than English, the installer will still prompt you to enter the second CD.
    4. Run the installer from the DISC1 directory after following the remaining instructions in this document.
    5. After you have completed the installation, reset your system's language to its previous setting if you had changed it during the installation.
    You will not be prompted for the next CD during installation if you have followed this naming convention. If you are installing silently, then you must follow this procedure or the installation will not proceed. If you are installing from a DVD or a downloaded image, then you do not need to take any action because these images are not spanned.bprac
    [AIX] [HP-UX] [Linux] [Solaris] Mount the drive if necessary as described in Mounting disk drives on operating systems such as AIX and Linux.
    [Linux] Avoid trouble: If you attempt to install the application Server from a CD or DVD that has been burned from an ISO image on Red Hat Linux®, the launchpad and installer applications might fail to run. When Red Hat Linux automatically mounts a CD or DVD, you cannot run the disk. The installation scripts and the launchpad script are unable to run properly. To resolve this issue, unmount the disk and then remount it with the relevant read and execute levels.gotcha
  3. Start the installation.
    Start the installation of a product image with the launchpad script.
    • [AIX] [HP-UX] [Linux] [Solaris] launchpad.sh
    • [Windows] launchpad.bat or launchpad.exe

    Or you can start the installation directly with the install command.

    • [AIX] [HP-UX] [Linux] [Solaris] /WAS/install
    • [Windows] \WAS\install
    [Windows] Avoid trouble: There might be certain operating system policy restrictions if you are installing as a non-administrator on Windows 2003 on an AMD processor. You might not be able to run the install command by double-clicking the file in Windows Explorer. Run the command from a command prompt or rename the command to something other than install.exe or setup.exe and run the command.gotcha
    If an error occurs with the Java™ SE Runtime Environment 6 (JRE 6), force the installation to use the correct runtime environment with the following command, where downloaded_directory is the name of the directory in which you downloaded the image:
    • [AIX] [HP-UX] [Linux] [Solaris] ./install -is:javahome disk_mount_point/downloaded_directory/JDK/jre.pak/repository/package.java.jre/java/jre
    • [Windows] install -is:javahome disk_drive:\downloaded_directory\JDK\jre.pak\repository\package.java.jre\java\jre

    If you cannot start the launchpad, use the troubleshooting information in Using the launchpad to start installations to correct the problem.

    When using the launchpad, launch the installation wizard for WebSphere Application Server.

  4. The installation wizard initializes and then displays the Welcome panel.

    Click Next to continue.

  5. The license agreement panel is displayed. Read the license agreement and accept its terms. After you accept the licensing terms, the installation wizard checks for a supported operating system and prerequisite patches.

    Although the installation wizard automatically checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the WebSphere Application Server detailed system requirements Web site if you have not already done so. The Web site lists all supported operating systems and the operating system fixes and patches that you must install to have a compliant operating system.

    The installation process verifies that the minimum required version of a supported operating system is available. If you meet the minimum release requirements or are at a higher minor release of a supported operating system, then you will not encounter a prerequisite error. If you are not at the minimum version of a supported operating system, you can continue with the installation, but the installation or product operation might not succeed without applying maintenance. If you are at a higher major release of a supported operating system, or the operating system itself is not on the supported list, you might encounter the following warning:
    Warning: A supported operating system was not detected.
    
    Support for your operating system might have been added after the release of the product.
    See the WebSphere Application Server detailed system requirements Web pages for more information
    about supported operating systems. You can continue with the installation, but the installation
    or product operation might not succeed without applying maintenance. Go to the product support Web pages 
    to obtain the latest maintenance packages to apply after installation.

    Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.

    Click the radio button beside the message I accept both the IBM and the non-IBM terms to agree to the license agreement and click Next to continue.

  6. The systems prerequisite check panel is displayed. After confirming that your operating system is supported and that you have installed all necessary patches, click Next to continue. The Installation wizard checks for a previous application server installation at the same product level.
  7. If you are installing the product as a non-root user (or a non Administrator on Windows operating systems), then a panel is displayed indicating that a non-root user has been detected. This panel contains important information about installing as a non-root user. See Non-root installations for more information. Click Next.
  8. If the wizard detects a previous installation, then the product detection panel is displayed.
    You have the following options:
    • Add features to the existing installation
    • Install a new copy of the product to another directory
    • Create a new WebSphere Application Server profile using the Profile management tool
    • Upgrade the product to another edition

    [aug2010] This procedure assumes that you want to upgrade the product. [aug2010]

    aug2010
    Otherwise, if you want to add features to an existing installation, see the Installing additional features on an existing base product topic.

    [aug2010] Select the Upgrade the product to another edition option to migrate from a trial version of the product to a full version and click Next. [aug2010]

    aug2010
    The installer program installs the new license files and updates the system properties to indicate that the actual product is installed.

    Click Next to continue.

Results

This procedure results in upgrading an Express product to the base WebSphere Application Server product.

What to do next

You can install the base product again to add features.

Further configuration is not necessary at this time. However, you can create additional standalone application servers with the Profile Management Tool. Each profile is created in the profile_root directory by default.

See the documentation on profiles for more information.

If you have already created the topology that you require, try deploying an application in your environment.

Deploy an application to get started!

See Fast paths for WebSphere Application Server to get started deploying applications.




In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 12:05:26 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-dist&topic=tins_upgradeeb
File name: tins_upgradeeb.html