≡ Menu

Tivoli Business Service Manager (TBSM) v4.x Scorecard Customization

in Best Practices, Business Service Management, IBM, Implementation, Netcool/RAD, OPAL, TBSM, Tivoli, Usability, Value, Visualization

A new contribution to OPAL has been made for TBSM v4.x (any version of Netcool/RAD or TBSM v4.x) that discusses ways to customize the TBSM scorecard capability. Create custom linked actions, change icons, etc. within the RAD_GetTreeColumnValue.ipl policy for rendering within your scorecard.

Download available here.

-snip-

IBM Tivoli Business Service Manager (TBSM) allows users to view business service dependency models and monitor how events and other data affect those services in realtime.

The Service Tree view – sometimes referred to as the “Scorecard” – provides a powerful, consolidated view of service relationships, status, and key performance indicators (KPI), all displayed in a single “tree table” viewer. However, at times, it would also be useful to allow users the ability to “drill-down” into a specific status indicator or KPI, rather than the generic actions available only at the business service level. This would allow users to, for example:

* View the details of a specific KPI to see why it has degraded to the current level.
* Search a customer’s historical database for previous resolutions to a specific KPI scenario.
* Open a browser to customer-specific “RunBook” information on procedures to be carried out when a particular indicator is within a particular range, or has exceeded a particular value.
* Search the company’s Intranet or Internet for context-specific information related to the specific indicator or status for a given application.

This whitepaper describes customization that can be performed by customers to allow them to convert the static text or images into clickable hypertext links. The customer can specify the URL to launch to when the user clicks on a specific image or text in the Service Tree. Service-specific information can also be passed in to the URL as parameters.

Comments on this entry are closed.

Next post:

Previous post: