startManager command

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

[AIX Solaris HP-UX Linux Windows] [z/OS] 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.

[AIX Solaris HP-UX Linux Windows] 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.

[IBM i] The startManager command reads the configuration file for the deployment manager profile and starts the server.

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 Using command-line tools.

Syntax

The command syntax is as follows:

startManager [options]

startManager [server] [options]

where server is an optional parameter that specifies the name of the deployment manager server. If you do not specify this option and you use the deployment manager profile, server defaults to the deployment manager. If you do not specify this option and you specify a profile other than the deployment manager, server defaults to the name of the profile.

[IBM i] Because the deployment manager profile is not the default profile, you must specify the -profileName option when using the startManager command.

Parameters

The following options are available for the startManager command:

-curlib <product_library>: Specifies the current library to use for the underlying Submit Job (SBMJOB) CL command.
-cpyenvvar: Tells the startServer command to set the environment variables that are currently defined for the application server process. The default is to not set the currently defined environment variables.
-inllibl <library_list>: Specifies the initial library list to use for the underlying Submit Job (SBMJOB) CL command.
-inlaspgrp <ASP_group>: Specifies the initial ASP group for the underlying Submit Job (SBMJOB) CL command.
-jobd <product_library/job_description>: Specifies the job description for the underlying Submit Job (SBMJOB) CL command.
-jobq <product_library/job_queue>: Specifies the job queue for the underlying Submit Job (SBMJOB) CL command.
-nowait: Tells the startManager command not to wait for successful initialization of the deployment manager process.
-outq <product_library/output_queue>: Specifies the output queue for the underlying Submit Job (SBMJOB) CL command.
-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.
-sbs <product_library/subsystem_description>: Specifies the subsystem to use for the underlying Submit Job (SBMJOB) CL command.
-trace: Generates trace information into a file using the startManager command for debugging purposes.; Enables tracing of the native process code that starts the deployment manager server. The trace output is written to the was_jobname-jobuser-jobnum.log file which is located in the profile_root/logs directory.
-timeout <seconds>: Specifies the waiting time before deployment manager initialization times out and returns an error.
-usejobd: Specifies to use the job description from the Submit Job (SBMJOB) process for the node agent when switching to the Run-As user ID.
Note: This command does not affect the USER field of the current job description.
-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)

The following examples demonstrate correct syntax:

startManager 

startManager -script (produces the start_dmgr.sh file)

startManager -trace (produces the startmanager.log file)

The following examples demonstrate correct syntax:

startManager -profileName dmgr (starts the deployment manager for the dmgr profile)

startManager -trace (produces trace files in the profile_root/logs directory)