IBM G210-1784-00 User Manual

Lotus

Learning Management System R1

Version 1.0.4 

March 2004

Installation Guide

G210-1784-00

Copyrights

Disclaimer

THIS DOCUMENTATION IS PROVIDED FOR REFERENCE PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS DOCUMENTATION, THIS DOCUMENTATION IS PROVIDED "AS IS" WITHOUT ANY WARRANTY WHATSOEVER AND TO THE MAXIMUM EXTENT PERMITTED, IBM DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SAME. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION, DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES, ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION. NOTWITHSTANDING ANYTHING TO THE CONTRARY, NOTHING CONTAINED IN THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF THIS SOFTWARE.

Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written consent of IBM, except in the manner described in the documentation or the applicable licensing agreement governing the use of the software.

Lotus Software IBM Software Group One Rogers Street Cambridge, MA 02142

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GS ADP Schedule Contract with IBM Corp.

List of Trademarks

Lotus Discovery Server, LearningSpace Forum, IBM Directory Server, AIX, Cloudscape, Notes, xSeries, and Domino are trademarks of Lotus Development Corporation and/or IBM Corporation in the United States, other countries, or both. IBM, Lotus, DB2, Lotus Notes, LearningSpace, RS/6000, Sametime, and WebSphere are registered trademarks of Lotus Development Corporation and/or IBM Corporation in the United States, other countries, or both.

Crystal Reports is a registered trademark of Crystal Decisions Corporation in the United States, other countries, or both.

Java, JavaServer Pages, JavaBeans, JavaScript, J2EE, JDBC, Sun Enterprise, and Sun Solaris are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

JReport and JReport Designer are trademarks of Jinfonet Software, Inc. in the United States, other countries, or both.

Macromedia and Dreamweaver are registered trademarks of Macromedia, Inc. in the United States, other countries, or both.

Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the United States and other countries.

Oracle is a registered trademark of Oracle Corporation in the United States, other countries, or both.

PKZIP is a registered trademark of PKWARE, Inc. in the United States, other countries, or both.

SmartForce is a trademark of SkillSoft Corporation in the United States, other countries, or both.

SQL Server and Internet Explorer are trademarks of Microsoft Corporation in the United States, other countries, or both. Windows, Windows NT, and Outlook are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product, company, and service names mentioned herein may be the trademarks, registered trademarks, or service marks of their respective owners.

Contents

Chapter 1 About the IBM Lotus Learning Management System............................................................1

Introduction ...............................................................................................................................................................................1

What is the Learning Management System? ......................................................................................................................... 1

Understanding the Learning Management System Architecture....................................................................................... 1

Chapter 2 Learning Management System Requirements ....................................................................... 3

Database server requirements................................................................................................................................................. 3

Learning Management System server requirements ...........................................................................................................3

Learning Management System client requirements............................................................................................................. 3

Chapter 3 Learning Management System Installation Overview ........................................................... 5

Packaging overview.................................................................................................................................................................. 5

Some words about the Learning Management System settings & configuration information...................................... 5

An outline of the installation process.....................................................................................................................................6

Chapter 4 Identifying Learning Management System Hardware Assets.............................................11

Allocating server responsibilities.......................................................................................................................................... 11

Creating a new database or upgrading an existing database ........................................................................................... 11

Learning Management System Hardware requirements ..................................................................................................12

Chapter 5 Installing the WebSphere Core..............................................................................................13

Enabling SSO in WebSphere.................................................................................................................................................. 14

Chapter 6 Installing or Identifying the LDAP Directory.........................................................................17

Installing the IBM Directory Server LDAP Directory: an example.................................................................................. 17

Chapter 7 Installing the Learning Management System Server Application Files.............................21

Installer program information............................................................................................................................................... 21

Installing the Learning Management System Server application software ....................................................................22

Chapter 8 Installing the Delivery Server (DS) Application Files...........................................................29

Installer program information............................................................................................................................................... 29

Installing the Delivery Server application software...........................................................................................................30

Chapter 9 Installing and Configuring Database Servers and Schema ................................................37

Database Creation Overview.................................................................................................................................................37

Table of Contents iii

DB2 database creation and configuration for the Learning Management System: an example...................................38

Oracle database creation for the Learning Management System .....................................................................................44

MS SQL Server database creation for the Learning Management System......................................................................45

Additional information about running scripts in different environments......................................................................46

Chapter 10 Installing the Network Deployment (ND) Module...............................................................49

Chapter 11 Configuring JDBC Data Sources.........................................................................................53

Data source overview ............................................................................................................................................................. 53

Defining the JDBC provider ..................................................................................................................................................54

Chapter 12 Configuring Environment Entries........................................................................................63

Configuring an environment entry for the log file location.............................................................................................. 63

Chapter 13 Configuring WebSphere Application Server Security.......................................................71

Configure the LDAP directory for use with the Learning Management System........................................................... 72

Chapter 14 Deploying the Learning Management System Server Application...................................75

Chapter 15 Deploying the Delivery Server (DS) Application ................................................................85

Starting the application and regenerating web server plug-in......................................................................................... 85

Chapter 16 Deploying the Learning Management System and DS Components onto Separate WAS Application Servers

..................................................................................................................................87

Chapter 17 Starting the Applications......................................................................................................89

Starting the Learning Management System Server application ...................................................................................89

Starting the Delivery Server application.......................................................................................................................... 89

Regenerating the web server plug-in ...............................................................................................................................90

Running the Updater..........................................................................................................................................................90

Chapter 18 Post-Installation Tasks.........................................................................................................92

Configuring on-line help........................................................................................................................................................ 92

Adding the Delivery Server to the Learning Management System application............................................................. 92

