1.
Installer should
be trivial to run for first-time users. Single-step a:install is
the goal. Intelligent defaults should be chosen so that InSight
will be operational on customer lab systems after installation.
Logical names, device drivers, message file and background task
configuration should all be automatic.
2.
Installation
should not require controller reboot.
3.
Try to fit
installer on a single diskette.
4.
Installation
should handle multiple nodes. All nodes should not have to be
present at time of installation. For MCF systems, installation will
be done from acting master.
5.
Installer should
handle both new install and upgrade install.
6.
For customers who
want to control their own installation, CDI options can control
InSight installation process. For example, user may not want all
steps automated.
7.
Installation
should be compatible with 4690 Apply Software Maintenance (ASM).
InSight installer should generate an ASM Product Control File and
other associated files.
8.
Single step
uninstall (will also provide single step InSight enable/disable).
| Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |