IBM Support

IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)

Download


Abstract

This Fix Pack addresses problems reported in IBM Tivoli Business Service Manager 6.1.1

Download Description


*************************************************************
* A change introduced by this Fix Pack might negatively
* affect existing product function.
*
* Please refer to APAR(s) IV91142 for a description of the
* problem(s) and corrective action(s). APAR IV71513 introduced in FP3
* may affect performance in rare circumstances.
*
* Evaluate these APARs for the potential impact in your environment.
*************************************************************
IBM Tivoli Business Service Manager 6.1.1
Fix Pack Version 6.1.1-TIV-BSM-FP0004


Readme file for: IBM Tivoli Business Service Manager
Product/Component Release: 6.1.1
Update name: Fix Pack 4
Fix ID: 6.1.1-TIV-BSM-FP0004
Publication Date: April 30, 2016
Last modified date: April 27, 2016
Online version of the readme file:
http://www.ibm.com/support/docview.wss?uid=swg24039742

Attention: You can always find the most current version of the readme file online.


Contents

1.0 Files included in this Fix Pack
2.0 Hardware and software requirements
3.0 Installation information
3.1 Dependencies
3.2 Prerequisites
3.3 Special considerations and Notices
3.4 Superceded Fixes
3.5 Extracting Fix Pack files
3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX
3.5.2 Extracting on Windows platforms
3.5.3 Fix pack directories
3.6 Maintenance upgrade strategy
3.6.1 Example maintenance scenario
3.7 Installation
3.7.1 Installing the Fix Pack
3.7.2 Discovery Library Toolkit
3.8 TBSM agent
3.9 Uninstalling the Fix Pack
3.10 Recovering from a failed Fix Pack install
3.11 Restoring failed DE upgrade from backup
3.12 "Service Level Objectives (SLO) Reporting" function
4.0 Additional information for TBSM Fix Pack 2 APARS
4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS
4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING
ON RADEVENTSTORE
4.3 Adding the new "Delete Service Instance" menu action
5.0 List of APARs
5.1 TBSM 6.1.1 Fix Pack 4 APARS
5.2 TBSM 6.1.1 Fix Pack 3 APARS
5.3 TBSM 6.1.1 Fix Pack 2 APARS
5.4 TBSM 6.1.1 Fix Pack 1 APARS
5.5 Tivoli Integrated Portal
5.6 Jazz for Service Management (JazzSM)
6.0 New support and features
6.1 TBSM 6.1.1 Fixpack 4
6.2 TBSM 6.1.1 Fixpack 3
6.3 TBSM 6.1.1 Fixpack 2
6.4 TBSM 6.1.1 Fixpack 1
6.5 Additional Browser Support with Fixpack 4
6.6 Additional Browser Support with Fixpack 3
6.7 Additional Browser Support with Fixpack 2
6.8 eWAS Fixes and Upgrades
6.9 OMNIbus 8.1
6.10 DB2
6.11 TADDM 7.3 Integration
7.0 Known issues
7.1 Some date options in TBSM Reports do not work
7.2 Issues creating wire between Service Tree and Active
Event List (AEL)
7.3 TBSM Agent Chart title differs from name in the
drop down list
7.4 Minimize-restore does not restore to correct size for
Service Navigation->Data Fetchers on Internet Explorer(IE) 9
7.5 Portlets covering content in a free form page
7.6 Creation and deletion of Services and Templates that contain
special characters
7.7 WEBSERVICES SECURITY NOT FUNCTIONAL
7.8 If using WEBSERVICES SECURITY (WSS) user authentication
7.9 Microsoft Internet Explorer 11
7.10 With certain Solaris installations the Event Summary portlet
may fail render
7.11 TIP Portlet blank or does not load after TIP 2.2.0.15
installation
7.12 TIP chart portlet blank if TBSM Service Admin page is
closed and re-opened
7.13 TBSM integration with ISM is no longer operational
7.14 Java Security Warnings
8.0 Copyright and trademark information


=======================================================================
1.0 Files included in this Fix Pack
-------------------------------

Fix Pack 4 addresses the problems that have been reported in IBM®
Tivoli® Business Service Manager version 6.1.1. The following table
contains a list of files included in this Fix Pack and operating systems
associated with these files:

+---------+----------------------------------------------------------------+
| Platform| File |
+---------+----------------------------------------------------------------+
| AIX® | 6.1.1-TIV-BSM-FP0004-aix.tar |
| | |
+---------+----------------------------------------------------------------+
| Linux® | 6.1.1-TIV-BSM-FP0004-linux.tar |
| | |
+---------+----------------------------------------------------------------+
| Solaris | 6.1.1-TIV-BSM-FP0004-solaris.tar |
| | |
+---------+----------------------------------------------------------------+
| Windows®| 6.1.1.-TIV-BSM-FP0004-windows.zip |
| | |
+---------+----------------------------------------------------------------+
| zLinux | 6.1.1-TIV-BSM-FP0004-zlinux.tar |
| | |
+--------------------------------------------------------------------------+
|all platforms| 6.1.1-TIV-BSM-FP0004.README |
+-------------+------------------------------------------------------------+
|all platforms| 6.1.1-TIV-BSM-FP0004.README_Translated.zip |
+-------------+------------------------------------------------------------+


Note: Whenever <ARCH> is used in the text of this readme, as part of the
filename of the Fix Pack package, it refers to, and can be
substituted for one of the following operating systems:
* Linux
* Solaris
* AIX
* Windows
* zLinux

The following files have been updated or replaced by this Fix Pack.

Added files on the Data Server:
ObjectServer_DS_config.ant
tbsm_generic_ant_caller.bat
tbsm_generic_ant_caller.sh
TBSM_BusCompCreateShadows.js
TBSM_BusCompPlaceAllCIsByIdentifier.js
TBSM_BusCompShadowTechnologyGroups.js
TBSM_ResEnrichReaderRecycle.js
ApplyPoliciesFor611FP4
BSM_TemplateUpdates611FP0004.radsh
setJVMSettings.jy
setJVMSettings.bat
setJVMSettings.sh
smack-3.3.0.jar
smackx-3.3.0.jar
org.apache.axis2-woden.jar
ipa-1.0-20120430.jar
TDWHistory.xml
Files under tbsm/tools directory

Replaced files on the Data Server:
ASQLStore.class
BSM_Templates.radsh
BSM_Templates_updatepropagation.radsh
BSM_Templates_templates_only.radsh
BSM_Templates_instances_only.radsh
canvasOpenURLActions.xml
collect_logs.ant
fo_config.ant
fo_data_config.ant
tbsm_consistency.zip
setTraceLevel.jy
scriptedAPIStartup.bsh
MigrateUserActionscanvasDynamicSubMenuActions_X.xsl
MigrateUserActionscanvasOpenURLActions_X.xsl
tbsm_viewDefinitionFiles.lst
tbsmDataImport.xml
VisualRepresentationAttributes.xml
av.jar
tbsm-info.jar
itmdataclient.jar
maintcli.jar
ncs.jar
tbsm-jviews.jar
ncsagent.jar
ncsSoapClient.jar
ncChartComponent.jar
new-server.xml
RAD_namevalidator.props
TBSM_BusCompPlaceAllCIsByAttr.js
TBSM_markerChangeProvider.ipl
TBSM_ResEnrichMain.js
TBSM_SLAUpdateServiceEvent.ipl
TBSM_AV_GetColorForSeverity.ipl
update-ear.py
versioninfo.bat
versioninfo
verutil.jar
Files under tbsm/contrib/gistools

Replaced Impact files on the Data Server:
nciJmxClient.jar
nci.jar

Removed from all servers:
AdventNetSnmp-4.jar


If you have made changes to the above mentioned files you will
find your copy of the file under:

- Copy of scriptedAPIStartup.bsh (scriptedAPIStartup.bsh.orig)
can be found in the same directory as the original.
- The copy of the files can be found in the following
directory:
[InstallDirectory]/
tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0004/data


If Service Level Objectives (SLO) Reporting was previously deployed,
then the following policy files will also be overwritten by this Fix
Pack:

TBSM_createBusinessCalendarDefn.js
TBSM_createServiceDefinition.js
TBSM_recordSLAMetric.js
TBSM_serviceDowntimeBasedOnTBSMStatusChange.js
TBSM_slaDefGlobalSettings.js
TBSM_serviceDefinition.js
TBSM_db2GetData.js
TBSM_getDataFromTBSMAvailability.js
TBSM_BusinessCalendar.js


---
Added files on the Dashboard Server:
ObjectServer_DS_config.ant
tbsm_generic_ant_caller.bat
tbsm_generic_ant_caller.sh
about_icon22.png
about_thumb.png
setJVMSettings.jy
setJVMSettings.bat
setJVMSettings.sh

Replaced files on the Dashboard Server:
canvasviewer_simple.html
tbsm-jviews.jar
tbsm-symbol-palette.jar
rad_nodes_links.css
LaunchTBSM.nova
RAD_help_eclipse.props
RAD_sla.props
RAD_namevalidator.props
serviceTreePortletView.jsp
serviceNavigatorPortletView.jsp
CreateDBPoller.jsp
ActionLoader.jsp
delete_template.jsp
About.jsp
esda_model.jsp
actionLoader.jsp
serviceViewerPortletView.jsp
autopop_config.jsp
ChartInstanceChooser.jsp
ism_instances.jsp
instanceuserpreferences.jsp
main_ruleset_id_fields.jsp
main_ruleset_rules_list.jsp
main_rulesets_output.jsp
main_rulesets_rules.jsp
main_rulesets_sla.jsp
serviceTreePortletEdit.jsp
serviceViewerPortletEdit.jsp
taguserpreferences.jsp
InstanceCustomizerWizard.jsp
EventRawAttributeSelector.jsp
TBSMCMPopup.jsp
BIRTChartConfig.jsp
columnProperties.jsp
dependency_rule.jsp
EditDBPollerFrames.jsp
ErrorMessageHandler.jsp
main_content.jsp
main_ruleset.jsp
main_rulesets_security.jsp
main_service.jsp
main_service_security.jsp
main_tabs.jsp
main_view.jsp
ServiceInstanceDependents.jsp
LaunchDataBrowser.jsp
rawattributeWizard/raw_event_table_fragment2.jsp
RAD_AV_GetColorForSeverity.ipl
radlabels*.properties
ncs.jar
ncsSoapClient.jar
ncChartComponent.jar
av.jar
itmdataclient.jar
ipa-1.0-20120430.jar
itmdataclient.jar
nci.jar
nciClient.jar
ncCommon.jar
tbsm-info.jar
web.xml
collect_logs.ant
fo_config.ant
fo_data_config.ant
Policies.jsp
TypeBrowser.jsp
impactAdmin.properties
ROIEffReportIWidget.xml
setTraceLevel.jy
versioninfo.bat
versioninfo
verutil.jar
Files under impactAdmin.war/scripts
Files under sla.war/dojo
Files under sla.war/audit/dojo
Files under sla.war/rad/debug
Files under twa.war/dojo
RAD_dashboard_dataprovider.props
timeSeriesSearchDialog.jsp
timeSeriesPortletView.jsp
tbsm-ltwd-server.jar


Replaced Impact files on the Dashboard Server:
nciClient.jar
nciJmxClient.jar
NCICLUSTER-EIC_configure.html
TBSMCLUSTER-EIC_configure.html
NCICLUSTER-new1twin.html
TBSMCLUSTER-new1twin.html
NCICLUSTER-newrwin.html
TBSMCLUSTER-newrwin.html


If you have made changes to the above mentioned files you will
find your copy of the file under:
- The copy of the files can be found in the following
directory:
[InstallDirectory]/
tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0004/dash

---

Added files associated with the Discovery Library Toolkit:
remove_merged_resources.xml
migration/loadTaddmJars.bat
migration/migrateTaddmModel.bat
migration/loadTaddmJars.sh
migration/migrateTaddmModel.sh
migration/migrateClassFilters.xml
migration/etc/userPasswordPrompt.properties
db-checkupbeforecleanup.sql

Replaced files associated with the Discovery Library Toolkit:
scc_refreshnamingcommitchanges.sql
scc_checkfordupsinstage.sql
scc_processcreatecomponents.sql
scc_remove_merged_resources.sql
NamingRules.xml
genStep1SqlForTADDMFromOrm.xsl
genStep2SqlForTADDMFromOrm.xsl
genTheSQLTADDMFromOrm.xsl
ScrProducePostProcessingSql.xsl
xmltoolkitsvc.properties
ASICLTools.jar
setdbshema.[sh|bat]
createidmlbook.sql
db-cleanup.sql



If you have made changes to the above mentioned toolkit files you will
find your copy of the files under:
[InstallDirectory]/tbsm/XMLtoolkit/log/install/maintenance/backup/611FP0004

---

TBSM agent packages are available for download from the TBSMAgent
directory on the support download.

TBSM Agent packages are now they will be available to download from Fix Central

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

2.0 Hardware and software requirements
----------------------------------

For information about hardware and software requirements, see the
Tivoli Business Service Manager Installation Guide on the IBM
Tivoli Business Service Manager Information Center (at IBM Knowledge Center):

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.ibm.tivoli.itbsm.doc/welcome.htm

To apply this Fix Pack you will need 3 GB of disk space. Please check
the amount of space you have before you install, as the installation
will fail if you run out of space.


=======================================================================
4.0 Additional information for TBSM Fix Pack 4 APARS:
------------------------------------------------

The following APARs fixed in this service delivery require additional
action by users. If your environment uses or is experiencing the
symptoms described, use the instructions provided to complete the fix.

4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS
Customers are now allowed to persist their log file settings
without manually editing the server.xml file. Currently, customers
use the setTraceLevel script to set the maximum number of log files
and the size of these of files using the following method:

$TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setTraceOutputToFile 30 40

Now they will be able to persist these sizes by using the following
command.

$TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setstartup

Before this change, the call would only persist changes to the trace
level. Now it persists changes to the trace level as well as the log
file configurations.


4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON
RADEVENTSTORE

The following SQL statements needs to be run after FP install, against
the TBSM DB2 Database:

CREATE INDEX RADEVENTSTORE_IDX1 ON TBSMBASE.RADEVENTSTORE(RADSERIAL) COLLECT STATISTICS

The above SQL statement can be found on the following file:

./tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/AddRADEventStoreIndex.sql

Please provide the above file to the TBSM DB2 Database Administrator,
along with the following Notes:

Notes:
1) Use
cat AddRADEventStoreIndex.sql | db2
to run the SQL. The command must be run against all DB2 databases
used for TBSM. The command does not require a server stop/start.

2) The ; delimiter is not used in the AddRADEventStore.sql file
- whether the delimiter is required or not depends on the
connection settings (-t option).

3) Typical output from the SQL: cat AddRADEventStoreIndex.sql | db2
db2 => db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The RUNSTATS command completed successfully.

4) Typical output from the SQL (if the index already exists)
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => SQL0605W The index was not created because an index
"TBSMBASE.RADEVENTSTORE_IDX" with a matching definition already exists.
SQLSTATE=01550
db2 => db2 => DB20000I The RUNSTATS command completed successfully.

5) Other warning:
SQL2314W Some statistics are in an inconsistent state. The newly
collected "INDEX" statistics are inconsistent with the existing
"TABLE" statistics. SQLSTATE=01650

To address the message above, RUNSTATS Is Run after the index is
created.

As well as the changes in the index there are 2
configurations changed required for this APAR

a) Increase the number of allowed connections for the TBSMDatabase
Data Source.

This can be done via the Impact GUI screen (Data Model) or via
the file tbsm\etc\TBSM_TBSMDatabase.ds

Increase the number from default 15 to 50 (or to limit
recommended by DB2 Admin)

TBSMDatabase.DB2.MAXSQLCONNECTION=15
to
TBSMDatabase.DB2.MAXSQLCONNECTION=50

If changing via file, then a Data Server restart is required.


b) Set the LOCKTIMEOUT in DB2 to 30 seconds. The default is -1,
which mean no timeout - If you set this parameter to -1, lock
timeout detection is turned off. Setting to 30 seconds means
sessions will only wait for 30 seconds for a lock. Again, this
change should be made in consultation with local DB2
Administrator.

4.3 Adding the new "Delete Service Instance" menu action.
A new menu action is now available, directly from the Service
Navigation, that will allow the TBSM Administrator to delete
Service Instances without the need to bring up a separate page.
To enable this new menu action, perform the following manual
actions:

1) From the tbsm/XMLToolkit/bin directory, execute the following
command, to retrieve the ServiceIntance.xml data from the TBSM
DB2 database (note: the -d parm requires a temporary directory):

getArtifact -U <db2admin> -P <db2pw> -d <tmpdir>\fp4 -n ServiceInstance.xml -c treetemplate

2) Locate the ServiceInstance.xml on the <tmdir>\fp4 and edit with
a text editor.

3) Locate stanza containing "ShowServiceInstanceEditor" and add the
following line after it:

<actionMapping clickType = "~popupMenu" actionName = "DeleteServiceInstance"/>

You should end up with something like this:
<actionMapping clickType = "~popupMenu" actionName = "ShowServiceInstanceEditor"/>
<actionMapping clickType = "~popupMenu" actionName = "DeleteServiceInstance"/>

4) Save the updated ServiceInstance.xml file

5) Put the updated ServiceInstance.xml back into the TBSM DB2
database, using the following command from the tbsm/XMLToolkit/bin
(note: the -n parm requires the fully qualified directory)

putArtifact -U <db2admin> -P <db2pw> -n <tmpdir>\fp4\ServiceInstance.xml -c treetemplate

6) Load the new the DeleteServiceInstance menu action using the
following command:

putArtifact -U <db2admin> -P <db2pw> -n \<installdir>\tbsm\av\xmlconfig\DeleteServiceInstance.xml -c menuactions -s action

7) Re-initialize the canvas, to get all of the TBSM Dashboard
consoles to pickup the new menu actions. The following
command to accomplish this action:

<installdir>/tbsm/bin/rad_reinitcanvas <tipadmin> <tippassword>

Now, every time a right-mouse click is done on a Service Instance,
on the Service Navigation, an additional menu action will be
displayed. The "Delete Service Instance" menu action will always
prompt for confirmation, prior to deleting the instance.

4.4 The service SLAPrunePolicyActivator
After the Fix Pack has been applied and the "ApplyPoliciesFor611FP4"
has been executed on the Data server, perform the following actions
to create a new PolicyActivator Service to allow for automatic
pruning of the SLA data from the TBSM database.

1) Logon to TBSM and to the "System Configuration", then
"Event Automation" and select Services

2) Once the "Services" page is displayed, click on the
"Create New Service" button and select the "PolicyActivator"
option.

3) On the "Create New PolicyActivator Service" page, enter the
following value on the Service Name:
SLAPrunePolicyActivator

4) For the Activation Interval, enter this value: 86400

5) For the Policy option, click on the pulldown and select:
SLAPrune

6) Click on the "Startup' box, to have the Service automatically
started when the server starts

7) Click on the Save button, to save this PolicyActivator Service

NOTE: With a value of 86400 on the Activation Interval, the
Service will be activated every 24 hours.

Refer to the "Configuring the SLA tracker period" on the
Configuration, for more information about SLA data tracking
and SLAPrune. This function is documented on the following page in
the Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.ibm.tivoli.itbsm.doc/customization/bsmc_slac_maint.html?lang=en

=======================================================================
5.0 List of APARs
-------------

5.1 TBSM 6.1.1 Fix Pack 4 APARs
---------------------------

The following TBSM APARs are delivered with Fix Pack 4:

IV53193: INCORRECT PROPERTY USE IN CODE ROOTCAUSEEVENTFIELD USED INSTEAD OF ROOTCAUSEEVENTKEYFIELD
IV69037: IE10 SERVICE TREE REFRESH
IV71194: GRID VIEW IN CANVAS GETTING SQUASHED PERIODICALLY AND WHEN INSPECTOR OPENED
IV75807: TOP LEVEL SERVICE INSTANCE WILL NOT POPULATE REST OF SERVICE MODEL. PARENT SIDE ESDA RULE FAILS.
IV75972: ORPHANED SERVICES IN ROOT OF TREE AFTER INVALIDATION
IV76788: INCOMPLETE SERVICE TREE CREATED AFTER INVALIDATION WHEN TEMPLATE PROPERTY USEESDAIDENTIFIERSONLY IS TRUE
IV76901: CORRUPTION IN THE DEFAULT TREE TEMPLATES
IV76976: LOADING POLICY FUNCTIONS CAUSES NATIVE MEMORY GROWTH
IV77455: TBSM 611. TBSM DATA SERVER HANG WHEN RUNNING ESDA/AUTOPOP
IV77750: RECALCSTATENODESALL AND RECALCSTATENODESLEAF ONLY WORKS FOR SERVICES WITH CHILDREN
IV78284: DATATYPES DELETED WHEN A DATASOURCE IS MODIFIED USING TBSM SERVICE CONFIGURATION GUI
IV81811: SOAPRESPONSESERVERFACADE_CONFIG.PROPERTIES ON TBSM DATA SERVER SYMPTOM: TBSM SERVICE EDITOR FAILS.C.
IV81987: TBSM 6.1.1 VULNERABILITY WITH COMMUNICATION BETWEEN THE DASHBOARD SERVER AND DATA SERVER.
IV82074: SECURITY APAR <CVE NOT AVAILABLE> CROSS-SCRIPTING VULNERABILITIES ../IBM/SLA/RAD
IV82185: OOM DUE TO LARGE COMMANDLIST OBJECT IN MANY SERVICE INSTANCES.

5.2 TBSM 6.1.1 Fix Pack 3 APARs
---------------------------

The following TBSM APARs are delivered with Fix Pack 3:
IV60619 DATA SERVER RESTART REQUIRED TO GET A WORKING DATA FETCHER AFTER DELETION OF DEPENDENT RULE
IV61278 RULE FILTER WITH 'NOT LIKE' ON SUMMARY FIELD MALFUNCTIONS
IV64797 SETDBSCHEMA -F A COMMAND SHOULD ALSO RESET THE RESENRICHREADER SERVICE. : 611
IV65695 FO_CONFIG SCRIPT DOES NOT CONFIGURE SET TBSM_B_IMPACTDB.DS DATA SOURCE PARAMETERS IN A FAILOVER ENVIRONMENT. : 611
IV65825 XMLToolkit: Single Quotes not Encoded on IDML file generation: 611
IV65947 ACCESSING CLOB DATATYPES IN TBSM DATABASE CAUSES DB2 ERROR, SQL0270N : 611
IV65949 ACCESSING TBSM DATABASE VIEWS WITH IN TBSM CAUSES DB2 ERROR : 611
IV65958 TBSM DATABASE QUERIES THAT USE MAX, MIN, DISTINCT, VIEWS CAUSES DB2 ERROR, SQL0243N : 611
IV66535 TOOLKIT ISSUE RELATED TO STATEMENT RTERMINATION CHARACTERS: 611
IV66950 TBSMEVENTREADER STOPS : THE REAL FIX FOR IV65545 IS TO FIX THE TXN CODE : 611
IV71255 SELECT STATEMENTS USED FOR LOGGING PURPOSES IN DB-CLEANUP.SQL SCRIPT NEED TO BE COMMENTED OUT. : 611
IV72005 IMPACT SLO FUNCTION

5.3 TBSM 6.1.1 Fix Pack 2 APARs
---------------------------

IV62456 OOM DUE TO CIRCULAR REFERENCES
IV62548 SAME SESSION CONTEXT USED FOR ALL RADSHELL SESSIONS, TRIGGERED FROM POLICIES
IV60168 MODIFIED 'TBSM_NUMERICATTRIBUTEFUNCTIONS' POLICY DOESN'T GET EXPORTED
IV56853 RADSHELL IMPORT FAILS DUE TO ORPHANED CHILD SERVICE
IV63608 AFTER FIX FOR APAR IV32754 SEE SQLSTATE=42704 EXCEPTION FOR TBSMSCR.SCCP_COMPCLASS IN TOOLKIT LOGS
IV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS
IV65786 TBSM CIRCULAR REFERENCES ISSUE
IV59886 TBSM DOES NOT RE-READ EVENT READER PROPS FILES AUTOMATICALLY WHEN YOU CONFIGURE/ENABLE EVENT ENRICHMENT
IV61880 INFINITE LOOP IN DATA SERVER CAUSED BY MALFORMED OFFLINE TASK
IV64950 DB2 ERROR DB2 SQL ERROR: SQLCODE=-805
IV60750 NUMERICAL RULES NOT CALCULATED ON TBSM RESTART
IV60961 CONCURRENTMODIFICATIONEXCEPTION THROWN WHEN YOU SELECT THE GUI FIND INSTANCE FUNCTION IN THE SERVICE AVILABILITY PORTLET
IV61199 TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUPOUT CHANGES
IV62273 CONCURRENTMODIFICATIONEXCEPTION ERRORS IN DASHBOARD LOG
IV62294 NUMERIC AGGRIGATION RULE CHANGES NOT SAVED
IV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT
IV64933 [NetcoolTimeoutException] Log file exceptions when persisting ESDA instances
IV65545 TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON RADEVENTSTORE
IV66210 NULLPOINTEREXCEPTION DISPLAYED ON SYSTEM STATUS ON FAILBACK
IV65484 TBSM: DISPLAY NAME IN PERSISTENT SERVICE MODEL NOT BEING UPDATED
IV68113 DELTA IMPORTS NOT WORKING FOR BUSINESS APPLICATIONS WITH IMPORTING FROM TADDM 7.3 TO TBSM 6.1.1 FP1
IV60842 QUERY CONCATENATION PROBLEM WHEN THE PROPERTY 'DL_LIFECYCLESTATE_FILTER' IS ENABLED
IV56450 NULL POINTER EXCEPTION AFTER CLICKING ON 'FIND INSTANCE'
IV65991 DOCS ABOUT CONFIGURING FOR HTTP ACCESS INCORRECT



5.4 TBSM 6.1.1 Fix Pack 1 APARs
---------------------------

The following TBSM APARs are delivered with Fix Pack 1:

IV21679 MODEL CLEANUP NEEDED AFTER ALIAS CHANGES
IV30875 ERROR CTGBC0053E WHEN SELCTING SERVICE IN A CANVAS
IV33717 ADVANCED THRESHOLD LOOKS CORRUPTED WHEN IT CONTAINS SINGLE SPACE CHARACTERS
IV36878 Dont create rules with ' character'
IV38053 MAINTENANCE SCHEDULE IS NOT WORKING
IV38471 ADD LONGPARENTSERVICENAME TO THE TBSM REPORTING DATA MODEL.
IV38574 SERVICE TREE COLUMNS DO NOT RESIZE TO FIT WHEN PORTLET RESIZES SMALLER.
IV39167 NEED ABILITY TO LOGIN USING UID AND HAVE CN IN TIP BANNER
IV39517 ESDA RULE DIALOG DOES NOT ALLOW PARENT TEMPLATE CHOICE
IV39796 MAINTENANCE SCHEDULE WITH ADJACENT TIME WINDOWS CAUSING LOOP
IV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER
IV42657 SERVICE STATUS INCORRECT
IV42941 COMPONENT COMPOSITES NAME TOO LONG IMPORTED FROM TADDM
IV43098 SERVICE TREE REFRESH UPON CLICKING OR EXPANDING
IV43165 INSTANCE PROPAGATION IN PLACE FOR SERVICES IMPORTED FROM TADDM BECAUSE OF RULE ON SCR_RETRIEVEDEPENDENTOBJECTSTEMPLATE
IV43469 TBSM HANGS DURING AUTOPOP - DATA SERVER IN WAIT LOOP
IV43804 VERSIONINFO ON A SPLIT SERVER, DATA SERVER IS INCOMPLETE
IV43865 SERVICE INSTANCE CONTAINING CHINESE/NLS CHARS GENERATES ERROR TCTUI1003E
IV44246 SOME INTERMEDIATE SERVICES MISSING EVENTS IN SERVICE DETAILS PORTLET
IV44582 TBSM 6.1.0 CONCURRENTMODIFICATIONEXCEPTION MESSAGE DISPLAYED.
IV45166 ITM POLICY DATA FETCHER CREATION - TBSM REMEMBERS ORIGINAL HOST DETAILS
IV45386 THE COLOR OF MAXSEVERITYRAWEVENTS NOT CORRECTLY HANDLED.
IV45868 THE SERVICE VIEWER DOES NOT LAUNCH ON ITALIAN CLIENT SYSTEMS
IV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER
IV46811 COMMA IN TEMPLATE NAME CAUSES ILOG.VIEWS EXCEPTION
IV46876 UNABLE TO LAUNCH LEL FROM HTTP SERVER
IV48813 ERROR POP UP WHEN SERVICE AVAILABILITY PAGE IS LAUNCHED
IV49791 SECURITY ROLE IS NOT ACTED ON, WHEN ESDA INSTANCES ARE BELOW
IV50625 CROSS-SITE SCRIPTING VULNERABILITY AT TBSM 6.1.0.1
IV53791 EVENT COUNTS FOR PARENT SERVICES IS NOT ALWAYS UPDATED
IV54197 TBSM DISCOVERY LIBRARY TOOLKIT REQUIRES UPDATES TO INTEGRATE WITH FUTURE TADDM RELEASES
IV54587 TBSM AGENT - TEPS WORKSPACE TITLE DOES NOT MATCH WHAT IT SHOWS
IV55756 TBSM 6.1.1 ESDA POPULATION CAUSES OUTOFMEMORY IN TBSM DATA
IV56050 ERROR : JAVA.LANG.ERROR: JSFSECURITYPHASELISTENER - POSSIBLE
IV56270 OUTOFMEMORY: USERPROFERENCESSTORE FOR CHILD RELATIONSHIP ATTRIBUTES IS NO
IV57273 REQUEST ERROR IN BOTH VIEWS OF TBSM SERVICE INDICATORS
IV59723 CROSS-SITE SCRIPTING VULNERABILITIES INVOLVING 3 JSPS
IV61668 NETCOOLTIMEOUTEXCEPTION WHEN ESDA DISCOVERS TRIGGERS POLICY



