InfoCenter Home >
6: Administer applications >
6.6a: Starting and stopping servers
6.6a: Starting and stopping servers
- Starting administrative servers:
- Obtaining feedback that the administrative server started successfully
- Configuring the administrative server startup settings
- Starting the Java-based administrative console
- Troubleshooting the administrative server startup
- Starting and stopping application servers
- Stopping administrative servers:
To start the administrative server:
- Ensure you are running as the root user.
- Change to the directory containing the
startup script (as described above), from a command prompt and enter:
./startupServer.sh
To stop a WebSphere administrative server on UNIX-based systems,
use an administrative client, such as the Java administrative
console. Using the kill command is not recommended.
The administrative server is started and stopped
from the Control Panel Services menu.
- From the Start menu, select Settings > Control Panel.
- Open the Services icon.
- From the Services panel, select IBM WS AdminServer 4.0.
- Use the Start and Stop buttons.
Stopping the administrative server also stops
the application server.
- To enable or disable automatic startup of the administrative server
on system reboot, click Startup and select Automatic or Manual.
- If starting the administrative server, start your Web server.
The WebSphere administrative server and the Web server run in separate
processes. You can start them in any order.
- Close Services.
Stop the server, by stopping the corresponding Windows service.
Running as non-root
Normally, the administrative server must run under the system root ID.
To avoid this restriction, see the information about running the
administrative server as non-root in "6.6.a.1:
Running the product servers and consoles as non-root."
Obtain feedback in the console window from which you start the application server.
You can also update the configuration to route the system output to a log file.
A message indicates that the Application Server is running successfully. A
typical message is shown here.
[01.05.31 12:03:34:434 CDT] 16023bce Server I WSVR0023I:
Server __adminServer open for e-business
The administrative server obtains its initialization parameters
from the administrative configuration file.
For UNIX platforms: You can add a property to the
admin.config file to enable the startupServer.sh script to do additional monitoring of the nanny
and administrative server processes. To activate this function, add the following property to the
admin.config file:
com.ibm.ejs.sm.adminServer.forceReconnect=true
Setting this property activates the additional monitoring. Setting the property to any value (not just true)
also causes the administrative server to always attempt to connect to the running application servers
instead of always restarting them. When this property is set to true, the startupServer.sh
script does the following:
- Checks to see if another copy of the
startupServer.sh script is running. It prints
an error message and ends if another copy is already running; otherwise, it continues.
- Checks once every five seconds to see if the nanny process is still running.
- If the nanny process is not running or stops running for some reason, the script checks to see if the
administrative server process is running, again checking once every five seconds.
- If the administrative server process stops running, the
startupServer.sh script
restarts the nanny process. The nanny process launches the administrative server.
- The administrative server reconnects to each of the running application servers for any non-null
setting of the property,
com.ibm.ejs.sm.adminServer.forceReconnect .
If this property is not set, the administrative server only tries to reconnect to running application servers
when it is restarted by the nanny process, or if it is started by the adminserver.sh script.
Do not set the com.ibm.ejs.sm.adminServer.forceReconnect property if you are running multiple
instances of WebSphere Application Server on a single system.
Note: This function is not available for HP-UX 11.
See the Problem Determination section for methodology and problem descriptions
for debugging a server that does not start. Here are some highlights. If
the server will not start ...
|
|