Installation Guide

Chapter 4. Optional Software Products and Service Updates

After the Base Operating System (BOS) is installed, you might want to install optional software or service updates.

Optionally installable software includes:

Optional Software Products: Software that is not automatically installed on your system when you install the Base Operating System (BOS). Software products include those shipped with the operating system and those purchased separately. The BOS is divided into subsystems that can be individually updated, such as bos.rte.install. Any update that begins with bos.rte updates a BOS subsystem.

Note: If you are installing the Kerberos package or the DCE server software, see Appendix D, Installing Kerberos Version 5 for important configuration information.
Service Updates: Software that corrects a defect in the BOS or in an optional software product. Service updates are organized by filesets. This type of update always changes part of a fileset.

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.

Software Product Identification

The product name and level number identify a software product. The format for a software product level in AIX 5.1 is:

versionnumber.releasenumber.modificationlevel.fixlevel

Each field in the software product identification is defined as follows:

The versionnumber field consists of 1 to 2 digits that identify the version number.
The releasenumber field consists of 1 to 2 digits that identify the release number.
The modificationlevel field consists of 1 to 4 digits that identify the modification level.
The fixlevel field consists of 1 to 4 digits that identify the fix level.

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 4.1.0.0.

Software Licensing

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.

Installing Optional Software Products and Service Updates

If either of the following conditions apply to you, go to the referenced item. Otherwise, continue with the procedures in this chapter.

If you need to commit updates or remove previously installed software, go to Maintaining Optional Software Products and Service Updates.
If you are using a network installation server, refer to AIX 5L Version 5.1 Network Installation Management Guide and Reference.

Step 1. Completing the Prerequisites

Before installing optional software or service updates, complete the following prerequisites:

You must be logged in to the system as the root user.
AIX 5.1 BOS must be installed on your system. If the BOS is not yet installed on your system, go to Chapter 1, Installing the Base Operating System, or if you are installing over a network, refer to the AIX 5L Version 5.1 Network Installation Management Guide and Reference.
Either insert the media that contains the optional software or service updates into the appropriate drive or know the local or routed path to the software.
If you are installing service updates and do not have a current backup of your system, use the procedures in Chapter 6, Creating System Backups. To create a system backup, you must have the backup fileset (bos.sysmgt.sysbr) installed on your system.
If system files have been modified, it is a good idea to back them up separately before updates are applied, because the update process might replace configuration files.
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.
If you are installing from CD-ROM or DVD-ROM and currently have a mounted documentation CD in the same CD/DVD-ROM drive that you want to install from, run the following commands in the sequence shown:
```
unlinkbasecd
umount /infocd
```
Press the eject button on the CD/DVD-ROM drive for at least two seconds to eject the documentation CD/DVD-ROM.

Step 2. Completing the Installation

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:

Web-based System Manager Installing Optional Software Products or Service Updates with Web-based System Manager
System Management Interface Tool (SMIT) Installing Optional Software and Service Updates Using SMIT

Installing Optional Software Products or Service Updates with Web-based System Manager

The graphical interface provides access to Web-based System Manager options for installing the following:

Optional software Installing Optional Software
Service updates Installing Service Updates
Software bundles Installing Software Bundles

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.

Installing Optional Software

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand Software in the Navigation area.
Select Overview and Tasks.
Select Install Software.

Installing Service Updates

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand Software in the Navigation area.
Select Overview and Tasks.
Select Update Software to the Latest Level.

Installing Software Bundles

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand Software in the Navigation area.
Select Installed Software.
From the Software menu, select New Software (Install/Update) --> Install Bundles (Easy).

Installing Optional Software and Service Updates Using SMIT

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.

Completing the SMIT Installation and Reading the Status Messages

This section describes the system activity and actions that you must take after the installation process has begun.