List of TBSM APARs that have updates to the documentation:

IV54828 GET REQUESTS FROM DASH WIDGETS TO TBSM DATA SERVER
There is a new property (impact.dataproviderupdateprocessorintervalsecs), that
defines the interval at which the data provider fires status change updates.

IV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER
The ObjectServer_DS.ObjectServer.FAILOVERPOLICY parm can be
changed (in the TBSM_HOME/etc/(TBSM or TBSM_B)_ObjectServer_DS.ds
file by either manually editing the file (as shown on the
Install Guide) or running this new command, with either of
the three listed values:

Windows:

%TBSM_HOME%\bin\tbsm_generic_ant_caller.bat ObjectServer_DS_config.ant <parm>


Unix:

$TBSM_HOME/bin/tbsm_generic_ant_caller.sh ObjectServer_DS_config.ant <parm>

Available values:
1. DISABLE - configure to only connect to Primary Object Server
2. FAILOVER - configure FAILOVER back and forth between Object Servers but,
only if connection is lost. This is the Default (if NULL' is used)
3. FAILBACK - configure to FAILBACK to Primary Object Server, as soon as it is available.

IV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER

#
# ---------------------------------------------------------------
# (Optional) Specifies a alias for building MSS Id. By default,
# the TADDM hostname is used. But in cases there TADDM is
# configured in failover, objects imported from the Primary
# TADDM and Backup TADDM will have different hostnames
# used for building MSS. This will mean 2 MSS associated
# with objects.
#
# When setting a string for the alias, use the primary taddm
# hostname.
#
DL_AliasForMSS = PrimaryTaddmHostname
#
# Note: Launch in Context uses the MSS hostname to build the
# sourceContactInfo value, which is used to contact the TADDM
# server. For this reason, when TADDM is configured in Failover,
# a front end server (load balancer) is required, to route Launch
# In Context requests to the active server. This will ensure
# requests are routed to the secondary TADDM server, when the
# primary is down.

IV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS
The property "UseESDAIdentifiersOnly" can be added, as an
additional parameter to the child Template, which will allow
users to select if they want previous event identifiers on a
service to be kept or erased with each invalidation.

When set to "true", all previous event identifiers will be
erased from TBSM memory model at each invalidation and the
service will only accept identifiers from ESDA policies or via
SCR API. When set to "false", all event identifiers, old or
newly added will be preserved for the service. User must
manually delete event identifiers that they do not wish to
keep. This is TBSM's default behavior.

IV65786 TBSM CIRCULAR REFERENCES ISSUE
There will be two new properties added in TBSM_sla.props file
that governs the check:

Property name: impact.sla.servicetreedepthlimit
Description: When the data is imported from TADDM, a depth
limit check will be done to the corresponding service tree
during invalidation to ensure that the service tree has normal
relationship data. This property governs the depth limit for
the service tree. If the system detects a service tree with
depth level larger than the value set by this property, a
warning service instance will be created to warn the user to
review their data relationship.

Default value: 20

Property name: impact.sla.disableimportalldescendantslimitcheck
Description: When set to "true", the service tree depth limit
will not be checked during invalidation.

Default value: false

IV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT
The APAR handles the issue of TBSM Failover settings for Data
Sources. Impact back-end java code handled whether or not
failover (or failback) is initiated in times of Data Source
failure. This back-end Impact code only uses the
FAILOVERPOLICY settings in the .ds files

The APAR change has been in the TBSM interfaces to setting up
Data Source. There are 2 interfaces 1) GUI screen (as above)
and 2 radshell (createDataSource and export functions).

1) TBSM GUI: The TBSM GUI will now set the FAILOVERPOLICY
setting in the .ds file. When editing existing files, if
no valid FAILOVERPOLICY exists, then the current
DISABLEFAILOVER setting will be used to determine a new
FAILOVERPOLICY setting, i.e. if no valid FAILOVERPOLICY
exists, then if DISABLEFAILOVER is true, FAILOVERPOLICY
will be set to DISABLED. If DISABLEFAILOVER is false,
FAILOVERPOLICY will be set to FAILOVER

Take good note of the above. It means that existing data
sources will have a new FAILOVERPOLICY set, when they are
first saved via the GUI. Previously if FAILOVERPOLICY was
not valid, Impact assumed FAILOVER. But if you edit a data
source, and the data source has DISABLEFAILOVER = true,
and no valid policy set, then the new value for
FAILOVERPOLICY is DISABLED. This is correct behavior, but
different to before. The best was to avoid any confusion,
it to check each .ds file and ensure that a valid
FAILOVERPOLICY is set. Do this either by editing the files
(in which case a Data Server restart is required) or by
opening each data source in the GUI. Not all Data Sources
will appear in the GUI (as some are built in). For these,
check the files. If editing files, ensure no spaces at the
end of settings. The only valid values for FAILOVERPOLICY
are DISABLED, FAILOVER and FAILBACK.

2) radshell: The Radshell interface also changes. The export()
function will now export the failover policy, and the
createDataSource takes a policy parameter (in place of the
boolean disablefailover parameter), Also, the old
createDataSource radshell function, will still work (for
backward compatibility with old exports). Note: Data Sources
exported with IV62246 in place, will NOT work on old
systems-as the generated radshell command will contain a
policy string.

IV82185 OOM DUE TO LARGE COMMANDLIST OBJECT IN MANY SERVICE INSTANCES
The TBSM Customization Guide is being updated to include the
following information, with regards to these Service variables
in a policy:

CHILDINSTANCEBEANS -
The array of child ServiceInstanceBeans for a service, if
the service has child services. This variable is a READ ONLY
variable. Setting this variable has no effect and will not
change the relationship of the ServiceInstance being
referred to.

PARENTINSTANCEBEANS -
The array of parent ServiceInstanceBeans for a service if
the service has parent services. This variable is a READ
ONLY variable. Setting this variable has no effect and will
not change the relationship of the ServiceInstance being
referred to.

IV51097: ADDITIONAL INFORMATION ON ROOT CAUSE EVENT PROPERTIES
The TBSM Customization Guide is being updated to include
information about the following parms:
- The minimum service state required to consider a service
event as the root cause for an outage:
impact.sla.minimumrootcausethreshold

- To update the root cause flag in other events:
impact.sla.updateeventrootcause

- The property to identify a policy to be called to re-tag
other events. This property is related to
impact.sla.updateeventrootcause (above):
impact.sla.eventtaggingrootcausepolicy

- The policy to call whenever an event is labeled as the
root cause:
impact.sla.customrootcausepolicy

- Property to turn off all root cause processing:
impact.sla.dorootcause


IV54466: AUTOSTART_ENABLE.SH SHOULD PROVIDE OPTION TO NOT RESTART
The TBSM Installation Guide has been updated to include
the following information related to "Configuring automatic
startup of TBSM on UNIX".

tbsm_suite.props file property values:

Property: RETAIN_CURRENT_SERVICE
Description: (Optional) When you run the autostartup_enable.sh
script, all the current, running sessions of the
TBSM services are stopped. If you want to be able
to run the script without stopping the current
session, set the value of this property to true.

IV72900: BSM ACCELERATOR SERVICES NOT POPULATING BSM_ACCEL SCORECARD
The TBSM Troubleshooting guide is beind updated with the
following:

By default, the Tree Template used by the Business Services
portlet is called BSM_Accel_Scorecard and the portlet has its
visibility rule, set to "ServiceVisibility".

The template, BSMAccelerator_ServiceApplication, has a
matching Internal Formula Rule called ServiceVisibility, and
is associated by default, with the top level service,
"BSM Accelerator".

The Starting Instance for the Business Services portlet
preference should be "BSM | Accelerator".

Given that the service model structure is as follows:

BSMAccelerator_ServiceApplication
> BSMAccelerator_AppServersGroup
> BSM_WebSphere_Server

the child templates do not have a ServiceVisibility rule
(by default) then the "Show starting node in tree" must be
enabled in the portlet preferences for the Business
Services portlet.

The ServiceVisibility Internal Formula Rule is used by
Solutions for Business Service Management to ensure that
only items that are in a marginal or critical
state displayed in the BSMAccelerator_ServiceApplication is
setting the appropriate value. The policy for the rule set
Status=0 if the children are good.

IV73493: TBSM GUI MOUSE SCROLLING DOSE NOT WORK IN SERVICE COLUMN FOR SCORECARD
The TBSM Customization guide has been updated to include
information about the following Custom property in both the
TBSM_sla.props file in the $TBSM_HOME/etc and the
RAD_sla.props file in the $TBSM_DASHBOARD_SERVER_HOME/etc
directories:

Property: impact.sla.persistifyautopop

Property: impact.sla.minimumrootcausethreshold

Property: impact.sla.updateeventrootcause

Property: impact.sla.eventtaggingrootcausepolicy

Property: impact.sla.customrootcausepolicy

Property: impact.sla.dorootcause

Property: impact.sla.forcecanvasAutoRefreshMode

Property: impact.sla.unlockServicecolumn

IV75380: TBSM 6.1.1 CUSTOM PROPERTIES

IV76114: TBSM 6.1.1 BEST PRACTISE FOR INVALIDATION AFTER MODIFCATION OF A TEMPLATE
Both the TBSM Customization and TBSM Configuration Guides
are being updated to provide best practice on "How to"
invalidate services and avoid confusion. Especially when it
involves the action changing of templates or template
properties which affects services


The following IMPACT APARs are delivered with Fix Pack 4:

IV59728: IMPACT SECONDARY IS NOT SHUTTING DOWN IF RESYNC WITH PRIMARY FAILS
IV59840: Jabber Service sending GroupChat message not received when accounts and groups are hosted on Cisco XMPP server
IV66337: WEBSERVICE LISTENER POLICY STRING VALUE PARAMETERS CAN'T ACCEPT MULTIPLES LINES ENTRIES AND SOME SPECIAL CHARACTERS
IV66441: NULLPOINTER EXCEPTION DURING REPLICATION
IV68163: IMPACT UNABLE TO STOP PROPER HAD TO KILL THE SERVICE
IV71068: JREXECACTION FAILS WHEN IMPACT.SERVER.SSL_ENABLED=TRUE
IV72091: GETBYFILTER UNABLE TO HANDLE DBCS DATA
IV72561: JAVA.LANG.RUNTIMEEXCEPTION: NO CONTEXT ASSOCIATED WITH CURRENT THREAD
IV72673: UNHANDLED EXCEPTION: ORA-01003: NO STATEMENT PARSED
IV74071: CPU USAGE INCREASING DUE TO REGEX LOOPING
IV74421: MEMORY LEAK DUE TO EVENT READER CHECK POINT"
IV74485: DATABASEEVENTREADER USES INCORRECT DATE FORMAT ON RESTARTING
IV75602: DERBY REPLICATION DOES NOT WORK CONSISTENTLY BETWEEN IMPACT CLUSTER MEMBERS
IV75913: ABLE TO ACCESS ITEMS IN SCRIPTS DIRECTORY WITHOUT AUTHENTICATION
IV77882: MDVREGR - LIKE COMPARISON OPERATOR IN A POLICY NOT WORKING
IV79004: DIRECTSQL ON OPERATOR VIEW POLICY DOESN'T WORK AFTER FP1
IV79769: SERVICE LEVEL OUTAGES(SLO) CALCULATED INCORRECTLY : REGRESSION
IV79910: REXTRACTALL FUNCTION DOES NOT RETURN MATCHING CONTENT :REGRESSION
IV80388: THE "COMMONS-FILEUPLOAD-1.0.JAR" FILE IS VULNERABLE TO CVE-2013-0248



The following IMPACT APARs are delivered with Fix Pack 3:

