This topic describes one of several options for installing a customized
installation package (CIP) that includes the IBM WebSphere Application Server
Network Deployment, Version 6 product and one or more maintenance packages.
This topic describes how to use the CIP Installation wizard to install features
that are included in the CIP. The Installation wizard also installs maintenance
packages that are included in the CIP.
- 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 CD-ROM or DVD with the customized
installation package (CIP). Or access the directory where the CIP is located.
If necessary, mount the disc drive as described in Mounting disc drives on operating systems such as AIX or Linux
.
- 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.
- 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 checks
for prerequisite operating system patches with the prereqChecker application,
review the prerequisites on the Supported hardware and software 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.
- 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. This task assumes that a previous installation exists and that you
are adding features with an incremental installation.
The CIP wizard
detects all WebSphere Application Server installations. You can use a CIP
to update the binary files of base, Network Deployment, and Express installations.
Thus, you can use a CIP to do cross product installation. However, you cannot
upgrade from one product level to the next; for example, you cannot use a
CIP to upgrade from a Version 5 product to a Version 6 product. Further, you
cannot use a CIP to add features to a different edition installation.
- Select the check box to apply maintenance and
add features, then click Next.
Do not
change the installation directory unless another existing installation is
in the directory that you specify. An incremental installation adds features
to the shared binaries identified in the field.
You can add available
CIP features to the binaries at any time, by running the CIP Installation
wizard again. Installing additional features does not affect profiles that
you might have already created. (Profiles are runtime environments that are
described in a later step.)
When adding features during an incremental
installation, the wizard displays the Features selection panel next.
- Select features to install and click Next.
A CIP might have
from zero to all of the product features. You can install only what was included
in the CIP.
Table 1. Features for
the WebSphere Application Server Network
Deployment product
Feature |
Description |
Core product files |
Installs the product binary code. |
Application Server
Samples |
Installs the Samples Gallery and Plants
By WebSphere applications. |
Javadoc |
Installs the application programming
interface (API) and system programming interface (SPI) documentation for WebSphere
Application Server classes. |
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 disc space. You can
save up to 30 percent of process footprint (based on a maximum heap size of
256 MB).
The installation wizard displays a confirmation panel.
- Review the summary information and click Next to
install the product code or Back to change your specifications.
The disc space shown on the pre-installation summary panel includes
space for the Java Virtual Machine (JVM). Subtract the size of the JVM for
your operating system to determine the installed size on disc for the features
that you selected.
Table 2. JVM sizes
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.
- 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/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/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/name_of_CIP directory.
If problems occur, consult the following applicable logs:
Log files for WebSphere Application
Server products: The following table shows the installation logs, content,
and indicators of success and failure for WebSphere Application Server products
for Version 6.
Table 3. Installation
and profile creation logs for WebSphere Application Server products
Log |
Content |
Indicators |
app_server_root/logs/log.txt |
Logs all installation events |
- INSTCONFFAIL
- Total installation failure.
- INSTCONFSUCCESS
- Successful installation.
- INSTCONFPARTIALSUCCESS
- Installation errors occurred but the installation is still usable. Additional
information identifies the errors.
|
app_server_root/wasprofileprofile_name.log |
- Traces all events that occur during the creation of the named profile
- Created when using the Profile Creation wizard or
the wasprofile 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/wasprofile/wasprofile_delete_ profile_name.log |
- Traces all events that occur during the deletion of the named profile
- Created when using the Profile Creation wizard or
the wasprofile 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.
|
profile_root/logs/pctLog.txt |
Logs all profile creation events that occur when using
the Profile Creation wizard |
- 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\instconfig.log (Not
available on systems such as AIX or Linux) |
Logs the activities of ANT configuration scripts that
run at the end of the installation procedure. |
- 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 Creation wizard to recreate
the profile.
Troubleshoot the installation if the app_server_root/logs/log.txt file or the app_server_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.
![[Windows]](../../windows.gif)
Examine
the Start menu entry. The menu is an indication of a successful installation:
- [All]
Programs > IBM WebSphere > Application Server Network Deployment v6
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.
Select
the check box to launch the Profile Creation wizard,
then click Next to close the installation wizard and
launch the Profile Creation wizard.
See Creating profiles through the graphical user interface
for more information.
Results
The Installation wizard installs the new features in the existing
installation root directory. The Installation wizard configures the WebSphere
Application Server Network Deployment product for the new features.
You must create a profile that defines a
deployment manager, a managed node, or a stand-alone application server to
have an operational environment.
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.
What to do next
Create
a deployment manager profile and an application server profile.
Use
the Profile Creation wizard to create profiles
in the default profile_root directory
or in a directory that you select.
See Creating profiles through the graphical user interface
.
Deploy
an application to get started!
After creating an application
server profile, you can deploy an application. See Fast paths for WebSphere Application Server
to get started deploying applications.
Note: Adding the samples
feature does not automatically deploy the samples to existing profiles that
did not have samples deployed to them initially. New profiles need to be created
to deploy the samples.