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

Download Description

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

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 2

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 2:
IJ15123: WHEN CLICK A GRAPH IN TBSM CHARTING, ERROR IS  ATKRST100E AN UNEXPECTED ERROR OCCURED
IJ15391: TBSM 6.2: PRIMARY SERVICES RESTARTS DURING SECONDARY SERVER STARTUP INCLUDING RADSERVICES
WHICH SHOULDN'T BE ON THE LIST
IJ15605: SRVE0190E  FILE NOT FOUND  FILE NOT FOUND  /NETCOOL/STYLES/CLAROGRID.CSS CLARO.CSS AND DOJO.CSS
IJ15902: NOT FIGURING OUT THE DATA TYPE OF THE COLUMN
IJ16015: SCRIPT CHANGE + DOCUMENT NEEDED ON HOW TO IMPORT/EXPORT ALL DATA/CONFIGURATION FROM ONE TBSM SERVER TO  ANOTHER TBSM SERVER
IJ16133: TWA ERROR CTGBH0014E
IJ16587: REMOTETBSMSHELL THROWS AN EXCEPTION WHEN RUN IN TBSM IMPACT SERVER
IJ16909: CAN'T RUN MIGRATETADDMMODEL.SH REQUSTS TIP_HOME TO FIND THE WS_ANT
IJ17100: TBSM 62 WITH SSL ENABLED UNABLE TO FIND NAMESERVER.PROPS ON DASH
IJ17355: IMPORT FROM TADDM CREATES NO SERVICES IN TBSM
IJ17356: TOOLKIT COMMANDS COMPLAIN THAT DB2 11.1 IS LOWER VERSION THAN 9.5
IJ17688: TBSM SERVICE TREE WIDGET DOES NOT ACCEPT PAGELOAD OR NODECLICKEDON EVENTS AFTER TBSM 6.2 FIX PACK 1 IS INS
IJ18054: TBSM 6.2 SSL CONFIGURATION REQUIRES CHANGES TO SECURE_SERVER_CONFIG SCRIPT
IJ18587: ADDING TBSM_B TO EXISTING DASHBOARD SERVER CONFIG NOT DOCUMENTED
IJ19803: TBSM 6.2 MIGRATION FAILS WITH TYPEERROR JAVA.IO.INPUTSTREAMREADER IS NOT A FUNCTION IN EVAL
IJ20193: TBSM 6.2 TRYING TO EXPORT DATA FETCHERS GENERATES "EVALERROR  UNDEFINED ARGUMENT  POLICYNAME  AT LINE  8250"

List of TBSM APARs that have updates to the documentation:

IJ15670: DOCS DON'T DESCRIBE VALUES FOR NON-DEFAULT DATABASE LOCATION
IJ15837: TBSM 6.2.0 INSTALLING/CONFIGURING TBSM TO USE AN EXTERNAL LDAP USER REPOSITORY NEEDS UPDATING
IJ16015: DOCUMENT NEEDED ON HOW TO IMPORT/EXPORT ALL DATA/CONFIGURATION FROM ONE TBSM SERVER TO ANOTHER TBSM SERVER
IJ16587: TBSM FUNCTION TOPIC CLEAN UP
IJ17100: TBSM 62 WITH SSL ENABLED UNABLE TO FIND NAMESERVER.PROPS ON DASH
IJ17355: IMPORT FROM TADDM CREATES NO SERVICES IN TBSM
IJ18054: TBSM 6.2 SSL CONFIGURATION REQUIRES CHANGES TO SECURE_SERVER_CONFIG SCRIPT
IJ18106: TBSM 6.2 OVERRIDE TEMPLATE MAPPING DOES NOT WORK FOR COMPOSITE OBJECTS
IJ18587: ADDING TBSM_B TO EXISTING DASHBOARD SERVER CONFIG NOT DOCUMENTED
IJ18768: Remove this Doc page for 6.2 SLA data in the dependency view
IJ18824: DOC APAR FOR TBSM 6.2 CHANGE HOSTNAME PROCEDURE
IJ19609: THE TBSM DATASERVER INSTALLER ALWAYS FAILS WHEN TRYING TO VERIFY DASH AND OMNIBUS HOSTS
IJ19614: ENABLEAUDIT PROPERTIES ARE NOT DOCUMENTED
IJ19803: TBSM 6.2 MIGRATION FAILS WITH TYPEERROR JAVA.IO.INPUTSTREAMREADER IS NOT A FUNCTION IN EVAL

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

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

Fix Pack 2 includes the following enhancements:

1. IJ19803: TBSM 6.2 MIGRATION FAILS WITH TYPEERROR JAVA.IO.INPUTSTREAMREADER IS NOT A FUNCTION IN EVAL
When attempting to perform a TBSM_DataserverMigration, on an environment, where Impact has been upgraded to 7.1.0.14 (or higher), the migration logic will fail, due to the version of Java Impact is running (Java 8). To avoid the issue, a new TBSM_Dataserver_Migration_*.zip package is available.  This new TBSM_Dataserver_Migration_*.zip package can be found here (after the Fix Pack is unpacked):
<fp_package>/data_*/ TBSM_Dataserver_Migration_*.zip

2. Script to import TBSM object schema reports failure on AIX has been resolved in TBSM FixPack 2.
A new import_schema.sh script is now available, to allow for the import of TBSM object schema to function properly on AIX.  This new import_schema.sh script can be found here (after the Fix Pack is unpacked): <fp_package>/data_*/omnibus/schema_files

3. PI99524: RCE vulnerability in JSF SUNRI 1.2 used by WebSphere Application Server fix require update to web.xml file in TBSM Fixpack 2. The JSF SUNRI 1.2 code was updated to throw an exception when client side state encryption is not enabled.
See https://www-01.ibm.com/support/docview.wss?uid=ibm10725813 for more detail..

This Fix Pack added the following stanza to the the sla.war’s web.xml file:

<env-entry>
<env-entry-name>com.sun.faces.ClientStateSavingPassword</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>mynewfacespassword</env-entry-value>
</env-entry>
The updated web.xml file is located at the following location: {JazzSM_directory}/profile/installedApps/JazzSMNode01Cell/isc.ear/sla.war/WEB-INF/web.xml

To enable client side encryption in JSF SUNRI 1.2, specify the password for the com.sun.faces.ClientStateSavingPassword environment entry in the web.xml file of the application.
To bypass client side state encryption, set the following property to true: com.ibm.ws.jsf.bypassClientSideStateEncryption
The default is false. This property can be set either as a context-parameter in the web.xml of the application or as a JVM argument.
 

NOTE: IBM does not recommend using this property, encryption must be done to prevent a remote code execution vulnerability.Â
Therefore the above changes in the sla.war’s web.xml file, is to specify the password for the com.sun.faces.ClientStateSavingPassword environment entry.

If you are installing TBSM 6.2 as a new install of TBSM, then the web.xml file at the location listed below, will need to have the above changes in the file and you will not be required to edit the web.xml file manually:
{JazzSM_directory}/profile/installedApps/JazzSMNode01Cell/isc.ear/sla.war/WEB-INF/web.xml
{JazzSM_directory}/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/sla.war/WEB-INF/web.xm
 

If you are upgrading TBSM 6.2 to FP2 and using WebSphere 8.5.5.15, then you will need to manually edit the web.xml file at the location shown below, with the above changes: {JazzSM_directory}/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/sla.war/WEB-INF/web.xml

Note: if the above changes are not performed, an error exception may be produced on the UI Services Configuration page, under 'Tagged Services' table of Templates and 'Dependents' table of Services.

4. Additional Browser Support with Fix Pack 2 
Firefox ESR 68
Microsoft Internet Explorer 11
Microsoft Edge 44
Google Chrome 74 - 77
Safari 12 and 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.5
IBM Tivoli Netcool/OMNIbus 8.1.0.20
IBM Tivoli Netcool/OMNIbus Web GUI 8.1.0.17
IBM WebSphere Application Serve 8.5.5.15

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

Symptom: When the Impact Fix Pack 2 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 

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