Two new IF’s are available for our TBSM clients who use the XML Toolkit integration with TADDM. These IF’s address all currently known issues with the integration. Be sure that you also update your TADDM installation!
TBSM 4.1 IF008
TBSM 4.1.1 IF003
—snip for TBSM 4.1.1 IF 003—
IZ12647 – Incorrect representation of TADDM functional groups
IZ05790 – Looping condition in Imported Business Service tree
IZ12344 – Loop in the service tree with an NFSService
NCORRECT REPRESENTATION OF TADDM FUNCTIONAL GROUPS (IZ12647)
After editing a TADDM business application, and removing members of a functional group, a delta import does not removed the objects from the TBSM service.
TADDM will send an update for a functional group the first time that a resource is added to the functional group. If the resource is removed from a functional group, and then later added again, an update is not sent. This results in the functional group not being added back into the service in TBSM.
LOOPING CONDITION IN IMPORTED BUSINESS SERVICE TREE (IZ05790)
TBSM loses the knowledge that a resource was built from an ESDA; after which, when the service component repository informs the base TBSM server that a resource no longer exists, the base server ignores the information and leaves the resource as is. This only applies to customers that have upgraded from TBSM 4.1.
LOOP IN THE SERVICE TREE WITH AN NFSSERVICE (IZ12344)
Business services containing an NFSService object contain a loop between the computer system and the NFSService.
—snip for TBSM 4.1 IF 008—
This version provides fixes to IBM Tivoli Business Service Manager 4.1 Discovery Library toolkit. This fix supercedes 4.1.0.0-TIV-BSM-IF0007, and therefore includes the fixes that were in IF0007.
* Fixes that are included from IF0007:
164321 – TBSM does not reflect deleted resources in TADDM business applications
IY98472- Problems handling deleted base classes in TADDM metadata.
IY99645- Performance improvements for TADDM imports
163212 – Namespace missing from WSPort
164995 – DL_TmpFile_CleanupInterval min value set to 4320
165159 – DB2 resources from latest zOS DLA are not displayed
164321 – TBSM DOES NOT REFLECT DELETED RESOURCES IN TADDM BUSINESS APPS
Resources that are removed from business applications in TADDM are not removed from the service views in TBSM following a bulk import.
PROBLEMS HANDLING DELETED CLASSES IN TADDM METADATA (IY98472)
TBSM maintains a list of classes that it collects from TADDM. Recent fixpacks to TADDM have implemented changes in the common data model, these changes included the deletion of classes that previously existed. TBSM continued to query for information on the deleted classes, resulting in exceptions that stopped processing.
PERFORMANCE IMPROVEMENTS FOR TADDM IMPORTS (IY99645)
This fix implements a number of changes to the methods used to import data from TADDM. These changes require that TADDM be at 5.1.1.3 FP3 or higher.
NAMESPACE MISSING FROM WSPort (163212)
WSPort objects missing namespace attribute because of method of checking object types using base class attribute list.
DL_TmpFile_ClenaupInterval MIN VALUE SET TO 4320 (164995)
The minimum allowed value for DL_TmpFile_ClenaupInterval has been changed to 4320 seconds (3 days). This was changed to ensure that data would be maintained for problem determination.
DB2 RESOURCES FROM LATEST ZOS DLA ARE NOT DISPLAYED (165159)
Changes in the latest zOS DLA resulted in DB2 resources not being processed correctly.
* Fixes that are included for IF0008:
IZ05787- TADDM Integration – dependency relationship problem
IZ05314- ITM data load causes all TBSM UI resources to disappear
IZ05790- Looping condition in Imported Business Service tree
IZ12344- Loop in the service tree with an NFSService
TADDM INTEGRATION – DEPENDENCY RELATIONSHIP PROBLEM (IZ05787)
TBSM loses the knowledge that a resource was built from an ESDA after which, when the service component repository informs the base TBSM server that a resource no longer exists, the base server ignores the information and leaves the resource as is.
ITM DATA LOAD CAUSES ALL TBSM UI RESOURCES TO DISAPPEAR (IZ05314)
Data received causes the dependency counters in the service component respository to be reset to zero. This causes the ESDA to stop traversing the dependency since it appears the the Imported Business Service does not have any dependencies/children.
LOOPING CONDITION IN IMPORTED BUSINESS SERVICE TREE (IZ05790)
This is closely related to IZ05787. Relationships received from TADDM create a looping where by two resources are dependent on each other. The XML was customized to ignore the relationships in one direction, breaking the dependency loop, but after invalidating, the UI continued to show the looping dependencies for some resources but not all. This was caused by the loss of knowledge as to the source of the resource’s discovery.
LOOP IN THE SERVICE TREE WITH AN NFSSERVICE (IZ12344)
Business services containing an NFSService object contain a loop between the computer system and the NFSService.