The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Monitor virtual systems on IBM SmartCloud Application Workload Service

Hook up your virtual system patterns to an IBM Tivoli Monitoring server

Revathi Subramanian, Senior Software Engineer, IBM Corporation

Revathi Subramanian is a senior software engineer in IBM research. Her areas of research include service oriented architecture, cloud computing and SaaS frameworks. Revathi has worked with many IBM development teams including WebSphere, Lotus, Rational and Tivoli to drive adoption of research technologies into products and service engagements.

Summary: IBM® SmartCloud Application Workload Service is one of the services available in the IBM Platform as a Service offering in IBM SmartCloud Enterprise. The Workload Service uses IBM Workload Deployer technology as its underpinning to deploy virtual applications and virtual systems to the IBM SmartCloud Enterprise. At the time of this writing, IBM Workload Deployer does not provide monitoring for virtual system patterns. If you want to hook up your virtual system patterns to an IBM Tivoli® Monitoring server, this tutorial shows you how.

Date: 16 Oct 2012
Level: Intermediate
PDF: A4 and Letter (420 KB | 13 pages)Get Adobe® Reader®

Activity: 6566 views
Comments:

Step 3: Associate the script packages with virtual image parts

Its time to attach the script packages to a virtual system pattern.

Click Patterns >Virtual Systems.
Click the Add icon plus sign to create a new virtual system pattern. Enter the name WebSphereWithMonitoring.
Click OK.
On the right panel, select the Edit icon to display the Pattern Editor.
On the left panel, from the Parts selection, drag the IBM WebSphere® Application Server v7.0 for IWD part and drop it on the canvas.
On the left panel, select Script Packages.
Drag the InstallJava script package and drop it on top of the WebSphere part that is already on the canvas. Repeat for the InstallOSAgent script package.
Make sure that the order of the scripts is correct. InstallJava must be first in the execution order followed by InstallOSAgent, so that Java can be installed prior to installing the OS Agent. If you need to change the order, click the Ordering link in the Pattern Editor.
On the canvas, click the Edit Parameter icon for the InstallOSAgent script package. This opens a window. Enter or edit the value for the TEMS_IP variable (this is the IP address of your monitoring server). If you don't want this value to be changed by anyone upon deployment, lock the field by clicking the lock icon alongside TEMS_IP in the window.
Click Done Editing on top of the canvas to save the virtual system pattern and exit the Pattern Editor.