The startServer command reads the configuration file for the specified application server and starts the server.
If you are using the Windows platform and the
you have the application server running as a Windows service, the startServer command
will start the associated Windows service and it will be responsible
for starting the application server.
WSVR0009E: Error occured during startup. com.ibm.ws.exception.RuntimeError: java.lang.NoClassDefFoundError: com/ibm/ws/process/Win32ProcessGlue
For more information about where to run this command, see the Using command line tools article.
startServer <server> [options]where server is the name of the application server to start.
This
argument is required.
The following options are available for the startServer command:
Use this option if a server fails and you do not want to accept new transactions during the recovery process.
If the ENV parameter includes the REC=N element, the
setting is automatically changed to REC=Y if you specify -recovery
when you restart the server. The REC=N element is automatically included
on the ENV parameter if you did not migrate from a previous version
of the product. Following is an example of what your updated PROC
statement might look like:
//BBO6ACR PROC ENV=,PARMS=' ',REC=N,Z=BBO6ACRZ
startServer server1 startServer server1 -script (produces the start_server1.sh or .bat files) startServer server1 -trace (produces the startserver.log file)
startServer server1 startServer server1 -script (produces the start_server1.sh file) startServer server1 -trace (produces the startserver.log file)