
Title: 
------

   IBM® Tivoli® Business Service Manager Interim Fix Version
   4.1.0.0-TIV-BSM-IF0008  Revised 2008/01/30 


 ====================================================================

Date:
-----

   January 28, 2008

 ====================================================================

Copyright Notice:
-----------------

   © Copyright IBM Corp. 2008 All Rights Reserved.
                                                                   
   US Government Users Restricted Rights - Use, duplication or
   disclosure restricted by GSA ADP Schedule Contract with 
   IBM Corp.

 ====================================================================

Contents:
---------


   * Files that are included in this Interim Fix:

      - This README file (4.1.0.0-TIV-BSM-IF0008.README)
      - 4.1.0.0-TIV-BSM-IF0008.zip (Windows only)
      - 4.1.0.0-TIV-BSM-IF0008.tar (Unix variants)

     The files in the tar or zip file that will be installed 
     include the following, they will be installed in <TK_DIR>.

     <TK_DIR> = <NCHOME>/XMLtoolkit
     <NC_DIR> = <NCHOME>/guifoundation/webapps/sla/install
    
          <TK_DIR>/bin/setdbschema.ksh (Unix only)
          <TK_DIR>/bin/runsetup.sh (Unix only)
          <TK_DIR>/bin/tbsm_init_updates.sh (Unix only)
          <TK_DIR>/bin/tbsminitd.sh (Unix only)
          <TK_DIR>/bin/tbsmrdr_startd.sh (Unix only)
          <TK_DIR>/config/AttributeGlobal.filter
          <TK_DIR>/jars/ASICLTools.jar
          <TK_DIR>/sql/scc_processCreates.sql
          <TK_DIR>/sql/scc_processRefresh.sql
          <TK_DIR>/sql/scc_processDeletes.sql
          <TK_DIR>/sql/scc_staging_schema_setup.sql
          <TK_DIR>/sql/scc_staging_schema_index_deletes.sql
          <TK_DIR>/sql/scc_staging_schema_index_setup.sql
          <TK_DIR>/sql/scc_staging_schema_truncate.sql
          <TK_DIR>/sql/ComponentRegistryQueries.sql
          <TK_DIR>/xml/ScrConfig.xml
          <TK_DIR>/xml/ScrCommonTemplates.xsl
          <TK_DIR>/xml/ScrProducePostProcessingSql.xsl
          <TK_DIR>/xml/CDM_TO_TBSM4x_MAP.xml
          <TK_DIR>/xml/CDM_TO_TBSM4x_MAP_Templates.xml
          <TK_DIR>/xml/log/install/maintenance/IZ05790/iz05790.sh
          <TK_DIR>/xml/log/install/maintenance/IZ05790/iz05790.bat
          <TK_DIR>/xml/log/install/maintenance/IZ05790/iz05790-1.sql
          <TK_DIR>/xml/log/install/maintenance/IZ05790/iz05790-2.sql
          <NC_DIR>/BSM_Templates.radsh
          <NC_DIR>/BSM_TemplatesUpdateIF0008.radsh
          <NC_DIR>/BSM_TemplatesUpdateIF0008.sh <Unix only>
          <NC_DIR>/BSM_TemplatesUpdateIF0008.bat <Windows only>

 ====================================================================

About this Interim Fix:
------------------------------------

   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

   TBSM DOES NOT REFLECT DELETED RESOURCES IN TADDM BUSINESS APPS
   (164321)
   
   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.  
   
 ====================================================================

