Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer nodes and resources > Work with dmgrs - centralized cell management

Start and stop the dmgr

The dmgr is an administration application that runs in a special application server, which is created when you install the WAS ND or when you create a management profile using the dmgr profile template. With the dmgr, you can administer multiple WAS nodes. This topic describes how you start and stop the dmgr.

Before you can start or stop the dmgr, you must first install the WAS WAS ND.

Start the dmgr so that you can manage all the elements of the WAS cell. Stop the dmgr as needed, such as when migrating to a new version of the WAS ND, when uninstalling the product, and so on.

Procedure

• Start the dmgr.

  Use one of these methods to start a dmgr:

  • Use the startManager command:

    startManager
    

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

    For more information, see the startManager command topic.

  If the message WSVR0629I: The request buffer for thread pool "server.startup" has reached its capacity is written to the dmgr SystemOut.log file when the dmgr starts, increase the size of the server.startup thread pool request buffer. We can run wsadmin commands to increase the maximum number of threads that are allowed in the pool. Start wsadmin for the dmgr and then runs in sequence:

  ### 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()
  

  ### 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 dmgr thread pool path; for example: "server.startup(cells/myCell01/nodes/cellMgr/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 dmgr.

  Use one of these methods to stop a dmgr:

  • Use the stopManager command:

    stopManager
    

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

    For more information, see the stopManager command topic.

  • Use the WAS ND dmgr admin console.

    To stop the dmgr from the admin console:

    1. Click System administration > Deployment manager.

    2. On the Configuration tab of the dmgr settings, click Stop.

Results

You have started the dmgr and have optionally stopped it.

What to do next

After you start a dmgr, run the startNode command to start federated application server nodes of the dmgr. After the dmgr and nodes are running, you can administer servers and applications on the nodes.

After you stop a dmgr, 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.
Start and stop a node

Related

startManager command
stopManager command
startServer command
stopServer command

+

Search Tips   |   Advanced Search