Installing CIP features on an existing base product

This topic describes one of several options for installing a customized installation package (CIP) that includes the IBM WebSphere Application Server, Version 6 product and one or more maintenance packages. This topic describes how to use the CIP Installation wizard to install features that are included in the CIP. The Installation wizard also installs maintenance packages that are included in the CIP.

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 what component to install and in what order to install the component is an important consideration. At some time before starting this installation, see Planning to install WebSphere Application Server.

About this task

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

This installation also installs maintenance packages that are included in the CIP.

Procedure

  1. Log on to the operating system.
    [AIX] [HP-UX] [Linux] [Solaris] In addition, select a umask that would allow the owner to read/write to the files, and allow 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 on a Windows® system, a Windows service is automatically created to autostart the application server if your installer user account has 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 set the advanced options. See your Windows 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 problem, install with a user ID that does not contain spaces.

  2. Insert the CD-ROM or DVD with the customized installation package (CIP). Or access the directory where the CIP is located. If necessary, mount the disc drive as described in Mounting disc drives on operating systems such as AIX or Linux.
  3. Start the installation directly with the install command.
    1. Change to the WAS directory.
    2. Run the install command.
      • ./install
      • [Windows] 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. Click Next to continue.

    The license agreement displays.

  5. Read the license agreement and accept its terms.

    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.

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

    Although the installation process verifies that the minimum required version of the operating system is available, the installation process might not correctly flag a maintenance upgrade of that operating system version as being a supported configuration. If you have upgraded your supported operating system version to a higher maintenance level and you receive the following error message, then you can ignore the message and click Next.
    Avoid trouble Avoid trouble: Although maintenance upgrades of the same major release are supported, subsequent major releases of the operating system might not be supported.gotcha
    Failed : Your operating system failed the
    prerequisites check.
    
    A supported operating system was not detected. Support for your
    operating system might have been added after the release of the
    product.

    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.

    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 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
    • Perform an upgrade of an Express® installation to the full product

    This task describes the scenario where a previous installation exists and you are adding features with an incremental installation.

  7. Select the option to install additional features, then click Next to continue to the Features selection panel.

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

    You can add available CIP features to the binaries at any time, by running the CIP Installation wizard again. Installing additional features does not affect profiles that you might have already created. (Profiles are run-time environments that are described in a later step.)

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

  8. Select features to install and click Next.

    In Version 6.1, just one feature is available, which installs the Samples Gallery.

    A CIP might not have the Samples feature. You can install only what was included in the CIP.

    Note: If an existing installation is at a lower level than the CIP or at the same level as the CIP, the core product will be updated to the CIP level automatically. If an existing installation is at a higher level than the CIP, the core product will not be down leveled. The feature panel only shows the features you are missing, if you select to install the new feature from CIP, the installed features will be at the same level of CIP, which is lower than existing installation. Thus incremental install on a higher level of existing installation is not recommended.

    Table 1. Features for the WebSphere Application Server product
    Feature Description
    Application Server Samples Installs the Samples Gallery and Plants By WebSphere applications.

    For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, you can improve application server startup time by 60 percent and save 15 percent of disk space. You 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 disc for the features that you selected.
    Table 2. 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 log.txt file for installation status.

    Examine the app_server_root/logs/install/log.txt file to verify that there were no file system or other unusual errors while installing. If there are problems, correct them, and reinstall the product.

    The slip install log for the Installation Factory is located in the app_server_root/logs/install/log.txt file, which is the same log file as for a normal installation. If the file already exists, new log messages are appended to the file.

    If you use the Update Installer to uninstall maintenance packages that the Installation Factory installed in a slip installation, the results are in a log in the app_server_root/logs/update directory.

    If problems occur, consult the following applicable logs:

    Log files for WebSphere Application Server: The following table shows the installation logs, content, and indicators of success and failure for WebSphere Application Server for Version 6.1:
    Table 3. Installation and profile creation logs for WebSphere Application Server
    Log Content Indicators
    app_server_root /logs/install/log.txt Logs all installation events
    Return code
    Meaning
    0
    Success
    1
    Failure
    2
    Partial Success
    app_server_root/logs/manageprofiles/profile_name_create.log
    • Traces all events that occur during the creation of the named profile
    • Created when using the Profile Management tool or the manageprofiles command
    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.
    app_server_root/logs/manageprofiles/profile_name_delete.log
    • Traces all events that occur during the deletion of the named profile
    • Created when using the Profile Management tool or the manageprofiles command
    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.
    app_server_root/logs/install/ installconfig.log.gz
    • Logs the activities of ANT configuration scripts that run at the end of the installation procedure
    • Gzip file
    Configuration action failed:
    Unsuccessful ANT script configuration.
    Configuration action succeeded:
    Successful ANT script configuration.

    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 Management tool to recreate the profile.

    Troubleshoot the installation if the app_server_root/logs/install/log.txt file or the app_server_root/logs/manageprofiles/profile_name_create.log file does not contain a record of any problems, but problems exist.

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

    [Windows] Examine the Start menu entry. The menu is an indication of a successful installation:
    • [All] Programs > IBM WebSphere > Application Server v6.1

    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 machine with an operating system such as AIX or Linux, and reinstall.

  11. Click Finish to close the installation wizard.

    See Creating profiles using the graphical user interface for more information.

    Select the check box to open the First Steps console, then click Finish.

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. Further configuration is not necessary at this time.

The Installation wizard updates selected features to the new maintenance level. If any maintenance package includes service for an existing profile, the profile is updated to the new service level.

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

See Creating profiles using the graphical user interface for more information.

What to do next

Deploy an application to get started!

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




In this information ...


Related information

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: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=tins_featuresb_cip
File name: tins_featuresb_cip.html