IBM Lotus Learning Management System R1.0.3 ReadMe


Copyright and Licensing Information


ReadMe contents

This document contains information you need to install IBM® Lotus® Learning Management System Release 1.0.3. 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 "Workplace Collaborative Learning Migration Utility and 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.0.2

If you are upgrading to LMS Release 1.0.3 from Release 1.0.2, follow this procedure:

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

  2. Copy the directories and files listed below to a back-up location, as they will be overwritten during the product upgrade.

These files all contain information that you may want to reapply after upgrading the product:

  1. Uninstall the LMS R1.0.2 Enterprise Applications from WebSphere, as described in the LMS R1.0.3 Installation Guide.

Important: Do not remove any databases.

  1. Apply the database upgrade scripts for the appropriate database backend you are using with LMS.

Do this by copying the upgrade scripts to a machine that has a database client configured to connect to the LMS databases, and then running the scripts against the LMM schema. Do this as follows:

For DB2 users:

LMM database

db2 connect to <lmmdbname> user <lmmdbusername> using <lmmdbpassword>
db2 -tvf upgrade_lmm_db2_103.sql

DS database

db2 connect to <dsdbname> user <dsdbusername> using <dsdbpassword>
db2 -tvf upgrade_ds_103.sql

For Oracle users:

LMM database

sqlplus <lmmdbuser>/<lmmdbpass>@<lmmdbserver> @upgrade_lmm_ora_103.sql

DS database

sqlplus <dsdbuser>/<dsdbpass>@<dsdbserver> @upgrade_ds_103.sql

For SQL Server users:

LMM database

isql -S <lmmserver> -U <lmmuser> -P <lmmpass> -d <lmmdb>  -i upgrade_lmm_mssql_103.sql

DS database

isql -S <dsserver> -U <dsuser> -P <dspass> -d <dsdb>  -i upgrade_ds_103.sql
  1. Install the new LMS Learning Management Module (lms-lmm.ear) and Delivery Server (lms-ds.ear) Applications to Websphere.

These files are stored in the Distribute directory on the LMS R1.0.3 CD. See "Deploying the Learning Management System Server Application" and "Deploying the Delivery Server Application" in the LMS R1.0.3 Installation Guide for more information on installing these applications.

  1. Restore changes to the ds-settings.xml and settings.xml files, if you modified them.

If the original files from R1.0.1 match the new versions installed with R1.0.3, you can simply replace the R1.0.3 versions with your customized versions of the R1.0.1 files.

If they don't match, or if you no longer have the original files from R1.0.1, you can review the older files, and manually reapply changes to the newer versions.

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

  2. Move any directories containing customization sets back to their original location, and update the customization sets as needed to accommodate this new release.

If you created customization sets in a previous release of the LMS, you may need to modify them for use with this release, to accommodate possible changes to JSPs, images, and style sheets. Compare your customized files from R1.0.1 with those used in R1.0.3 to determine where changes can be reapplied.


Upgrading from LMS R1.0a or R1.0.1

If you are upgrading to LMS Release 1.0.3 from Release 1.0a or R1.0.1 follow this procedure:

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

  2. Copy the directories and files listed below to a back-up location, as they will be overwritten during the product upgrade.

These files all contain information that you may want to reapply after upgrading the product:

  1. Uninstall the LMS R1.0a Enterprise Applications from WebSphere, as described in the LMS R1.0.3 Installation Guide.

Important: Do not remove any databases.

  1. Apply the database upgrade scripts for the appropriate database backend you are using with LMS.

Do this by copying the upgrade scripts to a machine that has a database client configured to connect to the LMS databases and then running the scripts against the LMM and DS schemas.

Note You only run the scripts starting from your current release; if you have R1.0.1 installed already, you don't need to run the first script in each sequence as it upgrades your database from R1.0a to R1.0.1 (which you have done already). Do this as follows:

For DB2 users:

LMM database

db2 connect to <lmmdbname> user <lmmdbusername> using <lmmdbpassword>
db2 -tvf upgrade_lmm_db2_101.sql [R1.0.a==>R1.0.1]
db2 -tvf upgrade_lmm_db2_102.sql [R1.0.1==>R1.0.2]
db2 -tvf upgrade_lmm_db2_103.sql

DS database

db2 connect to <dsdbname> user <dsdbusername> using <dsdbpassword>
db2 -tvf upgrade_ds_db2_101.sql [R1.0.a==>R1.0.1]
db2 -tvf upgrade_ds_102.sql [R1.0.1==>R1.0.2]
db2 -tvf upgrade_ds_103.sql [R1.0.2==>R1.0.3]

