INSTALLATION

Using silent server installation to install Domino on Windows systems
Use Domino's silent server installation to install local or remote servers without any intervention during the installation process. There is no need to monitor the installation or to provide additional input through the typical installation dialog boxes.

Before running Domino's silent server install on a Windows system, do the following:

Silent Server Install on Win32 systems

There are two steps to running a silent server install.

1. Create or record the response file, which contains the installation configuration information.

2. Run the install in "playback mode," referencing the response file.

Creating the response file for silent server installation

A typical (non-silent) install uses dialog boxes to receive input from you during installation. The silent (automated) server install receives input from the InstallShield Silent Response File (*.iss) and does not prompt you for input. This response file is a plain text file consisting of sections containing data entries. The file format resembles that of an *.ini file. You can create the ISS response file manually or by recording a server install which is then saved in the response file.

To record a response file

Run the server install with the command line parameter -r as shown below:


InstallShield records your installation choices in the file SETUP.ISS and places the file in the folder C:\WINNT. The installer's dialog box functions are designed to write values into SETUP.ISS when SETUP.EXE is run with the -r switch.

Sample response file for Lotus Domino

Use the following sample response file as a guide when creating your own response file.

# This is a sample response file for Lotus Domino

# All response files begin with a silent header. The silent header allows

# InstallShield to identify the file as a legitimate response file. It

# also helps to verify that the file corresponds to an setup created

# with the proper version of InstallShield.

[InstallShield Silent]

# The Version=v5.00.000 line indicates the version of the InstallShield

# Silent response file, not the version of InstallShield.

# Always use v5.00.000

Version=v5.00.000

File=Response File

# The application header is the second block of information in the

# response file, immediately following the silent header. The

# application header identifies the product being installed.

[Application]

Name=Domino

Version=6.0

Company=Lotus

Lang=0009

# Any global settings used by the installer appear here.

[File Transfer]

OverwriteReadOnly=NoToAll

# The next block of information is the dialog box sequence.

# The dialog box sequence section lists all dialog boxes you would need to

# use in a normal setup (including custom dialog boxes), in the order in

# which they would appear.

[DlgOrder]

Count=7

Dlg0=SdWelcome-0

Dlg1=SdLicense-0

Dlg2=SdRegisterUser-0

Dlg3=SdAskDestPath-0

Dlg4=SdSetupType-0

Dlg5=SdSelectFolder-0

Dlg6=SdFinishReboot-0

# The last block of information is the dialog box data. This

# is a collection of sections containing the values returned by each dialog

# box identified in the dialog box sequence section. Each dialog box has

# its own section. The values listed are the same values that the

# dialog box returns in a normal, user input-driven setup.

# SdWelcome is the initial dialog box that is displayed.

[SdWelcome-0]

Result=1

# SdLicense is the dialog box that displays the license agreement.

[SdLicense-0]

Result=1

# SdRegisterUser is the dialog box that displays information about the user

# installing Domino.

# It is only used for display.

[SdRegisterUser-0]

szName=Jane Doe

szCompany=IBM

Result=1

# SdAskDestPath is the dialog box which prompts for the path to install

# Domino to.

# szDir is the location of the Program Files.

# szDir1 is the location of the DataFiles.

# gUpgrade=0 for clean installs and =1 for upgrades.

[SdAskDestPath-0]

szDir=C:\Lotus\Domino

szDir1=C:\Lotus\Domino\Data

gUpgrade=0

Result=1

# SdSetypType is the dialog box which prompts for the install type.

# szSetupType can be one of the following values, which correspondes to a

# radio button in this dialog

# Domino Utility Server

# Domino Messaging Server

# Domino Enterprise Server

[SdSetupType-0]

szSetupType=Domino Messaging Server

bCustomize=0

Result=1

# SdSelectFolder is the dialog box which prompts for the menu item name

# that is used on the Program Files menu.

# szFolder is the value used.

[SdSelectFolder-0]

szFolder=Lotus Applications

Result=1

# SdFinishReboot is the last dialog box displayed after the install has

# finished.

# BootOption controls wether or not the machine reboots after the install

# has finished.

# the bOpt1 and bOpt2 items are not used.

[SdFinishReboot-0]

Result=1

BootOption=0

Running the Silent Server Install on Win32 Systems

To create a response file for automating the Lotus Domino installation, you must pass command line parameters to SETUP.EXE. The command line parameters are listed and explained in the table in Step 2.

When the response file has been created, perform the silent install of the Domino server.

1. Copy the file SETUP.ISS into the folder that contains the file SETUP.EXE.

2. Launch the server install with any of the command line parameters shown in the table below.
ParameterDescription and example
-sRuns the basic silent server install.

For example, setup.exe -s

Note You can use -s and -f1 together, or you can use -s by itself to run the silent install.

-rRecords in a response file, all of the installer selections you use. By default, the response file is SETUP.ISS stored in the Windows directory.

For example, setup.exe -r

Note You can use -r and -f1 together, or you can use -r by itself to record the response file.

-pbTo view a progress bar during the installation, use the -pb switch.

For example, setup.exe -pb -s

-f1To specify an alternate location and a response file name (.iss file), use the -f1 switch. If this switch is used, the response file is read from the folder/file specified in <path\ResponseFile>.

For example, setup.exe -s -f1<path\ResponseFile>

-f2To specify the alternate location and name of the log file created by the silent install. By default, the file SETUP.LOG is created and stored in the same directory as that of SETUP.EXE .

For example, setup.exe -s -f2<path/LogFile.Log>

SMSTo prevent the network connection and the file SETUP.EXE from closing before the silent install is complete, use the switch SMS. The SMS switch works with installations that originate from a Windows NT server over a network. SMS is a case-sensitive switch and must be entered in uppercase characters only.

The Log File

With the exception of the progress bar, no messages are displayed during the silent server install. Instead, the log file, SETUP.LOG, captures install information and error messages, including whether the setup was successful. The default location of SETUP.LOG is the same as that of the response file, SETUP.ISS. You can review SETUP.LOG to determine installation results.

SETUP.LOG contains the following three sections:

See also