IV67780: ´GENIDML.SH´ IMPORT/EXPORT CAPABILITIES AND LIMITATIONS.

6.1.0-TIV-BSM-FP0004-zlinux
6.1.0-TIV-BSM-FP0004-windows
6.1.0-TIV-BSM-FP0004-solaris
6.1.0-TIV-BSM-FP0004-linux
6.1.0-TIV-BSM-FP0004-aix
6.1.0-TIV-BSM-FP0003-solaris
6.1.0-TIV-BSM-FP0003-aix
6.1.0-TIV-BSM-FP0003-zlinux
6.1.0-TIV-BSM-FP0003-windows
6.1.0-TIV-BSM-FP0003-linux
IBM Tivoli Business Service Manager V6.1.0 Fix Pack 4(6.1.0-TIV-BSM-FP0004)

APAR status

• Closed as documentation error.

Error description

• The following 'addendum' needs to be included in the TBSM
  import/export documentation on How ´genidml.sh´ works:
  
  TBSM only exports:
  
   1. TBSM created services with the 'ServiceExport'
  attribute, as Business Systems or Business Applications
  (depending on the attribute setting)
  
   2. TBSM export relationships (only) from the services
  above, to services created via a TADDM import.
  
  TBSM will *not* export relationships created within TBSM
  
  3.  In order for newly added service instances to appear under
  the Service Component Repository (SCR), these must be
  invalidated first and the model tree refreshed.
  
  4. the recommended approach is to build tree in TADDM
  
  5. export will not export computer systems from TBSM to TADDM
  -only relationships (if the computer systems are TADDM
  generated)
  
  7. export only export Business Services and Applications.
  
  8. export from TBSM to TADDM must follow cmdb rules - i.e. A
  Functional Group is a child of an Application server.
  
  9. TBSM exported from TBSM into TADDM, will not be re-imported
  back into TBSM.
  
  10. The Service Component Registry tree is not automatically
  invalided.
  
  11. Services created in TBSM, exported to TADDM, will not be
  re-imported into TBSM by a bulk import.
  

Local fix

• script to add relationships manually using the GUID provided.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All TBSM Users                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Documentation for genidml lack clarity.                      *
  *                                                              *
  * genidml will not export services which were previously       *
  * imported from an iDML book, or from TADDM. It will only      *
  * export a relationship to these services.  Relationships to   *
  * TBSM created services, are only exported, if these TBSM      *
  * created services are exported.                               *
  *                                                              *
  * To summarize, TBSM exports:                                  *
  * 	1. TBSM created services with the ServiceExport attribute,  *
  * as Business Systems or Business Applications (depending on   *
  * the ServiceExport attribute setting)                         *
  * 	2. TBSM export relationships (only) from the services       *
  * above, to services created via a TADDM import.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The recommended approach is to build the service tree in     *
  * TADDM. TBSM can be used to update the structure with         *
  * Business Services and Business Applications.                 *
  ****************************************************************
  * Note, services can only be successfully imported into TADDM is
  the follow standard CMDB rules, for example a Functional Group
  is a child of an Application Server.
  
  * Services created in TBSM, exported to TADDM, will not be
  re-imported back into the same TBSM by a bulk import.
  
  * TBSM exports only Business Services and Business Applications.
  Non Business Application or Business Service TBSM Services,
  exported from TBSM, to TADDM, will not be imported into TADDM.
  This fails because the services were TBSM services, not TADDM
  created ones, and thus are missing vital information required by
  TADDM.
  
  * The Service Component Registry tree is not automatically
  invalided after a toolkit import. This tree must be manually
  invalidated.
  

Problem conclusion

• The TBSM documentation will be updated in the next documentation
  refresh.
  

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