You can install additional features on an existing IBM WebSphere
Application Server Network Deployment installation.
- Log on to the operating 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.
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.
- Stop each running application server
with the stopServer command.
Stop
all server processes in all profiles on the machine. 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
If
a server is running and security is enabled, use the following command:
./stopServer.sh server1 -user user_ID -password password
If
you have multiple servers, you can use the
serverStatus command
to find running application servers. Issue the following command from
the
profile_root/bin directory
to determine which servers, if any, are running:
./serverStatus.sh -all
- Stop the node agent process with the stopNode command.
Stop the node agent process that might be running on the
machine. For example, issue the following command from the
profile_root/bin directory
of a federated node on a Linux machine to stop the node agent process:
./stopNode.sh
If servers are running and security is enabled,
use the following command:
./stopNode.sh -user user_ID -password password
- Stop the deployment manager dmgr process
with the stopManager command.
Stop
all dmgr processes that are running on the machine. For example, issue
this command on a Linux machine from the
profile_root/bin directory
of the deployment manager profile:
./stopManager.sh -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.
- Insert the product disc that provides the feature
into the disc drive.
Feature |
Product disc |
Sample Applications |
WebSphere Application Server Network
Deployment |
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 Network
Deployment.
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 both the IBM and the non-IBM terms 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 product level. This task describes the scenario where a previous
installation exists and you are adding features with an incremental installation.
When
the wizard detects a previous installation, it displays the Existing installation
panel. The panel lets you add features to the existing installation, or perform
a new installation to another directory.
- Choose to install additional features. Click Next to
continue to the Features selection panel.
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 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.
When
adding features during an incremental installation, the wizard displays the
Features selection panel next.
- Select features to install and click Next.
In Version 6.1, just one feature is available, which
installs sample applications.
Table 1. Features for the WebSphere Application Server Network Deployment product
Feature |
Description |
Application Server
Samples |
Installs the Samples Gallery and Plants
By WebSphere applications. |
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).
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 disk 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/install/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.
If problems occur, consult the following applicable
logs:
Log files for WebSphere Application
Server Network
Deployment: The following table shows the installation logs,
content, and indicators of success and failure for WebSphere Application
Server
Network
Deployment for Version 6.1:
Table 3. Installation and profile creation logs for WebSphere
Application Server Network
Deployment
Log |
Content |
Indicators |
app_server_root/logs/install/log.txt |
Logs all installation events |
- Return code
- Meaning
- 0
- Success
- 1
- Failure
- 2
- Partial Success
|
app_server_root/logs/manageprofiles/profile_name_create.log |
• Traces all events that occur during the
creation of the named profile
• Created when using the Profile Management tool or the manageprofiles 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.
|
user_data_root/profileRegistry/logs/manageprofiles/create.log |
• Traces all events that occur during the
creation of the named profile
• Created when using the Profile Management tool or the manageprofiles 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/manageprofiles/profile_name_delete.log |
• Traces all events that occur during the
creation of the named profile
• Created when using the Profile Management tool or the manageprofiles 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.
|
app_server_root/logs/install/installconfig.log.gz |
• Logs the activities of ANT configuration
scripts that run at the end of the installation procedure
•
Gzip file
|
- Configuration action failed:
- Unsuccessful ANT script configuration.
- Configuration action succeeded:
- Successful ANT script configuration.
|
app_server_root/logs/install/installconfig.log |
• 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 Management tool to
recreate the profile.
Troubleshoot the installation if
the app_server_root/logs/install/log.txt file
or the app_server_root/logs/manageprofiles/profile_name_create.log file
does not contain a record of any problems, but problems exist.
Troubleshoot the installation
if the app_server_root/logs/install/log.txt file
or the user_data_root/profileRegistry/logs/manageprofiles/create.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.1
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.
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 Creating profiles using the graphical user interface for
more information.
If you
did create a profile, select the check box to open the First Steps
console.
What to do next
Create any deployment manager profile or application server profile
that your configuration requires.
Adding the samples feature does not automatically
deploy the samples to existing profiles that did not have samples deployed
to them initially. You must create a new profile to deploy the samples. For
example, create an application server profile and select to deploy the sample
applications.
Use the Profile Management tool to
create profiles in the default profile_root directory
or in a directory that you select.
See Creating profiles using the graphical user interface.
After creating an
application server profile, you can deploy an application. See Fast paths for WebSphere Application Server to
get started deploying applications.