Install ND

Install ND

Use the Installation wizard GUI to install IBM WAS ND on distributed operating system platforms.
Obtain the installation image from the WAS disc, or Passport Advantage...
For example...

Download WAS ND V7.0 for the Linux
Download WAS ND V7.0 for the HP-UX
Download WAS for Developers V7.0 for the AIX
Download WAS for Developers V7.0 for the IBM i (formerly i5/OS)
Download WAS for Developers V7.0 for the Solaris

Before installing...

Plan the installation
Verify the OS is ready

Use the launchpad to start the installation.

Log on to the operating system. If installing as a non-root or non-administrative user, then there are certain limitations. See the documentation for non-root installation for more information.
[AIX] [HP-UX] [Linux] [Solaris]
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:
umask

To set the umask setting to 022...
umask 022

(Windows) When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the appserver. The installer user account must have the following advanced user rights:

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

For example, on some Windows operating systems, click Administrative Tools > Local Security Policy > User Rights Assignments to set the advanced options. See the Windows operating system documentation for more information.

(Windows) If we plan to run the appserver 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 restriction, install with a user ID that does not contain spaces.
Access the root directory of the installation image on the hard disk, or insert the disc labeled WAS ND into the disc drive.
The appserver product installer is spanned across multiple CDs. If installing WAS ND from CD, you will be prompted during the installation for the next CD.
Best practice: Use the following procedure to avoid being prompted for subsequent CDs:

Copy both installation CDs into the same parent directory (for example, WebSphere7) on the hard disk
Name the directories DISC1 and DISC2 (for example, WebSphere7/DISC1 and WebSphere7/DISC2)
If the system's language is not set to English, set the language to English for the duration of the installation.
If the language is set to something other than English, the installer will still prompt you to enter the second CD.
Run the installer from the DISC1 directory after following the remaining instructions in this document.
After we have completed the installation, reset the system's language to its previous setting if we had changed it during the installation.

You will not be prompted for the next CD during installation if we have followed this naming convention. If installing silently, then follow this procedure or the installation will not proceed. If installing from a DVD or a downloaded image, then you do not need to take any action because these images are not spanned
[AIX] [HP-UX] [Linux] [Solaris]
Mount the drive if necessary.
[Linux] If we attempt to install the application Server from a CD or DVD that has been burned from an ISO image on Red Hat Linux, the launchpad and installer applications might fail to run. When Red Hat Linux automatically mounts a CD or DVD, we cannot run the disc. The installation scripts and the launchpad script are unable to run properly. To resolve this issue, unmount the disc and then remount it with the relevant read and execute levels.
Start the installation of a product image with the launchpad script...

./launchpad.sh

...or we can start the installation directly with the install command.
./install.sh

(Windows) There might be certain operating system policy restrictions if we are installing as a non-administrator on Windows 2003 on an AMD processor. We might not be able to run the install command by double-clicking the file in Windows Explorer. Run the command from a command prompt or rename the command to something other than install.exe or setup.exe and run the command.
If an error occurs with the Java SE Runtime Environment 6 (JRE 6), force the installation to use the correct runtime environment with the following command, where downloaded_directory is the name of the directory in which you downloaded the image:

[AIX] [HP-UX] [Linux] [Solaris]
./install -is:javahome disc_mount_point/downloaded_directory/JDK/jre.pak/repository/package.java.jre/java/jre
(Windows) install -is:javahome disc_drive:\downloaded_directory\JDK\jre.pak\repository\package.java.jre\java\jre

If we cannot start the launchpad, use the troubleshooting information in Use the launchpad to start the installation to correct the problem.
When using the launchpad, launch the installation wizard for WAS ND.
The installation wizard initializes and then displays the Welcome panel.
Click Next to continue.
The license agreement panel is displayed. Read the license agreement and accept its terms. After you accept the licensing terms, the installation wizard checks for a supported operating system and prerequisite patches.
Although the installation wizard automatically checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the WAS detailed system requirements Web site if we have not already done so. The Web site lists all supported operating systems and the operating system fixes and patches that install to have a compliant operating system. The installation process verifies that the minimum required version of a supported operating system is available. If we meet the minimum release requirements or are at a higher minor release of a supported operating system, then you will not encounter a prerequisite error. If not at the minimum version of a supported operating system, we can continue with the installation, but the installation or product operation might not succeed without applying maintenance. If at a higher major release of a supported operating system, or the operating system itself is not on the supported list, we might encounter the following warning:
Warning: A supported operating system was not detected.
Support for the operating system might have been added after the release of WAS ND. See the WAS detailed system requirements Web pages for more information about supported operating systems. We can continue with the installation, but the installation or product operation might not succeed without applying maintenance. Go to WAS support Web pages to obtain the latest maintenance packages to apply after installation.

Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
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.
The systems prerequisite check panel is displayed.
After confirming that the operating system is supported and that we have installed all necessary patches, click Next to continue. The Installation wizard checks for a previous application server installation at the same product level.
If installing WAS ND as a non-root user (or a non Administrator on Windows operating systems), then a panel is displayed indicating that a non-root user has been detected.
This panel contains important information about installing as a non-root user. See Non-root installation for more information. Click Next.
If the wizard detects a previous installation, then WAS detection panel is displayed.
If the wizard does not detect a previous installation, then skip this step. we have the following options:

