1.6 Silent Installation of iManager

iManager provides a silent (non-interactive) installation option that doesn’t display a user interface and poses no questions to the user. In place of user input, InstallAnywhere* uses information from a predefined properties file.

NetWare does not support a silent install.

Solaris GUI libraries must be installed for iManager’s silent install option as well as its normal installation option. The iManager installer for Solaris does not support command line (text-based) or headless installation.

There are two silent installation options:

1.6.1 Standard Silent Install

To perform a standard silent install on Linux, Windows, Solaris, or HP-UX, accepting all default values:

  1. Open a console window and go to the directory containing the iManager file you downloaded.

  2. On the command line, enter the following for Linux, Solaris, or HP-UX:

    ./iManagerInstall< platform>.bin -i silent

    or enter the following for Windows:

    iManagerInstall.exe -i silent

1.6.2 Customized Silent Install

The customized silent install uses an installer.properties file to provide the desired installation options to the install program. An installer.properties file can include the following entries:

CONFIGIMAN_DIRECTORY= (Optional) Specifies a directory tree in which the authorized user object is located. The CONFIGIMAN_USER_CONTEXT entry specifies the authorized user object.

CONFIGIMAN_USER_CONTEXT= (Optional) Specifies an authorized user for iManager. The authorized user can manage the iManager environment, including installing plug-ins and changing iManager server settings. If you leave this entry blank, all users can perform these authorized user activities. For more information, see Authorized Users in the iManager 2.6 Administration Guide.

TOMCAT_HTTP= Specifies the Tomcat HTTP port for use by iManager. The default value is 8080.

TOMCAT_SSL= Specifies the Tomcat HTTPS port for use by iManager. The default value is 8443.

TOMCAT_JK= Specifies the MOD_JK connector port Apache uses to send requests to Tomcat. The default value is 9009.

APACHE_CONF_DIR= (Optional) Specifies the path to an existing Apache httpd.conf file. Use this entry when installing iManager into an existing Apache environment.

PLUGIN_INSTALL_MODE= Specifies the plug-in installation mode. Options include the following:

  • (Default) NET: Specifies that plug-ins are installed from the network.

  • DISK: Specifies that plug-ins are installed from a local disk.

  • BOTH: Specifies that plug-ins are installed from both disk and network.

  • SKIP: Specifies that plug-ins are not installed.

PLUGIN_DIRECTORY= (Conditional) Specifies the directory from which plug-ins are installed when PLUGIN_INSTALL_MODE is set to DISK or BOTH. All plug-ins in this directory are installed as part of the installation routine.

PLUGIN_INSTALL_URL= (Conditional) Specifies the URL from which to download plug-ins when PLUGIN_INSTALL_MODE is set to NET or BOTH. Leave this entry blank to use the default URL, which is http://www.novell.com/products/consoles/imanager/iman_mod_desc.xml.

LAUNCH_BROWSER= Specifies whether the install should launch a Web browser at the end of the installation routine and display iManager’s Getting Started page. The default value is TRUE.

PLUGIN_MODULE_ID_ x= (Conditional) Specifies the ID of a plug-in module to install as part of the installation routine when PLUGIN_INSTALL_MODE is set to NET or BOTH. The ID is listed in the \META-INF\MANIFEST.MF file, located in the NPM's folder.

The value of x in PLUGIN_MODULE_ID_ x should be incremented for each unique plug-in entry specified in installer.properties. If no modules are specified, the most commonly installed modules, tagged as typical in the iman_mod_desc.xml files on the download Web site, are installed.

PLUGIN_VERSION= (Conditional) Specifies the version of the plug-in specified in PLUGIN_MODULE_ID, to install as part of the installation routine. This entry is only used when PLUGIN_INSTALL_MODE is set to NET or BOTH.

The version is listed in the \META-INF\MANIFEST.MF file, located in the NPM's folder. If no version is defined for a module, then any module that matches the NPM name is installed.

To perform a customized silent install on Linux, Windows, Solaris, or HP-UX, which provides more control over which modules are installed:

  1. Create an installer.properties file in, or copy an existing file to, the same directory that contains the installer executable file.

    The installer.properties file should look something like the following:

    CONFIGIMAN_DIRECTORY=CONFIGIMAN_USER_CONTEXT=TOMCAT_HTTP=8080TOMCAT_SSL=8443TOMCAT_JK=9009APACHE_CONF_DIR=PLUGIN_INSTALL_MODE=NETPLUGIN_DIRECTORY=PLUGIN_INSTALL_URL=http://www.novell.com/products/consoles/imanager/iman_mod_desc.xmlLAUNCH_BROWSER=TRUEPLUGIN_MODULE_ID_2=pwdpolicyPLUGIN_VERSION_2=10.1.20060705PLUGIN_MODULE_ID_3=LDAPConfigurationPLUGIN_VERSION_3=2.5.20061108PLUGIN_MODULE_ID_5=eDirExtendedPLUGIN_VERSION_5=2.6.20061128PLUGIN_MODULE_ID_6=eDirectoryRepairAndLogfilePLUGIN_VERSION_6=2.5.20061103PLUGIN_MODULE_ID_7=eDirectoryMergePLUGIN_VERSION_7=2.5.20061103PLUGIN_MODULE_ID_12=eDirectoryBackupAndRestorePLUGIN_VERSION_12=2.5.20050908
    
  2. Launch the silent install with the following command:

    ./iManagerInstall platform.bin -i silent -f pathto_properties_file