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. Frequently, the Learning Management System 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
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
6.Edit and copy the HTTP
7.Stop and restart the application servers whose ports you just added to default_host.
To help ensure the successful deployment of both the Learning and Delivery Servers, you must also set an additional WebSphere variable, ConnectionIOTimeOut, must be set for both the Learning 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 87