Deploying the Offline Learning Client.................................................................................................................................93

Installing the Authoring Tool................................................................................................................................................ 93

Installing the Command Line Import Utility (CLIMP)...................................................................................................... 93

Migrating LearningSpace data..............................................................................................................................................94

Installing XVFB on UNIX platforms to enable reporting ..................................................................................................94

iv IBM Lotus LMS Release 1 Installation Guide

Determining the correct SSO settings for the Learning Management System................................................................ 96

Chapter 19 Special Installation Issues ...................................................................................................99

Using SSL with the Learning Management System........................................................................................................... 99

Using the Directory Server Web Administration Interface with Linux...........................................................................99

Chapter 20 Removing the IBM Lotus Learning Management System...............................................101

Uninstalling the Learning Management System Server and Delivery Server applications........................................ 101

Removing the installed Learning Management System files .......................................................................................... 101

Removing the Learning, DS, and Audit databases...........................................................................................................101

Appendix A LMS Performance and Fine-tuning Information..............................................................103

Moving static LMS elements to the Web Server ............................................................................................................... 103

Tuning LDAP performance .................................................................................................................................................105

Tuning database server performance.................................................................................................................................106

Tuning TCP/IP settings on LMS servers........................................................................................................................... 107

Tuning HTTP servers............................................................................................................................................................109

Tuning performance using the WebSphere Application Server Administrative Console.......................................... 114

Tuning the LMS applications ..............................................................................................................................................118

Index ........................................................................................................................................................122

Table of Contents v

vi IBM Lotus LMS Release 1 Installation Guide

Chapter 1 About the IBM Lotus Learning Management System

Introduction

This document provides information on the IBM® Lotus® Learning Management System installation process as well as information on packaging and layout. The intended audience for this document is system administrators, developers, and other users who wish to install the Learning Management System.

What is the Learning Management System?

The IBM Lotus Learning Management System is a scalable, flexible platform for managing both classroom-based and e-learning activities, resources, curriculums, and courseware catalogs across the enterprise. The product is an end-to-end fully integrated learning solution that is comprised of the following modules: Learning Management System Server, Authoring Tool, Delivery Server, and an Offline Learning Client to support disconnected use. Learning Management System organizes and delivers courses, tracks and reports on student activities, and reserves instructors and resources, enabling customers to manage their entire training program from a single platform.

Using a web browser, students can review the online course catalog to enroll in both instructor-led classroom training and e-learning offerings, then receive confirmations and/or notifications of schedule changes. Training managers are able to reserve resources to avoid scheduling conflicts, develop curriculums for various audiences, and provide managers with reports on their employees' training activities. The Learning Management System product streamlines the overall management of an organization's training activities, increasing efficiencies and saving time and expenses.

With the product's support for industry standards, organizations can offer a wide variety of courseware developed with third party products such as Macromedia® Dreamweaver™, or they can develop their own courses in house with the Learning Management System authoring tool. Subject matter experts can create courses on their own, with no programming skills required.

Understanding the Learning Management System Architecture

Learning Management System components

Learning Management System framework can include some or all of the following components:

• Learning Management Server

• Delivery Server

• WebSphere® Application Server

• Relational database management system

• Authoring tools

• Domino™ servers

• LDAP

• IBM® Lotus® Virtual Classroom (LVC)

Chapter 1: About IBM Lotus Learning Management System 1

Relational database management system

The Learning Management System stores user, course, and assessment data in a relational database, which consists of a series of tables. The database management software can reside on the same machine as the Learning Management System software for a small installation, but generally resides on a separate machine for data security and performance reasons. A Learning Management System specific database is created with the database management system and then customized during the Learning Management System installation. This database interacts with the Learning Management System Server. When users run the Learning Management System, the Learning Management System Server initiates database transactions to retrieve and update information about course structure, user permissions, and assessment questions. For more information on the Learning Management System and its many components, refer to the rest of the documentation shipped with this product.

2 IBM Lotus LMS Release 1 Installation Guide

Chapter 2 Learning Management System Requirements

The Learning Management System is supported on a specific set of hardware and software components. Whether you are installing the Learning Management System for the first time on a server or upgrading from an earlier release of LearningSpace®, you may need to upgrade hardware and/or software before the Learning Management System can function on that machine.

Using the Learning Management System with unsupported hardware or software may result in data loss, as well as problems accessing the system. Before installing the Learning Management System, verify that you have installed the required hardware and software described in this chapter.

Database server requirements

You’ll need a relational database management system with the Learning Management System. When you install the Learning Management System, you’ll create a database specifically for use with the Learning Management System. Refer to the README.TXT file and the Release Notes shipped with this product for more information on supported databases and additional requirements.

Learning Management System server requirements

Learning Management System servers need the hardware and software specified below in order to properly support the product.

Hardware requirements

For the most up-to-date server hardware requirements, refer to the README.TXT file and the Release Notes shipped with this product.

Software requirements

For the most up-to-date server software requirements, refer to the README.TXT file and the Release Notes shipped with this product.

Time zone settings

Remember the following guidelines regarding time zone settings. All user-viewable time zone settings are stored as GMT/UTC.

• Make sure that you have set WAS server time zone settings set correctly

• Collaboration servers may use different time zones

• During Live sessions, clients will see their own time zones reflected in date/time stamps.

Learning Management System client requirements

Learning Management System client machines’ hardware and software is described below.

Chapter 2: LMS System Requirements 3

Client hardware requirements

For the most up-to-date client hardware requirements, refer to the README.TXT file and the Release Notes shipped with this product.

Client software requirements

For the most up-to-date client software requirements, refer to the README.TXT file and the Release Notes shipped with this product.

