Prepare Windows systems for WAS v6.1 installation

 

+

Search Tips   |   Advanced Search

 

Overview

The installation uses an InstallShield MultiPlatform wizard. You can use the graphical interface or use the wizard in silent mode.

Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.

If you encounter a problem such as needing more temporary space or missing prerequisite packages on the OS,...

  1. cancel the installation
  2. make the required changes
  3. restart the installation

Preparing the OS involves such changes as allocating disk space and installing patches to the OS. IBM tests WAS products on each OS platform. Such tests verify whether an operating system change is required for WAS products to run correctly. Without the required changes, WAS products do not run correctly.

 

Procedure

  1. Log on to a user ID that belongs to the administrator group.

    Log on as a member of the administrator group to successfully install the product. You cannot create Windows services from a user ID that does not belong to the administrator group. The creation of Windows services requires the user to have the advanced user rights...

    Act as part of the operating system
    Log on as a service

    Windows service creation can be disabled by launching the graphical interface from the command line with the following additional option:

    install.exe -OPT PROF_winserviceCheck="false"

  2. Optional: Download and install the latest supported version of Internet Explorer 6.

  3. Optional: Download and install Mozilla 1.7.5 or later.

    If you plan to use the Mozilla browser, install the 1.7.5 version to avoid a known problem that causes two browser windows to open when using the launchpad.bat script. This problem is caused by a known bug with the Mozilla -CreateProfile feature. See bugzilla bug 249585 for more information.

  4. Stop all WAS-related Java processes on the machine where you are installing the product.

  5. Stop any Web server process such as the IBM HTTP Server.

  6. Stop all instances of the process_spawner.exe program.

  7. Provide adequate disk space.

    The ND product requires the following disc space:

    730 MB for...

    C:\IBM\WebSphere\AppServer

    ...before creating profiles

    The installation root directory includes the core product files. This size does not include space for profiles or applications. Profiles require 40 MB of temp space in addition to the sizes shown. Profiles have the following space requirements:

    30 MB for the Deployment manager profile

    This size does not include space for Sample applications that you might install. The size also does not include space for applications that you might deploy.

    200 MB for an Application Server profile with the Sample applications

    This size does not include space for applications that you might develop and install.

    10 MB for an unfederated custom profile

    This size does not include space for applications that you might develop and install. The requirement does include space for the node agent. However, federate a custom profile to create an operational managed node.

    After federating a custom profile, the resulting managed node contains a functional node agent only. Use the deployment manager to create server processes on the managed node.

    100 MB for the C:\temp directory

    The temporary directory is the working directory for the installation program.

    830 MB total requirement

    This amount is the total space requirement when installing the product from the disc and when not installing service. Installing profiles requires more space.

    The following space is required for the IBM HTTP Server product:

    110 MB for the C:\IBM HTTP Server directory

    The IBM HTTP Server product requires this space.

    25 MB for the C:\ibm\gsk7 directory

    The IBM Global Security Kit (GSKit) requires this space.

    The following space is the maximum amount that is required for the Web server plug-ins for WAS:

    200 MB for the C:\IBM\WebSphere\Plugins directory

    The Web server plug-ins require this space.

    25 MB for the C:\ibm\gsk7 directory

    The IBM Global Security Kit (GSKit) requires this space.

    The following space is required for the Application Client for WAS:

    150 MB for the C:\IBM\WebSphere\AppClient directory

    The amount of space required to install the application clients is actually less than 150 MB. The amount of space depends on the clients that you install as features.

    The following space is required for the Update Installer:

    200 MB for the C:\IBM\WebSphere\UpdateInstaller directory

    The following space is required for the Application Server Toolkit:

    550 MB maximum for the C:\IBM\WebSphere\AST directory

    The Application Server Toolkit does not include an integrated test environment.

    Install the WAS ND product and configure an appserver to create a test environment.

    The installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The installation wizard also warns you if you do not have enough space to install the product. If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disc space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:

    • For V4.0.x: The size of enterprise archive (EAR) files

    • For V5.0.x: The size of EAR files

  8. Verify that prerequisites and corequisites are at the required release levels.

    Although the installation wizard checks for prerequisite OS patches with the prereqChecker application, review the prerequisites on the Supported hardware and software Web site if you have not done so already.

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

  9. Download Windows Script 5.6 to create Start menu items correctly on Windows 2000 and Windows XP.

  10. Verify that the Java 2 SDK on your copy of the product disc is functioning correctly.

    If you created your own product disc from an ISO image or by copying the actual disc, perform the following steps to verify that the Java 2 SDK on the product CD-ROM or DVD is working correctly.

    1. Change directories to the \win\WAS\jdk\java\bin directory on the product disc. Type the following command:

      cd disc_drive_D:\WAS\jdk\java\bin

    2. Verify the version of the Java 2 SDK. Type the following command:

      .\java -version

      The command completes successfully with no errors when the Java 2 SDK is intact.

 

Results

This procedure results in preparing the OS for installing the product.

 

What to do next

After preparing the OS for installation, you can install the WAS product.

Go to Prepare to install ND on a Windows system for the next step in the overall procedure, which is selecting the type of installation to perform.

 

Related tasks

Prepare to install ND on a Windows system