On distributed systems, you have several choices for installation:
The installation wizard is suitable for installing WebSphere Application Server on a small number of systems. Executing the installation wizard will install one system. You can start with the Launchpad, which contains a list of installation activities to select, or you can execute the installation program directly.
The installer checks for the required operating system level, sufficient disk space, and user permissions. If you fail any of these, you can choose to ignore the warnings. Note that there is a danger that the installation might fail or the product might not work as expected later on.
To install WebSphere Application Server V7.0 on multiple systems or remote systems, use the silent installation. This option enables you to store installation and profile creation options in a single response file, and then issue a command to perform the installation and (optionally) profile creation. The silent installation approach offers the same options as the graphical installer. Providing the options in a response file provides various advantages over using the graphical installation wizard:
The installation options can be planned and prepared in advance
The prepared response file can be tested
The installation is consistent and repeatable
The installation is less fault-prone
The installation is documented through the response file
The Installation Factory is an Eclipse-based tool that allows the creation of WebSphere Application Server installation packages in a reliable and repeatable way tailored to your needs.
The installation factory is part of the WebSphere deliverable on a separate media and download.
The Installation Factory can produce two types of packages:
Customized Installation Packages (CIP)
A WebSphere Application Server CIP package includes a WebSphere Application Server product, product maintenance, profile customization, enterprise archives, other user files as well as user-defined scripting.
Integrated Installation Packages (IIP)
An IIP can be used to install a full WebSphere software stack including Application Servers, feature pack, and other user files and might even contain multiple CIPs.
The Installation Factory allows you to create one installation package to install the full product stack you need to run your applications. Using the scripting interface you can ship and install components not related to the WebSphere installation process.
Depending on the platform on which you are running the Installation Factory, you can build installation packages for operating systems other than the one on which the Installation Factory is running. The Installation Factory running on AIX, HP-UX, Linux, and Solaria operating systems can create installation packages for all supported platforms. The Installation Factory running on Windows can create installation packages for Windows and i5/OS.
The CIP or IIP can be installed on the target system through two methods:
Silent installer using a response file
The benefit of the Installation Factory is mainly in terms of installation time (fix packs, for example, are directly incorporated into the installation image) and in consistency and repeatability of the installations. This gives you a quick pay-back for the time required to build the CIP and IIP.
Centralized installation manager
Another product feature which can be used to install and update WebSphere Application Server Network Deployment installations is the CIM.
Silently install the application server product. To configure the installation, change the options in the response file before you issue the installation command.
Customize the response file to add your selections before attempting to install silently.
Use the response file to supply values to the installation wizard as the wizard runs in silent mode. The wizard does not display interactive panels when it runs in silent mode, but reads values from the response file instead.
Log on to the operating system. If you are installing as a non-root or non-administrative user, then there are certain limitations.
In addition, select a umask that allows the owner to read/write to the files, and allows 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:
To set the umask setting to 022, issue the following command:
Access the root directory of your installation image on your hard disk, or insert the disk labeled "WebSphere Application Server Network Deployment" into the disk drive.
Locate the sample options response file. The file is named
WAS directory on the product image, CD-ROM, or DVD.
Copy the file to preserve it in its original form. For example, copy and save it as
myresponsefile.txt to a location on your hard drive.
Edit the copy in your flat file editor of choice, on the target operating system. Read the directions within the response file to choose appropriate values that reflect parameters for your system. The response file contains a description of each option.
Save the file.
Issue the proper command to use your custom response file. For example, issue a command such as the following:
mnt_cdrom/WAS/install.sh -options /tmp/WAS/myresponsefile.txt -silent
After the installation, examine the logs for success.