24
Novell iManager 2.7 Installation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
1.6.2 Customized Silent Install
To perform a customized silent install for more control over which modules are installed:
1
Create an
installer.properties
file in the same directory that contains the installer
executable file.
2
To perform a silent install using the installer.properties file, enter:
./iManagerInstall
platform
.bin -i silent -f
pathto_properties_file
3
In
installer.properties
, set and save the following values for:
$PLUGIN_INSTALL MODE$: The property that controls whether plug-ins are installed
from disk, network, both disk and network, or neither.
If plug-ins are to be installed from disk, set this property to DISK. This is the default
value.
If plug-ins are to be installed from the network, set this property to NET.
If plug-ins are to be installed from both disk and network, set this property to BOTH.
If plugins are not to be installed, set this property to SKIP.
$PLUGIN_DIR$: The property that defines an alternate path where plug-ins are located
on disk.
The default path is
installer_root_directory
/iManager/installs/
platform path
/plugin
All modules found in the plug-in directory are installed, except for subdirectories.
$PLUGIN_INSTALL_URL$: The property that specifies the URL where plug-ins are
located.
You can modify this URL. For more information, see “
Downloading and Installing Plug-
in Modules
” in the
iManager 2.7.3 Administration Guide
.
$LAUNCH_BROWSER$: The property that enables/disables launching of
gettingstarted.html
when the iManager installation completes.
$USER_INSTALL_DIR$: The property that specifies the default path where iManager is
to be installed.
4
To specify particular modules to download, use the following examples, providing the module
ID and version from the
MANIFEST.MF
file, located in the NPM's META-INF/ folder.
$PLUGIN_MODULE_ID_1$=eDirectoryBackupAndRestore
$PLUGIN_VERSION_1$=2.7.20050517
$PLUGIN_MODULE_ID_2$=ldap
$PLUGIN_VERSION_2$=2.7.20050517
etc. . . . (repeated as many times as there are modules)
If no modules are defined, then the most commonly installed modules, tagged as “seleceted” in
the
iman_mod_desc.xml
files on the download Web site, are installed.
If no version is defined for a module, then any module that matches the NPM name is installed.
