Upgrading the trial to the full product using a CIP
This page describes one of the installation options for a customized installation package (CIP) that includes the IBM WAS product and one or more maintenance packages. This page describes how to use the Installation wizard to upgrade a trial installation to the full base product.
This topic describes one of the available installation procedures. Other installation paths include:
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 WAS, V7.0 Information Center. The planning diagrams show typical topologies for WAS ND. 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 to upgrade a trial installation to the full WAS product.
- Log on to the operating system. If installing as a non-root or non-administrative user, then there are certain limitations.
In addition, select a umask that allows the owner to read/write to the files, and allows others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users, a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command:
umaskTo set the umask setting to 022, issue the following command:umask 022When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the appserver. The installer user account must have the following advanced user rights:
- Act as part of the operating system
- Log on as a service
For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See the Windows operating system documentation for more information.
If you plan to run the appserver as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this restriction, install with a user ID that does not contain spaces.
- Access the root directory of the installation package on the hard disk, or insert the disc containing the installation package into the disc drive. If installing WAS ND from CD and the CIP installer is spanned across multiple CDs, you will be prompted during the installation for the next CD.
Best practice: To avoid being prompted for subsequent CDs, copy all installation CDs into the same directory on the hard disk, name them DISC1. DISC2, and so on for each disc, and run the installer from the DISC1 directory. You will not be prompted for the next CD during installation if we have followed this naming convention. If installing silently, then use this naming convention or the installation will not proceed
Mount the drive if necessary.
- Start the installation directly with the install command.
- Change to the WAS directory.
- Run the install command.
./install
- install
After launching the CIP installation wizard from the command line, the wizard initializes and then displays the Welcome panel. Click About this custom installation package to display detailed information about the current custom installation package, such as the edition and version.
- The installation wizard initializes and then displays the Welcome panel.
Click Next to continue.
- The license agreement panel is displayed. Read the license agreement and accept its terms. After you accept the licensing terms, the installation wizard checks for a supported operating system and prerequisite patches.
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 we 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. The installation process verifies that the minimum required version of a supported operating system is available. If you meet the minimum release requirements or are at a higher minor release of a supported operating system, then you will not encounter a prerequisite error. If not at the minimum version of a supported operating system, we can continue with the installation, but the installation or product operation might not succeed without applying maintenance. If at a higher major release of a supported operating system, or the operating system itself is not on the supported list, we might encounter the following warning:
Warning: A supported operating system was not detected. Support for the operating system might have been added after the release of WAS ND. See the WAS detailed system requirements Web pages for more information about supported operating systems. We can continue with the installation, but the installation or product operation might not succeed without applying maintenance. Go to WAS support Web pages to obtain the latest maintenance packages to apply after installation.
Results
This procedure results in upgrading a trial installation to the full WAS product.
Next steps
We can install the CIP again to add features or install maintenance. Or we can use the Profile Management Tool to create more standalone appservers.
See the documentation on profiles for more information.
If we have already created the topology that you require, try deploying an application in the environment.
Deploy an application to get started!
See Fast paths for WebSphere Application Server to get started deploying applications.
Last updated Nov 11, 2010 1:01:09 PM CST