Install additional features on an existing Network Deployment installation

This topic describes how to install additional features on an existing IBM WAS Network Deployment, V6 installation.

 

Before you begin

This path is one of the installation paths that is available for any operating system. Two other installation paths exist:

Select the appropriate installation path before you begin the installation.

Before starting the installation, see Using the launchpad to start the installation for information about the Installation solutions diagrams. The diagrams show typical topologies for the product. The solutions are also in Planning to install Network Deployment .

 

Overview

Use the following procedure to add features to an existing WAS Network Deployment installation.

 

Procedure

  1. Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.

    In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command 

    umask
    To set the umask setting to 022, issue the following command 

    umask 022
    Some steps of the installation on a Windows platform require the administrator group user to have the following advanced user rights:

    • Act as part of the operating system

    • Log on as a service

    For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to see the advanced options. See your Windows documentation for more information.

    The installation wizard grants your Windows user ID the advanced user rights, if the user ID belongs to the administrator group. The silent installation does not grant these rights. If you create a new user ID on a Windows platform to perform a silent installation, restart the system to activate the proper authorizations for the user ID before you can perform a successful silent installation.

    When installing the WAS as a Windows service, do not use 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 problem, install with a user ID that does not contain spaces, or do not choose to install Windows services.

  2. Insert the product CD-ROM labeled WAS Network Deployment into the CD-ROM drive and mount the drive if necessary, as described in Mounting CD-ROMS on Linux and UNIX operating systems.

  3. Start the installation with the launchpad.sh command on Linux and UNIX platforms or the launchpad.bat command on Windows platforms.

    We can also start the installation using the install command:

    • /WAS/install

    • \WAS\install

    If you have a problem starting the launchpad, use the troubleshooting information in Using the launchpad to start the installation to correct the problem.

    When using the launchpad, launch the Installation wizard for Network Deployment.

    After launching the Installation wizard from the launchpad or from the command line, the InstallShield MultiPlatform (ISMP) wizard initializes and then displays the Welcome panel.

  4. Click Next to continue.

    The license agreement displays.

  5. Click the radio button beside the I accept the terms in the license agreement message to agree to the license agreement and click Next to continue.

    After you accept the licensing terms, the Installation wizard checks for a supported operating system and prerequisite patches.

    If you encounter a problem such as not having the right prerequisite updates on your system, cancel the installation, make the required changes, and restart the installation.

    Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware, software, and APIs 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 install to have a compliant operating system.

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

  6. 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 product level. This task describes the scenario where a previous installation exists and you are adding features with an incremental installation.

    When the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, or perform a new installation to another directory.

  7. Select the check box for installing additional features and click Next.

    Do not change the installation directory unless another existing installation is in the directory that you specify. An incremental installation adds features to the shared binaries identified in the field.

    We can add features to the core product files at any time by running the Installation wizard again. Installing additional features does not affect profiles that you might have already created.

    When adding features during an incremental installation, the wizard displays the Features selection panel next.

  8. Select features to install and click Next.

    Table 1. Features for the Network Deployment product
    Feature Description
    Core product files Installs the product binary code.
    Application Server Samples Installs the Sample applications.
    Javadoc Installs the API documentation of WAS classes.

    Performance considerations

    For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, one can improve application server startup time by 60 percent and save 15 percent of disk space. We can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).

    The Installation wizard displays a confirmation panel.

  9. Review the summary information and click Next to install the product code or Back to change your specifications.

    The disk space shown on the pre-installation summary panel includes space for the Java Virtual Machine (JVM). Subtract the size of the JVM for your operating system to determine the installed size on disk for the features that you selected.

    Table 1. JVM sizes
    AIX HP-UX Linux Solaris Windows
    59 MB pa-risc: 109 MB

    64 bit: 137 MB

    		ia32: 83 MB

    64 bit: 133 MB

    		81 MB ia32: 75 MB

    64 bit: 71 MB

    Verify that you have the total amount of free space shown before installing. Space is required for a working copy of the JVM during the installation.

    The Installation wizard creates the uninstaller program and then displays a progress panel that shows which components are being installed. At the end of the installation, the wizard displays the Installation completion panel.

    At the end of the installation, the wizard displays the Installation completion panel.

  10. Verify the success of the installer program by examining the completion panel and the install_root/logs/log.txt file for installation status.

    If problems occur, consult the following applicable logs:

    Log files for WebSphere Application Server products: The following table shows the installation logs, content, and indicators of success and failure for WAS products for V6.

    Table 1. Installation and profile creation logs for WAS products
    Log Content Indicators
    install_root/logs/log.txt Logs all installation events

    INSTCONFFAIL

    Total installation failure.

    INSTCONFSUCCESS

    Successful installation.

    INSTCONFPARTIALSUCCESS

    Installation errors occurred but the installation is still usable. Additional information identifies the errors.

    install_root/logs/wasprofile/wasprofile_create_profile.log

    INSTCONFFAIL

    Total profile creation failure.

    INSTCONFSUCCESS

    Successful profile creation.

    INSTCONFPARTIALSUCCESS

    Profile creation errors occurred but the profile is still functional. Additional information identifies the errors.

    install_root/logs/wasprofile/wasprofile_delete_profile.log

    INSTCONFFAIL

    Total profile deletion failure.

    INSTCONFSUCCESS

    Successful profile deletion.

    INSTCONFPARTIALSUCCESS

    Profile deletion errors occurred but the profile is still deleted. Additional information identifies the errors.

    install_root/profiles/profile/logs/pctLog.txt Logs all profile creation events that occur when using the Profile creation wizard

    INSTCONFFAIL

    Total profile creation failure.

    INSTCONFSUCCESS

    Successful profile creation.

    INSTCONFPARTIALSUCCESS

    Profile creation errors occurred but the profile is still functional. Additional information identifies the errors.

    If the installation of the core product files fails, fix the error and reinstall.

    If the creation of a profile fails, fix the error and run the Profile creation tool to recreate the profile.

    Troubleshoot the installation if the install_root/logs/log.txt file or the install_root/logs/wasprofile/wasprofile_create_default.log file does not contain a record of any problems, but problems exist.

    See Troubleshooting installation and Installation component troubleshooting tips for more information.

    Examine the Start menu entry. The menu is an indication of a successful installation:

    • Programs > IBM WebSphere > Application Server Network Deployment v6

    • All Programs > IBM WebSphere > Application Server Network Deployment v6

    If problems exist that cause you to reinstall the product, correct the errors, uninstall the product as described in Uninstalling the product, reboot a Windows machine or log off and back on as root on a Linux or UNIX machine, and reinstall.

  11. Select the check box to launch the Profile creation wizard and click Next to close the Installation wizard and launch the Profile creation wizard.

    See Using the Profile creation wizard for information about creating an operational environment that includes a deployment manager, a managed node, or a stand-alone application server.

    Network Deployment V6 includes the ability to create a deployment manager profile, an application server profile, or a custom profile. The second step of installation is to use the Profile creation wizard to create an operational environment that includes one of these profiles.

 

Result

The Installation wizard installs the new features in the existing installation root directory. The Installation wizard configures the WAS Network Deployment product for the new features.

However, create a profile that defines a deployment manager, a managed node, or a stand-alone application server to have an operational environment.

 

What to do next

Create a deployment manager profile!

Use the Profile creation wizard to create profiles in the default install_root/profiles directory or in a directory that you select.

See Using the Profile creation wizard.

Deploy an application to get started!

After creating an application server profile, one can deploy an application. See Fast paths for WebSphere Application Server to get started deploying applications.