Installing a base product CIP with full installation options

This topic describes how to install a customized installation package (CIP) that includes the IBM WebSphere Application Server, Version 6 product and one or more maintenance packages. This topic describes using the CIP Installation wizard and selecting the installation method that installs all of the available features 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 install all of the features that are in the CIP for the base WebSphere Application Server product and to accept default characteristics for the application server profile.

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

Procedure

  1. Log on to the operating system.

    Log on as root on an operating system such as AIX® or Linux®, or as a member of the administrator group on a Windows® 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] 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, you must restart the system to activate the proper authorizations for the user ID before you can perform a successful silent installation.

    [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 the terms in the license agreement 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: 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 scenario assumes that there is no existing Version 6.x product on the machine.

    The wizard displays a panel that prompts you for the location of the installation root directory for the product binaries.

  7. Specify the destination of the installation root directory and click Next.

    Specify the location of the installation root directory for the product binaries, which are also known as the core product files or system files.

    The core product files do not change unless you:
    • Install a CIP
    • Add a feature
    • Install service, such as refresh packs, fix packs, or interim fixes
    • Install another product that extends the base product.
    Restriction:
    • Deleting the default target location and leaving an installation directory field empty prevents you from continuing.
    • [AIX] [HP-UX] [Linux] [Solaris] Do not use symbolic links as the destination directory. Symbolic links are not supported.
    • [AIX] [HP-UX] [Linux] [Solaris] Spaces are not supported in the name of the installation directory on operating systems such as AIX or Linux.
    • [Windows] Do not use a semicolon in the directory name on Windows systems. WebSphere Application Server cannot install properly on a Windows platform if the target directory includes a semicolon. A semicolon is the character used to construct the class path on Windows systems.

    The installer program checks for required space before calling the installation wizard. If you do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, and restart the installation.

  8. Choose a type of installation and click Next.

    Select Full installation to install all features. Choose this option to install everything you need to run Web applications on your server. Use this option if you are new to WebSphere Application Server and are unsure of what to install.

    The wizard displays the preinstallation summary panel for you to review before installing the product.

  9. Review the summary information, then 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. 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/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/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 products: The following table shows the installation logs, content, and indicators of success and failure for WebSphere Application Server products for Version 6.
    Table 1. Installation and profile creation logs for WebSphere Application Server products
    Log Content Indicators
    app_server_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.
    app_server_root/wasprofileprofile_name.log
    • Traces all events that occur during the creation of the named profile
    • Created when using the Profile Creation wizard or the wasprofile 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/wasprofile/wasprofile_delete_ profile_name.log
    • Traces all events that occur during the deletion of the named profile
    • Created when using the Profile Creation wizard or the wasprofile 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.
    profile_root/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.
    app_server_root\logs\instconfig.log (Not available on systems such as AIX or Linux) Logs the activities of ANT configuration scripts that run at the end of the installation procedure.
    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 Creation wizard to recreate the profile.

    Troubleshoot the installation if the app_server_root/logs/log.txt file or the app_server_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.

    [Windows] Examine the Start menu entry. The menu is an indication of a successful installation:
    • [All] Programs > IBM WebSphere > Application Server 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 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

This procedure results in the installation wizard installing WebSphere Application Server into the installation root directory. The installation wizard creates a profile named default that provides the runtime environment for the server1 application server.

Further configuration is not necessary at this time. However, you can create additional stand-alone application servers with the Profile Creation wizard. 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 ...


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: Aug 29, 2010 5:25:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=tins_typicalb_cip
File name: tins_typicalb_cip.html