Audio and video requirements

For the most up-to-date client audio and video requirements, refer to the README.TXT file and the Release Notes shipped with this product.

Packaging and layout of the Learning Management System software components

For more information on the packaging and layout of the Learning Management System software components, refer to the README.TXT and Release Notes shipped with this product.

4 IBM Lotus LMS Release 1 Installation Guide

Chapter 3 Learning Management System Installation Overview

The following information provides an outline of the Learning Management System installation process.

Packaging overview

The functional components of the Learning Management System product are J2EE™ web applications. J2EE provides the packaging for these components as a standard.

The important units of the Learning Management System packaging as J2EE applications are

• .war (web application archive) files

• .ear (enterprise application archive) files

Both of these package types are zip-format archives containing standardized metadata. These files are identified by the .war and .ear filename extensions, respectively.

Of these two, the .war file is the lower level entity. An .ear file may contain multiple .wars, each with its own URL context and the needed information to resolve bindings implied by the .war file. An important binding involves security. A .war file may refer to a security-role that it uses, but the .ear file has the information to bind that role to a specific subject or user group.

The Learning Management System packages its two functional servers as separate .ear files. .Ear files can contain resource references and environment entries. These are items that the application has identified as required services or settings. An example resource reference would be a reference to a JDBC™ connection, which the Learning Management System uses to access the relational database.

When an .ear file that contains resource references or environment entries is deployed on a J2EE application server (for example, a WAS server), the application server generally presents a means where you can resolve those references or environment values. With a WAS server this is done via the Administration Console user interface. By representing the Learning Management System setup requirements as either resource references or environment entries, you can the use the WebSphere Application Server deployment process to gather the needed install-time settings.

Some words about the Learning Management System settings & configuration information

Most Learning Management System settings are stored in either of two places:

• XML-format text files located in the web-application WEB-INF/classes directory. The relevant file for the

Learning Management System Server is named settings.xml, and the corresponding file for the Delivery Server is named ds-settings.xml. When the servers first start, they read settings from these files.

• The Learning Management System application database. After the servers read settings from the XML files,

they read additional settings from the database. When a setting is specified in both the database and the XML files, the one in the database overrides the setting specified in the XML file.

When you specify application settings using the Learning Management System Installer or, subsequently, the Learning Management System user interface, those settings are stored in the application database. You can change settings that you specified with the Learning Management System Installer by using the Learning Management System Updater, a utility that resides in the /update directory. The Updater presents you with the necessary screens, pre-populated with your original settings data. After you have made the necessary settings changes, the

Chapter 3: LMS Installation Overview 5

Updater then creates two update SQL scripts - one for the Learning Management System server (updateLMM.sql) and one for the Delivery Server (updateDS.sql). These scripts are then run to change the respective databases.

You can change settings through the user interface at any time. Since virtually all required application settings can be specified through the Installer or the user interface, it is unlikely that you would ever need to modify the XML files.

Finally, some Learning Management System application settings come from the WebSphere application server itself. The Learning Management System application is packaged containing references to Objects that are retrieved from the application server environment at runtime. For example, the Learning Management System uses JDBC datasources it retrieves from the environment via JNDI. By changing the definition of the datasource in the WebSphere console, you can change the database that the Learning Management System connects to without modifying the Learning Management System directly.

An outline of the installation process

The following steps outline the Learning Management System installation/deployment process. They should be followed in this order to avoid version skew among the various components to be installed:

1. Identify hardware assets

The Learning Management System can be installed on various types and configurations of servers. The expected capacity of the installation is the key factor in determining the requirements for servers. The install process described in this document assumes that the desired server or servers have been identified and configured such that required products can be installed.

For more information, refer to “Chapter 4 Identifying Learning Management System Hardware Assets.” Refer also to your WebSphere documentation for guidelines on the various server configuration options that are available for your Learning Management System deployment.

2. Install the database server software

The Learning Management System runs against the following back-end relational databases:

• DB2®

• Oracle®

• SQL Server™

You must install one or another of these before you install the Learning Management System software.

3. Install WebSphere core

You are required to have the WAS (WebSphere Application Server) Core installed on the desired systems. This can be a single server or multiple servers. If multiple servers are used, you must also install the Network Deployment module. The WebSphere Core installation is accomplished by using the GUI installer that is standard with WAS.

For more information, refer to “Chapter 5 Installing the WebSphere Core.”

4. Install or identify the LDAP Directory

The Learning Management System requires an LDAP directory for product operation. Either an IBM Directory Server™ 4.1 directory is installed or configured, or a pre-existing LDAP directory must be identified. Also, at least two user names that are recorded in the directory must be identified. These are for

6 IBM Lotus LMS Release 1 Installation Guide

the WebSphere and the Learning Management System administrator (who may be one and the same person).

The organization of the LDAP directory is a key factor in operating the Learning Management System. Many aspects of the Learning Management System operation require that directory path expressions be specified. An example is rostering. While users can be rostered in the application manually, large deployments will either employ the "roster from file" capability, where a directory LDIF file is imported into the system, or will employ "auto rostering" where a directory path or group indicating users who should be given access is specified.

For more information, refer to “Chapter 6 Installing or identifying the LDAP Directory.”

5. Run the Learning Management System Installer to install the necessary Learning Management Server and Delivery Server files

The Learning Management System Installer installs all of the files necessary for the eventual deployment of the Learning Management System and Delivery Servers. The Installer also gives you the option to install additional Learning Management System-related utilities and tools. The final deployment of each application is then carried out via the application server Admin console (explained later in this section).

For more information, refer to “Chapter 7 Installing the Learning Management Server application files” and “Chapter 8 Installing the Delivery Server application files.”