Add features to the existing installation
Install a new copy of WAS to another directory
Create a new WAS profile using the Profile management tool

This procedure assumes that you do not have an existing installation that you intend to update. If the wizard detects a previous installation, see the following depending on the situation:
See Install additional features on an existing ND product for more information about the scenario that adds features to an existing product.
The optional features panel is displayed.
There are several features available. If we choose not to install a feature at this time, then we can run the installer later and add features to this installation. Choose from the following features:

Install the sample applications
Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.
Install non-English language packages for the admin console
Installs all the non-English language files for using the admin console from machines with non-English locales. If we do not select this option then only the English language pack is installed.
Install non-English language packages for the appserver runtime environment
Installs all the non-English language files that support the appserver runtime environment such as wsadmin and logging. If we do not select this option then only the English language pack is installed.

New feature: Language support has been modularized into language packs for the admin console and appserver runtime components. This allows you to update the current language packs or add new language packs released by IBM using the Update Installer. The language pack design also allows you to defer installing non-English language packs for these two components to save disk space
Avoid trouble: We might want to defer installing features, such as language packs and samples, to save disk space. However, consider installing the features if there is a chance we might use them in the future. If we choose not to install the features and then later install maintenance, you will have to uninstall all maintenance, install the features, and then reapply all maintenance or the features might be corrupted.
Select the features you want to install and click Next.
The installation directory panel is displayed.
Specify the destination of the installation root directory and click Next.
Specify the location of the installation root directory for WAS binaries, which are also known as the core product files or system files. The core product files do not change unless you:

Add a feature
Install maintenance, such as refresh packs, fix packs, or interim fixes
Install another product that extends WAS ND.

The system-owned default APP_ROOT directories for installing as a root user or an administrator are different than the user-owned default APP_ROOT directories when installing as a non-root installer.
Restriction:

Delete 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 systems such as AIX or Linux.
(Windows) Do not use a semicolon in the directory name on Windows systems.
WAS 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.
If using parentheses () in the directory name, include a space before the leading parenthesis or profile creation actions will fail.

The installer program checks for required space before calling the Installation wizard. If we do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, then restart the installation.
Select an initial server environment on the WAS environments panel.

Profile Type Description
Cell Create a cell with two profiles: a dmgr and an appserver node that is already federated into the dmgr cell. This is useful for development environments.
Management Create a management profile that provides the servers and services necessary to manage the WebSphere environment. We can select one of the following management profile types on the following panel:

Deployment manager
The dmgr deploys and manages applications to a cell of appservers. Appservers that belong to the cell managed nodes.
Job manager
The job manager provide a single console to administer multiple base servers, multiple dmgrs, and do asynchronous job submission.
Administrative agent Provide a single interface to administer multiple unfederated appservers.

Application server Create a stand-alone appserver profile.
Custom Create a custom profile which belongs to a dmgr cell, to make applications available to the Internet or to an intranet under the management of the dmgr. You must federate this node to use it.
Secure proxy Create a secure proxy server to take requests from the internet and forward them to appservers. The proxy server resides in the DMZ.
None Do not create a profile during installation. However, if we do not create a profile during installation, then create a profile after installation to have an operational product.

The administrative security panel is displayed.
Choose whether to enable administrative security and click Next.
The default setting is to enable administrative security. Clear the check box to disable security or supply an administrative ID and password. If installing the samples on an application server profile, specify the samples security information in the samples section below the administrative security section.
In environments where you plan to have multiple standalone application servers, the security policy of each appserver profile is independent of the others.
Changes to the security policies in one appserver profile are not synchronized with the other profiles.
Write down the user name and password.
We cannot log onto the admin console without it. We cannot use WAS at all unless you know the ID and password.

