Configuring a websphere cluster to run as a service (Windows)

 Steps to be executed:
 

1. Configure your node agent or node agents, to run as a service by using the WASService command line tool.

The following example code uses the Local System account, SYSTEM, as the default user ID. If you want to use a different account, you can specify your own user ID by using the -userid option.

C:\IBM\WebSphereND855\AppServer\bin>WASService

-add "myNode01" -servername nodeagent

-profilePath C:\IBM\WebSphereND855\AppServer\profiles\Custom01

-wasHome C:\IBM\WebsphereND855\Appserver

-logFile C:\IBM\WebSphereND855\AppServer\profiles\Custom01\

  logs\nodeagent\startNode.log

-logRoot C:\IBM\WebSphereND855\AppServer\profiles\Custom01\logs\nodeagent

-restart true -startType automatic

Adding Service: ImyNode01

        Config Root: C:\IBM\WebSphereND855\AppServer\profiles\Custom01\config

        Server Name: nodeagent

        Profile Path: C:\IBM\WebSphereND855\AppServer\profiles\Custom01

        Was Home: C:\IBM\WebsphereND855\Appserver\

        Start Args:

        Restart: 1

IBM WebSphere Application Server V8.5.5 - myNode01 service successfully added.

2. Configure your cluster members to restart automatically:

1. Log in to the WebSphere administrative console.
2. Click Servers > Application Servers > server_name.
3. Expand Java and Process Management and select Monitoring Policy.
4. Change the node restart state to RUNNING.
5. Click OK and Save.

Repeat this step for each server in the cluster.

3. Shut down your node agents by using the stopNode command:

4. Shut down your cluster by using the WebSphere administrative console.
5. Start your node agents by using the Windows Services Console. Your cluster will automatically restart.

Note: Your node agents and cluster members must now run in the context of the Local System account instead of your own user account, unless you specified a different account when you ran the WASService command in step 1

You can now safely log out of your Windows user account and your cluster will continue to run.