The next mega fix pack for TBSM 4.2.1 is available today with many fixes for core TBSM and TIP bugs impacting core functionality and performance and a few new capabilities to boot. The README is available here. A separate README for the Discovery Library Toolkit is available here. The fixpack is available for download here.
My advice is for you to read the README. Then READ it again. Then REVIEW your systems and TBSM implementation. Note the DISK SPACE requirements. I’d double them to be safe. READ the README again. Review all of your TBSM implementation customizations. READ THE README AGAIN. Do a full end-to-end backup of your TBSM system (on each component) before you start. Think carefully about bypassing the fixpack backup procedure. Consider applying appropriate WebTop 2.2, WebGUI 7.3 or OMNIbus 7.x fixpacks/interim fixes. You do know that TBSM maintenance releases never include core Netcool/OMNIbus maintenance right?
If you’ve already installed TBSM 4.2.1 FP1, your installation time for TBSM 4.2.1 FP2 should be improved compared to your FP1 installation experience. If you haven’t installed TBSM 4.2.1 FP1 and are installing the all inclusive TBSM 4.2.1 FP2, be prepared for a significant installation time. This can and will vary widely by hardware and operating system type/version. Don’t interrupt the installation process!
Before you start, READ THE README AGAIN! Pay attention to the post installation tasks and configurations which may be required. Let me know if you have any problems, I’ll be watching for PMRs closely.
The TBSM 4.2.1 Documents have been updated appropriately here. I’ll try to point out some new features in follow on posts.
by doug on March 25, 2010
If you’re using TBSM v4.2.1 FP1 with OMNIbus 7.3 GUI you should take a look at getting this interim fix (IF) installed. If you are not seeing normal behaviors with the interaction of the service tree, service viewer and the service details portlet, it’s likely this WebGUI (WebTop) IF is required.
The most common symptom is that when you click on something in the tree or topology, the service details portlet isn’t filtering the events to what was selected.
For more information, check out this support note.
alm00128949 / IZ69508
=====================
Short Description: PROBLEMS WITH THE AEL AND LEL ON TBSM 4.2.1 WITH OMNIBUS 7.3
Summary: AEL not shown when it is launched in a new TIP tab from TBSM 4.2.1 Service Tree with incorrect filter and view. The problem is caused by calling setAspect method from JavaScript before AEL is fully initialized.
The problem is fixed by ensuring setAspect can handle cases when it is called after AEL is initialized. If it is called before AEL is fully initialized, AEL should use filter, view and data source as provided by setAspect.
ALM00128818 / IZ69498
=====================
Short Description: THE LEL CANNOT DISPLAY ANY EVENT DATA FROM TRANSIENT FILTERS
Summary: The LEL cannot display any event data from transient filters. It is caused by data misalignment. The LEL is applying a default hard-coded view to event data that has been retrieved from the ObjectServer with the correct view. The correct view is being applied to the SQL query, but the returned fields are not aligned with the view that the LEL has applied in the client.
This issue is resolved by performing failback checking for system and then user transient filter.
