Installation Guide
software
Learning Management System R1
Installation Guide
September 2003
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
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 LMS System Requirements......................................................................................................3
Database server requirements ................................................................................................................................................. 3
Learning Management System server requirements ........................................................................................................... 3
Learning Management System client requirements............................................................................................................. 3
Chapter 3 LMS Installation Overview........................................................................................................5
Packaging overview.................................................................................................................................................................. 5
Some words about LMS Settings & Configuration information......................................................................................... 5
An outline of the installation process..................................................................................................................................... 6
Chapter 4 Identifying LMS Hardware Assets .........................................................................................11
Allocating server responsibilities.......................................................................................................................................... 11
Creating a new database or upgrading an existing database ........................................................................................... 11
LMS 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 (LMS) Server Application Files ................................21
Installer program information............................................................................................................................................... 21
Installing the LMS Server application software.................................................................................................................. 22
Chapter 8 Installing the LMS 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 ................................................39
Database Creation Overview................................................................................................................................................. 39
Table of Contents iii
DB2 database creation and configuration for LMS: an example ...................................................................................... 40
Oracle database creation for LMS ......................................................................................................................................... 46
MS SQL Server database creation for LMS.......................................................................................................................... 48
Additional information about running scripts in different environments...................................................................... 49
Chapter 10 Installing the Network Deployment (ND) Module ...............................................................51
Chapter 11 Configuring JDBC Data Sources .........................................................................................55
Data source overview ............................................................................................................................................................. 55
Defining the JDBC provider .................................................................................................................................................. 56
Chapter 12 Configuring Environment Entries........................................................................................65
Configuring an environment entry for the log file location .............................................................................................. 65
Chapter 13 Configuring WebSphere Application Server Security .......................................................73
Configure the LDAP directory for use with LMS............................................................................................................... 74
Chapter 14 Deploying the Learning Management System (LMS) Server Application........................77
Chapter 15 Deploying the Delivery Server (DS) Application ................................................................87
Starting the application and regenerating web server plug-in ......................................................................................... 87
Chapter 16 Deploying the LMS and DS Components onto Separate WAS Application Servers ......89
Chapter 17 Starting the Applications......................................................................................................91
Starting the LMS Server application................................................................................................................................. 91
Starting the Delivery Server application.......................................................................................................................... 91
Regenerating the web server plug-in ............................................................................................................................... 92
Running the Updater.......................................................................................................................................................... 92
Chapter 18 Post-Installation Tasks .........................................................................................................93
Configuring on-line help........................................................................................................................................................ 93
Adding the Delivery Server to the LMS application.......................................................................................................... 93
Deploying the Offline Learning Client................................................................................................................................. 94
Installing the LMS Authoring Tool....................................................................................................................................... 94
Installing the Command Line Import Utility (CLIMP)...................................................................................................... 94
Migrating LearningSpace data .............................................................................................................................................. 95
Installing XVFB on UNIX platforms to enable reporting .................................................................................................. 95
Determining the correct SSO settings for LMS ................................................................................................................... 97
iv IBM Lotus LMS Release 1 Installation Guide
Chapter 19 Special Installation Issues ...................................................................................................99
Using SSL with the LMS......................................................................................................................................................... 99
Using the Directory Server Web Administration Interface with Linux........................................................................... 99
Chapter 20 Removing the IBM Lotus Learning Management System ...............................................101
Uninstalling the LMS and DS applications........................................................................................................................ 101
Removing the installed LMS files ....................................................................................................................................... 101
Removing the LMS, DS, and Audit databases .................................................................................................................. 101
Index ........................................................................................................................................................103
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 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 (LMS) is a scalable, flexible platform for managing both classroombased 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 (LMS) Server, Authoring Tool, Delivery Server, and an Offline Learning Client to support
disconnected use. LMS 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 LMS product streamlines the overall
management of an organization's training activities, increasing efficiencies and saving time and expenses.
With the LMS' 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 LMS authoring tool. Subject matter experts can create courses on their own, with no programming skills
required.
Understanding the Learning Management System Architecture
The Learning Management System components
The 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 the 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 LMS Server. When users run The Learning Management System, the LMS Server initiates
database transactions to retrieve and update information about course structure, user permissions, and assessment
questions. For more information on LMS 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
LMS System Requirements
The IBM Lotus 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 Learning Management System with unsupported hardware or software may result in data loss, as well as
problems accessing the system. Before installing 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 LMS software components
For more information on the packaging and layout of the LMS software components, refer to the README.TXT and
Release Notes shipped with this product.
4 IBM Lotus LMS Release 1 Installation Guide
Chapter 3
LMS 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 (LMS) product are J2EE™ web applications. J2EE
provides the packaging for these components as a standard.
The important units of the LMS 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 LMS 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 LMS 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 LMS 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
LMS Server is named settings.xml, and the corresponding file for the Delivery Server is named dssettings.xml. When the servers first start, they read settings from these files.
•
The LMS 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 LMS Installer or, subsequently, the LMS user interface, those
settings are stored in the application database. You can change settings that you specified with the LMS Installer by
using the LMS 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
Updater then creates two update SQL scripts - one for the LMS server (updateLMM.sql) and one for the Delivery
Server (updateDS.sql). These scripts are then run to change the respective databases.
Chapter 3: LMS Installation Overview 5
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 LMS 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, 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 Learning Management System connects to without modifying 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 LMS Hardware Assets.” Refer also to your WebSphere
documentation for guidelines on the various server configuration options that are available for your LMS
deployment.
2. Install the database server software
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 LMS 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
the WebSphere and Learning Management System administrator (who may be one and the same person).
The organization of the LDAP directory is a key factor in operating Learning Management System. Many
aspects of Learning Management System operation require that directory path expressions be specified. An
6 IBM Lotus LMS Release 1 Installation Guide
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 LMS Installer to install the necessary LMS Server and Delivery Server files
The Learning Management System Installer installs all of the files necessary for the eventual deployment of
the LMS and Delivery Servers. The Installer also gives you the option to install additional LMS-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 System (LMS) 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
LMS, 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 LMS 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 LMS 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, LMS,
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 LMS database account.
o
Execute the supplied LMS 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.
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”.
Chapter 3: LMS Installation Overview 7
7. Install the Network Deployment module (optional)
The Network Deployment (ND) module configures and controls multi-server WAS installations. If you
intend to deploy 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 LMS, Audit, and
Delivery.
For more information, refer to “Chapter 11 Configuring JDBC Data Sources.”
9. Configure environment entries
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 System (LMS) Server application
After the application files have been installed with the LMS 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 LMS Server and the LMS Delivery Server. The LMS 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.
For more information, refer to “Chapter 14 Deploying the Learning Management System (LMS) Server
application “ and “Chapter 16 Deploying the LMS and DS components onto separate WAS App Servers.”
12. Deploy the LMS 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 LMS Server.
8 IBM Lotus LMS Release 1 Installation Guide
For more information, refer to “Chapter 15 Deploying the LMS Delivery Server (DS) application.” and
“Chapter 16 Deploying the LMS 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 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 LMS 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 LMS more successfully. These tasks include
the following:
•
Configuring on-line help
•
Adding the Delivery Server to the LMS application
•
Deploying the Offline Learning Client
•
Installing the LMS 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 LMS
To complete these tasks, make sure that you have logged into LMS as the Administrator. Refer to the LMS
Administrator’s Guide for more information.
Finally, should you need to remove the LMS, 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 LMS 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.
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 System LMS 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 LMS 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 LMS 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 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 Learning Management System. Perform the database upgrade during installation or
after. In all cases you need to install the LMS complete with the LMS databases. The migration procedures will then
connect to the source (LearningSpace 4 or 5) database to unload the data and load it into the LMS database.
For additional information on information migration, refer to the “Information Migration” chapter or the LMS
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
LMS 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 LMS, 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://www3.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 local machine)
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 local machine)
# 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 LMS 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.
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.
5.
For Windows users, choose to run both WebSphere Application Server and IBM HTTP Server as
services.
Chapter 5: Installing the WebSphere Core 13
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 LMS 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:
•
Expand the Security panel on the left side.
•
Expand Authentication Mechanisms
14 IBM Lotus LMS Release 1 Installation Guide
•
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 LMS and SSO refer to Chapter 5 Managing Users in the IBM Lotus LMS 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 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 Learning Management System. Many aspects of
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 www.ibm.com/software/directory for more information on obtaining
the necessary components.
Installing the IBM Directory Server LDAP Directory: an example
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.
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.
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:
Chapter 6: Installing or identifying the LDAP directory 17
9.
•
Client SDK 4.1
•
*DMT 4.1 & Java 1.3
•
Server 4.1
•
DB2 V7.2 (if necessary)
•
GSKit5
•
IBM HTTP Server 1.3.19 (if necessary)
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.
18 IBM Lotus LMS Release 1 Installation Guide
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.
•
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:
1.
Start the Directory Management Tool: Start - Programs - IBM Directory Server - Directory Management
Tool.
2.
Logon as the directory administrator and do the following:
3.
4.
•
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.
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.
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 LMS 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 LMS 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 LMS, 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 (LMS) Server Application Files
Before deploying the complete Learning Management System, the LMS Server files should first be installed on the
Application Server.
Note: If you are installing and deploying the LMS Server and the Delivery Server onto separate WAS servers, refer
also to Chapter 16 Deploying the LMS and DS Components onto Separate WAS Application Servers for further
information.
The important unit of packaging in the LMS 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 LMS and Delivery Servers. The Installer also gives you the option to install additional LMSrelated 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 LMS 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
Install.bat
Installer.exe
AIX
install.sh
AIXInstaller.bin
Linux
install.sh
LinuxInstaller.bin
Sun
install.sh
SolarisInstaller.bin
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.
The following steps explain the LMS Server file install procedure using the Installer.
Chapter 7: Installing the LMS Server Application Files 21
Note: You can install the LMS 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 LMS Server and
Delivery Server (LDAP settings, for example), installing both applications together allows you to specify those
settings only once.
Installing the LMS 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
LMS license agreements are installed in the LMS license subdirectory. Use any text viewer to read or print
them in English or in the language configured on your machine.
Select the LMS 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 LMS 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). LMS 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 LMS 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 LMS Server settings
13. Enter the following LMS Server Settings for your LMS configuration:
•
Base URL – Enter the base URL for accessing the LMS Server. An example setting would be:
http://lms.acme.com/lms-lmm
•
Description – this is an optional text field to provide additional information about the LMS Server.
•
User Name and Password– Enter a user name and password for the LMS Server. These will be used for
authenticating the LMS server when it communicates with the Delivery Server. The user name and
password are arbitrary: they don’t need to identify an actual user in your LDAP directory. During the
Chapter 7: Installing the LMS Server Application Files 23
install of the DS Server, the LMS username and password is asked again. Make sure that you provide
there the same LMS Server password that you are providing here.
14. Click Next to continue after you have entered all of the settings. You are now shown the Administrator
Settings screen.
24 IBM Lotus LMS Release 1 Installation Guide
Select the Administrator settings
15. Select the Administrator Role Type for the LMS Server. User is the default value. If you select the User
setting, enter the corresponding Administrators LDAP User ID. An example of this user name is: jsmith.
16. If you wish to have Group as your role type, select Group and enter the corresponding LDAP Group Name.
Typically, you would enter a group name if you want to enable multiple users to have administrator
privileges. An example of this group name is: LMSadmins/group/acme.
17. Click Next to continue. You are now shown the Content Manager Settings screen.
Select the Content Management settings
18. Enter the following Content Management Settings for your LMS configuration. The information you enter at
this screen determines how you deploy course content. These settings determine the FTP source used for
managing your LMS course content. All of these fields must contain a value.
•
Path to Imported Course Packages – Enter the local directory on the LMM server's file system
where LMM will store uploaded course packages. If the path is a relative directory (for
example, "packages"), the course packages will be stored at
<WASInstallPath>\InstalledApps\<NODE>\LMM.ear\lms-lmm-complete-23.war\<relative
directory>. If the path is a non-relative directory (for example, "d:\packages"), the course
packages will be stored on the LMM server in the specified directory without adding the
LMM's ear file installation path to the beginning of the directory.
•
FTP User Name for Deploying Content – Enter a user name for accessing the FTP server(s) that will
manage course content. This is the account that the Content Manager will use to access any content
Chapter 7: Installing the LMS Server Application Files 25
deployment servers that want content transferred to them via FTP. Any content deployment server
(defined in a Delivery Server screen) that will use FTP must create an account with the specified FTP
User Name / Password for the Content Manager. This is a global setting used when defining the FTP
servers to deploy the content to the content servers. Since it is a global value, all content servers must be
setup with the same FTP username and password.
•
FTP Password for Deploying Content – Enter the password associated with the user name used for
accessing the FTP server(s) that will manage course content. This is a global setting used when defining
the FTP servers to deploy the content to the content servers. Since it is a global value, all content servers
must be setup with the same FTP username and password
•
Notification E-mail Format – Select the e-mail format that will be used for notifying you of course
package FTP transfers.
19. Click Next to continue. You are now shown the Destination screen.
Select the installation destination and complete the installation
20. Click Next to install LMS server to the default directory or click Browse to select and install to a different
directory.
21. Before the installation begins you are shown a Summary screen displaying all of your selected installation
options.
22. Click Next to install the LMS Server software as specified by your selected options. A Progress screen will
let you monitor the progress being made while LMS installs.
23. Enter the appropriate information in the product Registration screen as the installation completes. When the
install is complete and successful you are shown a Completed screen.
24. Click Finish to exit the Installer.
26 IBM Lotus LMS Release 1 Installation Guide
Note: If you wish to change installation settings after initially installing LMS you can do so by running the Updater,
which is included with the LMS Installer program in the /update directory. This option presents you with the
necessary screens, pre-populated with your original settings data. After you have made the necessary settings
changes, the Updater then creates two update SQL scripts - one for the LMS server (updateLMM.sql) and one for the
Delivery Server (updateDS.sql). These scripts are then run to change the respective databases. The Updater is
described in more detail in Chapter 17: Starting the Applications.
Starting the LMS Server application
For details on starting this application, refer to “Chapter 17 Starting the Applications.”
Chapter 7: Installing the LMS Server Application Files 27
28 IBM Lotus LMS Release 1 Installation Guide
Chapter 8
Installing the LMS Delivery Server (DS) Application Files
Before deploying the complete Learning Management System, the Delivery Server files should first be installed on
the Application Server.
Note: If you are installing and deploying the LMS Server and the Delivery Server onto separate WAS servers, refer
also to Chapter 16 Deploying the LMS and DS Components onto Separate WAS Application Servers for further
information.
The important unit of packaging in the LMS 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 LMS and Delivery Servers. The Installer also gives you the option to install additional LMSrelated 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 LMS 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
Install.bat
Installer.exe
AIX
install.sh
AIXInstaller.bin
Linux
install.sh
LinuxInstaller.bin
Sun
install.sh
SolarisInstaller.bin
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.
The following steps explain the Delivery Server file install procedure using the Installer.
Chapter 8: Installing the LMS Delivery Server Application Files 29
Installing the Delivery 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
LMS license agreements are installed in the LMS license subdirectory. Use any text viewer to read or print
them in English or in the language configured on your machine.
Select the LMS features to install
6.
At the Features Screen, select the Delivery Server. The information you enter in the screens that follow
is collected and written to a settings_init_ds.sql file under the ds 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 LMS 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. An example
setting would be: o=ibm
•
LDAP User ID – Enter the user ID for authenticating the LMS server to the LDAP provider. An example
setting would be: cn=ldap.
•
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.
30 IBM Lotus LMS Release 1 Installation Guide
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 LMS Server settings
13. Enter the following LMS Server Settings for your LMS configuration:
•
Base URL – Enter the base URL for accessing the LMS Server. An example setting would be:
http://lms.acme.com/lms-lmm.
•
Description – this is an optional text field to provide additional information about the LMS Server.
•
User Name – Enter a user name for the LMS Server. This will be used for authenticating the LMS server
when it communicates with the Delivery Server. The user name provided here must be identical to the
user name that was provided in the same install screen during the installation of the LMS Server
•
Password – Enter the password to be used for accessing the LMS Server. This will be used for
authenticating the LMS server when it communicates with the Delivery Server. The password provided
here must be identical to the password that was provided in the same install-screen during the
installation of the LMS Server.
Chapter 8: Installing the LMS Delivery Server Application Files 31
14. Click Next to continue after you have entered all of the settings. You are now shown the Delivery Server
Definition screen. Use this screen to enter all the necessary information for accessing the Delivery
Server.
Select the Delivery Server settings
15. Enter the following Delivery Server Settings for your server configuration. These settings provide the basic
server definition information for LMS. All of these fields except for Description must contain a value.
•
Server ID – Enter your server ID. This is a unique name that you will use to refer to this Delivery
Server later (deploying an offering, etc.). An example setting would be: ds1.
•
Base URL – Enter the base URL you wish for the Delivery Server. An example setting would be:
http://ds1.acme.com/lms-ds.
•
Description – this is an optional text field to provide additional information about the Delivery Server.
•
Delivery Server User Name – Enter a user name for this Delivery Server. This will used for
authenticating the Delivery Server when it communicates with the LMS Server. The user name and
password are arbitrary: they don’t need to identify an actual user in your LDAP directory.
•
Delivery Server Password – Enter a password for this Delivery Server. This will used for authenticating
the Delivery Server when it communicates with the LMS Server. The user name and password are
arbitrary: they don’t need to identify an actual user in your LDAP directory.
32 IBM Lotus LMS Release 1 Installation Guide
16. Click Next to continue. You are now shown the Web Server Settings screen.
Select the Web Server settings
17. Enter the following Web Server Settings for your server configuration. These settings provide the basic
information about the Web Server used for deploying course content. All of these fields except for
Description must contain a value.
•
URL of Deployed Content – Enter the URL where the Delivery Server looks for content when it launches
a course. There may be multiple content deployment servers (clustered) but this is the single URL that is
used to access them. An example setting would be: http:/contentserver.acme.com/content.
Note: You need to create the directory in which to place deployed content, as the application will not do
this for you. By default, the application will look for a subdirectory in the HTTP server’s htdocs
subdirectory for the installed language (in the present example,
IBMHTTPServer\htdocs\en_US\content).
•
Tracking URL – Enter the URL to the tracking servlet on the Delivery Server. This is pre-populated
based on the "Base URL" you entered previously for the DS and generally will not need to be changed.
Chapter 8: Installing the LMS Delivery Server Application Files 33
18. Click Next to continue. You are now shown the Content Deployment Settings screen. This screen lets you
define the content deployment servers. For any server you can choose between FTP and File system as a
deployment type. If you choose FTP, then the Content Manager will deploy content to the FTP Host you
specify, in the location you specify (if any), using the FTP User Name and Password you defined on the
Content Manager Settings. If you choose File System, then the Content Manager will deploy content to the
absolute file location you specified in the preceding step. The Servers list simply allows you to see the
servers you have created and gives you the ability to remove them.
Select the Content Deployment settings for FTP deployment
19. If you selected FTP from the Deployment Type drop-down list, enter the following settings for each server
that you wish to add to the FTP server list on the right. Selecting this option means that LMS will locate an
FTP server for deployed content. If you selected File System as the type go to the next section.
•
Location for Deployed Content – Enter the URL that Indicates where on the FTP host the content is
stored. For example, if you’ve specified IBMHTTPServer\htdocs\en_US\content as your directory for
deployed content, you need to configure the FTP server so that this directory is accessible. If the FTP
server is set up to map that physical directory to the FTP root directory course_content, you would enter
“course_content” as the Location for Deployed Content.
•
FTP Host – Enter the URL of the FTP host where the content is located.
34 IBM Lotus LMS Release 1 Installation Guide
20. After you have entered the settings, click Add to add the server to the server list. Click Remove Server to
remove any server from the list.
21. Add any additional servers using the same procedure.
22. Click Next to continue when you have added all of your servers. You are now shown the System
Administrator E-mail Settings screen. Skip to that section below to continue with the installation
instructions.
Select the Content Deployment settings for file system deployment
23. If you selected File System from the Deployment Type drop-down list, enter the following setting. Selecting
this option means that LMS will search a file path for deployed content.
•
Location for Deployed Content – Enter the file path that indicates where on the server the content is
stored (for example, F:\IBMHttpServer\htdocs\en_US\content).
Note: Because the Content Manager runs on the LMS Server, the location you specify here must be
accessible by the LMS Server.
24. Click Next to continue. You are now shown the System Administrator E-mail Settings screen.
Select the System Administrator E-mail settings
25. Enter the following settings for setting up System Administrator E-mail. The DS will send out system
administration emails when certain events occur. The addresses you enter here let you specify who the emails should go to as well as what address they should be coming from. Both fields are required.
•
E-mail To Address – Enter the address that you want the System Administrator e-mail sent to.
Chapter 8: Installing the LMS Delivery Server Application Files 35
•
E-mail From Address – Enter the address that you displayed as to where the System Administrator email originated from.
26. Click Next to continue. You are now shown the Destination screen.
Select the installation destination and complete the installation
27. Click Next to install the Delivery Server to the default directory or click Browse to select and install to a
different directory.
28. Before the installation begins you are shown a Summary screen displaying all of your selected installation
options.
29. Click Next to install the Delivery Server software as specified by your selected options. A Progress screen
will let you monitor the progress being made while the LMS Delivery Server installs.
30. Enter the appropriate information in the product Registration screen as the installation completes. When the
install is complete and successful you are shown a Completed screen.
31. Click Finish to exit the Installer.
Important: Editing settings files created during installation incorrectly can result in data loss. Most of the needed
settings changes can be made via the LMS Administrator’s Console. Refer to the LMS Administrator’s Guide for
more information on changing settings via the LMS Administrator’s Console. If you wish to change installation
settings after initially installing LMS you can also use the Updater that comes with the LMS Installer program in the
/update directory. This option presents you with the necessary screens, pre-populated with your original settings
data. After you have made the necessary settings changes, the Updater then creates two update SQL scripts - one
for the LMS server (updateLMM.sql) and one for the Delivery Server (updateDS.sql). These scripts are then run to
change the respective databases. The Updater is described in more detail in Chapter 17: Starting the Applications.
36 IBM Lotus LMS Release 1 Installation Guide
Starting the Delivery Server application
For details on starting this application, refer to “Chapter 17 Starting the Applications.”
Chapter 8: Installing the LMS Delivery Server Application Files 37
38 IBM Lotus LMS Release 1 Installation Guide
Chapter 9
Installing and Configuring Database Servers and Schema
The Learning Management System requires a number of different logical database schemas to function. These are
the following:
•
LMM database – this database resides on the LMS server and stores all information about courses, users,
progress, resources, deployment, status, etc. It is used for learning management and reporting.
•
Audit database – this database stores information about all actions taken on the LMS server.
•
DS (Delivery Server) database – this database contains a subset of the information on the LMS server. It has
the information that is required to deliver and track content to learners. It only contains information about
courses that are deployed to an individual delivery server. You can have multiple delivery servers for a
single LMS server. Each Delivery Server will be associated with a unique Delivery Server database - the
database is not shared among several distinct Delivery Servers).
There is an LMM and Audit schema to support LMS on the LMS Server and one schema for each DS database.
To begin, make sure that the desired database server software is installed on all the desired systems. After you have
done that, use your vendor-supplied database utilities to run the SQL scripts supplied with the Learning
Management System product. These SQL scripts create and initialize the needed databases.
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 LMS database on an Oracle system.
Database Creation Overview
To create and initialize the three databases as well as keep them logically separated, perform the following steps:
1.
If you are running Oracle, obtain three separate accounts for your DB system: one each for Audit, LMS, and
Delivery databases. If you are running SQL Server or DB2, you will create three separate databases rather
than a single partitioned database.
2.
Do the following general tasks 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 LMS database account
o
Execute the supplied LMS 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
The procedure for each database platform is basically the same. The major difference is the set of SQL scripts that
are run. As mentioned, there is a specific set of scripts for each database platform.
Be sure to follow your database software’s 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 table spaces. You
may also need to edit the provided database scripts before execution.
For more information on the LMS databases and database schemas, refer to the LMS Administrator’s Guide.
Chapter 9: Installing and configuring Database Servers and Schema 39
DB2 database creation and configuration for LMS: an example
In this DB2 database creation example, the database schemas are logically distinct and can be located on the same
DB2 instance or different instances.
The database can be located on the application server, but for performance and security reasons it is best to have it
on a dedicated database server.
This installation example involves the following
•
copying the database creation scripts to the database server
•
editing the scripts for site specific considerations (for example, file placement and size)
•
running the scripts
•
running a script that creates site specific seed data.
Installation Requirements
You must have the following to complete this example procedure successfully
•
An installed and running DB2 instance.
Note: Refer to http://www-3.ibm.com/cgibin/db2www/data/db2/udb/winos2unix/support/v7pubs.d2w/en_main for more information DB2 and how
to install it.
•
Unicode codeset. For multilingual support, a unicode (UTF-8) codeset must be used for database creation.
An example script is supplied with the product. Note: You create a database for each schema with DB2. See
the example below for more information.
•
Sufficient disk space and memory. Refer to your DB2 documentation for these requirements.
Before you begin
•
If you are installing on a system that currently has LMS databases, you must either back up and drop those
databases OR edit the supplied scripts to provide new database names.
•
You must be running JDBC 2.0 or higher.
•
UNIX USERS: Before running scripts in a UNIX environment, make sure that the “execute” permission is set.
•
SOLARIS USERS: Before installing the DB2 for Solaris product using the DB2Setup Utility or the DB2_install
and PKGADD commands, you may have to update your system's kernel configuration parameters. The
following lines should be added to the file, /etc/system. You must reboot your machine after updating
any kernel configuration parameters:
set msgsys:msginfo_msgmax=0xFFFF
set msgsys:msginfo_msgmnb=0xFFFF
set msgsys:msginfo_msgmap=0x102
set msgsys:msginfo_msgmni=0xFF
set msgsys:msginfo_msgssz=0x10
set msgsys:msginfo_msgtql=0x400
set shmsys:shminfo_shmmax=0x20000000
40 IBM Lotus LMS Release 1 Installation Guide
set shmsys:shminfo_shmseg=0x32
set shmsys:shminfo_shmmni=0x12C
set semsys:seminfo_semmni=0x400
set semsys:seminfo_semmap=0x400
set semsys:seminfo_semmns=0x800
set semsys:seminfo_semmnu=0x800
set semsys:seminfo_semume=0x32
The settings can be verified with these commands:
# ipcs –a
# sysdef | egrep MSG\|SEM\|SHM
This information is also available in the DB2 knowledge base at: http://www-3.ibm.com/cgibin/db2www/data/db2/udb/winos2unix/support/document.d2w/report?fn=db2v7ixdb2ix31.htm#HDR
UPDATE_SOLARIS_KERNEL.
•
LINUX USERS: Running DB2 on a Linux 2.4 server requires changes to the Linux kernel parameters.
Recompile the kernel source as explained below before you install DB2 on the server.
•
Change the msgmni parameter to 256 with the following command:
echo 256 > /proc/sys/kernel/msgmni
This resets the maximum number of SYSV IPC message queues from the default of 16 to 256.
•
Increase SEMMNI from 128 to 2048.
This specifies the maximum number of semaphore IDs allowed in the kernel; the upper limit for this
value is 32768.
•
Increase SEMMSL from 250 to 500.
This specifies the maximum number of semaphores per sem ID; the upper limit for this value is 8000.
•
Increase SEMOPM from 32 to 256.
This specifies the maximum number of operations allowed per semop() call; the upper limit for this value
is 1000.
•
Increase the number of open files using the command:
echo 32768 > /proc/sys/fs/file-max
This specifies the maximum number of open files, system-wide, to 32K.
Chapter 9: Installing and configuring Database Servers and Schema 41
Database creation details
The following procedures provide detailed instructions on installing and creating the necessary DB2 databases for
use with LMS:
Creating an Audit database
1.
Copy the script files to the database server. The files required are: cr_db2db_audit.bat (for Windows) or
cr_db2db_audit.sh (for UNIX) and audit_db2.sql.
Note: The default location that the Installer places these files is \Program Files\IBM\lms\scripts. However
if you plan to run the scripts from a DB2 command window, \Program Files\SQLLIB\bin is a more
convenient location.
Note: When UNIX shell scripts are copied, they may need to be made executable by using the following
command: chmod +x *.sh
Note: When running the .bat files to create the Audit, LMM, and DS databases, you can edit each .bat file to
run all of the other DB scripts automatically. This is done by removing the REM comments from within the
file. Each of the 3 batch files allows this.
2.
Log into the DB2 server using the DB2 administrator account. The database creation must happen on the
actual database server. The script cannot be run from a database client machine. The cr_db2db_audit.bat
(Windows) or cr_db2db_audit.sh (UNIX) scripts create a unicode. Your database administrator should
review and edit this file for your environment.
3.
If desired, edit the cr_db2db_audit.bat or cr_db2db_audit.sh file. Changes that might have to be made
include specifying multiple database files, increasing file size, and increasing bufferpool size.
4.
Open a DB2 command window and run the cr_db2db_audit.bat or cr_db2db_audit.sh file. For example, in
Windows use the following command: cr_db2db_audit.bat > audit_db.log. For example, in UNIX
use the following command: ./cr_db2db_audit.sh > audit_db.log. This step creates a database
named “lsaudit”, and creates the buffer pools required for any LMS schema.
5.
If desired, edit the audit_db2.sql script.
6.
From a DB2 command window, run the script with the following command: db2 -tvf audit_db2.sql
> audit_schema.log.
7.
From the DB2 command window, run the Audit seed data script db2 -tvf audit_data.sql
Creating the LMM database
1.
Copy the script files to the database server. The files required are: cr_db2db_lmm.bat (for Windows) or
cr_db2db_lmm.sh (for UNIX) and lmm_db2.sql.
Note: When UNIX shell scripts are copied, they may need to be made executable by using the following
command: chmod +x *.sh
2.
Log into the DB2 server using the DB2 administrator account. Database creation must happen on the actual
database server. This script cannot be run from a database client machine.
3.
If desired, edit the cr_db2db_lmm.bat or cr_db2db_lmm.sh file. Changes that might have to be made
include specifying multiple database files, increasing file size, and increasing bufferpool size - temporary
and database tablespaces with a 16K blocksize, and bufferpools with a 16K blocksize. Your database
administrator should review and edit this file for your environment.
4.
Open an DB2 command window and run the cr_db2db_lmm.bat or cr_db2db_lmm.sh file. For example:
cr_db2db_lmm.bat > lms_db.log. This creates a database named lmm, and creates the buffer pools
required for any LMS schema.
42 IBM Lotus LMS Release 1 Installation Guide
5.
If desired, edit the lmm_db2.sql script for file size and placement. From a DB2 command window, run the
script with the following command: db2 -tvf lmm_db2.sql > lms_schema.log
6.
From the DB2 command window run the seed data scripts. For example: db2 -tvf
permission_data.sql AND db2 -tvf settings_init.sql.
Creating the DS database(s)
1.
Copy the script files to the database server. The files required are: cr_db2db_ds.bat (for Windows) or
cr_db2db_ds.sh (for UNIX) and ds_db2.sql.
Note: When UNIX shell scripts are copied, they may need to be made executable by using the following
command: chmod +x *.sh
2.
Log into the DB2 server using the DB2 administrator account. Database creation must happen on the actual
database server. The script cannot be run from a database client machine.
3.
If desired, edit the cr_db2db_ds.bat or cr_db2db_ds.sh file. Changes that might have to be made include
specifying multiple database files, increasing file size, and increasing bufferpool size - temporary and
database tablespaces with a 16K blocksize, and bufferpools with a 16K blocksize. Your database
administrator should review and edit this file for your environment.
4.
Open a DB2 command window and run the cr_db2db_ds.bat or cr_db2db_ds.sh file. For example:
cr_db2db_ds.bat > ds_db.log. This creates a database named ds, and creates the buffer pools
required for any LMS schema.
5.
If desired, edit the ds_db2.sql script for file size and placement. From a DB2 command window, run the
script with the following command db2 -tvf ds_db2.sql > ds_schema.log.
6.
From the DB2 command window, run the DS seed data script. For example: db2 –tvf
settings_init_ds.sql.
Connecting the DB2 client to a remote database
In order to run applications using remote DB2, you must do the following:
•
Install the DB2 client on the same machine where the WebSphere Application Server (WAS) is installed (see
“Chapter 6 Installing the WebSphere Core” for more information).
•
Verify the DB2 client (UNIX only).
•
Add the remote databases to the DB2 client’s catalog.
•
Modify WAS environment to use DB2 drivers.
Installing the DB2 client
Use the following instructions to install the DB2 client for AIX:
1.
Refer to the IBM DB2 Universal Database for Unix Quick Beginnings for requirements and change the kernel
parameters as needed.
2.
If DB2 has not been installed run db2setup from the directory where DB2 is located and install the
Administration client. If DB2 is already installed run /usr/lpp/db2_07_01/install/db2setup.
3.
Select the “To create a DB2 instance” option, Admin Server and click Enter.
4.
Select the “To create a DB2 instance” option. A panel for db2inst1 user is presented.
5.
Create a password for db2inst1.
6.
Select OK. The installation may take up to 15 minutes. When installation has completed a notice window
informs you whether the installation was successful.
Chapter 9: Installing and configuring Database Servers and Schema 43
7.
Highlight OK when finished and click Enter.
8.
If errors are found check the DB2 error log on /tmp.
Use the following instructions to install the DB2 client for Windows:
1.
From CD ROM, run setup.exe
2.
Select Administration Client
3.
Select the default values.
Verify the DB2 client (UNIX only)
1.
Check the DB2 instance profile.
2.
Login as db2inst1
3.
Verify that .profile has the following content. If it is not there, add it to the client:
if [ -f
.
/home/db2inst1/sqllib/db2profile ]; then
/home/db2inst1/sqllib/db2profile
fi
4.
Update the root environment file by logging in as the root
5.
Add the following to .profile:
# Set up DB2 environment for root user.
if [ -f /home/db2inst1/sqllib/db2profile ]; then
. /home/db2inst1/sqllib/db2profile
fi
6. Log out
Configure JDBC 2.0
Although WebSphere requires JDBC 2.0 drivers for its JDBC data sources, DB2 uses JDBC 1.0 by default. You must
configure DB2 to use its supplied JDBC 2.0 drivers in order for WebSphere to connect to DB2 databases using JDBC.
On Windows systems:
1.
Stop any running DB2 processes.
2.
Open a command prompt and navigate to the …\sqllib\java12 directory.
3.
Execute the file jdbc2.bat.
4.
You can now restart DB2 processes.
On UNIX systems:
1.
Log in as the DB2 instance owner (for example, db2inst1).
2.
Type
cd $HOME/sqllib
3.
Add the following line to the file userprofile:
44 IBM Lotus LMS Release 1 Installation Guide
. /$DB2_INSTALL_PATH/java12/usejdbc2
where /$DB2_INSTALL_PATH is the actual path where DB2 is installed on the machine, NOT an
environment variable.
Note: You should update each user account profile for your database system with the
.$HOME/sqllib/java12/usejdbc2 command.
4.
Save your changes to the file.
5.
Stop any running DB2 processes.
6.
Log out and log back in.
7.
You can now restart DB2 processes.
Catalog the remote databases
Use the following instructions for AIX:
1.
Catalog a TCP/IP node.
2.
Login as db2inst1.
3.
Run the startup script INSTHOME/sqllib/db2profile.
4.
Catalog the node as follows
db2 catalog tcpip node db2node remote serverhost server port_number
5.
Catalog the database as follows:
db2 catalog database database_name as database_alias at node node_name
6.
Repeat for this procedure for the DS and Audit databases.
7.
Test the client-to-server communication by doing the following:
•
Connect to remote databases as follows:
db2 connect to database_alias user userid using password
•
Try the following command:
Select tabname from syscat.tables
Use the following instructions for Windows configurations:
1.
Start Programs-IBM DB2-Client Configuration Assistant
2.
Click Add.
3.
Select Manually configure a connection to a database and click Next.
4.
Select TCP/IP protocol. Click Next.
5.
Enter the Hostname.
6.
Enter the Port number.
7.
Click Next.
8.
Enter the Database name (for example, LMS)
9.
Enter the Database alias (for example, LMS2)
10. Click Next
11. Unselect Register this database for ODBC and click Next.
12. Click Next on Step for Add Database Wizard
Chapter 9: Installing and configuring Database Servers and Schema 45
13. Check Configure security options and click Next.
14. Click Finish and test your connection.
15. Repeat for this procedure for the DS and Audit databases.
Oracle database creation for LMS
In this example, LMS requires several distinct schemas to operate. There is an LMM and Audit schema to support
LMM on the LMS Server and one schema for each DS database.
These schemas are logically distinct, and can be located on the same Oracle instance - or different instances. The
database can be located on the application server but for performance and security reasons is usually on a dedicated
database server. This installation involves the following
•
editing the scripts for site specific considerations (for example, file placement and size)
•
running the scripts
•
running scripts that create site-specific seed data (these are called from the schema creation scripts).
Installation requirements
•
Client and server should have the same version of Oracle. There are known problems running an Oracle 8i
client (JDBC driver) against an Oracle 9i RDBMS.
•
Installed Oracle software.
•
Unicode codeset. For multilingual support, a unicode (UTF-8) codeset must be used for database creation.
An example database creation script is included.
•
Sufficient disk space and memory
Database creation details
Oracle instance database creation can be done during the Oracle software GUI installation. Specify the UTF-8
character set during the installation.
If you want to create a database outside of the GUI, example scripts cr_oradb_8i.sql or cr_oradb_9i.sql can be
edited and run to create an Oracle 8i or Oracle 9i database.
Use the following procedures to create the Oracle databases.
Creating an LMS schema
1.
Create a user to be the database owner. You can do this by editing the cr_oraown_lmm.sql script and then
running it. (The script actually creates two users: lmm, which designates the database owner, and lmm_app,
which you can ignore.) To run the script from the sqlplus command line, type the following:
sqlplus system/<password>@<database> @cr_oraown_lmm.sql
2.
Run the schema creation script for the LMS owner account created in the previous step as follows. This
script will also call the seed data script.
sqlplus lmm/[email protected]<database> @lmm_oracle.sql
Creating an Audit schema
1.
Create a user to be the database owner. You can do this by editing the cr_oraown_aud.sql script and then
running it. . (The script actually creates two users: lmm, which designates the database owner, and
lmm_app, which you can ignore.) To run the script from the sqlplus command line, type the following:
46 IBM Lotus LMS Release 1 Installation Guide
sqlplus system/<password>@<database> @cr_oraown_aud.sql
2.
Run the schema creation script for the LMS owner account created in the previous step. This script will also
call the seed data script.
sqlplus aud/[email protected]<database> @audit_oracle.sql
Creating the DS schema(s)
1.
Create a user to be the database owner. You can do this by editing the cr_oraown_ds.sql script for file and
then running it. . (The script actually creates two users: lmm, which designates the database owner, and
lmm_app, which you can ignore.) To run the script from command line sqlplus, type:
sqlplus system/<password>@<database> @cr_oraown_ds.sql
2.
Run the schema creation script for the LMS owner account created in the previous step.
sqlplus ds/[email protected]<database> @ds_oracle.sql
JDBC driver information
Make sure that you install the same version of Oracle client software on the application server as that which was
installed on the database server (for example, 9i database = 9i client). This will install Oracle’s thin JDBC driver,
which is used in the examples for configuring WAS.
Chapter 9: Installing and configuring Database Servers and Schema 47
MS SQL Server database creation for LMS
There is an LMS and Audit schema to support LMS on the LMS Server and one schema for each DS database. These
databases are logically distinct, and can be located on the same SQL Server instance, or different instances.
The database can be located on the application server, but for performance and security reasons are usually will on a
dedicated database server. This installation involves the following
•
editing the scripts for site specific considerations (for example, file placement and size)
•
running the scripts
•
running a script that creates site specific seed data.
Installation requirements
•
Installed and running MS SQL Server instance.
•
MS SQL Server client installed on the machine from which Install is run.
•
Sufficient disk space and memory
Database creation details
Use the following procedure for creating the databases. Observe the following when running the scripts from the
command line:
•
The “-S” server name option can be omitted if the script is being run on the database server itself.
•
The name that you will give for the server is the server alias you created with the “client network utility”
•
The “-e” option should be omitted unless you are debugging installation problems.
•
If you have DB2 installed, you may need to rename the isql.bat file in the DB2 directory to isqldb2.bat, in
order to prevent conflicts.
Creating an Audit database
•
If desired, have the Database Administrator edit the cr_mssqldb_audit.sql script for the correct file size and
placement.
•
From a DOS command line, Run the scripts with the commands:
C:>isql -S <server_name> -U sa -i cr_mssqldb_audit.sql > auditdb.log
C:>isql -S <server_name> -d <audit_db> -U sa [-e] -i audit_mssql.sql >
audit.log
C:>isql -S <server_name> -d <audit_db> -U sa -i audit_data.sql > auditseed.log
Creating an LMS database
•
If desired, have the Database Administrator edit the cr_mssqldb_lmm.sql script for the correct file size and
placement.
•
From a command window, run the scripts with the commands:
C:>isql -S <server_name> -U sa -i cr_mssqldb_lmm.sql > lmmdb.log
C:>isql -S <server_name> -d lmm_db -U sa [-e] -i lmm_mssql.sql > lmm.log
C:>isql -S <server_name> -d lmm_db -U sa -i permission_data.sql
C:>isql -S <server_name> -d lmm_db -U sa -i settings_init.sql
48 IBM Lotus LMS Release 1 Installation Guide
Creating a DS database(s)
•
If desired, have the Database Administrator edit the cr_mssqldb_ds.sql script for the correct file size and
placement.
•
From a command window, run the scripts with the commands:
C:>isql -S <server_name> -U sa -i cr_mssqldb_ds.sql > dsdb.log
C:>isql -S <server_name> -d ds_db -U sa [-e] -i ds_mssql.sql > ds.log
C:>isql -S <server_name> -d ds_db -U sa [-e] -i settings_init_ds.sql
•
Repeat these steps for each database instance that requires an delivery server database
JDBC Driver information
If you need to get copies of these drivers go to http://msdn.microsoft.com/downloads/.
Additional information about running scripts in different environments
LMS provides you with a variety of scripts for creating LMS databases in a variety of DBMS and OS environments.
The following are some guidelines to keep in mind when running these scripts:
•
To meet the need for UNIX script files for DB2 that accomplish the same thing that the provided DB2 DOS
batch files do, ".sh" scripts have been provided. There is one script for each database. These files should be
read and edited before executing them.
•
Both the DOS and UNIX scripts have comments in them to provide some instruction in running and editing
them. Depending on how a script was installed on the DB machine, you may need to make it executable (for
example, by using the UNIX command chmod +x *.sh) and then run it ( ./cr_db2db_lmm.sh)
•
All databases can also be built by running one script. The following points present information on how this
can be done:
•
DB2 users: Commands for creating schemas and populating seed data are added to the ".sh" and ".bat"
scripts, but are commented out. System administrators can uncomment the scripts and run the .sh or .bat
script to build the whole database. On the other hand, you can still run the commands as described
earlier in this chapter while using the remarked commands as documentation of what is needed to run
all of the scripts manually.
•
Oracle users: Schema creating scripts are provided that call seed data scripts (this has already been
explained earlier in this chapter)
•
SQLServer users: The run_mssql_*.bat scripts have been provided. These scripts run all commands to
create an SQLServer database, create schema, and run seed data scripts. These are written to run as "sa"
or sysadmin, but can be edited to work for their environment. The batch file assumes that it is running
on the database server and creates the directory that the database files will be put into. As with every
other script, you should edit the script if these assumptions are not correct for your environment.
Chapter 9: Installing and configuring Database Servers and Schema 49
50 IBM Lotus LMS Release 1 Installation Guide
Chapter 10
Installing the Network Deployment (ND) Module
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 install the Network Deployment module. The Network Deployment (ND)
module configures and controls multi-server WAS installations. If the intent is to deploy Learning Management
System on a cluster of servers for capacity and high availability, then ND must be installed to manage the cluster.
The ND module can be installed on a node where WAS Core has been installed. The following instructions explain
how to install ND
1.
Obtain the ND software from your LMS software package.
2.
Unzip the file in a temporary directory.
3.
Run the LaunchPad (launchPad.bat for Windows, launchPad.sh on UNIX).
Note: Before running .sh files in a UNIX environment, make sure that the “execute” permission is set.
4.
During installation, accept all default values except for the following:
•
Deselect the Embedded Messaging install.
•
Windows users, drop “\Program Files” from the path.
5.
The installation creates the WebSphere/DeploymentManager directory. The DeploymentManager
directory is similar to AppServer directory.
6.
Stop any WebSphere servers (identifiable in Windows Task Manager of using ps in UNIX as Java processes
which consume 80-100 MB+ of RAM) that are running.
7.
Start the manager, and wait for the “Open for e-business” message.
8.
9.
•
For Unix use: WebSphere/DeploymentManager /bin/startManager.sh.
•
For Windows 2000 use: Websphere\DeploymentManager\bin\startmanager
Add your existing WAS node. This will add the existing server into the configuration. You can also migrate
applications at the same time. This command is run from the AppServer not the DeploymentManager,
directory:
•
For Unix use: WebSphere/AppServer/bin/addNode.sh nodename
youruser –password yourpassword
•
For Windows 2000 use: WebSphere\AppServer\bin\addNode nodename –includeapps –
username youruser –password yourpassword
–includeapps –username
Check for error messages.
10. Run startNode, wait for message “open for e-business”
•
For Unix use: WebSphere/AppServer/bin/startNode.sh
•
For Windows 2000 use: WebSphere\AppServer\bin\startNode
11. Start your browser and log into your admin console: http://hostname:9090/admin. At this point
security is not enabled.
12. 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
Chapter 10: Installing the Network Deployment (ND) module 51
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.
13. Enable SSO by doing the following:
•
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)
14. Enable Security (for more information, refer to the “Enable WAS Global Security” section of Chapter 13
Configuring WebSphere Application Server Security)
15. 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
16. Start the servers by first starting the manager then starting the nodes.
17. Once security is enabled, you will have to provide the proper credentials when stopping the node or the
manager.
18. If you need to disable security, do it in security.xml located in
DeploymentManager/config/cells/hostNetwork.
19. 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.
20. Edit the file and change the references from DeploymentManager to AppServer.
21. Restart the Apache server.
52 IBM Lotus LMS Release 1 Installation Guide
The following provides a graphical representation of the WAS nodes, servers, and applications when WAS Core and
Network Deployment (ND) are deployed on the same machine:
Single Physical Host
WebSphere Node: $Hostname
WebSphere Node: $HostnameManager
WebSphere Application Server process:
LMS LS Server
WebSphere Application Server process:
dmgr
WebSphere Enterprise Application:
LMS LMS Server
WebSphere Enterprise Application:
adminconsole
WebSphere Application Server process:
LMS DS Server
WebSphere Enterprise Application:
filetransfer
WebSphere Enterprise Application:
LMS Delivery Server
WebSphere Application Server process:
nodeAgent
WebSphere Enterprise Application:
$Hostname
WebSphere Application Server process:
server1*
WebSphere Enterprise Application:
DefaultApplication
*server1 will still be present (but should NOT be started) if
a WAS Base node was migrated to ND after it had already
been started. Server1 will not be present if WAS Base
and ND were installed together -- i.e., Base was never
brought up prior to the deployment of ND.
WebSphere Enterprise Application:
SamplesGallery
Additional guidelines regarding the use of ND
•
Always use the Admin Console to start and stop application servers.
•
Use the Admin Console to stop or restart the Node Agent.
•
You must start the Node agent (from a stopped state) using the command line.
•
The Deployment Manager can only be stopped and started using the command line.
•
Any time you make changes that require all servers to be restarted (for example, cell-wide changes, such as
security configuration), the following order MUST be observed:
1.
Save the change you have made as you would any change made in the Admin Console.
2.
Synchronize the nodes and wait for synchronization to complete. Navigate in the Admin Console
and come back to the “Nodes” screen to see if the node status is “Synchronized.
3.
Stop any running application servers using the Admin Console.
4.
Stop the Node using the Admin Console.
5.
Logout of the Admin Console and close its browser window.
6.
Stop the Deployment Manager.
7.
Start the Deployment Manager.
8.
Wait until the Manager has started (the “open for e-business” message)
9.
Start the Node Agent.
Chapter 10: Installing the Network Deployment (ND) module 53
54 IBM Lotus LMS Release 1 Installation Guide
Chapter 11
Configuring JDBC Data Sources
After the WebSphere Application Server (WAS) is installed, but before the Learning Management System (LMS)
application is deployed, resources must be configured. There are two types of resources that apply to Learning
Management System
•
environment entries
•
JDBC data sources
Configuration of these resources is done from the WebSphere Application Server’s Administrative Console. The
WAS Administrative Console is its administrative interface. To access the WebSphere Application Server
Administrative Console, launch an Internet browser and navigate to http://was_server:9090/admin.
Data source overview
The LMS Server uses two logical databases in its operation. The first is referred to as the default database. This
database stores all core application data. The second is the audit database. This database is required for application
server operation, even if Auditing is disabled. It holds entries that record application operations performed by LMS
users.
The LMS Delivery Server uses its own logical database. It is frequently abbreviated as DS.
In order to access these databases from WAS, the JDBC drivers for the database engine must be installed on the
WAS server machine. In some cases, this will require that a database run-time client be installed. Other times, a
single zip file containing the drivers can simply be copied into the machine’s file system.
LMS requires a JDBC datasource for each of these logical databases. The following information explains how to
define and configure these JDBC data sources.
Chapter 11: Configuring JDBC Data Sources 55
Defining the JDBC provider
The first step is to define the overall JDBC Provider. This corresponds to the specific driver and database vendor. In
the following example, you are shown how to configure a provider named “DB2 JDBC Provider.” This provider is
for the DB2 database server.
1.
Using the WebSphere Application Server’s Admin Console, expand the Resources section in the left-hand
navigation bar and select JDBC Providers.
2.
Click New to begin configuring a new provider. A drop-down list shows all the supported provider types.
3.
Select DB2 JDBC Provider.
56 IBM Lotus LMS Release 1 Installation Guide
4.
Click OK to continue.
5.
At the Configuration - General Properties screen for the JDBC Provider, note the value in the Classpath field
and click OK to continue.
Chapter 11: Configuring JDBC Data Sources 57
The classpath uses an environment variable that must be verified or set. Use the following procedure to do this:
•
From the starting screen of the Admin console, navigate to Environment -Manage WebSphere Variables and
locate the variable referenced by the classpath in the JDBC Providers Configuration screen. In this example,
it is DB2_JDBC_DRIVER_PATH.
•
Make sure the value is set or set the value to the directory that contains the JDBC drivers for your database.
58 IBM Lotus LMS Release 1 Installation Guide
Defining the JDBC data sources
The next step is to define the JDBC data sources. Access to JDBC connections is made via JNDI lookup of a named
data source. These data sources have well-known names that are embedded in the Learning Management System
.ear file. Using the WAS admin console, three data sources must be configured: LMM (Default), LSAUDIT (Audit),
and DS (Delivery). The following steps provide the instructions for completing these tasks. This section describes
the procedure to create data sources and configure DB connections.
Create the J2C Authentication Data Entries
1.
Expand Security on the left panel of the WAS console.
2.
Expand JAAS Configuration
3.
Click J2C Authentication Data
4.
Click New
5.
Enter you data base information. For example:
•
Alias: db_name - This identifier is used to identify the authenticated data entry. When configuring
resource adapters or JDBC data sources, the administrator can specify which authentication data to
choose for the corresponding alias.
•
User ID: your_id - This is the user identity of the intended security domain. For example, if a particular
authentication data entry is intended to be used to open a new connection to DB2, this entry would
contain a DB2 user identity.
•
Password: your_password - This password of the user identity is encoded in the configuration
respository.
6.
Click Apply. This creates an entry like hostnameManager/db_name
7.
Repeat for the other two databases.
Chapter 11: Configuring JDBC Data Sources 59
Create the data sources
1.
Expand Resources on the WAS console left panel.
2.
Click JDBC Providers.
3.
On the right panel, erase the entry on Node.
4.
Click Browse Nodes.
5.
Select Node.
6.
Click Apply. The changes will apply only at the node level.
7.
Click New.
8.
From the JDBC providers drop down, select you database provider (DB2 for this example).
9.
Click OK
10. Click OK. Under JDBC provider you will now have a new entry for your database provider.
11. Click DB JDBC provider.
12. Click on Data Sources at the bottom of the screen. To create the entries each database, do the following:
•
Click New to access the screen to enter the database information.
60 IBM Lotus LMS Release 1 Installation Guide
13. Enter the following information:
•
Name: dbname (for example, lmm, ds, audit)
•
JNDI name: jdbc/dbname
•
Statement Cache Size: 0
•
Component-managed Authentication Alias: $hostnameManager/db_name
•
Container -managed Authentication Alias: $hostnameManager/db_name
14. Click Apply.
15. Change the database Max connection pool size by doing the following:
•
Click on dbname
•
Click on Connection Pool at bottom of the screen
•
Set Max Connections to 30
Chapter 11: Configuring JDBC Data Sources 61
•
Click Apply
16. Repeat this procedure for the two remaining databases.
62 IBM Lotus LMS Release 1 Installation Guide
Change the Custom Properties for each data source depending on the database type
1.
Go to Data Sources
2.
Click on the desired db_name
3.
Click on Custom Properties
4.
Depending on the database type you may change the following properties. The entries presented are for
example purposes only.
•
DB2 databases:
•
databaseName: db_name - this is the database alias used when cataloging the remote database. The
following screen shows the custom properties for a DB2 example.
Chapter 11: Configuring JDBC Data Sources 63
•
•
•
5.
The databaseName property has been selected and you are shown the following screen to change this
custom property. This property provides the database alias used when cataloging the remote
database. The value used in the following example for databaseName is “lmm.”
For Oracle databases, you may see the following properties:
•
URL: jdbc:oracle:thin:@server.acme.com:1521:name
•
portNumber: 1521
For MS SQL databases, , you may see the following properties:
•
databaseName: db_name – this is the remote data base name.
•
portNumber: 1433
•
serverName: servername
Repeat this process for the other two databases.
64 IBM Lotus LMS Release 1 Installation Guide
Chapter 12
Configuring Environment Entries
After the WebSphere Application Server (WAS) is installed, but before the Learning Management System (LMS)
application is deployed, resources must be configured. There are two types of resources that apply to Learning
Management System
•
environment entries
•
JDBC data-sources
Configuration of these resources is done from the WebSphere Application Server’s Administrative Console. The
WAS Administrative Console is its administrative interface. To access the WebSphere Application Server
Administrative Console, launch an Internet browser and navigate to http://was_server:9090/admin.
It is recommended that you save your work frequently when working with the WebSphere Application Server’s
Administrative Console. When you make a change, a message box will appear at the top of the right-hand frame,
prompting you to save your changes to the master configuration. Try to do this regularly.
Configuring an environment entry for the log file location
LMS uses an environment entry to configure the file-system path used to store application log files. This section
describes how to set up this environment entry using the WebSphere Application Server’s Admin Console.
1. Create the Resource Environment Provider
a.
Using the WebSphere Application Server’s Admin Console, expand the “Resources” section in the lefthand navigation bar and select “Resource Environment Providers.”
b. Click “New” to begin configuring a new provider.
Chapter 12: Configuring Environment Entries 65
2. Enter the provider information
a.
Enter the name, for example, “LMS Provider,” and an optional description for the provider
b. Click OK. A new provider appears in the list of defined providers.
66 IBM Lotus LMS Release 1 Installation Guide
3. Enter the provider details
a.
Click the name of the newly entered provider to go to the details page of that provider
b. Enter the desired details.
4. Configure the Referenceable
Before environment-entries can be made, a Referenceable must be defined. A Referenceable is a class of object that is
able to handle bindings for specific reference values. A single Referenceable must be defined.
a.
Click Referenceables in the provider details page to see the list of defined Referenceables.
b. Click New to get to the detail page for defining a new Referenceable.
Chapter 12: Configuring Environment Entries 67
c.
For Factory Classname, enter com.lotus.elearn.naming.StringObjectFactory.
d. For Classname, enter java.lang.String.
e.
Click OK.
5. Configure the Resource Environment entries
After the Referenceable has been defined, the specific environment entries need to be defined.
a.
Go back to the Provider Details page.
b. Click Resource Environment Entries. You should see an empty list.
68 IBM Lotus LMS Release 1 Installation Guide
c.
Click New to go to the page to define an entry. Enter LMS_LOG as both the name and JNDI name for the
new entry.
d. Click OK. This will bring you back to the Env-Entries list page. You now need to define properties for
the new entry.
Chapter 12: Configuring Environment Entries 69
e.
Click that link and define a new Custom Property with the name LMS_LOG_PATH . For the value, enter
the name of the directory where the LMS should store application log files, for example, C:\lms_logs.
Note: You need to create this directory by hand as the application won’t do it for you and will not start
properly without it.
f.
Click OK to complete this entry and its properties.
g. Create two additional resource environment entries: LMS_TRUE and LMS_FALSE. These are used to set
the resource environment references HTTPS_LOGIN and HTTPS_APPLICATION when deploying the
LMS and DS .ear files in WAS and are used to enable SSL for login or for the whole application. These
instructions assume that a resource environment provider named LMS Provider already exists:
1.
Go to the Resource Environment Providers page.
2.
Make sure the appserver node is selected and not the DM node.
3.
Click the LMS Provider link.
4.
Click the Resource Env Entries link.
5.
Click New.
6.
Set Name to LMS_TRUE.
7.
Set JNDI Name to LMS_TRUE.
8.
Click OK.
9.
Click LMS_TRUE.
10. Click Custom Properties.
11. Click New.
12. Set Name to value.
70 IBM Lotus LMS Release 1 Installation Guide
13. Set Value to true.
14. Click OK
15. Click the Resource Env Entries link in the trail.
16. Click New.
17. Set Name to LMS_FALSE.
18. Set JNDI Name to LMS_FALSE.
19. Click OK.
20. Click LMS_FALSE.
21. Click Custom Properties.
22. Click New.
23. Set Name to value.
24. Set Value to false.
25. Click OK.
26. Save your work.
Chapter 12: Configuring Environment Entries 71
72 IBM Lotus LMS Release 1 Installation Guide
Chapter 13
Configuring WebSphere Application Server Security
Learning Management System assumes that the WebSphere Application Server (WAS) is configured to use LDAP
authentication. The WAS Administrative Console is used to configure LDAP as the active user registry and to
specify the LDAP settings as part of setting up WAS Security. Before you attempt to do this, your LDAP server
must be installed, running, and populated with the node within the directory tree that is the starting point for all
directory searches—an identitity under this node that is used by the WAS server for security purposes, and an
identity used to bind to the directory.
For example, in the set-up description below, we’ll assume you’ve created an LDAP directory using the IBM
Directory Server V4.1 called “ldapserver.ibm.com” that runs on default port 389 and contains a root node called
“o=ibm”. In addition, the root node contains a security identity with following characteristics:
Distinguished Name:
cn=ldapadmin,o=ibm
Uid:
ldapadmin
Password:
password
Finally, the bind identity (setup during installation of the LDAP directory) has the following characteristics:
Distinguished Name:
cn=root
Password:
password
Security must be configured and enabled after WAS is installed but before the Learning Management System (LMS)
application is deployed. This is done from the WAS Administrative Console; accessed by launching an Internet
browser and navigating to http://was_server:9090/admin (substitute the name of your server for was_server).
Chapter 13: Configuring WebSphere Application Server Security 73
Configure the LDAP directory for use with LMS
The following steps show how to configure WAS security to use an LDAP directory:
1.
1. Launch the WAS Administrative Console and go to Security - User Registries.
2.
2. Click on the LDAP link. The LDAP User Registry page is displayed.
3.
Enter the Server User ID (for example, ldapadmin).
4.
Enter the Server User Password (e.g. password).
5.
Select the Type from the drop-down box (for example, IBM_Directory_Server).
6.
Enter the Host (for example, ldapserver.ibm.com). This should be the name of your LDAP server.
7.
Make sure the LDAP port is correct (for example, 389).
8.
Enter the Base Distinguished Name (for example, o=ibm).
9.
Enter the Bind Distinguished Name (for example, cn=root).
10. Enter the Bind Password (for example, password).
11. Update the remaining settings as needed
74 IBM Lotus LMS Release 1 Installation Guide
12. Click Apply. Note that a Message(s) section appears at the top of the page and indicates that you’ll need to
Save these changes.
13. Click the Advanced LDAP Settings link. You’ll see the Advanced LDAP Settings page.
If your LDAP directory has been customized you may need to change the User Filter, the User ID Map, the
Group Filter or the Group ID Map. Get this information from you LDAP directory administrator and update
the appropriate fields accordingly.
14. Click OK. You’ll return to the LDAP User Registry page. The value in the Type drop-down box may change
if you update any values in the Advanced LDAP Settings page. This is perfectly normal. Do not change the
Type back to its previous value.
15. Click Save in the Message(s) section at the top of the page. You’ll see the Save to Master Configuration page
appear.
16. Click Save.
17. Click OK.
These changes will most likely change the value of the Type field on the LDAP User Registry page to Custom. This
is perfectly normal. Do not change the Type back to its previous value.
Chapter 13: Configuring WebSphere Application Server Security 75
Enable WAS Global Security
1.
Launch the WAS Administrative Console and go to Security – Global Security.
2.
Check the Enabled checkbox and (if it isn’t automatically checked when security is enabled) the Enforce Java
2 Security checkbox.
3.
Assuming that you followed the steps for enabling Single Sign-On (SSO) outlined in “Chapter 10 Installing
the Network Deployment (ND) Module,” the Active Authentication Mechanism field has the value LTPA.
4.
Select LDAP In the Active User Registry drop-down box.
5.
Click OK. At this point the Server User Id and Server User Password you entered in the LDAP User Registry
page are validated. If there is a problem then you’ll get an error and you’ll have to correct it before
proceeding.
6.
Restart the WAS server for the security changes to take effect. You must now provide a username and
password when executing the stopServer script. In addition, you’ll have to specify the Server User Id and
Password when you open the WAS Administrative console.
76 IBM Lotus LMS Release 1 Installation Guide
Chapter 14
Deploying the Learning Management System (LMS) Server
Application
Application deployment refers to the process where an application package has been installed and is then configured
on an application server to create a running instance of that application.
The important unit of packaging in the LMS application 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.
The WebSphere Application Server Admin Console provides a multi-step process for deploying an .ear file and
resolving the needed bindings and settings. This chapter describes the steps for deploying the LMS Server .ear file.
Refer to the Release Notes for complete information regarding browser requirements.
The following steps provide the information on the process of deploying the Learning Management System (LMS)
Server application (one piece of the complete LMS deployment) from an .ear file from the WAS Admin Console.
1. Select the .ear file for deployment
Select “Install New Application” from the left-hand navigation window in WAS Administrative Console.
Use the browse button to select the desired LMS .ear file stored on your file system. Refer to the Release
Notes for the exact name of this file. When finished, click Next to continue.
Chapter 14: Deploying the LMS Server Application 77
2. Prepare for application install
It sometimes takes a few minutes for WAS to read and validate an .ear file. When this has completed, the
“Preparing for application installation” screen is displayed.
You can make selections here that change how the next steps are performed. You should accept the
defaults. When finished, click Next to continue.
78 IBM Lotus LMS Release 1 Installation Guide
3. Provide options to perform the installation
At the next screen, select some options for the application deployment; for example you can pre-compile all
JSPs.
With the exception of the Application Name, accept the defaults.
Caution The Application Name should not include spaces, because the LMS Installer generates a WAS .ear
directory using that name. Even if you want to use the default name “IBM Lotus LMS LMM” as shown
above, you should edit the name and remove all the spaces.
When finished, click Next to continue.
Chapter 14: Deploying the LMS Server Application 79
4. Map resources references to resources
At the following screens, you map the resource references that are specified in the .ear file to actual resources
you configured in WAS.
Check the first entry for the LMS data (jdbc/LMS_Default) and select “jdbc/lmm” from the “Specify existing
Resource JNDI name" drop-down list.”
80 IBM Lotus LMS Release 1 Installation Guide
This list is populated with the names of data source definitions that have been defined and lets you resolve
JDBC data source references. For each data source referenced in the .ear file, an entry is displayed. Clicking
the IBM Lotus LMS checkbox and then specifying select “jdbc/lmm” from the “Specify existing Resource
JNDI name" drop-down list maps that resource reference to the correct resource. Click Apply when finished.
Check the second entry for the Audit data source (jdbc/LMS_Audit) and select “jdbc/audit” from the
“Specify existing Resource JNDI name" drop-down list. Click Apply when finished.
When finished, click Next to continue.
5. Map resource env (environment) entry references to resources
After the data source references have been resolved, you must do the same for all environment entries.
If you know the JNDI name of the environment entry already, you may enter it directly. If not, click the
“Apply Multiple Mappings” control to get a dropdown of available entries. Map LMS_LOG_PATH to
LMS_LOG, HTTPS_LOGIN to LMS_FALSE, and HTTPS_APPLICATION to LMS_FALSE. When you have
finished, click Next to continue.
Chapter 14: Deploying the LMS Server Application 81
6. Map virtual hosts to web modules
In this step, you map web modules to different virtual hosts. The application server can run multiple,
separate servers. For example, by default, the server runs the admin host on port 9090 and the default host
on port 9080. Accept the default value. When finished, click Next to continue.
7. Map modules to application servers
It is possible to have several application servers defined for a given host. At this point you can define which
of the multiple servers (if any) you want to map the web modules to. Accept the defaults and click Next to
continue.
82 IBM Lotus LMS Release 1 Installation Guide
8. Map security roles to users/groups
In this step, map references to security roles in the application to specific user registry groups or application
server special subjects. The .ear file already contains a default security binding. Accept the default value
(ALL_AUTHENTICATED) by clicking Next to continue.
Chapter 14: Deploying the LMS Server Application 83
9. View summary and confirmation information
When you have completed these steps, you are shown a summary of the options you have selected.
Review them and if they are correct, click Finish to continue.
84 IBM Lotus LMS Release 1 Installation Guide
The application performs some final processing to finalize all the selections. Status information on this
process is printed to the console.
When complete processing is complete, you are presented with a link to save the new configuration. It is
recommended you perform the Save at this time.
10. Starting the application and regenerating web server plug-in
At this point, refer to “Chapter 17 Starting the Applications” for information on starting your LMS Server
application.
Chapter 14: Deploying the LMS Server Application 85
86 IBM Lotus LMS Release 1 Installation Guide
Chapter 15
Deploying the Delivery Server (DS) Application
For complete information on the process of deploying the Delivery Server application portion of the LMS
installation, follow the same steps outlined in “Chapter 14 Deploying the Learning Management System (LMS)
Server application.”
The only difference for deploying the Delivery Server is in” Step 4. Map resources references to resources.” In this
step you should check the entry for the IBM Lotus LMS Delivery Server data (jdbc/LMS_Delivery_Default) and
select “jdbc/ds” from the “Specify existing Resource JNDI name" drop-down list.
Clicking the IBM Lotus LMS Delivery Server checkbox and then specifying select “jdbc/ds” from the “Specify
existing Resource JNDI name" drop-down list maps that DS resource reference to the correct DS resource. Click
Apply when finished.
Starting the application and regenerating web server plug-in
At this point, refer to “Chapter 17 Starting the Applications” for information on starting your Delivery Server
application and regenerating the web server plug-in.
Chapter 15: Deploying the Delivery Server (DS) Application 87
88 IBM Lotus LMS Release 1 Installation Guide
Chapter 16
Deploying the LMS and DS Components onto Separate
WAS Application Servers
By default, new Application Servers created in the WAS Admin Console generate their own unique HTTP ports.
WAS assigns ports incrementally, beginning with port 9080, which is usually assigned to the Application Server
server1. Subsequent servers will be assigned incrementally higher ports. Frequently, the LMS Server’s Application
Server uses port 9081 and the Delivery Server’s Application Server uses port 9082. You should verify the ports used
by the different applications servers. Use the following procedure to do so:
1.
In the WAS Admin Console, navigate to Servers and click on Application Servers.
2.
Click on the application server you are investigating (for example, lmsServer)
3.
In that server’s screen, click on Web Container.
4.
In the Web Container screen, click on HTTP Transports.
5.
Note the port number that has SSL Enabled set to False. This port should be 908n. Write the port number
down.
In order for the HTTP plug-in and for WAS to function with all the port numbers, they must be added to the virtual
host in use by LMS WAS Application Servers. To enable this, use the following procedure:
1.
In the WAS Admin Console, navigate to Environment and click on Virtual Hosts.
2.
Click on the “default_host” virtual host.
3.
In the “default_host” screen, click on Host Aliases.
4.
Add a Host Alias for each additional port by doing the following
a.
Click the “Add” button
b. Set the hostname to “*” (asterisk, do NOT enter the quotes in the “Hostname” field)
c.
Set the Port to one of your additional Application Server ports
d. Save your changes
5.
Regenerate the HTTP plug-in.
6.
Edit and copy the HTTP plug-in configuration file plugin-cfg.xml. For more information, refer to “Chapter
10 Installing the Network Deployment (ND) Module.”
7.
Stop and restart the application servers whose ports you just added to default_host.
To help ensure the successful deployment of both the LMS and Delivery Servers, you must also set an additional
WebSphere variable, ConnectionIOTimeOut, must be set for both the LMS and Delivery Server’s Application Servers.
To set it, perform the following steps for each application server:
Chapter 16: Deploying the LMS and DS Components onto Separate WAS Application Servers 89
1.
In the WAS Admin Console, navigate to Servers and click on Application Servers.
2.
Click on the Application Server.
3.
In the Application Server’s screen, click Web Container.
4.
In the Web Container screen, click on HTTP Transports.
5.
In the HTTP Transports screen, click on the asterisk associated with the port for which “SSL enabled” is set
to False.
6.
In the port’s screen, click on Custom Properties.
7.
Click the New button.
8.
Set the name to ConnectionIOTimeOut and the value to 1000.
90 IBM Lotus LMS Release 1 Installation Guide
Chapter 17
Starting the Applications
At this point, the Learning Management System applications are ready to start. The WAS admin console is used to
start these applications. Both the WAS logs and Learning Management System logs should be examined to verify
correct initialization. At this point, the applications can be accessed via browser. The administrator identified
during installation must login to the LMS application and roster users, provide for importing content, and otherwise
perform the tasks needed for actual learning to be delivered to users. The following information provides more
details on starting the applications.
Starting the LMS Server application
After the LMS server has been installed, the application can be started.
1.
Go to the WAS Enterprise Application selection at the Administrative Console.
2.
Click the Learning Management System LMS Server checkbox.
3.
Click Start. After a short time for startup-processing, the display will update to show the new application
status
4.
Once the application is deployed, click on it in the Applications window.
5.
In the application’s window (for example, the “Learning Management System” window in the current
example), scroll down and click the “View Deployment Descriptor” link. Expand the + sign next to “Web
Modules” and expand the + sign next to the specific Web module for the application.
6.
Make a note of the “Context-root.” Appended to your WAS server’s hostname, this value forms the URL for
your application. For example, if the Context root for your Learning Management System LMS server
application is lms-lmm and you deployed it to a WAS server called xyz.acme.com, the publishable URL for
the Learning Management System is http://xyz.acme.com/lms-lmm (case-sensitive).
7.
To verify that the LMS server is running properly, simply enter http://xyz.acme.com/lms-lmm in a browser.
Starting the Delivery Server application
After the Delivery Server has been installed, the application can be started.
1.
Go to the WAS Enterprise Application selection at the Administrative Console.
2.
Click the LMS Delivery Server checkbox.
3.
Click Start. After a short time for startup-processing, the display will update to show the new application
status
4.
Once the application is deployed, click on it in the Applications window.
5.
In the application’s window (for example, the “LMS Delivery Server” window in the current example), scroll
down and click the “View Deployment Descriptor” link. Expand the + sign next to “Web Modules” and
expand the + sign next to the specific Web module for the application.
6.
Make a note of the “Context-root.” Appended to your WAS server’s hostname, this value forms the URL for
your application. For example, if the Context root for your LMS Delivery Server application is lms-ds and
you deployed it to a WAS server called xyz.acme.com, the publishable URL for the LMS Delivery Server is
http://xyz.acme.com/lms-ds (case-sensitive).
7.
To verify that the Delivery Server is running properly, you can enter the following URL in a browser:
http://xyz.acme.com/lms-ds/about.ds. This displays the About box.
Chapter 17: Starting the Applications 91
Regenerating the web server plug-in
With J2EE servers such as WebSphere, high-volume deployments (such as LMS) that have static HTTP assets (for
example, .html or .gif files) have them served by a dedicated HTTP server. The application server then is
responsible for serving requests for dynamic pages (such as, servlet or .jsp requests).
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.
In WebSphere, the key step in using this type of configuration is the "Create Plug-in Configuration" command. This
creates the needed configuration files/settings for the HTTP server plug-in that routes requests to the application
server. For all deployed applications to run correctly and for the Application Server to have all of the most recent
information on deployed applications, you must then regenerate the Web sever plug-in after any major changes.
The following steps outline this procedure:
1.
In the WAS Administrative Console, go to Environment-Update Web Server Plug-in.
2.
Click OK to regenerate the plug-in. A confirmation message will appear indicating that it was successfully
regenerated.
3.
If you don’t want to wait for the HTTP server to poll the plug-in for updates, manually restart the HTTP
server with one of the following commands:
Windows example: \HTTP_INSTALL_ROOT\Apache –k restart
UNIX example: /HTTP_INSTALL_ROOT/apachectl restart
Running the Updater
If you have a problem starting either the LMS or DS application, it may be because you entered one or more
incorrect settings when you ran the Installer. You can remedy this situation by running the Updater.
The Updater is a batch file (updateSettings.bat for Windows and updateSettings.sh for UNIX) that resides in the
/update directory. When you run updateSettings.bat (or updateSettings.sh), the following screens are displayed,
primed with the settings you entered when you ran the Installer (as described in chapters 7 and 8 above):
1.
LDAP Settings
2.
LMS Server Settings
3.
Content Management Settings
4.
Delivery Server Settings
5.
Web Server Settings
6.
Content Deployment Settings
7.
System Administrator E-mail Settings
When you have finished making your changes, the Updater creates two SQL scripts (updateLMM.sql for the LMS
server, and updateDS.sql for the Delivery Server). When you run these, the respective databases are updated with
the new settings you specified in the Updater. You can then try to start the LMS and DS applications again.
92 IBM Lotus LMS Release 1 Installation Guide
Chapter 18
Post-Installation Tasks
After you have installed LMS, there are other tasks that must be completed to make full use of your installation.
These include the following:
•
Configuring on-line help
•
Adding the Delivery Server to the LMS application
•
Deploying the Offline Learning Client
•
Installing the LMS Authoring Tool
•
Installing the Command Line Import Utility
•
Migrating LearningSpace data.
•
Installing XVFB on UNIX platforms to enable reporting
To complete these tasks, make sure that you have logged into LMS as the Administrator. Refer to the LMS
Administrator’s Guide for more information.
Configuring on-line help
The Learning Management System on-line help is contained in a .war. Refer to the product Release Notes and
README for more information on the correct file name.
To configure this help, create a directory for files in your HTTP Server’s document root (for example,
/usr/IBMHttpServer/htdocs/en_US on an AIX system) to store the help files. Unzip the help .war file into this
directory.
Note: UNIX and AIX users creating directories must have root privileges. Remember also not to use spaces when
creating directory names.
Next, access the LMS start page at http://$LMM_HOSTNAME/$LMM_CONTEXT_ROOT (for example,
http://xyz.acme.com/lms-lmm) and navigate to Settings-LMM General Settings-General tab.
In the URL entry for the help system, enter http://$LMM_HOSTNAME /$HELP_DIR/ (for example,
http://xyz.acme.com/help_dir/) where $HELP_DIR is the help directory created previously within the HTTP
server’s document root.
Adding the Delivery Server to the LMS application
To add the Delivery Server (DS)to the LMS Server application, access the LMS Server start page at http://
$LMM_HOSTNAME /$LMM_CONTEXT_ROOT (for example, http://xyz.acme.com/lms-lmm).
Go to Settings-Delivery Server and click Add.
Enter a name, description, username and password for the DS. The Delivery Server URL is http://
$DS_HOSTNAME/$DS_CONTEXT_ROOT (for example, http://xyz.acme.com/lms-ds).
Click Save.
Chapter 18: Post-Installation Tasks 93
Deploying the Offline Learning Client
The Learning Management System allows students to take courses without being connected to the network. When
working on a course offline, all course prerequisites and navigation features are fully functional for the student.
The Offline Learning Client lets you access the disconnected use feature. To properly deploy the Offline Learning
Client after you have installed and deployed the LMS Server, use the following steps:
1.
Start the LMS Server.
2.
Go to the Settings tab.
3.
Click LMM Server.
4.
Click General Settings.
5.
Enter "duc/OfflineClientWin32.exe" in the URL of Offline Learning Client Software field. This should
correspond to wherever the client software is deployed. If you want to put the Offline Learning Client on
another web server, the URL could point to "http://someotherserver/offlineclient/OfflineClientWin32.exe"
or another similar URL.
6.
Enter the version of the Offline Learning Client that is being deployed in the Version field. The LMS Server
“About" document contains a version number like "1.0 - eu20021122_M12." Enter the “1.0”
7.
Restart the LMS Server if needed.
Installing the LMS Authoring Tool
The Learning Management System provides the option to copy an installable Authoring Tool during product
installation. The Authoring Tool is a course development tool with two separate modes. You use Planner mode to
build a course structure. You use Authoring mode to create course content and assessment pages. The authoring tool
is designed to be used by a course developer working at his or her own workstation. To install the Authoring Tool
after you have copied the files, use the following procedure:
1.
Download Authoring_Tool.zip from the LMS Server to your workstation. This file is installed when you
select Authoring Tools as an option in the Server installation procedures. See the chapters “Installing the
Learning Management System (LMS) Server application files” and “Installing the Delivery Server
application files” for more information.
2.
Unzip the contents of the zip file to your root directory. Important: Maintain the zip file's folder names
during the unzipping process.
3.
Go to the Disk1 folder created during the unzipping process and run setup.exe.
4.
Follow the instructions on screen to complete the installation process.
5.
To start the tool, choose Start - Programs - IBM Lotus LMS Authoring Tool - IBM Lotus LMS Authoring Tool.
If you selected the option for copying an installable Authoring Tool to the LMS server during product installation,
an Authoring Tool Guide was also copied to the server. The guide is provided as a zip file that contains the
Authoring Tool Guide and sample courses. To use the guide, download AuthoringToolGuide.zip to your local
workstation. Extract AuthoringToolGuide.pdf to your workstation and follow the instructions in Chapter 1 for
installing and using the sample courses.
Installing the Command Line Import Utility (CLIMP)
The Learning Management System provides the option to copy an installable Command Line Import Utility during
product installation. The Learning Management System Command Line Import Utility (CLIMP) is a Java
application.
CLIMP allows you to import SCORM 1.2 course package files into LMS, making them available for deployment.
Course package files can contain new courses, or updates to previously-deployed courses. Course packages are
94 IBM Lotus LMS Release 1 Installation Guide
created by content vendors using the LMS Authoring Tool, or by using some other tool that can produce SCORM 1.2
content.
Note: It is not necessary to use CLIMP with the Authoring Tool, since the Authoring Tool provides the same
capabilities to import courses that CLIMP does.
CLIMP can be used to both upload course package files and then import them into LMS or just to import course
packages that are already available on an FTP or file server. After the file has been uploaded, CLIMP initiates the
import operation by sending an HTTP request to Content Manager servlet, which runs on the LMS Server. A single
CLIMP command can process multiple files, although the Content Manager will import those files one at a time.
With CLIMP, you can optionally specify one or more e-mail addresses to receive e-mail notifications about the status
of the import operation. After a new course has been successfully imported, it appears as an unregistered master in
the LMS course master catalog.
You need a Java run-time environment (JRE) installed and on your search path in order to run CLIMP. CLIMP is
built using JDK 1.3 and may not work with other JDK versions. The name of the installed zip file (if you chose to
install Utilities during LMS installation) is climp.zip. To install the utility, use the following procedure:
1.
Create a directory on your local workstation in which to install CLIMP. The climp.zip is installed when you
select Utilities as an option in the Server installation procedures. See the chapters “Installing the Learning
Management System (LMS) Server application files” and “Installing the Delivery Server application files” for
more information.
2.
Unzip the contents of climp.zip into the CLIMP directory.
3. For UNIX only, change the permissions of CLIMP shell script as follows: chmod +x climp
4.
Change your CLASSPATH to include the directory where you installed CLIMP (if it not already in
CLASSPATH).
Migrating LearningSpace data
If you need to migrate information from a previous version of LearningSpace into the new Learning Management
System deployment, consult the documentation for the migration utilities posted to the Web.
To obtain the migration utility and quarterly updates of the LMS documentation, please go to
http://www-1.ibm.com/support/search/index.html and search on Learning Management System Migration
Utility and Quarterly Documentation Updates.
Installing XVFB on UNIX 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.
1.
2.
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.
Download the XVFB file from the following link to a directory on the Linux machine:
ftp://ftp.xfree86.org/pub/XFree86/4.2.0/binaries/Linux-ix86-glibc22/
Chapter 18: Post-Installation Tasks 95
3.
Extract the file with the following commands:
chmod +x extract
mkdir /etc/X11
./extract -C /usr/X11R6 Xvfb
4.
Generate a script file named /etc/init.d/xvfb containing the following, and make it executable:
#!/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
5.
Change the run-level to 3 by doing the following:
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)
#
96 IBM Lotus LMS Release 1 Installation Guide
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.
6.
Create soft link:
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 ).
7.
Restart the server.
8.
Verify that XVFB is running with the following command:
ps -ef | grep Xvfb
9.
Set DISPLAY from the command line using:
DISPLAY=hostname:1.0
export DISPLAY
Previous lines can be added to .bash_profile or whatever profile you're using.
10. Start Servers
Installing XVFB on AIX
For complete instructions for XVFB see the AIXwindows Programming Guide, Appendix E. The X Virtual Frame
Buffer is http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/aixwnpgd/xvfb.htm#xvfb.
1.
Add the following line to /etc/initab:
xvfb:2:respawn:/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :1 > /dev/null
2.
Set DISPLAY by adding the following line to .profile:
DISPLAY=`hostname`:1.0
export DISPLAY
3.
Restart the server machine.
4.
Disable JIT on application server(s).
Determining the correct SSO settings for LMS
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 LMS deployment planning to
allow for the greatest efficiency in logging in users. For further information on LMS and SSO refer to Chapter 5
Managing Users in the IBM Lotus LMS Release 1 Administrator's Guide and the Installing the WebSphere Core
chapter in this guide.
Chapter 18: Post-Installation Tasks 97
98 IBM Lotus LMS Release 1 Installation Guide
Chapter 19
Special Installation Issues
For information on special issues related to this release of LMS, refer to the ReadMe.html and ReleaseNotes.html
files that ship with this version of the product.
Using SSL with the LMS
Use of the Secure Sockets Layer for LMS is supported with Release 1.0a and greater. 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.
Using the Directory Server Web Administration Interface with Linux
The Web Administration interface for Directory Server is not supported on Linux. You can work around this issue
by manually creating the suffix, as follows:
1.
Edit SLAPD32.CONF (default location of SLAPD32.CONF is /etc/slapd32.conf).
2.
Manually add the new suffix below the following line:
ibm-slapdSuffix: cn=localhost
For example:
ibm-slapdSuffix: o=myorg, c=us OR
ibm-slapdSuffix: o=myorg
Note: Unix is case-sensitive.
3.
Restart the LDAP server.
Chapter 19: Special Installation Tasks 99
100 IBM Lotus LMS Release 1 Installation Guide
Chapter 20
Removing the IBM Lotus Learning Management System
LMS does not include an automated uninstall program. To remove the LMS component technologies (IBM Directory
Server, IBM DB2 7.2, and IBM WebSphere Application Server 5), use the Windows Add/Remove Programs utility in
the Control Panel. To remove the LMS software from your system, you must remove each installed component
manually.
Uninstalling the LMS and DS applications
To remove the LMS and DS enterprise applications from within WebSphere:
1.
From the WebSphere Administration interface, expand Applications
2.
Click Enterprise Applications.
3.
Select IBM Lotus LMS LMM and IBM Lotus LMS DS.
4.
Click Stop.
5.
Select IBM Lotus LMS LMM and IBM Lotus LMS DS.
6.
Click Uninstall.
7.
When the uninstall process has completed, click Save to save your changes to the Master Configuration.
Note: To uninstall the LMS and DS applications from UNIX platforms, use the same WebSphere procedure just
described.
Removing the installed LMS files
To remove the LMS files from your hard drive:
1.
Navigate to the install directory for LMS. By default, this directory is X:\Program Files\IBM\lms, where X is
the letter of your hard drive.
2.
Delete the lms folder.
Note: To remove the LMS files in UNIX installations, delete the correct directory in your UNIX installation. The
example above was given for a Win32 installation.
Removing the LMS, DS, and Audit databases
To remove the LMS, DS, and Audit databases from your database program:
1.
Back up the database.
2.
For an Oracle database, in SQLPlus, type DROP USER <schema owner username> CASCADE. For a DB2
database, connect to the database and type DB2 DROP DATABASE <database name>. For a SQLServer
database, connect using ISQL, type DROP DATABASE <database name>, then type GO on the next line to
execute the statement.
Note: These are destructive commands and, for that reason, a DBA is required to issue them.
Chapter 20: Removing the IBM Lotus Learning Management System 101
102 IBM Lotus LMS Release 1 Installation Guide
Index
Application Servers
deploying LMS components to separate, 89
applications
starting, 91
starting from WAS Admin console, 91
Command Line Import Utility (CLIMP), 94
installing, 94
database creation and configuration, 40
database schemas, 39
Delivery Server
adding to the LMS application, 93
Delivery Server (DS) application, 87
deploying, 87
environment entries, 65
configuring, 65
defining, 65
Hardware requirements, 3
IBM Directory Server 4.1
installing, 17
deploying, 77
LearningSpace
migration from, 95
LMS Authoring Tool, 94
installing, 94
LMS Installer
using for the Delivery Server, 29
using for the LMS server, 21
migration from LearningSpace, 95
multiple servers, 51
Network Deployment Module, 51
installing, 51
Offline Learning Client, 94
deploying, 94
post-installation tasks, 93
Referenceable, 67
regenerating the Web sever plug-in, 92
Resource Environment Provider, 65
Identifying LMS Hardware Assets, 11
server configuration options, 11
installation process
server responsibilities, 11
outline, 6
Installer program information, 21, 29
installing XVFB, 95
JDBC data sources, 55
configuring, 55
defining, 59
JDBC Provider, 56
LDAP authentication, 73
LDAP directory, 17
identifying, 17
installing, 17
Learning Management System, 1
components, 1, 2
inastallation overview, 5
overview, 1
system requirements, 3
Learning Management System (LMS) Server
application, 77
single logon, 14, 97
Software requirements, 3
SSO, 14, 97
configuring, 14, 97
uninstalling the LMS, 101
Updater, 92
WAS Global Security, 76
web server plug-in
regenerating, 92
WebSphere, 13, 43
WebSphere Application Server security, 73
configuring, 73
WebSphere Core
installing, 13
XVBF
installing, 95
Index 103
104 IBM Lotus LMS Release 1 Installation Guide
Printed in USA
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement