Specifications

Lotus Redbooks Wiki – IBM Lotus Notes and Domino V8.5 Deployment Guide
120
Server Locations
If, at a certain point, the custom installation package needs to be configured to be installed from a file server
location (as opposed to a local installation, be it on the local hard disk or on a CD/DVD) and that there are
additional server location paths specified, it is possible that the Lotus Notes client might need to access
sometimes these locations after the initial install of the server. The Notes client can also require access to a
specified server is a file is removed or becomes corrupt, as the Notes client can copy the problematic file(s)
automatically from the server.
In order to ensure that the users have always access to a server that is available on the network in such
circumstances, it is possible to copy the custom installation package to one or more additional servers and
then to indicate these servers from the above page. If the primary file server were to become unavailable --
for whatever reason -- the installer will try to connect to the other servers specified here, in the order they
are listed. If no server is found, the Windows installation program will invite the user to specify an
appropriate server.
Setup Properties
The Setup properties page exposes the entries in the properties table (the fundamental structure of
InstallShield-based installation kits) which includes options that are not available elsewhere in the
Installshield Tuner. It is also possible to add custom-made properties here.
Properties exist in two formats: Private and Public.
• Private properties are placed by the company that provides the software or placed by the
installation program at install time and cannot be changed. The private properties are always
written in lowercase and appear in InstallShield Tuner are grayed out entries.
• Public properties are always written in uppercase and can be also placed by the company that
provides the software, but can be edited. InstallShield Tuner permits equally the addition of public
properties to the transform file. The public properties that are custom created can be edited or
deleted as needed, while public properties that existed at the onset can only be edited.
Important: Before all these changes can be made to the properties appearing in the setup properties table,
that carefully consideration be applied beforehand. Changes may create validation errors, installation errors
or other unplanned and unexpected problems. Especially when changing the default installation path, go
through all these options to ensure, at a minimum that the path C:\Program Files\Lotus (...) is replaced by
your custom path (for example "C:\Lotus" (...).
Dialogs
This sub category allows to activate or deactivate dialog boxes that appear in the four interface sequences
to the end user in the package that we are in the process of customizing
By selecting the installation mode, it is possible to see the dialogs associated with the installation sequence,
(1) the administration sequence, (2) the maintenance sequence or (3)the patch sequence for the installation
package. Another option (4) admin sequence will appear if you’re depliying a combined client which also
contains the administrator and designer client.
By clicking on the selection box at the left of the dialog name to display it (or not display it) when users
execute the installation package in this mode.
Properties for each dialog can be shown by clicking on "Properties". Clicking on "Preview".will provide an
example of how the dialog box will look like at runtime.