Starting the WebSphere Application Server

In a clustered environment, you must start all the components of WebSphere Application Server (WAS) in a specific order.

In a standalone environment, start WAS with a single command. For example, in the command prompt, issue the following command:

WAS_ROOT\bin\startServer server1

To start WAS in a clustered environment:

Start the deployment manager.
For example, in the command prompt, from the WAS_ROOT\bin\directory, issue the startManager command.
Start the node agents.
For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the startNode command. You can also issue the following command:
```
WAS_ROOT\bin\startNode -profileName profile
```
Start the Message Queue servers.
For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the startServer command. You can also issue the following command:
```
WAS_ROOT\bin\startServer serverName -profileName profile
```
Start the application servers or server clusters.
For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the startServer command. You can also issue the following command:
```
WAS_ROOT\bin\startServer serverName -profileName profile
```
You can start several servers simultaneously by using the WebSphere Application Server Administrative Console. In the administrative console, click Servers > Clusters > WebSphere application server clusters. Select the servers or clusters whose members you want started and click Start.

After the steps have been completed, WAS is now running. If needed, you can deploy your application.