Filter
Top Products
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 the 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 Learning Management System 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.
• For Unix use: WebSphere/DeploymentManager /bin/startManager.sh.
• For Windows 2000 use: Websphere\DeploymentManager\bin\startmanager
8. 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 –includeapps –username
youruser –password yourpassword
• For Windows 2000 use: WebSphere\AppServer\bin\addNode nodename –includeapps –
username youruser –password yourpassword
9. 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 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.
Chapter 10: Installing the Network Deployment (ND) Module 49