The path to the architect 17th Day IBM WebSphere Cluster Quest-wasnd (i)

The release of IBM WebSphere is divided into stand-alone and Networkdeployment editions, and we refer to network deployment as ND as a cluster version.

Was's cluster, like the WebLogic cluster, can also be used for both vertical and horizontal clusters.

And the WASND cluster is the most powerful in all clusters, because it can:

Each node is composed of a cell, and the cell can be composed of a new cluster, and Cluter and cluster can also be a total of one manager node to form a new cluster, so that through the wasnd to set up a large cluster.

At the same time, IBM's next generation of products such as: Grid computing (after we finish talking about wasnd), cloud computing Some enterprise-class virtual applications are based on the wasnd.

I. Basic CONCEPTS

There are many steps to using WASND as a cluster, the following tutorial has dozens of pages, all steps, just remember the next few steps to catch the key points.

1. First install wasnd, nonsense, but you must also have wasnd rather than the general was, the general was not a cluster.

2. Establish a Deployment Manager node, which we call dmgr.

3. Establishment of "Application Unit".

4. To "Unite" the "Application Unit" with Dmgr, the official document on this side is "federate", which we can interpret as "applying the unit" to Dmgr management.

5. Start dmgr with Startmanager.

6. Start each node with Startnode.

7. The admin console that enters Dmgr can start and stop individual members under the cluster.

Let's build a cluster, in this case we'll install 1 dmgr, two node, then add two node to the Dmgr, and then use IBM Httpserver (IHS) to distribute the HTTP request ( see the table below-the case is strictly case-sensitive )

logical name	cell function	profilename	server
Dmgr	cluster snap-in	dmgr
Server1	cluster node 1	appsrv01	server1
Server2	cluster node 1	server1

In order to test conveniently, we all three units enable "security management", username and password are "admin/password_1".