Install IBM® WebSphere® Application Server - Express using the Installation wizard on distributed operating system platforms. You can install from the installation image on the product media, or the downloaded Passport Advantage® image.
Knowing which components to install and in what order to install them is important. Before starting this installation, see Planning the WebSphere Application Server product installation. The planning diagrams show typical topologies for the product. The solutions are also available through the Installation solution diagrams link in the launchpad. See Using the launchpad to start installations. You cannot run the launchpad remotely to install a product. Only local use of the launchpad is supported.
Make sure that your operating system is ready for product installation. Read the Preparing the operating system for product installation topic for more information.
Perform the following procedure to install the WebSphere Application Server - Express product.
umaskTo set the umask setting to 022, issue the following command:
umask 022
If you plan to run the application server as a Windows service, do not install
from a user ID that contains spaces. A user ID with spaces cannot
be validated. Such a user ID is not allowed to continue the installation.
To work around this restriction, install with a user ID that does
not contain spaces.
Or you can start the installation directly with the install command.
If you cannot start the launchpad, use the troubleshooting information in Using the launchpad to start installations to correct the problem.
When using the launchpad, launch the installation wizard for WebSphere Application Server - Express.
Click Next to continue.
Although the installation wizard automatically checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the WebSphere Application Server detailed system requirements Web site if you have not already done so. The Web site lists all supported operating systems and the operating system fixes and patches that you must install to have a compliant operating system.
Warning: A supported operating system was not detected. Support for your operating system might have been added after the release of the product. See the WebSphere Application Server detailed system requirements Web pages for more information about supported operating systems. You can continue with the installation, but the installation or product operation might not succeed without applying maintenance. Go to the product support Web pages to obtain the latest maintenance packages to apply after installation.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
Click the radio button beside the message I accept both the IBM and the non-IBM terms to agree to the license agreement and click Next to continue.
Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.
Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.
Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.
Select the features you want to install and click Next.
Specify the location of the installation root directory for the product binaries, which are also known as the core product files or system files.
The system-owned default app_server_root directories for installing as a root user or an administrator are different than the user-owned default app_server_root directories when installing as a non-root installer.
The installer program checks for required space before calling the Installation wizard. If you do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, then restart the installation.
Profile Type | Description |
---|---|
Management | Create a management profile that provides
the servers and services necessary to manage your WebSphere environment. You can select one
of the following management profile types on the following panel:
|
Application server | Create a standalone application server profile. |
None | Do not create a profile during installation. However, if you do not create a profile during installation, then you must create a profile after installation to have an operational product. |
The default setting is to enable administrative security. Clear the check box to disable security or supply an administrative ID and password. If you are installing the samples on an application server profile, you must specify the samples security information in the samples section below the administrative security section.
Review the summary information. 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.
Select the Launch the First steps console checkbox if you wish to launch the First steps application. Use the First steps console to verify the installation, start the Profile Management Tool, start the application server, or open the administrative console, where you can deploy sample applications. See the First steps documentation for more information.
If you did not create a profile during the installation, the option to launch the Profile Management Tool is displayed. Use the Profile Management Tool to create an operational environment that includes a profile.
If the installation of the core product files fails, fix the error and reinstall.
If the creation of a profile fails, fix the error and run the Profile Management Tool to recreate the profile.
Troubleshoot the installation if the app_server_root/logs/install/log.txt file or the app_server_root/logs/manageprofiles/profile_name_create.log file does not contain a record of any errors, but errors exist.
If problems exist that cause you to reinstall the product, correct the errors, uninstall the product as described in the uninstallation topics, reboot a Windows machine or log off and back on as root on a machine with an operating system such as AIX® or Linux, and reinstall.
If you did not create a profile during the installation, the option to launch the Profile Management Tool is displayed. Use the Profile Management Tool to create an operational environment that includes a profile.
See the profiles documentation for more information.
If you did create a profile, select the check box to open the First Steps console then click Finish.
This procedure results in the installation wizard installing WebSphere Application Server - Express into the installation root directory. The installation wizard creates a profile named default that provides the runtime environment for the server1 application server.
Further configuration is not necessary at this time. However, you can create additional standalone application servers with the Profile Management Tool. Each profile is created in the profile_root directory by default.
After installing the product from the installation image, the next step is to check for available updates before you alter the configuration of the product. Read the "Installing maintenance packages" topic for more information.
See Roadmap: Installing the Express product for more information on starting a server.
After creating an application server profile, you can deploy an application. See Fast paths for WebSphere Application Server to get started deploying applications.
In this information ...Related concepts
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |