WebSphere Application Server Base 6.0 Install
- Installing
- Troubleshooting
- Access this information online
- Install the product and additional software
- New installation and operating model
- New and improved launchpad console
- Roadmap for installing the base product
- Understanding what we can do with the base product
- What to do when an installation problem occurs
- Getting the latest information
- What to do next
- Plan to install WAS
- Prepare the operating system for product installation
- Install the base product with full installation options
- Install the base product with custom options
- Install additional features on an existing base product
- Upgrade Express to the WAS product
- Upgrade the trial to the full product
- Install silently
- Customizing the base options response file
- Configure the product after installation
- firststeps command
- Use the Profile creation wizard
- wasprofile command
- Use the installation verification test
- Use the launchpad to start the installation
- Mounting CD-ROMS on Linux and UNIX operating systems
- Prepare AIX systems for installation
- Prepare HP-UX systems for installation
- Prepare Linux systems for installation
- Prepare Solaris systems for installation
- Prepare Windows systems for installation
- Troubleshooting installation
- Installation component troubleshooting tips
- Troubleshooting installation problems
- Installation either completes with errors or warnings, or hangs
- Problems installing or starting Apache or IBM HTTP Server
- Messages issued during installation and profile creation
- Uninstalling the product
- uninstall command
- vpd.properties file
- Uninstalling the base WAS product
- Uninstalling manually
- Notices
- Trademarks and service marks
Installing
Verify you have enough disk space
df -k
WebSphere Application Server (WAS) products an InstallShield for MultiPlatforms (ISMP) wizard that provides both a graphical interface and silent mode. Silent mode reads options and field values from a response file. WAS products do not support the ISMP console method of installation.
V6 has separate installation procedures for these installable components on the product disc:
The installation program for installing WAS does not install the other components.
New for V6 is the Profile creation wizard. Use the Profile creation wizard after the installation to create more Application Server run-tine environments.
Also new for V6 is the Migration wizard. Use the Migration wizard after the installation to migrate the configuration and applications from a previous version to V6.
Troubleshooting
The log file for the WAS installer is log.txt.
The Profile creation wizard uses several different log files, including files named after the profile being created or deleted. The main file is the pctLog.txt file.
The Migration wizard uses several log files to record migration events.
Access this information online
Information center articles are available at...
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp
This document is superseded by the PDF version of this document at...
www.ibm.com/software/webservers/appserv/infocenter.html
Install the product and additional software
Review the hardware and software requirements.
The launchpad is the preferred method of starting the installation. Use the Launchpad to access...
- product overview
- installation guide
- readme file
If you encounter a problem such as needing more disk space or temporary space or missing prerequisite packages on your Linux or UNIX system, cancel the installation, make the required changes, and restart the installation.
Log on as a member of the administrator group to successfully install the product. We cannot install the product correctly from a user ID that does not belong to the administrator group. Some steps of the installation procedure require the administrator group ID to have the following advanced user rights, Act as part of the operating system and Log on as a service.
The Installation wizard performs the following actions:
- Automatically checks prerequisites
- Looks for a previous WAS V6 installation, to determine whether to let you add features to the product binaries or to install a new set of product binaries
- Looks for a previous V6 installation, to determine whether to let you upgrade from a trial installation to the real product
- Creates a stand-alone application server node
Perform the following procedure to start your installation.
- Plan your installation
- Prepare your operating platform for installation
- Review the roadmap for installing the base product
- Install the base product.
- Perform a typical installation with the wizard
- Perform a custom installation with the wizard
- Install silently
- Install additional features to an existing installation
The installer program does not support the ISMP -console installation method at this time.
- Optional: Install IBM HTTP Server.
Use the application server to serve applications over the Internet. It is not necessary to install the IBM HTTP Server or another Web server. It is also not necessary to install Web server plug-ins. You also do not need the application clients unless the application you are deploying was designed to run as a client application. You also do not have to install an integrated development environment. The development environment is for developers of Web applications.
- Optional: Install Web server plug-ins for IBM HTTP Server or another supported Web server.
If you install the IBM HTTP Server or another Web server, install a binary module for the Web server to enable it to communicate with WAS products. Before install a Web server plug-in, install the Web server.
After installing a Web server plug-in, the Plug-ins installation wizard configures a new element in the application server configuration called a Web server definition. We can then manage applications for the Web server using the administrative console.
- Optional: Install the application clients.
This procedure results in installing IBM WAS, V6.
We can also install IBM HTTP Server, the Web server plug-ins for WAS, and the application clients for WAS.
New installation and operating model
V6 separates the core product binary data from the data that you create as you define and customize your Application Server run-time environment. We can have multiple sets of customized run-time environments. Each environment is known as a profile in V6.
Application Server environments that are created during product installation
Product Default environments Application Server instances created during installation WAS - Express One stand-alone Application Server profile and the Profile creation wizard for creating other Application Server profiles on the same machine. server1 WAS One stand-alone Application Server profile and the Profile creation wizard for creating other Application Server profiles on the same machine. server1 Network Deployment A default run-time environment is not created during installation of the core product files. From the last installation panel, we can launch the Profile creation wizard to create one of the three available profiles:
- Deployment manager profile
- Application Server profile
- Custom profile
Install the Network Deployment product on each machine in a multiple-machine, distributed environment to give each server process access to a local copy of the core product files.
Launchpad console
The launchpad is the focal point for installing from the product compact disc, with important guidance for creating typical topology scenarios. Diagrams help you identify the types of systems that we can create. The launchpad is in the root directory of the product CD.
The launchpad works on installable components in the primary packet of compact discs. Select and launch any of the components on the product disc or view their HTML documentation on the disc.
Use the launchpad command if the program does not start automatically when you insert the product disc:
./launchpad.sh
If we cannot start the launchpad, see the appropriate locale-specific readme file in the root directory on the disc. We can also launch the installation programs directly, using the information in the following table:
Launch command Documentation Name of installable component WAS/install WAS/readme/ readme_en.html
WAS/docs/ InstallGuide_en.htmlThe name of the component varies per product offering:
- WAS - Express
- WAS
- WAS Network Deployment
IHS/install IHS/readme/ readme_en.html
IHS/docs/ InstallGuide_en.htmlIBM HTTP Server plugin/install plugin/readme/ readme_en.html
plugin/docs/ InstallGuide_en.htmlWeb server plug-ins for WAS AppClient/install AppClient/readme/ readme_en.html
AppClient/docs/ InstallGuide_en.htmlApplication client for WAS
Other directories on the product CD contain components that are automatically installed during one or more of the installation procedures for the installable components.
Linux AIX, HP-UX, Solaris WAS products require that you log on as root on a Linux or UNIX operating system to install. Set the umask to 022 for security purposes after logging on as root before you install:
umask 022
Set file permissions to 755 after installation, as in the following example for one file:
chmod 755 setupCmdLine.sh
The IBM HTTP Server tolerates a non-root installation, but we cannot install the Global Services Kit 7 (GSKit 7) that is required for HTTPS security. We can install IBM HTTP Server as a non-root user, then log on as root to install the GSKit program from the directory on the product disc.
V6 package descriptions
Each product package contains three sets of compact discs, which are the primary packet and two supplemental packets. The product CD is always in the primary packet. The product packages and their installable components are described in detail in the following sections:
Packaging information for IBM WAS
| Disc label | Versions of the disc | Comments |
|---|---|---|
| WAS | Platform versions available:
| Each platform-specific CD contains the following installable components:
In addition, the Windows platform CD has the Data Direct JDBC drivers. Use the launchpad application in the root directory to install and view information about any of the installable components in the primary packet. |
| WAS Application Server Toolkit disc
Application Server Toolkit | Two different platform versions of this CD are available:
| The license for the Application Server Toolkit is an unlimited use license. |
| Rational Application Developer Trial for WAS |
Three compact discs are available for Linux (Intel) platforms and four compact discs are available for Windows platforms. | Rational Application Developer is the next generation of the award-winning IBM WebSphere Studio Application Developer. Rational Application Developer is a comprehensive integrated development environment for visually designing, constructing, testing, and deploying Web services, portals, and J2EE applications. Rational Application Developer accelerates J2EE development with a complete set of high-productivity tools, templates, and wizards. See the Application Server Toolkit in the primary package for an integrated development environment that includes an unlimited use license. |
| DB2 Universal Database Express Edition V8.2 | Three different platform versions of this CD are available:
| IBM DB2 Universal Database Express Edition is the lowest-priced, full-function relational database. DB2 UDB Express Edition is designed to meet the needs of small and medium businesses. DB2 UDB Express Edition features self-tuning and self-configuring capabilities for ease of manageability, Linux or Windows platform choices, and support for transparent installation with business partner applications. This DB2 Express Edition is for use with WAS only. |
Packaging information for IBM WAS Network Deployment
| Disc label | Versions of the disc | Comments |
|---|---|---|
| WAS Network Deployment | Seven different platform versions of this CD are available:
| Each platform-specific CD contains the following installable components:
In addition, the Windows platform CD has the Data Direct JDBC drivers. Use the launchpad application in the root directory to install and view information about any of the installable components in the primary packet. |
| WAS Network Deployment Application Server Toolkit | One CD is available for each of the following platforms:
| The license for the Application Server Toolkit is an unlimited use license. |
Compact discs in the two supplemental packets
| Disc label | Versions of the disc | Comments |
|---|---|---|
| WAS Network Deployment
Edge Components | Seven different platform versions of this CD are available:
| Network Deployment addresses the needs of highly available, high-volume environments with the Edge components. |
| DB2 Universal Database Enterprise Server Edition for WAS Network Deployment | Nine different platform versions of this CD are available:
| DB2 Universal Database V8.2 has numerous innovative enhancements. Improved integration with WAS Network Deployment, key development tools, and platforms help make programmers more efficient than ever. A broad array of autonomic or self-managing capabilities can free more administrator time to focus on driving business value. The ease of use in DB2 V8.2 and the self-managing characteristics might even eliminate the need for dedicated administrators in smaller implementations. |
| Tivoli Directory Server for WAS | Seven different platform versions of this CD are available:
| The IBM Tivoli Directory Server product is a powerful LDAP infrastructure. Tivoli Directory Server provides a foundation for deploying comprehensive identity management applications and advanced software architectures. |
| Rational Application Developer Trial for WAS | Three CDs for each of two different platform versions are available:
| Rational Application Developer is the next generation of the award-winning IBM WebSphere Studio Application Developer. Rational Application Developer is a comprehensive integrated development environment for visually designing, constructing, testing, and deploying Web services, portals, and J2EE applications. Rational Application Developer accelerates J2EE development with a complete set of high-productivity tools, templates, and wizards. See the Application Server Toolkit in the primary package for an integrated development environment that includes an unlimited use license. |
| IBM Tivoli Access Manager Servers for WAS | Six different platform versions of this CD are available:
| IBM Tivoli Access Manager for e-business integrates with e-business applications right out of the box, to deliver a secure, unified, and personalized e-business experience. By providing authentication and authorization APIs and integration, Tivoli Access Manager for e-business helps you secure access to business-critical applications and data that might be spread across the extended enterprise. |
Roadmap for installing the base product
The launchpad gives you important clues about creating typical scenarios. The installation solution diagrams identify some of the system topologies that we can create. The launchpad is in the root directory of the product CD.
Use the launchpad to launch the installation program for each of the installable components in the primary disc packet. The launchpad also provides access to the documentation for each of the installable components on the product CD.
To start...
./launchpad.sh
Installing the base product to create a single stand-alone application server named server1. Use the Profile creation wizard to create multiple stand-alone application servers on the machine.
Roadmap for installing a stand-alone application server
The installation of the base product creates a stand-alone application server. You simply have to start the application server named server1 to begin using the server:
- Insert the product disc.
- Start the launchpad.
- Launch the installation program for the WAS product.
- Install the product
- Change directories to...
install_root/profiles/default/bin
- Start the application server named server1 with the startServer command:
./startServer.sh server1
Roadmap for creating multiple application servers on a single machine
Two different wizards create an application server:
- The Installation wizard creates one stand-alone application server profile.
- Each use of the Profile creation wizard also creates one stand-alone application server profile.
Install the base product again on the same machine is not necessary. Simply use the Profile creation wizard to create additional application server profiles. Each profile contains one server1 application server.
Each application server profile is a unique run-time environment, with its own configuration, applications, data, logs, and administrative interface. All of the application server instances on a machine share the same set of core product files.
For example, the following procedure shows the basic steps for creating two profiles on one machine:
- Insert and mount the product disc.
- Start the launchpad.
- Launch the installation program for the WAS product.
- Change directories to...
install_root/profiles/default/bin directory:
- Start the Application Server named server1 with the startServer command:
./startServer.sh server1
- Start the First steps console with the firststeps command:
cd install_root/firststeps ./firststeps.sh
- Select the Profile creation wizard option and create a new application server profile.
Give the new profile a unique name, such as Profile02.
- Change directories to...
install_root/profiles/Profile02/bin directory:
- Start the application server named server1 with the startServer command:
./startServer.sh server1
Understanding what we can do with the base product
Select the Installation solutions diagrams link in the navigation area on the launchpad to view typical topologies for the base product. The solutions are shadowed in Plan to install WAS. The topic describes the installation steps for each solution in detail.
What to do when an installation problem occurs
If you encounter a problem such as needing more space or missing the right prerequisite updates on your system, cancel the installation, make the required changes, and restart the installation. The installation procedure has a description of more comprehensive troubleshooting procedures.
Getting the latest information
The information center always has the most current information.
The Getting Started PDF is updated occasionally. Download a new Getting Started guide from wasv60base_gs.pdf.
What to do next
After installing the base product, the next step is to use the product. We can start the application server and use the administrative console to deploy an existing application.
Plan to install WAS
- Scenario 1: Single-machine installation of WAS
Installing WAS by itself on a single machine creates a stand-alone application server, which is automatically named server1. Install the base product creates the core product files and a profile for application server. The profile is a separate set of files that define the application server environment.
In this scenario, application server uses its internal HTTP transport chain for communication, which is suitable for handling an application with a relatively low request work load. For example, this type of installation can support a simple test environment or a departmental intranet environment.
- Scenario 2: Single-machine installation of WebSphere application servers and a Web server
Install a Web server, such as IBM HTTP Server, on the same machine as the application server provides a more robust Web server environment. Install a Web server plug-in is a requirement for the Web server to communicate with the application server. This type of installation supports rigorous testing environments or production environments that do not require a firewall. However, this is not a typical production environment.
- Install WAS.
- Install IBM HTTP Server or another supported Web server.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard.
- Scenario 3: Two-machine installation of WAS and a Web server
In the typical production environment, the application server on one machine communicates with a Web server on a separate (remote) machine through the Web server plug-in. Optional firewalls can provide additional security for the application server machine.
- Install WAS on Machine A.
- Install IBM HTTP Server or another supported Web server on Machine B.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard on Machine B.
- The Plug-ins installation wizard creates a script named configureWeb_servername in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the Application Server to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
- Scenario 4: Creating multiple profiles that use one installation of WAS
A profile is a separate data partition that contains the files that define the run-time environment for an application server. A default profile is created during the installation of the base product. Create additional profiles using the Profile creation wizard. Each profile defines a separate stand-alone application server that has its own administrative interface.
After creating a profile and installing a dedicated Web server, use the Plug-ins installation wizard to install a Web server plug-in and to update the Web server configuration file. The Web server can then communicate with the application server.
With topology, each profile has unique applications, configuration settings, data, and log files, and shares the same set of core product files. Creating multiple profiles creates multiple application server environments that we can dedicate to different purposes.
For example, each application server on a Web site can serve a different application. In another example, each application server can be a separate test environment that you assign to a programmer or to a development team.
Update the core product files
Another feature of having multiple profiles is enhanced serviceability. When a refresh pack or a fix pack updates the core product files on a machine, all of the application server profiles that were created from the core product files begin using the updated files. In some situations, you might prefer to not update all of the application servers on a machine. In such situations, simply install the product a second time to create a second set of core product files. Create application server profiles from both installations to manage the product updates incrementally.
- Install WAS on Machine A.
- Install IBM HTTP Server or another supported Web server on Machine B.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard on Machine B.
- The
Plug-ins installation wizard creates a script named
configureWeb_servername in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate
the plugin-cfg.xml file from the application server
to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
- Create the second Application Server profile using the Profile creation wizard on Machine A. Make the profile the default profile during the profile creation by selecting the check box on the appropriate panel.
The script that the Plug-ins installation wizard creates works on the default profile only. So, this script can only create a Web server definition on the profile that is the default profile at the time that the script runs.
- Install IBM HTTP Server or another supported Web server on Machine B.
- On Machine B, install the Web server plug-ins to configure the second Web server using the Plug-ins installation wizard. Both Web servers share a single installation of the plug-in binaries but must be configured individually.
- The Plug-ins installation wizard creates a script named configureWeb_servername for the second Web server. The script is in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the second application server to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
We can review common installation scenarios to find a possible match for the topology that you intend to install. Each product installation diagram provides a high-level procedure for installing the components that comprise the topology.
After determining a possible topology, you are ready to follow the detailed installation instructions for each product that you plan to install.
Plan to install WAS
This topic describes common installation scenarios and links to component installation procedures for each scenario.
IBM WebSphere Application Server, v6 is an integrated platform that contains an Application Server, a set of Web development tools, a Web server, and additional supporting software and documentation.
The following information describes scenarios for installing the product in various topologies on one or more machines:
- Scenario 1: Single-machine installation of WAS
- Scenario 2: Single-machine installation of WAS and a Web server
- Scenario 3: Two-machine installation of WAS and a Web server
- Scenario 4: Creating multiple profiles that use one installation of WAS
Each scenario includes a diagram and a list of detailed installation steps.
- Scenario 1: Single-machine installation of WAS
Install WAS by itself on a single machine creates a stand-alone application server, which is automatically named server1. Install the base product creates the core product files and a profile for application server. The profile is a separate set of files that define the application server environment.
In this scenario, application server uses its internal HTTP transport chain for communication, which is suitable cellpadding=10 for handling an application with a relatively low request work load. For example, this type of installation can support a simple test environment or a departmental intranet environment.
- Scenario 2: Single-machine installation of WebSphere application servers and a Web server
Install a Web server, such as IBM HTTP Server, on the same machine as the application server provides a more robust Web server environment. Install a Web server plug-in is a requirement for the Web server to communicate with the application server. This type of installation supports rigorous testing environments or production environments that do not require a firewall. However, this is not a typical production environment.
- Install WAS.
- Install IBM HTTP Server or another supported Web server.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard.
- Scenario 3: Two-machine installation of WAS and a Web server
In the typical production environment, the application server on one machine communicates with a Web server on a separate (remote) machine through the Web server plug-in. Optional firewalls can provide additional security for the application server machine.
- Install WAS on Machine A.
- Install IBM HTTP Server or another supported Web server on Machine B.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard on Machine B.
- The
Plug-ins installation wizard creates a script named
configureWeb_servername in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin directory
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the Application Server to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
- Scenario 4: Creating multiple profiles that use one
installation of WAS
A profile is a separate data partition that contains the files that define the run-time environment for an application server. A default profile is created during the installation of the base product. Create additional profiles using the Profile creation wizard. Each profile defines a separate stand-alone application server that has its own administrative interface.
After creating a profile and installing a dedicated Web server, use the Plug-ins installation wizard to install a Web server plug-in and to update the Web server configuration file. The Web server can then communicate with the application server.
With topology, each profile has unique applications, configuration settings, data, and log files, and shares the same set of core product files. Creating multiple profiles creates multiple application server environments that we can dedicate to different purposes.
For example, each application server on a Web site can serve a different application. In another example, each application server can be a separate test environment that you assign to a programmer or to a development team.
Updating the core product files
Another feature of having multiple profiles is enhanced serviceability. When a refresh pack or a fix pack updates the core product files on a machine, all of the application server profiles that were created from the core product files begin using the updated files. In some situations, you might prefer to not update all of the application servers on a machine. In such situations, simply install the product a second time to create a second set of core product files. Create application server profiles from both installations to manage the product updates incrementally.
- Install WAS on Machine A.
- Install IBM HTTP Server or another supported Web server on Machine B.
- Install the Web server plug-ins and configure the Web server using the Plug-ins installation wizard on Machine B.
- The
Plug-ins installation wizard creates a script named
configureWeb_servername in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the application server to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
- Create the second Application Server profile using the Profile creation wizard on Machine A. Make the profile the default profile during the profile creation by selecting the check box on the appropriate panel.
The script that the Plug-ins installation wizard creates works on the default profile only. So, this script can only create a Web server definition on the profile that is the default profile at the time that the script runs.
- Install IBM HTTP Server or another supported Web server on Machine B.
- On Machine B, install the Web server plug-ins to configure the second Web server using the Plug-ins installation wizard. Both Web servers share a single installation of the plug-in binaries but must be configured individually.
- The Plug-ins installation wizard creates a script named configureWeb_servername for the second Web server. The script is in...
plugins_install_root/bin
...on Machine B. Copy the script to...
install_root/bin directory
...on Machine A.
- Run the configureWeb_servername script to create a Web server definition in the administrative console. We can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the second application server to the Web server using the administrative console. Click...
Servers | Web server | Propagate Plug-in
Web servers other than IBM HTTP Server require manual propagation.
We can review common installation scenarios to find a possible match for the topology that you intend to install. Each product installation diagram provides a high-level procedure for installing the components that comprise the topology.
After determining a possible topology, you are ready to follow the detailed installation instructions for each product that you plan to install.
Prepare the operating system for product installation
- Prepare AIX systems for installation
- Prepare HP-UX systems for installation
- Prepare Linux systems for installation
- Prepare Solaris systems for installation
- Prepare Windows systems for installation
Help for installation wizard panels
Install the WAS v6 base with full installation options
This topic describes how to install IBM WAS, V6 with full installation options.
This path is one of the installation paths that are available for any platform.
Other installation paths include:
- Install the base product with custom options
- Install additional features on an existing base product
- Upgrade Express to the WAS product
- Upgrade the trial to the full product
- Install silently
Before starting the installation, see Use 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 Plan to install WAS in the Information center.
Perform the following installation to install all features for the base WAS product and to accept default characteristics for the application server profile.
- Log on as root.
- Verify that the umask setting is 022. To set the umask setting to 022, issue the following command:
umask 022
- Insert the product CD-ROM labeled WAS into the CD-ROM drive and mount the drive if necessary
- Start the installation with the launchpad.sh command on Linux and UNIX platforms
We can also start the installation using the install command:
/WAS/install
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.
After launching the Installation wizard from the launchpad or from the command line, the ISMP wizard initializes and then displays the Welcome panel.
- Click Next to continue.
The license agreement displays.
- Click the radio button beside the I accept the terms in the license agreement message to agree to the license agreement, then 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 IBM WAS 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.
If the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, perform a new installation to another directory, or perform an upgrade of a trial installation to the full product.
If a V6 product exists:
- See Install additional features on an existing base product for the installation scenario that adds features to an existing product.
- See Upgrade the trial to the full product for the installation scenario that upgrades a trial to the full Express product.
- See Upgrade Express to the WAS product for the installation scenario that upgrades a full Express product to the full base WAS product.
This scenario assumes that there is no existing V6 product on the machine.
The wizard displays a panel that prompts you for the location of the installation root directory for the product binaries.
- Specify a destination directory and click Next.
Specify the location of the installation root directory for the core product files, which are also known as the shared system files or the product binaries. 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 base product.
The following list shows default installation locations for supported platforms:
AIX /usr/IBM/WebSphere/AppServer Linux
HP-UX
Solaris/opt/IBM/WebSphere/AppServer Important: Do not use symbolic links as the destination directory. Symbolic links are not supported.
Spaces are not supported in the name of the installation directory.
Delete 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.
The wizard displays the Installation options panel. The panel lets you choose whether to do a full installation or a custom installation, which displays the Features selection panel to let you choose features to install. This procedure describes performing the full installation.
- Choose a type of installation and click Next.
Select Full installation to install all features. Choose this option to install everything we need to run Web applications on your server. Use this option if you are new to WAS and are unsure of what to install.
The wizard displays the pre-installation summary panel for you to review before installing the product.
- Review the summary information and click Next to install the product code or Back to change your specifications.
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 complete panel.
- Verify the success of the installer program by examining the completion panel and the log files for installation status.
If problems occur, consult the following applicable logs (copied from the troubleshooting section):
- install_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.
- install_root/logs/wasprofile/wasprofile_create_profile.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.
- install_root/logs/wasprofile/wasprofile_delete_profile.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.
- install_root/profiles/profile/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.
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 file...
install_root/logs/log.txt
...or the file...
install_root/logs/wasprofile/wasprofile_create_default.log
...does not contain a record of any problems, but problems exist.
Examine the Start menu entry. The menu is an indication of a successful installation:
- Programs | IBM WebSphere | Application Server V6
- All Programs | IBM WebSphere | Application Server V6
If problems exist that cause you to reinstall the product...
- Correct the errors
- Uninstall the product
- Reboot a Windows machine or log off and back on as root on a Linux or UNIX machine
- Reinstall.
- Click Finish to close the Installation wizard.
This procedure results in the Installation wizard installing WAS into the installation root directory. The Installation wizard creates a profile named default that provides the run-time environment for the server1 application server.
Further configuration is not necessary at this time. However, we can create additional stand-alone application servers with the Profile creation wizard. Each profile is created in...
install_root/profiles
Install the base product with custom options
- Install the base product with full installation options
- Install additional features on an existing base product
- Upgrade Express to the WAS product
- Upgrade the trial to the full product
- Install silently
Before starting the installation, see Use 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 Plan to install WAS in the Information center.
Perform the following installation to select features for the base WebSphere Application Server product and to select characteristics for the application server profile.
- Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Insert the product CD-ROM labeled WAS into the CD-ROM drive and mount the drive if necessary, as described in Mounting CD-ROMS on Linux and UNIX operating systems.
- Start the installation with the launchpad.sh command on Linux and UNIX platforms
We can also start the installation using the install command:
- Linux AIX, HP-UX, Solaris /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 ISMP wizard initializes and then displays the Welcome panel.
- Click Next to continue.
The license agreement displays.
- Click
the radio button beside the I accept the terms in the license agreement message to
agree to the license agreement, then 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 IBM WAS 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.
If the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, perform a new installation to another directory, or perform an upgrade of a trial installation to the full product.
If a V6 product exists see:
- Install additional features on an existing base product
- Upgrade the trial to the full product
- Upgrade Express to the WAS product
This scenario assumes that there is no existing V6 product on the machine.
The wizard displays a panel that prompts you for the location of the installation root directory for the product binaries.
- Specify
a destination directory and click
Next.
Specify the location of the installation root directory for the core product files, which are also known as the shared system files or the product binaries. 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 base product.
The following list shows default installation locations for supported platforms:
-
/usr/IBM/WebSphere/AppServer
-
Linux
/opt/IBM/WebSphere/AppServer
- C:\Program Files\IBM\WebSphere\AppServer
Linux AIX, HP-UX, Solaris Important: Do not use symbolic links as the destination directory. Symbolic links are not supported.
Spaces are not supported in the name of the installation directory.
Delete 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.
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 Installation options panel. The panel lets you choose whether to do a full installation or a custom installation, which displays the Features selection panel to let you choose features to install. This procedure describes performing the full installation.
-
- Choose a type of installation and click Next.
Select Custom installation to select features to install.
The wizard displays the Features selection panel.
- Select features to install and click Next.
Table 3. Features for the base product 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. Tuning performance
For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, we can improve application server startup time by 60 percent and save 15 percent of disk space. We can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).
- Verify
that the ports in the server that you are creating do not conflict with
existing ports.
Use the netstat -a command to display all ports in use. Programs and products must run to use ports. The netstat command only displays ports in use by active applications.
The Installation wizard displays the Node and host names panel.
- Specify
the node and host names for the application server and click
Next.
A good practice is to use unique names for each application server that you create. However, unique names are important only at the profile name level in the configuration directory.
Reserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Field name Default value Constraints Description Node name DefaultNode Avoid using reserved folder names.
Pick any name except for the reserved names. To help organize your installation, use a unique name if you plan to create more than one application server on the machine. However, a unique name for a stand-alone application server is not required. Host name DNS name of your machine See the following considerations for the host name field. Use the actual DNS name or IP address of your machine to enable communication with your machine. See additional information about the host name following this table. Node name considerations
The installation directory path must be no longer than 60 characters.
Host name considerations
The host name is the network name for the physical machine on which the node is installed. The host name must resolve to a physical network node on the server. When multiple network cards exist in the server, the host name or IP address must resolve to one of the network cards. Remote nodes use the host name to connect to and to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.
If you define coexisting nodes on the same computer with unique IP addresses, define each IP address in a domain name server (DNS) look-up table. Configuration files for stand-alone Application Servers do not provide domain name resolution for multiple IP addresses on a machine with a single network address.
The value that you specify for the host name is used as the value of the hostName property in configuration documents for the stand-alone Application Server. Specify the host name value in one of the following formats:
- Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com
- The default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the Application Server configuration. This value for host name is particularly useful if you plan to change the IP address frequently when using Dynamic Host Configuration Protocol (DHCP) to assign IP addresses. A format disadvantage is being dependent on DNS. If DNS is not available, then connectivity is compromised.
The short host name is also dynamically resolvable. A short name format has the added ability of being redefined in the local hosts file so that the system can run the Application Server even when disconnected from the network. Define the short name to 127.0.0.1 (local loopback) in the hosts file to run disconnected. A format disadvantage is being dependent on DNS for remote access. If DNS is not available, then connectivity is compromised.
A numeric IP address has the advantage of not requiring name resolution through DNS. A remote node can connect to the node you name with a numeric IP address without DNS being available. A format disadvantage is that the numeric IP address is fixed. You must change the setting of the hostName property in Express configuration documents whenever you change the machine IP address. Therefore, do not use a numeric IP address if you use DHCP, or if you change IP addresses regularly. Another format disadvantage is that you cannot use the node if the host is disconnected from the network.
After specifying application server characteristics, the wizard displays the Windows service definition panel, if you are installing on a Windows platform.
-
Choose whether to
run the application server as a Windows service on a Windows platform
and click Next.
V6 attempts to start Windows services for application server processes started by a startServer command. For example, if you configure an application server as a Windows service and issue the startServer command, the wasservice command attempts to start the defined service.
If you chose to install a local system service, you do not have to specify your user ID or password. If you create a specified user type of service, specify the user ID and the password for the user who is to run the service. The user must have Log on as a service authority for the service to run properly.
To perform this installation task, the user ID must not have spaces in its name. The ID must also belong to the administrator group and must have the advanced user rights Act as part of the operating system and Log on as a service. The Installation wizard grants the user ID the advanced user rights if it does not already have them, if the user ID belongs to the administrator group.
We can also create other Windows services after the installation is complete, to start other server processes.
The installation wizard shows which components are selected for installation in a pre-installation summary panel.
- Review
the summary information and click
Next to
install the product code or Back to change your specifications.
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 complete panel.
- Verify
the success of the installer program by examining the completion panel
and the log files for installation status.
If problems occur, consult the following applicable logs (copied from the troubleshooting section):
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...
install_root/logs/log.txt
...or...
install_root/logs/wasprofile/wasprofile_create_default.log
...does not contain a record of any problems, but problems exist.
See...
Examine the Start menu entry. The menu is an indication of a successful installation:
- Programs | IBM WebSphere | Application Server V6
- All Programs | IBM WebSphere | Application Server 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 Linux or UNIX machine, and reinstall.
- Click Finish to close the Installation wizard.
This procedure results in the Installation wizard installing WAS into the installation root directory. The Installation wizard creates a profile named default that provides the run-time environment for the server1 application server.
Further configuration is not necessary at this time. However, we can create additional stand-alone application servers with the Profile creation wizard. Each profile is created in...
install_root/profiles
...by default.
See Use the Profile creation wizard for more information.
Install additional features on an existing base product
This topic describes how to install additional features to an existing IBM WAS, V6 installation.
This path is one of the installation paths that are available for any platform.
- Install the base product with full installation options
- Install the base product with custom options
- Upgrade Express to the WAS product
- Upgrade the trial to the full product
- Install silently
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 Plan to install WAS in the Information center.
Perform the following installation to add features to an existing WAS installation.
- Log on as root on a Linux
or UNIX operating system, or as a member of the administrator group on a
Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 see the advanced options.
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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Insert the product CD-ROM labeled WAS into the CD-ROM drive and mount the drive if necessary.
- Start the installation with the launchpad.sh command
We can also start the installation using the install command:
- Linux AIX, HP-UX, Solaris /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 ISMP wizard initializes and then displays the Welcome panel.
- Click
Next to
continue.
The license agreement displays.
- Click
the radio button beside the I accept the terms in the license agreement message to
agree to the license agreement, then 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 IBM WAS 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 another directory. An incremental installation adds features to the shared binaries identified in the location field.
We can add uninstalled features at any time, by running the Installation wizard again. Install additional features does not affect profiles that you might have already created. (Profiles 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.
Table 5. Features for the base product Feature Description Core product files Installs the product binary code. Application Server Samples Installs the Sample applications. Javadoc Installs the API documentation of WAS classes. Tuning performance
For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, we can improve application server startup time by 60 percent and save 15 percent of disk space. We can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).
- 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 disk for the features that you selected.
Table 6. 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 files for installation status.
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...
install_root/logs/log.txt
...or...
install_root/logs/wasprofile/wasprofile_create_default.log
...does not contain a record of any problems, but problems exist.
See...
Examine the Start menu entry. The menu is an indication of a successful installation:
- Programs | IBM WebSphere | Application Server V6
- All Programs | IBM WebSphere | Application Server 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 Linux or UNIX machine, and reinstall.
- Click Finish to close the Installation wizard.
The Installation wizard installs the new features in the existing installation root directory. The Installation wizard configures the WAS product for the new features. Further configuration is not necessary at this time.
Further configuration is not necessary at this time. However, we can create additional stand-alone application servers with the Profile creation wizard. Each profile is created in...
install_root/profiles
...by default.
Deploy an application to get started!
See Fast paths for WAS to get started deploying applications.
Upgrading Express to the WAS product
This topic describes how to upgrade an Express installation of the base WAS product to the actual product.
This path is one of the installation paths that are available for any platform.
- Installing the base product with full installation options
- Installing the base product with custom options
- Installing additional features on an existing base product
- Upgrading the trial to the full product
- Installing silently
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 Plan to install WAS in the Information center.
Perform the following installation to upgrade an Express installation to the WAS product.
- Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.
- Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 see the advanced options.
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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Insert the product CD-ROM labeled WAS into the CD-ROM drive and mount the drive if necessary.
- Start the installation with the launchpad.sh command
We can also start the installation using the install command:
/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 ISMP wizard initializes and then displays the Welcome panel.
- Click Next to continue.
The license agreement displays.
- Click the radio button beside the I accept the terms in the license agreement message to agree to the license agreement, then 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 IBM WAS 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.
If the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, perform a new installation to another directory, or perform an upgrade of a trial installation to the full product.
This task describes the scenario where a previous installation of the Express product exists and you are installing the WAS product to upgrade the Express product.
Select the Upgrade option and click Next. The installer program installs the new license files and updates the system properties to indicate that the WAS product is installed.
The licensing agreement for the base product permits you to install the product on more than two machines, which is the legal limit for the Express product.
This procedure results in upgrading an Express installation to the actual WebSphere Application Server product.
We can install the base product again to add features. Or use the Profile creation wizard to create more stand-alone application servers.
Further configuration is not necessary at this time. However, we can create additional stand-alone application servers with the Profile creation wizard. Each profile is created in...
install_root/profiles
...by default.
See Using the Profile creation wizard 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 WAS to get started deploying applications.
Upgrading the trial to the full product
This topic describes how to upgrade a trial installation of the base WAS product to the actual product.
This path is one of the installation paths that are available for any platform.
- Installing the base product with full installation options
- Installing the base product with custom options
- Installing additional features on an existing base product
- Upgrading Express to the WAS product
- Installing silently
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 Plan to install WAS in the Information center.
Perform the following installation to upgrade a trial installation to the actual WAS product.
- Log on as root on a Linux
or UNIX operating system, or as a member of the administrator group on a
Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Insert the product CD-ROM labeled WAS into the CD-ROM drive and mount the drive if necessary.
- Start the installation with the launchpad.sh command
We can also start the installation using the install command:
- Linux AIX, HP-UX, Solaris /WAS/install
- \WAS\install
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 ISMP wizard initializes and then displays the Welcome panel.
- Click
Next to
continue.
The license agreement displays.
- Click
the radio button beside the I accept the terms in the license agreement message to
agree to the license agreement, then 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 IBM WAS 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.
If the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, perform a new installation to another directory, or perform an upgrade of a trial 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.
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.
We can install the base product again to add features. Or use the Profile creation wizard to create more stand-alone application servers.
Further configuration is not necessary at this time. However, we can create additional stand-alone application servers with the Profile creation wizard. Each profile is created in...
install_root/profiles
...by default.
See Using the Profile creation wizard 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 WAS to get started deploying applications.
Installing silently
This topic describes how to perform a silent installation of the product.
This is one of the installation paths available for any platform. Other installation paths include:
- Installing the base product with full installation options
- Installing the base product with custom options
- Installing additional features on an existing base product
- Upgrading the trial to the full product
- Upgrading Express to the WAS product
Select the appropriate installation path before you begin the installation.
Before starting the silent installation, see Using the launchpad to start the installation for information about the Installation solution diagrams. The diagrams show typical topologies for the product.
The solutions are also in Plan to install WAS.
Use this procedure to perform a silent installation of the WAS product.
A silent installation uses the Installation wizard to install the product in silent mode, without the graphical user interface. Instead of displaying a wizard interface, the silent installation causes the installation program to read all of your responses from a file that you provide.
- Log on as root on a Linux
or UNIX operating system, or as a member of the administrator group on a
Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 see the advanced options.
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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Copy the response file as myoptionsfile to your disk drive and customize it, as described in Customizing the base options response file.
The name of the original file is responsefile.base.txt.
- Issue
the proper command to use your custom response file. For example, issue
one of the following commands:
- Linux AIX, HP-UX, Solaris mnt_cdrom/WAS/install -options /tmp/WAS/myoptionsfile.txt -silent
- "CD_drive_D:\WAS\install" -options "C:\temp\WAS\myoptionsfile.txt" -silent
We can find the sample options response file in the WAS directory on the product CD.
The Installation wizard and the Profile creation wizard record installation events in the following log files:
Log more information when ISMP cannot start the Installation wizard.
Verify or troubleshoot the installation if...
install_root/logs/log.txt
...or...
profiles_install_root/profile/logs/pctLog.txt
...does not contain a record of any problems, but problems exist. If...
profiles_install_root/profile
...exists, the pctLog.txt file is in the logs directory. If the error happens early in the installation, look for the logs in the system temporary area. The installation program copies the logs from the system temporary area to the logs directory at the end of the installation.
If...
profiles_install_root/profile
...does not exist, the pctLog.txt file is in the USER_HOME directory and is named .$~pctLog.txt. Issue the env command to display the USER_HOME directory on Linux and UNIX systems. See the environment variable settings on Windows system to display the value of the variable.
Certain events can prevent ISMP from starting the Installation wizard. Such an event is not enough disk space to launch the Installation wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the ISMP program to fail to start the installation wizard. The syntax of the install command for logging such events is:
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALLThe following example is for AIX systems:
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALLThe following example is for Linux systems, HP-UX systems, and Solaris systems:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALLThe following example is for Windows systems:
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALLCustomizing the base options response file
This topic describes how to customize the response file for installing the WAS product from a command line without using the graphical user interface of the Installation wizard.
Before using the install -options myoptionsfile -silent command on a Linux or UNIX platform, or the install.exe -options myoptionsfile -silent command on a Windows platform to invoke a silent installation, customize the response file to add your selections.
Use the response file to supply values to the Installation wizard as the wizard runs in silent mode. The wizard does not display interactive panels when it runs in silent mode, but reads values from the response file instead.
Be precise when supplying values in the file: Customize the options response file precisely to let the installation program read the option values that the file contains. Incorrect specifications affect the silent interface of the Installation wizard. For example, always enclose values in double quotation marks.
If you customize the response file incorrectly, the Installation wizard cannot install the product with the -options or -silent parameters. If the error is an invalid option value, ISMP displays a warning message that confirm and stops the installation.
Compare your options response file to the responsefile.base.txt file that is shipped with the product to make the necessary corrections. After correcting the file, reinstall.
Guidance: The options response file has comments that describe each directive in the file. Read the explanations in the file to further understand the purpose of each directive.
See responsefile.base.txt for an example of the comments and directives in the response file.
Use the following description of options as a worksheet to plan your values.
-W silentInstallLicenseAcceptance.value="false" # -W detectedexistingcopypanelInstallWizardBean.choice="addFeatures" Platform specific: -P wasProductBean.installLocation="/usr/IBM/WebSphere/AppServer" Platform specific: -P wasProductBean.installLocation="/opt/IBM/WebSphere/AppServer" Platform specific: -P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer" # -W detectedexistingcopypanelInstallWizardBean.choice ="upgrade" # -W detectedexistingcopypanelInstallWizardBean.upgradeMatchInstallLocations = "BASE TRIAL OR EXPRESS INSTALL LOCATION" -W setuptypepanelInstallWizardBean.selectedSetupTypeId="Custom" -P samplesProductFeatureBean.active="true" -P javadocsProductFeatureBean.active="true" -W defaultprofileportspanelInstallWizardBean.WC_defaulthost="9080" -W defaultprofileportspanelInstallWizardBean.WC_adminhost="9060" -W defaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443" -W defaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043" -W defaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809" -W defaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8880" -W defaultprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401" -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403" -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402" -W defaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100" -W defaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353" -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276" -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_SECURE_ADDRESS="7286" -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558" -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578" -W nodehostandcellnamepanelInstallWizardBean.nodeName="nodeName" -W nodehostandcellnamepanelInstallWizardBean.hostName="hostName" Platform specific: -W winservicepanelInstallWizardBean.winServiceQuery="true" Platform specific: -W winservicepanelInstallWizardBean.accountType="localsystem" Platform specific: -W winservicepanelInstallWizardBean.startupType="manual" Platform specific: -W winservicepanelInstallWizardBean.userName="YOUR_USER_NAME" Platform specific: -W winservicepanelInstallWizardBean.password="YOUR_PASSWORD"- -W silentInstallLicenseAcceptance.value="false"
- Valid values are true or
false. You must accept the license agreement before you are allowed to
install the product.
Default value Description Your value false By changing the silentInstallLicenseAcceptance.value in this response file to "true", you agree that you have reviewed and agree to the terms of the IBM International Program License Agreement accompanying this program, which is located at CD_ROOT\WAS\lafiles. If you do not agree to these terms, do not change the value or otherwise download, install, copy, access, or use the program and promptly return the program and proof of entitlement to the party from whom you acquired it to obtain a refund of the amount you paid. Change the value to true to accept the license agreement and install the product. We cannot install the product with the default value.
- -W detectedexistingcopypanelInstallWizardBean.choice="addFeatures"
- The only valid value for
this directive is addFeatures. Leave the line commented if you are not
adding features to a previous installation.
Default value Description Your value Commented out Uncomment the line to add features to an existing installation in an incremental migration. Change the value of the following -P wasProductBean.installLocation= directive to the directory of the existing installation.
To avoid problems, set the feature active properties for currently installed features to false. To install a new feature, set the feature active property to true.
For example, suppose that you have an existing installation of the product with the Javadocs feature installed, but not the Samples feature. To install the Samples feature, set the following directives accordingly:
- -P samplesProductFeatureBean.active="true"
- -P javadocsProductFeatureBean.active="false"
The feature selection options are described after the installation type option.
- -P wasProductBean.installLocation=""
-
-
-P wasProductBean.installLocation=
"/usr/IBM/WebSphere/AppServer"
- Linux -P wasProductBean.installLocation="/opt/IBM/WebSphere/AppServer"
- -P wasProductBean.installLocation= "C:\Program Files\IBM\WebSphere\AppServer"
Default value Description Your value Varies per product disc The installation root directory for the product. Specify a valid directory unless you are upgrading. If you are upgrading, comment this directive. The default installation location is for a Windows system. Comment the Windows line to install on a Linux or UNIX operating system.
Uncomment the line that describes your platform and optionally change the location. The installation path must be 80 characters or less.
Linux AIX, HP-UX, Solaris Important: Do not use symbolic links as the destination directory. Symbolic links are not supported.
Spaces are also not supported in the name of the installation directory.
On a Windows system, the directory can contain spaces. Enclose a directory name with spaces within double quotation marks as shown in the Windows example.
The installation directory path must be no longer than 60 characters.
-
- -W detectedexistingcopypanelInstallWizardBean.choice ="upgrade"
- The only valid value is
upgrade.
Default value Description Your value Commented out Leave this directive commented if you do not have a trial or an Express installation that you intend to upgrade. Uncomment the line to upgrade the configuration and applications of a product trial installation to the actual WAS (base) product that you are installing.
We can also upgrade the Express product to the base product. (Upgrade the Express product, which is limited to installation on two machines, lets you install WAS on more than two machines.)
You must also use the next directive to specify the location of the existing trial or Express product.
- -W detectedexistingcopypanelInstallWizardBean.upgradeMatchInstallLocations = "BASE TRIAL OR EXPRESS INSTALL LOCATION"
- The only valid value is the absolute file path to the installation root directory of the trial base product or the Express product.
Default value Description Your value Commented out Leave this directive commented if you are not upgrading an existing trial or Express installation to the actual base product that you are installing. Uncomment the line to upgrade the product trial installation to the WAS (base) product. Replace the value "BASE TRIAL OR EXPRESS INSTALL LOCATION" with the installation root directory of the existing trial or the Express product.
During an upgrade, all other installation options are ignored. Only the upgrade occurs.
- -W setuptypepanelInstallWizardBean.selectedSetupTypeId="Custom"
- The only valid value is Custom.
Default value Description Your value Custom Do not change the value of this directive. A custom installation of the base product is required when using an options response file. A custom installation accepts values for all of the options that you have specified in the response file.
- -P samplesProductFeatureBean.active="true"
- Valid values are true or false.
Default value Description Your value true This option installs the Samples feature. Change the value to false to skip the installation of the Samples feature.
Change the value to false during an incremental installation if the Samples feature is already installed.
Do not use a value of true if the Samples feature is already installed.
- -P javadocsProductFeatureBean.active="true"
- Valid values are true or
false.
Default value Description Your value true This option installs the Javadocs feature. Change the value to false to skip the installation of the Javadocs feature.
Change the value to false during an incremental installation if the Javadocs feature is already installed.
Do not use a value of true if the Javadocs feature is already installed.
- -W defaultprofileportspanelInstallWizardBean.WC_*=*
- The following port
assignment directives use default values. It is your responsibility to
specify values that are not in conflict with other ports in use on your
operating system. Use the netstat -a command to display ports in use on your
system. The resulting display shows ports in use at the current time. If
applications or products are not running, the ports that they use do not
appear in the list.
Default port assignments are shown in the following list:
- -W defaultprofileportspanelInstallWizardBean.WC_defaulthost="9080"
- -W defaultprofileportspanelInstallWizardBean.WC_adminhost="9060"
- -W defaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443"
- -W defaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043"
- -W defaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809"
- -W defaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8880"
- -W defaultprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401"
- -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403"
- -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402"
- -W defaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100"
- -W defaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353"
- -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276"
- -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_SECURE_ADDRESS="7286"
- -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558"
- -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578"
Default value Description Your value WC_defaulthost="9080" Virtual host named defaulthost. This virtual host serves Samples and the default application, including the snoop servlet. WC_adminhost="9060" Virtual host named adminhost. This virtual host serves the administrative console application. WC_defaulthost_secure="9443" Secure port assignment for the defaulthost. WC_adminhost_secure="9043" Secure port assignment for the adminhost. BOOTSTRAP_ADDRESS="2809" These port assignments do not normally change unless they are already in use on your system. All port assignments must be unique on a machine to avoid conflicts with other products and applications on your machine. Other installations of WAS can use conflicting port assignments.
Multiple profiles (V6 Application Servers) on the machine must each have unique port assignments.
SOAP_CONNECTOR_ADDRESS="8880" SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401" CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403" CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402" ORB_LISTENER_ADDRESS="9100" DCS_UNICAST_ADDRESS="9353" SIB_ENDPOINT_ADDRESS="7276" SIB_ENDPOINT_SECURE_ADDRESS="7286" SIB_MQ_ENDPOINT_ADDRESS="5558" SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578" - -W nodehostandcellnamepanelInstallWizardBean.nodeName="nodeName"
- Replace nodeName with a
valid and meaningful name for your system. WAS
configuration files use the value as a folder name in the configuration
and also within certain XML configuration files.
Reserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Default value Description Your value nodeName The nodeName value is not a variable. The Installation wizard supplies a value of the short DNS form of the machine name when you use the graphical interface without a response file. Comment this line to accept the default value. We can change the value to any unique value other than the reserved words. The node name is used in the administration of the WAS product.
- -W nodehostandcellnamepanelInstallWizardBean.hostName="hostName"
- Replace hostName with the
actual host name of your machine in long or short DNS format. We can
also specify the IP address.
Default value Description Your value hostName The hostName value is not a variable. The Installation wizard replaces the value with the short local host name when you use the graphical interface without a response file. Every Application Server environment in WAS products must be addressable through a host name on a network file system. See Using the Profile creation wizard for more information about the field.
The maximum length of the host name is 15 characters.
- -W winservicepanelInstallWizardBean.winServiceQuery="true"
- Valid values are true or
false.
Default value Description Your value true A true value creates a Windows service that starts or stops the Application Server that is named server1. A value of false skips the creation of the Windows service. When you create a Windows service, WAS attempts to start the Windows service whenever you start or stop the server that the service controls. This attempt to start or stop the service occurs even though you might select a startup type of manual.
The name of the service is the node name, which is DefaultNode.
- -W winservicepanelInstallWizardBean.accountType="localsystem"
- Valid values are
localsystem or specifieduser. The user account must belong to the
administrator user group and have the advanced user rights
Act as part of
the operating system and Log on as a service.
Default value Description Your value localsystem You can install the service on the local system account or on the specified user account that you identify. - -W winservicepanelInstallWizardBean.startupType="manual"
- Valid values are
- automatic
- Indicates that you choose to let Windows start the server1 process whenever there is an abnormal stop or whenever Windows is rebooted.
- manual
- Indicates that you choose to start the service manually and do not intend to let Windows restart the service for you.
- disabled
- Indicates that the service is disabled and cannot start.
Default value Description Your value manual You can start the service automatically or manually or disable the service. When you create a Windows service, WAS attempts to start the Windows service whenever you start or stop the server that the service controls. This attempt to start or stop the service occurs even though you might select a startup type of manual.
No attempt is made to start or stop a disabled Windows service.
- -W winservicepanelInstallWizardBean.userName="YOUR_USER_NAME"
- Valid values are your user
account that belongs to the administrator user group.
Default value Description Your value YOUR_ USER_NAME You must specify your user account. The user account must belong to the administrator user group and have the advanced user rights Act as part of the operating system and Log on as a service.
- -W winservicepanelInstallWizardBean.password="YOUR_PASSWORD"
- The only valid value is
the password for your user account.
Default value Description Your value YOUR_ PASSWORD You must specify your password if you have password protection enabled on the Windows operating system. The password is not recorded in a file other than this one. After installing the product, edit the response file and remove the password.
Perform the following procedure to edit the response file.
- Locate the sample options response file. The file is named responsefile.base.txt in the WAS directory on the product CD-ROM.
- Copy the file to preserve it in its original form. For example, copy it as myoptions on your disk drive.
- Edit the copy in your flat file editor of choice, on the target operating system. Read the directions within the response file to choose appropriate values. Important: To prepare the file for a silent installation on AIX, use UNIX line-end characters (0x0D0A) to terminate each line of the options response file. The safest method of preparing the file is to edit the file on the target operating system.
- Include
custom option responses that reflect parameters for your system.
Read the directions within the response file to choose appropriate values.
- Save the file.
- Log
on as root on a Linux or UNIX operating system, or as a member of the
administrator group on a Windows system.
Linux AIX, HP-UX, Solaris In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
Some steps of the installation on a Windows platform require the administrator group user to have 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 see the advanced options.
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, restart the system to activate the proper authorizations for the user ID before we can perform a successful silent installation.
When installing the WAS 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.
- Use your custom response file...
mnt_cdrom/WAS/install -options /tmp/WAS/myoptionsfile.txt -silent
We can find the sample options response file in the WAS directory on the product CD.
This procedure results in creating a customized response file and using the file to start a silent installation.
Edit the version of the file that ships with the WAS product. The example in responsefile.base.txt is not guaranteed to be an accurate representation of what ships with the product.
responsefile.base.txt
This topic describes the response file for installing the base WAS product.
Install the product with an options response file after logging on as root on a Linux or UNIX platform, or after logging on as a user that belongs to the administrator group on a Windows platform. Some steps of the installation procedure on a Windows platform require the administrator group user to have the advanced user rights Act as part of the operating system and Log on as a service.
Location of the response file
The sample options response file is named responsefile.base.txt. The file is in the WAS directory on the product disc or in the downloaded installation image.
Mode of use
The installation wizard can read an existing options response file and run silently without displaying the graphical user interface.
Installing silently
Use the options file to run the Installation wizard in silent mode, which is referred to as installing silently or as a silent installation. The wizard reads the options file to determine responses and does not display the graphical user interface. Use the following command to use a copy of the options file named myresponsefile.txt for a silent installation:
install -options "myresponsefile.txt" -silent
Logging
Information that ISMP can log when it cannot start the Installation wizard
Verify or troubleshoot the installation if...
install_root/logs/log.txt
...or...
profiles_install_root/profile/logs/pctLog.txt
...does not contain a record of any problems, but problems exist. If...
profiles_install_root/profile
...exists, the pctLog.txt file is in the logs directory. If the error happens early in the installation, look for the logs in the system temporary area. The installation program copies the logs from the system temporary area to the logs directory at the end of the installation.
If...
profiles_install_root/profile
...does not exist, the pctLog.txt file is in the USER_HOME directory and is named .$~pctLog.txt. Issue the env command to display the USER_HOME directory on Linux and UNIX systems. See the environment variable settings on Windows system to display the value of the variable.
Certain events can prevent ISMP from starting the Installation wizard. Such an event is not enough disk space to launch the Installation wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the ISMP program to fail to start the installation wizard. The syntax of the install command for logging such events is:
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALL
The following example is for AIX systems:
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALL
The following example is for Linux systems, HP-UX systems, and Solaris systems:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALL
The following example is for Windows systems:
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
See...
Usage notes
- The file is not a read-only file.
- Edit this file directly with your flat file editor of choice, such as WordPad on a Windows platform.
- The file must exist to perform a silent installation. The installation program reads this file to determine installation option values when you install silently.
- Save the file in a location that we can identify when you specify the fully qualified path as part of the installation command.
- If you are installing on a Windows platform, your user ID must belong to the administrator group and must have the advanced rights Act as part of the operating system and Log on as a service. If you select the following option when your user ID does not comply, the installation fails:
-W winservicepanelInstallWizardBean.winServiceQuery="true"
-
The installation directory path must be no longer than 60 characters.
- Avoid using reserved folder names when providing values for the following directives:
-P wasProductBean.installLocation
-W nodehostandcellnamepanelInstallWizardBean.nodeName
-W setcellnameinglobalconstantsInstallWizardBean.valueReserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Example responsefile.base.txt file
Edit the version of the file that ships with the WAS product. The following example is not guaranteed to be an accurate representation of the file that ships with the product.
################################################################################ # # InstallShield Options File # # Wizard name: Install # Wizard source: setup.jar # # This file can be used to configure Install with the options specified below # when the wizard is run with the "-options" command line option. Read each # setting's documentation for information on how to change its value. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the # wizard in graphical or console mode. To use this options file for silent mode # execution, use the following command line arguments when running the wizard: # # -options "D:\installImage\WAS\responsefile.base.txt" -silent # ################################################################################ ################################################################################### # # License Acceptance # # Valid Options : true Accepts the license. Will install the product. # false Declines the license. Install will not occur. # # If no install occurs, this will be logged to a temporary log file in the user's # temporary directory. # # By changing the silentInstallLicenseAcceptance.value in this response file to "true", # you agree that you # have reviewed and agree to the terms of the IBM International Program License # Agreement accompanying this # program, which is located at CD_ROOT\WAS\lafiles. If you do not agree to these terms, # do not change # the value or otherwise download, install, copy, access, or use the program and # promptly return the # program and proof of entitlement to the party from whom you acquired it to obtain a # refund of the amount you paid. # # -W silentInstallLicenseAcceptance.value="false" ################################################################################ # # Incremental Install # # If you are installing additional features on top of an existing installation, # (e.g. incremental install), uncomment the following line. This will notify # the installer that you are doing an incremental install. # # -W detectedexistingcopypanelInstallWizardBean.choice="addFeatures" # # Please make sure installLocation is set to your existing install location. # # For already installed features, we need to set the feature active property # to false. For new features you want to install, we need to set the active # properties to true. # # For example, you have installed core product feature, now you want to install # samples feature, the active properties should be: # # -P samplesProductFeatureBean.active="true" # -P javadocsProductFeatureBean.active="false" ################################################################################ # # IBM WAS, V6.0 Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes as shown in the Windows example below. Note that spaces in the # install location is only supported on Windows operating systems. # # Below is the list of default install locations for each supported operating # system. By default, in this response file, the Windows install location is # used. If you want to use the default install location for another operating # system, uncomment the appropriate default install location entry (by removing '#') and # then comment out (by adding '#') the Windows operating system entry below. # # # AIX Default Install Location: # # -P wasProductBean.installLocation=/usr/IBM/WebSphere/AppServer # # # HP-UX, Solaris or Linux Default Install Location: # # -P wasProductBean.installLocation=/opt/IBM/WebSphere/AppServer # # # Windows Default Install Location: # -P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer" ################################################################################ # # IBM WAS - Base, V6.0 UPGRADE from Base Trial or Express # # NOTE - : DO NOT Set this Option if you do not have any Base Trial or Express installed # We can not do an upgrade if you do not have at least one Base Trial or # Express installed # # # To setup an upgrade install, uncomment the following entry # (do not change the "upgrade" value ) # #-W detectedexistingcopypanelInstallWizardBean.choice="upgrade" # # # Additionally, specify the installation location where the Base Trial or Express # (which you want to upgrade) # is installed, by uncommenting the following entry and by replacing # "BASE TRIAL OR EXPRESS INSTALL LOCATION" with the # actual installation directory # #-W detectedexistingcopypanelInstallWizardBean.upgradeMatchInstallLocations= # "BASE TRIAL OR EXPRESS INSTALL LOCATION" # # # # NOTE - : In an Upgrade the following entries will be skipped and only an upgrade of the specified Base Trial or Express # to Base will occur # ################################################################################ # # Setup type # # This value is required for the installation. Do not change this! # -W setuptypepanelInstallWizardBean.selectedSetupTypeId="Custom" ################################################################################ # # "Core Product Files" feature # # This feature is required by Application Server and will be installed by default. # Selection is not required. # ################################################################################ # # "Application Server samples" feature # # The selection state of the "Application Server samples" feature. Legal values # are: # # true - Indicates that the feature is selected for installation # false - Indicates that the feature is not selected for installation # # For example, to select "Application Server samples" for installation, use # # -P samplesProductFeatureBean.active="true" # # -P samplesProductFeatureBean.active="true" ################################################################################ # # "Javadocs" feature # # The selection state of the "Javadocs" feature. Legal values are: # # true - Indicates that the feature is selected for installation # false - Indicates that the feature is not selected for installation # # For example, to select "Javadocs" for installation, use # # -P javadocsProductFeatureBean.active="true" # -P javadocsProductFeatureBean.active="true" ################################################################################ # # Port value assignment # # The following entries are used to reset port numbers used in the configuration # # They are currently set to the defaults. # Please check to make sure there are no Port Conflicts # -W defaultprofileportspanelInstallWizardBean.WC_defaulthost="9080" -W defaultprofileportspanelInstallWizardBean.WC_adminhost="9060" -W defaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443" -W defaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043" -W defaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809" -W defaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8880" -W defaultprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401" -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403" -W defaultprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402" -W defaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100" -W defaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353" -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276" -W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_SECURE_ADDRESS="7286" -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558" -W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578" ################################################################################ # # Node name # # Please select the node name for the Application Server. Node name under one cell # has to be unique. # # Replace YOUR_NODE_NAME with the actual node name. # -W nodehostandcellnamepanelInstallWizardBean.nodeName="YOUR_NODE_NAME" ################################################################################ # # Host name # # Specify the host name for the Application Server. The host name is the domain # name system (DNS) name (short or long) or the IP address of this computer. # # Replace YOUR_HOST_NAME with the actual host name. Comment the line to use # the default value. # -W nodehostandcellnamepanelInstallWizardBean.hostName="YOUR_HOST_NAME" ################################################################################ # # Cell name # # You should not Modify this, unless absolutely necessary. # # The Wizard would set this to short local host name + "Node##Cell" by default. # # If you would like to override the resolved cell name value, uncomment the line and # replace YOUR_CELL_NAME with <YOUR_OWN_VALUE>. # # -W setcellnameinglobalconstantsInstallWizardBean.value="YOUR_CELL_NAME" ################################################################################ # # Run WAS as a Windows service # (Windows ONLY) # # The selection state of the service installation. Legal values are: # # true - Indicates that you choose to install the service # false - Indicates that you not choose to install the service # -W winservicepanelInstallWizardBean.winServiceQuery="true" # Specify account type of the service. Legal values are: # # localsystem - Indicates that you choose to use Local System account. # specifieduser - Indicates that you choose to use specified user account. # -W winservicepanelInstallWizardBean.accountType="localsystem" # Specify startup type of the service. Legal values are: # # automatic - Indicates that you choose to use automatic startup type # manual - Indicates that you choose to use manual startup type # disabled - Indicates that you choose to use disabled startup type # -W winservicepanelInstallWizardBean.startupType="manual" # Specify your user name and password. Your user name # must belong to the administrator group to be authorized # to install a Windows service. Your user name must have # the "Log On as a Service" user right for the service to run properly. # # Replace YOUR_USER_NAME with your username. # Replace YOUR_PASSWORD with your valid password. -W winservicepanelInstallWizardBean.userName="YOUR_USER_NAME" -W winservicepanelInstallWizardBean.password="YOUR_PASSWORD" ################################################################################Configure the product after installation
This topic summarizes how to configure the application serving environment.
Use the First steps console to configure and test the WAS environment after installation.
This procedure uses the First steps console to launch the installation verification test (IVT) that tests and verifies your WAS environment. This procedure also uses the First steps console to launch the Profile creation wizard to create an additional Application Server.
- Start the First
steps console by selecting the check box on the last panel of the
wizard.
The First steps console can start automatically at the end of the installation. Select the check box on the last panel of the Installation wizard.
The First steps console access to...
- administrative console
- Samples Gallery
- Profile creation wizard
- installation verification test
- Migration wizard
- Click Installation verification on the First steps console.
The installation verification test starts the Application Server process named server1 and runs several tests to verify that the server1 process can start without errors.
- Click Profile creation wizard on the First steps console to create an Application Server profile.
We can create multiple Application Servers on the system without installing the product again.
- Start the First steps console by selecting the check box on the last panel of the Profile creation wizard.
This First steps console belongs to the Application Server profile that you just created. Each profile has its own First steps console.
- Click Installation verification on the First steps console.
The installation verification test starts the new Application Server process named server1 and runs several tests to verify that the server1 process can start without error.
This procedure results in configuring and testing the Application Server environment.
firststeps command
The firststeps command starts the First steps console.
The First steps console
The First steps console is a post-installation ease-of-use tool for directing WAS elements from one place. Options display dynamically on the First steps console, depending on features you install. With all of the options present, use the First steps console to start or stop the application server, verify the installation, access the information center, access the administrative console, launch the Migration wizard, or access the Samples gallery.
Select the check box to start the First steps console at the end of the product installation.
We can also start the First steps console from the command line as described later.
- Installation verification
- This option starts the installation verification test (IVT). The test consists of starting and monitoring the application server during its start up.
If this is the first time that you have used the First steps console since creating an application server profile, click Installation verification to verify that all is well with your installation. The verification process starts the application server.
If you select the Installation verification option, the Start the server option is grayed out while the IVT is running.
The IVT provides the following useful information about the application server:
- The server name: server1
- The name of the profile
- The profile file path
- The type of profile: default
- The cell name
- The node name
- The current encoding
- The port number for the administrative console
- Various informational messages that include the location of the SystemOut.log file and how many errors are listed within the file
- A completion message
- Start the server
- This option toggles to
Stop the
server when the application server is running.
After selecting the Start the server option, an output screen displays with status messages. The success message informs you that the server is open for e-business. Then the menu item changes to Stop the server.
If you select the Start the server option, the Installation verification option is grayed out while the application server is running.
- Administrative console
- This option is grayed
out until the application server is running.
The administrative console is a configuration editor that runs in a Web browser. The administrative console lets you work with XML configuration files for the application server. To launch the administrative console, click Administrative console. We can also point your browser to http://localhost:9060/ibm/console to start the administrative console. Substitute your own host name in the address if the localhost variable does not resolve correctly. As the administrative console opens, it prompts you for a login name. This is not a security item, but merely a tag to identify configuration changes that you make during the session. Secure signon is also available.
- Profile creation wizard
- This option starts the
Profile creation wizard. The wizard lets you create additional
application servers. A profile consists of files that define the run-time
environment for the application server. Each environment has its own
administrative interface. This means that the new application server has
its own administrative console.
Each application server has its own First steps console. The location of the command is within the set of files in the profile. A prompt to launch the First steps console displays on the last panel of the Profile creation wizard.
- Samples gallery
- This option starts the
Samples gallery. The option is grayed out until you start the
application server. The option displays when you have installed the
Samples during installation. The typical installation includes the
Samples by default.
From the First steps console, click Samples gallery to explore the application Samples. Alternatively we can point your browser directly to http://localhost:9080/WSsamples. Substitute your own host name in the address if the localhost variable does not resolve correctly. The Web address is case sensitive. Substitute your own host name in the address.
- Information center for WAS
- This option links you to the online information center at the http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp IBM Web address.
- Migration wizard
- This option starts the Migration wizard. The Migration wizard is a new graphical interface to the migration tools. The migration tools are described in WASPreUpgrade command and in WASPostUpgrade command.
- Exit
- This option closes the First steps console.
Location of the command file
Install the product creates a default profile for the server1 application server. The location of the First steps console for the default profile is:
install_root/profiles/default/firststeps/firststeps.sh
The location of the firststeps.sh is
install_root/profiles/profile/firststeps/firststeps.sh
Parameters
No parameters are associated with this command.
Syntax for the firststeps command
Use the following syntax for the command:
./firststeps.sh
Usage tips
The following links exist on the First steps console for the base WAS product:
Option Link Installation verification Calls the ivt command. The location of the installation verification test varies per platform:
install_root/profiles/profile/bin/ivt.sh
Start the server Calls the startServer command. The location of the startServer command varies per platform:
install_root/profiles/profile/bin/startServer.sh server1
When you have more than one application server on the same machine, the command starts the same application server that is associated with the First steps console.
Stop the server Calls the stopServer command. The location of the stopServer command varies per platform:
install_root/profiles/profile/bin/stopServer.sh server1
Administrative console Opens the default browser to the http://localhost:9060/ibm/console Web address. When you have more than one application server on the same machine, the port varies. The First steps console starts the administrative console that is associated with the First steps console.
Profile creation wizard Calls the pctplatform command. The command is in...
install_root/bin/ProfileCreator
The name of the command varies per platform:
-
pctAIX.bin
-
pctHPUX.bin
-
64-bit platforms: pctHPUXIA64.bin
- Linux pctLinux.bin
- Linux 64-bit platforms: pct.bin S/390 platforms: pctLinux390.bin
- Linux Power platforms: pctLinuxPPC.bin
-
pctSolaris.bin
- pctWindows.exe
- 64-bit platforms: pctWindowsIA64.exe
Samples Gallery Opens the default browser to the http://localhost:9080/WSsamples Web address. If you do not install Samples, the option does not appear on the First steps console. If you do not install the Samples during the initial installation of the product, the option does not display on the First steps console. We can perform an incremental installation to add the Samples feature. After adding the Samples, the options displays on the First steps console.
When you have more than one profile on the same machine, the port varies. The First steps console starts the Samples gallery that is associated with the First steps console.
Information center for WAS products Opens the default browser to the online information center at the http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp Web address. Migration wizard Calls the migration command. The location of the migration command is:
install_root/bin/migration.sh
The migration tools are also in the /migration folder on the product disc.
Use the Profile creation wizard
This topic describes how to create run-time environments for WAS. Each run-time environment is created within a profile. A profile is the set of files that define the run-time environment. The Profile creation wizard creates the profile for each run-time environment.
Before using the Profile creation wizard, install the core product files.
The Profile creation wizard is the wizard interface to the profile creation tool, wasprofile. See the description of the wasprofile command for more information.
An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
You must have 200 MB of available disk space in the directory where you create an Application Server profile.
Manually verify that the required space for creating a profile
is available on AIX. A known problem in the underlying
ISMP code prevents proper space checking on AIX systems
at the time that the product disc was created.
Important: Concurrent profile creation is not supported at this time for one set of core product files. Concurrent attempts to create profiles result in a warning about a profile creation already in progress.
The installation procedure creates one profile named default for an application server named server1. Use the Profile creation wizard to create more application server processes. For example, a second profile can allow two different teams in a department to test independently of one another using the same machine.
Each use of the Profile creation wizard or the wasprofile command line tool creates one profile.
- Install the product to create the core product files.
- Start
the Profile creation wizard to create a new run-time environment.
Several ways exist to start the wizard.
One way to start the wizard is to issue the command directly from a command line.
The command is in...
install_root/bin/ProfileCreator
The name of the command varies per platform:-
pctAIX.bin
-
pctHPUX.bin
-
64-bit platforms: pctHPUXIA64.bin
- Linux pctLinux.bin
- Linux 64-bit platforms: pct.bin S/390 platforms: pctLinux390.bin
- Linux Power platforms: pctLinuxPPC.bin
-
pctSolaris.bin
- pctWindows.exe
- 64-bit platforms: pctWindowsIA64.exe
Another way to start the Profile creation wizard is to select the wizard from the First steps console.
- Open a command window.
- Change
directories to the firststeps directory in the installation root
directory:
The installation root varies by platform:
-
/usr/IBM/WebSphere/AppServer/firststeps
-
Linux
/opt/IBM/WebSphere/AppServer/firststeps
- C:\Program Files\IBM\WebSphere\AppServer\firststeps
-
- Issue the firststeps command to start the console:
./firststeps.sh
- Select the Profile creation wizard option on the console.
The Profile creation wizard is an InstallShield for Multiplatforms application. The wizard loads the Java 2 SDK and then displays its Welcome panel.
-
- Create another stand-alone application server.
The installation procedure creates a stand-alone application server during installation. However, use the Profile creation wizard to create additional stand-alone application servers.
Using the Profile creation wizard to create an application server
The Profile creation wizard can create an application server profile on any machine where the core product files exist.
Before using the Profile creation wizard, install the core product files.
The Profile creation wizard is the wizard interface to the profile creation tool, wasprofile. See the description of the wasprofile command for more information.
An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
You must have 200 MB of available disk space in the directory where you create an Application Server profile.
Manually verify that the required space for creating a profile is available on AIX. A known problem in the underlying ISMP code prevents proper space checking on AIX systems at the time that the product disc was created.
The Installation wizard creates an application server profile with a server named server1. We can create additional profiles. Each additional profile is an application server named server1.
This procedure describes creating an application server profile using the graphical user interface provided by the Profile creation wizard.
We can also use the wasprofile command to create an application server profile.
- Start the Profile creation
wizard to create a new run-time environment.
Several ways exist to start the wizard.
One way to start the wizard is to issue the command directly from a command line.
The command is in...
install_root/bin/ProfileCreator
The name of the command varies per platform:
-
pctAIX.bin
-
pctHPUX.bin
-
64-bit platforms: pctHPUXIA64.bin
- Linux pctLinux.bin
- Linux 64-bit platforms: pct.bin S/390 platforms: pctLinux390.bin
- Linux Power platforms: pctLinuxPPC.bin
-
pctSolaris.bin
- pctWindows.exe
- 64-bit platforms: pctWindowsIA64.exe
Another way to start the Profile creation wizard is to select the wizard from the First steps console.
- Open a command window.
- Change
directories to the firststeps directory in the installation root
directory:
The installation root varies by platform:
-
/usr/IBM/WebSphere/AppServer/firststeps
-
Linux
/opt/IBM/WebSphere/AppServer/firststeps
- C:\Program Files\IBM\WebSphere\AppServer\firststeps
-
- Issue
the firststeps command to start the console:
./firststeps.sh
- Select the Profile creation wizard option on the console.
The Profile creation wizard is an InstallShield for Multiplatforms application. The wizard loads the Java 2 SDK and then displays its Welcome panel.
See the description of the firststeps command for more information.
-
- Click Next on the Welcome panel.
The wizard displays the Profile type selection panel.
- Click
Next.
The wizard displays the Profile name panel.
Each profile that you create must have a name. The name is the name of the folder that contains all of the files that define the run-time environment for the profile. When you have more than one profile, we can tell them apart at their highest level by this name.
- Specify
a name for the profile, then click
Next.
Profile naming guidelines: The profile name can be any unique name with the following restrictions. Do not use any of the following characters when naming your profile:
- Spaces
- Illegal special characters that are not allowed within the name of a directory on your operating system, such as *&?
- Slashes (/) or (\)
Double-byte characters are allowed.
The default profile
The first profile that you create on a machine is the default profile. The default profile is the default target for commands issued from the bin directory in the product installation root. When only one profile exists on a machine, every command works on the only server process in the configuration.
Addressing a profile in a multi-profile environment
When two or more profiles exist on a machine, certain commands require that you specify the profile to which the command applies. These commands use the -profileName parameter to identify which profile to address. You might find it easier to use the commands that in the bin directory of each profile.
A command in the profiles/profile/bin directory has two lines. The first line sets the WAS_USER_SCRIPT environment variable for the command window. The variable sets up the command environment to address the profile. The second line calls the actual command in...
install_root/bin
The actual command queries the command shell to determine the calling profile and to autonomically address the command to the calling profile.
The wizard then displays the Profile directory panel.
- Accept
the default directory or specify a non-default location, then click
Next. Or click
Browse to select a different location.
If you click Back and change the name of the profile, manually change the name on this panel when it displays again.
The wizard displays the Node and host name panel.
- Specify
the characteristics for the application server, then click
Next.
Use unique names for each application server that you create.
Reserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Field name Default value Constraints Description Node name Name of your machine Avoid using the reserved words. Pick any name you want. To help organize your installation, use a unique name if you plan to create more than one application server on the machine. Host name DNS name of your machine Addressable through your network. Use the actual DNS name or IP address of your machine to enable communication with your machine. See additional information about the host name following this table. Node name considerations:
The installation directory path must be no longer than 60 characters.
The host name is the network name for the physical machine on which the node is installed. The host name must resolve to a physical network node on the server. When multiple network cards exist in the server, the host name or IP address must resolve to one of the network cards. Remote nodes use the host name to connect to and to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.
If you define coexisting nodes on the same computer with unique IP addresses, define each IP address in a domain name server (DNS) look-up table. Configuration files for stand-alone Application Servers do not provide domain name resolution for multiple IP addresses on a machine with a single network address.
The value that you specify for the host name is used as the value of the hostName property in configuration documents for the stand-alone Application Server. Specify the host name value in one of the following formats:
- Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com
- The default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the Application Server configuration. This value for host name is particularly useful if you plan to change the IP address frequently when using Dynamic Host Configuration Protocol (DHCP) to assign IP addresses. A format disadvantage is being dependent on DNS. If DNS is not available, then connectivity is compromised.
The short host name is also dynamically resolvable. A short name format has the added ability of being redefined in the local hosts file so that the system can run the Application Server even when disconnected from the network. Define the short name to 127.0.0.1 (local loopback) in the hosts file to run disconnected. A format disadvantage is being dependent on DNS for remote access. If DNS is not available, then connectivity is compromised.
A numeric IP address has the advantage of not requiring name resolution through DNS. A remote node can connect to the node you name with a numeric IP address without DNS being available. A format disadvantage is that the numeric IP address is fixed. You must change the setting of the hostName property in Express configuration documents whenever you change the machine IP address. Therefore, do not use a numeric IP address if you use DHCP, or if you change IP addresses regularly. Another format disadvantage is that we cannot use the node if the host is disconnected from the network.
After specifying application server characteristics, the wizard displays the Port value assignment panel.
- Verify
that the ports specified for the stand-alone application server are
unique, then click Next.
After specifying port assignments, the wizard displays the Windows service definition panel, if you are installing on a Windows platform.
-
Choose whether to
run the application server as a Windows service on a Windows platform
and click Next.
V6 attempts to start Windows services for application server processes started by a startServer command. For example, if you configure an application server as a Windows service and issue the startServer command, the wasservice command attempts to start the defined service.
If you chose to install a local system service, you do not have to specify your user ID or password. If you create a specified user type of service, specify the user ID and the password for the user who is to run the service. The user must have Log on as a service authority for the service to run properly.
To perform this installation task, the user ID must not have spaces in its name. The ID must also belong to the administrator group and must have the advanced user rights Act as part of the operating system and Log on as a service. The Installation wizard grants the user ID the advanced user rights if it does not already have them, if the user ID belongs to the administrator group.
We can also create other Windows services after the installation is complete, to start other server processes.
The installation wizard shows which components are selected for installation in a pre-installation summary panel.
- Click
Next to create the application server or click
Back to change the characteristics of the application
server.
The wizard displays the Installation status panel that shows which components are installing.
When the installation is complete, the wizard displays the Profile creation is complete panel.
- Click Finish to exit, then click Profile creation wizard on the First steps console to start the wizard again to create other application servers.
We can create an application server profile. The node within the profile has an application server named server1.
Refer to the description of the wasprofile command to learn about creating this type of profile using a command instead of a wizard.
Delete a profile
This topic describes how to manually delete a profile.
Before using the manual procedure to remove a profile, try the wasprofile command with the -delete option. For example...
./wasprofile.sh -delete \ -profileName profile | \ -profilePath profile_path
See wasprofile command.
If the command does not work, use this procedure to delete the profile.
This procedure describes how to manually delete a profile when the wasprofile -delete command results in the following message:
INSTCONFFAILED: Cannot delete profile
- Delete...
profiles_install_root/profile
- If...
install_root/properties/profileRegistry.xml
exists, edit the file in a flat-file editor to delete the entry for the profile, if the entry is present.
The entry resembles the following example:
<profile isDefault="true" name="BadProfile" path="E:\IBM\WebSphere\AppServer\profiles\BadProfile" template="E:\IBM\WebSphere\AppServer\profileTemplates\default"/>
- Linux AIX, HP-UX, Solaris Compare the two batch files...
install_root/properties/fsdb/_was_profile_default/default.sh
...and...
install_root/properties/fsdb/bad_profile.sh
If the files are identical, delete...
install_root/properties/fsdb/_was_profile_default
...and...
install_root/properties/fsdb/bad_profile.sh
If the files are not identical, delete only...
install_root/properties/fsdb/bad_profile.sh
- Compare the two batch files...
install_root\properties\fsdb\_was_profile_default\default.bat
...and...
install_root\properties\fsdb\bad_profile.bat
If the files are identical, delete...
install_root\properties\fsdb\_was_profile_default
...and...
install_root\properties\fsdb\bad_profile.bat
If the files are not identical, delete only...
install_root\ properties\fsdb\bad_profile.bat
See the description of the wasprofile command to learn more about the command-line method of working with profiles.
See Use the Profile creation wizard for more information about creating profiles with the Profile creation wizard.
wasprofile command
The wasprofile command line tool creates all Application Server run-time environments in V6. The command creates a profile, which is the set of files that define the run-time environment for a stand-alone Application Server.
The wasprofile command is also referred to as the profile creation tool.
Introduction to terms that describe V6 profiles
The wasprofile command creates the run-time environment for a WAS process in a set of files called a profile. The profile defines the run-time environment and includes all of the files that the server processes in the run-time environment can change. The profile creation tool and its graphical user interface, the Profile creation wizard, are the only ways to create run-time environments in V6.
The Profile creation wizard is an ISMP application. Use the wizard to enter most of the parameters that are described in this topic. Some parameters, however, require you to use the wasprofile command. You must use the wasprofile command to delete a profile, for instance, because the Profile creation wizard does not provide a deletion function.
However, the Profile creation wizard also performs tasks that the wasprofile command does not. For instance, the wizard can create a Windows service for each profile that it creates. It can also assign non-conflicting ports based on previous V6 port assignments.
Core product files
The core product files are the shared product binaries. The binary files are shared by all profiles.
The directory structure for V6 has two major divisions of files in the installation root directory for the product:
- The core product files are shared product binary files that do not change unless you install a refresh pack, a fix pack, or an interim fix. Some log information is also updated.
- The profiles directory is the default directory for creating profiles. The configuration for every defined Application Server process is within the profiles directory unless you specify a new directory when you create a profile. These files change as often as you create a new profile, reconfigure an existing profile, or delete a profile.
All of the folders except for the profiles directory and a few others such as the logs directory and the properties directory do not change unless you install service fixes. The profiles directory, however, changes each time you add, change, or delete a profile. The profiles directory is the default repository for profiles. However, we can put a profile anywhere on the machine provided there is enough available disk space.
If you put a profile in another existing folder in the installation root directory, a risk exists that the profile might be affected by the installation of a service fix that applies maintenance to the folder. Use a directory outside of the installation root directory when using a directory other than the profiles directory for creating profiles.
WAS profile
The wasprofile command line tool defines each Application Server instance of a V6 product.
You must run the wizard or the command line tool each time that you want to create a stand-alone Application Server. A need for more than one stand-alone Application Server on a machine is common.
Administration is greatly enhanced when using V6 profiles instead of multiple product installs. Not only is disk space saved, but updating the product is simplified when you only maintain a single set of product core files. Also, creating new profiles is faster and less prone to error than full product installs, allowing a developer to create new disposable profiles of the product for development and testing.
We can run the Profile creation wizard or the profile creation tool to create a new Application Server environment on the same machine as an existing one. Simply define unique characteristics (such as profile name and node name) for the new profile. Each profile has its own administrative console and administrative scripting interface. Each Application Server process shares all run-time scripts, libraries, the Software Development Kit, and other core product files.
The installation program for the base WAS product uses the profile creation tool to create an Application Server profile named default.
Installed file set
You decide where to install the files that define a profile. The default location is in the profiles directory in the installation root directory. But we can change the location on the Profile creation wizard or in a parameter when using the command line tool. For example, assume that you create two profiles on a Linux platform with host name devhost1. The profile directories resemble the following example if you do not relocate them:
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile02Suppose that you specify a different directory, such as /opt/profiles, for the profile directory field in the wizard. The profile directories resemble the following example:
/opt/profiles/devhost1Profile01
/opt/profiles/devhost1Profile02The following directories exist within a profile. This example assumes that a profile named devhost1Profile01 exists:
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/bin
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/config
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/etc
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/firststeps
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/installableApps
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/installedApps
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/installedConnectors
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/installedFilters
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/logs
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/properties
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/samples
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/temp
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/tranlog
- /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01/wstemp
The profile repository
The profile repository is the default location of profile-related metadata. The repository is the default location for new profiles, which is often referred to as the profiles installation root directory.
However, we can decide where to install a profile. The default location of the profile repository is...
install_root/profiles
In the earlier example, creating two profiles on a Linux platform with host name devhost1 results in the following example directories in the profile repository:
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile02When you specify a directory, such as /opt/profiles, the profiles are no longer in the default repository, which is not a problem. For example, the following locations are valid:
/opt/profiles/devhost1Profile01
/opt/profiles/devhost1Profile02Location of the command file
The command file is located in...
install_root/bin
The command file is a script named wasprofile.sh
The Profile creation wizard is the graphical user interface to the command line tool. The file name of the command that calls the Profile creation wizard varies per operating system platform.
Logging
The wasprofile command creates a log for every profile that it creates. The logs are in...
install_root/logs/wasprofile
The files are named in this pattern:
wasprofile_create_profile.log
The command also creates a log for every profile that it deletes. The logs are in...
install_root/logs/wasprofile
The files are named in this pattern: wasprofile_delete_profile.log.
Required disk space
Manually verify that the required space for creating a profile is available on AIX. A known problem in the underlying ISMP code prevents proper space checking on AIX systems at the time that the product disc was created.
An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
You must have 200 MB of available disk space in the directory where you create an Application Server profile.
Concurrent profile creation
Important: Concurrent profile creation is not supported at this time for one set of core product files. Concurrent attempts to create profiles result in a warning about a profile creation already in progress.
Entering lengthy commands on more than one line
The length of the wasprofile command can exceed the normal shell window limit for one line of 256 characters. If your command is longer than the limit, issue the command on multiple lines by ending a line with a backward slash, pressing Enter, and continuing the command on the next line.
For example, on a Solaris system, the following command requires input on multiple lines:
./wasprofile.sh -create \ -profileName bladetcb6profile \ -profilePath /usr/IBM/WebSphere/AppServer/profiles/bladetcb6profile \ -templatePath /usr/WebSphere/AppServer/profileTemplates/default \ -nodeName bladetcb6node \ -cellName bladetcb6Cell \ -hostName bladetcb6.rtp.raleigh.ibm.comOmit the line continuation character from the last line to signal the end of the command to the operating system.
wasprofile.sh command syntax
List existing profiles:
# ./wasprofile.sh -listProfiles [-debug]
Delete profiles:
# ./wasprofile.sh -delete -profileName profile | -profilePath profile_path [-debug]
Create new profiles:
wasprofile.sh -create -profileName profile -profilePath fully_qualified_profile_path -templatePath template_path -nodeName node -cellName cell -hostName host_name -server iSeries_servername [-startingPort starting_port | -portsFile filepath] -winserviceCheck true | false -winserviceAccountType specifieduser | localsystem -winserviceUserName yourusername -winservicePassword yourpassword -winserviceStartupType manual | automatic | disabled [-debug]
Get name of existing profile from path:
# ./wasprofile.sh -getName -profilePath profile_path [-debug]Get path of existing profile from name:
# ./wasprofile.sh -getPath -profileName profile [-debug]Check the integrity of the profile registry:
# ./wasprofile.sh -validateRegistry [-debug]Check the integrity of the profile registry, removing profiles that are not found:
# ./wasprofile.sh -validateAndUpdateRegistry [-backup file_name] [-debug]Parameters
Supported arguments include:
- -augment
- Refreshes or augments the given profile using the template in the templatePath parameter.
- -backup file_name
- Backs up the profile registry file to a file with the file name specified.
- -cellname file_name
- Specifies the cell name of the profile.
This is an optional parameter for WAS.
If you omit the parameter, a default cell name is assigned.
- -create
- Creates the profile.
- -debug
- Turns on the debug function of the Ant utility, which the wasprofile command uses.
- -delete
- Deletes the profile.
- -getName
- Gets the name for a profile registered at a given file system path. Requires the -profilePath parameter.
- -getPath
- Gets the file system location for a profile of a given name. Requires the -profileName parameter.
- -hostName host_name
- Specifies the host name where you are creating the profile. This should match the host name that you specified during installation of the initial product.
- -listProfiles
- Lists all defined profiles.
- -nodeName node
- Node name for the node that is created with the new profile. Use a unique value or on the machine. Each profile that shares the same set of product binaries must have a unique node name.
- -portsFile file_path
- An optional parameter that specifies the path to a file that defines port settings for the new profile. When omitted, the wasprofile tool looks for...
install_root /profileTemplates/profile_type/actions/portsUpdate/bin/portdef.props
Do not use this parameter when using the startingPort parameter.
- -profileName profile
- Name of the profile. Use a unique value when creating a profile. Each profile that shares the same set of product binaries must have a unique name.
- -profilePath profile_path
- Specifies the fully qualified path to the profile.
If the fully qualified path contains spaces, enclose the value in quotation marks.
- server iSeries_servername
- Name of the server on an iSeries platform.
- -startingPort startingPort
- Specifies the starting port number for generating all ports for the profile. If not specified, the wasprofile command uses default ports specified in the serverindex.xml file.
- -templatePath template_path
- Specifies the path to the templates in the shared binaries.
- -validateAndUpdateRegistry registry_file backup_file
- Checks all of the profiles that are listed in the profile registry to see if the profiles are present on the file system. Removes any missing profiles from the registry. Returns a list of the missing profiles that were deleted from the profile.
- -validateRegistry registry_file
- Checks all of the profiles that are listed in the profile registry to see if the profiles are present on the file system. Returns a list of missing profiles.
- -winserviceAccountType type_of_owner_account
- The type of the owner account of the Windows service created for the profile can be either specifieduser or localsystem. The Windows service can run under the local account of the user who is creating the profile.
- winserviceCheck value
- The value can be either true or false. Specify true to create a Windows service for the server process that is created within the profile. Specify false to not create the Windows service.
- -winservicePassword yourpassword
- Specify the password for the specified user or the local account that is to own the Windows service.
- -winserviceStartupType startup_type
- Possible startup_type values are:
- manual
- automatic
- disabled
- -winserviceUserName user_ID
- Specify your user ID so that Windows can verify you as an ID that is capable of creating a Windows service. Your user ID must belong to the administrator group and have the following advanced user rights, Act as part of the operating system and Log on as a service
Scenario: Delete a profile
wasprofile.sh -delete -profileName shasti
Scenario: Use predefined port numbers
When you use the wasprofile tool without the -startingPort parameter, the tool uses...
/profileTemplates/profile_type/actions/portsUpdate/bin/portdef.props
...to set the initial ports.
Example of using the -portsFile parameter
Copy the file, edit the port settings, and use your copy by using the -portsFile parameter as shown in the following example:
wasprofile.bat -create -profileName Wow_Profile -profilePath C:\ExpressV6\IBM\WebSphere\AppServer\profiles\Wow_Profile -templatePath C:\ExpressV6\IBM\WebSphere\AppServer\profileTemplates\default -nodeName Wow_node -cellName Wow_cell -hostName loyAllen -portsFile C:\temp\ports\portdef.props
Suppose that the portdef.props file has the following values:
WC_defaulthost=39080 WC_adminhost=39060 WC_defaulthost_secure=39443 WC_adminhost_secure=39043 BOOTSTRAP_ADDRESS=32809 SOAP_CONNECTOR_ADDRESS=38880 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=39401 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=39403 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=39402 ORB_LISTENER_ADDRESS=39100 DCS_UNICAST_ADDRESS=39353 SIB_ENDPOINT_ADDRESS=37276 SIB_ENDPOINT_SECURE_ADDRESS=37286 SIB_MQ_ENDPOINT_ADDRESS=35558 SIB_MQ_ENDPOINT_SECURE_ADDRESS=35578
As you run the command, messages similar to the following appear in the output stream:
replaceRegExpAllInstancesOfGivenTokenWithGivenValueForTheGivenFile: [echo] File C:\ExpressV6\IBM\WebSphere\AppServer\profiles\ Wow_Profile/config/templates/default/serverentry-template.xml: setting CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS to 39403 ... replaceRegExpAllInstancesOfGivenTokenWithGivenValueForTheGivenFile: [echo] File C:\ExpressV6\IBM\WebSphere\AppServer\profiles\ Wow_Profile/config/templates/default/serverentry-template.xml: setting CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS to 39402 ...
The resulting serverindex.xml file looks similar to the following example:
<?xml version="1.0" encoding="UTF-8"?> <serverindex:ServerIndex xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" ... <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="BOOTSTRAP_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="32809"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SOAP_CONNECTOR_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="38880"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39401"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39403"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39402"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_adminhost"> <endPoint xmi:id="EndPoint_..." host="*" port="39060"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_defaulthost"> <endPoint xmi:id="EndPoint_..." host="*" port="39080"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="DCS_UNICAST_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39353"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_adminhost_secure"> <endPoint xmi:id="EndPoint_..." host="*" port="39043"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_defaulthost_secure"> <endPoint xmi:id="EndPoint_..." host="*" port="39443"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_ENDPOINT_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="37276"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_ENDPOINT_SECURE_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="37286"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_MQ_ENDPOINT_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="35558"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_MQ_ENDPOINT_SECURE_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="35578"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="ORB_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39100"/> </specialEndpoints> </serverEntries> </serverindex:ServerIndex>The wasprofile command creates a copy of the current portdefs.props file in...
install_root\profiles\profile\logs
Do not use the portsFile parameter when using the startingPort parameter. The two parameters are mutually exclusive.
Scenario: Increment default port numbers from a starting point
The wasprofile command can assign port numbers based on a starting port value that you give on the command line, using the -startingPort parameter. The tool assigns port numbers sequentially from the starting port number value.
The order of port assignments is arbitrary. Predicting assignments is not possible.
For example, ports created with -startingPort 20002 would appear similar to the following example:
Assigned ports for an Application Server profile
WC_defaulthost=20002 WC_adminhost=20003 WC_defaulthost_secure=20004 WC_adminhost_secure=20005 BOOTSTRAP_ADDRESS=20006 SOAP_CONNECTOR_ADDRESS=20007 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=20008 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=20009 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=20010 ORB_LISTENER_ADDRESS=20011 DCS_UNICAST_ADDRESS=20012 SIB_ENDPOINT_ADDRESS=20013 SIB_ENDPOINT_SECURE_ADDRESS=20014 SIB_MQ_ENDPOINT_ADDRESS=20015 SIB_MQ_ENDPOINT_SECURE_ADDRESS=20016
Example of startingPort parameter use
The following example of using the wasprofile command creates ports from an initial value of 20002, with the content shown in the previous example:
wasprofile.bat -create -profileName shasti -profilePath G:\shasti\WebSphere -templatePath template_path -nodeName W2K03 -cellName W2K03_Cell01 -hostName planetnt -startingPort 20002
Scenario: Setting up and using the profile environment
Most tasks that you perform in a profile are done using the -profileName attribute on the command line tools that you use. Such a scenario might be:
- Create the server process using...
install_root/bin/wasprofile.sh
...from the original installation. Assume that you create the Profile02 profile.
- In that command window or in another, change directories to the /bin directory of the new server process.
- Establish a temporary
override for the normal WAS environment by
using the -profileName attribute on a command you issue. In the same
window, start server1 by changing directories to...
install_root/bin
...of the original installation and issuing the command. There is no such command in the /bin directory of the server process:
startServer.sh server1 -profileName Profile02
- Notice the changes in the environment. Display all of the ports for the machine to see the ports that you set for the server process. For example, in a Linux bash shell or in the command window on a Windows platform, type:
netstat -a
- Open a browser window and point it at the port defined for the HTTP_TRANSPORT_ADMIN port of the new process. For example, suppose the setting is HTTP_TRANSPORT_ADMIN=20003. Open the administrative console for server1 by pointing your browser at:
http://hostname_orIP_address:20003/ibm/console/
Scenario: Profile creation for a non-root user
Two methods exist for a non-root user to create a profile:
- The root user creates the profile and assigns ownership to the non-root user.
- A non-root user creates a profile after getting write permission to the appropriate directories.
Remember: An ease-of-use limitation exists for non-root users who create profiles. Mechanisms within the Profile creation wizard that suggest unique names and port values are disabled for non-root users. The non-root user must change the default field values in the Profile creation wizard for the profile name, node name, and port assignments. Consider assigning non-root users a range of values for each of the fields. We can assign responsibility to the non-root profilers for adhering to their proper value ranges and for maintaining the integrity of their own definitions.
Root creates the profile and assigns ownership to a non-root user
The root user can create a profile and assigns ownership of the profile directory to a non-root user.
- The root user creates the profile with the following command:
./wasprofile.sh -create -profileName profile01 -profilePath install_root/profiles/profile01
- The root user changes ownership of the directory for the profile to the non-root user with the following command:
chown -R user1 install_root/profiles/profile01
A non-root user creates the profile (advanced option)
The root user can grant write permission to the appropriate files and directories to a non-root user. The non-root user can then create the profile. We can create a group for users who are authorized to create profiles. Or we can give everyone the ability to create profiles. The following example shows how to create a group that is authorized to create profiles.
- Log on to the Application Server system as root.
- Create the profilers group that use to create profiles.
- Create a user named user1 to create profiles.
- Add users root and user1 to the profilers group.
- Log off and back on as root to pick up the new group.
- As root, use operating system tools to change file permissions.
mkdir /opt/IBM/WebSphere/AppServer/logs/wasprofile
chgrp profilers /opt/IBM/WebSphere/AppServer/logs/wasprofile
chmod g+wr /opt/IBM/WebSphere/AppServer/logs/wasprofile
chgrp profilers /opt/IBM/WebSphere/AppServer/properties
chmod g+wr /opt/IBM/WebSphere/AppServer/properties
chmod g+wr /opt/IBM/WebSphere/AppServer/properties/profileRegistry.xmlYou might have to change the permissions on additional...
/opt/IBM/WebSphere/AppServer
...directories if you encounter permission problems.
- The non-root user who
belongs to the profilers group can then create a profile in any
directory to which the non-root user has write permission.
If the non-root user does not have write access to any directories, it is up to the root user to change that situation. If the non-root user does not have write access to the /tmp directory, it is up to the root user to change that as well.
The commands listed in step 6 give users assigned to the profilers group the ability to write to...
/opt/IBM/WebSphere/AppServer/logs/wasprofile
...directory and to...
/opt/IBM/WebSphere/AppServer/properties
...directory. It is not necessary to write to any other directories in the installation root of your WAS product.
Have non-root users create a profiles directory in their own area, not in the installation root directory of the product.
Use the installation verification test
The IVT verifies that the installation of the application server profile was successful. A profile consists of files that define the run-time environment for an application server. Each profile has its own IVT command.
The IVT program scans product log files for errors and verifies core functionality of the product installation. After installing the product, the Installation wizard displays a prompt for starting the First steps console.
The test consists of starting and monitoring the application server during its start up.
- Select Installation verification on the First steps console after installing the product.
We can also start the ivt command directly from the bin directory of the profile:
install_root/profiles/default/bin/ivt.sh
If you create additional profiles, the ivt script location is within the profile_home/bin directory.
- Observe
the results in the First steps status window.
The log file for installation verification is...
install_root/profiles/default/logs/ivtClient.log
If you create additional profiles, the file path is...
profile_home/logs/ivtClient.log
The IVT provides the following useful information about the application server:
- The application server name
- The name of the profile
- The profile file path
- The type of profile
- The node name
- The current encoding
- The port number for the administrative console
- Various informational messages that include the location of the SystemOut.log file and how many errors are listed within the file
- A completion message
As the IVT starts the application server on a Windows platform, the IVT attempts to start the Windows service for the application server, if a Windows service exists. This is true even though the Windows service might have a manual startup type.
- If the log shows that errors occurred during the installation verification, correct the errors and run the IVT again. If necessary, create a new profile after correcting the error, and run the IVT on the new profile.
The IVT program starts the server process automatically if the server is not running. Once the server initializes, the IVT runs a series of verification tests. The tool displays pass or fail status in a console window. The tool also logs results to the profile_home/logs/ivtClient.log file. As the IVT verifies your system, the tool reports any detectable cellpadding=10 errors in the SystemOut.log file.
ivt command
The ivt command starts the installation verification test (IVT) program. The IVT verifies that the installation of the application server profile was successful. A profile consists of files that define the run-time environment for an application server. Each profile has its own IVT command.
The IVT program starts the application server automatically if the server process is not already running. After the server process initializes, the IVT runs a series of verification tests and displays pass or fail status in a console window.
The IVT program scans the SystemOut.log file for errors and verifies core functionality of the profile.
We can start the IVT program from the command line or from the First steps console.
Location of the command file
Install the product creates a default profile for the server1 application server. The location of the installation verification test program for the default profile is:
install_root/profiles/default/bin/ivt.sh
The location of the ivt.sh for any profile is:
install_root/profiles/profile/bin/ivt.sh
Parameters
The following parameters are associated with this command.
- servername
- Required parameter that identifies the name of the server process, such as server1.
- profile
- Required parameter that identifies the name of the profile that contains the server definition.
- -p server_port_number
- Optional parameter that identifies the default_host port when the port is not 9080, which is the default.
- -host machine_host_name
- Optional parameter that identifies the host machine of the profile to test. The default is localhost.
Syntax for the ivt command
Use the following syntax for the command:
install_root/profiles/profile/bin/ivt.sh
Logging
The ivt command logs results to...
install_root/profiles/profile name/logs/ivtClient.log
Example
The following examples test the server1 process in the profile01 profile on the myhost machine using the default_host on port 9081.
ivt.sh server1 profile01 -p 9081 -host myhost
Use the launchpad to start the installation
The launchpad console is the starting point for installing WAS products.
The launchpad is a Web application. Before using the launchpad, have a supported Web browser. The launchpad supports the following browsers:
- Mozilla
- Internet Explorer
The launchpad program is available on the root directory of the product CD in a program named:
launchpad.sh
Start the launchpad if it does not launch automatically.
Use this topic to learn how to use the launchpad.
WAS is an integrated platform that contains an Application Server, a set of Web development tools, a Web server, and additional supporting software and documentation. The launchpad is the single point of reference for installing the entire Application Server environment.
The launchpad opens in the language of the machine locale setting. The launchpad identifies components on the product disc that we can launch.
The launchpad can install the tools component in the primary packet of discs. The launchpad on the separate Application Server Toolkit disc can launch the installation of the tool on Windows 2000 and Linux (Intel) systems.
The launchpad has diagrams that show the possible application server topologies that we can create with all of the components in the primary packet.
A link exists for each installable component on the product compact disc and for the installable tools component that is on a separate disc in the primary packet of compact discs in the product package.
There is no launchpad for the compact discs in the secondary packet in the product package, such as the DB2 product. See Packaging for more information about the installable components in each package.
For example, the installation links on the initial launchpad panel for the base WebSphere Application Server product are:
- The Welcome panel with its fastpath links that launch the installer programs for the following installable components:
- Launch the installation wizard for WAS
- Launch the installation wizard for IBM HTTP Server
- Launch the installation wizard for Web server plug-ins
- Launch the installation wizard for WAS Clients
- Launch the installation wizard for the Application Server Toolkit
- A navigation frame on the left side of the launchpad has the following links:
- Solution installation diagrams
- WAS installation
- IBM HTTP Server installation
- Web server plug-ins installation
- WAS Clients installation
- Application Server Toolkit installation
The launchpad panel for each installable component in the primary packet includes a link to the installation program for the component and to documentation that describes the product, how to install it, and how to configure it for use.
For example, the links on the launchpad panel for the base WAS installable component are:
- Launch the Installation wizard for WAS
- View the product overview for WAS
- View the installation guide for WAS
- View the readme file for WAS
Perform the following procedure to use the launchpad.
- Log on as root on a Linux or UNIX system, or as a member of the administrator group on a Windows system.
- Install
the Internet Explorer Web browser or the Mozilla browser if neither
browser is installed.
-
Install the two
prerequisite packages that Mozilla on AIX requires and install Mozilla,
as described in Prepare
AIX systems for installation.
- Download the latest supported version of Internet Explorer. Download Internet Explorer from the following location:
-
Linux
Download and install
the Mozilla Web browser. If you do not have the Mozilla Web
browser, download and install the browser from
http://www.mozilla.org.
-
Linux
AIX, HP-UX, Solaris Export the location
of the supported browser. Export the location of the supported
browser using the following command:
EXPORT BROWSER=/usr/bin/mozilla
-
- Start
the launchpad.
We can start the launchpad manually using a fully qualified command instead of changing directories to the CD-ROM and running the command locally from the root directory:
- Mount the CD-ROM drive on Linux or UNIX platforms, if necessary. This procedure varies per platform.
- Open a shell window and
issue a fully qualified command to start the launchpad:
launchpad.sh
- Use the launchpad to access the product overview, the readme file, and the installation guide.
- Click Launch the installation wizard for ... to launch the installation wizard for the installable component that you select.
Use the launchpad to start the installation and to access information through a browser.
Troubleshooting
If we can start the launchpad, but clicking a link does not resolve to a page in the launchpad, you might have the media for the wrong operating system in the CD drive. Check the validity of the media. Otherwise, use the following procedure. If the links do not work at the end of the procedure, open the readme file for reference and launch the installation programs directly.
If we cannot start the launchpad, use the following procedure to correct any error that is preventing the launchpad from displaying, then start the launchpad again:
- Install Mozilla or Internet Explorer as described in the procedure.
- If the product CD is no
longer accessible, insert the CD.
Mount the drive as necessary on Linux and UNIX platforms.
- Enable the JavaScript function in your browser.
Mozilla: Click...
Edit | Preferences | Advanced | Scripts & Plugins:
- Enable JavaScript for: Navigator.
- Allow scripts to select all boxes.
Internet Explorer: Click...
Tools | Internet Options | Security | Custom Level for Internet | Scripting | Active scripting | Enable
- Restart the launchpad...
./launchpad.sh
If you still cannot use the launchpad console, access the readme file in the root directory of the product disc or launch each installer program directly. We can launch the following links directly:
- Welcome page links
- The fastpath links to
installable components on the product disc are provided in the following
table:
Installable component Directory Program WAS WAS install IBM HTTP Server IHS install Web server plug-ins plugin install Application clients AppClient install The fastpath link to the installable component on the Application Server Toolkit disc is:
Application Server Toolkit: setup (in the root directory)
Mount the CD for the Application Server Toolkit and use the launchpad on that disc.
- Solution installation diagrams
- See the installation scenarios in Plan to install WAS.
- WAS installation
- Links on the page include:
- Launch the installation wizard...
-
Installable component Directory Program WAS WAS install - View the product overview...
- /WAS/docs/InstallGuide_en.html#over
This is a section of the Getting Started guide. Language versions of this information are available only in the online Information center in Packaging.
- View the installation guide...
- /WAS/docs/InstallGuide_en.html#install
This is the Getting Started guide. Language versions of the information in the Getting Started guide are available only in the online Information center in Installing the product and additional software.
- View the readme file...
- /WAS/readme/readme_en.html
- Web server plug-ins installation
- Links on the page include:
See Configuration behavior of the Plug-ins installation wizard for an overview of how Web server configuration works.
Mounting CD-ROMS on Linux and UNIX operating systems
The following sections describe how to mount the CD-ROM on Linux and UNIX operating systems.
After inserting a CD-ROM into a drive, some Linux and UNIX operating systems require you to mount the drive.
Use these procedures to mount the product discs.
- Mounting the CD-ROM on
AIX To mount the CD-ROM on AIX using the System Management
Interface Tool (SMIT), perform the following steps:
- Log in as a user with root authority.
- Insert the CD-ROM in the drive.
- Create a CD-ROM mount point by entering the mkdir -p /cdrom command, where cdrom represents the CD-ROM mount point directory.
- Allocate a CD-ROM file system using SMIT by entering the smit storage command.
- After
SMIT starts, click...
File Systems | Add / Change / Show / Delete File Systems | CDROM File Systems | Add CDROM File System
- In
the Add a File System window:
- Enter a device name for your CD-ROM file system in the DEVICE Name field. Device names for CD-ROM file systems must be unique. If there is a duplicate device name, you may need to delete a previously-defined CD-ROM file system or use another name for your directory. The example uses /dev/cd0 as the device name.
- Enter the CD-ROM mount point directory in the MOUNT POINT window. In our example, the mount point directory is /cdrom.
- In the Mount AUTOMATICALLY at system restart field, select yes to enable automatic mounting of the file system.
- Click OK to close the window, then click Cancel three times to exit SMIT.
- Next, mount the CD-ROM file system by entering the smit mountfs command.
- In
the Mount a File System window:
- Enter the device name for this CD-ROM file system in the FILE SYSTEM name field. In our example, the device name is /dev/cd0.
- Enter the CD-ROM mount point in the Directory over which to mount field. In our example, the mount point is /cdrom.
- Enter cdrfs in the Type of Filesystem field. To view the other kinds of file systems we can mount, click List.
- In the Mount as READ-ONLY system field, select yes.
- Accept the remaining default values and click OK to close the window.
Your CD-ROM file system is now mounted. To view the contents of the CD-ROM, place the disk in the drive and enter the cd /cdrom command where cdrom is the CD-ROM mount point directory.
- Mounting
the CD-ROM on HP-UX Because the product contains several files with
long file names, the mount command can fail. The following steps
successfully mount the product CD-ROM on the HP-UX platform:
- Log in as a user with root authority.
- In
the /etc directory, add the following line to the
pfs_fstab
file:
where mount_point represents the mount point of the CD-ROM./dev/dsk/c0t2d0 mount_point pfs-rrip ro,hard
- Start
the pfs
daemon by entering the following commands (if they are not already
running):
/usr/sbin/pfs_mountd & /usr/sbin/pfsd 4 &
- Insert
the CD-ROM in the drive and enter the following
commands:
mkdir /cdrom /usr/sbin/pfs_mount /cdrom
The /cdrom variable represents the mount point of the CD-ROM.
- Log out.
- Mounting
the CD-ROM on Linux To mount the CD-ROM on Linux:
- Log in as a user with root authority.
- Insert
the CD-ROM in the drive and enter the following command:
mount -t iso9660 -o ro /dev/cdrom /cdrom
The /cdrom variable represents the mount point of the CD-ROM.
- Log out.
Some window managers can automatically mount your CD-ROM for you. Consult your system documentation for more information.
- Mounting
the CD-ROM on Solaris To mount the CD-ROM on Solaris:
- Log in as a user with root authority.
- Insert the CD-ROM into the drive.
- If
the Volume Manager is not running on your system, enter the following
commands to mount the CD-ROM:
The /cdrom/unnamed_cdrom variable represents the CD-ROM mount directory and the /dev/dsk/c0t6d0s2 represents the CD-ROM drive device.mkdir -p /cdrom/unnamed_cdrom mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/unnamed_cdrom
If you are mounting the CD-ROM drive from a remote system using NFS, the CD-ROM file system on the remote machine must be exported with root access. You must also mount that file system with root access on the local machine.
If the Volume Manager (vold) is running on your system, the CD-ROM is automatically mounted as:
/cdrom/unnamed_cdrom
- Log out.
Prepare AIX systems for installation
The installation uses a ISMP wizard. Use the graphical interface of the wizard. We can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Use the following procedure to prepare the operating system for the installation of WAS products.
- Log on as root.
We cannot install the product correctly as a non-root user.
If you create a copy of the product CD-ROM, do so as root. Copies made from non-root users do not preserve the correct file attributes and do not work.
In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Stop all WAS-related Java processes on the machine where you are installing the product.
- Stop any Web server process such as the IBM HTTP Server.
- Use the System Management Interface Tool (SMIT) to display packages that are installed to determine whether update packages that are described in the following steps.
- Download the most current version of the INFOZIP product to avoid problems with zipped files. Although zipped files are primarily used in the service stream, prepare your AIX operating system by downloading a current version of the INFOZIP package from the http://www.info-zip.org Web site.
- Install
the prerequisite xlC.rte 6.0 run-time code on AIX 5.2 maintenance level
1.
You must install the xlC.rte 6.0 run-time code before you install the Global Security Kit 7 (GSKit7). The GSKit is installed as part of the installation of the IBM HTTP Server and also as part of the installation of Web server plug-ins for WAS. Download the run-time code as a fix from the AIX Support site.
If you have AIX 5.2, we can install the xlC.rte 6.0 run-time code from the AIX 5.2 CD.
- Provide adequate disk space.
With the JFS file system on AIX, we can allocate expansion space for directories. If the Installation wizard does not have enough space, ISMP issues a system call for more space that increases the space allocation dynamically. The message you might see when this occurs for the /usr directory is similar to the following example:
NOTE: The following file systems will be expanded during the installation: /usr
The base WAS product requires the following disk space:
- 930 MB for the /usr/IBM/WebSphere/AppServer directory
-
The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.
Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.
- 100 MB for the /tmp directory
-
The temporary directory is the working directory for the installation program.
- 1030 MB total requirement
-
This amount is the total space requirement when installing the product from the CD.
Manually verify that the required space for creating a profile is available on AIX. A known problem in the underlying ISMP code prevents proper space checking on AIX systems at the time that the product disc was created.
The following space is required for the IBM HTTP Server product:
- 110 MB for the /usr/IBMIHS directory
-
The IBM HTTP Server product requires this space.
- 35 MB for the /usr/ibm/gsk7 directory
-
The Tivoli Global Security Kit requires this space.
The run-time module is gskkm.rte.
The following space is the maximum amount that is required for the Web server plug-ins for WAS:
- 200 MB for the /usr/IBM/WebSphere/plugins directory
-
The Web server plug-ins require this disk space.
- 25 MB for the /usr/ibm/gsk7 directory
-
The Tivoli Global Security Kit requires this space.
The following space is required for the IBM HTTP Server product:
- 110 MB for...
/opt/IBMIHS
-
The IBM HTTP Server product requires this space.
- 25 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The following space is required for the WAS Clients:
- 150 MB for the /usr/IBM/WebSphere/AppClient directory
-
The amount of space required to install the application clients is actually less than 150 MB. The amount of space depends on the clients that you install as features.
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:
- For V4.0.x: The size of enterprise archive (EAR) files
- For V5.0.x: The size of EAR files
- Unmount
file systems with broken links to avoid java.lang.NullPointerException
errors.
Unmount file systems with broken links before installing.
Installation can fail with the following error when broken links exist to file systems:
An error occurred during wizard bean change notification: java.lang.NullPointerException at com.ibm.wizard.platform.aix.AixFileUtils. getFileSystemData(AixFileUtils.java:388) at com.ibm.wizard.platform.aix.AixFileUtils. getPartitionDataWithExecs(AixFileUtils.java:172) at com.ibm.wizard.platform.aix.AixFileUtils. getPartitionData(AixFileUtils.java:104) at com.ibm.wizard.platform.aix.AixFileServiceImpl. getPartitionNames(AixFileServiceImpl.java:397) ...
Use the df -k command to check for broken links to file systems. Look for file systems that list blank values in the 1024-blocks size column. Columns with a value of "-" (dash) are not a problem. The following example shows a problem with the /dev/lv00 file system:
> df -k Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 447924 58% 2497 1% / /dev/hd3 4259840 2835816 34% 484 1% /tmp /proc - - - - - /proc /dev/lv01 2097152 229276 90% 3982 1% /storage /dev/lv00 /dev/hd2 2097152 458632 79% 42910 9% /usr iw031864:/cdrom/db2_v72_eee_aix32_sbcs
The /proc file system is not a problem. The iw031864:/cdrom/db2_v72_eee_aix32_sbcs file system is a definite problem. The /dev/lv00 file system is also a likely problem. Use one of the following commands to solve this problem:
> umount /cdrom/db2_v72_eee_aix32_sbcs > umount /cdrom
Start the installation again. If the problem continues, unmount any file systems that have blank values, such as the /dev/lv00 file system in the example. If you cannot solve the problem by unmounting file systems with broken links, reboot the machine and start the installation again.
- Verify
that prerequisites and corequisites are at the required release
levels.
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware and software Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
- Verify
the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your operating system, verify that the system cp command is used.
- Type which cp at the command prompt before running the installation program for the WAS product.
- Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example, assume that the output is similar to the following message: .../freeware/bin/cp. If so, remove the directory from the PATH.
- Install the WAS product.
- Add the freeware directory back to the PATH.
If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in...
install_root/java
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, install the Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
- Verify
that the Java 2 SDK on your copy of the product CD is functioning
correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
cd /mnt/JDK/repository/prereq.jdk/java/bin
- Verify
the Java 2 SDK version. Type the following command:
./java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
- Optional: Install
the Mozilla browser if it is not already installed. The Mozilla browser
supports the launchpad console.
- Use smit to see if the Mozilla 1.4 or 1.7 or later package is already installed.
- Download two prerequisites from the AIX Toolbox for Linux Applications (glib & gtk+). Download the packages from the following locations:
- Install
the packages after downloading them: Use the following
command:
rpm -Uvh glib-1.2.10-2.aix4.3.ppc.rpm gtkplus-1.2.10-4.aix5.1.ppc.rpm
- Download
the latest supported version of Mozilla (1.7 or later) for
AIX. Download Mozilla for AIX from the following location:
http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=mozilla
Download the installp image and install it from smit.
The Mozilla images distributed on the http://www.mozilla.org Web site are not provided by IBM. IBM has not tested and does not support the download from the non-IBM Web site. Download the Mozilla images from the IBM Web site to verify that the version that you download is tested and supported.
- Optional: Export
the location of the supported browser.
Export the location of the supported browser using a command that identifies the actual location of the browser.
For example, if the Mozilla package is in the bin /mozilla directory, use the following command:
EXPORT BROWSER=/usr/bin/mozilla
-
Silent installation only: Make an allowance for a
known ISMP problem that causes a call to the Xwindows service during a
silent installation.
The DISPLAY environment variable on your AIX machine might point to an X server that is not logged in. Two common scenarios can cause this to occur:
- Your AIX machine has an X server running, but the X server is stuck at the graphical login screen because you have not yet logged in.
- Your AIX machine is configured to display X Windows applications on a remote X server that is not logged in.
A silent installation can hang in either case as ISMP calls Xwindows services.
Two solutions exist:
- Login to the local X server through the graphical user interface before beginning the silent installation.
- Export the DISPLAY
environment variable to point to null or blank.
EXPORT DISPLAY=null
Prepare HP-UX systems for installation
This topic describes how to prepare an HP-UX system for the installation of IBM WAS, V6 products.
The installation uses a ISMP wizard. Use the graphical interface of the wizard. We can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Use the following procedure to prepare the operating system for the installation of WAS products.
- Log on as root.
We cannot install the product correctly as a non-root user.
If you create a copy of the product CD-ROM, do so as root. Copies made from non-root users do not preserve the correct file attributes and do not work.
In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Optional: Download and install the Mozilla Web browser so that use the launchpad application on the product disc. If you do not have the Mozilla Web browser, download and install the browser from http://www.mozilla.org.
- Optional: Export
the location of the supported browser. Export the location of the
supported browser using a command that identifies the actual location of
the browser.
For example, if the Mozilla package is in the bin /mozilla directory, use the following command:
EXPORT BROWSER=/opt/bin/mozilla
- Stop all WAS-related Java processes on the machine where you are installing the product.
- Stop any Web server process such as the IBM HTTP Server.
- Provide
adequate disk space.
The base WAS product requires the following disk space:
- 980 MB for...
/opt/IBM/WebSphere/AppServer
-
The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.
Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.
- 100 MB for the /tmp directory
-
The temporary directory is the working directory for the installation program.
- 1080 MB total requirement
-
This amount is the total space requirement when installing the product from the CD.
The following space is required for the IBM HTTP Server product:
- 110 MB for...
/opt/IBMIHS
-
The IBM HTTP Server product requires this space.
- 25 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The run-time module is gsk7bas for HP-UX platforms.
The following space is the maximum amount that is required for the Web server plug-ins for WAS:
- 280 MB for...
/opt/IBM/WebSphere/plugins
-
The Web server plug-ins require this disk space.
- 25 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The following space is required for the IBM WAS Clients:
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:
- For V4.0.x: The size of enterprise archive (EAR) files
- For V5.0.x: The size of EAR files
- 980 MB for...
- Set
kernel values to support Application Server. Several HP-UX kernel
values are typically too small for the product.
To set kernel parameters, perform the following steps:
- Log into the host machine as root.
- Determine the physical
memory, which know to avoid setting certain kernel parameters
above the physical capacity:
- Start the HP-UX System Administration Manager (SAM) utility.
- Select...
Performance Monitors | System Properties | Memory
- Note the value for Physical Memory and click OK.
- Exit from the SAM utility.
- Set the maxfiles and
maxfiles_lim parameters to at least
4096. (The following table recommends 8000 and
8196, respectively. You must first edit the
/usr/conf/master.d/core-hpux file, so the SAM
utility can set values greater than 2048:
- Open the /usr/conf/master.d/core-hpux file in a text editor.
- Change the line," *range maxfiles<=2048" to "*range maxfiles<=60000"
- Change the line, "*range maxfiles_lim<=2048" to "*range maxfiles_lim<=60000"
- Save and close the file.
Old values might be stored in...
/var/sam/boot.config file
Force the SAM utility to create a new boot.config file:
- Move the existing version of...
/var/sam/boot.config
...to another location, such as the /tmp directory.
- Start the SAM utility.
- Select...
Kernel Configuration | Configurable Parameters
When the Kernel Configuration window opens, a new boot.config file exists.
Alternatively, rebuild the boot.config file with the following command:
# /usr/sam/lbin/getkinfo -b
- Move the existing version of...
- Set new kernel parameter
values:
- Start the SAM utility.
- Click...
Kernel Configuration | Configurable Parameters
- For each of the parameters in the following table, perform this procedure:
- Highlight the parameter to change.
- Click...
Actions | Modify Configurable Parameter
- Type the new value in the Formula/Value field.
- Click OK.
Typical kernel settings for running WAS display in the following table:
Parameter Value dbc_max_pct 25 maxdsiz 805306358 maxdsiz 2048000000 (when running multiple profiles on the same system) maxfiles_lim 8196 (Change this one before maxfiles.) maxfiles 8000 maxssiz 8388608 maxswapchunks 8192 max_thread_proc 3000 maxuprc 512 maxusers 512 msgmap 2048 msgmax 65535 msgmax 131070 (when running multiple profiles on the same system) msgmnb 65535 msgmnb 131070 (when running multiple profiles on the same system) msgmni 50 msgseg 32767 msgssz 32 msgtql 2046 nfile 58145 nflocks 3000 ninode 60000 nkthread 7219 nproc 4116 npty 2024 nstrpty 1024 nstrtel 60 sema 1 semaem 16384 semmap 514 semmni 2048 semmns 16384 semmnu 1024 semume 200 semvmx 32767 shmmax 2147483647 shmem 1 shmmni 1024 shmseg 1024 STRMSGSZ 65535 When WebSphere Application Server and IBM DB2 are on the same machine, some kernel values are higher than those shown in the preceding table.
- Click...
Actions | Process New Kernel
- Click Yes on the information window to confirm your decision to restart the machine.
Follow the on-screen instructions to restart your machine and to enable the new settings.
- If you plan to redirect displays to non-HP machines, do the following before running the WAS installation wizard:
- Issue the following command to obtain information on all the public locales that are accessible to your application:
# locale -a
- Choose a value for your system from the output that is displayed and set the LANG environment variable to this value. Here is an example command that sets the value of LANG to en_US.iso88591
# export LANG=en_US.iso8859
- Issue the following command to obtain information on all the public locales that are accessible to your application:
- Verify that prerequisites and corequisites are at the required release levels.
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware and software Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
- Verify the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your operating system, verify that the system cp command is used.
- Type which cp at the command prompt before running the installation program for the WAS product.
- Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example, assume that the output is similar to the following message:
.../freeware/bin/cp
If so, remove the directory from the PATH.
- Install the WAS product.
- Add the freeware directory back to the PATH.
If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in...
install_root/java
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, install the Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
- Verify that the Java 2 SDK on your copy of the product CD is functioning correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
- Verify the Java 2 SDK version. Type the following command:
/mnt/JDK/repository/prereq.jdk/java/bin
./java -versionThe command completes successfully with no errors when the Java 2 SDK is intact.
- Verify the Java 2 SDK version. Type the following command:
Prepare Linux systems for installation
The installation uses a ISMP wizard. Use the graphical interface of the wizard. We can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Use the following procedure to prepare the operating system for the installation of WAS products.
- Log on as root.
We cannot install the product correctly as a non-root user.
If you create a copy of the product CD-ROM, do so as root. Copies made from non-root users do not preserve the correct file attributes and do not work.
In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Optional: Download and install the Mozilla Web browser so that use the launchpad application on the product disc. If you do not have the Mozilla Web browser, download and install the browser from http://www.mozilla.org.
- Optional: Export the location of the supported browser. Export the location of the supported browser using a command that identifies the actual location of the browser.
For example, if the Mozilla package is in the bin /mozilla directory, use the following command:
EXPORT BROWSER=/opt/bin/mozilla
- Stop all WAS-related Java processes on the machine where you are installing the product.
- Stop any Web server process such as the IBM HTTP Server.
- Provide adequate disk space.
The base WAS product requires the following disk space:
- 930 MB for...
/opt/IBM/WebSphere/AppServer
-
The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.
Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.
- 100 MB for the /tmp directory
-
The temporary directory is the working directory for the installation program.
- 1030 MB total requirement
-
This amount is the total space requirement when installing the product from the CD.
The following space is the maximum amount that is required for the Web server plug-ins for WAS:
- 200 MB for the /usr/IBM/WebSphere/plugins directory
-
The Web server plug-ins require this disk space.
- 25 MB for the /usr/ibm/gsk7 directory
-
The Tivoli Global Security Kit requires this space.
The run-time module is gskkm.rte.
The following space is required for the IBM HTTP Server product:
- 110 MB for...
/opt/IBMIHS
-
The IBM HTTP Server product requires this space.
- 25 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The run-time module is gsk7bas.i386.rpm for Linux distributed platforms and gsk7bas.s390.rpm for Linux for S/390 platforms.
The following space is required for the IBM WAS Clients:
The following space is required for the Application Server Toolkit:
- 550 MB maximum for...
/opt/IBM/WebSphere/AST
-
The Application Server Toolkit does not include an integrated test environment.
Install the WAS product to create a test environment.
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:
- For V4.0.x: The size of enterprise archive (EAR) files
- For V5.0.x: The size of EAR files
- 930 MB for...
- Verify
that prerequisites and corequisites are at the required release
levels.
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware and software Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
- Provide
necessary prerequisites for Red Hat Enterprise Linux V3.0. A known
limitation exists in the prerequisites checker program when examining
prerequisite packages on Linux systems. Although not all of the
following packages are required for V6, the packages are required
if you install V6 to coexist with a V5.x installation.
You must install the following packages on Red Hat Enterprise Linux V3.0 for xSeries platforms:
- compat-gcc-7.3-2.96.122
- compat-libstdc++-7.3-2.96.122
- compat-libstdc++-devel-7.3-2.96.122
- compat-glibc-7.x-2.2.4.32.5
- compat-gcc-c++-7.3-2.96.122
- compat-db-4.0.14-5
- rpm-build-4.2.1-4.2
The following package is required for Red Hat Enterprise Linux V3.0 for pSeries platforms: rpm-build-4.2.1-4.2.
You must install the following packages on Red Hat Enterprise Linux V3.0 for S/390 (z/VM and VM/ESA) platforms:
- compat-db-4.0.14-5
- compat-pwdb-0.62-3
- compat-libstdc++-7.2-2.95.3.77
- rpm-build-4.2.1-4.2
We can install a later release of any of these packages.
- Upgrade
Red Hat Enterprise Linux V3.0 to service level 2 (update 2) or service
level 3 (update 3).
Upgrade the RHEL 3.0 service level by downloading and installing the service updates from Red Hat.
If you do not upgrade the service level, certain national language issues in the released version of GLIBC included in Red Hat Enterprise Linux V3 might cause Java virtual machine (JVM) failures due to segmentation faults. These failures can occur during installation when the locale is set to anything other than an English locale.
Do not install, log off, and log back on when you are installing from the operator console attached to the machine. This can produce segmentation faults that cause the installation to fail, as described in Troubleshooting the installation.
- Prepare
the SuSE Linux Enterprise Server 8.0 - Powered by UnitedLinux 1.0
operating platform for WAS installation.
- Install SP3 for the
United Linux 1.0 operating platform to let you use the Launchpad.
It is your responsibility to install this service pack. The prereqChecker function of the installer cannot detect service pack versions definitively on United Linux. Kernel unames and versions between 8.0 and 8.0.3 are identical. No signature RPM denotes a service pack install.
- Use the IBM Developer Kit that WAS provides to support the Java 2 SDK on the SuSE SLES 8.0 operating system to avoid potential problems when uninstalling an interim fix or a fix pack. To use the IBM Developer Kit, remove the java2-jre-1.3.1-524 and java2-1.3.1-524 RPMs from the machine before installing WAS.
- Install SP3 for the
United Linux 1.0 operating platform to let you use the Launchpad.
- Correct
font problems on SuSE Linux Enterprise Server 8.0 in Simplified Chinese
and Traditional Chinese locales.
On the Linux for Power platform that SuSE Linux Enterprise Server 8.0 provides, a missing package causes a font problem. The ttf-hanyi package is not installed during the normal product installation of the SuSE 8.0 operating system. The missing package causes the Installation wizard for WebSphere Application Server products to display garbled characters in the Simplified Chinese locale and in the Traditional Chinese locale.
Copy the ttf-hanyi-2021016-0.noarch.rpm package on the SuSE 8.0 for i386 CD to the Power PC system. Install the package on the Power PC machine and reboot the machine to solve the problem.
- Verify
the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your operating system, verify that the system cp command is used.
- Type which cp at the command prompt before running the installation program for the WAS product.
- Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example, assume that the output is similar to the following message: .../freeware/bin/cp. If so, remove the directory from the PATH.
- Install the WAS product.
- Add the freeware directory back to the PATH.
If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in...
install_root/java
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, install the Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
- Verify
that the Java 2 SDK on your copy of the product CD is functioning
correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
cd /mnt/JDK/repository/prereq.jdk/java/bin
- Verify
the Java 2 SDK version. Type the following command:
./java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
Prepare Solaris systems for installation
This topic describes how to prepare Solaris systems for the installation of IBM WAS, V6 products.
The installation uses a ISMP wizard. Use the graphical interface of the wizard. We can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Use the following procedure to prepare the operating system for the installation of WAS products.
- Log on as root.
We cannot install the product correctly as a non-root user.
If you create a copy of the product CD-ROM, do so as root. Copies made from non-root users do not preserve the correct file attributes and do not work.
In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Optional: Download and install the Mozilla Web browser so that use the launchpad application on the product disc. If you do not have the Mozilla Web browser, download and install the browser from http://www.mozilla.org.
- Optional: Export
the location of the supported browser. Export the location of the
supported browser using a command that identifies the actual location of
the browser.
For example, if the Mozilla package is in the bin /mozilla directory, use the following command:
EXPORT BROWSER=/opt/bin/mozilla
- Stop all WAS-related Java processes on the machine where you are installing the product.
- Stop any Web server process such as the IBM HTTP Server.
-
Provide
adequate disk space.
The base WAS product requires the following disk space:
- 930 MB for...
/opt/IBM/WebSphere/AppServer
-
The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.
Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.
- 100 MB for the /tmp directory
-
The temporary directory is the working directory for the installation program.
- 1030 MB total requirement
-
This amount is the total space requirement when installing the product from the CD.
The following space is required for the IBM HTTP Server product:
- 110 MB for...
/opt/IBMIHS
-
The IBM HTTP Server product requires this space.
- 25 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The following space is the maximum amount that is required for the Web server plug-ins for WAS:
- 200 MB for...
/opt/IBM/WebSphere/plugins
-
The Web server plug-ins require this disk space.
- 35 MB for...
/opt/ibm/gsk7
-
The Tivoli Global Security Kit requires this space.
The following space is required for the IBM WAS Clients:
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:
- For V4.0.x: The size of enterprise archive (EAR) files
- For V5.0.x: The size of EAR files
- 930 MB for...
- Set
kernel values to support Application Server. Several Solaris kernel
values are typically too small.
Before installing, review the machine configuration:
sysdef -i
The kernel values are set in the /etc/system file, as shown in the following example.
set shmsys:shminfo_shmmax = 4294967295 set shmsys:shminfo_shmseg = 1024 set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semaem = 16384 set semsys:seminfo_semmni = 1024 set semsys:seminfo_semmap = 1026 set semsys:seminfo_semmns = 16384 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set semsys:seminfo_semmnu = 2048 set semsys:seminfo_semume = 256 set msgsys:msginfo_msgmap = 1026 set msgsys:msginfo_msgmax = 65535 set rlim_fd_cur=1024
We can change kernel values by editing the /etc/system file then rebooting the operating system. For more information about setting up the Solaris system, see the Solaris System Administration documentation. For example, the Solaris Tunable Parameters Reference Manual.
Queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system.
- Verify
that prerequisites and corequisites are at the required release
levels.
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware and software Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
Solaris 9 SPARC workstations require the following patches to fix certain :
- 112874-16 SunOS 5.9: patch libc
- 113319-12 SunOS 5.9: libnsl nispasswdd patch
- 115545-01 SunOS 5.9: nss_files patch
- 115542-01 SunOS 5.9: nss_user patch
- 115544-01 SunOS 5.9: nss_compat patch
Solaris 8 SPARC workstations require the following patches to fix certain :
- 115827-01 SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch
- 115583-01 SunOS 5.8: /usr/lib/nss_user.so.1 patch
- 108820-02 SunOS 5.8: nss_compat.so.1 patch
- 113648-02 SunOS 5.8: /usr/sbin/mount patch
- 108993-27 SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch
- 108528-24 SunOS 5.8: kernel update patch
Refer to the IBM WAS supported hardware and software Web site for a complete list of required patches and to determine whether your operating system is supported when you receive a message from the prereqChecker program. The Web site lists all supported operating systems and the operating system fixes and patches that install to have a compliant operating system.
- Verify
the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your operating system, verify that the system cp command is used.
- Type which cp at the command prompt before running the installation program for the WAS product.
- Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example, assume that the output is similar to the following message: .../freeware/bin/cp. If so, remove the directory from the PATH.
- Install the WAS product.
- Add the freeware directory back to the PATH.
If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in...
install_root/java
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, install the Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
- Verify
that the Java 2 SDK on your copy of the product CD is functioning
correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
cd /mnt/JDK/repository/prereq.jdk/java/bin
- Verify
the Java 2 SDK version. Type the following command:
./java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
- Change
directories to the /mnt/JDK/repository/prereq.jdk/java/bin
directory on the product CD-ROM. For
example:
Prepare Windows systems for installation
This topic describes how to prepare your Windows systems for the installation of IBM WAS, V6 products.
The installation uses a ISMP wizard. Use the graphical interface of the wizard. We can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Use the following procedure to prepare the operating system for the installation of WAS products.
- Log on to a user ID that
belongs to the administrator group.
Log on as a member of the administrator group to successfully install the product. We cannot create Windows services from a user ID that does not belong to the administrator group. The creation of Windows services requires the user to have the advanced user rights Act as part of the operating system and Log on as a service.
- Optional: Download the latest supported version of Internet Explorer so that use the launchpad on the product disc. Download Internet Explorer 6 from the following location:
- Stop all WAS-related Java processes on the machine where you are installing the product.
- Stop any Web server process such as the IBM HTTP Server.
- Stop all instances of the process_spawner.exe program.
- Provide
adequate disk space.
The base WAS product requires the following disk space:
- 930 MB for the C:\Program Files\IBM\WebSphere\AppServer directory
-
The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.
Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.
- 100 MB for the C:\temp directory
-
The temporary directory is the working directory for the installation program.
- 1030 MB total requirement
-
This amount is the total space requirement when installing the product from the CD.
The following space is required for the IBM HTTP Server product:
- 110 MB for the C:\Program Files\IBM HTTP Server directory
-
The IBM HTTP Server product requires this space.
- 25 MB for the C:\Program Files\ibm\gsk7 directory
-
The Tivoli Global Security Kit requires this space.
The following space is the maximum amount that is required for the Web server plug-ins for WAS:
- 200 MB for the C:\Program Files\IBM\WebSphere\Plugins directory
-
The Web server plug-ins require this disk space.
- 25 MB for the C:\Program Files\ibm\gsk7 directory
-
The Tivoli Global Security Kit requires this space.
The following space is required for the Application client for WAS:
- 150 MB for the C:\Program Files\IBM\WebSphere\AppClient directory
-
The amount of space required to install the application clients is actually less than 150 MB. The amount of space depends on the clients that you install as features.
The following space is required for the Application Server Toolkit:
- 550 MB maximum for the C:\Program Files\IBM\WebSphere\AST directory
-
The Application Server Toolkit does not include an integrated test environment.
Install the WAS product to create a test environment.
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:
- For V4.0.x: The size of enterprise archive (EAR) files
- For V5.0.x: The size of EAR files
- Verify
that prerequisites and corequisites are at the required release
levels.
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS supported hardware and software Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
-
Verify
that the Java 2 SDK on your copy of the product CD is functioning
correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
- Change
directories to the \win\WAS\jdk\java\bin directory on the product
CD-ROM. Type the following
command:
cd CD_Drive_D:\WAS\jdk\java\bin
- Verify
the version of the Java 2 SDK. Type the following command:
.\java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
- Change
directories to the \win\WAS\jdk\java\bin directory on the product
CD-ROM. Type the following
command:
Troubleshooting installation
A successful installation of a WAS product installs the core product files and creates the server1 Application Server.
The files...
install_root/logs/log.txt
...and...
install_root/logs/wasprofile/wasprofile_create_default.log file
...record installation status.
The installer program records the following indicators of success in the logs:
- INSTCONFSUCCESS
- INSTCONFPARTIALSUCCESS
- INSTCONFFAILED
If the error happens early in the installation, look for the log.txt file in the system temporary area. The installation program copies the log from the temporary area to the logs directory at the end of the installation.
Perform the following procedure to troubleshoot an installation.
- Use the First steps console to run the installation verification test (IVT).
The installation wizard can start the First steps console at the end of installation. Select Installation verification. Check...
install_root/profiles/default/logs/ivt.log
...file for a summary of test results. Correct any errors and retry. If you performed a custom installation, the location of the default profile is in the profiles installation root directory that you selected during the installation.
If you created another profile using the Profile creation wizard or the wasprofile command, the location of the profile and the name of the profile are different than what is displayed in the example.
- Check the installation log files for errors after installing:
During installation, a single entry in the...
/logs/log.txt
...file points to the temporary log file, either...
%TEMP%\log.txt
...on Windows platforms, or...
/tmp/log.txt
...on Linux and UNIX platforms. The installation program copies the file from the temporary directory to...
install_root/logs/log.txt
...at the end of the installation.
If the installation fails and...
install_root/logs/log.txt
...has only this one pointer to the temporary directory, open the log.txt file in the temporary directory. The log might have clues to the installation failure. Uninstalling creates...
install_root/logs/uninstlog.txt
Log more information when ISMP cannot start the Installation wizard.
Verify or troubleshoot...
installation if the install_root/logs/log.txt
...file or...
profiles_install_root/profile/logs/pctLog.txt
...file does not contain a record of any problems, but problems exist. If...
profiles_install_root/profile
...directory exists, the pctLog.txt file is in the logs directory. If the error happens early in the installation, look for the logs in the system temporary area. The installation program copies the logs from the system temporary area to the logs directory at the end of the installation.
If...
profiles_install_root/profile
...directory does not exist, the pctLog.txt file is in the USER_HOME directory and is named .$~pctLog.txt. Issue the env command to display the USER_HOME directory on Linux and UNIX systems. See the environment variable settings on Windows system to display the value of the variable.
Certain events can prevent ISMP from starting the Installation wizard. Such an event is not enough disk space to launch the Installation wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the ISMP program to fail to start the installation wizard. The syntax of the install command for logging such events is:
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALLThe following example is for AIX systems:
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALLThe following example is for Linux systems, HP-UX systems, and Solaris systems:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALLThe following example is for Windows systems:
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALLLog file names and locations
The following information shows the log files for all of the installable components on the product disc.
Log files for IBM HTTP Server
Windows system log path name Linux and UNIX operating system log path name C:\Program Files\IBM HTTP Server\log.txt
C:\Program Files\IBM HTTP Server\ihsv6_install.log
AIX: /usr/IBMHttpServer/ log.txt
AIX: /usr/IBMHttpServer/ ihsv6_install.log
Linux, HP-UX, Solaris: /opt/IBMHttpServer/ log.txt
Linux
/opt/IBMHttpServer/ ihsv6_install.log
Log files for Application client for WebSphere Application Server
Table 11. Installation log locations when installing the Application Clients for WAS Windows system log path name Linux and UNIX operating system log path name C:\Program Files\IBM\WebSphere\AppClient\logs\WAS.Client.install.log usr/IBM/WebSphere/AppClient/logs/WAS.Client.install.log
Linux
/opt/IBM/WebSphere/AppClient/logs/WAS.Client.install.log
The wasprofile_create_profile.log file is an XML file that contains a record of the events that occur during the creation of the last profile.
In addition to the date tag at the beginning of the file, other tags of interest in the log files include the sequence tag, the level tag, the method tag, and the message tag:
- The sequence tag records the sequence of events that occur during the creation of the profile.
- The level tag is an early
indicator of event status:
- INFO
- Indicates a normal event.
- WARNING
- Indicates an event that occurred with errors that do not prevent the creation of the profile.
- ERROR
- Indicates an event that prevents the creation of the profile.
- The method tag indicates the name of the routine that recorded the event.
- The message tag describes the event and contains any data returned by the method.
The following stanza is an example of how an event is documented in each log file:
<record> <date>2004-09-08T11:51:39</date> <millis>1094658699225</millis> <sequence>0</sequence> <logger>com.ibm.ws.profile.WSProfile</logger> <level>INFO</level> <class>com.ibm.ws.profile.WSProfile</class> <method>getRegistryFile</method> <thread>10</thread> <message>Returning registry file at: C:\NDV6\IBM\WebSphere\AppServer\properties\profileRegistry.xml </message> </record>Log files created during the creation of the Application Server profile
In addition to the logs created within the core product files, the following logs are created in...
install_root/profiles/default/logs
...when the Profile creation wizard or the wasprofile command creates an Application Server profile:
- activity.log
- Compiled activity log from various installation activities
- amjrte_config.log
- Tivoli Access Manager configuration log for its Java Runtime Environment
- collect_metadata.log
- Collects metadata information about managed objects in the system to evaluate and prevent potential installation conflicts
- createDefaultServer.log
- A log from wsadmin recording the creation of the server1 process in the default profile
- createshortcutforprofile.log
- Windows tool log for creating menu entries and shortcuts
- defaultapp_config.log
- JACL script log from configuring default application resources
- defaultapp_deploy.log
- Application DefaultApplication installation log
- Node_name Service.log
- Start and stop events for server1
- filetransfer_config.log
- Application filetransfer installation log
- hamanager_config.log
- Configuration log for the high availability application
- ivt_config.log
- Application ivtApp installation log
- mejb_config.log
- Application ManagementEJB installation log
- pctLog.txt
- Log created when using
the Profile creation wizard to create a profile. This log is not created
when using the wasprofile command directly.
This log is not created during installation of the product.
- query_config.log
- Application Query installation log
- samples_config.log
- Configuration log for the PlantsByWebSphere Samples application
- samples_install.log
- Installation log for the SamplesGallery and PlantsByWebSphere Samples applications
- scheduler.cal_config.log
- Application SchedulerCalendars installation log
- SIBDefineChains.log
- Creation log for service integration bus endpoints, inbound channels and channel chains, outbound thread pool, and outbound channel and channel chains
- SIBDeployRA.log
- Deployment log for the service integration bus function
- webui_config.log
- Application administrative console installation log
- winservice_config.log
- Node_name service log for the Windows service created for server1
The following logs are created in...
install_root/profiles/default/logs/server1
- startServer.log
- Log of start server events
- stopServer.log
- Log of stop server events
- SystemErr.log
- Record system errors
- SystemOut.log
- Log of all activity within the system
- trace.log
- Log of all traced events within the system
The following logs are created in...
install_root/profiles/default/logs/ffdc
- server1_exception.log
- First failure data capture log for server1 errors
- server1_numeric_identifier.txt
- Any first failure data capture logs
- Verify
that no files exist in...
install_root/classes
IBM Support sometimes queues work for customers and provides test or debugging fixes. A common location for the fixes is in...
install_root/classes
By default,...
install_root/classes
...picked up first in the WAS class path to let it override other classes.
Putting a fix in the directory lets you verify that the fix does indeed solve your problem. After verifying that the fix solves the problem, you are supposed to delete the fix from...
install_root/classes
...to return the system to a working state.
If you do not remove such fixes from...
install_root/classes
...we can experience errors.
- Uninstall the product, if possible, and reinstall after turning on tracing if the error logs do not contain enough information to determine the cause of the problem.
- Report the stdout and stderr logs to the console window, by adding the -is:javaconsole parameter to the install command:
- Linux AIX, HP-UX, Solaris
install -is:javaconsole
Capture the stream to a file with the following commands:
install -is:javaconsole > captureFileName.txt 2>&1
-
install.exe -is:javaconsole
Capture the stream to a file with the following commands:
install -is:javaconsole > drive:\captureFileName.txt
- Linux AIX, HP-UX, Solaris
- Capture additional information to a log of your choice with the -is:log file_name option.
- Turn on additional
installation logging by passing the
-W
Setup.product.install.logAllEvents="true" parameter to the
install
command:
-
Linux
AIX, HP-UX, Solaris
install -W Setup.product.install.logAllEvents="true"
-
install -W Setup.product.install.logAllEvents="true"
-
Linux
AIX, HP-UX, Solaris
- Report the stdout and stderr logs to the console window, by adding the -is:javaconsole parameter to the install command:
- Use
the First steps console or the command line method to start the
Application Server.
Start the First steps console for a particular node:
install_root/profiles/profile/firststeps/firststeps.sh
Start the server from the command line:
- Change directories to...
install_root/profiles/profile/bin
...in the profile.
- Start the server process.
- Linux AIX, HP-UX, Solaris ./startServer.sh server1
- startServer server1
- Change directories to...
- Verify
whether the server starts and loads properly by looking for a running
Java process and the Open for e-business message in the
SystemOut.log and
SystemErr.log files.
If no Java process exists or if the message does not appear, examine the same logs for any miscellaneous errors. Correct any errors and retry.
We can find the SystemOut.log and SystemErr.log files in...
install_root/profiles/default/logs/server1
(Linux and UNIX platforms) or...install_root\profiles\default\logs\server1
...(Windows platforms) directory in an Application Server profile.
- Refer to the plug-in configuration documentation, if you have installed plug-ins and the Web server does not come up properly.
-
Start the
Snoop servlet to verify the ability of the Web server to retrieve an
application from the Application Server.
Test your environment by starting your Application Server, your Web server, and using the snoop servlet with an IP address.
- Start
the Application Server.
Change directories to...
install_root/profiles/profile/bin
...and run the startServer command:
- Linux AIX, HP-UX, Solaris ./startServer.sh server1
- startServer server1
- Start
the IBM HTTP Server or the Web server that you are using.
Use a command window to change the directory to the IBM HTTP Server installed image, or to the installed image of your Web server. Issue the appropriate command to start the Web server, such as these commands for IBM HTTP Server:
To start the IBM HTTP Server from the command line:
Access the apache and apachectl commands in the IBMHttpServer/bin directory.
- Linux AIX, HP-UX, Solaris ./apachectl start
- apache
- Point
your browser to http://localhost:9080/snoop to test the internal
HTTP transport provided by the Application Server. Point your browser to
http://Host_name_of_Web_server_machine/snoop to test
the Web server plug-ins.
The HTTP Transport port is 9080 by default and must be unique for every profile. The port is associated with a virtual host named default_host, which is configured to host the installed DefaultApplication and any installed Samples. The snoop servlet is part of the DefaultApplication. Change the port to match your actual HTTP Transport port.
- Verify
that snoop is running.
Either Web address should display the Snoop Servlet - Request/Client Information page.
- Remote IBM HTTP Server only: Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local Web servers.
- Run the htpasswd command on the Web server machine to create the administrative user ID and password information.
- Use the administrative console of the Application Server to enter the User ID and password information that you created for the administrative user of IBM HTTP Server. Go to...
Servers | Web server | Web_server_definition | Remote Web server administration
- Start
the Application Server.
- Start
the WAS administrative console.
- Start the Application Server.
- Point
your browser to http://localhost:9060/ibm/console.
The HTTP Admin port is 9060 by default and must be unique for the administrative console of each stand-alone Application Server. The port is associated with a virtual host named admin_host, which is configured to host the administrative console, which is installed by default as a system application. Change the port to match your actual HTTP Admin port.
If you have problems accessing the administrative console after installation, check the installAdminConsole.log file for a failure indication. Clean up the system temporary directory and reinstall the administrative console using the wsadmin scripting facility.
- Type any ID and click OK at the administrative console window.
The server starts. The administrative console starts. We can access the administrative console through the browser. The administrative console accepts your login.
- Resolve
any IP address caching problems.
By default, the Java 2 SDK caches the IP address for the domain name service (DNS) naming lookup. After resolving the host name successfully, the IP address stays in the cache. By default, the cache entry remains forever.
This default IP caching mechanism can cause problems, as described in the following problem scenarios.
Problem scenario 1
Suppose the Application Server at host1.ibm.com has an initial IP address of 1.2.3.4. When a client at host2.ibm.com conducts a DNS lookup of host1.ibm.com, the client stores the 1.2.3.4 address in the cache. Subsequent DNS name lookups return the cached value, 1.2.3.4.
The cached value is not a problem until the host1.ibm.com IP address changes, to 5.6.7.8, for example. The client at host2.ibm.com does not retrieve the current IP address, but always retrieves the previous address from the cache.
If this scenario occurs, the client cannot reach host1.ibm.com unless you stop and restart the client process.
Problem scenario 2
Suppose the Application Server at host1.ibm.com has an initial IP address of 1.2.4.5. Although the IP address of the application server does not change, a network outage can record an exception code as the IP address in the cache, where it remains until the client is restarted on a working network.
For example, if the client at host2.ibm.com disconnects from the network because of an unplugged cable, the disconnected lookup of the Application Server at host1.ibm.com fails. The failure causes the IBM Developer Kit to put the special exception code entry into the IP address cache.
Subsequent DNS name lookups return the exception code, which is java.net.UnknownHostException.
Use the IP address cache setting
We can always stop and restart a deployment manager process to refresh its IP address cache. However, this process might be expensive or inappropriate.
The networkaddress.cache.ttl (public, JDK1.4) and sun.net.inetaddr.ttl (private, JDK1.3) parameters control IP caching. The value is an integer that specifies the number of seconds to cache IP addresses. The default value, -1, specifies to cache forever. A value of zero (0) is a specification to never cache.
Use a zero (0) value is not recommended for normal operation. If you do not anticipate network outages or changes in IP addresses, use the cache forever setting. The never caching setting introduces the potential for DNS spoofing attacks.
For more information about the Java 2 SDK
The Java 2 SDK, Standard Edition 1.4 Web site at http://java.sun.com/j2se/1.4/docs/guide/net/properties.html describes the private sun.net.inetaddr.ttl property, which works in both Java 2 SDK, Standard Edition 1.3 (WAS V5.0.0, V5.0.1, and V5.0.2) and Java 2 SDK, Standard Edition 1.4 (WAS V5.1 and V6).
This procedure results in using some simple procedures to debug errors that might be occurring in the installation.
The Troubleshooting installation problems contains more detailed debugging and reporting instructions.
See Installation component troubleshooting tips for more information about troubleshooting the installation.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering the information that we need to resolve a problem. Before opening a PMR, see the IBM Support page.
Installation component troubleshooting tips
If you are having problems installing your WAS product, follow these steps to resolve the problem:
- If possible, follow the steps that are outlined in Troubleshooting installation.
- Browse the relevant log files for clues:
- The main installation log file:
install_root/logs/log.txt
- The Profile creation wizard log file:
install_root/profiles/profile/logs/pctLog.txt
...when you create a profile with the Profile creation wizard.
- The profile creation log for creating the profile:
install_root/logs/wasprofile/wasprofile_create_profile.log
- IBM HTTP Server logs:
ihs_install_root/log.txt
ihs_install_root/ihsv6_install.log - The log files produced when the default application .ear file is installed are:
install_root/profiles/profile/logs/defaultapp_config.log
install_root/profiles/profile/logs/defaultapp_deploy.log - Other logs for other applications for a profile in...
install_root/profiles/profile/logs
- The main installation log file:
- Verify that you have installed the correct level of dependent software, such as operating system version and revision level, by reviewing http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.php.
If none of these steps solves the problem:
Check to see if the problem is identified and documented using the links in Diagnosing and fixing problems: Resources for learning.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem,contact IBM support for further assistance.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
Troubleshooting installation problems
Select the problem that you are having with the WAS installation:
- I need information about Troubleshooting Web server plug-ins installation and removal.
- Installation either completes with errors or warnings, or hangs.
- There are Messages issued during installation and profile creation
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Troubleshooting installation.
If you did not find your problem listed, contact IBM support.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
Installation either completes with errors or warnings, or hangs
Errors while installing the product
If the WAS installation program indicates that errors were encountered while installing the product:
- Browse the log files in...
install_root/logs directory
...and in...
install_root/profiles/profile/logs
...for clues. Pay particular attention to the main installation log file, log.txt.
- Check the command prompt from which the installation panel was launched for error messages.
- Look up any error or warning messages in the message reference table by selecting the "Reference" view in the information center navigation and expanding the "Messages" heading.
- Review Troubleshooting installation.
Problems installing or starting Apache or IBM HTTP Server
What kind of error are you seeing?
- "Failed to initialize GSK environment" error appears when trying to start Apache
- IBM HTTP Server (IHS) on Windows does not start, error WSADuplicateSocket failed for socket appears in error.log.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
"Failed to initialize GSK environment" error appears when trying to start Apache
The following messages may appear in Apache's error log file when you attempt to start Apache:
[Wed Aug 27 19:21:59 2003] [error] lib_security: initializeSecurity: Failed to initialize GSK environment
[Wed Aug 27 19:21:59 2003] [error] ws_transport: transportInitializeSecurity: Failed to initialize security
[Wed Aug 27 19:21:59 2003] [error] ws_server: serverAddTransport: Failed to initialize securityThese messages are most common after building Apache from the downloadable source code and installing Apache separately from WAS.
If SSL Transport (HTTPS) is defined in the plugin-cfg.xml file, the plug-in will try to load the Global Security Kit (GSKit) library libgsk7ssl.so. The error messages appear in the error log file if the level 7 GSKit libgsk7ssl.so is not installed on your system. To correct these errors, try one of the following:
- Remove the transport section that has "https" in the plugin-cfg.xml file
- Install the level 7 GSKit Note: The GSKit installs automatically if you install either the IBM HTTP Server (IHS) product or the Web server plug-ins for WebSphere Application Server from the product disc.
For details and help on the Apache web server, visit the Apache web site http://httpd.apache.org/.
IBM HTTP Server on Windows does not start, error WSADuplicateSocket failed for socket appears in error.log
If your installation of IBM HTTP Server (IHS) on a Windows platform will not start, you may find a message similar to the following in the log\error.log file of your IHS installation:
"[crit] (10045) The attempted operation is not supported for the type of object referenced: Parent: WSADuplicateSocket failed for socket nnnn
This problem occurs when IHS is run on a system with a Virtual Private Networking client such as Aventail Connect. Aventail Connect is a Layered Service Provider (LSP) that intercepts calls between the Winsock 2 API and Window's native Winsock 2 implementation. The failure occurs because Aventail Connect does not implement WASDuplicateSocket(). The interception still takes place when Aventail Connect is shut down.
To correct the problem try one of the following:
- Reboot the machine, or
- Uninstall the LSP product
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem.
Messages issued during installation and profile creation
What kind of problem are you having?
- Error: The input line is too long
- Note: The following file systems will be expanded during the installation
- The disk space is nn Mbyte less than required. The installation cannot continue.
- Specify a different directory or perform a manual uninstall
- Error: /usr/opt/ibm/gskta/bin/gsk7ikm: not found
- Error writing file = There may not be enough temporary disk space.
- Error: localhost is not a valid host name for remote access
- INFO: Created system preferences directory in java.home
- The installer could not successfully add the product information into the RPM database.
- Error: java.io.IOException: konqueror: not found
If you did not find your problem listed, contact IBM support.
Error: The input line is too long
This is a profile creation error.
It can occur during installation or when using the Profile creation wizard.
Installation problem
The following error within a log in...
install_root\profiles\default\logs
...indicates that a wsadmin action has failed to create a profile. The failure is because the length of the file path and the node name on the command string has caused the entire command to exceed the operating system limit for command length.
The input line is too long.
The installation directory path must be no longer than 60 characters.
- Option 1: If the installation failed, reinstall the
WAS product using a shorter directory path and
a shorter node name.
The node name field is available during a custom installation. The length of the default node name is usually short enough. Avoid using a node name that is longer than 10 characters if possible.
- Option 2: If the installation was successful but the ISMPWSProfileLaunchAction failed, use the Profile creation wizard to create the profile. Use a shorter profile directory path and a shorter node name when creating the profile.
We can select your own profiles path. It could be C:\profiles, for example.
Verify from the log.txt file that the ISMPConfigManagerLaunchAction is successful.
Examine the following messages in the log.txt file to determine whether the installation was successful. If so, we can run the Profile creation wizard to create the default profile.
(date time), Install, com.ibm.ws.install.ni.ismp.actions.ISMPConfigManagerLaunchAction, msg1, INSTCONFSUCCESS: Post-installation configuration is successful. (date time), Install, com.ibm.ws.install.ni.ismp.actions.ISMPWSProfileLaunchAction, err, INSTCONFFAILED: Cannot complete required configuration actions after the installation. The configuration failed. The installation is not successful. Refer to C:\Program Files\IBM\WebSphere\AppServer1234567890\logs\wasprofile\ wasprofile_create_default.log for more details. (date time), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Profile Creation Tool (PCT) is executed. (date time), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED
Profile creation wizard problem
The following error within a log in...
install_root\profiles\default\logs
...indicates that a wsadmin action has failed to create a profile. The failure is because the length of the file path, the cell name, and the node name on the command string has caused the entire command to exceed the operating system limit for command length.
The input line is too long.
The profiles directory path must be no longer than 80 characters.
If your directory path is 80 characters or less and you still have a problem, edit...
install_root\bin\setupCmdLine.bat
...to make it use the Windows subst command. The subst command maps an entire path to a virtual drive. After editing the file, run the Profile creation wizard again. If changing the setupCmdLine.bat file does not fix the problem, install the WAS product using a shorter installation path, such as C:\WAS.
See "The input line is too long" section of Problems starting or using the wsadmin command for a description of how to edit the setupCmdLine.bat file.
We can allocate expansion space for directories on AIX. If the Installation wizard does not have enough space, ISMP issues a system call for more space that increases the space allocation dynamically. The message you might see when this occurs for the /usr directory is similar to the following example:
NOTE: The following file systems will be expanded during the installation: /usr
The disk space is nn Mbyte less than required. The installation cannot continue.
If the file system is not dynamically expandable, an insufficient amount of disk space results in a message that is similar to the following example:
The disk space is 33 Mbyte less than required. The installation cannot continue.
Specify a different directory or perform a manual uninstall
This error indicates that you deleted the installation root directory before using the uninstaller program to remove the product. Now you attempting to reinstall into the same directory.
To correct the problem, perform a manual uninstall.
The warning entry in the $TMP/log.txt file is:
(Month day, year time), Install, com.ibm.ws.install.ni.ismp.actions.ISMPWarningDialogAction, wrn, Specify a different directory or perform a manual uninstall to remove all packages before reinstalling to the same directory.
Error: /usr/opt/ibm/gskta/bin/gsk7ikm: not found
This error indicates that the xlC.rte 6.0 run-time code has not been installed. You must install the xlC.rte 6.0 run-time code before you install Global Security Kit 7 (GSKit7).
To correct this problem, download the run-time code from the AIX Support site at https://techsupport.services.ibm.com/server/aix.fdc. If you have AIX 5.2, install the xlC.rte 6.0 run-time code from the AIX 5.2 CD.
For a complete list of installation prerequisites, see http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.php.
Error writing file = There may not be enough temporary disk space.
Searching for Java(tm) Virtual Machine... A suitable cellpadding=10 JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR> Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space.
This error can occur when you have not provided enough temp space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
See Using the Profile creation wizard for more information about creating profiles.
Error: localhost is not a valid host name for remote access
This error occurs when you enter localhost as the value for the Host name field in the Profile creation wizard.
The error can also occur during product installation if you enter localhost as the value of the host name field.
The host name is the network name for the physical machine on which the node is installed. The host name must resolve to a physical network node on the server. When multiple network cards exist in the server, the host name or IP address must resolve to one of the network cards. Remote nodes use the host name to connect to and to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.
If you define coexisting nodes on the same computer with unique IP addresses, define each IP address in a domain name server (DNS) look-up table. Configuration files for stand-alone Application Servers do not provide domain name resolution for multiple IP addresses on a machine with a single network address.
The value that you specify for the host name is used as the value of the hostName property in configuration documents for the stand-alone Application Server. Specify the host name value in one of the following formats:
- Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com
- The default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the Application Server configuration. This value for host name is particularly useful if you plan to change the IP address frequently when using Dynamic Host Configuration Protocol (DHCP) to assign IP addresses. A format disadvantage is being dependent on DNS. If DNS is not available, then connectivity is compromised.
The short host name is also dynamically resolvable. A short name format has the added ability of being redefined in the local hosts file so that the system can run the Application Server even when disconnected from the network. Define the short name to 127.0.0.1 (local loopback) in the hosts file to run disconnected. A format disadvantage is being dependent on DNS for remote access. If DNS is not available, then connectivity is compromised.
A numeric IP address has the advantage of not requiring name resolution through DNS. A remote node can connect to the node you name with a numeric IP address without DNS being available. A format disadvantage is that the numeric IP address is fixed. You must change the setting of the hostName property in Express configuration documents whenever you change the machine IP address. Therefore, do not use a numeric IP address if you use DHCP, or if you change IP addresses regularly. Another format disadvantage is that we cannot use the node if the host is disconnected from the network.
Warning: Cannot convert string "<type_name>"to type FontStruct
If you install the Web server plug-ins for WAS, you also install the ikeyman utility. The ikeyman utility is part of the Global Services Kit 7 (GSKit7).
If you issue the ikeyman.sh script on a Linux system, you might see the following message:
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
We can safely ignore the warning and use the ikeyman utility.
INFO: Created system preferences directory in java.home
The Key Man Utility (ikeyman) on Linux Redhat Enterprise 3.0 displays the following message after your first use of the utility.
[root@bensonl2 bin]# ./ikeyman.sh Oct 19, 2004 10:47:26 AM java.util.prefs.FileSystemPreferences$3 run INFO: Created system preferences directory in java.home.
The utility is logging preferences. The message does not display when you use the utility again.
We can safell ignore the message.
The installer could not successfully add the product information into the RPM database.
If the last line in the log.txt file is something similar to the following example, the problem might be a corrupt RedHat Package Manager (RPM) database:
(Oct 17, 2004 4:02:16 PM), Plugin.Install, com.ibm.wizard.platform.linux.LinuxProductServiceImpl, wrn, The installer could not successfully add the product information into the RPM database. Installation will continue as this is not critical to the installation of the product.
Run the following command to verify that the problem is a corrupt RPM database:
rpm -q --all
If the command hangs, the problem is a corrupt RPM database.
Error: java.io.IOException: konqueror: not found
The ISMP Launch Browser action throws the following exception on Linux and UNIX systems:
com.installshield.wizardx.actions.LaunchBrowserAction, err, java.io.IOException: konqueror: not found STACK_TRACE: 11 java.io.IOException: konqueror: not found at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:72) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:602) at java.lang.Runtime.exec(Runtime.java:524) at java.lang.Runtime.exec(Runtime.java:490) at com.installshield.util.BrowserLauncher.openURL(BrowserLauncher.java:578) at com.installshield.wizardx.actions.LaunchBrowserAction.execute(LaunchBrowserAction .java:62) at com.installshield.wizard.RunnableWizardBeanContext.run(RunnableWizardBeanContext. java:21)
This action searches for a Netscape, Mozilla, or Konqueror browser for displaying an HTML page or a Web site. In the case of the Web server plug-ins for WAS, the target page is the Plug-ins roadmap. Even though the ISMP Launch Browser action might find Mozilla or Netscape, the exception is thrown and a log entry occurs.
We can safely ignore this error.
Uninstalling the product
This task describes how to uninstall WAS.
The uninstall command calls the uninstaller program that is created during installation. The uninstaller program is customized for each product installation, with specific disk locations and routines for removing installed features.
The uninstaller program removes registry entries, uninstalls the product, and removes all related features. The uninstaller program does not remove log files in the installation root directory.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
This procedure uninstalls the WAS product.
See the following topics to uninstall other components on the product disc:
- Uninstall the Web server plug-ins for WAS
- Uninstall IBM HTTP Server
- Uninstall Application Client for WAS
Estimating the time required to uninstall The time required to uninstall is dependent on the processing speed of your machine. As a rough guideline, uninstalling the core product files and one application server profile takes approximately 10 minutes when using the uninstall command.
- Log on as root on a Linux or UNIX system, or as a user who belongs to the administrator group on a Windows system.
- Run the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the Application Server, uninstall the plug-ins to remove the configuration from the Web server. See Uninstalling the Web server plug-ins for WAS.
- Stop each running Application Server with the stopServer command.
If security is disabled, the uninstaller program can stop all WAS processes automatically. If servers are running and security is enabled, the uninstaller program cannot shut down the servers and the uninstall procedure fails. Manually stop all servers before uninstalling.
Stop all server processes in all profiles on the machine. For example, issue the following command from...
/opt/IBM/WebSphere/AppServer/profiles/app_server_profile/bin
...on a Linux machine to stop the server1 process in the profile:
./stopServer.sh server1
If servers are running and security is enabled, use the following commands:
./stopServer.sh server1 -user user_ID -password password
- Optional: Back up configuration files and log files to refer to them later, if necessary.
The uninstaller program does not remove log files in the installation root directory. The uninstaller program removes all profiles and all of the data in all profiles.
Back up the config folder and the logs folder of each profile to refer to it later, if necessary. We cannot reuse profiles so there is no need to back up an entire profile.
- Uninstall the product.
Uninstall the base WAS product
After running the uninstall command, the directory structure has only a few remaining directories. The logs directory is one of the few directories with files.
- Review...
install_root/logs/uninstlog.txt
The install_root/logs/uninstlog.txt file records file system or other unusual errors. Look for the INSTCONFSUCCESS indicator of success in the log:
Uninstall, com.ibm.ws.install.ni.ismp.actions. ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS
- Uninstall
manually before reinstalling.
The uninstaller program leaves some log files, including...
install_root/logs/uninstlog.txt
Manually uninstall the product to remove all artifacts of the product so that we can reinstall into the same installation root directory. If you do not plan to reinstall, you do not need to manually uninstall.
This procedure results in uninstalling the product.
After uninstalling the product and cleaning the system with the manual uninstall procedure, we can reinstall.
uninstall command
The uninstall command uninstalls the product. When you uninstall the product, the uninstaller program removes the core product files and all of the profiles.
Before you begin uninstalling the product
If servers are running and security is enabled, the uninstaller program cannot shut down the servers and the uninstall procedure fails. Manually stop all servers before uninstalling the product.
We can disable security in the administrative console before uninstalling the product. Then the uninstaller program can stop all server processes. Click...
Security | Global security
...and clear the check box for enabling global security in the administrative console.
We can also modify...
install_root/profiles/profile/properties/soap.client.props
...in each profile to allow the uninstaller program to issue commands against the profile. After modifying the file, we can run the uninstaller program in a secure environment without having to manually stop each server process.
Location of the command file
The command file is located in the _uninst directory in the installation root directory.
The command file is named:
-
uninstall
Command syntax
Command parameters are described at the end of this topic. This section describes the recommended command syntax, which starts the uninstaller wizard.
- Issue the uninstall command:
install_root/_uninst/uninstall
- Run the uninstaller program in the installation root of the product that you intend to uninstall. Issue a fully qualified command or change directories to...
install_root\_uninst
...and issue the uninstall command. For example, if the installation root is...
C:\IBM\WebSphere\AppServer
...issue the following command:
"C:\IBM\WebSphere\AppServer\_uninst\uninstall.exe"
Uninstalling the product
See Uninstalling the base WAS product for information about how to uninstall the product.
Logging
Examine...
install_root/logs/uninstlog.txt
...to verify that there were no file system or other unusual errors while uninstalling. If there are problems, correct them, and uninstall manually before reinstalling the product.
After uninstalling a WAS product, delete the installation root directory before reinstalling into the same directory. Deleting the old directory avoids XML configurations that are not valid that result from retaining old files. To delete all files so that we can reinstall with a clean system, see Uninstalling manually.
vpd.properties file
The installer program for any WAS product uses the ISMP program to install code. ISMP uses the vpd.properties file to track WebSphere products that it installs on all platforms but Solaris and HP-UX. The vpd.properties file lists program components that are currently installed. The file helps ISMP and the installer programs of WAS products to recognize previous installations of WAS products and to control options for new installations.
Situations that require you to edit the vpd.properties file
Certain situations require you to edit the vpd.properties file before reinstalling a WAS product. The uninstaller programs for WAS products edit the vpd.properties while uninstalling a product, to remove entries for the product and any of its features that might have entries in the file.
It is necessary to remove product entries in the vpd.properties file before we can reinstall the product. Some situations that occur require manually removing entries from the vpd.properties file before we can reinstall a product. These situations include:
- Bypassing the uninstaller program to uninstall a product manually
- Uninstalling a product manually when the uninstaller program is not present or is not working
If the vpd.properties file has entries for a product that you uninstalled, edit the file and remove the entries. If you do not edit the vpd.properties file to remove entries for a product or features of a product, we cannot reinstall the product into the same directory structure. If product entries in the vpd.properties file are present, the installer program reads the vpd.properties file, determines that the product is already installed, and displays the panel that prompts you to install additional features into the existing product or to install the binaries a second time. Unfortunately, the existing binaries might not be valid at that point. The installer program does not verify the products that it finds listed in the vpd.properties file.
Location of the vpd.properties file
The location of the vpd.properties file varies per operating platform:
- AIX platforms: The root directory or the usr/lib/objrepos directory
- Linux platforms: The root directory
- Windows platforms: installation directory of the operating system, such as the C:\WINNT directory or the C:\windows directory.
Example of the vpd.properties file
The following example shows all of the entries for the vpd.properties file for v6.0 of the Network Deployment product on a Windows platform. The example shows entire lines but breaks each line for formatting purposes. The identifier for the first component is highlighted. The installation location of the first component is also highlighted.
WSBAA60|6|0|0|0|6.0.0.0|1=WAS| IBM WAS| |IBM| |6.0.0.0| >C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60|6|0|0|0|6.0.0.0|1|0|false| "_uninst" "uninstall.jar" "uninstall.dat" ""|true|3| WSBAA60|6|0|0|0|6.0.0.0|1 WSBAA60NDOnlyComponent| | | | | |1=NDOnly.ismp.component| ND Only| |IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer\properties\version\install\ 6.0.0.0\componentmaps|0|0|1| WSBAA60NDOnly|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60NDOnlyComponent| | | | | |1 WSBAA60JavadocsComponent|6|0|0|0|6.0.0.0|1=Javadocs.ismp.component| Javadocs| |IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer\properties\version\install\ 6.0.0.0\componentmaps|0|0|1| WSBAA60Javadocs|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60JavadocsComponent|6|0|0|0|6.0.0.0|1 WSBAA60Javadocs|6|0|0|0|6.0.0.0|1=Javadocs| Javadocs|$L(com.ibm.ws.install.resourcebundle.WSResourceBundle, Features.javadoc.description)|IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60Javadocs|6|0|0|0|6.0.0.0|1 WSBAA60LicensingComponent| | | | | |1=LAP Component| LAP Component|This bean will work with the licensing files| | | | C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60LicensingComponent| | | | | |1 WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1=CoreRuntime| Core Runtime|$L(com.ibm.ws.install.resourcebundle.WSResourceBundle, Features.coreruntime.description)|IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1 WSBAA60SamplesComponent|6|0|0|0|6.0.0.0|1=Samples.ismp.component| Samples| |IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer\properties\version\install\ 6.0.0.0\componentmaps|0|0|1| WSBAA60Samples|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60SamplesComponent|6|0|0|0|6.0.0.0|1 WSBAA60CoreRuntimeComponent|6|0|0|0|6.0.0.0|1=CoreRuntime.ismp.component| Core Runtime| |IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer\properties\version\install\ 6.0.0.0\componentmaps|0|0|1| WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60CoreRuntimeComponent|6|0|0|0|6.0.0.0|1 WSBAA60NDOnly|6|0|0|0|6.0.0.0|1=NDOnly| Invisible ND Only Feature| |IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60NDOnly|6|0|0|0|6.0.0.0|1 WSBAA60Samples|6|0|0|0|6.0.0.0|1=Samples| Samples|$L(com.ibm.ws.install.resourcebundle.WSResourceBundle, Features.samples.description)|IBM| |6.0.0.0| C:\Program Files\IBM\WebSphere\AppServer|0|0|1| WSBAA60CoreRuntime|6|0|0|0|6.0.0.0|1|0|false| |true|3| WSBAA60Samples|6|0|0|0|6.0.0.0|1Identifying entries in the vpd.properties file
Table 13. Identifers in the vpd.properties file for WebSphere products Identifier Product WSB...60 All V6 products use this identifier to identify the core product files: - WAS - Express, V6
- WAS, V6
- WAS Network Deployment, V6
WSP...60 Web server plug-ins for WAS, V6 WSC... WAS Clients, V6 Web server plug-ins for WAS installs the following packages:
Operating system Registry keys AIX, Linux, and Windows - WSPAA60
- WSPAA60DefineglobalconstantsComponent
- WSPAA60DefinelocalvariablesComponent
- WSPAA60LicensingComponent
- WSPAA60Webserverplugins
- WSPAA60WebserverpluginsComponent
- WSPAA60AddBytes
- WSPAA60gskit
- WSPAA60gskitComponent
Uninstalling the base WAS product
This task describes using the uninstaller program to uninstall WAS.
The uninstaller program removes registry entries, uninstalls the product, and removes all related features. The uninstaller program does not remove log files in the installation root directory.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
This procedure uninstalls the WAS product.
See the following topics to uninstall other components on the product disc:
- Uninstalling the Web server plug-ins for WAS
- Uninstalling IBM HTTP Server
- Uninstalling Application Client for WAS
- Stop any browsers and any Java processes related to WAS products as described in Uninstalling the product.
- Change
directories to the _uninst directory before issuing the
uninstall
command. The command file is located in...
install_root/_uninst
...on a Linux or UNIX platform, and in...
install_root\_uninst
...on a Windows system.
For example, to change directories before uninstalling the product from a Linux platform...
cd /opt/IBM/WebSphere/AppServer/_uninst
- Issue the uninstall command. The command file is named uninstall for Linux and UNIX platforms
Linux, AIX, HP-UX, and Solaris issue the uninstall command from...
install_root/_uninst
...:
./uninstall
The Uninstaller wizard begins and displays the Welcome panel.
- Click Next to begin uninstalling the product. The Uninstaller wizard displays a confirmation panel that lists the product and features that you are uninstalling.
- Click Next to continue uninstalling the product. The Uninstaller wizard deletes existing profiles first.
After deleting profiles, the Uninstaller wizard deletes core product files by component.
- Click Finish to close the wizard after the wizard removes the product.
This procedure uninstalls the WAS product.
After running the uninstall command, the directory structure has only a few remaining directories. The logs directory is one of the few directories with files.
The file...
install_root/logs/uninstlog.txt
...records file system or other unusual errors. Look for the INSTCONFSUCCESS indicator of success in the log:
Uninstall, com.ibm.ws.install.ni.ismp.actions. ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS
If you plan to reinstall, perform the manual uninstall procedure for your system.
The uninstaller program leaves some log files, including...
install_root/logs/uninstlog.txt
Manually uninstall the product to remove all artifacts of the product so that we can reinstall into the same installation root directory. If you do not plan to reinstall, you do not need to manually uninstall.
See Uninstalling manually for more information.
Uninstalling manually
The uninstaller program leaves some files that can prevent you from reinstalling into the original directory. Delete files and registry entries to clean the machine so that we can reinstall into any directory. If you are not planning to reinstall, do not uninstall manually.
We can reinstall without a clean machine. Such an installation creates a coexistence scenario that can prevent you from installing into the original directory.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
Cleaning the machine means deleting everything from the previous installation, including log files that are left behind by the uninstall command. Before you start the procedure, back up log files, if necessary. See Troubleshooting installation for the location of log files.
This procedure uninstalls your WAS product.
Run one of the following procedures to produce a clean machine on your operating system.
- Uninstall manually on an AIX system.
- Uninstall manually on an HP-UX system.
- Uninstall manually on a Linux system.
- Uninstall manually on a Solaris system.
- Uninstall manually on a Windows system.
Manually uninstalling produces a clean system. A clean system has no evidence of a previously deleted installation.
Manually uninstalling on an AIX system
This procedure uninstalls a WAS product from an AIX system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, we can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root /usr/IBM/WebSphere/AppServer profiles_install_root /usr/IBM/WebSphere/AppServer/profiles plug-ins_install_root /usr/IBM/WebSphere/Plugins The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The ~/.WASRegistry file identifies the installation root for all installed WAS products.
- The file...
install_root/logs/wasprofile/wasprofile_create_profile.log
for each created profile identifies the installation location in the stanza with the tag...
<method>invokeWSProfile</method>
Uninstalling the product leaves...
profiles_root/profile
...with the pctLog.txt file.
Perform the following procedure to produce a clean system.
- Log on as root.
- Run
the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server.
- Issue the uninstall command.
If you have already run the uninstaller program or if we cannot run the uninstaller program, simply skip this step.
install_root/_uninst/uninstall
See the description of the uninstall command for more information.
The Uninstaller wizard begins and displays the Welcome panel.
- Use
the kill
command to kill all Java processes that are running.
If running Java processes are not related to WAS products and it is not possible to stop them, stop all WAS product-related processes. Use the following command to determine all processes that are running:
ps -ef | grep java
Stop all WAS-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.
- List
WAS components that are installed.
Type the following command to search for related packages:
lslpp -l| grep -i WS
Do not remove packages for WAS products that you are not uninstalling. V6 package names have a prefix of WSB or WSP and a suffix of 60. WSC package names do not have a suffix of 60.
- Use
the geninstall command to remove registry information for
each component that displays in the list.
For example, issue the follow command to display packages with a prefix of WS:
lslpp -l | grep -i WS
The system displays the list of matching packages:
WSBAA60CoreRuntime 6.0.0.0 COMMITTED Installs the core product run
Issue the follow command to remove the registry entry:
geninstall -u WSBAA60CoreRuntime
- Change directories to the /usr/IBM directory.
- Type rm -rf WebSphere to delete this WAS-related directory, but only if the AppServer directory is the only directory within the WebSphere directory. Delete the directory if the only products contained in the directory are products that you intend to delete.
- Edit
the .WASRegistry file.
The file location is the home directory, ~/.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
We can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
/usr/IBM/WebSphere/AppServer /usr/IBM/ND/AppServer /usr/ExpressV6/IBM/WebSphere/AppServer /usr/ND/IBM/WebSphere/AppServer /usr/Express/IBM/WebSphere/AppServer
- Run
the odmclean.sh and
aixclean.sh scripts.
Do not run the aixclean.sh script if the WebSphere MQ product is installed.
- Obtain the scripts from the technote document titled, Manual uninstall On AIX requires odmclean.sh and aixclean.sh on the WAS Support site.
- Edit the odmclean.sh script and replace every instance of the string /usr/WebSphere/AppServer with the actual installation root directory.
- Run
the aixclean.sh script from the command
line:
./aixclean.sh
- Run
the odmclean.sh script from the command
line:
./odmclean.sh
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
Example of displaying package names beginning with WS, for WAS-related products
==>>lslpp -l | grep WS WSBAA60 6.0.0.0 COMMITTED ISMP installed entry WSBAA60AddBytesNonHP 6.0.0.0 COMMITTED ISMP installed entry WSBAA60CoreRuntime 6.0.0.0 COMMITTED Installs the core product run WSBAA60CoreRuntimeComponent WSBAA60Javadocs 6.0.0.0 COMMITTED Installs the public Java API WSBAA60JavadocsComponent 6.0.0.0 COMMITTED ISMP installed entry WSBAA60License 6.0.0.0 COMMITTED ISMP installed entry WSBAA60LicenseComponent 0.0.0.0 COMMITTED ISMP installed entry WSBAA60LicensingComponent 0.0.0.0 COMMITTED This bean will work with the WSBAA60Samples 6.0.0.0 COMMITTED Includes Samples with source WSBAA60SamplesComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60DefineglobalconstantsComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60DefinelocalvariablesComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60LicensingComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60Webserverplugins 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60WebserverpluginsComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60AddBytes 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60gskit 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60gskitComponent 6.0.0.0 COMMITTED ISMP installed entry...
Manually uninstalling on an HP-UX system
This procedure uninstalls a WAS product from an HP-UX system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary.
See Use command line tools for a description of managing configuration files.
Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, we can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root /opt/IBM/WebSphere/AppServer profiles_install_root /opt/IBM/WebSphere/AppServer/profiles plug-ins_install_root /opt/IBM/WebSphere/Plugins The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The ~/.WASRegistry file identifies the installation root for all installed WAS products.
- The file...
install_root/logs/wasprofile/wasprofile_create_profile.log
...for each created profile identifies the installation location in the stanza with the tag...
<method>invokeWSProfile</method>
Uninstalling the product leaves...
profiles_root/profile
...with the pctLog.txt file.
Perform the following procedure to produce a clean system.
- Log on as root.
- Run the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server.
- Issue the uninstall command.
If you have already run the uninstaller program or if we cannot run the uninstaller program, simply skip this step.
install_root/_uninst/uninstall
The Uninstaller wizard begins and displays the Welcome panel.
- Use the kill command to kill all Java processes that are running.
If running Java processes are not related to WAS products and it is not possible to stop them, stop all WAS product-related processes. Use the following command to determine all processes that are running:
ps -ef | grep java
Stop all WAS-related processes with the command...
kill -9 java_pid_1 java_pid_2 ... java_pid_n
- Use HP-UX System Administration Manager (SAM) to remove packages.
- Start the SAM utility and verify that your DISPLAY and TERM environment variables are set properly.
- Click Software management.
- Click View installed software.
- Look for WAS entries or IBM HTTP Server entries in the SD list.
- Close the SD list.
- Click Remove local host software.
- Click any of the following instances that display in the SD Remove List:
- IBM HTTP Server
- WSBAA60
- WSPAA60
- WSCAA
- gsk7bas
- Click Actions > Mark for remove.
- Click Actions > Remove.
- Click OK in the Remove analysis dialog box.
- Click Logs to display real-time removal of selected packages.
- Click Done when all packages are removed.
- Exit SAM.
- Search for the packages to verify their removal.
Type swlist | grep WS to show packages for WAS.
Package names for Web server plug-ins for WAS are:
WSPAA60 WSPAA60DGCC WSPAA60DLVC WSPAA60LC WSPAA60WSPC WSPAA60AddBytesHS WSPAA60gskitHP WSPAA60gskitHPC WSPAA60jdkHP
- Type...
rm -rf /opt/IBM/WebSphere/AppServer/
...to remove WAS directories in the...
/opt/IBM/WebSphere/AppServer
...installation root. Do not remove installation root directories for products that you intend to keep. Remove all of the profile directories as well.
- Edit the .WASRegistry file.
The file location is the home directory, ~/.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
We can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
/opt/IBM/WebSphere/AppServer /opt/IBM/P1/AppServer /opt/V6/IBM/WebSphere/AppServer /opt/P2/IBM/WebSphere/AppServer /opt/P3/IBM/WebSphere/AppServer
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
Example of displaying package names for WAS products
Issue the following command:
swlist | grep WSBAA60
The following package name is returned:
WSBAA60 6.0.0 IBM WAS
Manually uninstalling on a Linux system
This procedure uninstalls a WAS product from a Linux system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, we can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root /opt/IBM/WebSphere/AppServer profiles_install_root /opt/IBM/WebSphere/AppServer/profiles plug-ins_install_root /opt/IBM/WebSphere/Plugins The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The ~/.WASRegistry file identifies the installation root for all installed WAS products.
- The file...
install_root/logs/wasprofile/wasprofile_create_profile.log
...for each created profile identifies the installation location in the stanza with the tag...
<method>invokeWSProfile</method>
Uninstalling the product leaves...
profiles_root/profile
...with the pctLog.txt file.
Perform the following procedure to produce a clean system.
- Log on as root.
- Run the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server.
- Issue the uninstall command.
If you have already run the uninstaller program or if we cannot run the uninstaller program, simply skip this step.
install_root/_uninst/uninstall
The Uninstaller wizard begins and displays the Welcome panel.
- Use
the kill
command to kill all Java processes that are running.
If running Java processes are not related to WAS products and it is not possible to stop them, stop all WAS product-related processes. Use the following command to determine all processes that are running:
ps -ef | grep java
Stop all WAS-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.
- Search
for related packages. Issue the following command to show packages
for the WAS
products:
rpm -qa | grep WS
For example, after issuing the command, the following list of packages might display:
WSBAA60CoreRuntimeComponent-6.0-0 WSBAA60LicenseComponent-6.0-0 WSBAA60JavadocsComponent-6.0-0 WSBAA60NDOnlyComponent-6.0-0 WSBAA60AddBytesNonHP-6.0-0 WSBAA60LicensingComponent-6.0-0 WSBAA60SamplesComponent-6.0-0 WSPAA60 WSPAA60DefineglobalconstantsComponent WSPAA60DefinelocalvariablesComponent WSPAA60LicensingComponent WSPAA60Webserverplugins WSPAA60WebserverpluginsComponent WSPAA60AddBytes WSPAA60gskit WSPAA60gskitComponent
Do not remove packages for WAS products that you are not uninstalling. V6 package names have a prefix of WSB or WSP and a suffix of 60. WSC package names do not have a suffix of 60.
- If
there are packages to delete, type
rpm -e packagename to remove any packages
for the product that you are uninstalling.
Alternatively, we can search for packages to verify that everything in the list is something to delete:
rpm -qa | grep WS
If the list contains packages that you intend to delete and no others, remove all of the packages with the following command:
rpm -qa | grep WS | xargs rpm -e
If there is a problem with package dependencies, use the following command to remove the packages:
rpm -e packagename --nodeps --justdb
The nodeps option skips the dependency check. The justdb option updates only the package database, and not the file system. Use only the nodeps option can cause a failure in package removal if there is any mismatch in the dependent file system (files and directories).
- Type...
rm -rf /opt/IBM/WebSphere/AppServer/
...to remove WAS directories in the...
/opt/IBM/WebSphere/AppServer
...installation root. Do not remove installation root directories for products that you intend to keep. Remove all of the profile directories as well.
- Edit
the .WASRegistry file.
The file location is the home directory, ~/.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
We can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
/opt/IBM/WebSphere/AppServer /opt/IBM/P1/AppServer /opt/V6/IBM/WebSphere/AppServer /opt/P2/IBM/WebSphere/AppServer /opt/P3/IBM/WebSphere/AppServer
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
Manually uninstalling on a Solaris system
This procedure uninstalls the WAS product from a Solaris system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Use command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, we can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root /opt/IBM/WebSphere/AppServer profiles_install_root /opt/IBM/WebSphere/AppServer/profiles plug-ins_install_root /opt/IBM/WebSphere/Plugins The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The ~/.WASRegistry file identifies the installation root for all installed WAS products.
- The file...
install_root/logs/wasprofile/wasprofile_create_profile.log
...for each created profile identifies the installation location in the stanza with the tag...
<method>invokeWSProfile</method>
Uninstalling the product leaves...
profiles_root/profile
...with the pctLog.txt file.
Perform the following procedure to produce a clean system.
- Log on as root.
- Run the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server.
- Issue the uninstall command.
If you have already run the uninstaller program or if we cannot run the uninstaller program, simply skip this step.
install_root/_uninst/uninstall
The Uninstaller wizard begins and displays the Welcome panel.
- Use the kill command to kill all Java processes that are running.
If running Java processes are not related to WAS products and it is not possible to stop them, stop all WAS product-related processes. Use the following command to determine all processes that are running:
ps -ef | grep java
Stop all WAS-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.
- Search for related packages....
pkginfo | grep WS
If no packages appear when using these commands, skip the next step. The resulting list of packages has the following format:
application WSBAA60 WAS
- Change directories to the directory where package information is registered.
cd /var/sadm/pkg
- Issue the following command to remove any WAS-related packages.
pkgrm packagename1 packagename2 packagename3 ...
Do not remove packages for WAS products that you are not uninstalling. V6 package names have a prefix of WSB or WSP and a suffix of 60. WSC package names do not have a suffix of 60.
Issue the following commands from the /var/sadm/pkg directory to search for and remove any WAS product-related packages that are registered in the /var/sadm/pkg directory:
- Change directories to the correct directory: cd /var/sadm/pkg
- ls |grep WSB|xargs -i pkgrm -n {} for WAS products
- ls |grep WSC|xargs -i pkgrm -n {} for WAS Clients
- ls |grep WSP|xargs -i pkgrm -n {} for Web server plug-ins for WAS
Package names for Web server plug-ins for WAS are:
WSPAA60 WSPAA60AC WSPAA60BC WSPAA60CC WSPAA60DC WSPAA60FC WSPAA60FB WSPAA60GC WSPAA60HC
If there is a problem removing the packages, remove the related package directories in the /var/sadm/pkg directory, including the preremove files. For example, remove the following file before issuing the pkgrm -n WSBAA60 command:
/var/sadm/pkg/WSBAA60/install/preremove
- Type...
rm -rf /opt/IBM/WebSphere/AppServer/
...to remove WAS directories in...
/opt/IBM/WebSphere/AppServer
...installation root. Do not remove installation root directories for products that you intend to keep. Remove all of the profile directories as well.
- Edit the .WASRegistry file.
The file location is the home directory, ~/.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
We can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
/opt/IBM/WebSphere/AppServer /opt/IBM/P1/AppServer /opt/V6/IBM/WebSphere/AppServer /opt/P2/IBM/WebSphere/AppServer /opt/P3/IBM/WebSphere/AppServer
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
Manually uninstalling on a Windows system
This procedure uninstalls a WAS product from a Windows system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary.
Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, we can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root C:\Program Files\IBM\WebSphere\AppServer profiles_install_root C:\Program Files\IBM\WebSphere\AppServer\profiles plug-ins_install_root C:\Program Files\IBM\WebSphere\Plugins Windows 2000 consideration: If you move either installation root directory, move them to a shorter path name. Windows 2000 has a length restriction of 258 characters for a command. A problem can occur that prevents the successful creation of a profile when either path is too long. The maximum length for the installation root directory is 60 characters. The maximum length for the profiles installation root directory is 80 characters.
The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The %USERPROFILE%\.WASRegistry file identifies the installation root for all installed WAS products.
- The file...
install_root\logs\wasprofile\wasprofile_create_profile.log
...for each created profile identifies the installation location in the stanza with the tag...
<method>invokeWSProfile</method>
Perform the following procedure to produce a clean system.
- Log on with a user ID that belongs to the administrator group.
- Run the uninstaller program for the Web server plug-ins for WAS.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server.
- Issue the uninstall command.
If you have already run the uninstaller program or if we cannot run the uninstaller program, simply skip this step.
install_root\_uninst\uninstall
The Uninstaller wizard begins and displays the Welcome panel.
- Verify that you have an Emergency Recovery Disk. Instructions for creating this disk are in the Windows help documentation.
This step is a safeguard. This procedure does not require the recovery disk.
- Use the regback.exe program from the Windows Resource Kit to back up the registry.
This step is a safeguard. This procedure does not require the backup copy of the registry.
- Delete product registry entries for the WAS product that you are uninstalling.
Invoke regedit.exe from a command prompt, to edit the Windows system registry.
Handle the Registry with care
Note: We can easily make a mistake while using the registry editor to view and edit registry contents. The editor does not warn you of editing errors, which can be extremely dangerous. A corrupt registry can disrupt your system to the point where your only option is to reinstall the Windows operating system.
- Use Ctrl-F to search for all instances of WebSphere, to determine whether you should delete each entry. You might not be able to remove all of the entries related to WAS, which is not a problem.
- Expand and select keys related to WAS products.
Delete the following keys for the WAS product:
- HKEY_CURRENT_USER\ Software\ Microsoft\ Windows\ CurrentVersion\ Explorer\ MenuOrder\ Start Menu\ Programs\ IBM WebSphere\ Application Server v6
- HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ Uninstall\ WSBAA60
- HKEY_LOCAL_MACHINE\ Software\ IBM\ WAS\ 6.0.0.0
- HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ Uninstall\ WSBAA60ND
- HKEY_LOCAL_MACHINE\ Software\ IBM\ Web server Plug-ins for IBM WAS\ 6.0.0.0
- Click Edit > Delete from the menu bar for each related key.
- Click Yes when asked to confirm deletion of the key.
- Click...
Registry | Exit
...from the menu bar when you are finished.
- Delete the installation root directory for the product that you are uninstalling.
- Determine all of the profile directories and remove the directories.
- Open
a Windows Explorer window and browse to the
C:\Documents and Settings\All Users\Start
Menu\Programs\IBM WebSphere directory.
If you have one installation of a WAS product, delete the following folder:
Application Server v6
- Delete the %WINDIR%\IsUninst.exe file.
- Edit
the .WASRegistry file.
The file location is the home directory of the user ID who installed the product, %USERPROFILE%\.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
We can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
C:\Program Files\IBM\WebSphere\AppServer C:\IBM\WebSphere\AppServer C:\ExpressV6\IBM\WebSphere\AppServer C:\ND_Install_9_25_2004_build\IBM\WebSphere\AppServer C:\Express_09_25_2004\IBM\WebSphere\AppServer
- Restart your machine if a prompt displays that directs you to restart.
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
- install_root/logs/log.txt