<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DevCampTivoli Updates</title>
	<atom:link href="http://www.johnmwillis.com/tivoli/devcamptivoli-updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johnmwillis.com/tivoli/devcamptivoli-updates/</link>
	<description>JOHNMWILLIS BLOG</description>
	<lastBuildDate>Wed, 02 Jun 2010 23:53:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Toby Pass</title>
		<link>http://www.johnmwillis.com/tivoli/devcamptivoli-updates/comment-page-1/#comment-3129</link>
		<dc:creator>Toby Pass</dc:creator>
		<pubDate>Sat, 15 Mar 2008 00:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnmwillis.com/devcamptivoli/devcamptivoli-updates/#comment-3129</guid>
		<description>just to add ... ITM 6.x for dashboard views is very flexible, especially if you modify the style sheets.

However the advantages to TBSM 4.x, that I can see is:
proper severities colours for a service (ie yellow if 1 node out of 3 fails, orange if 2 nodes fail and red if all 3 nodes fail - however you can change that severity as it propogates up to reflect the actual business status - a good demonstration?

Also maintenance mode is a good feature.

The real power of TBSM though is being able to create business process views or operational dashboards from other datasources like CMDB&#039;s and for it to automatically make these changes on the fly as it re-reads the database - that would be worth demonstrating!

However I agree with Roberts views that ITM 6.x can create these views very quickly and considerably cheaper, all be it, a bit clunky depending on your screen resolution and the number of updates required to maintain the view and so long as you do not need to keep changing the background picture/gif/jpg etc.

Kind regards,
Toby Pass</description>
		<content:encoded><![CDATA[<p>just to add &#8230; ITM 6.x for dashboard views is very flexible, especially if you modify the style sheets.</p>
<p>However the advantages to TBSM 4.x, that I can see is:<br />
proper severities colours for a service (ie yellow if 1 node out of 3 fails, orange if 2 nodes fail and red if all 3 nodes fail &#8211; however you can change that severity as it propogates up to reflect the actual business status &#8211; a good demonstration?</p>
<p>Also maintenance mode is a good feature.</p>
<p>The real power of TBSM though is being able to create business process views or operational dashboards from other datasources like CMDB&#8217;s and for it to automatically make these changes on the fly as it re-reads the database &#8211; that would be worth demonstrating!</p>
<p>However I agree with Roberts views that ITM 6.x can create these views very quickly and considerably cheaper, all be it, a bit clunky depending on your screen resolution and the number of updates required to maintain the view and so long as you do not need to keep changing the background picture/gif/jpg etc.</p>
<p>Kind regards,<br />
Toby Pass</p>
]]></content:encoded>
	</item>
</channel>
</rss>