The installation summary panel is displayed.

[AIX] [HP-UX] [Linux] [Solaris]
If installing as a non-root user, we can choose to verify whether we have the correct permissions to install WAS successfully. Select the check box...
Verify my permissions to perform the installation

...to verify the permissions to install WAS ND. If the permission check fails, then review the user permissions and retry the installation. Read the Non-root installation topic for more information.
(Windows) The verify permissions function is currently not available on Windows operating systems.

Review the summary information. Click Next to install WAS 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.
The centralized installation manager (CIM) panel is displayed.
The CIM capability is automatically installed with WAS ND, but we can defer installing the repository until later with the CIM repository manager tool. Select the check box...
Install Centralized Installation Manager Repository

...to install the repository now and specify or browse to a target location.
Note that installations that are submitted by the CIM might become unresponsive on AIX 5.3 targets.
CIM uses Remote Execution and Access V2.3 to transfer files to target systems. OpenSSH V4.7.0.5302 for IBM AIX V5.3 is not compatible with Remote Execution and Access V2.3. If the target systems are running AIX V5.3 with OpenSSH V4.7.0.5302 installed, the file transfer might stop in the middle of the transfer.
From the "Installations in progress" panel, the status of the installation stays in the transferring files state for longer than 90 minutes.
To determine the level of OpenSSH that is installed on the AIX system
lslpp -l | grep openssh

OpenSSH version 4.7.0.5301 does not have this problem. We can revert the OpenSSH version from V4.7.0.5302 to V4.7.0.5301.
Click Next.
The Installation results panel is displayed. Verify the success of the installer program by examining the completion panel and...
APP_ROOT/logs/install/log.txt

...to verify that there were no file system or other unusual errors while installing. If there are problems, correct them, and reinstall the product. Important information about the profile you created is also available in...
$WP_PROFILE/logs/AboutThisProfile.txt

See Troubleshooting installation for more information on other installation logs and log locations.
Select the checkbox...
Launch the First steps console

...to launch the First steps application. Use the First steps console to verify the installation, start the Profile Management Tool, start the appserver, or open the admin console, where we can deploy sample applications. See the First steps documentation for more information.
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...
APP_ROOT/logs/install/log.txt file
APP_ROOT/logs/manageprofiles/profile_name_create.log

...does not contain a record of any errors, but errors exist.
Read the Troubleshooting installation and Installation component troubleshooting tips topics for more information.

(Windows) Examine the Start menu entry. The menu is an indication of a successful installation:

[All] Programs > IBM WebSphere > Application Server ND V7.0

If problems exist that cause you to reinstall WAS ND, correct the errors, uninstall WAS as described in the uninstallation topics, 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.
Click Finish to close the installation wizard.
If we did not create a profile during the installation, the option to launch the Profile Management Tool is displayed. Use the Profile Management Tool to create an operational environment that includes a profile.
See the profiles documentation for more information.
If we did create a profile, select the check box to open the First Steps console then click Finish.

Results

The installation wizard installs WAS files into the installation root directory.

Next steps

After installing WAS from the installation image, the next step is to check for available updates before you alter the configuration of WAS ND. Read the "Installing maintenance packages" topic for more information.
After creating an appserver profile, we can deploy an application. See Fast paths for WAS to get started deploying applications.

Related concepts
Non-root installation

Related tasks
Troubleshooting installation
Install maintenance packages, interim fixes, fix packs, and refresh packs
Install WAS and additional software

Related
firststeps

Profile Type	Description
Cell	Create a cell with two profiles: a dmgr and an appserver node that is already federated into the dmgr cell. This is useful for development environments.
Management	Create a management profile that provides the servers and services necessary to manage the WebSphere environment. We can select one of the following management profile types on the following panel: Deployment manager The dmgr deploys and manages applications to a cell of appservers. Appservers that belong to the cell managed nodes. Job manager The job manager provide a single console to administer multiple base servers, multiple dmgrs, and do asynchronous job submission. Administrative agent Provide a single interface to administer multiple unfederated appservers.
Application server	Create a stand-alone appserver profile.
Custom	Create a custom profile which belongs to a dmgr cell, to make applications available to the Internet or to an intranet under the management of the dmgr. You must federate this node to use it.
Secure proxy	Create a secure proxy server to take requests from the internet and forward them to appservers. The proxy server resides in the DMZ.
None	Do not create a profile during installation. However, if we do not create a profile during installation, then create a profile after installation to have an operational product.