This topic describes how to use the custom installation path to install IBM WebSphere Application Server Network Deployment, Version 6.
Before you begin
This path is one of the installation paths that is available for any operating system. Two other installation paths exist:
Select the appropriate installation path before you begin the installation.
Before starting the installation, see Using the launchpad to start the installation for information about the Installation solutions diagrams. The diagrams show typical topologies for the product. The solutions are also in Planning to install Network Deployment .
Why and when to perform this task
Use the following procedure to install the WebSphere Application Server Network Deployment product.
Steps for this task
umaskTo set the umask setting to 022, issue the following command:
umask 022
For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to see 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.
When
installing the WebSphere Application Server as a Windows service, do not use
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, or do not
choose to install Windows services.
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 Network Deployment.
After launching the Installation wizard from the launchpad or from the command line, the InstallShield MultiPlatform (ISMP) wizard initializes and then displays the Welcome panel.
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 IBM WebSphere Application Server supported hardware, software, and APIs 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.
The Installation wizard checks for a previous installation at the same product level.
If the wizard detects a previous installation, it displays the Existing installation panel. This procedure assumes that you do not have an existing installation that you intend to update. See Installing additional features on an existing Network Deployment installation for more information about that scenario.
The wizard displays a panel that prompts you for the location of the installation root directory for the core product files.
Specify the location of the installation root directory for the product binaries, which are also known as the system files. The system files do not change unless you add features; install service such as refresh packs, fix packs, or interim fixes; or install a product that extends the Network Deployment product.
Spaces are not supported in the name of the installation
directory on Linux and UNIX systems.
Deleting the default target location and leaving an installation directory field empty prevents you from continuing.
Non-ASCII special characters are not supported in the name of the installation directory.
The installer program checks for required space at the beginning of the installation. If you do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, and restart the installation.
Important: Do not use a semi-colon in the directory
name on all Windows systems. WebSphere Application Server cannot install properly
on a Windows platform if the target directory includes a semi-colon. A semi-colon
is the character used to construct the classpath in all Windows systems.
The installation directory path must be no longer than 60 characters to successfully create the Application Server profile on a Windows 2000 system.
The wizard displays the Features selection panel.
Feature | Description | |
---|---|---|
Core product files | Installs the product binary code. | |
Application Server Samples | Installs the Sample applications. | |
Javadoc | Installs the API documentation of WebSphere Application Server classes. |
Performance considerations
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.
The Installation wizard creates the uninstaller program and displays a progress panel that shows which components are being installed.
At the end of the installation, the wizard displays the Installation completion panel.
If problems occur, consult the following applicable logs:
Log | Content | Indicators |
---|---|---|
install_root/logs/log.txt | Logs all installation events |
|
install_root/logs/wasprofile/wasprofile_create_profile_name.log |
|
|
install_root/logs/wasprofile/wasprofile_delete_profile_name.log |
|
|
install_root/profiles/profile_name/logs/pctLog.txt | Logs all profile creation events that occur when using the Profile creation wizard |
|
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 tool to recreate the profile.
Troubleshoot the installation if the install_root/logs/log.txt file or the install_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.
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 Linux or UNIX machine, and reinstall.
See Using the Profile creation wizard for information about creating an operational environment that includes a deployment manager, a managed node, or a stand-alone application server.
Network Deployment V6 includes the ability to create a deployment manager profile, an application server profile, or a custom profile. The second step of installation is to use the Profile creation wizard to create an operational environment that includes one of these profiles.
Result
The Installation wizard installs the core product files and selected features into the installation root directory.
However, you must create a profile that defines a deployment manager, a managed node, or a stand-alone application server to have an operational environment.
What to do next
Create a deployment manager profile!
Use the Profile creation wizard to create profiles in the default install_root/profiles directory or in a directory that you select.
See Using the Profile creation wizard.
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.