IV27869: related to PMR 15590,SGC,724 - For 6.1.1 Impact
- The latest build should be installing version 2.2.0.2 of
VMMObjectServerPlugin
IV50058: IMPACT SERVER FAILS TO WORK PROPERLY WITH ANY SPACES IN CONFIGURABLE PROPS FILES
IV58590: SNMPTRAPACTION FAILS ON 2ND TRAP WHEN PROCESSING MULTIPLES
IV59481: UNABLE TO SEND HIBERNATIONS TO CLUSTER MEMBERS WHENEVER DIRECTSQL IS BEING USED
IV59770: DATA ITEMS RETRIEVED FROM A DIRECTSQL'S SELECT ARE NOT ABLE TO BE UPDATED
IV60438: IMPACT POLICY WIZARD (XML) FAILS WITH JAVA.LANG.NULLPOINTEREXCEPTION
IV61538: MWM WINDOWS DO NOT ADJUST FOR DST
IV61725: GETSCHEDULEMEMBER FUNCTION ISSUE
IV63535: UNABLE TO PERFORM DECRYPTION OF INPUT VALUE - DATA SOURCE ACCOUNT GETTING LOCKED
IV63942: SESSION.SENDCOMMAND IN A JS POLICY DOESN'T RETURNS ANY RESPONSE
IV64075: NullPointerExceptions
IV64837: IMPACT MWM WINDOW CREATED WITH WRONG END DATE
IV65055: GET/SETGLOBALVARIABLES DO NOT WORK WITH ACTIVATE FUCNTION
IV65179: LOCAL VARIABLES NOT RESTORED AFTER HIBERNATION
IV66164: ADD RECURRING MW WINDOW
IV67091: TBSM FAILOVER BACKUP NOT STARTED CORRECTLY IF STARTED TOO SOON
IV67829: ITM/TEPS DATA DISPLAYED INCORRECTLY IN UI
IV68383: DEBUG FLAG GENERATES MEMORY ISSUES WHEN NON OMNIBUS EVENTS ARE PROCESSED
IV69164: POLICY USES HIBERNATION WILL NOT WAKE UP
IV70836: COMMANDRESPONSE ERROR IN JS POLICY
IV71157: ACTIVATE FUNCTION CALLED FROM WITHIN POLICY SUB-FUNCTION HAS NO EFFECT
IV71513: EVENT IS NOT BEING PROCESSED CORRECTLY AFTER HIBERNATION
IV73098: EVENTS OCCURING ONE HOUR BEFORE ONE TIME WINDOW GOING INTO MAINTENANCE
IV73243: XSS ISSUE IN PROJECTNAME PARAMETER

The following IMPACT APARs are delivered with Fix Pack 2:

IV18554: 511:EVAL FUNCTIONALITY HAS CHANGED FROM 4.1 TO 5.1.1
IV23315: UPGRADE FROM IMPACT 5.1.1 TO IMPACT 6.x DISTRIBUTED [611]
IV64152: SECONDARY NODE CAN'T BIND TO THE NAME SERVER
IV61089: INSTALL FAILS AT STARTWAS STEP
IV63137: IMPACT 6.1.1 REPLICATION FROM PRI TO SEC NOT WORKING
IV62792: 1.2 GB WAS BEING FILLED BY BLANKS FROM LOGGER FUNCTION
IV61956: DATA MODEL NOT SORTED IN ALPHABETICAL ORDER
IV61746: IMPACT 611 FP1 INSTALL FAILS WHEN INSTALLING ON GA 611, WHICH HAS BEEN FIRST UPGRADED FROM IMPACT
IV61399: NULL VALUE ON FIELD, DASH WIDGET SPINS TO MANY TIME MAKING DATA VEIW VERY SLOW TO VIEW.
IV60005: DATA TYPE NOT SAVED CORRECTLY IF FEILD DELETED AND REMAINDER RE-ORDERED.
IV60253: TEPS UIDP NOT CLEARING CACHE, CAUSING MEMORY LEAKS.
IV58616: DIRECTSQL EXECUTE CAUSES EXCEPTION IN POLICY EXECUTION
IV58511: EMAIL READER SERVICE DOES NOT HANDLE EMAILS THAT USE A NON-STANDARD CHARACTER SET
IV53717: JMS MESSAGE LISTENER SERVICE NOT STOPPING PROPERLY
IV56745: IMPACT IS UNABLE TO HANDLE EXCEPTIONS FROM A WEBSERVICES CALL
IV56068: IMPACT THREADS INCREASING WHEN WEBSERVICES SECURITY IS ENABLED
IV55989: HIDDEN/DELETED FIELDS NOT BEING REMOVED FORM OPERATOR VIEW
IV50329: WEBSERVICES SECURITY NOT FUCTIONAL
IV56541: CONFVMM4NCOS SCRIPT IN IMPACT 6.1 IS NOT WORKING AS EXPECTED
IV47748: CAN'T LOAD WEBSERVICE LIBRARIES THAT HAVE JAVA OR JAVAX PACKAGES IN THEM
IV55464: UNABLE TO CREATE A BUTTON ON JAZZ AFTER JAZZ FP2
IV60923: USING THE DIRECTSQL APPROACH AND HAS IDENTIFIED THE NON-REFRESH OF THE SCHEMA ON USERNAME UPDATE IN THE DSA AS SECURITY RISK
IV59920: NO MEANS OF ENCRYPTING IMPACT.OBJECTSERVER.SECUREPASSWORD THAT WILL ALLOW AUTHENTICATION TO AN OBJECT SERVER USING FIPS

The following IMPACT APARs are delivered with Fix Pack 1:

IV11728: USING EVENTREADER PARSERESTRICTIONFILTER TO ALLOW THE USE OF GETDATE()
IV21717: ONE TIME MAINTENANCE WINDOWS DO NOT ADJUST FOR DST
IV22560: ANALYZE EVENT MAPPING TOOL FAILS AND HAMMERS CPU
IV33973: JMS READER DOES NOT CONVERT ACTIVEMQMAPMESSAGE DATA FOR TRANSFER TO SECONDARY CLUSTER MEMBER
IV34503: "OPTIMIZE LIST" OPTION DOESN'T REFLECT THE APPLIED CHANGES TOTHE LIST IN THE "RESTRICT FIELDS", WITHIN THE EVENTREADER
IV35827: ERROR PRODUCED IN NETCOOL.LOG WHEN USING AN EVENTREADER WITH A BLANK FILTER VALUE
IV35885: IMPACT NEEDS TO CHECK USER CREATED SERVICES, FOR WITH NAMES THAT END WITH A "_SERVER".
IV35940: RETURNEVENT() FUNCTION WITHIN DATABASEEVENTREADER ADDED UNWANTED SINGLE QUOTES TO THE IDENTIFER FIELD IN THE SQL "VIA" STATEMENT
IV36405: THE CONFVMM4LDAP COMMAND IS SHIPPED WITH IMPACT 6.1, BUT IS NOT DOCUMENTED
IV36503: MWM CALENDAR: USING FORWARD BY ONE MONTH CAN LEAD TO NON-EXISTENT DATES BEING CREATED
IV37040: USING "NCI_COLLECT_LOGS" UTILITY IN A GUI SERVER ONLY INSTALL DOES NOT WORK.
IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
IV37717: IMPACT 6.1 FP1 OPVIEW SOAP ERROR
IV37759: INTERNAL DATATYPE STRING VALUE IS INTERPRETED AS AN INTEGER IF IT CONTAINS ONLY DIGITS
IV38045: ORACLE DSA ERROR FOR COLUMN NAMES WITH "DOUBLE-QUOTES" AND "NOT-ALL-CAPS"
IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
IV38961: APPLICATION AND DATA NEEDS TO BE VALIDATED.
IV39368: INCREASING CPU WHEN JABBERSERVICE
IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
IV41888: DISABLE THE HIBERNATION STORAGE
IV42715: ERROR WHEN USING # IN IMPACT FILTER FROM DATATYPE DATAITEMS GUI WINDOW
IV43030: IMPACT MISSED ENRICHING FEW EVENTS WHICH OCCURED SIMULTANIOUSLY
IV43751: EVENTPROCESSOR IN A SECONDARY SERVER IS UN-ABLE TO CONTACT PRIMARY SERVER EVENTPROCESSOR.
IV45068: ERROR TRYING TO CREATE SCHEDULE DATATYPE DATAITEM: ERROR MESSAGE: HTTP ERROR 500 INTERNAL SERVER ERROR
IV45511: NEEDED 6.1.1 MWM OPVIEW POLICIES GET OVER-WRITTEN, AFTER MIGRATION FROM EITHER IMPACT 5.X OR 6.1, CAUSING MWM ISSUES
IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
IV45838: OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF SELFMONITORING (DATASOURCE MONITORING) IS ENABLED
IV46099: JMSREPLYTO WAS NOT ABLE TO SET CORRECT QUEUE.
IV46493: ATTEMPTING TO USE DATATYPE FILTERS - "SPECIAL" CHARACTERS BEING CONVERTED TO HTML ENCODING THAT BREAKS OUTGOING SQL.
IV46696: LIMITING THE NUMBER OF CONNECTIONS THAT IMPACT OPENS TO JMS
IV46729: TOPOLOGY WIDGET KEEPS THE OLD LINKS BETWEEN NODES AND DOESN'T CLEAR IT, RESULTING IN AN INCORRECT RELATIONSHIP
IV46799: FUNCTION <FUNCTIONNAME> IS NOT DEFINED BEFORE CALL
IV47058: MWM POLICY SETS SUPPRESESCL FIELD TO 6 IMMEDIATELY AFTER SETTING TO 1.
IV47799: SELECTING 2 KEY FIELDS IN DATA TYPE ON DEFAULTOBJECTSERVER DOESN'T WORK
IV47904: EIC 'TEST SQL' FAILS DUE TO UNSCAPED CHARACTERS
IV47988: SETTING THE WSSETDEFAULTPKGNAME VALUE GLOBALLY DOESN'T WORK WHEN THE WSINVOKE FUNCTION IS INSIDE A POLICY FUNCTION
IV48113: SLOW RESPONSE ON THE POLICY PAGE WHEN ATTEMPTING TO OPEN A LARGE NUMBER OF POLICIES VIA THE GUI
IV50464: JMS TIMEOUT CAUSES POLICY ASSIGNED TO OPERATORVIEW EXECUTE TWICE
IV50932 MAINTENANCE WINDOW EVENT SHOWED STATUS 'NORMAL' - parent apar cancelled
IV51062: DB2 DSA FAILS TO QUERY COLUMN NAMES WITH "DOUBLE-QUOTES AND NOT-ALL-CAPS"
IV53483: CALLDBFUNCTION USAGE IN ORACLE DATABASE WITH FILTER 0=1
IV53810: I10N - TRANSLATION ISSUE
Translation issues in XinY policy and in Browse and Cancel buttons have been fixed.
IV53818: ISSUES WITH INTEGRATIONS ON 611
Web services related issues have been fixed.
IV53822: FIXES FOR HA IN 611 FP1
Issues related to Omnibus failover/failback have been fixed.
IV53824: FIXES IN IMPACT SCRIPTS FOR 611 FP1
Issues in Impact scripts nci_export, nci_import and nci_encryptpolicy have been fixed.
IV53825: THIS APAR INCLUDES FIXES FOR DATA MODEL ISSUES IN 611 FP1
IV53826: FIXES ISSUES IN 611 FP1 WITH POLICIES
IV53827: THIS APAR FIXES SERVICES RELATED ISSUES IN 611 FP1
IV53836: FIXES UI DATA PROVIDER ISSUES IN 611 FP1
IV54939: A MISSING $IMPACT_HOME/LOGS/INSTALL/ DIRECTORY WILL RESULT IN THE NCI_CONFIGURATION_UTILITY PROBLEM
IV55776: UI PROVIDER ENHANCEMENTS IN 611 FP1
This contains UI Provider enhancements where the user can show status and percentage in topology,
tree, table, and list widgets
IV55778: JABBER UPDATES IN 611 FP1
This contains Jabber Updates to use the smack library.
IV55779: ADDITIONAL POLICY FUNCTIONS IN 611 FP1
This contains additional policy functions to escape special characters and filter malicious
content in strings.
IV55780: DSA ENHANCEMENTS IN 611 FP1
DSA enhancements that alert the user when users switch between failover and
failback configuration. Improved handling of network timeouts.
IV55781: SERVICEABILITY IMPROVEMENTS IN 611 FP1
Serviceability improvements, which include improved error messages for
GetHTTP and services.


List of Impact APARs that are marked as updates to the documentation:

IV20165: E-MAIL READER DELETES E-MAILS AFTER READING THEM
The email reader service reads incoming email, and runs
policies based on the contents of the email. To stop the
email reader from deleting emails after you read them, add the
following property to the <EmailReaderName>.props file.
<emailreadername>.deleteonread=false

Where <emailreadername> is the email reader service name.
Restart the service.This only works for IMAP email servers.

IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
If a customer is using Object.prototype.toString.call(obj) in
a javascript policy, and wants to follow the javascript
standard, he can add the following property to
NCI_server.props file -

impact.featureToStringAsSource.enabled=false

When the property is set to false, the data follows the
JavaScript standard and the data output by the Log function
is not the same as in IPL. To make the output the same in
JavaScript and IPL, make the value true but this does not
follow the javascript standard.

IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
NCI_EXPORT restriction: nci_export will not execute on the
non-primary member of a cluster.

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/admin/imag_tools_nci_export_c.html

IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
In order to make the readEventBuffer store the events for a
longer interval, the number of intervals can be updated. The
default number is 3.

Add the following property to the
<CLUSTERNAME>_<readername>.props. file
(eg NCI_omnieventreader.props file)-

impact.<readername>.numreaderbuffer=4

The default value for this property is 3.

IV40179: ERROR MESSAGES FIRST APPEAR ON 6.1 AND 6.1.1 DURING STARTUP, DUE TO THE FACT THE
NAMESERVER IS NOT INITIALISED YET
When the Impact Server is started during the installation,
the following message is displayed in the netcool.log file:

Unable to login to configured name servers host , port

The message occurs because the Name Server can take time to
initialize while Netcool/Impact starts. You can ignore this
message. It is normal and it disappears when the Name Server
server is initialized.

IV43157: ALL SERVERS IN A CLUSTER ARE REQUIRED TO USE THE SAME ADMIN UID AND PASSWORD
If you are configuring the Tivoli® Integrated Portal profile
for a cluster of servers, you must use the same user name and
password for all the servers in the cluster.

IV44875: SET JREXEC TO LOG TO FILE IS NOT WORKING
Documentation has been updated on JRExec server logging.

IV45481: NO DOCUMENTATION ON THE REQUIRED HTTP AUTHENTICATION FOR THE IMPACT 6.X WEBSERVICES
Documentation has been updated for Impact web services.

IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
A new policy has been added - XINY_DataType_PurgeData - to
remove aged data items. More information can be found in the
Troubleshooting Guide.

IV46185: JAVACALL METHOD FAILS WITH JAVA.LANG.ILLEGALACCESSEXCEPTION-CANNOT ACCESS A MEMBER OF CLASS JAVA.UTIL.HASHTABLE$HASHITERATOR
Documentation has been updated for the NewJavaObject function.

