IBM Lotus Learning Management System R1.0.1 ReadMe

Copyright and Licensing Information

ReadMe contents

This document contains information you need to install IBM® Lotus® Learning Management System Release 1.0.1. The information in this document is divided into the following sections:

For information on known issues for this release, see the Release Notes (ReleaseNotes.html).

Finding the most recent LMS documentation

Updates to the LMS ReadMe, Release Notes, LMS guides, and other related LMS documentation will be available periodically. To obtain the updated documentation, point your browser at: http://www-1.ibm.com/support/search/index.html and search on "Learning Management System Migration Utility and Quarterly Documentation Updates." This will bring up the documents that contain the information about the latest documentation updates, and where to obtain them.

Upgrading from LMS R1.0a

If you are upgrading to the LMS Release 1.0.1 from Release 1.0a, follow this procedure:

  1. On the LMS Server, copy the packages directory to a back-up location, so you don't lose it during the upgrade.

  2. Uninstall LMS Release 1.0a, as described in the Release 1 Installation Guide.

  3. Review the R1.0.1 system requirements in this document and make sure your systems meet these requirements.

  4. Install the LMS R1.0.1 as described in the R1.0.1 Installation Guide.

  5. Move the packages directory (which you backed up in Step 1.) to its original location.

Upgrading directly from LMS R1.0

If you are upgrading directly to LMS Release 1.0.1 from Release 1.0, follow this procedure:

  1. On the LMS Server, copy the packages directory to a back-up location, so you don't lose it during the upgrade.

  2. Uninstall LMS Release 1.0, as described in the Release 1 Installation Guide.

  3. Review the R1.0.1 system requirements in this document and make sure your systems meet these requirements.

  4. SQL Server users only: export R1.0 data to a new SQL Server database (instructions below) to incorporate database schema changes.

  5. Install the LMS R1.0.1 as described in the R1.0.1 Installation Guide.

  6. Move the packages directory (which you backed up in Step 1.) to its original location.

Exporting your SQL Server data to a new database

This method copies your R1.0 data directly to a new R1.0.1 database, leaving your R1.0 database intact.

  1. Create a new SQL Server database, using a new name.

  2. Run the LMS schema creation scripts, but do not run the scripts that seed the database with data.

  3. Open the SQL Server Enterprise Manager.

  4. In Enterprise Manager, right-click on the source database (the R1.0 database), select "all tasks," and then click Export data.

  5. Select your new database as the target database.

  6. Select "copy objects and data."

  7. Deselect "create destination objects."

  8. Select "append data" (instead of "replace").

Database server requirements

You'll need a relational database management system with IBM Lotus Learning Management System. When you install the LMS, you'll create (or upgrade) a database specifically for use with the LMS. The LMS supports the following relational database management systems:

LMS supports all of these databases for all the platforms on which they run. DB2 running on IBM zSeries or IBM iSeries machines is not supported.

LMS server (LMM and Delivery) operating system requirements

LMS servers support the following operating systems:

Keep in mind the following information concerning LMS servers and operating systems:

Note All servers used within the LMS framework should be synchronized to the same time and date, to ensure correct timestamps on reports.

Client operating system and browser requirements

LMS clients support the following operating systems and browsers:

Keep in mind the following information concerning client operating systems, browsers, and other related software :

Offline Learning Client: System Requirements

Users intending to install the Offline Learning Client to their workstations should be made aware of the following system requirements for this component:

Application server information

The WebSphere® Application Server (WAS) Release 5.0 is bundled as part of LMS. LMS has been tested with WAS but it is possible to substitute other Application Servers though you may not qualify for technical support.

WAS Release 5.0 supports the following:

Web server information

The IBM HTTP server is bundled with WebSphere as part of LMS and has been tested.

LDAP server requirements

Learning Management System Release 1.0 requires a LDAP v3. compliant directory. The list of supported LDAP products includes:

Using SSL with the LMS

Use of the Secure Sockets Layer for LMS is supported with this release. To switch to SSL-enabled transactions, use https:// in all relevant URLs, including those you specify during installation, at application startup, and for content launching.

Setting up WebSphere for SSL

