This topic describes how to install IBM WebSphere Application Server,
Version 6 with full installation options.
Before you begin
This topic describes
one of the available installation procedures.
Other installation
paths include:
You can install a customized installation
package (CIP) that includes a WebSphere Application Server product and one
or more maintenance packages and other customizations. The Installation Factory
must create a CIP before you can install the CIP. See IBM Installation Factory for WebSphere Application Server for
more information about creating a customized installation package (CIP).
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. Before starting
this installation, see Planning to install WebSphere Application Server. The diagrams
show typical topologies for the product. The solutions are also in
the Installation solution diagrams in the launchpad.
See Using the launchpad to start the installation. You cannot
run the launchpad remotely to install a product. Only local use of
the launchpad is supported.
- Log on to the operating system.
![[Windows]](../../windows.gif)
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.
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.
- Insert the disc labeled WebSphere® Application Server into the disc drive.
If you are installing a customized installation
package (CIP), insert the CD-ROM or DVD with the CIP. Or access the
directory where the CIP is located.
Mount the drive if necessary
as described in Mounting disc drives on operating systems such as AIX or Linux.
- Start the installation.
Or you can start the installation directly with the install command.
/WAS/install
\WAS\install
If you have a problem starting the launchpad, use the
troubleshooting information in Using the launchpad to start the installation to
correct the problem.
When using the launchpad, launch the installation
wizard for WebSphere Application
Server.
After launching the installation wizard from
the launchpad or from the command line, the installer wizard initializes
and then displays the Welcome panel.
- Click Next to continue.
The license agreement displays.
- Read the license agreement and accept its terms.
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.
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.
- 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.
Specifically, the
wizard looks for an existing Version 6.1 installation.
If the
wizard detects a previous installation, it displays the Existing installation
panel, where you can:
- Add features to the existing installation
- Perform a new installation to another directory
- Perform an upgrade of a trial installation or an Express® installation to
the full product
- Add maintenance from a CIP to the existing
installation
- Add files, directories, enterprise application
archive (EAR) files, and a configuration archive (CAR) file from a
CIP to the existing installation
- Use scripts in a CIP to configure the existing
system
See the following articles for more information
about adding features:
If
a previous product exists when installing a CIP:
This procedure assumes that you do not have an existing
installation that you intend to update.
- 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 fix packs or interim
fixes
- Install another product that extends the base product.
The system-owned default app_server_root directories
for installing as a root user or an administrator user are different
than the user-owned default app_server_root directories
when installing as a non-root installer.
Restriction:
- Deleting the default target location and leaving an installation
directory field empty prevents you from continuing.
Do not use symbolic links as
the destination directory. Symbolic links are not supported.
Spaces are not supported in
the name of the installation directory on operating systems such as AIX® or Linux®.
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.
- 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 pre-installation
summary panel for you to review before installing the product.
- 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.
- 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/install/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/install/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: The following
table shows the installation logs, content, and indicators of success
and failure for WebSphere Application
Server for Version 6.1:
Table 1. Installation
and profile creation logs for WebSphere Application
Server
Log |
Content |
Indicators |
app_server_root /logs/install/log.txt |
Logs all installation events |
- Return code
- Meaning
- 0
- Success
- 1
- Failure
- 2
- Partial Success
|
app_server_root/logs/manageprofiles/profile_name_create.log |
- Traces all events that occur during the creation of the named
profile
- Created when using the Profile Management tool or the manageprofiles 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/manageprofiles/profile_name_delete.log |
- Traces all events that occur during the deletion of the named
profile
- Created when using the Profile Management tool or the manageprofiles 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.
|
app_server_root/logs/install/
installconfig.log.gz |
- Logs the activities of ANT configuration scripts that run at the
end of the installation procedure
- Gzip file
|
- 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 Management tool to
recreate the profile.
Troubleshoot the installation if
the app_server_root/logs/install/log.txt file
or the app_server_root/logs/manageprofiles/profile_name_create.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]](../../windows.gif)
Examine the Start menu entry. The menu is an indication
of a successful installation:
- [All] Programs >
IBM WebSphere > Application Server v6.1
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.
- 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 Management tool. Each profile is
created in the profile_root directory
by default.
See Creating profiles using the graphical user interface for more information.