This topic describes how to install additional features to an existing IBM WebSphere Application Server - Express, Version 6 installation.
Before you begin
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 shadowed in Planning to install WebSphere Application Server - Express in the information center.
Why and when to perform this task
Perform the following installation to add features to an existing WebSphere Application Server - Express installation.
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.
./stopServer.sh server1
./stopServer.sh server1 -user user_ID -password password
You are using the product installation image to install additional features. The features have not had any maintenance applied to them. If you remove all maintenance packages, your entire product will be at the same release level. You can then reapply the maintenance packages as described in a later step.
Start the Update Installer program with the install_root/updateinstaller/update command to search for and uninstall all maintenance packages.
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.
This task describes the scenario where a previous installation exists and you are adding features with an incremental installation.
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.
Do not change the installation directory unless another existing installation is in another directory. An incremental installation adds features to the shared binaries identified in the location field.
You can add features to the binaries at any time, by running the Installation wizard again. Installing additional features does not affect profiles that you might have already created. (Profiles are run-time environments that are described in a later step.)
When adding features during an incremental installation, the wizard displays the Features selection panel.
Feature | Description | |
---|---|---|
Core product files | Installs the product binary code. | |
Application Server Samples | Installs the Sample applications. | |
Javadoc | Installs the API documentation of WebSphere Application Server - Express classes. |
Performance considerations
For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, you can improve application server startup time by 60 percent and save 15 percent of disk space. You can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).
AIX | HP-UX | Linux | Solaris | Windows |
---|---|---|---|---|
59 MB | pa-risc: 109 MB 64 bit: 137 MB |
ia32: 83 MB 64 bit: 133 MB |
81 MB | ia32: 75 MB 64 bit: 71 MB |
Verify that you have the total amount of free space shown before installing. Space is required for a working copy of the JVM during the installation.
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.
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
The Installation wizard installs the new features in the existing installation root directory. The Installation wizard configures the WebSphere Application Server - Express product for the new features.
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