Install additional features on an existing ND product

Install additional features on an existing ND product

+
Search Tips | Advanced Search

You can install additional features on an existing IBM WAS ND installation.
This topic assumes that you have an existing ND installation and to install a feature using the installation wizard graphical user interface.
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.

Installing ND
Installing silently

Before starting this installation, see the following topics:

Preparing the operating system for product installation
Use the launchpad to start the installation

Overview

Use the following procedure to add features to an existing WebSphere Application Server ND installation.

Procedure

Log on to the operating system. In addition, select a umask that would allow the owner to read/write to the files, and allow others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting,...
umask
To set the umask setting to 022,...
umask 022

When installing on a Windows system, a Windows service is automatically created to autostart the appserver 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.

If you plan to run the appserver 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 appserver with the stopServer command. Stop all server processes in all profiles on the machine. For example, issue the following command from...
profile_root/bin

...to stop the server1 process in the appserver 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 appservers. 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 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 WAS ND

Mount the drive if necessary

Start the installation.

launchpad.sh

launchpad.bat on product DVD or launchpad.exe on product CD

Or you can start the installation directly with the install command.

/WAS/install

\WAS\install

If a problem occurs with the Java Runtime Environment (JRE), use the WAS JRE in the /java/jre/bin directory of an installation image to start the installation.
If you have a problem starting the launchpad, use the troubleshooting information in Use the launchpad to start the installation to correct the problem.
When using the launchpad, launch the installation wizard for WAS ND.
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 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 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 specified. 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 V6.1, just one feature is available, which installs sample applications.
For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, you can improve appserver 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 disc space shown on the pre-installation summary panel includes space for the 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...
app_server_root/logs/install/log.txt

...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 WAS ND: The following table shows the installation logs, content, and indicators of success and failure for WAS ND for V6.1:
Table 3. Installation and profile creation logs for WAS ND

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.

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.

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 file...
app_server_root/logs/install/log.txt

...or the file...
app_server_root/logs/manageprofiles/profile_name_create.log

....does not contain a record of any problems, but problems exist.
See Troubleshooting installation and Installation component troubleshooting tips for more information.
Examine the Start menu entry. The menu is an indication of a successful installation:

[All] Programs > IBM WebSphere > Application Server ND v6.1

If problems exist that cause you to reinstall the product, correct the errors, uninstall the product as described in Uninstall 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 through the graphical user interface for more information.
If you did create a profile, select the check box to open the First Steps console.

Results

The Installation wizard installs the new features in the existing installation root directory. The Installation wizard configures the WAS ND product for the new features.

What to do next
Create any deployment manager profile or appserver profile that the 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 appserver 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.
After creating an appserver profile, you can deploy an application.

Installing the product and additional software

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.
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.