Installation, migration, upgrade and configuration information:
---------------------------------------------------------------

   * Hardware and software requirements:

      Refer to the TBSM 4.1 Release Notes for a full description
      of all the hardware and software requirements.


   * Dependencies:

      IBM Tivoli Business Service Manager Discovery Library toolkit
          Version 4.1
      IBM Tivoli Business Service Manager Version 4.1 IF0004
      IBM Tivoli Application Dependency Discovery Manager 
          5.1.1.3-TIV-ITADDM-IF0003
      IBM Tivoli Application Dependency Discovery Manager 
          defect 18917.1 and 20871. (recommended, see Note 1)
          
      Note 1:  Tivoli Application Dependency Discovery Manager defects
               18917.1,  and 20871 will resolve a number of issus 
               associated with data synchronization between TBSM and
               TADDM, primarily dealing with the deletion of objects.
               
               It is recommended that you apply these fixes.
               This list supersedes the list in earlier copies of this
               README.

   * Superseded fixes:

      Tivoli Busines Service Manager 4.1.0.0-TIV-BSM-IF0007.


   * Special considerations:

      Stop the TBSM Discovery Library toolkit:

      The installer will backup the TBSM files to the following
      location:
       
      <TK_DIR>/log/install/maintenance/backup/IF0008


   * Extracting this Interim Fix:
   
      On Windows:
      1. Copy the file 4.1.0.0-TIV-BSM-IF0008.zip to a temporary
         directory on your operating system.
      2. Unzip the file.

      On Unix:
      1. Copy the file 4.1.0.0-TIV-BSM-IF0008.tar to a temporary
         location on your operating system.
      2. Untar the files with the following command:
          tar -xvf 4.1.0.0-TIV-BSM-IF0008.tar 


   * Installing this Interim Fix:

      <Interim Fix> Refers to the directory where this Interim Fix
      resides (after you have extracted it from the zip/tar file).

      <NCHOME> Refers to the full path of the Tivoli Business 
      Service Manager installation directory on the server.

      On the Tivoli Business Service Manager server system:

       1. Ensure that the <NCHOME> environment variable is set. 

       2. The installer will look for a Java JRE 1.4.2.  If on
          step four below, the install is unable to locate Java,
          set JAVA_HOME as follows and then rerun step four.
          
          for Unix:

             export JAVA_HOME=$NCHOME/XMLtoolkit/_jvm/jre
             
          for Windows:
          
             set JAVA_HOME=%NCHOME%\XMLtoolkit\_jvm\jre
             
          A second option is to pass -is:javahome as an argument
          to the setup executable
          
          for Unix:
          
             4.1.0.0-TIV-BSM-IF0008-<os>.bin -is:javahome 
             $NCHOME/XMLtoolkit/_jvm/jre
             
          for Windows:
          
             4.1.0.0-TIV-BSM-IF0008-win32.exe -is:javahome 
             %NCHOME%\XMLtoolkit\_jvm\jre

       3. Navigate to the <Interim Fix> directory where the files
          were extracted.
      
       4. If you are on a Unix operating system, run the following
          command from a prompt:

             ./4.1.0.0-TIV-BSM-IF0008-<os>.bin
             
             where <os> is the appropriate operating system.

             Note:  The following warning may appear when starting
                    the installer, this can be ignored.
                    
               WARNING: could not write using log service:
               ServiceException: (error code = 200;
               message = "/var/log/Undefname_Undefpurpose.06091058 
               (Permission denied)";
               severity = 0;
               exception = [java.io.FileNotFoundException:
               /var/log/Undefname_Undefpurpose.06091058 
               (Permission denied)])
             
             Note:  If you are ssh'd into the server and either
                    do not have a console or can not export the
                    console back, then pass the -console option
                    to the installer.
                     
          If you are on a Windows operating system, run the following
          command from a prompt:

             .\4.1.0.0-TIV-BSM-IF0008-win32.exe

       5. Please see "Installation Prompts and Guidance" below for
          instructions to run the Interim Installer.

       6. Two post installation issues must be addressed before 
          restarting the toolkit.
          
          (1) If the TADDM 5.1.1.3 IF3 sdk jar files have not already
              been copied to TBSM, then the
                 ../dist/sdk/lib/*.jar 
              files on the TADDM server must be copied to the TBSM
              server and placed at:
                 $NCHOME/XMLtoolkit/sdk/lib
                 
          (2) The files CDM_TO_TBSM4x_MAP.xml and 
              CDM_TO_TBSM4x_MAP_templates.xml have been updated.
              See the information below in the "Installation
              Prompts and Guidance" section concerning these two 
              files.
              
          (3) In $NCHOME/XMLtoolkit/log/install/maintenance, check 
              policyUpdateIF0008.out to ensure that the policy was
              properly updated.  Please see 
              "policyUpdateIF0008.out Guidance" below for additional
              information about this file.
              
       7. Restart the Tivoli Business Service Manager Discovery 
          Library toolkit.

       8. Notes:
                a.) Files that are installed are backed up in 
                    <TK_DIR>/log/install/maintenance/backup/IF0008
                    directory.  If you encounter a problem after 
                    installing this fix and want to restore the old 
                    files, contact IBM service for instructions to
                    perform this operation.

                b.) The log, 4.1.0.0-TIV-BSM-IF0008_install.log, 
                    can be found in <TK_DIR>/log/install/maintenance.

                c.) After installation is complete, you may remove
                    <Interim Fix> to save space.
                    
 ====================================================================

Explicit relationship generation:
---------------------------------

 Previously the toolkit required that the TADDM property, 
 com.collation.topomgr.generateExplicitRelationship be set to true.
 IF0007 allowed the toolkit to optionally generate these relationships
 prior to importing the data from TADDM.  This moves the generation
 of these relationships from the time that the TADDM discovery is
 run to the time when the TBSM import is run.  
   
 The property DL_TADDM_ExplicitRelationship can be added to the 
 toolkit's property file xmltoolkitsvc.properties. If set to true, 
 then the relationships will be generated prior to each TBSM import
 of TADDM data.
 
 The default value for DL_TADDM_ExplicitRelationship is true.
 
 If you set DL_TADDM_ExplicitRelationship=false, then you must set 
 com.collation.topomgr.generateExplicitRelationship=true.       
 
 If you set DL_TADDM_ExplicitRelationship=true, then you should set 
 com.collation.topomgr.generateExplicitRelationship=false.  This is 
 the recommended configuration.
 
 The property com.collation.topomgr.generateExplicitRelationship is
 in TADDM's collation.properties file.
 
 ====================================================================

TADDM bulk copy option:
-----------------------
 
 IF0007 allowed you to specify that the toolkit process TADDM
 data using the PostgreSQL copy command.  This can dramatically 
 decrease the time required to move the data received from TADDM into
 the TBSM staging tables.  To enable this function, edit the 
 xmltoolkitsvc.properties file, and add the property: 
 DL_Xform_Use_BCP=true.
 
 The default value for DL_Xform_Use_BCP is false. 
 
 ====================================================================

Disable automatic polling:
--------------------------
 
 If the DL_PollIntervalSeconds in xmltoolkitsvc.properties is set to
 a value of zero or less, then the toolkit will not request data 
 from TADDM unless directed to do so by the cmdbdiscovery command.
 
 ====================================================================
 
Synchronize service tables (IZ05790):
-------------------------------------
 
 APAR IZ05790 is a two part fix.  The TBSM interim fix IF0009 contains
 code changes that will prevent two tables within the base server from
 getting out of synchronization.  IF0008 contains a script that will
 check the database for this condition and optionally repair the 
 tables.
 
 This only applies to customers running the TBSM XML toolkit.
 
 Run the script (or command file for windows):
 
 <TK_DIR>/log/install/maintenance/IZ05790/iz05790.sh -U <dbid> -f 1
 
 If the results contain zero rows, then your system does not contain
 the problem and you are finished.  If one or more rows is returned
 then the database needs to be repaired.  Before proceeding, backup
 your TBSM database.
 
 Next, stop the TBSM server and start the PostgreSQL database.  You 
 can do this either manually or run the script:
 
 <TK_DIR>/log/install/maintenance/IZ05790/iz05790.sh -U <dbid> -f 2
 
 With only the database running, issue the following command.  
 Note, the TBSM server process must be stopped when the following 
 command is issued.

 <TK_DIR>/log/install/maintenance/IZ05790/iz05790.sh -U <dbid> -f 3
 
 You can now start the TBSM server.  After the TBSM server has been
 started, login and invalidate the "Imported Business Service". 
 Invalidating this service will force the ESDA to run and rebuild
 the service component repository resources.
 
 ====================================================================
 
TBSM and TADDM integration paper:
---------------------------------

 A white paper, TBSM Integration with TADDM, is available on the TBSM
 support web page, click tecnotes.  The following URL will also take 
 you to it:
 
 http://www-1.ibm.com/support/search.wss?rs=3189&tc=SSSPFK
 &rank=8&dc=DB520+D800+D900+DA900+DA800+DB560&dtm
 
 This paper provides an overview of the integration between TBSM and
 TADDM.  It is highly recommended that the setup and configuration 
 sections of this document be reviewed.  The suggested recommendations
 can have a significant impact on performance.
 
 ====================================================================
 
Relationship changes in CDM_TO_TBSM4x_MAP.xml:
----------------------------------------------

 This fix contains changes to CDM_TO_TBSM4x_MAP.xml that will result
 in TBSM ignoring several relationships received from TADDM.
 
 The first change is associated with provides and routes. 
 
     changed: 
        <class type='cdm:provides' reversedirection='yes'/>                 
        <class type='cdm:routes' reversedirection='yes' /> 
     to: 
        <class type='cdm:provides' isDependency='false'/>                 
        <class type='cdm:routes' isDependency='false' /> 

 The second set of changes involved adding:
  
        <class type='cdm:systemDependency' isDependency='false'/>   
        <class type='cdm:ipDependency' isDependency='false'/>   
        
 It was found that these relationships were often between servers and
 not applications, resulting in the appearance that everything had
 a relationship with everything else.  Ignoring these relationships
 should provide a more meaningful topology.
 
 ====================================================================

policyUpdateIF0008.out Guidance:
--------------------------------

 This fix will update the template SCR_Servers_Unix.  The update uses
 radshell.  The output lacks a message that indicates success.  
 Generally if it fails it is fairly obvious.  Following is an example
 of a successful update.

 D:\download\tbsm41\images\service>type d:\IBM\Netcool\guifoundation\
  webapps\sla\install\BSM_TemplatesUpdateIF0008.radsh
  | d:\IBM\Netcool\bin\rad_radshell
 Using username: 
 ScriptedAPIClient Starting...
 ScriptedAPIClient: sessionID is root@mcormickt41_17005681_118239136633
 ScriptedAPIClient: host/port are null:null
 RADSoapUtil: url is http://mcormickt41:8080/sla/xml/
   jaxrpc/RADSoapFacadeIfc
 SoapRADClientFacadeImpl: in initializeStub for 12960684
 ScriptedAPIClient initialized RAD Facade with ID: 
  root@mcormickt41_17005681_1182391366334 ("rad")
 UserStore using endpoint: http://mcormickt41:8077/netcoolsecurity/
  NetcoolUserSecurityMgrSoapRqstIfc
 Security Mgr End point:http://mcormickt41:8077/netcoolsecurity/
  NetcoolUserSecurityMgrSoapRqstIfc
 NetcoolUser:getOID():user:admin
 ScriptedAPIClient initialized Security Manager Facade ("adminuser")
 ScriptedAPIClient: setting bsh prompt
 Initializing with: d:\ibm\Netcool\etc\rad\scriptedAPIStartup.bsh ...
 Sourcing startup file: d:\ibm\Netcool\etc\rad\scriptedAPIStartup.bsh
 Welcome to the RAD Shell.
 Enter help(); for help and Ctrl-D or exit(); to exit.
 BeanShell 1.3b2 - by Pat Niemeyer (pat@pat.net)
 radshell> radshell> 
 
 --------------------------------------------------------------------

 If the policyUpdateIF0008.out file indicates that the installer was
 unable to update the template, the update should be made by:
                    
 On Unix:

  cd $NCHOME/guifoundation/webapps/sla/install
  ./BSM_TemplatesUpdateIF0008.sh

 On Windows:

  cd %NCHOME%\guifoundation\webapps\sla\install
  BSM_TemplatesUpdateIF0008.bat
       
 ====================================================================

Known Limitations:
------------------
 1). Each TBSM import will request that TADDM update the relationship
     table for any new or changed resources since the last import.  
     This process uses a stored timestamp and the TADDM changeHistory 
     table to determine which resources need to be checked for 
     relationship updates.
     
     If TBSM is being added to an existing TADDM environment, there
     may be resources that are no longer in the changeHistory table,
     and therefore the relationships for these resources would not be
     built.  To ensure that this does not happen, run 
     "explicitrel.sh 0" on the TADDM server before running the first
     TBSM import.  Passing the "0" argument to this script will force
     TADDM to rebuild the relationships for all resources, not just 
     those in the changeHistory table.
     
     This limitation may also apply if TBSM has not imported data for
     an extended period of time and the TADDM changeHistory table
     has been pruned since the last TBSM import.  In this case, 
     run "explicitrel.sh 0" once to regenerate all of the relationships.
      
 2). Avoid running a TBSM import while TADDM business applications
     and business services are being updated via the TADDM UI.  If
     an UI update is being saved when a TBSM import is started, the
     relationship information displayed by TBSM for the edited business 
     application or business service may not be accurate.  Editing
     and saving the effected business application or service in TADDM,
     and then running another TBSM import will resolve this.
      
 ====================================================================

Installation Prompts and Guidance:
---------------------------------------------------------------

   * The following prompts occur when the installer is run in console
     mode (-console).
     
   * The suggested responses are provided between the arrows >> <<.  
     The alternatives to the default responses and/or descriptions of 
     the field are provided between the asterisks *** ***.
     
   * In the example below, the NCHOME environment variable is set to
     /home/tbsmbvt/IBM/Netcool.

---------------------------------------------------------------------
This process will install the IBM Tivoli Business Service Manager 4.1 
Discovery Library toolkit - IF0008.

Welcome to the InstallShield Wizard for IBM Tivoli Business Service 
Manager 4.1 Discovery Library toolkit - IF0008

The InstallShield Wizard will install IBM Tivoli Business Service 
Manager 4.1 Discovery Library toolkit - IF0008 on your computer.
To continue, choose Next.

IBM Tivoli Business Service Manager 4.1 Discovery Library toolkit
International Business Machines, Tivoli Systems
http://www.ibm.com


Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]

>>Hit Enter<<

---------------------------------------------------------------------
International Program License Agreement
     Part 1 - General Terms

     BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING THE 
     PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE 
     ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY
     OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE
     FULL AUTHORITY TO BIND THAT PERSON, COMPANY, OR LEGAL ENTITY 
     TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS,



- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE PROGRAM; AND



- PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY

Press Enter to continue viewing the license agreement, or, Enter "1" 
to accept the agreement, "2" to decline it or "99" to go back to the
previous screen, "3" Print, "4" Read non-IBM terms.
 
>>Enter 1<<

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]

>>Hit Enter<<

---------------------------------------------------------------------
Installation Notes:

Three post installation issues must be addressed.

(1) This fix includes updates to files that may have been customized. 
So as not to overwrite the customized files, the latest files are 
placed in the $NCHOME/XMLtoolkit/xml/install directory. The files 
are:
      - CDM_TO_TBSM4x_MAP.xml
      - CDM_TO_TBSM4x_MAP_Templates.xml

If the corresponding files in $NCHOME/XMLtoolkit/xml have not been 
customized, then simply copy the files from 
$NCHOME/XMLtoolkit/xml/install to the $NCHOME/XMLtoolkit/xml directory.

If you have customized either of these files, then the customization 
must be merged into the new files in the $NCHOME/XMLtoolkit/xml/install 
directory, and then saved/copied to the $NCHOME/XMLtoolkit/xml 
directory.

This must be completed before restarting the toolkit.

(2)If Tivoli Application Dependency Discovery Manager (TADDM) is used
as a data source, you must upgrade to TADDM 5.1.1.3 IF3
or later and copy the TADDM SDK jar files from the TADDM server to the
TBSM server. The TADDM jar files should be placed in 
$NCHOME/XMLtoolkit/sdk/lib on the TBSM server. The toolkit should be 
stopped when the files are copied.

(3)$NCHOME/XMLtoolkit/log/install/maintenance/policyUpdateIF0008.out,
check to ensure that the policy was properly updated.

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]

---------------------------------------------------------------------
IBM Tivoli Business Service Manager 4.1 Discovery Library toolkit - 
IF0008

Install Location

Please specify a directory or press Enter to accept the default 
directory.

Directory Name: [d:\IBM\Netcool\XMLtoolkit]

>>Hit Enter<<

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 

>>Hit Enter<<

***If the directory is not the directory where the toolkit was  ***
***installed, please provide the correct directory and hit enter***

---------------------------------------------------------------------
IBM Tivoli Business Service Manager 4.1 Discovery Library toolkit - 
IF0008 will be installed in the following location:

d:\IBM\Netcool\XMLtoolkit


for a total size:

 532.6 KB

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 

>>Hit Enter<<

---------------------------------------------------------------------
Installing IBM Tivoli Business Service Manager 4.1 Discovery Library 
toolkit - IF0008. Please wait...

---------------------------------------------------------------------
The InstallShield Wizard has successfully installed IBM Tivoli 
Business Service Manager 4.1 Discovery Library toolkit - IF0008. 
Choose Finish to exit the wizard.

Press 3 to Finish or 4 to Redisplay [3]

>>Hit Enter<<
---------------------------------------------------------------------
Date of Created/Revised by Creation/Update Summary of Changes 
------------------------------------------------------------------------
KM   1/22/08                                Document created 
------------------------------------------------------------------------
DK  1/30/09                                 TADDM fix number incorrectly listed. 
------------------------------------------------------------------------






 ====================================================================

Notices and trademarks:
-----------------------

   Notices:

    This information was developed for products and services offered 
    in the U.S.A. IBM may not offer the products, services, or 
    features discussed in this document in other countries. Consult 
    your local IBM representative for information on the products 
    and services currently available in your area. Any reference to 
    an IBM product, program, or service is not intended to state or 
    imply that only that IBM product, program, or service may be 
    used. Any functionally equivalent product, program, or service 
    that does not infringe any IBM intellectual property right may be
    used instead. However, it is the user’s responsibility to 
    evaluate and verify the operation of any non-IBM product, 
    program, or service.

    IBM may have patents or pending patent applications covering 
    subject matter described in this document. The furnishing of this 
    document does not give you any license to these patents. You can 
    send license inquiries, in writing, to:

    IBM Director of Licensing 
    IBM Corporation
    North Castle Drive
    Armonk, NY 10504-1785 U.S.A.

    For license inquiries regarding double-byte (DBCS) information, 
    contact the IBM Intellectual Property Department in your country 
    or send inquiries, in writing, to:

    IBM World Trade Asia Corporation
    Licensing
    2-31 Roppongi 3-chome, Minato-ku
    Tokyo 106, Japan

    The following paragraph does not apply to the United Kingdom or 
    any other country where such provisions are inconsistent with 
    local law:

    INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
    PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
    EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
    WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
    FOR A PARTICULAR PURPOSE.

    Some states do not allow disclaimer of express or implied 
    warranties in certain transactions, therefore, this statement 
    might not apply to you.

    This information could include technical inaccuracies or 
    typographical errors. Changes are periodically made to the 
    information herein; these changes will be incorporated in new 
    editions of the publication. IBM may make improvements and/or 
    changes in the product(s) and/or the program(s) described in this
    publication at any time without notice.

    Any references in this information to non-IBM Web sites are 
    provided for convenience only and do not in any manner serve as 
    an endorsement of those Web sites. The materials at those Web 
    sites are not part of the materials for this IBM product and use 
    of those Web sites is at your own risk.

    IBM may use or distribute any of the information you supply in 
    any way it believes appropriate without incurring any obligation 
    to you.
 
    Licensees of this program who wish to have information about it  
    for the purpose of enabling: (i) the exchange of information 
    between independently created programs and other programs 
    (including this one) and (ii) the mutual use of the information 
    which has been exchanged, should contact:

    IBM Corporation
    2Z4A/101
    11400 Burnet Road
    Austin, TX 78758 U.S.A.

    Such information may be available, subject to appropriate terms 
    and conditions, including in some cases payment of a fee.

    The licensed program described in this document and all licensed 
    material available for it are provided by IBM under terms of the 
    IBM Customer Agreement, IBM International Program License 
    Agreement or any equivalent agreement between us.

    Any performance data contained herein was determined in a 
    controlled environment. Therefore, the results obtained in other 
    operating environments may vary significantly. Some measurements 
    may have been made on development-level systems and there is no 
    guarantee that these measurements will be the same on generally 
    available systems. Furthermore, some measurement may have been
    estimated through extrapolation. Actual results may vary. Users 
    of this document should verify the applicable data for their 
    specific environment.

    Information concerning non-IBM products was obtained from the 
    suppliers of those products, their published announcements or 
    other publicly available sources. IBM has not tested those 
    products and cannot confirm the accuracy of performance, 
    compatibility or any other claims related to non-IBM products. 
    Questions on the capabilities of non-IBM products should be 
    addressed to the suppliers of those products.

    All statements regarding IBM’s future direction or intent are 
    subject to change or withdrawal without notice, and represent 
    goals and objectives only.

    This information may contain examples of data and reports used in 
    daily business operations. To illustrate them as completely as 
    possible, the examples include the names of individuals, 
    companies, brands, and products. All of these names are 
    fictitious and any similarity to the names and addresses used by 
    an actual business enterprise is entirely coincidental.

    COPYRIGHT LICENSE:

    This information may contain sample application programs in 
    source language, which illustrate programming techniques on 
    various operating platforms. You may copy, modify, and distribute 
    these sample programs in any form without payment to IBM, for the 
    purposes of developing, using, marketing or distributing 
    application programs conforming to the application programming 
    interface for the operating platform for which the sample 
    programs are written. These examples have not been thoroughly 
    tested under all conditions. IBM, therefore, cannot guarantee or
    imply reliability, serviceability, or function of these programs. 
    You may copy, modify, and distribute these sample programs in any 
    form without payment to IBM for the purposes of developing, 
    using, marketing, or distributing application programs conforming
    to IBMs application programming interfaces.


   Trademarks:

    The following terms are trademarks of International Business 
    Machines Corporation in the United States, other countries, or 
    both: IBM, IBM logo, Tivoli, Tivoli logo, AIX®, AOC/MVS™, APPN, 
    CICS®, CICSPlex®, CICS/ESA®, DB2®, DB2 Universal Database™, 
    DFSMShsm™, Domino®, DB2 Universal Database, IMS™, IMS/ESA®,
    Informix®, MQSeries®, MVS, MVS/ESA™, NetView®, NWays, OS/390®,
    RACF®, RMF™, SNA/APPN, SecureWay®, Tivoli Enterprise™, Tivoli
    Enterprise Console®, Tivoli Management Environment, TME 10™,
    VTAM®, WebSphere®, z/OS®.
 
    UNIX® is a registered trademark of The Open Group in the United 
    States and other countries.

    Microsoft®, Windows, Windows NT®, and the Windows logo are 
    trademarks of Microsoft Corporation in the United States, other 
    countries, or both.

    Java™ and all Java-based trademarks and logos are trademarks or 
    registered trademarks of Sun Microsystems, Inc. in the United 
    States and other countries.

    Pentium® is a registered trademark of Intel® in the United States 
    and other countries. Other company, product, or service names may 
    be trademarks or service marks of others.

 ====================================================================
