Restart the deployment manager

The deployment manager is an administration application that runs in a special application server, which is created when we install the WebSphere Application Server, Network Deployment product or when we create a management profile using the deployment manager profile template. With the deployment manager, we can administer multiple WAS nodes. The steps describe how we start and stop the deployment manager. Start the deployment manager so that we can manage all the elements of the WAS cell. Stop the deployment manager as needed, such as when migrating to a new version of the WAS ND product, when uninstalling the product, and so on. Start the deployment manager using the startManager

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. We can run wsadmin commands to increase the maximum number of threads allowed in the pool. Start wsadmin for the deployment manager and then enters in sequence:

• Use 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()

• Use 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, we might run showall twice, first to see the maximumSize value and then, after running the modify command, to ensure that the maximumSize value changed.

To stop the deployment manager: stopManager

You can also used Use the WAS ND deployment manager administrative console.

System administration > Deployment manager > Configuration tab > Stop

What to do next

After we start a deployment manager, run the startNode command to start federated application server nodes of the deployment manager. After the deployment manager and nodes are running, we can administer servers and applications on the nodes. After you stop a deployment manager, run the stopNode command to stop federated application server nodes if they are running. After you stop product processes, the product is no longer running.

Subtopics

• Directory conventions
  
• Starting and stopping a node
• startManager command
• stopManager command
• startServer command
• stopServer command