This is a big one folks. You’re going to want to apply this if you’ve deployed TBSM v4.2. This updates Netcool/WebTop and TIP stuff as well! It’s not just bug fixes, this includes significant new capability and features. New layout options, new custom canvas gauges, Firefox 3 support!
READ the full READ ME here.
The Interim Fix is available for download here.
his Interim Fix addresses problems reported in IBM Tivoli Business Service Manager 4.2
* APARs that are included in this Interim Fix:
IZ25279 SETTING IMPACT.SLA.SECONDSTILLSTARTSTANDALONE ON BACKUP SERVER
When using the property: impact.sla.secondstillstartstandalone=5 To start the backup machine in standalone mode, the backup doesn’t start unless the primary has started first
IZ28625 SERVICE TREE IS MISSING INSTANCES UNDER INTERMEDIATE CHILD
When a new instances is created via an autopop rule and ESDA parent rule, and immediate services exist in the hierarchy that should be affected, the instance is not seen in the service tree. The service instances is seen in the TBSM database, the delete services window,and the add dependents view.
IZ29610 SERVICES DUPLICATE IN THE SERVICE TREE AFTER DESKTOP IS LEFT
Duplicate services appear at the root of the service tree. These services are the intermediate services that are displayed within a hierarchy creating instances via ESDA. The only time the instances show at the root of the tree is when the users digs into the service model to display the intermediate parents in the tree. When the intermediate instances are invalidated, they are deleted from the tree then added back right away. There relationships for the intermediate instances are not recalculated until a new tree is retreived from the server via a viewpoint refresh.
IZ30800 ESDA QUERY CAN NOT EXCEED 1024 BITES
When the customer tries to save a template which contains an ESDA rule which has a SQL query that exceeds 1024 characters, it fails.
IZ30976 ESDA INTERFACE NEEDS TO CHECK FOR ALLOWABLE CHARACTERS
When creating new services via ESDA, services are allowed to have newline and carriage return characters in their names. However,when this is allowed, the service cannot be shown in the service tree and the service cannot be exported.
IZ31843 PARENT SERVICES DELETED AFTER CHILD SERVICE IS INVALIDATED
If the connection to the datasource of an ESDA source is lost, such as in a cable pull situation, and the services are invalidated, the parents of the invalidated service are deleted and in some instances the remaining services are moved to the root of the tree.
IZ34892 NULL value in numerical rules
When the text rules pull in a value that has the value “NULL” or “null” the rule displays “0” on a custom service tree.
IZ37679 SERVICE VIEWER DOESN’T PAINT COMPLETELY, SOME BLANK AREAS
When the service viewer is expanded/maximized and then restored, the applet containing the service viewer does not occupy all the horizontal portlet realestate resulting in a large gray or white unused space. Additionally, there is a thin strip of white initially on IE only.
IZ38526 RAD FAILOVER&FAIL-BACK IS UNEXPECTEDLY UPDATING REMOTE OMNIBUS
If an event storm comes into omnibus during the TBSM failover process, the prior status will be shown instead of the new status and the tally field of the event increases by one.
IZ38629 THERE ARE EVENTS IN OBJECT SERVER MATCHING THIS INSTANCE –
In an event storm, some events are not processed by TBSM at times.A simple way to reprocess the events on demand is needed.
IZ38947 TBSM 42 EXPORT SERVICES WITH \R IN DESCRIPTION
If a service instance has the \n or \r character in the description, the instance will not be imported.
IZ39009 CUSTOM CANVAS FREEZES AFTER 4 HOURS.
Service Viewer screen goes white intermittently. The only way to fix it is to restart Internet Explorer
IZ39100 CSS FUNCTION TO ALLOW FORMATTING OF NUMERIC RULE OUTPUTS IN
THE KPI values should be formatted as integers in the viewer Now: 42690.0 After: 42,690
IZ39734 IE HANGS LOADING LARGE NUMBERS OF INSTANCES INTO SERVICE TREE
When a parent that is populated by an ESDA is expanded in the service tree, some children are added multiple times to the parent.
IZ39888 RESTARTING TBSM SERVERS RESETS SLA POLICY SETTINGS
Internal rules that report the status of current downtimes of slas may be incorrect when TBSM starts up.
IZ40144 DATAFETCHER LOG DISPLAY SHOWS THE WRONG LOG
In some circumstances, when displaying Datafetchers in the Service Navigation, if you select Show Log against one datafetcher, the log display shows the log for another one.
IZ42292 TOOLKIT RESOURCE INVALIDATION PROCESS SLOW
Discovery takes several hours.
See READ ME for Webtop APARS.
* TIP APAR included in this Interim Fix:
PK75175 OC COMPARE APPLY DSNU049I INVALID OPERAND
Cannot load ITM chart in TIP if a few of the managed systems are offline.
* TBSM Defects that are included in this Interim Fix:
169255 Tree text width not re-calculated on portlet resize
170564 Word Error in data fetcher show log
170917 Corrution displayed in the canvas name
171601 Child templates initially appear both under parent and root
171682 Incorrect message when viewing data fetcher
171901 Error in VMMUserImpl after failover
172194 svc editor thin/full client switch –> new window/tab
172729 errant text on numeric incoming status rule page
173135 Poor Service Tree response times with large scorecard
173148 Selected menu change after maximizing the portlet
173205 data fetcher view log won’t go away
173226 Chart error when Data Server is down
173341 Custom canvases for groups not shown
173430 policy.manager.errmsg.polchkoutfailed error
173500 ESDA services with over 25 (or so) identifiers fail
173501 SCR for AbstractResource and global policy
173504 Child ESDA created objects not being cleaned up correctly.
173517 omni_stop.sh fails on Solaris
173527 Cannot delete template that has instance with mainten
173533 Hardcoded error message in ServiceInstanceBean.java
173537 Launch from TEP to TBSM not reusing browser.
173538 rad_reinitcanvas utility fails on UNIX
173539 canvas does not reflect modified service display name/desc
173541 missing xmltoolkit file prevents HPUX to come up after boot
173554 Chart definition color palette window is confusing
173556 content replaced when chart def is maximized
173558 Problems using special chars in chart defn
173566 Edit View definition screen not accepting apply, ok, cancel
173575 Cumul SLA bar does not reset to green after time win
173586 “new” icons should be disabled for users w/o create roles
173588 Able to edit template from service tree action w/o role
173657 URL to TEP needs update.Should have 3 slashes before cnp not 2
173806 Windows: policy files not replicated to backup
173843 InstanceGarbageCollector needs to delete invalid instances
173894 request processor Auto Tick
173985 Launch into TBSM using MSSName/sourcetoken/CDMClass params
* TBSM Additional Functions:
1) Enhancement to Viewer Layouts
The following attributes were added to the view definition to enable additional flexibility to the standard “Concentric” and “Grid” views. They are placed in the
2) Custom Widgets
We are adding 4 new widgets that can be dropped into a Custom Canvas from the Indicators tab. The widgets are circular gauges and its use is similar to the existing gauge in TBSM. All 4 widgets allow the following configuration options when you drop it on a canvas:
– Minimum value
– Maximum value
– Gauge value (this is the value that is used to define the needle position on the gauge)
In addition, two of the gauges have an additional configurable field:
– Gauge odometer – This is the value that is displayed on the odometer and typically would be the same as the gauge value. However, since the new gauges have a red/yellow/green background, the user may want to translate the needle position to reflect a red/green/yellow status rather than reflect the gauge value. Having an additional configuration for the odometer de-couples the odometer reading from the needle position.
3) ITM Policy based Data Fetchers
To provide TBSM 4.2 customers a way of using ITM data collected by its agents, policy based data fetchers can be used. Today most TBSM 4.2 data fetchers are limited to using SQL type data stores such as DB2, Oracle, etc. Although ITM data is stored in a database this database is a proprietary store and is not easy to get data from. To provide access to ITM data the ITM policy based data fetcher will use the ITM Web Service which is an installable component of TBSM 4.2 today. This service provides a Web Service wrapper around the ITM CORBA interface. Accessing the ITM Web Service through a JAVA helper class will allow an Impact policy to gain
access to the ITM data. This policy can then be used within a policy based data fetcher and allow the data to be using within incoming status rules. This will allow any ITM agent data to then be used within TBSM similar to how SQL based data is used.
4) Fire Fox 3.0 Support
With this TBSM Interim Fix, Fire Fox 3.0 browser is supported.