For Oracle users:

LMM database

sqlplus <lmmdbuser>/<lmmdbpass>@<lmmdbserver>  @upgrade_lmm_ora_101.sql [R1.0.a==>R1.0.1]
sqlplus <lmmdbuser>/<lmmdbpass>@<lmmdbserver>  @upgrade_lmm_ora_102.sql [R1.0.1==>R1.0.2]
sqlplus <lmmdbuser>/<lmmdbpass>@<lmmdbserver>  @upgrade_lmm_ora_103.sql [R1.0.2==>R1.0.3]

DS database

sqlplus <dsdbuser>/<dsdbpass>@<dsdbserver>  @upgrade_ds_ora_101.sql [R1.0.a==>R1.0.1]
sqlplus <dsdbuser>/<dsdbpass>@<dsdbserver>  @upgrade_ds_102.sql [R1.0.1==>R1.0.2]
sqlplus <dsdbuser>/<dsdbpass>@<dsdbserver>  @upgrade_ds_103.sql [R1.0.2==>R1.0.3]

For SQL Server users:

LMM database

isql -S <lmmserver> -U <lmmuser> -P <lmmpass> -d <lmmdb> -i upgrade_lmm_mssql_101.sql [R1.0.a==>R1.0.1]
isql -S <lmmserver> -U <lmmuser> -P <lmmpass> -d <lmmdb> -i upgrade_lmm_mssql_102.sql [R1.0.1==>R1.0.2]
isql -S <lmmserver> -U <lmmuser> -P <lmmpass> -d <lmmdb> -i upgrade_lmm_mssql_103.sql [R1.0.2==>R1.0.3]

DS database

isql -S <dssserver> -U <dsuser> -P <dspass> -d <dsdb> -i upgrade_ds_mssql_101.sql [R1.0.a==>R1.0.1]
isql -S <dssserver> -U <dsuser> -P <dspass> -d <dsdb> -i upgrade_ds_102.sql [R1.0.1==>R1.0.2]
isql -S <dssserver> -U <dsuser> -P <dspass> -d <dsdb> -i upgrade_ds_103.sql [R1.0.2==>R1.0.3]
  1. Install the new LMS Learning Management Module (lms-lmm.ear) and Delivery Server (lms-ds.ear) Applications to Websphere.

These files are stored in the Distribute directory on the LMS R1.0.3 CD. See "Deploying the Learning Management System Server Application" and "Deploying the Delivery Server Application" in the LMS R1.0.3 Installation Guide for more information on installing these applications.

  1. Restore changes to the ds-settings.xml and settings.xml files, if you modified them.

If the original files from R1.0a match the new versions installed with R1.0.3, you can simply replace the R1.0.3 versions with your customized versions of the R10.a files.

If they don't match, or if you no longer have the original files from R1.0a, you can review the older files, and manually reapply changes to the newer versions.

  1. Move the packages directory (which you backed up in Step 2) to its original location.
  2. Move any directories containing customization sets back to their original location, and update the customization sets as needed to accommodate this new release.

If you created customization sets in a previous release of the LMS, you may need to modify them for use with this release, to accommodate possible changes to JSPs, images, and style sheets. Compare your customized files from R1.0a with those used in R1.0.3 to determine where changes can be reapplied.


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:

Unless noted above, the LMS supports all of these databases for all the platforms on which they run.


LMS server (Learning Server and Delivery Server) operating system requirements

LMS servers support the following operating systems:

As of R1.0.3, Microsoft Windows NT Release 4.0 is no longer supported.

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:

As of R1.0.3, Microsoft Windows NT workstation is no longer supported for LMS clients.

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:

LMS R1.0.3 also supports WAS Release 5.01.


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 an LDAP v3. compliant directory. The list of supported LDAP products includes:


Collaboration requirements

Live session requirements

The Lotus Learning Management System R1.0.3 requires the IBM Lotus Virtual Classroom R1.1, or higher, to support live sessions.

Chat, audio, and video requirements

The Lotus Learning Management System R1.0.3 requires Sametime R3 (installed over Domino R5.0.10 or later) to support chat features (previous releases of the LMS used earlier versions of these products). 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.


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.

  1. 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).

  1. 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 the 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.

    1. Click OK, then save the WebSphere configuration.
  1. Edit the WebSphere Apache plugin-cfg.xml:
  1. 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.

    1. Extract the self-signed certificate.

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

    1. Import the certificate into the WAS trust file by issuing the following command on one line from ${USER_INSTALL_ROOT}:
