Step 4: Deploy virtual system
Now, deploy the virtual system and see the outcome.
Log in to the Workload Service:
- Click Patterns > Virtual Systems.
- Select pattern WebSphereWithMonitoring. Click Deploy.
- In the Deploy pattern window, give your virtual system a name, say WASITM1.
- Click Configure virtual parts and then select the WebSphere part.
- Enter or edit any required values for the pattern and the script package environment variables.
- Click OK.
- Click OK to deploy the pattern.
The virtual system goes through several state changes before it is completely up and running. When you see the green arrow in the virtual system dashboard, you can look in the virtual system details and note the following:
- IP address of the WebSphere Application Server virtual machine
- Hostname of the WebSphere Application Server virtual machine
- Script execution report. The Script Packages section of the details page lists all the
scripts associated with the virtual image. In our case, there should be two scripts. A green tick mark should be displayed against each script upon successful execution. You can click on the cloudburst_collect*.zip files to see the logs from your scripts.
Figure 4. Script execution results in the virtual system dashboard
Now that the virtual system is running, and the scripts have executed successfully, check to see if the Linux OS agent running on the WebSphere Application Server VM has been able to connect to the shared monitoring server. Log into your Tivoli Enterprise Portal at this url: http://<YOUR_ITM_IP>:1920///cnp/kdh/lib/cnp.html. You should see the hostname of your WebSphere Application Server VM show up under the Linux Managed Systems in the Navigator.
Figure 5. Automatic registration of Linux Managed System
You should see that the Linux OS agent is communicating with the monitoring server and providing monitoring data about CPU, Memory, File System and other valuable metrics, as shown in the figure below.
Figure 6. Linux OS Agent on virtual system reporting monitored data