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.
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 tools article.
Syntax
The command syntax is as follows:
startServer <server> [options]
where
server is
the name of the application server to start.
This
argument is required.
Parameters
The following options are available
for the startServer command:
- -?
- Prints a usage statement.
- -help
- Prints a usage statement.
- -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.
- -nowait
- Tells the startServer command not to wait for successful
initialization of the launched server process.
- -profileName
- Defines the profile of the Application 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.
- -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 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 execute it.
Note: The startserver.sh
script launches a new process from the app_server_root directory
to initialize the application server. The start_server1.sh script
launches the application server from the directory in which the script
is located. Because of this, the directory for the process launched
using the startserver.sh script is the app_server_root directory
and the directory for the process launched using the start_server1.sh
script is the app_server_root/bin directory. Any system properties
that are dependant on the process directory such as user.dir, might
be different for processes launched using the startserver.sh and start_server1.sh
scripts.
- -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:
startServer server1
startServer server1 -script (produces the start_server1.sh or .bat files)
startServer server1 -trace (produces the startserver.log file)