1.Allows the user to select which components to install.
The user can install any combination of the following: Learning Management Module (LMM) server application, the Delivery Server (DS) application, LMS Authoring Tool, and/or LMS utilities
2.Prompts the user for the following information, depending upon which components are selected:
•LDAP settings (URL, base distinguished name (DN), username and password, provider). If the LDAP server is available, there's a button that allows the user to test the LDAP connection.
•LMM server settings, including the base url of the deployed LMM application.
•Delivery Server settings, including the base url of the deployed DS application.
•Administrator settings
•Course content management and deployments settings.
3.Generates database scripts using the information supplied by the user, and depending upon the components selected, creates the following directory structure in the selected target directory:
•bin:
•discussion: JAR file to be installed on Domino discussion database server
•distribute: Offline Learning Client installer, Authoring Tool installer, content tracking frameset files; files are moved to the appropriate location by the administrator
•java: IBM JDK used by the utilities in bin
•lib: JAR files used by the utilities in bin
•license: license text files in various languages
•portlet: 3 sample LMS portlets
•prt: product registration files
•scripts: database scripts used to populate the LMS databases
•update: LMS Updater (more information below)
•
The LMS Installer includes an LMS Updater component, which allows users to change settings that were specified during the initial install. The Updater presents the same UI as the Installer, with all the properties (except for passwords) entered on install. The user makes the desired changes, and the Updater generates a set of update database scripts that must be run to apply the changes to the LMM and DS application databases.
