The startServer command reads the configuration file for
the specified server process and starts that server process.
Use the startServer command
to:
- Start an application server.
- Start a DMZ Secure Proxy Server for IBM® WebSphere® Application Server.
- Start an administrative agent.
- Start a job manager.
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.
Avoid trouble: You can use the administrative
console to change the Java™ virtual
machine Classpath setting or the environment entries settings for
a server. However, before making these changes you should understand
the following consequences of making these changes:
gotcha
For more information about where to run this command, see the Using
command line tool topic.
Syntax
The command syntax is one of the
following:
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.
Parameters
The following options are available
for the startServer command:
- -?
- Prints a usage statement.
- -help
- Prints a usage statement.
- -J <java_option>
- Specifies options to pass through to the Java interpreter.
- -logfile <fileName>
- Specifies the location of the log file to which trace information
is written. By default, the log file is named startServer.log and
is created in your logs directory.
- -profileName
- Defines the profile of the server process in a multi-profile installation.
The -profileName option is not required for running in a single profile
environment. The default for this option is the default profile.
- -quiet
- Suppresses the progress information that the startServer command
prints in normal mode.
- -replacelog
- Replaces the log file instead of appending to the current log.
- -recovery
- Specifies that the server will start in recovery mode, perform
a transactional recovery, and shut down. The server will not accept
any new transactions while it is in recovery mode. When you start
the server again, resources that were unavailable due to questionable
transactions will be available.
Use this option if a server fails
and you do not want to accept new transactions during the recovery
process.
For transitioning users: If you are migrating
from a previous version of the product, make sure that the ENV parameter
included on the JCL procedure statement for the controller includes
either the REC=N or the REC=Y element. If the ENV parameter does not
include either the REC=N or the REC=Y element, the server will not
restart in recovery mode even if you specify the -recovery option.
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
trns
- -statusport <portNumber>
- An optional parameter that allows an administrator to set the
port number for server status callback. The tool opens this port
and waits for status callback from the server indicating that the
server has started. If the parameter is not set, an unused port is
automatically allocated.
- -script [<script fileName>] -background
- Generates a launch script with the startServer command instead
of launching the server process directly. The launch script name is
an optional argument. If you do not supply the launch script name,
the default script file name is start_server based
on the server name that is passed as the first argument to the startServer command.
The -background parameter is an optional parameter
that specifies that the generated script will run in the background
when you run it.
- -trace
- Generates trace information to the log file
for debugging purposes.
- -timeout <seconds>
- Specifies the waiting time before server initialization times
out and returns an error.
Usage scenario
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 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)