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.
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 left panel of the WebSphere web 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.
Start a deployment manager.
~]# was_home/profiles/your_dmgr_server/bin/startManager.sh . . . ADMU3000I: Server your_dmgr_server open for e-business; process id is 12345
Stop a deployment manager.
~]# was_home/profiles/your_dmgr_server/bin/stopManager.sh . . . ADMU4000i: Server your_dmgr_server stop completed.
Username / Password
The -user and -password options can be used to stop or start the dmgr as a certain user.
~]# ./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 has the username and password of a user with the administrative user role.
~]# cat was_home/profiles/your_profile/properties/soap.client.props com.ibm.SOAP.loginUserid=your_username com.ibm.SOAP.loginPassword=your_password
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