6. Install and/or configure logical database servers and schema

The Learning Management System requires a number of different logical databases to function. They are the Learning, Audit, and Delivery databases. The needed database server software must be installed on the desired systems. Vendor-supplied database utilities are then used to run SQL scripts supplied with the Learning Management System product. These SQL scripts create and initialize the needed databases for the Learning Management System to operate.

The scripts are named for their logical database and database platform. For example, the script to create the Audit database on IBM’s DB2 is audit_db2.sql while lmm_oracle.sql creates the Learning Management System database on an Oracle system. To create and initialize the three databases, keeping them logically separated, perform the following steps:

• If you are running Oracle, obtain three separate accounts for your DB system: one each for Audit,

Learning, and Delivery databases. If you are running SQL Server or DB2, you will create three separate databases rather than a single partitioned database.

• Do the following using your database vendor’s tools:

o Log in using your Audit database account. o Execute the supplied Audit SQL script for your database platform. o Log in using your Learning Management System database account. o Execute the supplied Learning Management System SQL script for your database platform. o Log in using your Delivery account. o Execute the supplied Delivery Server SQL script for your database platform.

Be sure to follow the database software guidelines for sizing the installation and configuring an efficient physical architecture for the database. You may need to take extra action, for example, to create separate tablespaces. You may also need to edit the database scripts before execution.

Chapter 3: LMS Installation Overview 7

At this time you should also identify the LDAP username for the Learning Management System administrator. This value is used to make an entry in the USER table and represents the only rostered user when the application starts.

For more information, refer to “Chapter 9 Installing and configuring database servers and schema”.

7. Install the Network Deployment module (optional)

The Network Deployment (ND) module configures and controls multi-server WAS installations. If you intend to deploy the Learning Management System on more than one application server, then ND must be installed to manage the cluster, which you can then do from a single machine. The ND module can be installed on a node where WAS Core has been installed.

For more information, refer to “Chapter 10 Installing the Network Deployment (ND) Module.”

8. Configure JDBC data sources

Access to JDBC connections is made via JNDI lookup of a named data source. These data sources have wellknown names that are embedded in the Learning Management System .ear file. Using the WAS admin console, you must configure three data sources. For example, the default data sources are Learning, Audit, and Delivery.

For more information, refer to “Chapter 11 Configuring JDBC Data Sources.”

9. Configure environment entries

The Learning Management System uses J2EE environment entries to obtain some needed settings. Similarly to the JDBC data sources, these have well-known names that are embedded in the Learning Management System application. The needed environment entries must be created and their values specified with the Was Admin console.

For more information, refer to “Chapter 12 Configuring Environment Entries.”

10. Configure WebSphere Application Server security

Learning Management System relies on WAS LDAP authentication. The WAS admin console must be used to configure LDAP as the active user registry. To perform this, an LDAP username must be selected as the WAS administrator; also bind credentials to the LDAP directory must be specified. This information was obtained in step 2 and is now used as input into the WAS configuration .

For more information, refer to “Chapter 13 Configuring WebSphere Application Server Security.”

11. Deploy the Learning Management Server application

After the application files have been installed with the Learning Management System Installer, you must then deploy the application via the Application Server Admin console. The Learning Management System product package includes separate application .ear files for the Learning Management System Server and the Delivery Server. The Learning Management System Server should be deployed first.

Using the Admin console, the .ear file is read and validated. A series of "wizard" pages is then presented to let you finalize the application settings. The main activity here is the binding of the references included in the .ear file to the specific JDBC data-sources and environment entries created in the earlier steps of this outline.

8 IBM Lotus LMS Release 1 Installation Guide

For more information, refer to “Chapter 14 Deploying the Learning Management Server application “ and “Chapter 16 Deploying the Learning Management System and DS components onto separate WAS App Servers.”

12. Deploy the Learning Management System Delivery Server (DS) application

The Learning Management System Delivery Server (DS) also has its own .ear file. The DS .ear file must be also be deployed and all bindings resolved just as for the Learning Management System Server.

For more information, refer to “Chapter 15 Deploying the Delivery Server (DS) application.” and “Chapter 16 Deploying the Learning Management System and DS components onto separate WAS Application Servers.”

13. Start the applications

At this point, the Learning Management System applications are ready to start. Again, the WAS Admin console is used to start the applications. Both the WAS logs and the Learning Management System logs should be examined to verify correct initialization. At this point, the applications can be accessed via browser. The administrator (identified in installation), must login to the Learning Management System application and roster users, provide for importing content, and perform the tasks needed for actual learning to be delivered to users.

For more information, refer to “Chapter 17 Starting the Applications.”

14. Complete post-installation tasks

Refer to “Chapter 18 Post-Installation Tasks” and “Chapter 19 Special Installation Issues” for more information on any additional tasks that may be needed to run the Learning Management System more successfully. These tasks include the following:

• Configuring on-line help

• Adding the Delivery Server to the Learning Management System application

• Deploying the Offline Learning Client

• Installing the Learning Management System Authoring Tool

• Installing the Command Line Import Utility

• Migrating LearningSpace data

• Installing XVFB on UNIX platforms to enable reporting

• Determining the correct SSO settings for the Learning Management System

To complete these tasks, make sure that you have logged into the Learning Management System as the Administrator. Refer to the Administrator’s Guide for more information.

Finally, should you need to remove the Learning Management System, the procedure for doing so is described in “Chapter 20 Removing the IBM Lotus Learning Management System.”

Chapter 3: LMS Installation Overview 9

10 IBM Lotus LMS Release 1 Installation Guide

Chapter 4 Identifying Learning Management System Hardware Assets

