5.7.7 Introducing
Software Installer
5.7.7 Introducing
Software Installer
This section discusses the installation steps required when migrating a previous version of OS/2 LAN or Warp Server or installing a pristine system.
The installation steps appear in this chapter logically divided into different phases roughly in the order that they need to be executed. Once in Presentation Manager mode, after Phase One, there are no real limitations on the order of installation. There are some prerequisites for specific products, and we highlight them.
We expect that, according to environmental requirements, you might want to add additional steps or modify the order.
| Note on Installation Order |
|---|
|
We have tried to highlight inter-dependencies between individual product installation steps, but it is impossible to guarantee that in your environment you will not encounter additional issues. Therefore, we repeat our advice that you fully test your CID environment prior to actually migrating a production system. |
The complete installation of all products can be divided into a number of broad phases. These help in understanding the different parts of the installation. The installation order within particular phases are, broadly speaking, only important in the preparation phase and Phase One. We highlight product prerequisites where they exist.
Some products require a reboot after installation. However, in many cases, it is possible to install multiple products before calling the reboot. Thus, the installation order can be optimized, depending on the set of products that are being installed, to reduce the number of overall system boots.
The first part of this section provides an overview of the installation order were we to install all of the available products.
This overview is followed with more detailed information on each product's individual installation requirements including prerequisites where they exist. It is in these sections that the working response files and LCU syntaxes are provided.
The first part of the installation involves procedures related to system preparation. This phase occurs in advance of the main installation and provides file system access to both the local disk and to the redirected installation drives. It also ensures that no system files are locked, which would prevent installation. The steps involved in this section are described below.
SEMAINT creates a minimal, maintenance system for the purposes of installation when system files would otherwise be locked. During migration, a maintenance system is necessary because a new version of the operating system is being installed over the top of an existing installation, and system files are locked.
During a pristine installation, this step is not required.
A maintenance system is a minimal version of the operating system that is stored in a different directory (that is, C:\MAINT instead of C:\OS2). It may be stored on a different partition, but this is not essential. The existence of a maintenance system eliminates the need to boot from diskettes.
OS/2 Warp Server for e-business includes a feature called Logical Volume Manager, which replaces older versions of OS/2's FDISK utility. LVM can handle the new logical volumes available with OS/2 Warp Server for e-business. This introduces some additional considerations into the installation scenario.
This program creates a seed LAN transport system.
The SrvIFS (Server Installable File System) provides an easy means of redirection. THINIFS installs the necessary SrvIFS redirection files on the hard disk.
This step is necessary for access to 386 HPFS volumes. We explain this in Section 5.11.4 386 HPFS.
CASINSTL installs the LAN CID Utility client code.
Phase One of the installation installs the OS/2 2.11 and a full LAN transport system.
The OS/2 2.11 is installed in two parts. In Phase One, SEINST installs the OS/2 2.11, after which, OS/2 boots to a Presentation Manager (PM) interface.
In Phase Two (see 5.8.3 Installation - Phase Two), additional applications are installed through the use of Feature Installer.
MPTS installs LAN transport code (Adapter and Protocol Services) onto the system.
Phase Two occurs in the Presentation Manager mode. During this phase, any or all of OS/2's installable features (which cannot be installed in maintenance mode) can be installed. The features are installed using OS/2 Feature Installer.
If SVGA display resolution is required (which generally is unnecessary on a server), it can be installed during this phase of installation. At the time of writing, however, Netscape Communicator requires 256-color support and, thus, installation of an SVGA display is essential. (A version of Netscape Communicator with 16-color support was expected for the final release of OS/2 Warp Server for e-business.)
New to OS/2 Warp, Version 4, and now included in OS/2 Warp Server for e-business, the Feature Installer program installs some additional OS/2 features. As previously mentioned, Feature Installer requires a OS/2 Presentation Manager (PM) interface. Feature Installer is also used to install other applications (see Section 5.7.6 Introducing &Feature. Installer.).
All other applications shipped with OS/2 Warp Server for e-business can also be installed in PM mode during Phase Two. However, for clarity, this section deals with what we consider to be the major applications. These include the File and Print Sharing Services and TCP/IP Application Services.
This installs File and Print Sharing Services, also known as OS/2 LAN or Warp Server.
386 HPFS provides improved access to large disk volumes, and it optimizes performance in a server environment where many files are open simultaneously from multiple clients.
If 386 HPFS is already installed on the system being migrated, it will be updated. If it is not already on the system, then it can be installed. The install uses Feature Installer. An additional license is required.
FFST/2, which used to be installed as part of OS/2 LAN Server or DB2/2, is now installed with the operating system during a local CD-ROM-based install.
In a CID environment, it must be installed by a separate install procedure.
Any subset or all of the TCP/IP Application Services can be installed. Individual requirements will vary between environments. It is installed using Feature Installer.
In addition to navigating the World Wide Web, Netscape Communicator can be used as a Graphical User Interface (GUI) for the installation, configuration, and uninstall of various products, for example, TCP/IP installation. It is installed using Software Installer.
Also installable in PM mode during Phase Two, this section considers applications that were included in OS/2 Warp Server, Version 4 but not in earlier versions of OS/2 LAN Server. We have grouped the applications here for reasons of clarity alone.
Personally Safe 'n' Sound (PSnS), or Backup and Recovery Services, was available in the Warp Server, Version 4 package and could be purchased also as a separate product. It is installed using Feature Installer.
LAN Distance Connection Server was available in the OS/2 Warp Server, Version 4 package and could be purchased also as a separate product. It has now been replaced by Remote Access Services (or PPP Server as it is known), which allows clients using the PPP protocol to use the LAN by dialing the Remote Access Services server. Any existing OS/2 LAN Distance must first be removed before installing the updated version.
Advanced Print Services, or Print Services Facility/2, allows you to print file formats that your printer typically does not support. For example, you can define print transforms that allow you to print postscript output on non-postscript printers.
The on-line books can be installed, if desired, during Phase Two using Feature Installer.
We believe that the majority of server administration in an Enterprise environment is conducted from an administrator client workstation. It is, therefore, not necessary to install this documentation on the server.
The last install section considers applications that have not been shipped with any previous versions of OS/2 LAN or Warp Server. These too can be installed in PM mode during Phase Two. We have grouped the applications here for reasons of clarity alone.
As these applications have not previously been available with OS/2 LAN or Warp Server, they should not be considered part of a true migration scenario. Instead, they are new applications and can be, therefore, considered new installations.
However, we understand that you might want to install these applications. Therefore, we briefly discuss installation of these applications and provide the necessary information required to complete the installation.
Netfinity Services supersedes OS/2 SystemView and TME10 Netfinity Server, Version 4. SystemView was included with OS/2 Warp Server, Version 4. An upgrade to TME10 Netfinity Server was available after initial shipment of OS/2 Warp Server, Version 4.
Netfinity Manager and Client Services are highly responsive hardware management features that support key systems management tasks. They can be installed in Phase Two of the installation.
OS/2 Warp Server for e-business supports Lightweight Directory Access Protocol (LDAP) client toolkit. It is installed using Feature Installer.
TMA is a replacement for the SystemView agent. It is used for managing PC Servers and supports OS/2 using TCP/IP. It can be installed in Phase Two using the Software Installer program.
OS/2 Warp Server for e-business includes a fully functional trial version of Lotus Domino Go Webserver. It can be installed during Phase Two of the installation using the Software Installer program.
WebSphere Application Server is a plug-in for Lotus Domino Go Webserver that adds Java support. It too can be installed during Phase Two of the installation but requires Lotus Domino Go Webserver to be functional prior to installation.
The final phase of the installation cleans the system up and removes all traces of the CID installation. In our environment, we leave the LCU and SrvIFS support installed on the systems but ensure that no connection exists with the remote server at boot time. We do this by removing the SRVATTCH statement from the client CONFIG.SYS file.
IFSDEL removes the files installed by THINIFS.
CASDELET removes LCU files from the system. It is executed as the last step.
At the time of writing, no fixpaks exist for any of the products in the OS/2 Warp Server for e-business package. If, at time of General Availability (GA), fixpaks are required for any of the individual products contained within the product, they should be applied during the overall installation.
We consider this step for completeness because some products, such as the Java Runtime Environment, are developing at a rapid pace.
If the products are OS/2 or LAN Server type products, then the update program to use will be FSERVICE. If the product is a Feature-Installed product, then Feature Installer should be used to update the program. If the product is a Software-Installed product, then Software Installer should be used to install the fixpak. The update could be an update or a replacement.
Generally, at least one reboot should have taken place between the installation of the base product and the fixpak or update installation although, in the case of an update, it will probably be possible to substitute the product in the installation scripts.
5.9 CID Installation
Parameters