Starting and stopping the deployment manager

The deployment manager is an administration application that runs in a special application server, which is created when you install the WebSphere® Application Server Network Deployment product or when you create a management profile using the deployment manager profile template. With the deployment manager, you can administer multiple WebSphere Application Server nodes. The steps describe how you start and stop the deployment manager.

• Start the deployment manager.
  Use one of these methods to start a deployment manager:

  • Use the startManager command:

    startManager

    Use the startManager Qshell script to start a deployment manager from the Qshell command line of the IBM® i server hosting the node.

    For example, from a command dialog at the bin directory of a deployment manager profile, run the startManager command.

    For more information, see the startManager command topic.

  • Use the Submit Job (SBMJOB) CL command.
    You can run this CL command from an IBM i command line:

    SBMJOB CMD(CALL PGM(product_library/QWASSTRSVR) PARM('-profilePath'
      'profile_root' '-server' 'deployment_manager')) JOB(server)
      JOBD(QWAS85/QWASJOBD) JOBQ(QWAS85/QWASJOBQ) USER(QEJBSVR) LANGID(*USRPRF)
      CNTRYID(*USRPRF) CCSID(*USRPRF) OUTQ(QWAS85/QWASOUTQ) ALWMLTTHD(*YES)

    where

    • profile_root is the profile root of the deployment manager.
    • deployment_manager is the name of the deployment manager server that you want to start.
  Note: If the message WSVR0629I: The request buffer for thread pool "server.startup" has reached its capacity is written to the deployment manager SystemOut.log file when the deployment manager starts, increase the size of the server.startup thread pool request buffer. You can run wsadmin commands to increase the maximum number of threads that are allowed in the pool. Start wsadmin for the deployment manager and then enter the following commands in sequence:

  • Using Jython:

    print AdminConfig.list('ThreadPool')
    tp = "server.startup(thread_pool_path_from_list_command)"
    print AdminConfig.showall(tp)
    AdminConfig.modify(tp, [['maximumSize', new_size_value]])
    print AdminConfig.showall(tp)
    AdminConfig.save()

  • Using Jacl:

    $AdminConfig list ThreadPool
    set tp "server.startup(thread_pool_path_from_list_command)"
    $AdminConfig showall $tp
    $AdminConfig modify $tp {{maximumSize new_size_value}}
    $AdminConfig showall $tp
    $AdminConfig save

  Set the tp variable to the deployment manager thread pool path; for example: "server.startup(cells/myCell01/nodes/myCellManager01/servers/dmgr|server.xml#ThreadPool_startup)". It is not necessary to run the showall command. However, you might run showall twice, first to see the maximumSize value and then, after running the modify command, to ensure that the maximumSize value changed.
• Stop the deployment manager.
  Use one of these methods to stop a deployment manager:

  • Use the stopManager command:

    stopManager

    Use the stopManager Qshell script to stop a deployment manager from the Qshell command line of the IBM i server hosting the node.

    For example, from a command dialog at the bin directory of a deployment manager profile, run the stopManager command.

    For more information, see the stopManager command topic.

  • Use the WebSphere Application Server Network Deployment deployment manager administrative console.
    To stop the deployment manager from the administrative console:

    1. Click System administration > Deployment manager.
    2. On the Configuration tab of the deployment manager settings, click Stop.
  • Use the End Job (ENDJOB) CL command.
    To use the ENDJOB CL command to end an application server, enter this command on an IBM i command line:

    ENDJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)
    

    where jobNumber is the job number, jobName is the name of the application server job for the deployment manager, and delayTime is the amount of time to wait for the job to end in seconds. Use a value of 600 seconds initially. To find out what the appropriate delayTime is, see Shutting down the WebSphere Application Server subsystem.