IBM Tivoli Business Service Manager V6.2.0 Fix Pack 3(6.2.0-TIV-BSM-FP0003)

Download Description

Before installing or upgrading Tivoli Business Service Manager Fixpack 3 refer to the following documentation:

• https://www.ibm.com/support/knowledgecenter/SSSPFK_6.2.0/com.ibm.tivoli.itbsm.doc/kc_welcome_tbsm.html

Download attached 6.2.0-TIV-BSM-FP0003.README file then review list of enhancements, pre-req, installation instruction and known issues in Tivoli Business Service Manager Fixpack 3.

1.0 Hardware and software requirements

For information about supported hardware and software, check the Software
Product Compatibility Reports (SPCR) here: https://www.ibm.com/software/reports/compatibility/clarity/index.html

Jazz for Service Management (JazzSM)
If JazzSM UI Services (DASH) is being used to visualize TBSM service model data, then the latest JazzSM fix pack should be installed after installing this TBSM FixPack.
See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=all
==========================================================================================

2.0  Summary of fixes  Fix Pack 3

-On Jan 21st 2021, certificates that IBM used to sign Java applets provided with IBM Tivoli Business Service Manager 6.2.0 will expire. This Fix Pack includes applet jars signed
with a newly issued certificate.

- TBSM Agent update - tmv630fp5

- For an individual APAR detail, go to https://www.ibm.com/support/home/ then enter the APAR name/# in "Search Support" then select search.

2.1 APARs Fixes delivered in Fix Pack 3:
IJ21471: WHEN SELECTING SERVICE FIRST TIME SERVICE DETAILS NOT UPDATED
IJ21765: TBSM 6.2.0 ERROR CTGTD1003E ERROR: _33D IS NULL
IJ22065: TBSM 6.2 RADSHELL FUNCTION FOR DISPLAYING ROOT SERVICES AND THAT CAN BE USED VIA TBSMSHELL IN A POLICY
IJ22338: TBSM 6.2 REMOVAL OF SERVICE INSTANCES WITH SLA TRACKING DOES NOT WORK WITHOUT DISABLING SLA
IJ23767: EXCEPTION RUNNING RADSHELL COMMANDS FROM A POLICY USING TBSMSHELL
IJ23769: RFE: RE-EVALUATION OF SERVICE AFFECTING EVENTS UPON IDENTIFICATION FIELD CHANGE
IJ24045: UNABLE TO SET DESIRED SLA FROM POLICY IN ESDA RULE
IJ24111: TBSM VERSIONINFO SCRIPT MISSES OUT ../IMPACT/LIB3P/NCS.JAR VERSION INFO
IJ25855: SECURITY APAR: PEN TEST CACHEABLE HTTPS RESPONSE IN TBSM 620
IJ26460: THE SLAPRUNE POLICY IS MISSING FROM TBSM 6.2

List of TBSM APARs that have updates to the documentation:
IJ20724: ALL CUSTOMER USEABLE RADSHELL FUNCTIONS SHOULD BE DOCUMENTED
IJ21870: RADSHELL FUNCTION ADDINTERNALATTRIBUTETOTEMPLATE NOT FULLY DOCUMENTED
IJ23856: ADDESDARULE: USE OF ALLORGNODEFIELDS FOR ADDITIONAL PARAMETERS
IJ24215: TBSM ESDA RELATED DOC CHANGES REQUIRED
IJ26344: SET BYPASSVALIDATION TO TRUE IF LDAP WITH AN ACTIVE DIRECTORY SERVER IS BEING ENABLED

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

3.0 New support and features added in TBSM 6.2.0.Fixpack 3

Fix Pack 3 includes the following enhancements:

- Updated TBSM 6.2.0 signed certificates, with a 2022 expiration year.
This fix addresses the TBSM Certificate expiry, which has a date of January
21, 2021

