Tivoli Storage Manager Installing the Clients


Appendix C. Customizing the Installation for Windows

TSM provides default options for the backup-archive client, administrator client, and the server. You can customize these options as well as the setup and readme files, to meet your particular installation requirements. To customize the installation for Windows, you can perform any of the following steps:


Setup Command Line Switches

The Setup.exe is the main installation program file for the TSM clients for Windows. You can customize, rename, and distribute the Setup.exe program with any other filename. There are no restrictions.

Table 31 contains the list of command-line parameters that you can use with Setup.exe. These switches are optional, but note that either a slash (/) or a dash (-) must precede the command-line parameters. Separate multiple command-line parameters with a space; but do not put a space inside a command-line parameter (for example /r /fInstall.ins is valid, but not /r /f Install.ins).

When using long path and file name expressions with switches, enclose the expressions in double quotation marks. The enclosing double quotes tell the operating system that spaces within the quotation marks are not to be treated as command-line delimiters.

Table 31. Command Line Parameters to Use with Setup.exe

Command Line Parameter Description
-f<path\CompileScript> The alternate compiled script can be specified using this option. Unless the compiled script (.ins file) also resides in the same directory as Setup.exe, the full path to the compiled script must be specified.
-f1<path\ResponseFile> The alternate location and name of the response file (.iss file) can be specified using this option. If this option is used when running InstallShield Silent, the response file is read from the folder or file specified by <path\ResponseFile>. If this option is used along with the r option, the response file is written to the folder or file specified by <path\ResponseFile>. If an alternate compiled script is specified using the f switch, the f1 switch entry must follow the f switch entry.
-f2<path\LogFile> The alternate location and name of the log file created can be specified by using this option. By default, Setup.log log file is created and stored in the same directory as that of Setup.ins. If an alternate compiled script is specified using the f switch, the f2 switch entry must follow the f switch entry.
-r Causes Setup.exe to automatically generate a silent installation file (.iss). The .iss file is a recording of the installation process stored in the WINDIR folder.
-m<filename> Causes InstallShield to generate a Management Information Format (.MIF) file automatically at the end of the installation. If you do not include a path, the MIF file is always placed in the Windows directory. The filename is optional. If you do not specify a filename, the resulting file will be called STATUS.MIF.
-m1<serial number> Instructs the InstallShield to place the indicated serial number in the created .MIF file.
-s Run InstallShield Silent to do a silent installation
-SMS (note only the SMS switch is case sensitive) The SMS switch prevents a network connection and the Setup.exe from closing before the installation is complete. The switch works with installations originating from a Windows NT server over a network. Please note that SMS must be uppercase; this is a case-sensitive switch.

Setup Usage Examples

This section contains some examples of using the setup command.

setup -s
Launches InstallShield Silent and tries to load SETUP.INS and SETUP.ISS from the directory containing Setup.exe. The log file SETUP.LOG is created in the same directory.
setup -s -f1c:\mydir\mydir.iss
Launches InstallShield Silent, tries to load SETUP.INS from the same directory, and uses MYDIR.ISS (from the C:\MYDIR directory) as the response file. This example also creates the log file SETUP.LOG in the same directory as that of the response file (C:\MYDIR).
setup -s -f1c:\mydir\mydir.iss -f2c:\mydir\mydir.log
Launches InstallShield Silent, tries to load SETUP.INS from the same directory, uses MYDIR.ISS from the C:\MYDIR directory, and generates log file MYDIR.LOG in the C:\MYDIR directory.

Silent Installation

This installation package comes with a ready-made response file called setup.iss, to perform a Typical setup using default values. This setup installs the Backup-Archive Client, the API, and the Web Client. If you want to create your own response file, perform the following steps:

  1. Start setup.exe with the -r (record mode) option:
      setup -r
    
  2. Select the Typical, Custom, or Compact setup option to use for your silent installation.
  3. After the setup completes, change directory to the Windows system directory (\winnt for Windows NT, \windows for Windows 95 or 98), and copy the setup.iss file to the directory containing the as the setup.exe program.

Performing a Silent Installation

To perform a silent installation, do the following:

  1. Ensure that you have the response file, setup.iss, in the directory containing the setup.exe program.
  2. Run setup.exe with the -s (silent mode) option:
       setup -s
    
    Note:The results of the installation are recorded in the setup.log file which is created in the directory containing the setup.exe file. A result code of 0 (zero) indicates a successful installation.
  3. A window displays asking you if you want to reboot.

SETUP Error Messages

The Setup.exe program may produce error messages if it cannot start properly or when a severe error occurs. When you get an error message, it appears in a message box. Every error message has a number. These are system error messages and cannot be suppressed in your script.

If you encounter an error, refer to the InstallShield support Web page at URL http://support.installshield.com/default.asp, and use the Search facility to obtain information.


TSM Sentinel Files

These files specify whether a TSM installation was successful and are created in the base directory of the TSM installation; typically c:\"program files"\tivoli\tsm. If the installation is successful, the file adsm.ok is created. If the installation is not successful, the file adsm.err is created. Other programs may watch for creation of this file to determine if unattended installation has completed.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]