After the Base Operating System (BOS) is installed, you might want to install optional software or service updates.
Optionally installable software includes:
Note: If you are installing the Kerberos package or the DCE server software, see Appendix D, Installing Kerberos Version 5 for important configuration information.
Software products can be divided into the following categories:
|Licensed Program||A licensed program (also known as a product) is a complete software product including all packages associated with that licensed program. For example, bos (the Base Operating System) is a licensed program.|
|Package||A group of separately installable units that provide a set of related functions. For example, bos.net is a package.|
|Fileset||An individually installable option. Filesets provide a specific function. An example of a fileset is bos.net.nfs.client 5.1. For more information on fileset packaging, see Fileset Installation Packaging.|
|Fileset Update||An individually installable update. Fileset updates either enhance or correct a defect in a previously installed fileset.|
|Bundle||A collection of packages, products, or individual filesets that suit a specific purpose, such as providing personal productivity software or software for a client machine in a network environment. A set of bundles is provided with BOS that contain a specific set of optional software. For more information on bundle packaging, see Bundle Packaging.|
A product can be composed of several packages, which in turn can be composed of different filesets. A product might be installed in its entirety, or only certain packages or filesets for the product might be installed. Software products are subdivided in this way, because many software products are large and have many pieces that can be used independently. Dividing a product into separately installable filesets allows you to install only those filesets you need.
You can install all the filesets included in a package or the entire product, or you can install only selected filesets, especially if you have limited hard disk space on your system.
The product name and level number identify a software product. The format for a software product level in AIX 5.1 is:
Each field in the software product identification is defined as follows:
For example, 04.01.0000.0000 is a software product level number, and 04.01.0001.0032 is a software product update level. It is not necessary to include the leading zeroes in the version, release, modification level, and fix level fields of the level. Level 04.01.0000.0000 can also be written as 18.104.22.168.
There are two types of software licensing that can be implemented in the software purchase: run-time licensing and acceptance of software license agreements. Normally, software requiring run-time licenses is only selected for installation when you have a license to use that software. Although the Web-based System Manager and System Management Interface Tool (SMIT) allow you to install licensed software even if you do not own a license, you might be prevented from using the newly installed software until you have obtained the appropriate license.
Accepting software license agreements requires that the license agreement be accepted as part of the installation process. If software installed as part of your Base Operating System installation requires accepting a software license agreement, you cannot exit the Configuration Assistant (or the Installation Assistant for non-graphical consoles) until the license agreement has been accepted. You can view as well as accept the license agreement. The BOS installation can be customized to automatically accept software licenses. Refer to Chapter 8, Customized BOS Installations for more information.
For optional software installation, you can preview the license agreements on the installation media using the smit license_on_media fast path or the installp -El command. During the installation process, there is a menu item you can select to accept the software license, or you can use the installp command with the -Y flag. To view accepted license agreements on a system, you can use the SMIT smit installed_license fast path or the lslpp -E command. To view licenses using the Web-based System Manager, type wsm to start the application, and select Software. When a product is uninstalled, the license agreement acceptance is changed to the inactive state. If the product is reinstalled, you will not be prompted to reaccept the license agrement.
After completing the prerequisites in this section, your next step is deciding whether to install software with the Web-based System Manager or with SMIT. Descriptions of both applications are included in this chapter.
Before you install optional software and service updates, refer to the specific instructions that accompany your installation media. If you ever need to reinstall your system, refer to the installation media instructions.
Note: For information about developing software products that are installed using the installp command, refer to Packaging Software for Installation in AIX 5L Version 5.1 General Programming Concepts: Writing and Debugging Programs.
If either of the following conditions apply to you, go to the referenced item. Otherwise, continue with the procedures in this chapter.
Before installing optional software or service updates, complete the following prerequisites:
In SMIT, you can set the DETAILED Output field to yes to list the files being restored during an install.
In Web-based System Manager, expand the Software container and choose Installed Software. From the Software menu, select New Software (Install/Update) --> Install Additional Software --> Advanced Method. In the resulting screen, choose the source drive and click on Advanced. In the resulting dialog, click beside Show detailed messages.
You can also use the installp command with the verbose option (-V2) to show which files have been updated.
unlinkbasecd umount /infocd
Optional software products and service updates can be installed using system management tools that come with the operating system. The following sections provide a brief description of the procedures:
The graphical interface provides access to Web-based System Manager options for installing the following:
The Web-based System Manager allows you to install software as well as to change the system's default install settings and specify other options. By default, the Web-based System Manager applies and commits any software updates you are installing. However, you can change this default setting and have only the software updates applied.
Note: Base software applications are always committed. If a previous version of the software is installed, it cannot be saved.
The following installation paths are available in SMIT:
|Install Software||Install or update software from the latest levels of software available on the media. To shorten the list of software displayed, message and locale software are omitted from the list. To use this option, type smit install_all on the command line.|
|Update Installed Software to Latest Level||Update all currently installed software to the latest level available on the installation media. To use this option, type smit update_all on the command line.|
|Install Software Bundle||Install complete bundles of software simply by specifying the input device and which bundle you are installing. You can also preview a bundle installation to see what software will be installed and how much space is required in the file system to install the bundle. To use this option, type smit install_bundle on the command line.|
|Update Software by Fix||Install a specific fix for a problem. This menu allows you to list all service fixes on the media and select a fix to install. You can also preview the installation to see what software will be updated and how much space is required in the file system to apply the fix. To use this option, type smit update_by_fix on the command line.|
|Install and Update from ALL Available Software||Install or update software from all software available on the media. To use this option, type smit install_all on the command line.|
Note: If a problem occurs during the installation of optional software that causes the installation process to halt abnormally, you might have to complete a cleanup procedure to remove the partially installed software from the system before attempting to reinstall it. If the system instructs you to do a cleanup, go to Cleaning Up Optional Software Products and Service Updates.
This section describes the system activity and actions that you must take after the installation process has begun.
Note: The system might prompt you to insert the volume of the installation media with a message similar to the following:
Mount volume 2 on /dev/cd0. Press the Enter key to continue.
When this message displays, insert the specified media and press Enter.
When the installation finishes, the Command: status field on the COMMAND STATUS screen changes to OK or failed. OK indicates that the installation ran to completion, although some filesets may not have installed successfully. The failed status means that there was a problem with the installation. Although a preview installation always finishes with an OK status, always check the summaries.
For information about error messages, refer to Acting on System and Error Messages.
If you need to install again and you have multivolume media, insert volume 1. Press F3 to return to the previous screen, then restart the installation. See Acting on System and Error Messages for information about bosboot command errors that may occur while the installation program is running, and about recovery procedures for these errors.
If you have additional software to install from a different installation media, remove the media that is in that drive and insert the new media.
Press F3 to return to the previous screen and continue installing the software product or service update.
During and after installation, four major maintenance actions can be taken with optional software products and service updates. Optional software and service updates can be:
Whether a particular action can be taken depends on whether the action is being applied to the entire software product, or only to a service update that has had a previous action taken on it.
You can perform these actions using either the Web-based System Manager or the System Management Interface Tool (SMIT) or by using commands directly from the command line. The following sections briefly describe how to do each action using Web-based System Manager, SMIT, or a command. Both Web-based System Manager and SMIT provide online help to guide you through each process.
When installing a service update, it can be left in the applied state. In this state, the former version of that software product is saved in the /usr/lpp/PackageName directory. Service Updates in the applied state allow you to restore the former version of the software without having to reinstall it.
Only service updates can be placed in the applied state. In contrast, after you install an entire software product, the product is left in the committed state. Software products in the committed state do not save the previous version of the software, because two versions of the same software product cannot be installed at the same time.
Committing a service update removes the previous version of a product from the system, which conserves disk space. After a software product or update has been committed, it cannot be deleted from the system except by removing the entire software product (the base level product and all of its updates) or by force-installing it back to a previous level. You must have the base level of the fileset available on media to do a force-installation.
Although applying and committing a service update are considered separate actions, both can be accomplished while installing the update. In fact, the default action under Web-based System Manager and SMIT is to both apply and commit the service update during installation. This default can be changed to just apply the update.
You can list all service updates in the applied state by selecting List Installed Software-->Updates in Applied State from the Software menu.
You can list all service updates in the applied state by typing smit list_installed on the command line.
You can list all service updates in the applied state by typing installp -s on the command line.
When you reject an applied service update, the update files are removed from the system and the previous version of the software is restored. Only service updates in the applied state can be rejected. You can use the Web-based System Manager or SMIT to reject applied service updates.
When you remove a software product, that product's files are removed from the system and the Software Vital Product Data information is changed to indicate that the product is removed. The remove process also attempts to restore the system's configuration to its previous state, although this is dependent on the product and might not always be complete. After a product is removed, no version of that product remains running on the system.
Use the Web-based System Manager or SMIT to remove software products. In either application, if you set the Remove dependent software? field to yes, any requisite software (software that is dependent on the product you are removing) is also removed, unless it is required by other software on your system.
Note: This procedure applies only to the update or installation of optional software products. If your AIX 5.1 BOS installation was unsuccessful, see Accessing a System That Does Not Boot for more information.
This section describes how to clean up software products and service updates after an interrupted installation. The cleanup procedure attempts to delete items that were partially installed or left in an incomplete state. For example, after an update is interrupted, the lslpp -l command might report the update status as applying rather than applied.
The cleanup procedure attempts to revert the update to its previous state. For example, when cleaning up an update that was interrupted in the committing state, the cleanup procedure attempts to return the update to its applied state.
If the interruption occurs during the initial state of an installation, then the cleanup procedure attempts to delete the installation entirely and restore the previous version of the product (if there is one). When the previous version is restored, it becomes the active version. When the previous version cannot be restored, the software is listed by the lslpp -l command as BROKEN.
When the product is deleted or BROKEN, you can attempt to reinstall the software. Any product in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.
The system automatically initiates a cleanup when an installation fails or is interrupted. Normally, you must initiate a cleanup procedure if the system shuts down or loses power during an installation or if the installation process terminates abnormally. Occasionally, you are prompted to reboot (restart) the system after running the cleanup procedure.
If you get a message indicating that no products were found that could be cleaned up, you may have executed the cleanup procedure when it was not needed. Try your installation again.
If you get a message indicating that you need to clean up a failed installation, contact your point of sale for assistance.
At this point, you might want to do the following: