Filter
Top Products
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. 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 Learning Management System Server or Delivery Server 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. Learning Management System 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
Learning Management System 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
Learning Management System Server and Delivery Server applications again.
90 IBM Lotus LMS Release 1 Installation Guide