This topic describes how to install IBM WebSphere Application Server - Express, Version 6 with full installation options.
Before you begin
This procedure is one of the installation paths that are available for any platform.
Select the appropriate installation path before you begin the installation.
Before starting the installation, see Using the launchpad to start the installation for information about the Installation solutions diagrams. The diagrams show typical topologies for the product. The solutions are also in Planning to install WebSphere Application Server - Express.
Why and when to perform this task
Perform the following installation to install all features for the WebSphere Application Server - Express product and to accept default characteristics for the application server profile.
Steps for this task
umaskTo set the umask setting to 022, issue the following command:
umask 022
For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to see the advanced options. See your Windows documentation for more information.
The installation wizard grants your Windows user ID the
advanced user rights, if the user ID belongs to the administrator group. The
silent installation does not grant these rights. If you create a new user
ID on a Windows platform to perform a silent installation, you must restart
the system to activate the proper authorizations for the user ID before you
can perform a successful silent installation.
When
installing the WebSphere Application Server as a Windows service, do not use
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, or do not
choose to install Windows services.
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 Express server.
After launching the Installation wizard from the launchpad or from the command line, the InstallShield MultiPlatform (ISMP) wizard initializes and then displays the Welcome panel.
The license agreement displays.
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 checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WebSphere Application Server supported hardware, software, and APIs Web site if you have not already done so.
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.
The Installation wizard checks for a previous installation at the same product level.
If the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, perform a new installation to another directory, or perform an upgrade of a trial installation to the full product.
This scenario assumes that there is no existing V6 product on the machine.
The wizard displays a panel that prompts you for the location of the installation root directory for the product binaries.
Specify the location of the installation root directory for the core product files, which are also known as the shared system files or the product binaries. The system files do not change unless you add features; install service such as refresh packs, fix packs, or interim fixes; or install a product that extends the Express product.
Spaces are not supported in the name of the installation
directory on Linux and UNIX systems.
Deleting the default target location and leaving an installation directory field empty prevents you from continuing.
Non-ASCII special characters are not supported in the name of the installation directory.
The installer program checks for required space at the beginning of the installation. 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.
Important: Do not use a semi-colon in the directory
name on all Windows systems. WebSphere Application Server cannot install properly
on a Windows platform if the target directory includes a semi-colon. A semi-colon
is the character used to construct the classpath in all Windows systems.
The installation directory path must be no longer than 60 characters to successfully create the application server profile on a Windows 2000 system.
The wizard displays the Installation options panel. The panel lets you choose whether to do a full installation or a custom installation. A custom installation displays the Features selection panel. Use the panel to select which features to install. This procedure documents using the full installation, which does not display the Features selection panel..
Select Full installation to install all features. Choose this option to install everything you need to run Web applications on your serve. Use this option if you are new to WebSphere Application Server - Express and are unsure of what to install.
The wizard displays the pre-installation summary panel for you to review before installing the product.
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.
If problems occur, consult the following applicable log files. See Troubleshooting installation for the complete list of log files.
Log | Content | Indicators |
---|---|---|
install_root/logs/log.txt | Logs all installation events |
|
install_root/logs/wasprofile/wasprofile_create_profile_name.log |
|
|
install_root/logs/wasprofile/wasprofile_delete_profile_name.log |
|
|
install_root/profiles/profile_name/logs/pctLog.txt | Logs all profile creation events that occur when using the Profile creation wizard |
|
install_root/logs/instconfig.log (Not available on Linux systems or UNIX systems) | Logs the activities of ANT configuration scripts that run at the end of the installation procedure. |
|
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 creation tool to recreate the profile.
Troubleshoot the installation if the install_root/logs/log.txt file or the install_root/logs/wasprofile/wasprofile_create_default.log file does not contain a record of any problems, but problems exist.
See Troubleshooting installation and Installation component troubleshooting tips for more information.
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 Linux or UNIX machine, and reinstall.
Result
This procedure results in the Installation wizard installing WebSphere Application Server - Express into the installation root directory. The Installation wizard creates a profile named default that provides the run-time 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 creation wizard. Each profile is created in the install_root/profiles directory by default.
See Using the Profile creation wizard for more information.
What to do next
Deploy an application to get started!
See Fast paths for WebSphere Application Server to get started deploying applications.
Related tasks
Installing the product and additional software