IV99690: TIVOLI BUSINESS SERVICE MANAGER 6.1.1 DOCUMENTATION UPDATE FOR ESDA RULES.

APAR status

• Closed as documentation error.

Error description

• Product: IBM Tivoli Business Service Manager.
  Release: 6.1.1.4
  Severity: 3
  
  PROBLEM DESCRIPTION: Tivoli Business Service Manager
  documentation requires updating.
  
  The following link below to our TBSM documentation for ESDA
  rules needs to include ESDA rule limitations.
  
  https://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.i
  bm.tivoli.itbsm.doc_6.1.1/ServiceConfigurationGuide/bsmu_esdc_ru
  le_triggers.html
  
  Service Configuration Guide->ESDA rules->ESDAs overview->ESDA
  rule triggers.
  
  ESDA doesn't do automatic updates
  The chapter could also be re-edited towards invalidation and
  discovery
  
  We need to clearly explain ESDA automated triggering and say
  that ESDA isn't designed for automated service model generation
  but for dynamic service model generation on user action.
  
  For automatic service model generation, users need to use
  autopop rules
  
  dynamic means - clicking the plus icon and showing levels up or
  down in Relationships/Basic Relationships view in Service
  Viewer portlet in Service Administration and Service
  Configuration portlets.
  
  Another limitation that should be documented is this is not
  going to work with JazzSM/DASH. ESDA can be triggered only from
  TIP.
  
  Only from Service Navigator / Service Tree portlets by + icon
  and by setting levels up/down in Service Editor portlet.
  Invalidation and discovery is also important, because clicking
  on + icon or levels up/down will not show fresh data unless the
  service instance being clicked was set to invalid
  
  So it's dynamic only for invalid instances
  
  Valid instances will show what's currently in TBSM memory if
  user clicks +
  
  The discovery of the data source and showing fresh data will
  work only for invalid service instances.
  Then the properties like impact.sla.runesdasonstartup and
  impact.sla.onlymanualinvalidation are relevant.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  

Problem conclusion

• doc update
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels