[AIX HP-UX Linux Solaris Windows]

Upgrading Express to the WebSphere Application Server product using a CIP

This topic describes one of the installation options for a customized installation package (CIP) that includes the IBM® WebSphere® Application Server product and one or more maintenance packages. This topic describes how to use the Installation wizard to upgrade the Express product to the base 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, read the "Planning the installation" topic in the WebSphere Application Server, Version 7.0 Information Center. The planning diagrams show typical topologies for the product. The solutions are also available through the Installation solution diagrams link in the launchpad. Also read the "Using the launchpad to start the installation" topic.

About this task

Perform the following installation to upgrade an Express installation to the base 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.
    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
    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.

    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 package on your hard disk, or insert the disc containing the installation package into the disc drive.
    If you are installing the product from CD and the CIP installer is spanned across multiple CDs, you will be prompted during the installation for the next CD.
    Best practice Best practice: To avoid being prompted for subsequent CDs, copy all installation CDs into the same directory on your hard disk, name them DISC1. DISC2, and so on for each disc, 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.bprac

    Mount the drive if necessary.

  3. Start the installation directly with the install command.
    1. Change to the WAS directory.
    2. Run the install command.
      • ./install
      • install

    After launching the CIP installation wizard from the command line, the wizard initializes and then displays the Welcome panel. Click About this custom installation package to display detailed information about the current custom installation package, such as the edition and version.

  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. Read the "Non-root installation" topic in the WebSphere Application Server, Version 7.0 Information Center for more information. Click Next.
  8. 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 installation at the same major product level.

    If the wizard detects a previous installation, it displays the Existing installation panel, where you can:
    • Add maintenance to the existing installation
    • Add features to the existing installation
    • Add files, directories, enterprise application archive (EAR) files, and configuration archive (CAR) files to the existing installation
    • Use scripts to configure the existing system
    • Perform a new installation to another directory
    • Perform an upgrade of a trial installation to the full product

    This task describes the scenario where a previous installation of the Express product exists and you are installing the WebSphere Application Server CIP to upgrade the Base product. The CIP includes the Express product and one or more maintenance packages.

    After upgrading, install the CIP again to install the maintenance to the upgraded product.

    Select the Upgrade option and click Next. The installer program installs the new license files and updates the system properties to indicate that the WebSphere Application Server product is installed.

  9. The installation summary panel is displayed.
    • 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. Read the "Non-root installation" topic in the WebSphere Application Server, Version 7.0 Information Center for more information.
    • 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.

  10. 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.
  11. Click Finish to close the installation wizard.

Results

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

What to do next

You can install the CIP again to add features or install maintenance. Or you can use the Profile Management Tool to create more standalone application servers.

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 tasks

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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 11:41:45 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=ifactory&topic=tins_upgradeeb_cip
File name: tins_upgradeeb_cip.html