1.
Determine if CSF
or 4690 install.
2.
Ensure InSight
logical names are defined.
3.
Ensure InSight
directory structure is created.
4.
Prompt for store
description if new installation.
5.
Determine if MCF
system. If MCF, ensure acting master node.
6.
Remove old
uninstall files from ADX_UPGM: and ADX_UDT1:
7.
Shutdown InSight
tasks on all reachable nodes and terminals using “insight –disable”
8.
Create temp
install directory
9.
Separate
compressed install .zip or .jar from insighti.286 and expand it
into temp install directory.
10.
Log current
contents of InSight directories [future].
11.
Copy current
contents to BUL directory if 4690 test mode install option is being
used [future].
12.
Copy QSA_BIN:
files from temp dir.
13.
Copy sample CDI
files from temp dir.
14.
Copy ‘always
add/replace’ QSA_DIR: files from temp dir. For example, readme and
license files.
15.
Copy ‘add if new’
QSA_DIR: files from temp dir. For example, default CDI file.
16.
Create PCF file
17.
Delete temp
install directory
18.
Verify/create QSA
directories on remote nodes
19.
Verify
distribution attributes for all files
20.
Update user
logical names active and inactive files for all nodes
21.
Update background
task active and inactive files for all nodes (if controller agent
is to run as normal 4690 background task which is how it runs by
default).
22.
Update message
file
23.
Add/update
line(s) in ipl command processor file which loads controller driver
24.
Unload old/load
new insight controller driver
25.
With help of
driver, ensure that InSight logicals are system logicals.
26.
Start controller
agent if agent is to run as hidden/system background task.
27.
Add InSight
terminal agent to 4690 terminal loadshrink image and rebuild image.
28.
Reload all
terminals.
Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |