24.Start the managing server using the command /opt/IBM/itcam/WebSphere/MS/bin/am-start.sh. 25.Log on to the Web console using the user ID that you specified in step 1. Go to ADMINISTRATION Managing Server Self Diagnostics. Verify that all of your managing server components are started. 4.2 Modify the managing server for the other site This task assumes that you already have installed a managing server that you will bring to the customer environment. If you must install the managing server from scratch, read 4.1, "Install the managing server" on page 48. Follow these implementation steps: 1. Clean up the managing server database. a. Stop the managing server component using this command: /opt/IBM/itcam/WebSphere/MS/bin/am-stop.sh b. Stop WebSphere Application Server using this command: /opt/IBM/itcam/WebSphere/MS/WAS60/profiles/default/bin/stopServer .sh server1 c. Optionally, back up your current managing server database using these commands: . /opt/IBM/itcam/WebSphere/MS/SQLLIB/db2profile db2move OCTIGATE export d. From /opt/IBM/itcam/WebSphere/MS/bin, run the command ./db e. Stop DB2 processes using the command db2 stop dbm. 2. Assign a new IP address and host name for the managing server database, using the appropriate tools provided with your Linux distribution. Make sure that your managing server is aware of the new IP address and host name. Verify these using the following commands: hostname ifconfig -a ping <ipaddr> ping <hostname> nslookup <ipaddr> nslookup <hostname> 3. Verify connectivity of the managing server. a. Start DB2 using this command: db2 start dbm. b. Start the managing server component using this command: /opt/IBM/itcam/WebSphere/MS/bin/am-start.sh Chapter 4. Implementation of ITCAM for WebSphere service 61