InfoCenter Home > 6.6a: Starting and stopping the server
See also: Running administrative and application servers as non-root on UNIX systems Scripts for configuring how administrative servers startOn 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 systemsTo start the administrative server:
Running as non-root on UNIX-based systemsNormally, 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 systemsTo 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 systemsThe administrative server is started and stopped from the Control Panel Services menu.
Stopping servers on Windows-based systemsTo stop the server, stop the corresponding Windows service. Obtaining feedbackAfter 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. TroubleshootingSee 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 ...
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|