The following are some guidelines for making the best of your hardware configuration.

Allocating server responsibilities

Installation of the Learning Management System server software includes three server components: the database server, the Learning Management Server, and the Delivery Server (DS). These server components can be installed on a single machine for evaluation purposes, but in a production environment you should use a different machine for each component. This guide assumes you have already installed DB2, Oracle, or SQL Server on the database server.

Installing and setting up the content server is not part of the Learning Management System installation. Consult the documentation in your HTML authoring system for instructions about installation.

If you are upgrading from an earlier releases of LearningSpace, see the Migration Guide for instructions.

Refer to your WebSphere Application Server documentation for information on the various server configuration options available for your Learning Management System deployment as well as for server and application deployment guidelines.

Creating a new database or upgrading an existing database

If you are installing the Learning Management System for the first time, you’ll need to create a new database to use with it. You can create the new database before installation (which allows you to set up the data source ahead of time), or you can use the help of the Learning Management System scripts to create it for you (requiring you to create or select a data source as you proceed). The instructions in this guide direct you to create the database before installing the Learning Management System, so you can verify that the database and the corresponding data source are configured correctly before you attempt to use them. Refer to the chapter “Installing and configuring database servers and schema” for more information on this subject.

If you are upgrading from LearningSpace 4.11 or 5.01, you already have a database, which must be upgraded to reflect the structure used in the Learning Management System. Perform the database upgrade during installation or after. In all cases you need to install the Learning Management System complete with the databases. The migration procedures will then connect to the source (LearningSpace 4 or 5) database to unload the data and load it into the Learning Management System database.

For additional information on information migration, refer to the “Information Migration” chapter or the Learning Management System Migration Guide. For more information on databases, refer to the chapter “Installing and configuring database servers and schema.”

Chapter 4: Identifying LMS Hardware Assets 11

Learning Management System Hardware requirements

For the most up-to-date hardware requirements, refer to the README.TXT file and the Release Notes shipped with this product.

12 IBM Lotus LMS Release 1 Installation Guide

Chapter 5 Installing the WebSphere Core

To successfully run the Learning Management System, you are required to have the WAS (WebSphere Application Server) Core installed on the desired systems. This can be a single server or multiple servers. The following instructions explain how to install this component.

Note: For more complete information on installing WAS, refer also to http://www-

3.ibm.com/software/webservers/appserv/library/index.html.

If multiple servers are used, you must install the Network Deployment module. Refer to “Chapter 10 Installing the ND Module” for more information.

The following instructions explain how to install the WebSphere Core:

• For remote UNIX users only, set up X session for a remote install from a local Linux machine as follows:

1. Open a terminal window on your local machine.

2. Type # ifconfig Note your IP address;

3. Type # xhost remote_hostname + (where remote_hostname is the name of the host to which

you will connect in order to install WAS).

4. Login to the remote machine as the root user.

5. Configure the remote machine to use your local machine as its graphical display. For a remote AIX

host, type the following:

# DISPLAY=x.x.x.x:0 xhost (where x.x.x.x = the IP address of your

For a remote Sun Solaris™ host, type the following:

# DISPLAY=x.x.x.x:0 (where x.x.x.x = the IP address of your # EXPORT DISPLAY

• If necessary, unzip the WAS5 installer into a temporary directory (unzip must be installed on the AIX and

Sun Solaris machines for this purpose).

• Launch the installer by executing LaunchPad.sh (for UNIX hosts) or install.bat (for Windows).

Note: Before running .sh files in a UNIX environment, make sure that the “execute” permission is set.

• Follow the prompts of the install display, accepting its defaults with the following exceptions:

1. Choose “Custom Install.”

2. Deselect “Embedded Messaging” because the Learning Management System does not use Java

Messaging Service (JMS).

3. For Windows users, drop “\Program Files” from the install path of both the WebSphere Application

Server and IBM HTTP Server products. You may not need to install the HTTP server, for example if you have previously installed IBM Directory Server 4.1 on the same machine.

Important Note for AIX and Linux users: The WebSphere Application Server installation contains the IBM HTTP Server. AIX and Linux can also include an HTTP server. This server should be removed or reconfigured before the installation of the WAS and HTTP server to avoid port conflicts.

local machine)

4. Make sure that the Node Name (first field) for your machine is not a qualified DNS name, but that

there is an IP address or fully-qualified Host Name in the second field.

Chapter 5: Installing the WebSphere Core 13

5. For Windows users, choose to run both WebSphere Application Server and IBM HTTP Server as

services.

6. Do not register the product.

7. Once the installer completes, the First Steps window will open. Select “Verify Installation” to launch

the Installation Verification Tool (IVT). Its output will be written to the terminal (or command) window “behind” the First Steps GUI.

8. Verify that IBM HTTP Server has set the server’s name correctly in its configuration file. Open the file

$HTTP_SERVER_ROOT/conf/httpd.conf and search for the ServerName directive. Be sure it is set to the desired host name of your WAS server.

9. Be sure to review the WebSphere release notes (especially platform-specific notes).

To start and stop WAS, use the startServer and stopServer scripts and/or (on Windows) Start Menu shortcuts. Once WAS Global Security has been enabled, you must provide a username and password to the stopServer script and shortcut.

On UNIX systems, use the following to start and stop WAS where $SERVERNAME is the name of the WAS Application Server to start or stop and $USERNAME and $PASSWORD are defined in the configuration of the Active User Registry for which WAS Global Security is enabled:

/$WAS_ROOT/bin/startServer.sh $SERVERNAME /$WAS_ROOT/bin/stopServer.sh $SERVERNAME /$WAS_ROOT/bin/stopServer.sh $SERVERNAME –username $USERNAME –password $PASSWORD

