Filter
Top Products
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. 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 Learning Management System
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:
14 IBM Lotus LMS Release 1 Installation Guide