IV46512: THERE'S A NEED TO DOCUMENT THE FACT THAT ONE NEEDS TO RESTART IMPACT FOR JVM TO RELEASE ANY LOADED JAR FILES FOR WEBSERVICES
Documentation has been updated to specify the procedure of
what to do when a user compiles a wsdl file using classes
from a previously compiled file.

IV47057: DATA TYPE QUERY CACHING RETURNING BAD DATA
Documentation on Data caching information has been updated.

IV47454: INSTRUCTIONS ON HOW TO RUN UPGRADE PACAKAGE FOR IMPACT 6.1.1 ON CONSOLE OR SILENT MODE
Documentation on How to upgrade from Netcool/Impact 6.1 in
console mode has been added.

IV50673: INCORRECT/UNCLEAR DOCUMENTATION FOR HANDLING EXCEPTIONS

IV50776: DURING UPGRADE WE WILL OVER WRITE ANY CUSTOMIZED MWM POLICIES WITH NEWER THE MWM DEFAULT POLICY'S VERSIONS

IV51431: NEED TO DOCUMENT THAT DOT NOATION CAN NOT BE USED IN THE NAMING OF POLICIES, SERVICES, DATA TYPES, DATA SOURCES, AND PROJECTS.
Documentation has been updated to note that Dot notation "."
can not be used in the naming of POLICIES, SERVICES, DATA
TYPES, DATA SOURCES, AND PROJECTS.

IV52651: DATABASEREADER NOT WORKING PROPERLY WHEN USING GETUPDATES ON DATABASE TABLE'S TIMESTAMP FIELD
Database event reader service

An additional property can be added to the NCI_XXX.props file
in order to match the the date and time format of the
timestamp field in the external database. Where NCI is the
name of the impact instance and XXX is the name of the
database event reader.

An example of this property is:
impact.XXX.formatpattern=dd-MMM-yy hh.mm.ss.SSS aaa

IV55778: JABBER UPDATES IN 611 FP1
An additional property can be added to the JabberReader property files if password is required to
login to a group.

impact.<jabberreader>.groupchatpassword=passwordToChatWithGroup

For e.g. if the reader is the DefaultJabberReader, then add the property shown below to the
NCI_defaultjabberreader.props file. If this property is present, it will be used while
login to the group.

impact.defaultjabberreader.groupchatpassword=passwordToChatWithGroup


IV71068: JREXECACTION FAILS WHEN IMPACT.SERVER.SSL_ENABLED=TRUE
Updated documentation, with specific steps needed to create
key file and setup SSL certificates between Impact and JRExec
server.

IV73181: ISSUES WITH SQL EXCEPTIONS APPEARING WHEN USING THE DB2 DSA, COULD BE RESOLVED BY ADDING ADDITIONAL DATASOURCE PROPERTIES
Troubleshooting Guide has been updated to address issues
related to the handling of "read only" data from DB2 Data
Sources. A new section has been added to the Troubleshooting
Guide and it is titled:
"Error returning read-only data from DB2 Data Source"

IV73633: HOW TO PROPERLY UPDATE THE INTERNAL HSQL OR DB2 DRIVERS WHICH ARE INCLUDED IN THE IMPACT 6.1.1 INSTALLATION
The Administration Guide has been updated. The section titled
"Adding JDBC drivers and third-party JAR files to the shared library"
has bee updated to include steps needed to drivers

IV75254: DOCUMENTATION OF ENABLING WEB SERVICES SECURITY NEEDS AN OVERHAUL"
Both the "Netcool/Impact DSA Reference Guide" and the
Troubleshooting Guide, have been updated to include detailed
information on Web Services security setup, specially in a
clustered environment.


IV75734: ERROR HANDLING NOT HANDLE BY POLICY EXECUTED FROM POLICY ACTIVATOR
The following information has been added to the
"Policy logger service configuration window" section, with
regards to the "Error-handling Policy":

Note: If you have a Policy Activator service and you want it
to utilize a default exception handler policy, you must
specify the following property in the
<servername>_<activatorservicename>.props file:
impact.<activatorservicename>.errorhandlername=<policy
name to run>


IV79194: DOCUMENTATION REQUIRED FOR UI DATA PROVIDER TIMEOUTS
Additional information has been added to the Solutions Guide.
The new information describes the availability of two parms
which can be used to control "Connection Timeout" and
"Response Timeout" associated with the UI data providers.
The two parms are:
impact.uidataprovider.gethttp.conntimeout=<connection_timeout_in_miliseconds>
and
impact.uidataprovider.gethttp.sotimeout=<response_timeout_in_miliseconds>

Those parms are to be defined in the server. props file.


5.5 Tivoli Integrated Portal
------------------------

The Tivoli Integrated Portal 2.2.0.17 (version 3) should be installed
after installing this FixPack.

The following other components are updated with that version
of TIP:

Driver tip_2.2.0.17 (version 3)
* This driver includes Java SDK version 1.6 SR17 Fix Pack 7
* This driver includes eWAS 7.0.0.39
* Browser support
Microsoft Internet Explorer version 11 (Compatibility Mode)
Firefox Extended Support Release (ESR) version 38

See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.17&platform=All&function=all

NOTE: If TIP 2.2.0.15 (version 1) was previously installed, you may
encounter the following issues. Please refer to the following
Technotes for resolution:

- TIP Portlet blank or does not load after TIP 2.2.0.15
installation:
http://www.ibm.com/support/docview.wss?uid=swg21696426


- TIP chart portlet blank if TBSM Service Admin page is closed and
re-opened:
http://www.ibm.com/support/docview.wss?uid=swg21696424



5.6 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



=======================================================================
6.0 New support and features
------------------------

6.1 TBSM 6.1.1 Fixpack 4
--------------------
Fix Pack 4 includes the following enhancements:

Refer to the following TBSM Wiki Advanced Topics link and look in
the "What's New document":

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics

1) TBSM Service Navigation: UI experience improvements
* Simplify the deletion of a single service. A new context menu
from the Service Navigation window's Services list allows the
direct deletion of the selected service

* Service Editor tab "Identification fields" doesn't use all space
available within Service Configuration page in TIP in
TBSM Dashboard Server.

2) TBSM UI Data Provider: Map Dataset
* First TBSM dataset that can be visualized by the DASH "Map"
widget
* It contains the standard set of base properties plus adds set
of geo-location properties (Latitude, Longitude, Geolocation).

* Supports same parameters as "All TBSM Services" dataset in
regards to location and gathering services. With option to
control what to do with services that do not have geolocation
data defined.

A tutorial document that covers the TBSM Map dataset can be found here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics

3) TBSM UI Data Provider: Business Impact Dataset
* Enable creation of legacy "Business Impact" custom views in
DASH Environment
- Additional dataset to provide data currently seen in the
TBSM 6.1.1 custom views called:
Business Impact
Business Impact All
- Graphical view of all services impacted by a selected
starting service, showing:
> Only the impacted services that are in a degraded
state (Marginal/Bad)
> All impacted services, regardless of status

A tutorial document that covers the TBSM Business Impact dataset
can be found here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics

4) Service Level Objectives (SLO) Reporting Enhancements

* Automatic pruning of the table of outage data used in the
reports

* Capability to delete service, SLA, and calendar definitions

* Improved TBSM sample policy to only consider Bad status as an
outage

* Capability to export service and calendar definitions

* Utility functions for removing and restoring specific outage
data

* Bug fixes and updated documentation

This is documented on the following page in the Knowledge
Center:
http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.4/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html?lang=en

5) Tool for automated pruning of the TBSM SLA data
A new Impact policy based option has been made available that when
paired with the Impact PolicyActivator Service, is able to prune
the SLA date in an automated way.

6) Additional Status Values Supported in all Datasets
- Maintenance
- Unknown

6.2 TBSM 6.1.1 Fixpack 3
--------------------
Fix Pack 3 includes the following enhancements:

1) Template Editor: sort items in "Rules" table

Adjusting the logic that handles the order of the rules displayed in
the table on the Rules tab. The following are the new rules each
of the columns will adhere to:

Type column
> use the same icon as the toolbar action that created the rule
> tooltips describe the rule's type

Rule Name column
> all rule names are now sorted A-Z
> A-Z ordering maintained as rules are created and/or deleted
> tooltips describe the rule's type; same as Type column
> the display order will not be customer configurable

Rule Settings column
> minor styling tweaks to assist readability

The above enhancement is specific to the TBSM console

2) Tree Template datasets: enable use of internal status attributes in
"Tree Template Editor"

Extended the capability of the Tree Template datasets by allowing
TBSM internal status attributes to be selected on the editor UI's
Template Rule Mapping section.

When Tree Template Viewed in TIP-based Service Tree

Without processing by the customization policy, these new status
attributes will display as the standard TBSM status values:
0.0, 3.0, or 5.0.

The above, enhances the TBSM Data Provider function and benefits
the DASH users.

3) Datasets need a parameter to optionally exclude "starting" or
"container" services.

With the addition of the Tree Template datasets in TBSM 6.1.1
Fixpack 1, we now have more situations where the administrator may
wish to exclude the starting or container service from a view.

The above, enhances the TBSM Data Provider function and benefits
the DASH users.

4) Support parameter to filter datasets in TBSM_Services datasource
by template

The parameter would be available on the datasets in the
TBSM_Services datasource, which includes the "All_TBSM_Services"
and "TBSM_Urgent_Services" datasets

The above, enhances the TBSM Data Provider function and benefits
the DASH users.

5) "UrgentServices" dataset added

This new dataset makes the service model data that was displayed
in the legacy Urgent Services portlet available for display using
the List and Table widgets.

The above, enhances the TBSM Data Provider function and benefits
the DASH users.

6) Managing Dataset Dynamic Updates

All datasets available from the TBSM UI Data Provider automatically
send updates when the content changes. This is the recommended usage
of the TBSM datasets, but there may be scenarios where the user
would like to turn off the dynamic updating.

The above, enhances the TBSM Data Provider function and benefits
the DASH users.

More information can be found in the new "Dynamic Updating and the
TBSM UI Data Provider" document on the TBSM Advanced Topics page at
the TBSM developersWorks site

7) Tivoli Netcool/Impact provides new property to ascertain which Data
Provider field is used, when retrieving ITM data from the REST
Service

8) Enhancements to the Impact Solution called
"Service Level Objectives (SLO) Reporting". The SLO function
is enhanced by Fixpack 3 for:

* Support of a time zone specification when creating the SLA
definitions

* Detection of active outages in the sample policy that reads from
a TBSM Metric History database

* Bug fixes and improved documentation




See the Advanced Topics at the TBSM developerWorks site for new and
updated information:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics


6.3 TBSM 6.1.1 Fixpack 2
--------------------

1) NUMERICAL RULES NOT CALCULATED ON TBSM RESTART
Numerical Aggregation rules are triggered by a child metric rule
change, i.e. OverallAttribute. When the status of a child changes, the
OverallAttribute metric rule's value will change and any Numerical
Aggregation rules, based on OverallAttribute, will be recalculated.
When TBSM is restarted, only services which have related existing
events will have their status recalculated. Therefore not all Numerical
Aggregation rules (based on OverallAttribute) will be recalculated on
TBSM restart, as some services will be green.

This may not be the desired outcome. On restart, it may be required
that all Numerical Aggregation rules are restarted. New functionality
has been provided for such a scenario, by forcing a bubble up of state
nodes. The code can be triggered from a policy, for leaf nodes
only, or for all, as shown here:

USE_SHARED_SCOPE;

Type="StateModel";
Filter = "RECALCSTATENODESLEAF";
log("Recalc Leaf Node Only. Policy Start." );
GetByFilter(Type, Filter, false);
log("Recalc Leaf Node Only. Policy Finish." );
}


USE_SHARED_SCOPE;

Type="StateModel";
Filter = "RECALCSTATENODESALL";
log("Recalc All Nodes. Policy Start." );
GetByFilter(Type, Filter, false);
log("Recalc All Nodes. Policy Finish." );
}

The above policy code needs to be scheduled from Impact Services on
startup.



2) TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUTPUT CHANGES
If a client wants SLAM event text for a Numerical rule, to update
(even if it's value does not change), the following parm needs to be
un-commented and set to "true"

#If true then send SLAM events, even when the value of a Metric rule does NOT change.
#Default is false.
#Omnibus de-duplication will handle the rest.
#impact.sla.sendslameventsformetricrulealways=true



6.4 TBSM 6.1.1 Fixpack 1
--------------------

1) The BSM_Templates.radsh defines service templates for common TBSM services.
It was executed when you installed the TBSM GA release(not during the fixpack
install). It's default template rules propagate child status to the parent
service based on child template changes. The script has been updated to set
the propagation type to instance propagation. When the child service status
changes, it will propagate the change to the parent service regardless of
which child template rule caused the status change. See the Service
Configuration publication for more information about the aggregation rule
option.

To update the rules with the instance propagation option in your current
installation, you can invoke the
$TBSM_HOME/install/BSM_Templates_updatepropation.radsh script.

If you re-execute the $TBSM_HOME/install/BSM_Templates.radsh script
to re-create the templates, the rules will be configured with
the instance propagation option.


2) The recommended version of JRE plugin is Sun JRE 1.7.0_51 or 1.8 for
Internet Explorer and Firefox.

3) Additional toolkit customization has been made. To pick up these
changes, run the following commands on the Data Server:

Windows:

cd %TBSM_HOME%\install
type BSM_TemplateUpdates611FP0003.radsh | %TBSM_HOME%\bin\rad_radshell

UNIX:

cd $TBSM_HOME/install
cat BSM_TemplateUpdates611FP0003.radsh | $TBSM_HOME/bin/rad_radshell

4) As noted in the following Technote, When configuring pages in DASH
(JazzSM) for TBSM datasets, it is often desirable to create them
in a development environment and then later move them to
production, perhaps via a test environment. With this Fix Pack and
in conjunction with JazzSM 1.1 Fix Pack 2, there is no need to create
two connections any longer.

http://www.ibm.com/support/docview.wss?uid=swg21660077

5) TBSM 6.1.1 Fixpack 1 adds a new UI data provider data source that
provides new datasets corresponding to the customer's tree templates.
This allows the same data to be visualized in the legacy Service Tree
as well as on a JazzSM/DASH page.


