The installation routine of the Agents onto workstations by using the network installer (drwinst.exe) is set by install.script. These files reside in the products root folder in the repository. In standard distributions they are located in the 10-drwupgrade and 20-drwagntd catalogs and describe the default installation.
If the .custom.install.script file is present in the folder, it is used instead of the standard installation routine.
|
Files with other names beginning with a period are not updated during the product update and do not influence the operation of the repository. |
The sequence of operations during the installation:
1.The network installer requests the Server for the installation of the following platforms: win-setup, common, win, win-nt and win-9x – this is the list of standard platforms in the default order. The order of use of the platforms can be changed by the -platforms=p1,p2,p3... switch when calling drwinst. The win-setup platform is not included into a standard distribution and is designed for creation of its own installation routines, if necessary.
2.The Server forms a list of files according to the list of platforms, viewing all products step by step in alphabetical order and lists of files set by the files{ } constructions for the given platform in the install.script installation routine (read below). At the same time, the summary script is created on the basis of the scripts{ } constructions.
3.The Server receives the general list of files and the summary script.
4.The Server sends the files and the script which will be executed by the network installer.
Now we consider install.script by example of the 20-drwagntd folder.
; master part of installation: Agent & its stuff. ; drwscr.dll goes with upgrader, so unlisted here.
platform{ ; win - for all Windows OS ; `name: XXX' MUST go first!
name: win ; (mandatory stanza) ; this platform name
; include, scripts{ }, files{ } ; can go in any order
scripts { ; (optional) ; script being merged with all others win.inst.rexx ; and executed after transfer all ; files for all platforms requested ; by installer ; Windows installer request order: ; - win-setup (optional! for ; customization) ; - common ; - win ; - win-nt OR win-9x }
files { ; (optional) ; this platform files being ; transfered to installer win/uninstall.rexx win/drwinst.exe win/drwagntd.exe win/drwagnui.exe win/drwhard.dll } }
platform { ; win-9x - for Windows 95-ME name: win-9x scripts{ win-9x.inst.rexx } }
platform { ; win-nt - for Windows NT-2003 name: win-nt scripts{ win-nt.inst.rexx } }
platform { ; common - for any OS including UNICES name: common scripts { common.inst.rexx } }
; include file.name ; (optional) ; this stanza tells to include other file. ; including file will be searched in the ; same folder where current file are ; located if `file.name' does not include ; folder specificator |
The script contains a list of the platform{ } constructions and allows to include determinations from other files with the help of the include construction (include is admissible on the upper level only and is inadmissible inside platform{ }). If file.name in include does not contain paths, but a file name only, it is searched for in the same folder as the current one. The use of include constructions in the included files is allowed.
The description of a platform begins with the name: XXX construction. Then, the pair of files{ } and scripts{ } lists follows; the order of these lists is inessential. The lists may contain any number of elements. The order of elements in the list is essential as it defines the order of files transferred to the station and the construction of the formed script.
The order of the platform{ } constructions is also inessential.
The variables of the installation scripts (the values for these variables can be specified from the command line of the network installer) with their default values are listed below:
◆spider.install = 'yes'
◆spiderml.install = 'yes'
◆scanner.install = 'yes'
◆install.home – installation folder
◆agent.logfile = install.home'\logs\drwagntd.log'
◆agent.loglevel = 'trace'
◆agent.logrotate = '10,10m'
◆agent.servers = install.servers
◆agent.serverkey = install.home'\drwcsd.pub'
◆agent.compression = 'possible'
◆agent.encryption = 'yes'
◆agent.findretry = '3'
◆agent.findtimeout = '5'
◆agent.spiderstatistics = '30'
◆agent.importantmsg = '2'
◆agent.discovery = 'udp/:2372'
◆agent.startmsg = '2' (or agent.startmsg = 'NONE')
The agent.importantmsg parameter defines displaying the messages on the updating error, on the reboot request, etc. to a user. 0 — do not display, 1 — display a pop-up notification.
Now we create a nonstandard installation scenario in which SpIDer Guard is not installed and maximum detailed logging is set:
1.Create a .win-setup.inst.rexx file in the 20-drwagntd folder and write to it
spider.install = 'no' agent.loglevel = 'all' |
2.Create the .custom.install.script file in the 20-drwagntd folder and write to it
include install.script
platform{ name: win-setup scripts{ .win-setup.inst.rexx } } |
3.Reboot the Server or instruct to reboot the repository:
◆for UNIX OS: kill -USR1 cat `drwcsd.pid`
◆for Windows: drwcsd.exe rerepository