On a Windows system, use the following:

\$WAS_ROOT\bin\startServer.bat $SERVERNAME \$WAS_ROOT\bin\stopServer.bat $SERVERNAME \$WAS_ROOT\bin\stopServer.bat $SERVERNAME –username $USERNAME –password $PASSWORD

For Windows systems you must also modify the properties of the Start Menu shortcut (Start -Programs -IBM WebSphere -Application Server -Stop the Server) to append -username $USERNAME –password $PASSWORD in the Target field.

Enabling SSO in WebSphere

Single Sign-On (SSO), also known as single logon, is the process which permits users to move between different Web applications or different parts of the same Web application hosted by the same or different physical machines, without being prompted for a user name and password (or certificate) every time.

For example, if SSO is not used, you will have to log in to the Delivery Server every time you launch a course from the LMM server. As such, SSO considerations should be carefully considered in your Learning Management System deployment planning to allow for the greatest efficiency in logging in users.

Use the following procedure to set up SSO for your configuration.

1. Start your browser and log into your WAS Administration Console: http://hostname:9090/admin. At

this point security is not enabled.

2. You will notice new features here. Under System administration, you will have Node Agents and Nodes. The

Node Agent is the physical machine. You can stop or restart the node here but to start the node you have to do it from the command line. On the Nodes panel it is very important that the Node is synchronized, this can take a few minutes to synchronize.

3. Enable SSO by doing the following:

14 IBM Lotus LMS Release 1 Installation Guide

• Expand the Security panel on the left side.

• Expand Authentication Mechanisms.

• Click LTPA.

• Enter the password for LTPA (for example, wasadmin)

• Click Save.

• On the LTPA panel, click Single Sign On at the bottom of the panel.

• Check that SSO is enabled.

• Enter the domain name (for example, acme.com).

4. Enable Security (for more information, refer to the “Enable WAS Global Security” section of Chapter 13

Configuring WebSphere Application Server Security).

5. Stop the servers. Stop the nodes first then stop the manager.

• For Unix use: WebSphere/AppServer/bin/stopNode.sh

• For Windows 2000 use: WebSphere\AppServer\bin\stopNode

• For Unix use: WebSphere/DeploymentManager /bin/stopManager.sh

• For Windows use: Websphere\DeploymentManager\bin\stopmanager

6. Start the servers by first starting the manager then starting the nodes.

7. Once security is enabled, you will have to provide the proper credentials when stopping the node or the

manager.

8. If you need to disable security, do it in security.xml located in

DeploymentManager/config/cells/hostNetwork.

9. Regenerate the HTTP plug-in. The plugin config is written to

DeploymentManager\config\cells\plugin-cfg.xml. You need to copy file to AppServer\config\cells.

10. Edit the file and change the references from DeploymentManager to AppServer.

11. Restart the Apache server.

For further information on the Learning Management System and SSO refer to Chapter 5 Managing Users in the IBM Lotus Learning Management System Release 1 Administrator's Guide.

Chapter 5: Installing the WebSphere Core 15

16 IBM Lotus LMS Release 1 Installation Guide

Chapter 6 Installing or Identifying the LDAP Directory

The Learning Management System requires an LDAP directory for product operation.

Either an IBM Directory Server 4.1 directory is installed or configured, or a pre-existing LDAP directory is identified. Also, at least two user-names that are recorded in the directory must be identified. These are for the WebSphere and the Learning Management System administrator.

Note: There are no naming conventions for these administrator names. Any valid user name will do for either.

The organization of the LDAP directory is a key factor in operating the Learning Management System. Many aspects of the Learning Management System operation require that directory path expressions be specified. An example is rostering; while users can be rostered in the application manually, large deployments will either employ the "roster from file" capability, where a directory LDIF file is imported into the system, or will employ "auto rostering" where a directory path or group indicating users who should be given access is specified.

Note: Some of the IBM components necessary for secure identity management (for example, IBM Directory Server) are not shipped with this product. Refer to the necessary components.

Installing the IBM Directory Server LDAP Directory: an example

www.ibm.com/software/directory for more information on obtaining

The following information provides instructions for installing the IBM Directory Server 4.1 on a Windows 2000 server. Before you begin, you must make sure that a web server (IBM HTTP Server, Apache, or IIS) is installed on your machine. It is needed to access the IBM Directory Server web-based administrative interface.

To begin, make sure you are logged on as a user with administrative privileges prior to starting the installer. Run the setup.exe program in the directory containing the program files and perform the following steps.

Installation Steps

1. At the ‘Select a language’ window select English (default) then click OK.

2. At the ‘Welcome to the InstallShield Wizard for IBM Directory Server 4.1’ click Next to continue.

3. At the ‘Software License Agreement’ window ensure that “I accept the terms in the license agreement” is

selected and then click Next.

4. Click Next at the informational window indicating what Web Servers are installed.

5. Click Next to install the IBM Directory Server 4.1 in the default location.

6. In the ‘Select the language for IBM Directory’ window, select English and then click Next.

7. In the ‘Choose the setup type that best suits your needs’ window, select Custom and then click Next.

8. In the ‘Select the features to install’ window ensure that the following are selected:

• Client SDK 4.1

• *DMT 4.1 & Java™ 1.3

• Server 4.1

Chapter 6: Installing or Identifying the LDAP Directory 17

• DB2 V7.2 (if necessary)

• GSKit5

• IBM HTTP Server 1.3.19 (if necessary)

9. Click Next.

10. In the ‘Select the components to configure’ window, ensure that all three options are selected, and then click

Next.

11. If you elected to install the IBM HTTP server, enter a user id, password, and password confirmation.

12. In the ‘Enter a new LDAP Administrator distinguished name and password’ window enter the following:

• An Administrator distinguished name, for example, cn=root.

• An Administrator password

13. Tab and reenter the password.

14. Click Next.

15. If you elected to install DB2, at the ‘Enter the userid and password for the DB2 system window, enter a user

id, password and password confirmation, and then click Next.

16. At the next window, ensure that ‘Create a Universal DB2 database (UTF8)’ is selected and then click Next.

17. At the next window, choose a drive for the DB2 database files and then click Next.

18. The next window is informational only, so simply click Next.

19. Click OK in the DB2 installation window. The installation of all selected software will take several minutes.

Do not interrupt the process.

20. Click OK at the ‘GSKit Installation’ window.

21. The ‘Please read the information below’ window is informational only, select Next to continue.

22. The next ‘Please read the information below’ window is informational only, click Next to continue.

23. Click Next at the ‘Yes, restart my system window.’

24. Click Finish.

After the system reboots the ‘Starting IBM Directory Server Configuration’ begins. This operation takes a few minutes. Do not cancel.

When the machine reboots the ldapcfg.exe will automatically run and setup the DB2 database it uses as a repository.

Directory Configuration Steps

Administering the directory – do the following to administer the directory:

1. Start the Directory Server Administrative interface and do the following:

• Open a browser session.

• Type in the URL to invoke the administrative interface: http://machine/ldap where machine is the DNS

name of your machine.

2. Login to the administrative interface and type in the administrator name (defined during the install process)

and password and click Logon.

3. Add a suffix to the directory by doing the following:

• Choose Setting - Suffixes in the Directory Server pane.

• Enter a suffix (for example, o=yoursuffix) in the Suffix DN text box.

18 IBM Lotus LMS Release 1 Installation Guide

• Click Update. You should see your suffix appear in the list of suffixes known to the directory server.

Note: The Web administration interface for Directory Server is also not supported on Linux. Refer to the Special Installation Issues chapter in this guide for a workaround for this issue.

4. Restart the directory server by choosing Current state - Start/Stop from the Directory Server pane.

5. Click the Start button. Eventually you should see a message that the directory server is currently running.

6. Logoff from the administrative interface by doing the following:

• Choose Logoff from the Directory Server pane.

• Click Logoff. All options (except Introduction and Logon) should disappear from the Directory Server

pane.

• Close the browser session.

Populating the directory – do the following to administer the directory:

7. Start the Directory Management Tool: Start - Programs - IBM Directory Server - Directory Management Tool.

8. Logon as the directory administrator and do the following:

• Choose Server - Rebind on the ldap://hostname:389 tab.

• Click the Authenticated button on the Rebind pane.

• Enter the directory administrator's DN and password in the appropriate text boxes.

• Click OK. You'll probably see a warning that the suffix you created earlier doesn't contain any data.

9. Define the suffix by doing the following:

• Choose Directory tree - Browse tree from the ldap://hostname:389 tab.

• Click the Add button in the Browse tree pane. The Add an LDAP Entry screen appears.

• At the Add an LDAP Entry screen do the following:

o Choose Organization in the Entry type drop down. o Leave Parent DN blank. o Enter the DN of the suffix (e.g. o=yourentry) in the Entry RDN text box. o Click OK. The Add an LDAP Entry screen expands to include additional attributes. o Click Add. The entry should appear in the directory tree.

10. Exit the Directory Management Tool by clicking the Exit button in the lower left hand pane.

Chapter 6: Installing or Identifying the LDAP Directory 19

Creating WebSphere and Learning Management System Administrator Accounts

You need at least two accounts in the LDAP directory to complete the installation of the IBM Lotus Learning Management System: an account for the WebSphere administrator and an account for the Learning Management System administrator. To create these accounts, you can either import an LDIF file or create the entries by hand. For instructions on importing LDIF files in IBM Directory Server, please consult the Directory Server Online Help. To create these entries by hand:

1. Start the Directory Management Tool: Start - Programs - IBM Directory Server - Directory Management Tool.

Note that each time you start the Directory Management Tool, you need to include a binding and password that identifies the administrator of the directory. These are created when Directory Server is installed. The default binding created during installation is cn=root.

2. Choose Directory tree - Browse tree.

3. Select the entry in the tree under which you want to add the new entry, and then click Add. For example, to

add the user accounts at the organization level, select your organization identifier, such as o=ibm, and then click Add.

4. Select the User Entry type.

5. For Parent DN, enter the distinguished name of the tree entry you selected (for example, o=ibm) if this is

different from the entry selected in the tree—the Parent DN should automatically default to the entry selected in the tree.

6. Entry RDN – Enter the relative distinguished name (RDN) of the entry that you are adding (for example,

cn=wasadmin).

7. Click OK to continue and to open the ‘Add and LDAP User dialog:

8. In the ‘Add an LDAP User’ dialog, select inetOrgPerson for object class (which is the default object class for

new entries). The DN (distinguished name) should be populated automatically, as should the Common Name. It is not necessary to enter a value for sn for this account. You must enter a userPassword on the Business tab and a uid on the Other tab, and you may fill in any other details you wish.

9. Repeat these steps to create the lmsadmin account.

WebSphere Application Server and LDAP User filter strings

In WAS, you must specify an LDAP user filter that searches the registry for users. This option is typically used for Security Role to User assignments. It specifies the property by which to look up users in the directory service.

For example, in the syntax example (&(uid=%v)(|(objectclass=inetOrgPerson)(objectclass=ePerson))), users are looked up based on their user IDs and the fact that the person entries have either inetOrgPerson or ePerson (or both) set as their objectclass attribute. For more information about this syntax, see the LDAP Directory Service documentation.