c.                 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.

  1. 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.


Installing XVFB on Linux and AIX platforms to enable reporting

If you run the LMS on a UNIX platform, you must install XVFB (Xserver Virtual Frame Buffer) to enable the reporting feature. XVFB provides a virtual Xserver that runs without a head or graphics card, releasing you from the requirement of running a real Xserver.

XVFB installation and configuration differs for Linux and AIX.

Installing XVFB on Linux

XVFB for Linux is a freeware and can be obtained from x.org's X11R6 distribution. Use the following procedure to install XVFB on Linux:

  1. Check the directory /usr/X11R6/bin for a file named Xvfb.
    • If you have this file, skip to step 4.
    • If you don't have this file, proceed with step 2.

  2. Download the XVFB file from the following link to a directory on the Linux machine:
  3. http://ftp.xfree86.org/pub/XFree86/4.2.0/binaries/Linux-ix86-glibc22/
    
  4. Download the file "Xvfb.tgz" and extract the file with the following commands:
  5. chmod +x extract
    mkdir /etc/X11
    ./extract -C /usr/X11R6 Xvfb
    

    For systems that do not have the extract utility, do the following:

    gunzip Xvfb.tgz    #this will uncompress the .tgz file to a Xvfb.tar
    mv Xvfb.tar /usr/X11R6
    tar -xvf Xvfb.tar  #from /usr/X11R6 directory
    
  6. Generate a script file named /etc/init.d/xvfb containing the following, and make it executable:
  7. #!/bin/sh
    mode=$1
    case "$mode" in
    'start')
       # start the X Virtual Framebuffer (Xvfb)
       if [ -f /usr/X11R6/bin/Xvfb ]; then
         echo "***Starting up the Virtual Frame Buffer on Screen 1***"
         /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &
       fi
       ;;
    *)
       echo " Usage: "
       echo " $0 start (start XVFB)"
       echo " $0 stop (stop XVFB - not supported)"
       exit 1
       ;;
    esac
    exit 0
    chmod +x xvfb
    

    The script ends with the "exit 0" line The line that follows lets you change the permissions on the file to allow users to execute it.

  8. Change the run-level to 3 by doing the following:
  9. Edit etc/inittab
    # Default run-level. The run-levels used by RHS are:
    #   0 - halt (Do NOT set initdefault to this)
    #   1 - Single user mode
    #   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
    #   3 - Full multiuser mode
    #   4 - unused
    #   5 - X11
    #   6 - reboot (Do NOT set initdefault to this)
    #
    id:5:initdefault:
    Change id:5:initdefault: to id:3:initdefault:
    

    Note: If you use a different run-level, be sure to match it when you set up the soft link in the next step.

  10. Create the soft link with the following command:
  11. ln -s /etc/init.d/xvfb /etc/rc3.d/S75xvfb
    

    This example uses run-level 3. If you intend to use XVFB in a different run-level, set up the soft link to the appropriate /etc/rcx.d directory. (The run-level of your Linux system is specified in your /etc/inittab file ).

    Note Always make sure to check the setting and exporting of the DISPLAY variable and to start XVFB from the soft link to help with consistent reporting performance.

  12. Start the Xvfb via the soft link by using the following command:
  13. /etc/rc3.d/S75xvfb start
    
  14. Verify that XVFB is running with the following command:
  15. ps -ef | grep Xvfb
    
  16. Set DISPLAY from the command line using:
  17. DISPLAY=hostname:1.0
    export DISPLAY
    

    where hostname is the fully qualified hostname for the server. For example, server.lotus.com. Previous lines can be added to .bash_profile or whatever profile you're using.

  18. If Network Deployment is installed, stop the nodes, stop the DeploymentManager, start the DeploymentManager and start the nodes from the ../WebSphere/DeploymentManager/bin and ../WebSphere/AppServer/bin directories respectively. In some cases, the ../AppServer/config/cells/plugin-cfg.xml file may need editing.
  19. If Network Deployment is not installed, stop and start the server from the ../WebSphere/AppServer/bin directory.

Installing XVFB on AIX

Use the following procedure to install XVFB on AIX. For complete instructions, refer to the AIXwindows Programming Guide - Appendix E - The X Virtual Frame Buffer . This information can be found at http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/aixwnpgd/xvfb.htm#xvfb.

  1. Add the following line to /etc/initab:
  2. xvfb:2:respawn:/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :1 > /dev/null
    
  3. Set DISPLAY by adding the following line to .profile:
  4. DISPLAY=`hostname`:1.0
    export DISPLAY
    
  5. Restart the server machine.


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.

Recommended minimum configuration for an LMS installation

The minimum configuration for LMS is a 2-tier configuration with 3 machines, where machine 1 will host:

and machine 2 will host:

and machine 3 will host:

Each of the 3 machines must have a P4 processor (or better), with a speed of 2.0 Ghz (or faster), and at least 2 GB RAM.

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:

Client machines with 64 MB may be used if the LMS student interface is being used without Collaboration features and without third-party content that requires Web players.


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.

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. You can use the LMS API to create a variety of application programs, including:

Using the LMS API, programs can perform the following Learning Management System functions:

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 documentation."


Tuning Parameters

This section describes tuning parameters thay may improve your LMS system performance:

Recommended server tuning parameters for LMS

IBM HTTP Server

Use the following parameters or make the following changes:

AFPA

Comment out the following lines in httpd.conf in IBMHttp\conf directory:

Application Server - JAVA VM

Set the minimum heap size and maximum heap size to same value. On a 2 GB system, set the heap size to 512 MB; on a 4 GB system set heap size to 768 MB.

Garbage collection setting: Use the "-Xnoclassgc" parameter (JVM setting > Advanced JVM Settings). Modify command line args to include param)

JIT

Turn on JIT.

Web Container

For Process priority (server1 > Process Definition >Process Priority) change from 20 to 0 so that the Learning Server has a higher priority than the application app server.

Set the Web Container thread pool size to 100.

Change the Session Management session Timeout from 30 to 15 minutes.

JDBC Connection Pool

Set the Pool size to 100. Appropriate changes also need to be made on the server side (MAXAPPLS for DB2).

DBMS Server

Disk space for databases (unlimited).

Updating the WebSphere plug-in file for the Application Server nodes

When Network Deployment is installed, the Deployment Manager (DM) attempts to synchronize the plugin-cfg.xml files of all its nodes. When the DeploymentManager is restarted or when the plugin file is regenerated from the WAS Admin console, the DM copies the plugin-cfg.xml from the ...\DeploymentManager\config\cells out to all its nodes under ...\AppServer\config\cells for each server.

Intermittently, there can be problems experienced with the plugin-cfg.xml file copied down from the DM. The URLs in this copy of the file are set to ...\DeploymentManager\... . In some deployments these URLs are invalid for the nodes and need to be updated to ...\AppServer\... in the plugin-cfg.xml files under \AppServer\config\cells.

The symptom of having an invalid plugin-cfg.xml file is typically the inability to launch the application via the IBMHttpServer. The application can be launched by specifying the virtual host port in its URL (for example, http://server.ibm.com:9080/lms-lmm).

Additional suggestions for fixing this problem:

Suggestions for deploying mutiple applications per Application Server

When installing the Learning and Delivery Server on the same node, do NOT create separate application servers for them. Instead, beside the default application server (server1), create one new application server (for example, named LMS) and deploy the Learning and Delivery Server applications onto this server.

Database disk space suggestions for archiving and back-ups

In some cases, the database server may run out of disk space if online back-ups are enabled. If databases are enabled for online back-up (DB2: logretain = recovery, Oracle: archivelog = enable), the storage of these archived recovery logs must be managed. If it is not managed, the database server will run out of disk space and the database server will not be able to process transactions causing the application to stop functioning. It is recommended that if there is no database administrator or procedure in place to manage the archived recovery logs, they should not be archived. If there is someone to manage them, online back-ups and archived recovery logs are recommended.

Tuning the Oracle PROCESSES parameter for use with LMS

On the Oracle server, the PROCESSES parameter is often set to 150 (the default). This may create performance problems. The recommended setting is four times that amount (PROCESSES = 600). This value is configured within the SPFILEORACLE.ORA file. After setting the PROCESSES parameter to a new value, you should restart the Oracle instance for the new value to take effect.

Using Multi Threaded Server (MTS) with Oracle

For Oracle back-end servers, do not enable Multi-threaded Server (MTS) for Oracle databases. This is basically connection pooling; since the application server does its own connection pooling, this will not help performance. Also, if it is not configured with enough servers, "deadlock" errors can occur.

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 "Workplace Collaborative Learning Migration Utility and 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 "Workplace Collaborative Learning Migration Utility and 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/.