{"id":394,"date":"2007-06-28T14:49:21","date_gmt":"2007-06-28T18:49:21","guid":{"rendered":"http:\/\/dougmcclure.net\/blog\/2007\/06\/integrating-tbsm-31-and-tbsm-41-an-esda-solution\/"},"modified":"2007-06-28T14:55:43","modified_gmt":"2007-06-28T18:55:43","slug":"integrating-tbsm-31-and-tbsm-41-an-esda-solution","status":"publish","type":"post","link":"https:\/\/dougmcclure.net\/blog\/2007\/06\/integrating-tbsm-31-and-tbsm-41-an-esda-solution\/","title":{"rendered":"Integrating TBSM 3.1 and TBSM 4.1 &#8211; An ESDA Solution"},"content":{"rendered":"<p>A new Tivoli OPAL submission today for Tivoli Business Service Manager (TBSM) 4.1.  This package introduces a method for leveraging the legacy Tivoli Business Systems Manager (TBSM) 3.1 backend with the new TBSM 4.1 front end to make use of the more advanced visualization and management capabilities within TBSM 4.1.<br \/>\n<em><strong><br \/>\nYou should review this even if you do not have the legacy TBSM 3.1 as there are some really good things in here related to TBSM 4.1 ESDAs, custom scorecards and even incorporating custom icons into the TBSM 4.1 system.<\/strong><\/em><\/p>\n<p>-snip-<\/p>\n<p>The IBM Tivoli Business Systems Manager (TBSM 3.1) ESDA feature is designed as an aid for representing TBSM 3.1 Business System folders in an IBM Tivoli Business Service Manager (TBSM 4.1) system. The feature utilizes the External Service Dependency Adapter (ESDA) capabilities of TBSM 4.1 to accomplish this task. This feature of TBSM 4.1 incorporates knowledge of the TBSM 3.1 database schema that would not generally be known to a customer trying to develop this capability on their own.<\/p>\n<p>The TBSM 3.1 ESDA feature provides rules that will retrieve high level TBSM 3.1 business system folders and create service instances in TBSM 4.1. This helps preserve the customer investment in building the TBSM 3.1 business systems tree by reflecting at least the executive level business systems in a TBSM 4.1 service model. In addition, the TBSM 3.1 status can be reflected on the 4.1 services. Thus, TBSM 3.1 and TBSM 4.1 can be run in parallel and will stay consistent with regards to the high level service content and status.<\/p>\n<p>Beyond simply reproducing the TBSM 3.1 high level service model, this feature exposes the model to all the many capabilities that TBSM 4.1 has to offer. By exploiting the SLA, data integration, and visualization capabilities of 4.1, TBSM 3.1 executive users can be provided with a greatly enriched Executive Dashboard.<\/p>\n<p>http:\/\/www.ibm.com\/software\/tivoli\/opal?NavCode=1TW10BM02<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A new Tivoli OPAL submission today for Tivoli Business Service Manager (TBSM) 4.1. This package introduces a method for leveraging the legacy Tivoli Business Systems Manager (TBSM) 3.1 backend with the new TBSM 4.1 front end to make use of the more advanced visualization and management capabilities within TBSM 4.1. You should review this even [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36,26,44,28,38,37,100,93,91,95,39,103,56],"tags":[],"class_list":{"0":"post-394","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-best-practices","7":"category-business-service-management","8":"category-dashboard","9":"category-e2e-service-management","10":"category-ibm","11":"category-implementation","12":"category-opal","13":"category-service-management","14":"category-service-modeling","15":"category-tbsm","16":"category-tivoli","17":"category-usability","18":"category-visualization"},"_links":{"self":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/comments?post=394"}],"version-history":[{"count":0,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/394\/revisions"}],"wp:attachment":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/media?parent=394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/categories?post=394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/tags?post=394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}