The WebSphere server needs to be enabled for SSL before the LMS and Delivery Servers can use SSL. You can either create a self-signed certificate, as described below, or get a certificate signed by a Certificate Authority. For more detailed information, see Sections 10.10.1 and 10.9.2 of the Redbook IBM WebSphere V5.0 Security WebSphere Handbook Series.

  1. Create a self-signed certificate using the IBM Key Management application.

    Be sure to set the common name to the fully qualified DNS name of the server.

  2. Edit <IBMHttpServer>/config/httpd.conf to include the following lines in the order in which they appear below.

    For Windows 2000:

    LoadModule ibm_ssl_module modules/IBMModuleSSL128.dll

    For Solaris/AIX/Linux:

    LoadModule ibm_ssl_module libexec/mod_ibm_ssl_128.so

    For all platforms:

    …
AddModule mod_ibm_ssl.c
…
Listen 80
Listen 443
…
<VirtualHost :443>
   SSLEnable
   SSLClientAuth none
   Keyfile "/usr/IBMHttpServer/ssc_keys/key.kdb"
   SSLStashfile "/usr/IBMHttpServer/ssc_keys/key.sth"
</VirtualHost>

    For keyfile and stashfile, specify filenames for the key database and stash that were created in step (1).

  3. Add a new host alias for SSL for port 443:

    1. In the WebSphere admin console, go to Environment - Virtual Hosts.

    2. Click the link for the name of them host to modify, typically default_host.

    3. In the detail page for the selected virtual host, click Host Aliases.

    4. Click New to define a new alias.

      For name, enter asterisk (*). For port, enter 443.

    5. Click OK, then save the WebSphere configuration.

  4. Edit the WebSphere Apache plugin-cfg.xml:

  5. Extract and install the self-signed certificate you created in Step 1 using the IBM Key Management application:

    1. Find the WAS keystore.

      In the WebSphere admin console, go to Security - SSL - (Application Node) and look at the value of "Trust File Name." Assume the trust filename is ${USER_INSTALL_ROOT}/etc/DummyServerTrustFile.jks.

    2. Extract the self-signed certificate.

      This is described in Step 19 on page 269 of the "IBM WebSphere V5.0 Security WebSphere Handbook Series."

    3. Import the certificate into the WAS trust file by issuing the following command on one line from ${USER_INSTALL_ROOT}: 
      java/bin/keytool -import -file tigris.cer -keystore etc/DummyServerTrustFile.jks
 -alias "LMS_Self_Sign" -trustcacerts

      Note The default password for DummyServerTrustFile.jks is WebAS.

  6. Restart IBMHttpServer.

Setting up the LMS and Delivery Servers

Perform these steps on both the LMS and Delivery Servers.

Requiring SSL for User Logins

  1. In the WebSphere admin console, create an environment entry with the name LMS_TRUE, using the StringObjectFactory referencable, and a custom property named "setting" and with the value "true."

  2. When deploying the LMM and DS .ear files, you are prompted to bind an environment entry to a reference named HTTPS_LOGIN. Select the LMS_TRUE entry that you just created.

  3. For the HTTPS_APPLICATION reference, leave this unbound, or bind it to an entry that specifies the value "false".

  4. In the WebSphere admin console, in SSO configuration activate the "Requires SSL" checkbox.

Requiring SSL for the LMS Application

  1. In the WebSphere admin console, create an environment entry with the name LMS_TRUE if you haven't already created it, using the StringObjectFactory referencable, and a custom property named "setting" and with the value "true."

  2. Bind an environment entry to a reference named HTTPS_APPLICATION. Select the LMS_TRUE entry that you just created.

Requiring SSL for tracking

If SSL is to be used for tracking, then the tracking URL that is part of the Delivery Server setup at installation time must specify the https protocol.

LMS Hardware guidelines

Server guidelines

The following servers are supported with LMS:

For servers, minimum memory requirements are 2 GB RAM per server. 4 GB RAM per server is recommended.

Client guidelines

