Download
Abstract
This Fix Pack addresses problems reported in IBM Tivoli Business Service Manager 6.1
Download Description
IBM Tivoli Business Service Manager 6.1.0
Fix Pack Version 6.1.0-TIV-BSM-FP0002
======================================================================
Readme file for: IBM Tivoli Business Service Manager
Product/Component Release: 6.1.0
Update name: Fix Pack 2
Fix ID: 6.1.0-TIV-BSM-FP0002
Publication Date: October 15, 2014
Last modified date: October 8, 2014
Online version of the readme file:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm+Tivoli&product=ibm/Tivoli/Tivoli+Business+Service+Manager&release=6.1.0
Publish date is subject to change at any time without notices
======================================================================
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
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.7.3 DBConfig
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
4.0 Additional information for TBSM Fix Pack 1 APARS
4.1 IV01649 - AFTER ZOOM IN ON CANVAS, SINGLE CLICK CAUSES ZOOM OUT
4.2 IV03630 - SETTRACELEVEL DOES NOT PERSIST NUMBER OF LOG FILES
4.3 IV07914 - TBSM CONSISTENCY CHECKER CONSUMES MUCH OF OS CONNECTION TIME
4.4 IV19006 - THERE IS AN ISSUE WITH THE TBSM 6.1 30 DAY REPORT LAUNCH.URL
TO TCR IS INCORRECT
5.0 List of APARs
5.1 TBSM 6.1.0 Fix Pack 2 APARS
5.2 TBSM 6.1.0 Fix Pack 1 APARS
5.3 Tivoli Integrated Portal
6.0 New support and features
6.1 TBSM 6.1 Fixpack 2
6.2 Additional Browser Support with FP 2
6.3 eWAS Fixes and Upgrades
7.0 Firefox 10 issues
7.1 TBSM 6.1 GA launchpad does not work on Firefox 10
8.0 Known issues
8.1 Some date options in TBSM Reports do not work
8.2 Issues creating wire between Service Tree and Active
Event List (AEL)
8.3 TBSM Agent Chart title differs from name in the
drop down list
8.4 Minimize-restore does not restore to correct size for
Service Navigation->Data Fetchers on Internet Explorer(IE) 9
8.5 Portlets covering content in a free form page
8.6 Java Security exception while editing Custom Canvas
8.7 Unexpected wide character messages are displayed in console mode during installation or upgrade
8.8 Java Runtime Environment (JRE) 1.6.0_nn and Internet Explorer 10 (and above) and Firefox 17 (and above).
9.0 Copyright and trademark information
1.0 Files included in this Fix Pack
Fix Pack 2 addresses the problems that have been reported in IBM®
Tivoli® Business Service Manager version 6.1.0. 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.0-TIV-BSM-FP0002-aix.tar |
| | |
| | Agent installer |
| | KR9_aix523CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit) |
| | KR9_aix526CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit) |
+---------+--------------------------------------------------------------+
| Linux® | 6.1.0-TIV-BSM-FP0002-linux.tar |
| | |
| | Agent installer |
| | |
| | KR9_li6263CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit) |
| | KR9_lx8266CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit) |
+---------+--------------------------------------------------------------+
| Solaris | 6.1.0-TIV-BSM-FP0002-solaris.tar |
| | |
| | Agent installer |
| | KR9_sol283CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit) |
| | KR9_sol286CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit) |
+---------+--------------------------------------------------------------+
| Windows®| 6.1.0.-TIV-BSM-FP0002-windows.zip |
| | |
| | Agent installer |
| | KR9_winntCD-6.1.0-TIV-BSM-FP0002.zip -(32 bit) |
| | KR9_wix64CD-6.1.0-TIV-BSM-FP0002.zip -(64 bit) |
+---------+--------------------------------------------------------------+
| zLinux | 6.1.0-TIV-BSM-FP0002-zlinux.tar |
| | |
| | Agent installer |
| | KR9_ls3243CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit) |
| | KR9_ls3246CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit) |
| | KR9_ls3266CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit) |
+------------------------------------------------------------------------+
|all platforms| 6.1.0-TIV-BSM-FP0002.README |
+-------------+----------------------------------------------------------+
|all platforms| 6.1.0-TIV-BSM-FP0002.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
ApplyPoliciesFor61FP2
BSM_TemplateUpdates61FP0002.radsh
setJVMSettings.jy
setJVMSettings.bat
setJVMSettings.sh
smack-2.2.1.jar
smackx-2.2.1.jar
org.apache.axis2-woden.jar
ipa-1.0-20120430.jar
tbsm-info.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
itmdataclient.jar
maintcli.jar
ncs.jar
ncsagent.jar
ncsSoapClient.jar
RAD_namevalidator.props
TBSM_BusCompPlaceAllCIsByAttr.js
TBSM_markerChangeProvider.ipl
TBSM_ResEnrichMain.js
TBSM_SLAUpdateServiceEvent.ipl
TBSM_AV_GetColorForSeverity.ipl
versioninfo.bat
versioninfo
verutil.jar
Files under tbsm/contrib/gistools
Replaced Impact files on the Data Server:
nciJmxClient.jar
nci.jar
*_EIC_utils.ipl
*_Import.ipl
*_MWM.ipl
*_MigrateMWMWindows.ipl
*_Opview_Add1TWin.ipl
*_Opview_EIC_confSubmit.ipl
*_Opview_EIC_requestHandler.ipl
*_Opview_onetwins.ipl
*_Opview_openwins.ipl
*_Opview_rdomwins.ipl
*_Opview_rdowwins.ipl
*_Opview_rwdomwins.ipl
*_SerialRollover.ipl
*_XINY_DataType_PurgeData.ipl
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.0.0/FP0002/data
---
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
tbsm-info.jar
Replaced files on the Dashboard Server:
canvasviewer_simple.html
tbsm-jviews.jar
tbsm-jviews-thin.jar
tbsm-symbol-palette.jar
Gauges.xml
Gauges_Content.xml
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
SLAReportToolbar.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
av.jar
ipa-1.0-20120430.jar
itmdataclient.jar
nci.jar
nciClient.jar
ncCommon.jar
tbsm-info.jar
web.xml
faces-config.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 twa.war/dojo
Replaced Impact files on the Dashboard Server:
nciClient.jar
nciJmxClient.jar
*-EIC_configure.html
*-new1twin.html
*-newrwin.html
*-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.0.0/FP0002/dash
---
Added files associated with the Discovery Library Toolkit:
scc_servicetreebuilder_reinit.sql
scc_servicetreebuilder_guts.sql
scc_servicetreebuilder_delta.sql
scc_servicetreebuilder_composites.sql
taddmconfig.bat
taddmrmiconfig.bat
taddmconfig.sh
taddmrmiconfig.sh
taddmmaint.bat
taddmmaint..sh
unloadBusinessComposerDefinitions.bat
unloadBusinessComposerDefinitions.sh
Replaced files associated with the Discovery Library Toolkit:
scc_refreshnamingcommitchanges.sql
scc_staging_schema_truncate.sql
scc_staging_schema_setup.sql
scc_staging_schema_index_setup.sql
scc_staging_schema_index_deletes.sql
scc_staging_schema_deletes.sql
scc_staging_schema_analyze.sql
scc_staging_schema_view_deletes.sql
scc_staging_schema_views.sql
scc_schema_truncates.sql
scc_schema_setup.sql
scc_schema_drop_indexes.sql
scc_schema_deletes.sql
scc_schema_views.sql
scc_schema_create_indexes.sql
scc_schema2_deletes.sql
scc_schema2_setup.sql
scc_schema_43_new_setup.sql
scc_processingworkingdeleterelations.sql
scc_processDeletes.sql
scc_processcreateattributes.sql
scc_processcreatecomponents.sql
scc_processAPICleanup.sql
scc_processAPIQueue.sql
scc_processcleanupstrandeddata.sql
scc_postdot1deleta.sql
scc_initialize.sql
scc_initiate_failover.sql
scc_migrate_421_to_43.sql
scc_pg_schema_setup.sql
scc_remove_merged_resources.sql
scc_getEnrichmentNotifications.sql
scc_getStageClassList.sql
genScrApiIdml.sql
scc_API_schema_analyze.sql
scc_610if0001_setup.sql
scc_analyzepersistent.sql
scc_processCreates.sql
scc_processAbstractRscs.sql
scc_processingworkingdeletecomps.sql
scc_processRefresh.sql
scc_recalc_dependency_and_counters.sql
createidmlbook.sql
db-cleanup.sql
scc_changeclasstypes.sql
scc_checkfordupsinstage.sql
scc_classToRuleE2.sql
scc_merge_guts.sql
remove_merged_resources.xml
base_schema_truncates.sql
taddm_del_gen_relations.sql
taddm_del_tag_attributes.sql
taddm_schema_setup_db2.sql
taddm_schema_setup_oracle.sql
tbsmudf_clear_regex_cache.db2.sql
ASICLTools.jar
BSM_Templates.xml
BSM_Templates.radsh
BSM_Templates_templates_only.radsh
BSM_Templates_instances_only.radsh
BSM_Templates_updatepropagation.radsh
BSM_TemplateUpdates61FP0001.radsh
BSM_TemplateUpdates61IF0001.radsh
classfilters.xml
uniqueClassFilters.xml
CDM_TO_TBSM4x_MAP.xml
CDM_TO_TBSM4x_MAP_Templates.xml
LabelingRules.xml
NamingRules.xml
EventIdentifierRules.xml
GenIdmlFromTWMNBN.xsl
genStep1DqlForTADDMFromOrm.xsl
getridofnamespaces.xsl
PolicyPatterns.xml
ScrPolicyRulesToSql.xsl
ScrProdcueEmulationsSql.xml
ScrProduceLabelingSql.xsl
ScrProducePostProcessingSql.xsl
ScrProducesql.xsl
sql_symbolics.xml
ScrNamingRulesToSql.xsl
loadBusinessComposerDefinitions.bat
loadBusinessComposerDefinitions.sh
setdbschema.bat
setdbschema.sh
reinit_servicemembership.xml
crviewer.zip (including most jar and SQL files under tools/crviewer)
TBSMExportToImport.xsl
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/61FP0002
---
Added files associated with the DBConfig installer:
tbsmdemo_create_indexes.sql
tbsmdemo_create_views.sql
tbsmdemo_drop_indexes.sql
tbsmdemo_drop_views.sql
tbsmmark_create_indexes.sql
tbsmmark_create_views.sql
tbsmmark_drop_indexes.sql
tbsmmark_drop_views.sql
Replaced files associated with the DBConfig installer:
scc_staging_schema_truncate.sql
scc_staging_schema_setup.sql
scc_staging_schema_index_setup.sql
scc_staging_schema_index_deletes.sql
scc_staging_schema_deletes.sql
scc_staging_schema_analyze.sql
scc_schema_truncates.sql
scc_schema_setup.sql
scc_schema_drop_indexes.sql
scc_schema_deletes.sql
scc_schema_create_indexes.sql
scc_schema_views.sql
scc_schema2_deletes.sql
scc_schema2_setup.sql
scc_610if0001_setup.sql
sql_symbolics.xml
setdbschema.bat
setdbschema.sh
dumpsql.bat
dumpsql.sh
ASICLTools.jar
If you have made changes to the above mentioned DBConfig files you will
find your copy of the files under:
[InstallDirectory]/tbsmdb/logs/install/maintenance/backup/61FP0002
====================================================================
2.0 Hardware and software requirements
For information about hardware and software requirements, see the
Tivoli Business Service Manager Installation Guide on the TBSM
Information Center:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/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.
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.0 to be installed.
This fixpack can also be installed on top of FP1.
3.2 Prerequisites
Tivoli Integrated Portal 2.2.0.13 (TIP FP 2.2.0.13) or higher certified
versions of TIP must be installed after installing this fix pack.
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.
If TIP FP 2.2.0.13 is installed on the GUI Server and the GUI server is on
a separate system than the Data server, the eWAS on the TBSM Data server
system must be upgraded to eWAS 7.0 Fix Pack 31 (or later). The instructions
to apply the eWAS Fix Pack are in section 6.3 below.
Please note that eWAS AppServer and Java SDK 7.0 Fix Pack 31 addresses
various sercurity related issues.
If the TBSM data server and TIP are on the same system, the TIP Server
and the data server must be stopped prior to installing the TIP FP.
Link to download TIP FP 2.2.0.13 -
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.13&platform=All&function=all
Prerequisites
IBM Tivoli Business Service Manager Version 6.1
Installation Instructions
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.0 GA
All TBSM and TIP processes or services must be stopped prior
to the update install, with the exception of Object server and the
DB2 database. Both the Object server and the DB2 database need to
be up and running prior to starting the install or un-install process.
Running the install without backup:
If you prefer to backup DE with your own procedures you can
run the install with the following parameter.
-DNO_BACKUP=true
If you choose this method you must backup DE
before you install. Restore the original system using
your backup/restore procedures or utilities.
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 the 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 to a location it can be edited (/tmp).
b. Update the file to match your environment.
c. 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 all servers.
5. After restarting the servers, run the script ApplyPoliciesFor61FP2 which can be
found on the Data Server under $TBSM_HOME/bin. This script loads
the new/updated policies.
NOTE: Do not run the ApplyPoliciesFor61FP2 on the secondary/backup
data server of a failover pair. This only needs to be run on
the primary data server.
On Windows:
ApplyPoliciesFor61FP2.bat <adminuser> <adminpassword>
For example - ApplyPoliciesFor61FP2.bat tipadmin tipadmin
On Linux/Unix:
./ApplyPoliciesFor61FP2 <adminuser> <adminpassword>
For example - ./ApplyPoliciesFor61FP2 tipadmin tipadmin
NOTE: Verify that the adminuser id and password are
correct, else the script will fail at the last step.
If incorrect, rerun the script with a valid adminuser id and password.
6. After installing the Fixpack, run the dbfileutility command found
under [InstallDirectory/tbsm/XMLtoolkit/bin to update the database
with the correct URL for the 'Show 30 day History' launch.
The canvasOpenURLActions.xml file has the updated URL
and this file can be found on the data server under
[InstallDirectory]/tbsm/av/xmlconfig.
On Windows:
dbfileutility.bat put -f <install_dir>/tbsm/av/xmlconfig/
canvasOpenURLActions.xml -category menuactions -subcategory
action -origin TBSM
On Linux/Unix:
./dbfileutility.sh put -f <install_dir>/tbsm/av/xmlconfig/
canvasOpenURLActions.xml -category menuactions -subcategory
action -origin TBSM
Then run
UNIX
$TBSM_HOME/bin/rad_reinitcanvas tipadmin tippass
Windows
%TBSM_HOME%\bin\rad_reinitcanvas.bat tipadmin tippass
3.7.2 Discovery Library Toolkit
===================================================
1. Navigate to the DiscoveryLibrary directory.
2. To install Fixpack 2,
If you are on a Windows operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.0-FP0002-windows<_64>.exe
If you are on a Unix operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.0-FP0002-<unixplatform><_64>.bin
For console mode, specify "-i console".
Note: If the installer cannot find the TBSM 6.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.
This fixpack includes an update to the database
schema used by the toolkit. The schema can be updated
either by the toolkit installer or by the DBConfig
installer.
In addition to the database schema update, the toolkit
installer will also update the IBM versions of the
CDM_TO_TBSM4x_MAP.xml, CDM_TO_TBSM4x_MAP_Templates.xml,
EventIdentifierRules.xml, LabelingRules.xml,
classfilters.xml, and uniqueClassFilters.xml files.
These are stored in the database.
The toolkit installer will ask whether or not it should
update the database schema.
If 'yes' is selected, then the database user and
password provided must have sufficient authority to create
and drop tables, indexes, and views. If 'yes' is selected,
then the DBConfig install for this fixpack does not
need to update the schema. If the DBConfig installer for
this fixpack was previously run and it updated the
database schema, then specify 'no' here since there is no
need to update the schema twice.
If 'no' is specified, then the database user and
password should have authority to write to the database.
This is required so that the above mentioned XML files can
be updated in the database.
The schema update may take several minutes to complete.
4. Notes and Post-Install Considerations:
a) After installation is complete, you may remove
[fixpack] to save space.
b) Before restarting the toolkit, the database schema
must be updated. If this installer did not perform
that task, then the DBConfig installer must be run
to update the schema.
5. Restart the toolkit.
Note:
This fixpack includes the Business Service Composer
(BSC). This feature uses the Impact service,
ResEnrichReader. This service is not set to automatically
start. If you plan to use the BSC, then the
ResEnrichReader should be set to automatically start.
To set the properties for the ResEnrichReader, go to:
System Configuration->Event Automation->Services
If the service is not shown in the service list, from
the Project pull-down, select Global, this should show
all of the available services in the list.
Select ResEnrichReader, right-mouse and select Edit.
Check the Startup Automatically check box and then save
the change (select the Save Service icon upper left).
Close the edit tab by selecting the "x" in the tab name.
To start the service, select ResEnrichReader, right-mouse
and select Start.
3.7.3 DBConfig
===================================================
1. Navigate to the DBConfig directory.
2. To install fixpack 2,
If you are on a Windows operating system, run the following
command from a prompt:
setup-dbconfig-6.1.0-FP0002-windows.exe
If you are on a Unix operating system, run the following
command from a prompt:
setup-dbconfig-6.1.0-FP0002-<unixplatform>.bin
For console mode, specify "-i console".
Note: If the installer cannot find the TBSM 6.1 DBConfig,
verify that the database configurator 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_DBCONFIG_BASE to the location of DBConfig and restart the
installer. For example:
Windows:
set TBSM_DBCONFIG_BASE=C:\Program Files\IBM\tivoli\tbsmdb
UNIX:
export TBSM_DBCONFIG_BASE=/opt/IBM/tivoli/tbsmdb
3. This fixpack includes an update to the database
schema used by the toolkit. The installer will
ask whether or not it should update the database
schema.
If 'yes' is specified, then the database user and
password provided must have sufficient authority to create
and drop tables, indexes, and views.
If 'no' is specified, then the updated files will be
written to the file system, and the database will need
to be updated either manually after the install completes
or by the Discovery Library Toolkit installer.
If the toolkit installer updated the database schema,
specify 'no'.
4. Notes and Post-Install Considerations:
a) Even if the toolkit installer updated the database
schema, we still recommend that you run the DBConfig
installer so that the SQL files used by any future
invocation of the tbsm_db script are up to date.
b) After installation is complete, you may remove
[fixpack] to save space.
c) To update the database schema manually:
- cd [InstallDirectory]/tbsmdb/tools/XMLtoolkit/bin
On Windows:
- setdbschema -U dbuser -P dbpw -f upd6102
- setdbschema -U dbuser -P dbpw -f 2
- setdbschema -U dbuser -P dbpw -f t
- setdbschema -U dbuser -P dbpw -f v
On UNIX:
- ./setdbschema.sh -U dbuser -P dbpw -f upd6102
- ./setdbschema.sh -U dbuser -P dbpw -f 2
- ./setdbschema.sh -U dbuser -P dbpw -f t
- ./setdbschema.sh -U dbuser -P dbpw -f v
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_aix523CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit)
KR9_aix526CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit)
* Linux: KR9_li6263CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit)
KR9_lx8266CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit)
* Solaris: KR9_sol283CD-6.1.0-TIV-BSM-FP0002.tar.gz -(32 bit)
KR9_sol286CD-6.1.0-TIV-BSM-FP0002.tar.gz -(64 bit)
* Windows: KR9_winntCD-6.1.0-TIV-BSM-FP0002.zip -(32 bit)
KR9_wix64CD-6.1.0-TIV-BSM-FP0002.zip -(64 bit)
* zLinux: KR9_ls3243CD-6.1.0-TIV-BSM-FP0002.tar.gz - (32 bit)
KR9_ls3246CD-6.1.0-TIV-BSM-FP0002.tar.gz -Li S390R2.4(64 bit)
KR9_ls3266CD-6.1.0-TIV-BSM-FP0002.tar.gz -Li S390R2.6(64 bit)
To install the updated TBSM agent:
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.0/com.ibm.tivoli.itbsm.doc_6.1/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 install of the FixPack and before the uninstall of the
FixPack, with the exception of Object server and the DB2 database.
Both the Object server and the DB2 database need to be up and running
prior to starting the install or un-install process.
Please note: If uninstalling on a windows system please copy the following
before attempting an uninstall:
Copy the files in:
<installDir>/tipv2/logs/tbsm/Maintenance/backup/6.1.0.0/FP0002/data/TBSM.ear
to
<installDir>/tipv2/profiles/TBSMProfile/installedApps/TBSMCell/TBSM.ear
Attention: Uninstall the Fix Pack with the same user that was used to
install TBSM 6.1.0 GA.
Install method and uninstall
The uninstaller runs using the same method that was used for
the install.
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/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:
1. Change to the directory:
<installDir>/tbsm/_uninst/TBSM_FP2
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
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. Restart the Data Server and Dashboard Server.
5. On Unix operating systems, uninstalling the Fix Pack may remove
execute permissions from rad files, in the <INSTALL DIR>/tbsm/bin
directory. To determine if this is the case, change to the
directory and use ls -l rad* command, as below:
cd <INSTALL DIR>/tbsm/bin
ls -l rad*
The permissions should show execute (x) for each file,
for all groups.
-rwxr-xr-x 1 <user> <user group> 2529 Aug 30 2008 rad_compilewsdl
-rwxr-xr-x 1 <user> <user group> 2238 Aug 30 2008 rad_crypt
-rwxr-xr-x 1 <user> <user group> 19398 Jul 20 14:02 rad_db
-rwxr-xr-x 1 <user> <user group> 2827 Aug 30 2008 rad_discover_schema
-rwxr-xr-x 1 <user> <user group> 2225 Aug 30 2008 rad_keystore
-rwxr-xr-x 1 <user> <user group> 2084 Aug 30 2008 rad_maint_add
-rwxr-xr-x 1 <user> <user group> 2084 Aug 30 2008 rad_maint_remove
-rwxr-xr-x 1 <user> <user group> 4055 Aug 30 2008 rad_radshell
-rwxr-xr-x 1 <user> <user group> 2494 Jul 20 14:02 rad_reinitcanvas
-rwxr-xr-x 1 <user> <user group> 2258 Aug 30 2008 rad_sendevent
If required, use chmod 755 to update the permission for required files,
i.e. chmod 755 rad_db
Discovery Library Toolkit
===================================================
The toolkt 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/61FP0002
DBConfig
===================================================
The DBConfig portion of this fixpack cannot be uninstalled.
A backup copy of the original files can be retrieved from:
[InstallDirectory]/
tbsmdb/log/install/maintenance/backup/61FP0002
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/TBSM_FP2,
then nothing really got installed and you can delete the TBSM_FP2 file and
reinstall.
3.11 Restoring failed DE upgrade from backup
To recover a failed Deployment Engine upgrade in TBSM 6.1.0, see the
TBSM Installation Guide at:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/installguide/bsmi_upgrade_t_restore42.html
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg24032540