Wait patiently. To see whether the system is still trying to start the server, examine the Performance page of the Task Manager. If the server is slow to start or does not start successfully, look at the last line in the \WebSphere\AppServer\logs\tracefile log. If the trace file says server is open for e-business, the server has started.
Hint: You can control the server from a command line or batch file using the following commands:
Explaining the AdminServer: The AdminServer doesn't run any servlets, Java Server Pages, or Enterprise Beans. Each node can have multiple JVMs known as servers which run the application code. The Admin Server manages these servers, and if they stop, it restarts them. Each server can have EJB Containers to run EJBs, and a servlet engine to run servlets. Servers can either be independent, running different code, or clones which are identical, and the infrastructure manages spreading the incoming requests across the servers. A cluster consists of multiple nodes, each with clones.
Although the installation has created a default server, it hasn't started it, so you can't run anything yet.
Once the server starts, it is marked in the configuration database that it should be running. If it stops, or if you reboot the machine, the administrative server will automatically restart it. Even if the administrative server fails, it will continue to run.