Fix Pack 2 addresses the problems that have been reported in IBM® Tivoli® Business Service Manager version 4.2.1. The following table contains a list of files included in this Fix Pack and operating systems associated with these files:
| Platform | File |
|---|---|
| AIX® | 4.2.1-TIV-BSM-FP0002-aix.tar
r9v421a8-100622.aix.tar - Agent installer |
| Linux® | 4.2.1-TIV-BSM-FP0002-linux.tar
r9v421a8-100622.ilinux.tar - Agent installer |
| Solaris | 4.2.1-TIV-BSM-FP0002-solaris.tar
r9v421a8-100622.sun.tar - Agent installer |
| Windows® | 4.2.1.-TIV-BSM-FP0002-windows.zip
R9V421A8-100622.win.zip - Agent installer |
| Linux for System z® | 4.2.1-TIV-BSM-FP0002-zlinux.tar
r9v421a8-100622.zlinux.tar - Agent installer |
| all platforms | 4.2.1-TIV-BSM-FP0002.README |
| all platforms | 4.2.1-TIV-BSM-FP0002.README.htm |
| all platforms | 4.2.1-TIV-BSM-FP0002.README.pdf |
| all platforms | 4.2.1-TIV-BSM-FP0002-DLT.README for the Discovery Library Toolkit |
The following files have been updated or replaced by this Fix Pack. If the file was replaced and you have made changes to that file you will find your copy of the file under [BackupLocation]/tbsmFP2_bkup:
Updated files:
Replaced files:
For information about hardware and software compatibility, see the Tivoli Business Service Manager Installation Guide on the TBSM Information Center:
To apply this Fix Pack you will need 5 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.
IBM Tivoli Business Service Manager Version 4.2.1
Consider this information before you install the Fix Pack:
4.2.1.0-TIV-BSM-IF0001 and 4.2.1-TIV-BSM-FP0001 are superceded by this Fix Pack.
tar -xvf 4.2.1-TIV-BSM-FP0002.<ARCH>.tar
When you extract the file, these directories are created:
Before you install the Fix Pack, you need to plan how and when you will upgrade each TBSM server in your environment. The Fix Pack installation backs up data and components for each TBSM server, which increases the amount of time required to install the fix pack. You need to take this into account when you plan the upgrade of the TBSM servers in your environment.
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:
Follow this sequence:
Before you start the maintenance window:
After you complete the upgrade the two secondary servers, start the maintenance window down time for the production servers.
After you complete the upgrade for all the servers:
If you are installing the Fix Pack in an environment with a failover pair of TBSM data servers, you must install using the failover steps described in the upgrade chapter of the TBSM Installation Guide.
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/ com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgradie_4.2.html
To improve the speed of the AIX version of the Fix Pack installation program, configure the installation program to use the native AIX file handler as follows:
<TBSM_USER_HOME>/.acsi_<TBSM_USER>/lib/
ln -s libNativeFile.so libNativeFile.a
Before you install the Fix Pack on a Solaris system, run the commands in this section to enhance system performance. You need to have super user privileges on the Solaris host to run these commands successfully. In this example, the root user is runs the commands:
projmod -s -K 'project.max-shm-memory=(privileged,4gb,deny)' user.root projmod -s -K 'project.max-shm-ids=(privileged,1024,deny)' user.root projmod -s -K 'project.max-sem-ids=(privileged,1024,deny)' user.root projmod -s -K 'project.max-sem-nsems=(privileged,512,deny)' user.root projmod -s -K 'project.max-sem-ops=(privileged,512,deny)' user.root projmod -s -K 'project.max-file-descriptor=(privileged,1024,deny)' user.root ndd -set /dev/tcp tcp_conn_req_max_q 8192 ndd -set /dev/tcp tcp_conn_req_max_q0 8192 ndd -set /dev/tcp tcp_max_buf 4194304 ndd -set /dev/tcp tcp_cwnd_max 2097152 ndd -set /dev/tcp tcp_recv_hiwat 400000 ndd -set /dev/tcp tcp_xmit_hiwat 400000
Before you run the Fix Pack installer, archive as many TBSM trace logs as possible. At the end of the install process, all the logs will be zipped up and made available for review. The more logs that need to be collected, the longer this step will take and the more space needed.
Before you install the Fix Pack, make sure that the you have the same tipadmin user’s password for all your TBSM servers. The password validation only verifies against the Dashboard server (tipprofile) and the the install will fail if the data server’s tipadmin user has a different password.
The following WAS wsadmin command can be used to change tipadmin's password on the Data server:
$TIP_HOME/profiles/TBSMProfile/bin
wsadmin -conntype NONE 3. Enter $AdminTask changeFileRegistryAccountPassword
{-userId <administrative userid> -p <new password> }$AdminConfig save
If the installer shows an error before you see the install summary panel, this is a pre-install processing error. For example, you may see an insufficient space error. You do not need to restore the installation for this type of error. Correct the problem, for example, allocate more space or change a directory location, and rerun the installer.
Before running the install, rename or move any the Deployment Engine backup files for Fix Pack 2:
tbsmfp2_bkup
The Fix Pack 2, the installer blocks the user from re-using the same backup location twice to prevent over-writing old backups.
To fix this you need to rename or move the backup files for the Deployment Engine and TBSM, since the installer ran to completion. To do this:
tbsmfp2_bkup
The InstallAnywhere installer uses the directory value specified for the IATEMPDIR variable for its temporary file space. The default value is the default temp directory for your operating system, This file space must be at least 500 MB. The IATEMPDIR does not affect the temporary directory used by Websphere Application Server
You need at least 260 MB of space available in the temp directory to update the Websphere Application Server included with TBSM. The Websphere Application Server installer uses the default temp directory for your operating system.
Before you run the Fix Pack installer make sure that your X-Server is running.
[Fix Pack] Refers to the directory where you extracted the Fix Pack files from the zip/tar file.
TBSM needs to be running when you install the Fix Pack.
Running the install without backup:
If you prefer to backup your system with your own procedures you can run the install with the following parameter.
-DNO_BACKUP=true
If you choose this method you must backup the entire system (hard drive) before you install. You will loose the capability to restore using method described in this readme. Restore the original system using your backup/restore procedures or utilities.
Follow this procedure to install the Fix Pack:
Installation command options:
UNIX® :install.sh -f /tmp/setupFP.rsp
orWindows: setup-windows.exe -f C:\tmp\setupFP.rsp
Messages similar to the follow may appear during the Deployment Engine upgrade step:
exception: java.lang.SecurityException: java.util.HashMap - protected system package 'java.util' exception: java.lang.SecurityException: java.lang.NullPointerException - protected system package 'java.lang' exception: java.lang.SecurityException: java.net.MalformedURLException - protected system package 'java.net'
There may be many messages of this type and you can ignore them. The install will finish successfully.
After the installation, note the following:
Unix:
$HOME
Windows:
C:\Documents and Settings\Administrator
If you customized some TBSM policies and views you may need to restore your changes to these files from the backup. There is also information to consider if you want to use the Tivoli Integrated Portal command line interface on UNIX systems.
See:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ installguide/bsmi_upgradie_4.2_postupgrade.html
If you need to add a feature to an existing 4.2.1 product after the 4.2.1 Fix Pack has been installed, the GUI mode for the TBSM 4.2.1 product's installer may not allow you add features.
Solution: use the console mode to run the 4.2.1 base product installer.
Launch the installer from the <dvd_image>/TBSMdirectory. Syntax is:
setup-windows.exe -i console
setup-<ARCH>.bin -i console
Before you uninstall the Fix Pack, the TBSM servers need to be running.
An uninstall of the Fix Pack will revert only the code that was installed by the Fix Pack. It should be used if the Fix Pack needs to be removed for any reason, but you have made other changes to your system that you do not want to be affected by a restore operation. The uninstall of the Fix Pack can take a considerable amount of time depending on the type of hardware and operating system that TBSM is installed on.
A restore of the Fix Pack is a total replacement of the DE and Tivoli directories. It must be used if the Fix Pack install fails for any reason, It can also be used in place of an uninstall if you have not made any other changes to those directories that you do not want restored (that is, the installation of another product or TBSM customization). A restore is a faster operation than an uninstall.
The uninstaller runs using the same method that was used for the install.
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:
$TBSM_INSTALL_HOME/_uninst/TBSM_FP2
and update the file with the correct information. Then launch the installer specifying the file. For example:
uninstall -f setup_uninstall.rsp
On the Tivoli Business Service Manager server system:
$TBSM_INSTALL_HOME/_uninst/TBSM_FP2
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
Linux/AIX: <TIP_HOME>/bin/clearClassCache.sh
Solaris: java -Xshare:dump
Windows: <TIP_HOME>\bin\clearClassCache.bat
After you uninstall the Fix Pack on a UNIX system the Service Tree may be blank. To fix this, copy all the directories and files from:
<installDir>/tip/systemApps/isclite.ear/isclite.war/secure/isclite/scripts/ ibm/tivoli/tbsm_BACKUP
to the directory:
<installDir>tip/systemApps/isclite.ear/isclite.war/secure/isclite/scripts/ ibm/tivoli/tbsm
To restore a TBSM system from a backup that was created during the Fix Pack installation, see the TBSM Installation Guide at:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ installguide/bsmi_upgrade_t_restore42.html
To recover a failed Deployment Engine upgrade in TBSM 4.2.1., see the TBSM Installation Guide at:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ installguide/bsmi_upgrade_t_de_restore42.html
Installing the TBSM agent:
The following packages are available for download in the TBSMAgent directory on the support download site.
To install the updated TBSM agent:
For instructions on installing and configuring the TBSM agent, see:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ installguide/bsmi_t_installing_tbsm_agent.html
Please refer to the Discovery Library readme: [Fix Pack]/DiscoveryLibrary/4.2.1-TIV-BSM-FP0002-DLT.README
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.
There is a new parameter in the file canvasviewer_simple.html called DispParam_AutoFitOnEdit. The default value is "true" which means that the canvas viewer with perform a "fit to view" function whenever the user edits the canvas and performs actions such as add a new indicator to the canvas, select a different indicator, or move an indicator. The effect is the user's current zoom level will be lost. When this value is set to "false", no "fit to view" function is performed while editing a canvas, thus preserving the current zoom level.
To turn off the "fit to view" function while editing a canvas, edit the file $TBSM_DASHBOARD_SERVER_HOME/av/canvasviewer_simple.html found on the TBSM Dashboard Server.
Change the two settings in the following lines from true to false:
<PARAM NAME = "DispParam_AutoFitOnEdit" VALUE ="true">
DispParam_AutoFitOnEdit = "true"
to:
<PARAM NAME = "DispParam_AutoFitOnEdit" VALUE ="false"> DispParam_AutoFitOnEdit = "false"
Then, on the machine where you run your BROWSER, clear any files that may have been cached by the browser. This will allow the browser to pick up changes to the HTML file.
For example, in Firefox, select Tools --> Clear Private Data, and select Cache. In Internet Explorer, select Tools --> Delete Browsing History, and click Delete for Temporary Internet Files Please note that any customization you made to the file canvasviewer_simple.html will not be preserved during an upgrade or cloning scenario. If you upgrade or clone your TBSM Dashboard Server, then you will have to replicate your customization afterwards.
TBSM provides a custom implementation that overcomes the IlvSDMNodeComparator limitations. It was written to properly handle numeric order property values.
It supports:
The following ordering is provided "out of the box":
this provides additional value by automatically ordering views that contain services that have not been customized with order property values
It is possible to adjust the node ordering by specifying different sort criteria. This requires a detailed understanding of TBSM's service model fields and their contents.
This definition results in the following ordering of nodes:
Subobject#nodeComparator {
class: "com.micromuse.common.canvascomponent.layout.NodeComparator";
sort1Property: "_overallServiceStatus";
sort1Ascending: "false";
You can now use the following new parameters in the "Additional" tab of the service template editor:
You can use either of these parameters:
OR use the following parameter: EventListFilter
To enable these features, you need to set the following property in the RAD_sla.props file on dashboard server:
impact.sla.usedepstable=false
The RAD_sla.props for the dashboard server is located in
$TIP_HOME/systemApps/isclite.ear/sla.war/etc/rad/RAD_sla.props
You need to restart the dashboard server to enable this change.
Customers that are experiencing this problem already have a corrupted layoutxml file containing hardcoded values. Even after this fix is applied, they need to delete their old custom canvas and create it again in order to restore the rule values in the canvas properties.
A property was added to RAD_sla.props to handle this situation.
The RAD_sla.props for the data server is located in the directory:
$TIP_HOME/profiles/ TBSMProfile/installedApps/TBSMCell/tbsm.ear/sla.war/etc/rad
To enable this new functionality, set the following property to true:
# Leaf node autopop services, without parents, can temporarily # appear in the root of the Service tree before being assigned # to DefaultAutopopParent. To hide these services, set to true. impact.sla.dontaddbottomautopoptoroot=true
The RAD_sla.props for the dashboard server is located in:
$TIP_HOME/systemApps/isclite.ear/sla.war/etc/rad/RAD_sla.props
To enable this new functionality, add the following property and set it the autopopulation delay.
# Non-Leaf node autopop services, can temporarily appear in the # root of the Service tree before being assigned a parent. # To delay the display of these services until their parents # and relationships have been generated set the value below to # be greater than the time expected to create parents and # relationships for new ESDA and autopop services. Default is 5. impact.sla.displayautopopdelayseconds=5
If the length of time to create autopopulation and ESDA parents and relationships is longer than 5 seconds, then the above value can be increased, as required.
To enable ObjectServer fail back after you install the Fix Pack, you need to update the RAD_server.props.
By default this fail back function is not enabled. To enable it, you need to edit the RAD_server.props file in the $TBSM_DATA_SERVER_HOME/etc/rad/ directory on both the primary and failover data servers. Add the following line:
objectserver.failback=true
(to disable, set to false)
Logging can be set with the following:
server.jdbc.debug=false|true
Changes have been made to the styling CSS used to render TBSM views (applies to both the full and thin clients). These changes have been made to:
From now on:
%TBSM_DASHBOARD_SERVER_HOME%\av\css
|
+-- custom_view.css (a)
+-- rad.css (b)
+-- rad_gis.css (c)
|
+-- rad_nodes_links.css (d)
|
+-- tbsm_custom.css (a)
+-- tbsm_gis.css (c)
+-- tbsm_view.css (b)
|
+-- customer
|
+-- custom_overrides.css (a)
+-- gis_overrides.css (b)
+-- rad_overrides.css (c)
|
+-- nodes_links_overrides.css (d) (e)
If you have previously customized any of the CSS files, you must manually migrate the change to the appropriate "customer" CSS file. The previous CSS files have been saved at: {BackupLocation}/tbsmFP2_bkup
The updated file is located at [Fix Pack]/tivolieif/rules/zos_identity.rules. Replace the existing file with the Fix Pack file in your eif_probe directory.
To address this, a new user role has been added.
After the fix pack has been applied, you need to edit each Maintenance Schedule and, without making any changes, click OK to correctly update TBSM for each schedule. This only needs to be done once for each maintenance schedule. It does not have to be done for each service with a maintenance schedule.
The following property can be added to $TBSM_DATA_SERVER_HOME/etc/rad/RAD_server.props:
# What is the default port to use for Object Server connections. # This is only used if the port gets reset to 0 impact.server.defaultObjectServerJDBCPort=4100
If a connection on port 0 is attempted, for an Object Server connection, then the port is read from this property. The default value is 4100.
By default the TBSM Agent only collects root cause events when the state of a service deteriorates. To enable collection of root cause events when the state of a service improves, uncomment the property impact.agentservice.sendeventsonstatusimprovement=true .
The property is in the file:
$TBSM_DATA_SERVER_HOME/etc/rad/RAD_agentservice.props
You need verify that the property impact.agentservice.sendeventsonstatusimprovement=true is set to true and remove the comment marks.
This property was added to the file with Fix Pack 2.
The custom canvas shape color does not give a color as a result, it only gives the results of the rule it assigned to it.
If there are existing black shape indicator icons, the user must do the following:
The indicator should no longer be black
If a user configures the primary template of a parent service as "None", then all rules from all templates assigned to the parent service are run whenever child services are added or removed. This is the default behavior.
If you want TBSM to only run rules from the primary template:
$TBSM_DATA_SERVER_HOME/etc/rad/RAD_sla.props.
impact.sla.onlyrecomputeprimary=true
If this property is not added, there should be no affect to any other functionality.
If this property is added, some rules that are not in the primary template of the parent service may not get updated with the correct value when child services are added or removed.
The following APARs are delivered with Fix Pack 1:
Whenever a policy is run against a given service instance, you can access this data from the Service Instance object.
| Variable name | Service attribute description |
|---|---|
| RADSTATUS
good (0), marginal (3), or bad (5). Local Fix: none |
The overall status of the service |
This canvas is either no longer locked or it cannot be determined who owns the lock. Do you want to ignore the lock, save the canvas and potentially lose changes?
The hostname, port and sometimes also the user name and password for the Oracle Data Source are cleared. The values are cleared from the etc/rad/RAD_<Data Source Name>.ds file.
The values will also be cleared from the GUI.
On viewing data for associated data fetchers, the error message shown will have the following for the JDBC connection data:
jdbc:oracle:thin:@null:null:null
The log file will have a similiar error message to the following:
JDBC Connection Pool will try to connect to null at
jdbc:oracle:thin:@null:null:null
CTGBC0054E when link selected in canvas CTGBC0054E An unexpected error occurred while retrieving information about the service instance with the ID or instance name NULL. : For input string: "NULL"
Further problem description reported by customer:
We created a business model in TBSM, and created a service view page, but every time we click the lines it will show error prompt above.
[2/17/10 17:59:54:877 EST] 0000007f clientmodel
1 com.micromuse.sla.clientmodel.ClientConfigUpdateListenerStore
fireInstanceInvalidated ENTER^^T^null
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification
(AbstractList.java:464)
at java.util.AbstractList$Itr.next(AbstractList.java:435)
at com.micromuse.sla.clientmodel.ClientConfigUpdateListenerStore.
fireInstanceInvalidated(ClientConfigUpdateListenerStore.java:235)
at com.micromuse.sla.updatesubscriber.InstanceInvalidationUpdate.
doit(InstanceInvalidationUpdate.java:83)
at com.micromuse.sla.updatesubscriber.RADClientUpdateHandler
$ConfigChangeProcessingThread.run(RADClientUpdateHandler.java:579)
[5/10/10 14:28:48:019 EDT] 0000004f beans 1 com.micromuse.sla.beans.GlobalInstanceStore addServiceIn stance EXIT ^tag1^T^CTGBC0062E The name a1pvap009|PROD2|SCR1 contains characters that are invalid for a serv ice instance. The following characters are considered invalid: <>*?|;"\
[2/17/10 17:59:54:877 EST] 0000007f clientmodel 1 com.micromuse.sla.clientmodel.ClientConfigUpdateListenerStore fireInstancePrimaryTemplateChanged ENTER^^T^null java.util.ConcurrentModificationException
The following APARs are delivered with Fix Pack 1:
-- OR -- Unable to use the following parameter in "Additional" tab of a template (which was possible in 4.1):
EventListFilter
These parameters allow the customer to display custom SQL result sets inside the LEL portlet upon clicking on a service.
See Additional Information for information on how to enable these filters.
Yet it is possible for this user with no edit or admin roles to add/modify/delete view definitions.
This occurs when the duplicate Service is at different levels in the branches AND the difference in level is greater than 1.
This Fix pack includes Tivoli Integrated Portal 1.1.1.11.
The following other components are updated with this version:
Driver tip_1.1.1.11_201006281504
The following APARs are new in TIP Tivoli Integrated Portal 1.1.1.11
The following APARs are new in TIP Tivoli Integrated Portal 1.1.1.09.
The following APARs are included in the TIP Tivoli Integrated Portal 1.1.1.09.
APAR included from TIP 1.1.1.7
APARs included from TIP 1.1.1.5
APARs included from TIP 1.1.1.3
This section describes the new support and features for this Fix Pack 2.
The Service Visibility option in the Service Tree preferences View tab. allows you to:
For more information on this feature, see:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ ServiceConfigurationGuide/bsmu_vwmc_tree_prefs.html
The Urgent Services preference window allows you to filter the services in the Urgent Services portlet. You can set your preferences to filter services by severity or template.
For more information on this feature, see:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ ServiceConfigurationGuide/bsmu_vwmc_urgent_service_prefs.html
New gauges, indicators, buttons have been added to the Custom Static Canvas palette.
For more information on this feature, see:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itbsm.doc/ ServiceConfigurationGuide/bsmu_canc_about.html
This section describes the new support and features for this Fix Pack 1.
After installing the Fix Pack 1 or later, you can clone TBSM data and dashboard servers. Cloning of the TBSM servers is useful in the following situations:
The ability to clone a system in general requires the ability to export the source system into an exchange format that can be imported into the target system. The goal is to reproduce the system state of the source system without actually copying the entire operating system to the target, then having to find all the configuration data to adjust for the new host.
TBSM will support cloning of the data and dashboard servers across operating systems. This procedure is for the primary TBSM data server, however, combining this procedure with the failover procedure will effectively allow you to clone the pair. This support does not include cloning of a load-balancing environment. The complete documentation and instructions are included in the TBSM Installation Guide at:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/ com.ibm.tivoli.itbsm.doc/welcome.htm
Service instance names will now be validated upon creation using the following rules:
" < > \ * ? | ;
In previous versions of TBSM, the system did not check for invalid characters in services names. Invalid characters prevent the service from saving properly.
If you are creating a service instance using the Console GUI, you will receive an error message if the service instance name does not follow the validation rules. If you are creating a service instance by another means, such as ESDA, autopopulation, radshell, or TADDM, error messages will appear in the trace.log file in the TBSM Data Server. (for example, $TIP_HOME\profiles\TBSMProfile\logs\server1\trace.log).
If you created a service instance name containing one of the invalid characters prior to Fix Pack 2 and encounter any problems using that service instance, please rename the service instance according to the validation rules.
TBSM 4.2.1 FP2 is now supported in Windows 2008 R2 operating system.
The following steps must be completed in order to successfully install TBSM 4.2.1 and TBSM 4.2.1 FP2 in Windows 2008 R2:
For example: Copy (from TBSM 4.2.1 FP2 install image): TBSM\DE\.data\setup.jar (to TBSM install image) TBSM\DE\.data\setup.jar.
After you install this Fix Pack, TBSM can support an upgrade from Netcool/OMNIBus version 7 release 2.1 to version 7 release 3.
After you upgrade Netcool/OMNIBus, run the rad_discover_schema command to ensure that the TBSM Data server is using the most recent changes to the ObjectServer schema. Run these commands on the primary and backup TBSM data servers:
$TBSM_HOME/bin/rad_discover_schema ObjectServer
$TBSM_HOME/bin/rad_discover_schema OutputObjectServer
If you install TBSM 4.2.1 and Fix Pack 2 in an environment with an existing Netcool/OMNIBus 7.3 and the Netcool/OMNIBus Web GUI, then you need to apply the fix:
Tivoli Netcool OMNIbus_GUI 7.3.0 Interim Fix 2, 7.3.0-TIV-NCOMNIbus_GUI-IF0002
If you install TBSM 4.2.1 and Fix Pack 2 in an environment with an existing Netcool/OMNIBus 7.3 and the Netcool/OMNIBus Web GUI 7.3.0 and Fix Pack 1 then you need to apply the fix:
Tivoli Netcool OMNIbus_GUI 7.3.0 Interim Fix 3, 7.3.0.1-TIV-NCOMNIbus_GUI-IF0003
You can download Netcool/OMNIBus Web GUI interim fixes from
http://www-947.ibm.com/support/entry/portal/All_download_links/Software/Tivoli/Tivoli_Netcool~OMNIbus
If you install TBSM 4.2.1 and Fix Pack 2 in an environment with an existing Netcool/OMNIBus 7.3 and the Netcool/OMNIBus Web GUI, then the views required by TBSM are not created.
To create the views, execute the following command on the Dashboard server:
On Unix:
cd <TIP_HOME>/products/ncw/waapi/bin
./runwaapi -file <TIP_HOME>/systemApps/isclite.ear/sla.war/install/ webtopcore/create_tbsm_views.xml -user <userid> -password <password>
On Windows:
cd <TIP_HOME>\products\ncw\waapi/bin
runwaapi -file <TIP_HOME>\systemApps\isclite.ear\sla.war\install\ webtopcore\create_tbsm_views.xml -user <userid> -password <password>
For additional information on this command, see the Netcool/OMNIBus 7.3 documentation.
If you upgrade a Netcool/OMNIBus failover environment to 7.3, you need to manually copy the NCO_GATE directory from the backup netcool directory (e.g netcool.1) to the current netcool/omnibus/gates directory.
Otherwise the gateway does not start and the log will show the following error
2010-01-22T15:47:47: Error: E-GTK-102-131: [ngtk]: Map File Parser: Failed to open map file '/home/tsystems/IBM/tivoli/netcool/omnibus/gates/NCO_GATE/NCO_GATE.map'. (2:No such file or directory) 2010-01-22T15:47:47: Error: E-GTK-102-134: [ngtk]: Failed to startup the map manager. (2:No such file or directory) 2010-01-22T15:47:47: Error: E-GTK-102-017: [ngtk]: Failed to startup the gateway toolkit. (2:No such file or directory) 2010-01-22T15:47:47: Error: E-IPC-005-001: OpenServer - Error: 16334/10/0: SRV_START event aborted srv_run 2010-01-22T15:47:47: Error: E-STK-102-014: [nstk]: NCO_GATE: Failed to start server processing loop. (-19:General failure)
If you use the Business Intelligence and Reporting Tools Designer (BIRT) charting utility to create or customize a chart, the chart does not open after the Fix Pack is installed. This can occur if you create a chart from the data provided through the TBSM data source (such as a web service running on the TBSM Data server) in BIRT.
The chart will not open if the data source is not specified in the chart design.
For Fix Pack 1 and later, the charting web services are password protected and the Tivoli Integrated Portal charting portlet on the TBSM Dashboard server does not support basic authentication for TBSM charting web services.
The resolution for the user is to take one of the following two actions:
<data-sources>
<oda-data-source extensionID="com.ibm.tivoli.tip.oda.ws.dataSource"
name="Data Source" id="6">
<text-property name="displayName"></text-property>
<property name="HOSTNAME">myhost</property>
<property name="USERNAME">tipadmin</property>
<encrypted-property name="PASSWORD" encryptionID="base64">
dGJzbTQyc3Z0</encrypted-property>
<property name="PORT">17310</property>
<property name="PROTOCOL">http</property>
<property name="SERVICE_NAME">sla/rad</property>
</oda-data-source>
</data-sources>
Within the above <oda-data-source> element, change the values of the properties as follows:
Once these changes are made to the file, save it and import it into the charting portlet running on the TBSM dashboard server.
> $TBSM_HOME/custom_chart_ds_updater updateds -Ddir=<working dir> -Dusername=tipadmin -Dpassword<tipadmin's password>
Where:
The utility can also be used to restore the original rptdesign files as follows:
> $TBSM_HOME/custom_chart_ds_updater restore -Ddir=<working dir> -Dusername=tipadmin -Dpassword<tipadmin's password>
On a restore, the rptdesign files residing in <working dir>/tbsmcustomcharts will be imported into the TIP charting portlet running on the TBSM dashboard server. If you wish to restore from a previous backup taken by the utility, first copy the rptdesign files from the appropriate backup directory (<working dir>/tbsmcustomcharts.<timestamp>) into the <working dir>/tbsmcustomcharts directory before running the utility with the restore command.
If a user creates a TBSM Chart in a Tivoli Integrated Portal Load Balancing environment, the chart will not show up in the Custom Charts for the Tivoli Integrated Portal Charting Portlet.
Workarond: To display the chart:
$TBSM_DATA_SERVER_HOME/birtcharts/custom
If you are running the web browser on a machine other than the data server, copy the chart from the above location to the machine running the browser, and then upload the chart. You only need to upload the chart to one of the web-browser machines running the TBSM client.
The radshell function cannot accept characters from the command line which are not available on an English keyboard such as Swedish, French, or Chinese characters. As an example, if you use "Tfföräldrapenning" or "Grâce âá téléphoniques" as the service instance name parameter for addServiceInstance(), the radshell will terminate with no error message.
WORKAROUND: If you are invoking a radshell function such as addServiceInstance() that can also be completed in the TBSM user interface, use the TBSM user interface to complete the task.
Problem: After you uninstall the Fix Pack, the custom charts created in the TBSM Charts interface do not render in the charting portlet. The charting portlet will display a pop-up error with text that reads
TIPMSG1000E An error occurred while processing the request to the server. Detail:AxisFault Transport error: 404 Error: Not Found.
Resolution:
When exporting as part of a cloning operation, the System Cloning Solution export will fail on a UNIX or Linux system with a message like:
/opt/IBM/tivoli/tip/bin/tssExportImport.xml:117: Execute failed: java.io.IOException: /opt/IBM/tivoli/tip/products/tss/bin/scheduler.sh: cannot execute
This results from there being no "execute" permission for the scheduler.sh script.
Execute the command:
chmod +x TIP_HOME/products/tss/bin/scheduler.sh
Where TIP_HOME is the directory where TIP is installed. The default is:
/opt/IBM/tivoli/tip
Rerun the System Cloning Solution export.
The commands you use to create the XML DSA data types fail on a UNIX or Linux system. The executable permissions are not set on these commands.
/home/tbsm421/IBM/tivoli/tip/profiles/TBSMProfile/installedApps/TBSMCell/ tbsm.ear/sla.war/dsa/XmlDsa/bin
chmod +x CreateDtdTypes.sh
chmod +x CreateXsdTypes.sh
If you input an invalid Service name and click save, the service name is not saved, but the Identification fields are generated with the invalid characters. If you then input a valid service name and save the service, the Identification fields are not updated.
As a result, events or other incoming data will not match to the invalid Identification field value.
Workaround:
To fix this, update the Identification fields with the correct values.
When pressing the Preview data button, you may receive a syntax error similar to the one listed below, when the column (in this case PID) is of a numerical value and is listed as one of the entries on the Threshold Filters table:
CTGBA0018E Verify that the query is valid. CTGBA0049E An exception occurred while processing the query SELECT KR9_A."Application_Component", KR9_A."PID" FROM ITMUSER.KR9_AVAILABILITY AS KR9_A WHERE KR9_A."PID" < 2000 and ((PID = '1')). Error with SQL Syntax or Resync..DB2 SQL error: SQLCODE: -401, SQLSTAT:42818, SQLERRMC:=
Workaround:
To address the above syntax error:
http://www.ibm.com/legal/copytrade.shtml
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.
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: