Install the product offerings

Use IBM Installation Manager to install WebSphere Application Server traditional and associated software on supported operating systems.

• Read the hardware and software requirements on the Supported hardware and software website.

• Prepare for installation and learn about IBM Installation Manager.

  Installation Manager is a single installation program that can use remote or local software repositories to install, modify, or update WAS products. Before using Installation Manager, refer to the Installation Manager documentation for a description of the various options that we can specify when we install the Installation Manager.

  In general, IBM recommends that we install new copies of product offerings at new fix-pack levels rather than upgrading existing levels in use. By installing a new copy, we can apply corrective service to both the old and new levels if necessary. We can uninstall any older levels when you no longer need them.

• (iSeries) We must have Java SE 8 64 bit (option 17 of the IBM Java SE) installed on the IBM i system before we install WAS. See IBM i prerequisites.

Depending on the operating system, we can install a product using the Installation Manager GUI, command line, response files, or console. Installation Manager performs the following actions:

• Automatically checks prerequisites
• Looks for a previous WAS installation to determine whether we can add features to WebSphere binaries or to install a new set of product binaries

• Installs the necessary product binaries

(Dist) Use the launchpad to launch each installation procedure. See Use the launchpad to start installations.

If we run into problems when we install the product, see the troubleshooting information at Troubleshoot installation.

Tasks

1. Roadmap
2. Plan the installation
3. Prepare the operating platform for installation
4. Install IBM Installation Manager if it is not already installed.
5. Access the product repositories that Installation Manager uses to install the product.

6. Install the product and any optional components.
   • Install using the GUI
   • Install using the command line
   • Install using response files

We can install the following product offerings:

• Install WAS with the required Java SDK.

• Install Application Client for IBM WAS.

• Install DMZ Secure Proxy Server for IBM WAS.

• Install IBM HTTP Server for WAS.

  IBM HTTP Server is based on the Apache HTTP Server developed by the Apache Software Foundation (ASF). WAS v9 provides advanced web server capabilities and a consistent cross-platform build of the Apache HTTP Server.

  After installing a WAS product, we can use the application server to serve applications over the Internet. It is not necessary to install the IBM HTTP Server or another web server.

  The installation solution diagrams in Planning the product installation show the components present in different types of environments.

• Install the Web Server Plug-ins for IBM WAS.

  After installing a web server plug-in, we can use the Web Server Plug-ins Configuration Tool to create a new element in the application server configuration called a web server definition. We can then manage applications for the web server using the administrative console.

• Install the WebSphere Customization Toolbox.

  The WebSphere Customization Toolbox includes tools for customizing various parts of our WAS environment. For example, we can use the WebSphere Customization Toolbox GUI to launch the Web Server Plug-ins Configuration Tool to configure the web server plug-ins for any operating system on which the WebSphere Customization Toolbox can be installed.

Restrictions:

• If a Beta version of the product is installed, uninstall it before we install this version.

• If we move or extract a product repository, do not transfer the content of a repository in non-binary mode and do not convert any content on extraction.

• The Installation Manager web interface, which is included in Installation Manager Version 1.8.0 and later, does not work with WAS v9.0 offerings.

• (Windows) If a non-administrator installs WAS into the Program Files or Program Files (x86) directory with User Account Control (UAC) enabled, WAS will not function correctly. We must install the product into a different directory or disable UAC.

Subtopics

• Use the launchpad to start installations
  
• Install Installation Manager
  
• Configure the product repositories in Installation Manager
  
• Install the product offerings on distributed operating systems using the GUI
  
• Install the product offerings using the command line
  
• Install the product offerings using response files
  
• Install and update IBM SDK on distributed operating systems
  
• Setting file permissions
  
• Verifying the installation
  
• Product version information
  
• Prepare for application update settings
• Use application properties files to install, update, and delete enterprise application files