This topic describes how to upgrade a trial installation of the
base WebSphere Application Server product to the actual product.
Before you begin
If you are upgrading a base trial that was installed
as part of a customized installation package (CIP), create a CIP for the full
base product. Then use the CIP for the full base product to upgrade the trial.
See IBM Installation Factory for WebSphere Application Server for more information
about creating a CIP.
This topic describes
one of the available installation procedures.
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.
Log on as root on an operating system such
as AIX® or Linux®, or as a member of the administrator
group on a Windows® 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.
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.
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 the terms in the license agreement 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.
If the wizard detects a previous installation, it
displays the Existing installation panel, where you can:
- Add maintenance to the existing installation
- Add features to the existing installation
- Add files, directories, enterprise application archive (EAR) files,
and configuration archive (CAR) files to the existing installation
- Use scripts to configure the existing system
- Perform a new installation to another directory
- Perform an upgrade of a trial installation to the full
product
- Perform an upgrade of an Express® installation to the
full product
This task describes
the scenario where a previous installation of the trial exists and you are
installing the actual product to upgrade the trial.
Select the Upgrade
option and click Next. The installer program installs
the new license files and updates the system properties to indicate that the
actual product is installed.
Results
The wizard completes the upgrade and exits at then end of the upgrade
without presenting another panel.
This procedure results in upgrading
a trial installation to the actual WebSphere Application Server product.
What to do next
You can install the base product again to add features. Or you
can use the Profile Creation wizard to create
more stand-alone application servers.
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 profile_root directory
by default.
See Creating profiles using the graphical user interface for more information.
If you have already created
the topology that you require, try deploying an application in your environment.
Deploy
an application to get started!
See Fast paths for WebSphere Application Server to get started deploying applications.