To view this administrative page in the WAS Administration Console, click Security- User Registries- LDAPAdvanced LDAP settings.

Additional LDAP information and guidelines

When setting up a Domino LDAP directory with the Learning Management System, make sure that it has full text indexing enabled as this significantly shortens the time for user rostering by file.

20 IBM Lotus LMS Release 1 Installation Guide

Chapter 7 Installing the Learning Management System Server Application Files

Before deploying the complete Learning Management System, the Learning Management System Server files should first be installed on the Application Server.

Note: If you are installing and deploying the Learning Management System Server and the Delivery Server onto separate WAS servers, refer also to Chapter 16 Deploying the Learning Management System and DS Components onto Separate WAS Application Servers for further information.

The important unit of packaging in the Learning Management System application install/deployment process is the .ear (enterprise application archive) file. This package is a zip-format archive containing standardized metadata. These files are identified by the .ear filename extension.

Installer program information

The Learning Management System comes with an Installer that lays down all of the files necessary for the eventual deployment of the Learning and Delivery Servers. The Installer also gives you the option to install additional Learning Management System-related utilities and tools.

After the initial application files are installed with the Installer, the application .ear file can then be read and validated from the WAS Admin Console via a series of "wizard" pages. These pages let you finalize the application settings for deployment.

The Learning Management System Installer comes packaged in four platform-specific sets of files: ibmlms_nt.zip, ibmlms_aix.tar, ibmlms_linux.tar, and ibmlms_sun.tar.

The following table describes where the LAUNCHER and INSTALLER files are depending on the platform:

PLATFORM LAUNCHER INSTALLER

Windows 2000 and XP

AIX™

Linux

Sun

Note: Before running the .sh files in a UNIX environment, make sure that the “execute” permission is set.

To start the Installer you must invoke the launcher for the platform you are installing on. The launcher will start the

Installer using the platform specific JDK that is included on the disk.

Note: The actual .ear and .war files are archived within setup.jar. The Authoring Tool is not archived and is available to copy directly (if desired) from the install image. You need to use the Installer to install the utilities because, if you don’t, the JDK won’t be installed.

Install.bat Installer.exe

install.sh AIXInstaller.bin

install.sh LinuxInstaller.bin

install.sh SolarisInstaller.bin

The following steps explain the Learning Management System Server file install procedure using the Installer.

Chapter 7: Installing the LMS Server Application Files 21

Note: You can install the Learning Management System Server and Delivery Server application files at the same time, even if you plan to deploy the applications to different machines. Since some of the settings are used for both the Learning Management System Server and Delivery Server (LDAP settings, for example), installing both applications together allows you to specify those settings only once.

Installing the Learning Management System Server application software

1. Start the Installer.

2. At the Language Selection Installer screen, select the language to be used by the Installer from the drop down

list.

3. Click OK to continue.

4. At the Welcome screen, click Next.

5. Read the license agreement and click Accept if you agree to its terms. Translated versions of the IBM and

Learning Management System license agreements are installed in the Learning Management System license subdirectory. Use any text viewer to read or print them in English or in the language configured on your machine.

Select the Learning Management System features to install

6. At the Features Screen, select the Learning Management System Server. The information you enter in the

screens that follow is collected and written to a settings_init.sql file under the lmm directory of the destination folder.

7. Select the Authoring Tool and/or Utilities if so desired. The Authoring Tool zip file is copied to the authoring

tool directory of the destination folder. All utilities are copied to the utilities directory of the destination folder.

8. Click Next to continue. You will now be shown the LDAP Settings screen.

Select the correct LDAP settings and test the LDAP connection

9. Enter the following LDAP Settings for your Learning Management System configuration:

• Provider URL – Enter the URL of the LDAP provider. An example setting would be:

ldap://myserver.acme.com:389

• Base Distinguished Name – Enter the Base Distinguished Name of the LDAP provider, indicating the

starting point for directory searches. An example setting would be: o=ibm (or, if the directory configuration includes the country, o=ibm,c=us). Learning Management System logins will not work if you do not include the country code in the Installer when the LDAP country attribute is used in directory entries.

• LDAP User ID – Enter the Distinguished Name (DN) of a user the Learning Management System Server

can use to authenticate to the LDAP provider. This user must have at least read access to the portion of directory starting at the Base Distinguished Name. You may specify the Directory Server administrator (for example, cn=root) or another LDAP user.

22 IBM Lotus LMS Release 1 Installation Guide

Note: The text on the LDAP Settings screen is incorrect; instead of "LDAP User ID" it should read "LDAP User Distinguished Name (DN)."

• LDAP Password – Enter the password used for accessing and further authenticating you to the LDAP

provider.

• LDAP Provider – Select the LDAP provider that you use from the drop down list of supported

providers.

10. After you have entered all of the LDAP settings, validate them to make sure they are correct.

11. To test these settings, click on the Test LDAP Connection button. If you have entered valid settings you will

receive a message box stating that you have a successful connection otherwise you will be informed that you connection has failed.

12. Click Next to continue.

Select the Learning Management System Server settings

13. Enter the following Learning Management System Server Settings for your Learning Management System

configuration:

• Base URL – Enter the base URL for accessing the Learning Management System Server. An example

setting would be:

• Description – this is an optional text field to provide additional information about the Learning

Management System Server.

• User Name and Password– Enter a user name and password for the Learning Management System

Server. These will be used for authenticating the Learning Management System Server when it

http://lms.acme.com/lms-lmm

Chapter 7: Installing the LMS Server Application Files 23

+ 101 hidden pages