startManager command

Use the startManager command to manipulate a deployment manager with scripting.

The startManager command reads the configuration file for the WebSphere® Application Server, Network Deployment manager process and constructs a launch command. Depending on the options you specify, the startManager command launches a new Java™ virtual machine (JVM) API to run the manager process, or writes the launch command data to a file.

You must run this command from the profile_root/bin directory of a WebSphere Application Server, Network Deployment installation.

If you are using the Windows® platform and you have the deployment manager running as a Windows service, the startManager command will start the associated Windows service and it will be responsible for starting the deployment manager.

You do not have to use a user name and password with the startManager command because this command launches a server process but does not invoke an MBean method.

For more information about where to run this command, see the Using command line tools article.

Syntax

The command syntax is as follows:

startManager [options]

Parameters

The following options are available for the startManager command:

-nowait
Tells the startManager command not to wait for successful initialization of the deployment manager process.
-quiet
Suppresses the progress information that the startManager command prints in normal mode.
-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 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.
-replacelog
Replaces the log file instead of appending to the current log.
-trace
Generates trace information into a file using the startManager command for debugging purposes.
-timeout <seconds>
Specifies the waiting time before deployment manager initialization times out and returns an error.
-statusport <portNumber>
An optional parameter that allows an administrator to set the port number for deployment manager status callback. The tool opens this port and waits for status callback from the deployment manager indicating that the deployment manager has started. If the parameter is not set, an unused port is automatically allocated.
-script [<script fileName>] -background
Generates a launch script with the startManager command instead of launching the deployment manager process directly. The launch script name is an optional argument. If you do not provide the launch script name, the default script file name is <start_dmgr>. The -background parameter is an optional parameter that specifies that the generated script will run in the background when you execute it.
-help
Prints a usage statement.
-?
Prints a usage statement.

Usage scenario

The following examples demonstrate correct syntax:
startManager 

startManager -script (produces the start_dmgr.sh or .bat file)

startManager -trace (produces the startmanager.log file)
Reference topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:38:49 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=rxml_startmanager
File name: rxml_startmanager.html