Install a IBM® WebSphere® Application Server customized installation package (CIP) using the Installation wizard on distributed operating system platforms. You install from a CIP image created with the Installation Factory.
This topic describes one of the available installation procedures.
If this topic does not describe the procedure that you meant to select, click the link to the description of the appropriate installation procedure before you issue the install command.
Knowing which components to install and in what order to install them is important. Before starting this installation, read the "Planning the installation" topic in the WebSphere Application Server, Version 7.0 Information Center. The planning diagrams show typical topologies for the product. The solutions are also available through the Installation solution diagrams link in the launchpad. Also read the "Using the launchpad to start the installation" topic.
Perform the following installation procedure to select available features for the base WebSphere Application Server product and to select characteristics for the application server profile.
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.
Mount
the drive if necessary.
You can start the installation directly with the install command.
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.
The Installation wizard checks for a previous installation at the same product level.
Specifically, the wizard looks for an existing installation.
This procedure assumes that you do not have an existing installation that you intend to update.
A CIP might not have all features available to install. You can install only what was included in the CIP.
Note: If an existing installation is at a lower level than the CIP or at the same level as the CIP, the core product will be updated to the CIP level automatically. If an existing installation is at a higher level than the CIP, the core product will not be down leveled. The feature panel only shows the features you are missing, if you select to install the new feature from CIP, the installed features will be at the same level of CIP, which is lower than existing installation. Thus incremental install on a higher level of existing installation is not recommended.
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.
The installation wizard displays a confirmation panel.
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 user 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, and 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.
The installer 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, you must 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.
You 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. 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.
The slip install log for the Installation Factory is located in the app_server_root/logs/install/log.txt file, which is the same log file as for a normal installation. If the file already exists, a new log message is appended to the file.
If problems occur, consult the following applicable logs:
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.
Troubleshoot
the installation if the app_server_root/logs/install/log.txt file
or the user_data_root/profileRegistry/logs/manageprofiles/create.log file
does not contain a record of any errors, but errors exist.
Read the "Troubleshooting installation" and the "Installation component troubleshooting tips" topics for more information.
If problems exist that cause you to reinstall the product, correct the errors, uninstall the product in the same way as the regular application server product, reboot a Windows machine or log off and back on as root on a machine with an operating system such as AIX or Linux, and reinstall.
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 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.
See the documentation on profiles for more information.
Deploy an application to get started!
See Fast paths for WebSphere Application Server to get started deploying applications.
In this information ... | 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. |