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.
The command syntax is as follows:
startManager [options]
The following options are available for the startManager command:
startManager startManager -script (produces the start_dmgr.sh or .bat file) startManager -trace (produces the startmanager.log file)
startManager startManager -script (produces the start_dmgr.sh file) startManager -trace (produces the startmanager.log file)