Windows Cluster installation: 5) create a cluster application

This chapter describes how to add an application to a Windows Cluster so that it can use the power of a Windows Cluster. When it comes to being powerful, if the application is not Cluster-aware, you can only use the basic functions of the Cluster: failover and failback ). For more information about how to develop a cluster-Aware Application, see Microsoft's Platform SDK (Platform SDK) or look forward to the next article in my Windows Cluster series: Windows Cluster application development. Now, we have to try it out first. Here we use the most popular Windows app Notepad as an example.

1) Add an application as a resource

First, open "Cluster Manager" on any node (Computer), right-click "resource", and choose "New" and "resource", for example:

The "New Resource" window appears, as shown in. Please set it as needed. The name and description are as follows:

Click "Next" and select available nodes. By default, all three nodes are available, for example:

Click "Next" to set the dependency settings of the application. You can skip this step and select two options at will, for example:

Click "Next", set the application parameters, and manually enter the parameters. Check "allow applications to interact with the desktop", because we need to see and operate on the application. For example:

Click "Next" and the registry settings will appear. Because our Notepad does not need the registry, you can ignore it, for example:

Click "Next" and our application will be added to the cluster resources. The default status is offline, for example:

2) start the application (online)

Right-click "ClusterNotepad" and select "online". After a while, Notepad will appear on Node0. For example:

In cluster manager, the "ClusterNotepad" status is changed to "online", for example:

Our application is successfully started (online.

3) test failover

Right-click our resource "ClusterNotepad" and choose "initial fault" or "offline", for example:

"Initial failure" simulates node failure operations. Notepad on Node0 will be closed and restarted. Manual close of the Notepad program can also produce similar results. The following screen is displayed during the process:

Finally, the clusternotepad resource is reconnected. Repeat this operation three times, and the group assembly transfers the resources to node1. Repeat these steps on node1. then, clusternotepad will be transferred to node2. Repeat .... Will loop to node0, so reciprocating.

Is it easy?

The next article describes how to configure a cluster application.