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.

1. In the WebSphere admin console, expand System Administration.
2. Select Deployment manager.
3. 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.

Start dmgr - Command Line

Start a deployment manager.

${WAS_INSTALL_ROOT}/profiles/your_dmgr_server/bin/startManager.sh

The dmgr SystemOut.log will 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/. . .

Username / Password

If administrative security is enabled and you do not have a user with the administrator or operator role defined in the soap.client.props file, you will be prompted to provide a username and password. The -user and -password options can be used to stop or start the dmgr as a certain user (the user must have the administrator or operator role).

startManager.sh -user your_username -password your_password
stopManager.sh -user your_username -password your_password

However, the -user and -password options should not be used, as the username and password can be seen using the ps command (Linux).

~]# ps -ef
root  12345  12345  0  18:07  pts/0  00:00:00  /bin/sh  ./stopManager.sh -user JohnDoe -password itsasecret

Instead, you will want to ensure that the soap.client.props file has the username and password of a user with the administrator or operator role.

~]# cat was_home/profiles/your_profile/properties/soap.client.props
com.ibm.SOAP.loginUserid=your_username
com.ibm.SOAP.loginPassword=your_password

Crontab

A crontab job 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