6.5 Additional Browser Support with Fix Pack 4
------------------------------------------
TBSM 6.1.1 supports FF ESR 38 as of Fix Pack 4 (with TIP 2.2.0.17).
As well as, Internet Explorer 11 (Compatibility Mode)


6.6 Additional Browser Support with Fixpack 3

None!

6.7 Additional Browser Support with Fixpack 2
-----------------------------------------

TBSM 6.1.1 supports FF ESR 10 and FF17 with Fix Pack 1 on TIP 2.2.0.11 (or below).

This Fix pack supports Internet Explorer 9(IE9) in
"Internet Explorer 9" browser mode which is the default mode, not
in "Internet Explorer 9 Compatibility View" browser mode.
The document mode is automatically set by TIP and should remain
'IE7 standards'.

IBM strongly recommends updating to TIP 2.2.0.15 version 2 (v2) if
support is required for FF ESR 24/31 and/or IE10/11

See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all



6.8 eWAS Fixes and Upgrades
-----------------------

Please Note: The TBSM 6.1.1 Fix Pack will upgrade WebSphere (eWAS) on the Data
server automatically, to version 7.0 Fix Pack 39 (7.0.0.39) but, only if the Dashboard
server is not installed on that environment. If the Dashboard server is installed on the
same server (in the case of a single server environment), the eWAS will not be upgraded.

eWAS upgrade, on the TBSM Dashboard server and on "Single server" environments, will
take place when TIP 2.2.0.17 is applied.

If un-installing TBSM 6.1.1 Fix Pack, refer to section 3.9 "Uninstalling the Fix Pack"
to manually remove eWAS 7.0.0.39 (on Data server only environments!).


6.9 OMNIbus 8.1
-----------
TBSM 6.1.1 Fix Pack 1 supports the use of OMNIbus 8.1. But, please note that
OMNIbus 8.1 is a separate install, requiring additional configuration changes to
make it work with TBSM. Refer to "IBM Tivoli Netcool OMNIbus Considerations" section
of the "Exploring TBSM" Guide:

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_c_netcool_omnibus.html

If using OMNIbus 8.1, IBM recommends upgrading to the latest 8.1
maintenance level (at the moment, Fix Pack 2).

If using JazzSM/DASH to display TBSM resources, the Event Viewer and/or AEL may fail to display the appropriate
TBSM events if (1) a Data Source is not setup to point to TBSM's OMNIbus and (2) the custom TBSM filters and views are
not defined to WebGUI. To setup the WebGUI views, it will be required to copy the following file from
the TBSM Dashboard server to a temporary location on the JazzSM server:

<installdir>/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/webtopcore/create_tbsm_views.xml

In addition to copying the file to the JazzSM server, it is necessary to execute the runwaapi command, to load filters/views
the WebGUI. On the JazzSM/DASH server, execute the following command:

<installdir>/netcool/omnibus_webgui/waapi/bin/runwaapi -file create_tbsm_views.xml -user <admin> -password <password>

Please refer to the integration document found in "Advanced Topics"
at the TBSM developerWorks site, for this and other topics:

TBSM developerWorks Advanced Topics: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics
Integration document: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=7d5ebce8-2dd8-449c-a58e-4676134e3eb8#fullpageWidgetId=Wea1cb2531f10_4ccd_99d7_6ab0334cb21f&file=c6d51b71-362e-44be-8aa2-650da0918ac7


6.10 DB2
---
Starting with TBSM 6.1.1 Fix Pack 2, TBSM supports the use of DB2
version 10.5.3


6.11 TADDM 7.3 Integration
---------------------
For import of Business Applications from TADDM 7.3 to TBSM 6.1.1, the
property com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility
must be set to "true" in collation.properties file (located under
taddm/dist/etc). This will be true by default for upgraded TADDM 7.3
servers. It is false by default for fresh TADDM 7.3 installs.

Note: TADDM restart is required after property modification.

If com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility is
flipped from false to true, then all Business Applications need to be
re-build, to regenerate backward compatible Business Applications. This
can be done by either waiting for scheduler to process all Grouping
Patterns (and recreate new and old Business Applications) or by manually
executing (all or selected) Grouping Patterns from TADDM UI (or command
line).

NOTE: Starting TBSM 6.1.1 Fixpack 4, the default value set for TADDM
port in the toolkit configuration file is 9433 instead of 9530.
Port 9433 is the default port number used in TADDM versions
7.2.2 and above.
The installer will not override the existing copy of toolkit
configuration xmltoolkitsvc.properties, but a copy with
updated comments on TADDM ports can be found in directory
$TOOLKIT_HOME/bin/install. To reconfigure TADDM ports if
necessary, please use the taddmconfig command:
taddmconfig.sh -e

=======================================================================
7.0 Known issues -
------------

7.1 Some date options in TBSM Reports do not work

When specifying the date parameters for reports, some options
like "last 30 days" do not work. However, one can get this data
for the reports by selecting the Date Range and choosing the
dates from the calendar. Below is a link to the TBSM reports in
our Service Configuration guide which outlines how to run reports.

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/ServiceConfigurationGuide/bsmu_rept_view_reports.html



7.2 Issues creating wire between Service Tree and Active
Event List (AEL)

If the user creates a wire between the Service Tree and AEL
when a page is first created, the wire does not work. The
workaround for this is to create a wire by editing the page
after the page has been created and saved.



7.3 TBSM Agent Chart title differs from name in the
drop down list

Name displayed at the top of a TBSM Agent Chart differs from
the name of that chart in the drop down list. For eg,
the chart name in the drop down list is "kr9_TBSM Service Status"
and the name shown at the top of the chart is "Kr9:KR91003".
The name at the top can be changed to display the same name
as the drop down list by going to Preferences and changing
the chart name.



7.4 Minimize-restore does not restore to correct size for
Service Navigation->Data/Data Fetchers on Internet Explorer(IE)9

In the Service Navigation->Data/Data Fetchers portlet, after the
minimize option has been exercised to minimize the portlet, the
portlet is not resized correctly after using the 'restore' option.
The window resizes to a smaller size. This is an issue on
Internet Explorer(IE) 9 but not on Firefox or on Internet
Explorer(IE) 8. In order to go back to the original size,
select 'maximize' and 'restore'.



7.5 Portlets covering content in a free form page

When creating free form pages, the Service Viewer and Active Event
List(AEL) portlets will always be on top of any content. This can
interfere with page layout and editing of portlet preferences.
To alleviate this issue, it is best to place these portlets
onto the created page last to avoid having other content covered
by them. If a page requires editing and contains Service Viewer
or Active Event List portlets, it may be necessary to move
those portlets out of the way before editing preferences of
other portlets.



7.6 Creation and deletion of Services and Templates that contain
special characters

Due to new security additions the deletion of services and templates
that contain the characters '+', '&', '<','>','%',' " ', is not
permitted through the browser. Some of these characters are
permitted on the creation of services, as services can still be
created with these through auto population and importing. The
deletion of these services will now have to be carried out
through the radshell command deleteServiceInstance.

More information on the command can be found here.

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/adminguide/bsma_shlr_service_delete.html




7.7 WEBSERVICES SECURITY NOT FUNCTIONAL
If using WebService Security when making a WebService call,
(callProps.EnableWSS=true), the jar file
tipv2/plugin/org.apache.axis2.jar must be replaced by the jar
file tbsm/lib3p/org.apache.axis2-woden.jar and the newly replaced
file must be renamed to org.apache.axis2.jar.

Restart is required.

7.8 If using WEBSERVICES SECURITY (WSS) user authentication, then the
impact/dsa/wsdsa/wss/conf/wscb.properties needs to be altered to
only have one entry. If there is more than one entry in the file,
only the uid.1 and pwd.1 will be read

7.9 Microsoft Internet Explorer 11.
IE11 (supported only with TIP 2.2.0.15 and above) may cause
unexpected behavior in the Policy Editor, whereby the Policy List
panel disappears when the Project drop-down menu is selected. To
circumvent this, simply click on a different project in the Project
drop-down list and then click again on the desired project, to
restore the correct layout

7.10 With certain Solaris installations the Event Summary portlet
(Administration -> Service Administration -> Services) may fail to
render and cause an Out Of Memory (PermGen) exception (as seen in
the TIP trace log:
"java.lang.OutOfMemoryError: PermGen space exception")


Solution:
1. Stop TBSM (kill the hung server if necessary).

2. Goto the $TBSM_HOME/tipv2/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1
directory and make a backup of the server.xml file.

3. Open the server.xml file for editing and in the jvmEntries xmi
tag modify the genericJvmArguments attribute to read something
like this, where these two PermSize and MaxPermSize parms are
being added (if other parms are already code, please preserve
those parms and just insert the two new ones):

genericJvmArguments=" -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+DisableExplicitGC"

4. Save the file and restart TBSM.


7.11 TIP Portlet blank or does not load after TIP 2.2.0.15 installation
Refer to the following Technote for resolution:

http://www.ibm.com/support/docview.wss?uid=swg21696426

NOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)

7.12 TIP chart portlet blank if TBSM Service Admin page is closed and
re-opened
Refer to the following Technote for resolution:

http://www.ibm.com/support/docview.wss?uid=swg21696424

NOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)

7.13 Java Security Warnings
With the ever changing security improvements to both the browsers
Java Runtime Environment (JRE), clients are now more likely to see
warning messages about untrusted connections or invalid
certificates. To avoid those issues, clients can replace the IBM
HTTP Server SSL certificate with an SSL certificate signed by a
third-party CA. For guidance on that task, refer to the following
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21424371

=======================================================================
8.0 Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

8.1 Notices

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 jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may 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.

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

Intel®, Intel logo, Intel Inside®, Intel Inside logo, Intel® Centrino®,
Intel Centrino logo, Celeron®, Intel Xeon®, Intel SpeedStep®, Itanium®,
and Pentium® are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other
countries.

Other company, product, or service names may be trademarks or service
marks of others.

Please read THE IBM Tivoli Business Service Manager NOTICES AND
INFORMATION in the file notices1.txt included in this Fix Pack before
you proceed with the download and installation of this Fix Pack. You can
find the additional notices file on the same web page as this Fix Pack.

8.2 THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to certain
software code. The relevant terms and conditions, notices and other
information are provided or referenced below. Please note that any
non-English version of the licenses below is unofficial and is provided
to you for your convenience only. The English version of the licenses
below, provided as part of the English version of this file, is the
official version.

Notwithstanding the terms and conditions of any other agreement you may
have with IBM or any of its related or affiliated entities (collectively
"IBM"), the third party software code identified below are "Excluded
Components" and are subject to the following terms and conditions:

* the Excluded Components are provided on an "AS IS" basis
* IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND
THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE
* IBM will not be liable to you or indemnify you for any claims related
to the Excluded Components
* IBM will not be liable for any direct, indirect, incidental, special,
exemplary, punitive or consequential damages with respect to the
Excluded Components.

8.3 Apache Woden Distribution

===============================================
== NOTICE file corresponding to the section 4 d of ==
== the Apache License, Version 2.0, ==
== in this case for the Apache Woden distribution. ==
===============================================

This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).

This product also includes software developed by :

