Lotus Learning Management System R1 ® Version 1.0.
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.
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.
Contents Chapter 1 About the IBM Lotus Learning Management System ............................................................1 Introduction ............................................................................................................................................................................... 1 What is the Learning Management System? .........................................................................................................................
DB2 database creation and configuration for the Learning Management System: an example................................... 38 Oracle database creation for the Learning Management System ..................................................................................... 44 MS SQL Server database creation for the Learning Management System ...................................................................... 45 Additional information about running scripts in different environments...........................
Determining the correct SSO settings for the Learning Management System................................................................ 96 Chapter 19 Special Installation Issues ...................................................................................................99 Using SSL with the Learning Management System ........................................................................................................... 99 Using the Directory Server Web Administration Interface with Linux........
vi IBM Lotus LMS Release 1 Installation Guide
Chapter 1 About the IBM Lotus Learning Management System Introduction This document provides information on the IBM® Lotus® Learning Management System installation process as well as information on packaging and layout. The intended audience for this document is system administrators, developers, and other users who wish to install the Learning Management System.
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.
Chapter 2 Learning Management System Requirements The Learning Management System is supported on a specific set of hardware and software components. Whether you are installing the Learning Management System for the first time on a server or upgrading from an earlier release of LearningSpace®, you may need to upgrade hardware and/or software before the Learning Management System can function on that machine.
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.
Chapter 3 Learning Management System Installation Overview The following information provides an outline of the Learning Management System installation process. Packaging overview The functional components of the Learning Management System product are J2EE™ web applications. J2EE provides the packaging for these components as a standard. The important units of the Learning Management System packaging as J2EE applications are • .war (web application archive) files • .
Updater then creates two update SQL scripts - one for the Learning Management System server (updateLMM.sql) and one for the Delivery Server (updateDS.sql). These scripts are then run to change the respective databases. You can change settings through the user interface at any time. Since virtually all required application settings can be specified through the Installer or the user interface, it is unlikely that you would ever need to modify the XML files.
the WebSphere and the Learning Management System administrator (who may be one and the same person). The organization of the LDAP directory is a key factor in operating the Learning Management System. Many aspects of the Learning Management System operation require that directory path expressions be specified. An example is rostering.
At this time you should also identify the LDAP username for the Learning Management System administrator. This value is used to make an entry in the USER table and represents the only rostered user when the application starts. For more information, refer to “Chapter 9 Installing and configuring database servers and schema”. 7. Install the Network Deployment module (optional) The Network Deployment (ND) module configures and controls multi-server WAS installations.
For more information, refer to “Chapter 14 Deploying the Learning Management Server application “ and “Chapter 16 Deploying the Learning Management System and DS components onto separate WAS App Servers.” 12. Deploy the Learning Management System Delivery Server (DS) application The Learning Management System Delivery Server (DS) also has its own .ear file. The DS .ear file must be also be deployed and all bindings resolved just as for the Learning Management System Server.
10 IBM Lotus LMS Release 1 Installation Guide
Chapter 4 Identifying Learning Management System 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.
Learning Management System Hardware requirements For the most up-to-date hardware requirements, refer to the README.TXT file and the Release Notes shipped with this product.
Chapter 5 Installing the WebSphere Core To successfully run the Learning Management System, you are required to have the WAS (WebSphere Application Server) Core installed on the desired systems. This can be a single server or multiple servers. The following instructions explain how to install this component. Note: For more complete information on installing WAS, refer also to http://www3.ibm.com/software/webservers/appserv/library/index.html.
5. For Windows users, choose to run both WebSphere Application Server and IBM HTTP Server as services. 6. Do not register the product. 7. Once the installer completes, the First Steps window will open. Select “Verify Installation” to launch the Installation Verification Tool (IVT). Its output will be written to the terminal (or command) window “behind” the First Steps GUI. 8. Verify that IBM HTTP Server has set the server’s name correctly in its configuration file.
• Expand the Security panel on the left side. • Expand Authentication Mechanisms. • Click LTPA. • Enter the password for LTPA (for example, wasadmin) • Click Save. • On the LTPA panel, click Single Sign On at the bottom of the panel. • Check that SSO is enabled. • Enter the domain name (for example, acme.com). 4. Enable Security (for more information, refer to the “Enable WAS Global Security” section of Chapter 13 Configuring WebSphere Application Server Security). 5. Stop the servers.
16 IBM Lotus LMS Release 1 Installation Guide
Chapter 6 Installing or Identifying the LDAP Directory The Learning Management System requires an LDAP directory for product operation. Either an IBM Directory Server 4.1 directory is installed or configured, or a pre-existing LDAP directory is identified. Also, at least two user-names that are recorded in the directory must be identified. These are for the WebSphere and the Learning Management System administrator. Note: There are no naming conventions for these administrator names.
9. • 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.
• 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.
Creating WebSphere and Learning Management System Administrator Accounts You need at least two accounts in the LDAP directory to complete the installation of the IBM Lotus Learning Management System: an account for the WebSphere administrator and an account for the Learning Management System administrator. To create these accounts, you can either import an LDIF file or create the entries by hand.
Chapter 7 Installing the Learning Management System Server Application Files Before deploying the complete Learning Management System, the Learning Management System Server files should first be installed on the Application Server. Note: If you are installing and deploying the Learning Management System Server and the Delivery Server onto separate WAS servers, refer also to Chapter 16 Deploying the Learning Management System and DS Components onto Separate WAS Application Servers for further information.
Note: You can install the Learning Management System Server and Delivery Server application files at the same time, even if you plan to deploy the applications to different machines. Since some of the settings are used for both the Learning Management System Server and Delivery Server (LDAP settings, for example), installing both applications together allows you to specify those settings only once. Installing the Learning Management System Server application software 1. Start the Installer. 2.
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.
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 install of the DS Server, the Learning Management System username and password is asked again. Make sure that you provide there the same Learning Management System 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.
Select the Administrator settings 15. Select the Administrator Role Type for the Learning Management System 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.
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 deployment servers that want content transferred to them via FTP.
22. Click Next to install the Learning Management System Server software as specified by your selected options. A Progress screen will let you monitor the progress being made while the Learning Management System 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.
28 IBM Lotus LMS Release 1 Installation Guide
Chapter 8 Installing the Delivery Server (DS) Application Files Before deploying the complete system, the Delivery Server files should first be installed on the Application Server. Note: If you are installing and deploying the Learning Management System Server and the Delivery Server onto separate WAS servers, refer also to Chapter 16 Deploying the Learning Management System and DS Components onto Separate WAS Application Servers for further information.
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 Learning Management System license agreements are installed in the Learning Management System license subdirectory.
10. After you have entered all of the LDAP settings, validate them to make sure they are correct. 11. To test these settings, click on the Test LDAP Connection button. If you have entered valid settings you will receive a message box stating that you have a successful connection otherwise you will be informed that you connection has failed. 12. Click Next to continue. Select the Learning Management System Server settings 13.
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 the Learning Management System. All of these fields except for Description must contain a value.
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.
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.
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 the Learning Management System will search a file path for deployed content.
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.
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 Learning Management System Server and stores all information about courses, users, progress, resources, deployment, status, etc. It is used for learning management and reporting.
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 Learning Management System databases and database schemas, refer to the Administrator’s Guide.
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 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
This specifies the maximum number of open files, system-wide, to 32K. Database creation details The following procedures provide detailed instructions on installing and creating the necessary DB2 databases for use with the Learning Management System: 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.
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 Learning Management System schema. 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.
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. 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.
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: . /$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.
9. Enter the Database alias (for example, Learning2). 10. Click Next. 11. Unselect Register this database for ODBC and click Next. 12. Click Next on Step for Add Database Wizard. 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 the Learning Management System In this example, the Learning Management System requires several distinct schemas to operate.
sqlplus lmm/lmm@ @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: sqlplus system/@ @cr_oraown_aud.sql 2.
• 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.
• 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.
48 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.
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.
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 En
52 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 application is deployed, resources must be configured. There are two types of resources that apply to the 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.
Defining the JDBC provider The first step is to define the overall JDBC Provider. This corresponds to the specific driver and database vendor. Defining the JDBC provider for a DB2 database 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.
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.
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.
Defining the JDBC provider for a SQL Server database 1. Install SQL Server 2000 Driver for JDBC Service Pack 2 on the WAS node(s) that will host the LMM and DS. If you don't have the MSSQL jars, you can get them from the Microsoft site. The URL for the SP2 drivers is: http://www.microsoft.com/downloads/details.aspx?FamilyID=9f1874b6-f8e1-4bd6947c-0fc5bf05bf71&DisplayLang=en 2. Access the WAS Admin Console. 3.
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.
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.
• Click Apply. 16. Repeat this procedure for the two remaining databases.
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.
• • • 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.
Chapter 12 Configuring Environment Entries After the WebSphere Application Server (WAS) is installed, but before the Learning Management System application is deployed, resources must be configured. There are two types of resources that apply to the 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.
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.
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.
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.
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.
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 Learning Management System 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.
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.
70 IBM Lotus LMS Release 1 Installation Guide
Chapter 13 Configuring WebSphere Application Server Security The 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.
Configure the LDAP directory for use with the Learning Management System The following steps show how to configure WAS security to use an LDAP directory: 1. Launch the WAS Administrative Console and go to Security - User Registries. 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.
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.
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.
Chapter 14 Deploying the Learning Management System 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 Learning Management System application deployment process is the .ear (enterprise application archive) file. This package is a zip-format archive containing standardized metadata.
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.
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 Learning Management System Installer generates a WAS .ear directory using that name. Even if you want to use the default name as shown above, you should edit the name and remove all the spaces.
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 Learning Management System data (jdbc/LMS_Default) and select “jdbc/lmm” from the “Specify existing Resource JNDI name" drop-down list.
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 Learning Management System 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.
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.
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.
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.
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 Learning Management System Server application.
84 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 Learning Management System installation, follow the same steps outlined in “Chapter 14 Deploying the Learning Management System Server application.” The only difference for deploying the Delivery Server is in” Step 4. Map resources references to resources.
86 IBM Lotus LMS Release 1 Installation Guide
Chapter 16 Deploying the Learning Management System 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.
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.
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.
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. Regenerating the web server plug-in With J2EE servers such as WebSphere, high-volume deployments (such as the Learning Management System) that have static HTTP assets (for example, .html or .gif files) have them served by a dedicated HTTP server.
Chapter 17: Starting the Applications 91
Chapter 18 Post-Installation Tasks After you have installed the Learning Management System, there are other tasks that must be completed to make full use of your installation.
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 Learning Management System Server, use the following steps: 1.
CLIMP allows you to import SCORM 1.2 course package files into the Learning Management System, making them available for deployment. Course package files can contain new courses, or updates to previously-deployed courses. Course packages are created by content vendors using the Learning Management System Authoring Tool, or by using some other tool that can produce SCORM 1.2 content.
• 2. 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/ 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.
# 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:5:initdefault: Change id:5:initdefault: to id:3:initdefault: Note: If you use a different run-level, be sure to match it when you set up the soft link in the next step. 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.
Management System and SSO refer to Chapter 5 Managing Users in the Administrator's Guide and the Installing the WebSphere Core chapter in this guide.
98 IBM Lotus LMS Release 1 Installation Guide
Chapter 19 Special Installation Issues For information on special issues related to this release of the Learning Management System, refer to the ReadMe.html and ReleaseNotes.html files that ship with this version of the product. Using SSL with the Learning Management System Use of the Secure Sockets Layer for the Learning Management System is supported with Release 1.0a and greater.
100 IBM Lotus LMS Release 1 Installation Guide
Chapter 20 Removing the IBM Lotus Learning Management System The Learning Management System does not include an automated uninstall program. To remove the Learning Management System 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 Learning Management System software from your system, you must remove each installed component manually.
102 IBM Lotus LMS Release 1 Installation Guide
Appendix A LMS Performance and Fine-tuning Information This chapter discusses post-installation tasks related to the running, maintenance, and fine-tuning of LMS operations. These tasks are not necessary to get LMS running, but are recommended for improving and correcting system performance.
5. Edit the WebSphere plug-in configuration file (plugin-config.xml) and search for the following line: Replace this line by the following lines: PAGE 112 PAGE 1134. There are several user attributes that are used quite often when searching for users (first name, last name, organization, etc.). For a faster response, you can index these attributes in the LDAP server’s database. Indexing LDAP attributes Every vendor provides different ways on how to index the information in their LDAP directory. In the case of Lotus Domino, for example, you just need to create a full text index on the address book (names.nsf) of the Domino server hosting the LDAP process.
• IBM DB2 tuning parameters: WebSphere Application Server http://publib7b.boulder.ibm.com/wasinfo1/en/info/ae/ae/rprf_db2parameters.html • IBM Redbook SG24-6417: DB2 UDB/WebSphere Performance Tuning Guide http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/SG246417.html • IBM Redbook SG24-6012: DB2 UDB V7.1 Performance Tuning Guide http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/SG246012.html • IBM Redbook SG24-5511: Database Performance Tuning on AIX http://publib-b.boulder.
TcpNumConnections This parameter defines the maximum number of simultaneous TCP connections and should be set higher than the expected number of simultaneous connections. Recommended value: 150-200% of your expected number of concurrent users Note: Instead of using the registry editor, you can create a text file with the extension .reg using Notepad. The values have to be specified as hexadecimal values.
Sun Solaris servers Adjust the following TCP/IP parameters to tune performance in Solaris: tcp_time_wait_interval This parameter tells Solaris how long in milliseconds to keep a socket that was closed before releasing it for re-use.
Tuning the Sun ONE Web server, Enterprise Edition - Solaris The default configuration of the Sun ONE Web server, Enterprise Edition provides a single-process, multi-threaded server. Adjusting the Active Threads parameter After the server reaches the limit set with this parameter, the server stops servicing new connections until it finishes with old connections. If this setting is too low, the server can become throttled, resulting in degraded response times.
Use the registry editor to set the ListenBackLog parameter located at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters\ListenBack Log The recommended value is 200. MaxPoolThreads and PoolThreadLimit parameter The MaxPoolThreads parameter controls the number of threads per CPU in the thread pool available for IIS to run Common Gateway Interface (CGI) processes (each process takes one thread). The PoolThreadLimit parameter specifies the upper limit for MaxPoolThreads.
• Time per request When testing different parameter settings for the httpd.conf, use these values to compare and find the best configuration setting for your system. MaxRequestsPerChild The MaxRequestsPerChild directive sets the limit on the number of requests that an individual child server process handles. After the number of requests reaches the value set for the MaxRequestsPerChild parameter, the child process dies.
2. Change the value of the parameter by starting with 100. 3. Save the changes and restart the IBM HTTP server. The recommended method is to start with a size of 100, then increase as necessary. An HTTP error message of type 503 (a refused connection) is a good indicator for the need to increase the value. There are two ways to find how many threads are being used under load. The following procedures show how this is done.
Use the following procedure to change this parameter: 1. Edit the IBM HTTP Server file httpd.conf located in the directory IBM_HTTP_Server_root_directory/conf. 2. Change the value of the parameter. 3. Save the changes and restart the IBM HTTP server. The recommended value is 250000. HTTP Logging This parameter enables logging for the HTTP server. Logging should be turned off unless you are trying to diagnose a problem. Use the following procedure to change this parameter: 1.
• Web container thread pool • Web container MaxKeepAliveConnections • Web container MaxKeepAliveRequests • JDBC Data Source Connection Pool size • JDBC Data Sources properties (to correct content deployment issues) Adjusting JVM Heap size The JVM heap size parameter specifies how often and how long the Java Virtual Machine spends collecting garbage (de-allocating unused Java objects). The JVM heap is a repository for live objects, dead objects, and free memory.
2. View or adjust the Maximum Heap Size and set the Initial Heap Size to the same value. 3. Stop and re-start the application. Enabling the JIT compiler When a JVM JIT (Just-In-Time) compiler is present and enabled, the Java Virtual Machine performs differently. After reading in a .class file for interpretation, the JVM hands the .class file to the JIT. The JIT takes the bytecodes and compiles them into native code for the machine that you are running on.
• Maximum size - Specifies the maximum number of threads to allow in the pool. This value should be set to 50% of the number of concurrent users planned for the LMS server. Use the maximum thread size parameter to specify the maximum number of threads that can be pooled to handle requests sent to the Web container. Requests are sent to the Web container through any of the HTTP transports. You have two choices: • Adjust the Minimum Size and Maximum Size for the thread pool.
Adjusting the JDBC Data Source Connection Pool size When accessing any database, the initial database connection is an expensive operation. Connection pooling and connection reuse reduces the number of these operations significantly. Only two parameters should be changed here: Min connections and Max connections. All other parameters should be left untouched. The minimum connections should be set to 15. The maximum connections should be set to equal the number of the Web Container Thread Pool size.
• Set the Logging level to warn Tracking Log: • Click Settings - LMM Server - System Logging - Tracking Log • Set the Logging level to warn Archiving the LMS log files LMS log files should be archived on regular basis. Otherwise, the files could continue to grow until no space is left on the hard drive.
Oracle PROCESSES Parameter (Oracle server only) This parameter must be changed on the Oracle server. Increasing this parameter from the default value of 150 to 600 can improve performance. Use the following procedures to change this parameter. 1. Find the SPFILEORACLE.ORA file on the Oracle server. 2. Open it for editing. 3. Find the PROCESSES parameter and change it to 600. 4. Restart the Oracle instance for the new value to take effect.
Appendix A: LMS Performance and Fine-tuning Information 121
Index Application Servers deploying Learning Management System components to separate, 87 applications starting, 89 starting from WAS Admin console, 89 Authoring Tool, 93 Authoring Tool installing, 93 Command Line Import Utility (CLIMP), 93 installing, 93 database creation and configuration, 38 installing, 17 Learning Management System components, 1, 2 installation overview, 5 overview, 1 system requirements, 3 Learning Management System Installer using for the Delivery Server, 29 using for the Learning Se
regenerating, 90 WebSphere, 13, 41 WebSphere Application Server security, 71 configuring, 71 WebSphere Core installing, 13 XVBF installing, 94 Index 123
Printed in USA
