InfoCenter Home >
6: Administer applications >
6.6a: Starting and stopping the server

6.6a: Starting and stopping the server

  1. Editing administrative server startup scripts (UNIX)
  2. Starting administrative servers:

  3. Obtaining feedback that the administrative server started successfully
  4. Starting the Java-based administrative console
  5. Troubleshooting the administrative server startup
  6. Starting and stopping application servers
  7. Stopping administrative servers:

See also: Running administrative and application servers as non-root on UNIX systems

Scripts for configuring how administrative servers start

On UNIX systems, you can configure the starting parameters for an administrative server by editing its startup file:

product_installation_root/bin/startupServer.sh

See below for recommended startup instructions. It is not always advisable to run the startup file directly.

Starting administrative servers on UNIX-based systems

To start the administrative server:

  1. Ensure you are running as the root user.
  2. From a command prompt, change to the directory containing the startup script (as described above) and enter:
    ./startupServer.sh
    
Running as non-root on UNIX-based systems

Normally, the administrative server must be run under the system root ID. To avoid this, see Running the administrative server as non-root .

Stopping servers on UNIX-based systems

To stop an WebSphere administrative server on UNIX-based systems, use an administrative client, such as the Java administrative console. Using the kill command is not recommended.

Starting administrative servers on Windows-based systems

The administrative server is started and stopped from the Control Panel Services menu.

  1. From the Start menu, select Settings > Control Panel.
  2. Open the Services icon.
  3. From the Services panel, select IBM WS AdminServer.
  4. Use the Start and Stop buttons. Stopping the administrative server also stops the application server.
  5. To enable or disable automatic startup of the administrative server on system reboot, click Startup and select the Automatic or Manual.
  6. 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.
  7. Close Services.
Stopping servers on Windows-based systems

To stop the server, stop the corresponding Windows service.

Obtaining feedback

After an administrative server starts, messages are written to the administrative server trace file at:

product_installation_root/logs/tracefile

Look for the following messages to confirm that the server started successfully:

Managed Server E Version: Runtime 3.0 dev Config: ES-jmon-3.0
Admin Server E Admin Server open for e-business.

Troubleshooting

See the Problem Determination section for methodology and problem descriptions for debugging the failure of the server to start. Here are some highlights. If the server will not start ...

  • ... and you encounter this error (in the Services panel on Windows NT):
    The IBM WebSphere AdminServer service returned service specific error 10
    

    Add a newline character at the end of the administrative server configuration file.

  • ... when WebSphere security is enabled, and it is on a Windows machine configured as a part of a Windows domain and not connected via the network to the domain server, then to solve the problem, configure the Windows NT/2000 machine so that it is not part of a Windows NT/2000 domain.
Go to previous article: Running the product servers and consoles as non-root Go to next article: Tutorials

 

 
Go to previous article: Running the product servers and consoles as non-root Go to next article: Tutorials