You must install the network deployment manager (dmgr) and create a deployment manager profile before you can start or stop the deployment manager. Starting or stopping the deployment manager will not stop or start the applications, application servers, or node agents.
Web console
Once you stop the deployment manager, you will no longer be to use the web console. The deployment manager will need to be started from the command line to be able to use the web console again.
- In the WebSphere admin console, expand System Administration.
- Select Deployment manager.
- Select Stop.
If the stop button is missing, this means you are signed into the dmgr as a user that does not have the Administrator or Operator user role.
Command Line
There are a number of similar scripts that can be used to start, stop and check the status of WebSphere servers.
- serverStatus
- startServer | stopServer (start / stop application server)
- startManager | stopManager (this article)
- startNode | stopNode | syncNode (start / stop node)
Start a deployment manager.
AVOID TROUBLE
If you are prompted for a username and password, refer to username password and the soap.client.props sas.client.props ipc.client.props files.
${WAS_INSTALL_ROOT}/bin/startManager.sh
If you have two (or more) profiles, there should be a startManager script for each profile, to only start the network deployment manager with the profile.
${WAS_INSTALL_ROOT}/profiles/your_profile/bin/startManager.sh
If the startup was successful, the HPEL or SystemOut log should have the following.
WSVR0001I: Server dmgr open for e-business
The dmgr startServer.log will have the following.
ADMU3201I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 12345
Stop dmgr - Command Line
Stop a deployment manager.
${WAS_INSTALL_ROOT}/profiles/your_dmgr_server/bin/stopManager.sh
The dmgr SystemOut.log will have the following.
WSVR0024I: Server dmgr stopped
The dmgr stopServer.log will have the following.
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.
dmgr status - Command Line
The serverStatus.sh (Linux) or serverStatus.bat (Windows) command can be used to check the status of the dmgr.
${WAS_INSTALL_ROOT}/profiles/your_profile/bin/serverStatus.sh
The dmgr serverStatus.log should have one of the following.
ADMU0509I: The Deployment Manager "dmgr" is STARTED.
ADMU0509I: The Deployment Manager "dmgr" cannot be reached. It appears to be stopped.
On Linux, the ps command can be used to determine if the dmgr is running. In this example, the dmgr is using PID 12345.
~]# ps -ef | grep -i WebSphere
root 12345 1 0 Dec13 ? 00:45:50 /opt/IBM/WebSphere/Dmgr/. . .
Crontab
A crontab job (on Linux systems) can be created to ensure the deployment manager is started when the system is rebooted.
@reboot bash /opt/IBM/WebSphere/your_dmgr_server/bin/startManager.sh
Did you find this article helpful?
If so, consider buying me a coffee over at 