Installing additional features on an existing base product

This topic describes how to install additional features to an existing IBM® WebSphere® Application Server installation.

Before you begin

This topic assumes that you have an existing product installation and that you want to install a feature using the installation wizard graphical user interface.

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.

Before starting this installation, see the following topics:

About this task

Perform the following installation to add features to an existing WebSphere Application Server installation.

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. Stop each running application server.

    Stop all server processes in all profiles associated with the target product instance. For example, issue the following command from the profile_root/bin directory to stop the server1 process in the application server profile:

    [AIX] [HP-UX] [Linux] [Solaris]
    ./stopServer.sh server1
    [Windows]
    ./stopServer server1

    If a server is running and security is enabled, use the following command:

    [AIX] [HP-UX] [Linux] [Solaris]
    ./stopServer.sh server1 -user user_ID -password password
    [Windows]
    ./stopServer server1 -user user_ID -password password
  3. Uninstall all maintenance packages.

    You are using the product installation image to install additional features. The features have not had any maintenance applied to them. If you remove all maintenance packages, your entire product will be at the same release level. You can then reapply the maintenance packages as described in a later step.

    Start the Update Installer program with the updi_root/update command to search for and uninstall all maintenance packages.

  4. Determine which disk or product image contains the feature you intend to install. Access the root directory of your installation image on your hard disk, or insert the disk into the disk drive.
    The application server product installer is spanned across multiple CDs. If you are installing the product from CD, you might be prompted during the installation for the next CD depending on which CD contains the feature you are installing.
    Best practice: To avoid being prompted for subsequent CDs, copy both installation CDs into the same directory on your hard disk, name them DISC1 and DISC2, and run the installer from the DISC1 directory. 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 use this naming convention 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.

  5. 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.

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

    Click Next to continue.

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

  8. 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.
  9. 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.
  10. If the wizard detects a previous installation, the product-detection panel is displayed.
    Perform one of the following actions:
  11. The optional features panel is displayed.
    There are several features available:
    • Install the sample applications

      Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.

    • Install non-English language packages for the administrative console

      Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.

    • Install non-English language packages for the application server runtime environment

      Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

    If you choose not to install a feature at this time, then you can run the installer later and add features to this installation. Select the features you want to install and click Next.

    Avoid trouble: You might want to defer installing features, such as language packs and samples, to save disk space. However, consider installing the features if there is a chance you might use them in the future. If you choose not to install the features and then later install maintenance, you will have to uninstall all maintenance, install the features, and then reapply all maintenance or the features might be corrupted.gotcha
  12. The installation summary panel is displayed.
    • [AIX] [HP-UX] [Linux] [Solaris] If you are installing as a non-root user, you can choose to verify whether you have the correct permissions to install the product successfully. Select the Verify my permissions to perform the installation check box if you wish to verify your permissions to install the product. If the permission check fails, then review your user permissions and retry the installation.
    • [Windows] The verify permissions function is currently not available on Windows operating systems.

    Review the summary information. Click Next to install the product code or Back to change your specifications.

    The installation wizard creates the uninstaller program and then displays a progress panel that shows which components are being installed.

  13. The Installation results panel is displayed. You can verify the success of the installer program by examining the completion panel and the app_server_root/logs/install/log.txt file for feature installation status. Although the samples feature has been installed, the samples have not yet been deployed into a specific application server. To deploy the samples choose one of the following options:
    • Deploy the samples to an existing application server. Run the install command found in app_server_root/samples/bin
    • Create a new profile using the Profile Management Tool, which provides an option to deploy the samples during profile creation. Select the checkbox if you want run the Profile Management Tool when the installation has completed.
  14. Click Finish to close the installation wizard.

Results

The Installation wizard installs the new features in the existing installation root directory. The Installation wizard configures the WebSphere Application Server product for the new features.

What to do next

Adding the samples feature does not automatically deploy the samples to existing profiles that did not have samples deployed to them initially. Use the samples install command mentioned in the installation summary panel, or create a new profile and deploy the samples. Use the Profile Management Tool or the manageprofiles command to create a profile. Make sure that you deploy the samples applications during profile creation.




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_featuresb
File name: tins_featuresb.html