ā‰” Menu

Integrating TBSM 3.1 and TBSM 4.1 – An ESDA Solution

in Best Practices, Business Service Management, dashboard, E2E Service Management, IBM, Implementation, OPAL, Service Management, Service Modeling, TBSM, Tivoli, Usability, Visualization

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 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.

-snip-

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.

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.

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.

http://www.ibm.com/software/tivoli/opal?NavCode=1TW10BM02

Comments on this entry are closed.

  • NCC74656

    G’day Doug,

    Great website – very impressive. Very motivating.

    My question is:

    Can I use TBSM 3.1 ESDA to pull BSVs from the z/OS DLA ?
    the z/OS DLA (IDML File has the depency links/pointers in it – but I want to build BSVs in TBSM 3.1 derived from the z/OS DLA.

    Thx

    Why – (I want to include CICS Progs in the TBSM Discovery) – I have SA generic REXX Stub polling and sending CICS Prog events to TBSM 3.1).

  • Thanks for your kind comments!

    If you help me with all of the Mainframe and z/OS acronyms and terms you just rattled off and I’ll help you get things done in TBSM 4.x. šŸ™‚ I do not have any background in the mainframe area.

    I will email you offline and we can chat.

    Doug

  • prashanth

    Hi Doug,
    seasons greetings and happy new year,
    We are looking at possible solution to integrate TBSM with Atrium CMDB to pull all the CI and relationship data into TBSM for creating services, can you please help us understanding if this is possilble?
    regards
    Prashanth

  • Prashanth,

    While there is no direct integration, you have a few options to explore. First, take a look at the Atrium Integration Engine and see what you can use that for. Look towards exporting Atrium information into a new database with a simplified schema that allows you to use either TBSM Autopop or ESDA rules to build and maintain your service models. A more sophisticated approach could be using policy based TBSM webservices calls to interact with Atrium.

    If you need more help, feel free to reach out to me directly.

    Doug

  • Manish

    Hello I would like to confirm is there any way to make TBSM 4.1 Loggin automation?

  • Manish – can you share more on what you’d like to do? The only way I know is by embedding the username and password in the URL string.

    Doug

  • Manish

    Doug : What i want exactly i don’t want to put user name and password again n again in TBSM and when we enterted the password then it will take appx. 7-9 minutes to load the TBSM application in whichwe get the Alerts.So is there any way to decrease some time.

    Manish

  • Hmm, there may be a way to change the inactivity timeout stuff within NGF, but I’m not sure off the top of my head. If it’s taking 7-9 minutes for you to see the initial screen paint, you’ve got some other problem that should be addressed. You should see the default screen in less than a minute in most cases.

    Laptop/Desktop memory, JRE and browser version?
    Size of model in TBSM that you’re landing on when logging in?

    Doug

  • Manish

    Hello,
    Internet Version:6.0.2900.2180.xpsp_sp2_gdr_070227-2254. Desktop memory: 1.96 GB of RAM,JRE Version 1.5.0 (build 1.5.0_15-b04).Size of model in TBSM i couldn’t find it.