4.4.3 Starting an appserver
How you start an appserver depends largely on personal preference and on whether the appserver is stand-alone or managed. Keep in mind that the appserver created by an appserver profile is always called server1. Multiple servers federated in this way are all named server1, but reside on different nodes.
Table 4-6 shows the various methods use to start an appserver.
Table 4-6
| Method
| Server types:
| Summary
|
| Windows service
| Managed and stand-alone
| Application servers can be registered as a Windows service. You can start the server by starting the service.
|
| First steps menu
| Managed and stand-alone
| The First Steps menu is located at <profile_home>/firststeps/firststeps.bat (.sh).
|
| Windows Start menu
| Managed and stand-alone
|
Select Start | Programs | IBM WebSphere | Application Server V6.1 | Profiles | <profile | Start the Server.
|
| Command line
| Managed and stand-alone
| cd <profile_home>/bin
startServer(.sh) server1
|
| Administrative console
| Managed
| Select Servers | Application Servers.
To start a managed server from the console, the node agent must be started.
|
| Administrative console
| Clusters
| Select Servers | Clusters.
Starting a cluster starts each appserver in the cluster.
|
| z/OS START command
| Managed and stand-alone
| START appserver_procname,JOBNAME=server_shortname, ENV=cell_shortname.node_shortname.server_shortname
|
Methods to start an appserver
|