- IJ23769: RFE: RE-EVALUATION OF SERVICE AFFECTING EVENTS UPON IDENTIFICATION FIELD CHANGE
In current implementation, when Identification field values for service instance in TBSM were changed, events that had
been previously identified and bound to service instance will continue to affect service instance status until they are 
deleted from ObjectServer, despite not matching any current Identification Field values.
TBSM will now perform a reevaluation of service affecting events upon Identification Field change.
Setting impact.sla.replayeventsonidentificationfieldchange=true will ensure that TBSM re-evaluates
the event matches for the changed service.
If previously matched events no longer apply, then they are removed from the service.
To enable this function, you need to add following line to this file on the backend server <INSTALL DIR>/etc/TBSM_sla.props:
 impact.sla.replayeventsonidentificationfieldchange=true
The property change requires a server restart for it to take effect.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=139305

- RFE139802: "NO SLA TRACKING" OPTION FOR INDIVIDUAL SERVICE INSTANCES

In current implementation of TBSM, if any custom SLA level is defined for a template and any thresholds are enabled 
(such as Duration), all service instances created with Standard SLA will begin tracking Standard SLA.
This means it is not possible to have service instances belonging to the same template with and without SLA at the same time.
The following has been added to the TBSM 6.2.0 Service Configuration Guide:
Disable SLA tracking
This topic describes how to disable SLA tracking.
If any SLA level is enabled in a template (for example, Cumulative Duration), all service instances created using the template with Standard
SLA will begin tracking Standard SLA.  To specify that no SLA tracking should occur for a specified service instance, the Service Level for the
service can be set to None. To do this, set the property below to true in the sla.props file on the Data Server and on the DASH Server.
impact.sla.noslatracking=true
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=139802

- New Service Instance command: prinCountOfServiceInstances
Refer to the following section of the TBSM Administrator's Guide:
https://www.ibm.com/support/knowledgecenter/SSSPFK_6.2.0/com.ibm.tivoli.itbsm.doc/adminguide/bsma_shlr_printcountofserviceinstances.html

- TBSM 6.2 now supports IBM Cognos Analytics 11.x for TBSM Historical Reports.
Refer to the following link for information related to Installation and how to migrate Tivoli Common Reporting v3.1.x to Cognos v11.x
https://www.ibm.com/support/knowledgecenter/SSSPFK_6.2.0/com.ibm.tivoli.itbsm.doc/installguide/bsmi_t_installing_historical_reporting.html#bsmi_t_installing_historical_reporting__connecting

4. Additional Browser Support with Fix Pack 2 
Firefox ESR 68
Microsoft Internet Explorer 11
Microsoft Edge 44
Google Chrome 74 - 77
Safari 13

5. Support for the following Operating Systems is now available
Windows Server 2016, 2019
RHEL 7.7
RHEL 8

6. Support for the following components is available
DB2 Version 11.1.2.2
JazzSM 1.1.3.0 DASH 3.1.3.7
IBM Tivoli Netcool/OMNIbus 8.1.0.22
IBM Tivoli Netcool/OMNIbus Web GUI 8.1.0.19
IBM WebSphere Application Serve 8.5.5.17

The Impact Fix Pack 2 Update or Rollback process, will fail if the TBSM XMLToolkit service is running.

Symptom: When the Impact Fix Pack 3 Update and Rollback is run, while the XMLToolkit service is active (on Windows), 
the following message will be generated on the Installation Manager Update Failed window:
Error during “install/rollback” phase:
Deleting files from C:\*\tbsm\XMLToolk\_jvm
Failed to delete C:\*\tbsm\XMLToolk\_jvm\jre\bin\classic\jvm.dll
Root Cause: On a Windows environment, the files are locked by the operating system, whenever they are in use. This prevents the installer from removing or changing files.
Resolution: Stop the “Tivoli BSM Discovery Library toolkit” (or XMLToolkitSvc.exe) service and re-attempt the Update or Rollback process.
For a complete list of Known Limitations, please refer to the following link: 
https://www.ibm.com/support/knowledgecenter/SSSPFK_6.2.0/com.ibm.tivoli.itbsm.doc/kc_welcome_tbsm.html 

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