When you press Enter to start the installation, the COMMAND STATUS screen displays. A series of messages display as the installation proceeds. The amount of time that the installation takes varies depending on your system and the software you are installing and updating.
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.
When the installation halts or finishes, the screen returns to the top of the list of messages that display during installation. You can review the message list as described in the next step, or you can exit SMIT and review the smit.log file (/smit.log or /home/user_id/smit.log).
Review the message list for error messages on software products or service updates that may not have been successfully installed. Use the following procedure to correct any errors in the installation:
1. Look at the pre- and post-installation summaries at the end of the message list to see whether any installation failure occurred.
2. Use the message list to determine problems and which software products or service updates were involved. For example, space limits might have been exceeded or the requisites might not have been met for some software. The system lists how much extra space is needed and which requisite software products or service updates to install.
3. Any product that is marked as FAILED, BROKEN, or CANCELLED can be reinstalled after the condition that caused the failure has been corrected. You do not need to reinstall any service update or software product that was marked as SUCCESS in the Installp Summary report. If you need to perform the installation again, change installation settings as appropriate. For example, if requisites were missing, set AUTOMATICALLY install requisite software? to yes. If there was not enough space to complete the installation, set EXTEND file systems if space needed? to yes.
  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.
4. If the installation was interrupted (for example, a power failure), you might need to use the cleanup procedure before continuing. Press F10 to exit SMIT, and refer to Cleaning Up Optional Software Products and Service Updates.
5. If the software has been installed successfully, and you have no other software to install, go to Step 4.
  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.
Press F10 to exit SMIT.
Remove all installation media from the drives.
Reboot your system when you are directed by typing:
```
shutdown -Fr
```

Maintaining Optional Software Products and Service Updates

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:

Applied Apply Action (Service Updates Only)
Committed Commit Action (Service Updates Only)
Rejected Reject Action (Service Updates Only)
Removed Remove Action (Software Products Only).

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.

Apply Action (Service Updates Only)

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.

To apply a service update using Web-based System Manager:

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand Software.
Select Overview and Tasks.
Select Update Software to the Latest Level.

To apply a service update using SMIT:

Type smit update_by_fix on the command line.

To apply a service update from the command line:

Use the installp -a command to only apply the update.

Commit Action (Service Updates Only)

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.

To commit a service update using Web-based System Manager:

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand the Software container.
Select Installed Software.
From the Software menu, choose Software Utilities --> Commit Applied Updates.

You can list all service updates in the applied state by selecting List Installed Software-->Updates in Applied State from the Software menu.

To commit a service update using SMIT:

Type smit commit on the command line.

You can list all service updates in the applied state by typing smit list_installed on the command line.

To commit a service update from the command line:

Use the installp -c command to commit applied updates.

You can list all service updates in the applied state by typing installp -s on the command line.

Reject Action (Service Updates Only)

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.

To reject a service update using Web-based System Manager:

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand the Software container.
Select Installed Software.
From the Software menu, choose Software Utilities --> Reject Applied Updates.

To reject a service update using SMIT:

Type smit reject on the command line.

To reject a service update from the command line:

Use the installp -r command to reject an applied update.

Remove Action (Software Products Only)

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.

To remove a software product using Web-based System Manager:

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand the Software container.
Select Installed Software.
Select the software product you want to remove.
From the Selected menu, choose Remove Software.

To remove a software product using SMIT:

Type smit remove_fast on the command line.

To remove a software product from the command line:

Use the installp -u command to remove the product.

Cleaning Up Optional Software Products and Service Updates

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.

To initiate a cleanup procedure using Web-based System Manager:

Start the Web-based System Manager by typing wsm on the command line.
Expand the machine name.
Expand the Software container.
Select Installed Software.
From the Software menu, choose Troubleshooting --> Cleanup Failed or Interrupted Installation.

To initiate a cleanup procedure using SMIT:

Type smit maintain_software on the command line.
Select Clean Up After Failed or Interrupted Installation.

To initiate a cleanup procedure from the command line:

Type installp -C on the command line.

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.

Where Do I Go Next?

At this point, you might want to do the following:

Read the README files that were shipped with the operating system. Any additional software you installed also might have associated README files with late-breaking news. For information on how to view README files, refer to Viewing README Files.
Go to Chapter 5, Documentation Library Service and Online Documentation and read the introductory material. This chapter guides you through installing the Documentation Library Service or the operating system's online documentation.
Create a new backup of your system. Go to Chapter 6, Creating System Backups.