About this task
Perform the following installation to add features to
an existing WebSphere Application Server installation.
This
installation also installs maintenance packages that are included
in the CIP.
- Log on to the operating system. If you are
installing as a non-root or non-administrative user, then there are
certain limitations.
![[Windows]](../../windows.gif)
When installing as an administrative
user on a Windows
® operating
system, a Windows service
is automatically created to autostart the application server. 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
Control Panel > Administrative Tools >
Local Security Policy > Local Policies > User Rights Assignments to
set the advanced options. See your Windows operating
system 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 restriction, install with a user ID that does
not contain spaces.
- Stop each running application server.
Stop all server processes in all profiles associated with
the target product instance. For example, issue the following command
from the profile_root/bin directory
to stop the server1 process in the application server profile:
./stopServer.sh server1
./stopServer server1
If
a server is running and security is enabled, use the following command:
./stopServer.sh server1 -user user_ID -password password
./stopServer server1 -user user_ID -password password
- Uninstall all maintenance packages.
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 updi_root/update command
to search for and uninstall all maintenance packages.
- Access the root directory of your installation
package on your hard disk, or insert the disc containing the installation
package into the disc drive.
If you are installing the product
from CD and the CIP installer is spanned across multiple CDs, you will be
prompted during the installation for the next CD.
Best practice: To
avoid being prompted for subsequent CDs, copy all installation CDs into the
same directory on your hard disk, name them DISC1. DISC2, and so on for each
disc, and run the installer from the DISC1 directory. You will not be prompted
for the next CD during installation if you have followed this naming convention.
If you are installing silently, then you must use this naming convention or
the installation will not proceed.
bprac
Mount
the drive if necessary.
- Start the installation directly with the install command.
- Change to the WAS directory.
- Run the install command.
- ./install
install
After launching the CIP installation wizard from the command
line, the wizard initializes and then displays the Welcome panel.
Click About this custom installation package to
display detailed information about the current custom installation
package, such as the edition and version.
- 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 WebSphere Application
Server detailed system requirements 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.
The installation
process verifies that the minimum required version of a supported
operating system is available. If you 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 you are not at
the minimum version of a supported operating system, you can continue
with the installation, but the installation or product operation might
not succeed without applying maintenance. If you are at a higher
major release
of a supported operating system, or the operating system itself is
not on the supported list, you might encounter the following warning:
Warning: A supported operating system was not detected.
Support for your operating system might have been added after the release of the product.
See the WebSphere Application Server detailed system requirements Web pages for more information
about supported operating systems. You can continue with the installation, but the installation
or product operation might not succeed without applying maintenance. Go to the product 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 your operating system is supported
and that you 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 you are installing the product 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. Read the "Non-root installation" topic in the WebSphere Application
Server, Version 7.0 Information Center for more information. Click Next.
- If the wizard detects a previous
installation, then the product detection panel is displayed.
You
have the following options:
- Add features to the existing installation
- Install a new copy of the product to another directory
- Create a new WebSphere Application Server profile using the Profile
management tool
An incremental installation adds features to the shared
binaries identified in the field. You can add features to the core
product files at any time by running the Installation wizard again.
Installing additional features does not affect profiles that you might
have already created.
Choose the radio button to add additional
features. Do not change the corresponding installation directory unless
another existing installation is in the directory that you specify.
Click Next to
continue.
- Select features to install and click Next.
A CIP might not have all features available to install. You
can install only what was included in the CIP.
Note: If
an existing installation is at a lower level than the CIP or at the
same level as the CIP, the core product will be updated to the CIP
level automatically. If an existing installation is at a higher level
than the CIP, the core product will not be down leveled. The feature
panel only shows the features you are missing, if you select to install
the new feature from CIP, the installed features will be at the same
level of CIP, which is lower than existing installation. Thus incremental
install on a higher level of existing installation is not recommended.
There
are several features available:
- 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 administrative
console
Installs all the non-English language files for using
the administrative console from machines with non-English locales.
If you do not select this option then only the English language pack
is installed.
- Install non-English language packages for the application server
runtime environment
Installs all the non-English language files
that support the application server runtime environment such as the
wsadmin tool and logging. If you do not select this option then only
the English language pack is installed.
The installation wizard displays a confirmation panel.
- The installation summary panel is displayed.
If you are installing as a non-root
user, you can choose to verify whether you have the correct permissions to
install the product successfully. Select the Verify my permissions
to perform the installation check box if you wish to verify your
permissions to install the product. If the permission check fails, then review
your user permissions and retry the installation. Read the "Non-root installation"
topic in the WebSphere Application Server, Version 7.0 Information Center
for more information.
The verify permissions function is currently not available
on Windows operating systems.
Review the summary information. 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.
- The Installation results panel
is displayed. You can verify the success of the installer program
by examining the completion panel and the app_server_root/logs/install/log.txt file
for feature installation status. Although the samples feature
has been installed, the samples have not yet been deployed into a
specific application server. To deploy the samples choose one of the
following options:
- Deploy the samples to an existing application server. Run the
install command found in app_server_root/samples/bin
- Create a new profile using the Profile Management Tool, which provides
an option to deploy the samples during profile creation. Select the
checkbox if you want run the Profile Management Tool when the installation
has completed.
- Click Finish to close
the installation wizard.
If you 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
you did create a profile, select the check box to open the First Steps
console then click Finish.
Results
The Installation wizard installs the new features in the
existing installation root directory. The Installation wizard configures
the WebSphere Application Server product for
the new features. Further configuration is not necessary at this time.
The
Installation wizard updates selected features to the new maintenance
level. If any maintenance package includes service for an existing
profile, the profile is updated to the new service level.
Further configuration
is not necessary at this time. However, you can create additional
standalone application servers with the Profile Management Tool. Each profile is
created in the profile_root directory by default.
See the documentation on profiles 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.