The startServer command reads the configuration file for the specified server process and starts that server process.
If you are running the product on a Microsoft® Windows® operating
system, and you have the server running as a Windows operating
system service, the startServer command will start the server and
the associated Windows service.
You do not have to use a user name and password with the startServer command because this command launches a server process but does not invoke an MBean method.
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 tool topic.
startServer server_name [options]
where server_name is the name of the application server or the DMZ Secure Proxy Server for IBM WebSphere Application Server that you want to start.
This argument is required.
startServer <adminagent_name>
whereadminagent_name is the name of the administrative agent that you want to start.
startServer <job_manager>
where job_manager is the name of job manager that you want to start.
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=BBO6ACRZtrns
The following examples demonstrate correct syntax. The information within the parentheses is a description of the output that is created if you issue the preceding command.
startServer server1
startServer server1 -script (produces the start_server1.sh or .bat files)
startServer server1 -trace (produces the startserver.log file)
startServer adminagent
startServer.sh server1 -trace -username MyUserName -password MyUserPassword
-profileName MyProfileName (starts the server1 server using the
MyProfileName profile. The server runs under the user name MyUserName,
and produces trace files under the profile_root/logs directory)
startServer jobmgr startServer proxy1 (for the secure proxy profile)
startServer server1
startServer server1 -script (produces the start_server1.sh file)
startServer server1 -trace (produces the startserver.log file)
startServer adminagent
startServer jobmgr
startServer proxy1 (for the secure proxy profile)
startServer.sh server1 -trace -username MyUserName -password MyUserPassword
-profileName MyProfileName (starts the server1 server using the
MyProfileName profile. The server runs under the user name MyUserName,
and produces trace files under the profile_root/logs directory)