- IBM Corporation (http://www.ibm.com),
WSDL4J was the initial code contribution for the Apache Woden
project and some of the WSDL4J design and code has been reused.
- The W3C Consortium (http://www.w3c.org),
Common W3C XML Schema and DTD files are packaged with Apache Woden.

Please read the different LICENSE files present in the root directory of
this distribution.

===========================================================================
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/


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

WODEN SUBCOMPONENTS:
For any subcomponents included with the Woden source code that contain
separate copyright and license terms, their License information is appended
below, in this file.
For any binary subcomponents redistributed with Woden under separate
licenses, their license files are included alongside those binary packages
in the Woden release files (for example, alongside the dependant jar files
in the /lib directory of the Woden zip file).

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

For the W3C schema and DTD files in the org.apache.woden.resolver package:

W3C® SOFTWARE NOTICE AND LICENSE
http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
This work (and included software, documentation such as READMEs, or other
related items) is being provided by the copyright holders under the following
license. By obtaining, using and/or copying this work, you (the licensee) agree
that you have read, understood, and will comply with the following terms and
conditions.

Permission to copy, modify, and distribute this software and its documentation,
with or without modification, for any purpose and without fee or royalty is
hereby granted, provided that you include the following on ALL copies of the
software and documentation or portions thereof, including modifications:

The full text of this NOTICE in a location viewable to users of the
redistributed or derivative work.

Any pre-existing intellectual property disclaimers, notices, or terms and
conditions. If none exist, the W3C Software Short Notice should be included
(hypertext is preferred, text is permitted) within the body of any redistributed
or derivative code.

Notice of any changes or modifications to the files, including the date changes
were made. (We recommend you provide URIs to the location from which the code is
derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE
OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or
publicity pertaining to the software without specific, written prior permission.
Title to copyright in this software and any associated documentation will at all
times remain with copyright holders.
____________________________________

This formulation of W3C's notice and license became active on December 31 2002.
This version removes the copyright ownership notice such that this license can
be used with materials other than those owned by the W3C, reflects that ERCIM is
now a host of the W3C, includes references to this specific dated version of the
license, and removes the ambiguous grant of "use". Otherwise, this version is the
same as the previous version and is written so as to preserve the Free Software
Foundation's assessment of GPL compatibility and OSI's certification under the
Open Source Definition. Please see our Copyright FAQ for common questions about
using materials from our site, including specific terms and conditions for packages
like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed
to site-policy@w3.org.

Joseph Reagle <site-policy@w3.org>

Last revised $Id: copyright-software-20021231.html,v 1.11 2004/07/06 16:02:49 slesch Exp $

===========================================================================
This license came from: http://www.megginson.com/SAX/copying.html
However please note future versions of SAX may be covered
See http://www.saxproject.org/faq.html


This page is now out of date -- see the new SAX site at
http://www.saxproject.org/ for more up-to-date
releases and other information. Please change your bookmarks.


SAX2 is Free!

I hereby abandon any property rights to SAX 2.0 (the Simple API for
XML), and release all of the SAX 2.0 source code, compiled code, and
documentation contained in this distribution into the Public Domain.
SAX comes with NO WARRANTY or guarantee of fitness for any
purpose.

David Megginson, david@megginson.com
2000-05-05
=======================================================================

8.4 IBM obtained Smack V3.3.0 under the following license from Apache Software Foundation:

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

Prerequisites


IBM Tivoli Business Service Manager 6.1.1

Installation Instructions


=======================================================================
3.0 Installation information
------------------------

3.1 Dependencies

This Fixpack must be installed on each server(s) that is running
the TBSM data server or TBSM dashboard server.

This Fixpack requires IBM Tivoli Business Service Manager
Version 6.1.1 to be installed.

3.2 Prerequisites
-------------

Tivoli Integrated Portal 2.2.0.17 version 3 (v3) has been certified. It
can be installed after installing this fix pack.

IBM strongly recommends updating to TIP FP 2.2.0.17 v3, if support is
required for FF ESR 38 and IE11. If the TBSM data server and dashboard
server are installed on different machines, the TIP Fix Pack needs to be
installed only on the dashboard server. In case of a TIP HA environment,
the HA nodes need to be disjoined first before upgrading to TIP FP.

See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.17&platform=All&function=all

Post installation of TIP 2.2.0.17 v3 requires a re-start of the
Dashboard server and clearing of all user's browser cache!



3.3 Special considerations and Notices
----------------------------------

* Announcement of future withdrawal from support of TADDM 7.2.0
and 7.2.1 has been made. Refer to the following link for
more info:

https://www.ibm.com/developerworks/community/blogs/7d5ebce8-2dd8-449c-a58e-4676134e3eb8/entry/Announcement_of_future_withdrawal_from_support_for_TADDM_7_2_0_and_7_2_1?lang=en

* Starting TBSM 6.1.1 Fixpack 4, the default value set for TADDM
port in the toolkit configuration file is 9433 instead of 9530.
Port 9433 is the default port number used in TADDM versions
7.2.2 and above.
The installer will not override the existing copy of toolkit
configuration xmltoolkitsvc.properties, but a copy with
updated comments on TADDM ports can be found in directory
$TOOLKIT_HOME/bin/install. To reconfigure TADDM ports if
necessary, please use the taddmconfig command:
taddmconfig.sh -e

* The Java plug-in for web browsers relies on the cross platform
plugin architecture NPAPI, which has been supported by all major
web browsers for over a decade. However, Mozilla intends to
remove support for most NPAPI plugins in Firefox by the end of
2016. Oracle has announced that it is to depreciate the Java
browser plug-in technology with the next release of the Java
platform (JDK9). Because of these industry moves, TBSM is
announcing the end of support for the Service Viewer (and custom
canvases). These features will be removed from the product in
Fix Pack 5. Customers are advised to replace custom canvas usage
with IBM Dashboard Application Services Hub pages, as soon as
possible. See link:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.ibm.tivoli.itbsm.doc/adminguide/bsmu_jazz_c_overview.html?lang=en.

Detailed information on the TBSM Datasets available for use with
DASH widgets is available in the "Advanced Topics" section of the
Tivoli Business Service Manager Wiki at
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Business+Service+Manager1/page/Advanced+Topics.

* Deprecation for Jazz(tm) for Service Management Registry Services is
due with version 1.1.3 and thus the Open Services Lifecycle
Collaboration (OSLC) Hover Preview functionality, which uses this
feature, is also deprecated, when used with versions or Jazz(tm) for
Service Management equal to or greater than version 1.1.3

* Integration between Tivoli Business Service Manager and
Tivoli Common Reporting (TCR) version 2.x is no longer supported,
as end-of-service for TCR 2.x is announced for April 2016.
For Tivoli Business Service Manager reports, use Tivoli Common
Reporting (TCR) 3.1 or higher. The Tivoli Business Service
Manager Infocenter has been updated to reflect this change.

* Support for TBSM BIRT reports has already been announced.
Support for BIRT reports with JazzSM will be deprecated
in future JazzSM releases (post 1.1.3). However, all shipped
TBSM BIRT reports already have a Cognos equivalent. It is
recommended to ensure that the Cognos versions of the reports
are being used, and to migrate custom BIRT reports to Cognos
as soon as possible. Support for Business Intelligence and
Reporting Tools (BIRT) reports has been deprecated in TBSM 6.1.1.
However, the BIRT reports provided previously with TBSM are
available for use until such time as JazzSM support for BIRT
is announced. An equivalent Cognos report is available for
each of the BIRT reports.

* The following browser version are no longer supported with
Fix Pack 4:

Firefox 17 ESR
Firefox 24 ESR
Firefox 31 ESR

Internet Explorer 8
Internet Explorer 9
Internet Explorer 10

* TBSM integration with ISM is no longer operational and therefore,
not supported with TBSM 6.1.1 This modification is due to changes
in the supported versions of ITCAM for Transaction / ISM


Consider this information before you install the Fix Pack:
1. You will be prompted during the installation to specify a backup
directory name. The installer backs up DE at this location.

2. This Fixpack does not backup the entire application. It only
backs up the files that it has updated/replaced. A backup copy of the
original files can be retrieved from:
[InstallDirectory]/tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0004

3. The TBSM and TIP processes or services may remain running but, will
be re-started during the Fix Pack install process. If the processes
or services are manually stopped, prior to the Fix Pack install,
please make sure both the OMNIbus Object server and DB2 processes or
services remain running! Both DB2 and OMNIbus are required components
that will prevent the TBSM Data server from successfully starting,
specially during the Fix Pack install re-starts.

NOTE: The installer will start/stop the TBSM and TIP services as
needed, during the install process.

On Linux/Unix: perform the following

1. To stop the TBSM Data server issue the following command:

$TIP_HOME/profiles/TBSMProfile/bin/stopServer.sh server1
-username <adminuser> -password <adminpassword>

2. To stop the TBSM Dashboard server, issue the following
command:

$TIP_HOME/profiles/TIPProfile/bin/stopServer.sh server1
-username <tipadminuser> -password <adminpassword>

By default, username is tipadmin and password is the
tipadmin password.

3. To stop the TBSM Discovery Library Toolkit issue the
following command:

$TBSM_HOME/XMLtoolkit/bin/tbsmrdr_stop.sh

On Windows:

1. In the Start menu, click Settings -> Control Panel
-> Administrative Tools -> Services.

The Services window opens. Depending on what services
you have installed, the available services are as follows:

Tivoli Business Service Manager - TBSMProfile_Port_17310.
This is the Data server.
Tivoli Integrated Portal - V2.2_TIPProfile_Port_16310.
This is the Dashboard server.
Tivoli BSM Discovery Library toolkit
EIF probe
This service appears only if the EIF probe was installed
as a Windows service.

2. Right-click the service that you want to stop and click Stop.


4. All non-vital programs should be closed prior to installation of
the Fixpack.


3.4 Superceded Fixes
----------------

6.1.1.0-TIV-BSM-IF0001 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0002 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0003 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0004 is superceded by this Fix Pack.
6.1.1-TIV-BSM-FP0001 is superceded by this Fix Pack.
6.1.1-TIV-BSM-FP0002 is superceded by this Fix Pack.
6.1.1-TIV-BSM-FP0003 is superceded by this Fix Pack.


3.5 Extracting Fix Pack files
-------------------------

3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX
platforms

1. Copy the file 6.1.1-TIV-BSM-FP0004-<ARCH>.tar to a temporary
location on your TBSM Server.

2. Unpack the file on each host where you need to install the Fix
Pack using these commands:

tar -xvf 6.1.1-TIV-BSM-FP0004.<ARCH>.tar


3.5.2 Extracting on Windows platforms
-------------------------------

1. Copy the 6.1.1-TIV-BSM-FP0004-windows.zip file to a temporary
location on your TBSM server host.

2. Unzip the file on each server where you need to install the Fix Pack.


3.5.3 Fix pack directories
--------------------

When you extract the file, these directories are created:

TBSM -TBSM data server and dashboard server and TIP updates.

DiscoveryLibrary -Discovery Library Toolkit updates

<ARCH>/Reports

Samples


3.6 Maintenance upgrade strategy
----------------------------

Before you install the Fix Pack, you need to plan how and when you will
upgrade each TBSM server in your environment.


3.6.1 Example maintenance scenario
----------------------------

In this example, the maintenance is staged into two phases to
reduce the time required for the TBSM maintenance window.

In this example environment, there are four servers:
* primary data server
* backup data server
* two dashboard servers set up for load balancing called: dash1
and dash2

Follow this sequence:

Before you start the maintenance window:
1. Upgrade backup data server
2. Upgrade one dashboard server (for example dash2)
3. Use the primary data server and dash1 for regular production
activities

After you complete the upgrade the two secondary servers, start
the maintenance window down time for the production servers.
1. Upgrade primary data server
2. Upgrade dash1

After you complete the upgrade for all the servers:
1. Start primary data server
2. Start backup data server
3. Wait until TBSM completes the server synchronization.
4. Start the dashboard servers.


3.7 Installation
------------


3.7.1 Installing the Fix Pack
-----------------------

[Fix Pack] Refers to the directory where you extracted the Fix
Pack files from the zip/tar file.

Attention: Install the Fix Pack with the same user that was
used to install TBSM 6.1.1 GA


NOTE: If you have deployed the Service Level Objectives (SLO)
Reporting Function, you must do the following before
installing the Fix Pack:

- Stop all Impact services that are running policies that
call the SLO functions to record data in the SLORPRT
database. If you have the service set to start at
server startup, then turn this option off before
installing the fixpack, as the server is restarted
during the fixpack install.

Running the install without DE backup:

If you prefer to backup DE with your own procedures you can
run the install with the following parameter.

-DNO_BACKUP=true

(for Silent Install, uncomment the "NO_BACKUP=true"
parm on the setupFP.rsp response file)

If you choose this method, you must backup DE before you install.
And restore the original system using your backup/restore
procedures or utilities (if uninstalling the Fix Pack).

Follow this procedure to install the Fix Pack:

1. On the Tivoli Business Service Manager server host, change to the
[Fix Pack]/TBSM directory where you extracted the files.
2. Run the installation using one the following commands:
* setup-windows.exe - Windows.
* setup-<unixplatform>.bin - other operating systems.

Installation command options:

GUI mode No options, for example:
Windows: setup-windows.exe

or

UNIX® : ./setup-<unixplatform>.bin

Console mode
Use the -i console option.
For example -
Windows: setup-windows.exe -i console

or

UNIX® : ./setup-<unixplatform>.bin -i console

Silent Mode

a. Copy setupFP.rsp from the TBSM directory of the extracted
Fix Pack file ([Fix Pack]/TBSM) to a location it can be
edited (/tmp).
b. Update the file to match your environment.
c. Confirm acceptance of license, by un-commenting this line
and setting the parm to "true":
#LICENSE_ACCEPTED=false
d. Run:

Windows: setup-windows.exe -f C:\tmp\setupFP.rsp

or

UNIX® :setup-<unixplatform>.bin -f /tmp/setupFP.rsp

Note: The response file needs to have a fully qualified
path.

3. During the install you will be asked to to verify
path names to the TIP install.

4. Restart both the Data and Dashboard processes/services

5. After install is complete (and with the data server started), run
the script ApplyPoliciesFor611FP4, which can be found on the Data
Server under $TBSM_HOME/bin. This script loads the new/updated
policies.

NOTE: Do not run the ApplyPoliciesFor611FP4 on the secondary/
backup data server of a failover pair. This only needs to
be run on the primary data server.

On Windows:

ApplyPoliciesFor611FP4.bat <adminuser> <adminpassword>
For example - ApplyPoliciesFor611FP4.bat tipadmin tipadmin

On Linux/Unix:

./ApplyPoliciesFor611FP4 <adminuser> <adminpassword>
For example - ./ApplyPoliciesFor611FP4 tipadmin tipadmin

NOTE: Verify that the admin user id and password are
correct otherwise, the script will fail at the last step.

If incorrect, rerun the script with a valid adminuser id
and password.

6. From the TBSM 6.1.1 Fix Pack 4 install media, copy these files
onto the DB2 server (where the tbsmdb was initially installed,
when TBSM was first setup).

from: [Fix Pack]/TBSM/TBSMDBChecker
to: [InstallDirectory]/tbsmdb/bin

TBSM_Check_DB.bat
TBSM_Check_DB.sh
tbsmDatabaseChecker.xml
TBSMDBChecker.props

NOTE: The above action is only needed if you ever plan to use
the TBSM_Check_DB script, which will now suppress the
display of the requested user password.

7. After installing this Fix Pack, end-users may need to clear their
browser cache, close and re-open the browser; in order to avoid
any issues on the client side.

8. If the Impact "Service Level Objectives (SLO) Reporting"
function was enabled, please refer to section 3.12 for additional
post Fix Pack installation required actions.

9. Please refer to section 4.0 "Additional information for TBSM Fix Pack 4 APARS"
for additional post install actions.


3.7.2 Discovery Library Toolkit
-------------------------

NOTE 1: Announcement of future withdrawal from support of TADDM 7.2.0
and 7.2.1 has been made. Refer to the following link for
more info:

https://www.ibm.com/developerworks/community/blogs/7d5ebce8-2dd8-449c-a58e-4676134e3eb8/entry/Announcement_of_future_withdrawal_from_support_for_TADDM_7_2_0_and_7_2_1?lang=en

NOTE 2: Starting TBSM 6.1.1 Fixpack 4, the default value set for TADDM
port in the toolkit configuration file is 9433 instead of 9530.
Port 9433 is the default port number used in TADDM versions
7.2.2 and above.
The installer will not override the existing copy of toolkit
configuration xmltoolkitsvc.properties, but a copy with
updated comments on TADDM ports can be found in directory
$TOOLKIT_HOME/bin/install. To reconfigure TADDM ports if
necessary, please use the taddmconfig command:
taddmconfig.sh -e

1. Navigate to the DiscoveryLibrary directory.

2. To install Fixpack 4,

If you are on a Windows operating system, run the following
command from a prompt:

setup-dltoolkit-6.1.1-FP0004-windows_64.exe

If you are on a Unix operating system, run the following
command from a prompt:

setup-dltoolkit-6.1.1-FP0004-<unixplatform>_64.bin

For console mode, specify "-i console".

Note: If the installer cannot find the TBSM 6.1.1 Discovery
Library Toolkit, verify that the toolkit is installed and
that it was installed by the user that the fixpack is being
installed with. If these are both okay, then set the environment
variable TBSM_TOOLKIT_BASE to the location of the toolkit and
restart the toolkit installer. For example:
Windows:
set TBSM_TOOLKIT_BASE=C:\Program Files\IBM\tivoli\tbsm\XMLtoolkit
UNIX:
export TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit

3. The toolkit installer requires access to the database.


4. Restart the toolkit.


3.8 TBSM agent
----------

Installing the TBSM agent:

The following packages are available for download in the TBSMAgent
directory on the support download site:

* AIX: KR9_aix526CD-6.1.1-TIV-BSM-FP0004.tar.gz -AIX (64 bit)

* Linux: KR9_lx8266CD-6.1.1-TIV-BSM-FP0004.tar.gz -Li x86_64R2.6(64 bit)

* Solaris: KR9_sol286CD-6.1.1-TIV-BSM-FP0004.tar.gz -Solaris R8(64 bit)

* Windows: KR9_wix64CD-6.1.1-TIV-BSM-FP0004.zip -(64 bit)

* zLinux: KR9_ls3266CD-6.1.1-TIV-BSM-FP0004.tar.gz -Li S390R2.6(64 bit)


To install the updated TBSM agent, if not already installed:
1. Download the appropriate agent code for your platform.
2. Untar or unzip the file.
3. Install the agent according to the directions in the TBSM
Installation Guide. This is a complete install package for the TBSM
agent support and can be used for a fresh install of the agent.

For instructions on installing and configuring the TBSM agent, see:

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html


3.9 Uninstalling the Fix Pack
-------------------------

Before uninstalling the FixPack all TBSM processes should be
STOPPED. The user must manually stop the TBSM processes, before
the uninstall of the FixPack (except for OMNIbus and DB2).

Attention: Uninstall the Fix Pack with the same user that was used to
install TBSM 6.1.1 GA.

Silent mode and uninstall


If silent mode was used for the install, the uninstall will
default to a silent uninstall and you must supply a response
file or the uninstall will fail.

For silent mode uninstalls, copy the setup_uninstall.rsp file
from the Fix Pack image to the directory:

<installDir>/tbsm/_uninst/TBSM611_FP4

and update the file with the correct information. Then launch
the installer specifying the file. For example:

uninstall(.exe) -f /tmp/setup_uninstall.rsp

Note: The response file needs to have a fully qualified path.

On the Tivoli Business Service Manager server system:

1. Change to the directory:
<installDir>/tbsm/_uninst/TBSM611_FP4

2. Run the uninstall command:

UNIX: If you are on a Unix operating system, run the following
command from a prompt.

./uninstall


Windows: If you are on a Windows operating system, run the following
command from a prompt.

.\uninstall.exe

For console mode, specify "-i console"

3. After the command has completed, run the following commands to clear
the server cache.

Linux/AIX: <TIP_HOME>/bin/clearClassCache.sh

Solaris: java -Xshare:dump

Windows: <TIP_HOME>\bin\clearClassCache.bat



4. Uninstall eWAS 7.0.0.39

NOTE: On a "Data server only" environment, the TBSM 6.1.1 Fix
Pack 4 un-installer will not remove the upgraded eWAS
7.0.0.39 Fix Pack it installed. If there are plans to, at
a future time, re-install TBSM 6.1.1 Fix Pack 4, it is
necessary to manually un-install eWAS 7.0.0.39.

These steps DO NOT apply to a "Dashboard sever only"
environment or a "Single server" environment, where both the
Data and Dashboard are installed together.

Again, these steps are only needed on a "Data server only"
environment. Failure to perform these actions, will prevent
the re-install of TBSM 6.1.1 Fix Pack 4!

a). Copy the uninstall-WASEmbeded.txt to a temporary location
The uninstall-WASEmbeded.txt file is located on:
<installdir>/tbsm/_uninst/TBSM611_FP4/plan/install/MachinePlan_localhost/00002_WASFP/uninstall-WASEmbeded.txt

For example on Unix:
/opt/IBM/tivoli/tbsm/_uninst/TBSM611_FP4/plan/install/MachinePlan_localhost/00002_IAGLOBAL_COI_STEP_WASFP/uninstall-WASEmbeded.txt

For example on Windows:
C:\IBM\tivoli\tbsm\_uninst\TBSM611_FP4\plan\install\MachinePlan_localhost\00002_IAGLOBAL_COI_STEP_WASFP\uninstall-WASEmbeded.txt


Or from the TBSM 6.1.1 FP4 install media:
6.1.1-TIV-BSM-FP0004-<ARCH>\TBSM\COI\PackageSteps\WASFP\uninstall-WASEmbeded.txt


b). Edit the uninstall-WASEmbeded.txt (on the temporary location)

c). locate this line: -W product.location="@IAGLOBAL_WAS_HOME@"

