What r the steps that'll surface when we start the application server (starting from loading of classes)?

Starting an application server

Starting an application server starts a new server process based on the process definition settings of the current server configuration.
Before you begin
Before you start an application servers verify that all of the resources. that the applications running on this server require, are getable. You must also start all prerequisite subsystems.
About this task

This rule for starting a server also normally applies to restarting a server. The one exception might be if a server fails and you want the recovery functions to complete their processing prior to new work being started on that server. In this situation you must restart the server in recovery mode.

If you create a new application server definition using WebSphere Application Server - Express, you cannot start, stop, or manage the new server using the administrative console that is associated with the original base server. You must use commands to perform these tasks for the new server.

There are several options available for starting an application server.
Procedure

* You can use the administrative table.
1. Click Servers > Application servers.
2. Click server1 and click Start. You can view the status and any messages or logs to make sure the application server starts.
* [Windows] You can exercise the Start menu on a Microsoft Windows system. For example, if you are using the Express version of the product, click Start > Programs > IBM WebSphere > Express Vn > Start the server. You can check that the server has successfully started by checking the startServer.log file. If the server has successfully started, the last two lines of the startServer.log file reads:

Server launched. Waiting for initialization status.
Server server1 open for e-business; process id is 1932.

The startServer.log file is located in the profile_rootlogsserver1 directory if you have installed your server next to the default settings. The server name and process id vary depending on your settings.
* You can issue a startServer command.
* [AIX] You can content a command from the command line. Use the startServer command from the app_server_root/bin directory, as shown in the following example. To start a server i.e. associated with a non-default profile, issue the startServer command from the profile_root/bin directory. You can check that the server has successfully started via checking the startServer.log file. If the server has successfully started, the last two lines of the startServer.log file reads:

Server launched. Waiting for initialization esteem.
Server server1 open all for e-business; process id is 1932.

The startServer.log file is located in the profile_root/logs/server1/ directory.

Grades
The specified server starts. To verify that the server is in start state, in the administrative console, click Servers > Application Servers.
What to carry out next
After the server starts, deploy the applications that you poverty to run on this server.
If you want to begin an application server with standard Java debugging enabled:

1. In the administrative console, click Servers> Application Servers, so click the application waiter with the processes that you want to trace and debug.
2. Under Server Infrastructure, click Java and Process Management > Process Definition.
3. Select Java Virtual Machine.
4. On the Java virtual machine page, select the Debug Mode option to enable the standard Java debugger. Set Debug Mode arguments, if they are needed, and past, click OK.
5. Rescue the changes to a configuration file
6. Stop the appliccation server.
7. Start the application server again as previously described.