WebSphere software- Copyright IBM Corporation 2005. All rights reserved. Issue the command server -al Command Prompt 回 C: \WebSphere\AppServer\profiles\dmgr\bin >ser atus -all ADMU01161: Tool information is being logged in filc ADMU01281: Starting tool wide=\ gr\logs\serverStatus lo DMU0503I: Retrieving server status for all servers ADMU9505I: Servers for n configuration ADMU05 0I name ADMU0509I: The Deplo yment Manager " dmgr"cannot be reached. It appears c:、 We sPhere \AppServer、 profiles \dmgr\bin 4. Start the Deployment Manager if it has a stopped status. Otherwise, skip this step Issue the command startManager c Command Prompl x ADMU0506I: Server name: dmgr ADMU0509I: The Deplo yment Manager "dmgr"cannot be reached. It appears C: \WebSphere \Ap er\ files \dmgr\bin>startmanager eing logged in file rofiles\dmgr、 logs \dmgr、 start Server ADMU01281: Startin dmgr profile ADMU31001 ADMU32001: Server launched. Waiting for initialization status ADMU3000I: Server dmgr business: process id is 2060 C: \We bSphere \AppServer\profiles \dmgr\bin> 5. Navigate to the profile 1 \bin directory. Issue the command cd WWebSpherelAppServerlprofileslprofile1\bin Command Prompt C: \WebSphere\AppServer\profiles\profile\bin). 6. Check the status of managed processes for profile 1 Proof of Technology Lab o7-Performance tools Product Introduction+ Exploration(PI+E Page 5 of 29© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 07 – Performance Tools Product Introduction + Exploration (PI+E) Page 5 of 29 Issue the command serverStatus –all. ____ 4. Start the Deployment Manager if it has a stopped status. Otherwise, skip this step. Issue the command startManager. ____ 5. Navigate to the profile1\bin directory. Issue the command cd \WebSphere\AppServer\profiles\profile1\bin ____ 6. Check the status of managed processes for profile1