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

6.6a: Starting and stopping servers

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

Starting administrative servers on UNIX-based systems

To start the administrative server:

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

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.

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.0.
  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 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

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."

Obtaining feedback

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

Configuring the administrative server startup settings

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:

  1. 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.
  2. Checks once every five seconds to see if the nanny process is still running.
  3. 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.
  4. If the administrative server process stops running, the startupServer.sh script restarts the nanny process. The nanny process launches the administrative server.
  5. 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.

Troubleshooting

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 ...

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

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

  • ... when WebSphere security is enabled, on a Windows machine that is configured as part of a Windows domain and not connected via the network to the domain server, configure the Windows NT/2000 machine separately from the 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