The sizes listed above are the minimum requirements for LMS Rel. 1.0; you may find your installation needs more. Memory and disk space requirements are directly affected by the number of courses and users registered in LMS and by the number of students enrolled in courses at one time. Machine speed will affected by the number of users attempting to access course information and materials at the same time.

The list below describes the minimum hardware requirements for LMS clients:

Additional LMS guidelines

URLs and Internet host names

The LMS servers should have a fully qualified URL, including the DNS suffix, and a static IP address.

Audio and video requirements

There are additional requirements for using Audio/Video software with LMS sessions. For more information about enhancing courses with audio/video software, see the Sametime® Administrator's Guide.

Authoring Tool operating system issues

If you plan to install Authoring Tool on a Windows NT OS + SP6a only machine, you will have problems running Authoring Tool. To correct this problem, make sure that you have installed MDAC (Microsoft Data Access Components) 2.5 or later. Refer to http://msdn.microsoft.com for more information on MDAC.

Ordering your copy of JReport Designer for building LMS reports

JReport DesignerTM allows you to create sophisticated reports with graphics, charts, crosstabs, sub-reports, parameters and functions, and output to a variety of formats. With JReport Designer, you can build templates, customize existing reports, and create whole new reports quickly and easily using a simple, drag-and-drop design interface and Report Wizard. The visual interface makes it easy to edit objects and properties, and to share them among reports. You can even define your own templates and styles. Every Learning Management System customer installation is entitled to one copy of JReport Designer, available from Jinfonet Software. Go to the Lotus LMS page on the Jinfonet site to request your copy.

LMS Application Programming Interface and Web Services

The IBM Lotus Learning Management System (LMS) Application Programming Interface (API) is a programming interface that provides developers with access to many features of the Learning Management System.

The LMS API is a Web Services API. This means that it uses the Simple Object Access Protocol (SOAP) to allow you LMS access from any system that supports HTTP as well as supporting many different programming languages.

Specifically the LMS API gives you the ability to do the following:

Developers who want to learn more should point their browsers at http://www-1.ibm.com/support/search/index.html and search on "LMS API and Web Services."

Migration paths

You can migrate to the LMS from LearningSpace Forum 3.5 and 3.6, from LearningSpace 4.11, and from LearningSpace 5.01. To obtain the migration utilities and Migration Guide, point your browser at: http://www-1.ibm.com/support/search/index.html and search on "Learning Management System Migration Utility and Quarterly Documentation Updates." This will bring up the documents that contain the information about the latest migration utilities and documentation, and where to obtain them. Be sure to read the Migration Guide before attempting to migrate any data.

Product documentation

In addition to this ReadMe file, the product documentation consists of the Release Notes and the following online Help and guides.

Help

Online help describes the steps needed to complete various tasks in the Learning Management System.

Guides

These guides provide high-level descriptions, as well as details, for the tasks involved in using the product. The guides are formatted as PDF files, which require the Adobe® Acrobat® Reader for display.

Updates to these guides will be available periodically. To obtain the updated guides, point your browser at: http://www-1.ibm.com/support/search/index.html and search on "Learning Management System Migration Utility and Quarterly Documentation Updates." This will bring up the documents that contain the information about the latest documentation updates, and where to obtain them.

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.

Copyright

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.

Copyright (c) 2003 International Business Machines Corporation.

All rights reserved.

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

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, Pathware, 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.

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, Active Directory, 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.

JReport Server EngineTM copyright and trademark information

Developed by Jinfonet Software, Inc.

9400 Key West Ave., Suite 250

Rockville, MD 20850

www.jinfonet.com

Copyright © 1998-2003, Jinfonet Software, Inc. All rights reserved.

Additional licensing information

LMS currently ships with additional software other than LMS software. The following is license information for those additional products:

Apache Software license, Version 1.3.26

Copyright (C) 2003 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
  4. The names "Apache Forrest" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
  5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/.

JDOM Software license

Copyright (C) 2000-2003 Brett McLaughlin & Jason Hunter. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.
  3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact license@jdom.org.
  4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management (pm@jdom.org).

In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following: "This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Brett McLaughlin (brett@jdom.org) and Jason Hunter (jhunter@jdom.org). For more information on the JDOM Project, please see http://www.jdom.org/.