d). Replace above line with: -W product.location="<installdir>/tipv2"

Where <installdir> is the fully qualified directory where tipv2 located:

for example (Unix): -W product.location="/opt/IBM/tivoli/tipv2"

for example (Windows): -W product.location="C:\IBM\tivoli\tipv2"

e). Save the uninstall-WASEmbeded.txt file (on the temporary location)

f). Execute the following command:
On Unix:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.sh -options <templocation>/uninstall-WASEmbeded.txt -silent

for example: /opt/IBM/tivoli_root/tipv2/WebSphereUpdateInstallerV7/update.sh -options /tmp/uninstall-WASEmbeded.txt -silent

On Windows:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.exe -options <templocation>/uninstall-WASEmbeded.txt -silent

for exampe: C:\IBM\tivoli\tipv2\WebSphereUpdateInstallerV7\update.exe -options C:\Temp\uninstall-WASEmbeded.txt -silent

5. Restart the Data Server and Dashboard Server.



Discovery Library Toolkit
===================================================

The Toolkit portion of this fixpack cannot be uninstalled.
A backup copy of the original files can be retrieved from:

[InstallDirectory]/tbsm/
XMLtoolkit/log/install/maintenance/backup/611FP0004



3.10 Recovering from a failed Fix Pack install
-----------------------------------------

If the install fails, try to uninstall in which case, it goes back to
the previous version. If there is no uninstall file under
_uninst/TBSM611_FP4, then nothing really got installed and you can delete
the TBSM611_FP4 file and reinstall.


3.11 Restoring failed DE upgrade from backup
---------------------------------------

To recover a failed Deployment Engine upgrade in TBSM 6.1.1, see the
TBSM Installation Guide at:

http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.4/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html


3.12 "Service Level Objectives (SLO) Reporting" function
---------------------------------------------------

The information in this section applies only if you have deployed
the Impact Solution called "Service Level Objectives (SLO)
Reporting". The SLO function is enhanced by Fixpack 4 for:

* Automatic pruning of the table of outage data used in the
reports

* Capability to delete service, SLA, and calendar definitions

* Improved TBSM sample policy to only consider "Bad" status as an
outage

* Capability to export service and calendar definitions

* Utility functions for removing and restoring specific outage
data

* Bug fixes and updated documentation

This function is documented on the following page in the Knowledge
Center:
http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.4/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html?lang=en

If you have not deployed this solution, then you can skip this section.

Before you install the Fixpack:
1) Stop all Impact services that are running policies that call
the SLO functions to record data in the SLORPRT database.
2) If you have the service set to start at server startup, then
turn this option off before installing the fixpack, as the
server is restarted during the fixpack install.


After installing the Fixpack, but before restarting any SLO
services, update the SLORPRT database schema using the following
steps:

a) You will need access to the machine where the SLORPRT
database was installed. If this database has not been
installed, then the SLO solution has not been deployed
and there is no need to continue this update to the schema.

b) It is recommended to make a backup of the SLORPRT database
before continuing.

c) Copy sql files needed to update the SLORPRT database schema:

If you have not previously installed Fixpack 3, copy files
add_timezone.sql and update_views_timezone.sql from
[InstallDirectory]/impact/add-ons/slo/db to a location
accessible from the system you will use to update the
database schema in the next step.

Copy file sloutility.sql from
[InstallDirectory]/impact/add-ons/slo/db to a location
accessible from the system you will use to update the
database schema in the next step.

d) Open a DB2 command window on a system with access to the
SLORPRT database and run the following commands:

db2 connect to SLORPRT user dbuser using dbpassword
(replace dbuser and dbpassword with the user/password
specified in datasource SLOReportDatasource )

(Only if you have not previously installed Fixpack 3)
db2 -tvf <slo_sql_dir>/add_timezone.sql

(Only if you have not previously installed Fixpack 3)
db2 -tvf <slo_sql_dir>/update_views_timezone.sql

db2 -tvf <slo_sql_dir>/sloutility.sql

db2 connect reset

Where <slo_sql_dir> would be
[InstallDirectory]/impact/add-ons/slo/db if on the same
machine as the TBSM Data server, or the directory where you
copied the files in step b if the SLORPRT database is on
a different machine.

Fixpack 4 provides a new Impact project called SLA_Utility which
provides most of the enhancements to the SLO function. Import
this project as follows:

a) Navigate to the [InstallDirectory]/tbsm/bin directory
and run the following command:

nci_import.[bat/sh] <servername> [InstallDirectory]/impact/add-ons/slo/sloutility

After importing the project, update datasource SLOUtilityDatasource
to use the same SLORPRT database that is used by datasource
SLOReportDatasource.

When you have installed the fixpack, updated the SLORPRT database
schema, and imported the SLA_Utility project, start any Impact
services configured for SLO processing. If you originally
configured the service to start when the server starts, remember
to check that option again.

This fixpack includes the option to collect outage data from
TBSM Metric History only when the status in TBSM is Bad. Refer
to the Impact documentation for information on how to update the
SLO configuration to use this option.

On
[{"DNLabel":"6.1.1-TIV-BSM-FP0004-linux","DNDate":"29 Apr 2016","DNLang":"English","DNSize":"1579185108","DNPlat":{"label":"Linux","code":"PF016"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0004-linux&source=SAR","DNURL_FTP":" ","DDURL":null},{"DNLabel":"6.1.1-TIV-BSM-FP0004-aix","DNDate":"29 Apr 2016","DNLang":"English","DNSize":"1672247830","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0004-aix&source=SAR","DNURL_FTP":" ","DDURL":null},{"DNLabel":"6.1.1-TIV-BSM-FP0004-solaris","DNDate":"29 Apr 2016","DNLang":"English","DNSize":"1640493945","DNPlat":{"label":"Solaris","code":"PF027"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0004-solaris&source=SAR","DNURL_FTP":" ","DDURL":null},{"DNLabel":"6.1.1-TIV-BSM-FP0004-windows","DNDate":"29 Apr 2016","DNLang":"English","DNSize":"1578587559","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0004-windows&source=SAR","DNURL_FTP":" ","DDURL":null},{"DNLabel":"6.1.1-TIV-BSM-FP0004-zlinux","DNDate":"29 Apr 2016","DNLang":"English","DNSize":"1615403606","DNPlat":{"label":"Linux","code":"PF016"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0004-zlinux&source=SAR","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SSSPFK","label":"Tivoli Business Service Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.1.1","Edition":"Advanced","Line of Business":{"code":"LOB15","label":"Integration"}}]

Problems (APARS) fixed
IV21679 IV30875 IV33717 IV36878 IV38053 IV38471 IV38574 IV39167 IV39517 IV39796 IV42339 IV42657 IV42941 IV43098 IV43165 IV43469 IV43804 IV43865 IV44246 IV44582 IV45166 IV45386 IV45868 IV46098 IV46811 IV46876 IV48813 IV49791 IV50625 IV53791 IV54197 IV54587 IV55756 IV56050 IV56270 IV57273 IV59723 IV61668 IV54828 IV42339 IV46098 IV62456 IV62548 IV60168 IV56853 IV63608 IV65503 IV65786 IV59886 IV61880 IV64950 IV60750 IV60961 IV61199 IV62273 IV62294 IV62246 IV64933 IV65545 IV66210 IV65484 IV68113 IV60842 IV56450 IV65503 IV65786 IV62246 IV60619 IV61278 IV64797 IV65695 IV65825 IV65947 IV65949 IV65958 IV66535 IV66950 IV71255 IV72005 IV53193 IV69037 IV71194 IV75807 IV75972 IV76788 IV76901 IV76976 IV77455 IV77750 IV78284 IV81811 IV81987 IV82074 IV51097 IV54466 IV72900 IV73493 IV75380 IV76114 IV82185 ;IV11728 IV21717 IV22560 IV33973 IV34503 IV35827 IV35885 IV35940 IV36405 IV36503 IV37040 IV37369 IV37717 IV37759 IV38045 IV38585 IV38961 IV39368 IV40158 IV41888 IV42715 IV43030 IV43751 IV45068 IV45511 IV45569 IV45838 IV46099 IV46493 IV46696 IV46729 IV46799 IV47058 IV47799 IV47904 IV47988 IV48113 IV50464 IV50932 IV51062 IV53483 IV53810 IV53818 IV53822 IV53824 IV53825 IV53826 IV53827 IV53836 IV54939 IV55776 IV55778 IV55779 IV55780 IV55781 IV20165 IV37369 IV38585 IV40158 IV40179 IV43157 IV44875 IV45481 IV45569 IV46185 IV46512 IV47057 IV47454 IV50673 IV50776 IV51431 IV52651 IV18554 IV23315 IV64152 IV61089 IV63137 IV62792 IV61956 IV61746 IV61399 IV60005 IV60253 IV58616 IV58511 IV53717 IV56745 IV56068 IV55989 IV50329 IV56541 IV47748 IV55464 IV60923 IV59920 IV50058 IV58590 IV59481 IV59770 IV60438 IV61538 IV61725 IV63535 IV63942 IV64075 IV64837 IV65055 IV65179 IV66164 IV67091 IV67829 IV68383 IV69164 IV70836 IV71157 IV71513 IV73098 IV73243 IV59728 IV59840 IV66337 IV66441 IV68163 IV71068 IV72091 IV72561 IV72673 IV74071 IV74421 IV74485 IV75602 IV75913 IV77882 IV79004 IV79769 IV79910 IV80388 IV71068 IV73181 IV73633 IV75254 IV75734 IV79194

Document Information

Modified date:
15 June 2018

UID

swg24041505