b issue the command server Status -all 画 Command Prompt -回x C:\WebSphere\AppServerprofiles\dmgr\bin>serverstatus -all ADMU0116I:T informat is be it in file C: We sPhere、RppS dmgr\logs\serverStatus log ADMU0128I: Starting tool with Retrieving server status servers ADMUG5G ervers found in configuration: ADMU0506I: Se ame: dmgr ADMU0509I: The Deployment Manager "dmgr "cannot be reached. It appears stopped C: \WebSphere \AppServer\profiles\dmgr\bin) C If the processes is not running, issue the command startManager Command Prompt ADMU05891: the deployment Manager"dmgr" cannot be reached. It appears C: \We bSphere \AppServer\profiles \dmgr\bin >startmanager ool information is being logged in file eDs phere r\profiles\dmgr\logs\dmgr\startserver ADMU3100I: Reading configuration for server: dmgr DMU3200I: Server launched. Waiting for initialization status ADMU3000I: Server dmgr open for iness; process id is 2060 \We bSphe re \AppServer\profiles\dmgr\bin> 2. Ensure that the managed processes for profile 1(nodeagent and server1)are started a Navigate to the profile 1 \bin directory cd WWebSpherelAppServerlprofileslprofile1 \bin Command Prompt C:\WebSphere\AppServer\profilesprofile\bin>- b. Check the status of managed processes for profile 1 Proof of Technology L04-Web Sphere Deployment Automation and WRU Page 3 of 28© Copyright IBM Corporation 2005. All rights reserved Proof of Technology L04 – WebSphere Deployment Automation and WRU Product Introduction + Exploration (PI+E) Page 3 of 28 __ b. Issue the command serverStatus –all. __ c. If the processes is not running, issue the command startManager. ____ 2. Ensure that the managed processes for profile1 (nodeagent and server1) are started. __ a. Navigate to the profile1\bin directory. cd \WebSphere\AppServer\profiles\profile1\bin __ b. Check the status of managed processes for profile1