Tivoli Business Systems Manager(TBSM)V3R1 Fix Pack 3(3.1.0-TIV-BSM-FP0003)

Downloadable files


Abstract

This Fix Pack addresses problems reported in Tivoli Business Systems Manager 3.1.

Download Description

IBM Tivoli Business Systems Manager

3.1.0-TIV-BSM-FP0003 (December 2007)

Version 3.1

+---- Note ------------------------------------------------------------+

Before using this information and the product it supports, read the
information in Appendix C, "Notices".

+----------------------------------------------------------------------+



This edition applies to Version 3, Release 1 of IBM Tivoli Business
Systems Manager and to all subsequent releases and modifications until
otherwise indicated in new editions.

Copyright International Business Machines Corporation 2000, 2007. All
rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.


Contents

1.0 About Fix Pack 3
1.1 What's in Fix Pack 3?
1.1.1 Additional support for prerequisites
1.1.2 APARs included in Fix Pack 3
1.1.3 Interim fixes included in Fix Pack 3
1.1.4 LA Fixes included in Fix Pack 3
2.0 Installation and configuration
2.1 Prerequisite
2.2 Corequisite
2.3 Hardware and software requirements
2.4 Backing up databases
2.5 Fix Pack 3 contents
2.6 Before Installing the Fix Pack
2.6.1 Special Considerations
2.6.2 For your information
2.7 Extracting the Fix Pack
2.8 Installing the Fix Pack
2.8.1 On the Tivoli Business Systems Manager Database Server:
2.8.2 On the Tivoli Business Systems Manager History Server:
2.8.3 On each of the other Tivoli Business Systems Manager
non-database servers:
2.8.4 On each Tivoli Business Systems Manager client install:
2.9 Silent console installation
2.10 Console Software Package Blocks (SPB) installation:
2.11 Tivoli Enterprise Console Event enablement component:
2.12 XML Toolkit:
2.13 Special configuration instructions for failover environment that
uses SQL 2000
2.14 Tivoli Business Systems Manager Warehouse Enablement Pack 3.2.0.9
updates
2.15 OpenView adapter
2.15.1 OpenView Server:
3.0 Tivoli Business Systems Manager support for WebSphere Application
Server v6
3.1 Introduction
3.1.1 Terminology used in this chapter
3.1.2 Default installation directory for v5 and v6
3.2 Prerequisites
3.2.1 IBM Tivoli Business Systems Manager
3.2.2 IBM WebSphere Application Server, Version 6
3.3 Compatibility
3.4 WebSphere Application Server Installation and Migration
3.4.1 1. Install WebSphere Application Server 6.1
3.4.1.1 Sample Applications
3.4.1.2 Installation Directory
3.4.1.3 Disable Administrative Security
3.4.1.4 Node and Host names
3.4.2 2. Install WebSphere Application Server 6.1 Fix pack 11
3.5 Create the tbsm31 profile
3.5.1 v6
3.6 Run the Migration wizard
3.7 Post Migration Steps
3.7.1 Remove the v5 Service
3.7.1.1 Verification Steps
3.7.2 Delete the v6 default profile
3.7.2.1 Verification Steps:
3.7.3 Troubleshooting:
3.7.4 Reboot
3.7.5 Configure Security Settings
3.8 Health Monitor support
3.8.1 Installing this support on the Health Monitor
3.8.1.1 On the Health Monitor server machine
3.9 Finished migration
3.10 Post Installation information
3.10.1 Failover
3.10.2 Health Monitor
3.10.3 Starting and Stopping WebSphere Application Server
3.10.3.1 To start the v6 server:
3.10.3.2 Verification Steps:
3.11 Problem determination
3.11.1 Log Files
3.11.1.1 Migration Log Files
3.11.1.2 TBSM Console Server Log Files
3.11.2 Known Problems and Workarounds
3.11.2.1 Service does not stop if userid in soap.client.props file
3.12 Command line alternatives to the v6 Migration wizard
3.12.1 WASPreUpgrade
3.12.2 WASPostUpgrade
4.0 Upgrading to SQL Server 2005 Enterprise Edition
4.1 Prerequisites
4.2 How to upgrade to SQL Server 2005
4.2.1 Apply Service Pack 2 for SQL Server 2005
4.2.2 Reboot the system
4.3 SQL 2005 Post-upgrade Steps
4.3.1 Apply the upgrade file for SQL 2005 on the Database server
4.3.2 Apply the upgrade file for SQL 2005 on the History server
4.3.3 Upgrade job steps that use tokens in SQL Server 2005
4.3.3.1 Upgrade steps:
4.3.4 Check database integrity
4.3.5 Disabling Selected SQL Server 2005 Management Studio Options
4.3.6 Detach and attach databases
4.3.7 Update statistics
4.4 Tivoli Business Systems Manager Failover
4.4.1 Considerations for Failover
Appendix A. APARs included in 3.1.0-TIV-BSM-FP0003
Appendix B. Contacting Customer Support
B.1 Describe the problem and gather background information
B.2 Submit the problem to IBM Software Support
Appendix C. Notices
C.1 Trademarks

1.0 About Fix Pack 3

3.1.0-TIV-BSM-FP0003, also known as Fix Pack 3, fixes problems reported
for Tivoli(R) Business Systems Manager 3.1. This Fix Pack must be
applied on Tivoli Business Systems Manager 3.1 that has Fix Pack 2
(3.1.0-TIV-BSM-FP0002) or higher, already installed on all the servers
and clients.

ATTENTION: Fix Pack 3 is not cumulative, and it prereqs TBSM 3.1, Fix
Pack 2.

1.1 What's in Fix Pack 3?

1.1.1 Additional support for prerequisites

The following additional supported versions of prerequisites that have
previously been listed for Tivoli Business Systems Manager 3.1:
* IBM WebSphere(R) Application Server 6.1.0.11
* Microsoft(R) SQL Server 2005, Service Pack 2

Important:
* Do not upgrade to Microsoft SQL Server 2005 until after you
apply TBSM 3.1, Fix Pack 3. This upgrade can only be applied
on top of Fix Pack 3 for TBSM 3.1.
* For TBSM 3.1, the only supported path to Microsoft SQL
Server 2005 is an upgrade from Microsoft SQL Server 2000. (A
fresh install of Microsoft SQL Server 2005 is not
supported.)

* MKS Toolkit 9.1 for System Administrators
* Support for HP OpenView 7
* Windows Server 2003, Service Pack 2



1.1.2 APARs included in Fix Pack 3

For APARs that are included in this Fix Pack, see Appendix A, "APARs
included in 3.1.0-TIV-BSM-FP0003".

1.1.3 Interim fixes included in Fix Pack 3

Fix Pack 3 includes the following interim fixes:

3.1.0.2-TIV-BSM-IF0011


3.1.0.2-TIV-BSM-IF0012


3.1.0.2-TIV-BSM-IF0013


3.1.0.2-TIV-BSM-IF0014


3.1.0.2-TIV-BSM-IF0015


1.1.4 LA Fixes included in Fix Pack 3

All LA Fixes shipped on top of Fix Pack 2 are included in Fix Pack 3

2.0 Installation and configuration

2.1 Prerequisite

TBSM v3.1 Fix Pack 3 has the following prerequisite:
* Tivoli Business Systems Manager 3.1, with Fix Pack 2 or higher.

2.2 Corequisite

TBSM v3.1 Fix Pack 3 has the following corequisite:
* Strongly recommended: IBM WebSphere Application Server 6.1.0.11

2.3 Hardware and software requirements

Refer to the IBM(R) Tivoli Business Systems Manager v3.1 Installation
and Configuration Guide for the hardware and software requirements for
installing Tivoli Business Systems Manager.

2.4 Backing up databases

Back up all databases before applying the Tivoli Business Systems
Manager v3.1 Fix Pack 3. It is critical to have valid database backups
taken prior to applying Fix Pack 3, as you might need them in the event
you want to reinstall the entire Fix Pack. The following 12 databases
should be backed up before applying this Fix Pack:
* ASIRuleSvc
* Meta
* msdb
* Object
* ObjectEvents
* ObjectQueues
* Resource Object Data Manager (RODM)
* RODMLoad
* WebServer
* OPCLoad
* History
* Adapter

Ensure that these backups exist and the backups were completed during
the same time frame. Typically, backups should be handled using a
database maintenance plan. Save the backups until Fix Pack 3 has been
successfully tested.

We recommend that you back up the databases again (into a new backup
file) after successful Fix Pack installation. In the event that you have
a hard failure of your system, taking this extra precaution saves you
the time required to re-apply the Fix Pack.

If you are applying the Tivoli Business Systems Manager Warehouse Pack,
ensure that backups of all IBM Tivoli Data Warehouse databases are
available before installing this Fix Pack.

2.5 Fix Pack 3 contents


* This readme file in two formats:
* 3.1.0-TIV-BSM-FP0003.readme.pdf
* 3.1.0-TIV-BSM-FP0003.readme (text file)

* 3.1.0-TIV-BSM-FP0003.tar

2.6 Before Installing the Fix Pack

Note: You should know that if you uninstall the Fix Pack you will be
removing the entire product, (either the server component code or
the client component code), not just the Fix Pack code.

* This Fix Pack could require up to 5 Gb of free space on your SQL
Server installation drive. Ensure that the free space is available
before applying this Fix Pack.
* Before applying the Fix Pack, make sure no shell scripts are running
in the background.
* Stop the following services and executables on all Tivoli Business
Systems Manager servers and clients:
* All Tivoli Business Systems Manager services
* SQLServerAgent (SQL server agent)
* MSSQLServer (SQL server)
* IIS Admin Service and World Wide Web Publishing Service (if
present)
* All IntelligentMonitor adapters and their daemons

Do not apply the console component of this Fix Pack without first
applying the base component.

This is not a cumulative Fix Pack. It must be applied on a Tivoli
Business Systems Manager v3.1, with Fix Pack 2 or higher.

2.6.1 Special Considerations


* This Fix Pack will create a new SQL job, Delete old OPC daily plans,
which will be disabled by default. If you are interested in using
this SQL job, you must manually enable it from the SQL Enterprise
Manager. It also has the @daystokeep parameter in the SQL job step
set to 60 days by default, which means any daily plan which is older
than 60 days will be deleted, alongwith all its corresponding data.
You may want to change the @daystokeep parameter to a much larger
number the first time the job is run (e.g. 365), as it may take a
long time to perform the initial cleanup if you have a large OPCLoad
database.
* For the fix for APAR OA21742, the cleanup of the additional tables
will occur with the running of the "Delete Old ObjectEvent Records"
and "Delete Old Closed Notes" SQL jobs.

If the cleanup of the ObjectStateHist table causes a performance
impact when the "Delete Old Closed Notes" job is run, change the job
step to run:

EXEC asisp_deleteOldNotes @trunc = 1

* For the fix for APAR OA22602, the capability will only be available
after it has been manually enabled by entering the following command
from SQL Query Analyzer on the database server, and restarting the
Console Server:
INSERT INTO SystemConfiguration VALUES
('Feature', 'WCDisplayURLHyperlinksInDescription', 1, 'INT')



This capability can be disabled at any time by running the following
command, and restarting the Console Server:

UPDATE SystemConfiguration SET propertyvalue = 0
WHERE groupname = 'Feature'
AND propertyname = 'WCDisplayURLHyperlinksInDescription'

* For the fix for APAR OA15386, by default, the new Date Received
column does NOT appear in the Event Viewer.

To enable display of the Date Received column, set the configuration
table property by using the SQL Server Query Analyser to connect to
the TBSM Object database. Once connnected, enter the following
command:

EXEC _SetSystemConfiguration @groupname='_GetEventViewerEvents',
@propertyname='DisplayDBServerCTime',
@propertyvalue=1,
@propertydatatype='INT'

To disable display of Date Received column, set the configuration
table property by using the SQL Server Query Analyzer to connect to
the TBSM Object database. Once connnected, enter the following
command:

EXEC _SetSystemConfiguration @groupname='_GetEventViewerEvents',
@propertyname='DisplayDBServerCTime',
@propertyvalue=0,
@propertydatatype='INT'

After you change the configuration table property value, you must
restart the Console Server and any connected consoles for the change
to take effect.

2.6.2 For your information

Notes:
1. Changes on the Object, Meta, RODM, and WebServer databases do not
show up on the History server until after the first backup has taken
place after the install.
2. To apply this Fix Pack in a failover environment
a. Stop SQLServerAgent on both primary and secondary servers, and
ensure that it is stopped.
b. Run the following script on the primary database server and
history server to gracefully abort the log shipping process :
sh fo_logship.ksh -A



Running this script stops the log shipping and brings the
secondary databases out of read-only mode.

If the database remains in the read-only mode, run the following
stored procedure from the SQL Query Analyzer on the secondary
(non-active) database server and the history server:

EXEC msdb..asisp_recover_databases

Configuration for Failover environment is located at 2.13, "Special
configuration instructions for failover environment that uses SQL
2000".

2.7 Extracting the Fix Pack

To expand file 3.1.0-TIV-BSM-FP0003.tar:
1. Copy the file 3.1.0-TIV-BSM-FP0003.tar to your system.
2. Unpack the file with the following command:

tar -xvf 3.1.0-TIV-BSM-FP0003.tar

This creates a directory called /3100TIVBSMFP0003 that includes the
following files:
* TIV_BSM_3.1.0_FP0003_base.tar
* TIV_BSM_3.1.0_FP0003_consoles.tar
* TIV_BSM_3.1.0_FP0003_consolesSPB.tar
* TIV_BSM_3.1.0_FP0003_IMfOpenView.tar
* TIV_BSM_3.1.0_FP0003_itecEventEnablement.tar
* TIV_BSM_3.1.0_FP0003_TDW_fix.tar
* TIV_BSM_3.1.0_FP0003_XMLToolkit.tar

.

2.8 Installing the Fix Pack

Note: In the following steps
* <fix pack> refers to the directory where this Fix Pack resides
after you extract it from the tar file.
* <TivoliManager> refers to the directory where Tivoli Business
Systems Manager is installed.

Important: If the database upgrade step fails for any reason during the
Fix Pack installation, do not rerun the install or do the upgrade
manually. Collect the install logs and contact IBM Service. The
install logs can be found in these 2 locations:
* The system temp directory. Enter cd %TEMP% to get to the system
temp directory. Send the install log from the system temp
directory.
* The <TivoliManager>/sql directory. From this directory type the
following 2 commands to package up the logs:
1. tar -cvf fp3_install_logs.tar *.log
2. gzip -c fp3_install_logs.tar < fp3_install_logs.tar.gz

2.8.1 On the Tivoli Business Systems Manager Database Server:


1. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

2. Change to the <baseServices> directory.
3. If you are running log shipping, stop it by issuing the following
command from the <TivoliManager>\bin directory.
sh fo_logship.ksh -A

4. Run the setup.exe file from the <baseServices> directory.
5. From the window that is displayed, select a language.
6. Click Next on the Welcome window.
7. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
8. After you read the list of services that will be stopped, click Next.
9. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
10. Click the box that represents the type of installation, either
distributed or distributed and z/OS(R).
11. A window is displayed while the Microsoft SQL Server service is
started. You can choose to upgrade databases automatically, as a part
of the installation.

If you choose not to upgrade the databases, the databases can be
upgraded manually after the installation by going to the
<TivoliManager>/sql directory and running

sh applyupgrade.ksh 3102tivbsmfp0003.upg
[ [-S<DBserver>] [-E | [[-U<DBuser>] [-P<DBpassword>]]] ]


Database parameters are as follows:

-S<DBserver>
Server where database resides. Default=[$tbsm_server]

-E Use trusted connection

-U<DBuser>
Database username. Default=[$tbsm_userid]

Otherwise, trusted connection used.


-P<DBpassword>
Database password. Default=[$tbsm_password]

If you choose to manually update the database, make sure the
MSSQLServer service is running before running the database upgrade
script from the command prompt.

Click Next.

12. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
updated on this server. Click Next to continue with the installation.
13. Status is displayed. The percentage completion bar is updated as
files are installed.

When the installation has finished, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

14. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.

If the upgrade is applied after the installation, instead of by the
installer, ensure the SQL agent is not running and all of the Tivoli
Business Systems Manager services have been stopped, including the
History server.

15. After the system has rebooted, ensure all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Database
Server have been restarted.

2.8.2 On the Tivoli Business Systems Manager History Server:


1. If it is not currently running, start MS SQL Server service.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

3. Change to the <baseServices> directory.
4. Run the setup.exe file from the <baseServices> directory.
5. From the window that is displayed, select a language and click OK.
6. Click Next on the Welcome window.
7. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
8. This panel lists the services that will be stopped. Click Next.
9. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
10. A window is displayed while the Microsoft SQL Server service is
started. You can choose to upgrade databases automatically, as a part
of the installation.

If you choose not to upgrade the databases and you are at 3.1 plus
Fix Pack 2 level, the databases can be upgraded manually after the
installation by going to the <TivoliManager>/sql directory and
running

sh applyupgrade.ksh 3102tivbsmhistfp0003.upg -S <HistoryServerName> -U
<SQLServerUserName> -P <SQLServerPassword>

Click Next.

11. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
upgraded on this server. Click Next to continue with the
installation.
12. Status is displayed. The percentage completion bar is updated as
files are installed.

When the installation has finished, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

13. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.
14. After the system has rebooted, ensure all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Database
Server have been restarted.

2.8.3 On each of the other Tivoli Business Systems Manager non-database
servers:


1. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

2. Run the setup.exe file from the <baseServices> directory.
3. From the window that is displayed, select a language.
4. Click Next in the Welcome window.
5. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
6. This panel lists the services that will be stopped. Click Next.
7. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
8. For the Console server, supply the WebSphere Server userid and
password. Click Next.
9. If you have already upgraded to WAS 6, you will see a screen
prompting for the WebSphere 6.x profile. The name of the profile is
tbsm31. Click Next.
10. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
upgraded on this server. Click Next.
11. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.
12. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.
13. After the system has rebooted, restart all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Server.

Note: If an error occurs installing the Console Server component, and
you need to run the update manually (for example, if the WebSphere
ID or password was entered incorrectly), do not rerun the Fix Pack
installer. Instead, run the following command from the
<TivoliManager>\Console Server, to update the console server:



"<WebSphere install dir>\AppServer\bin\wsadmin.bat"
-f update.jacl -conntype SOAP -user <UserID> -password <UserPswd>

If you are upgrading to WAS 6.1.0.11, go to 3.0, "Tivoli Business
Systems Manager support for WebSphere Application Server v6".

2.8.4 On each Tivoli Business Systems Manager client install:


1. Stop the console.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_consoles.tar

3. The console is supported on a number of operating systems. Change to
the directory representing the appropriate operating system. Run the
setup file from the consoleInstall\<platform> directory.
4. From the window that is displayed, select a language.
5. Click Next in the Welcome window.
6. Read the software license agreement. If you accept the terms of the
agreement, click the radio button to indicate that you accept the
terms and then click Next.
7. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
8. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed. Click Next to continue with the
installation.
9. You are asked if you want the console to be started once the
installation is complete Yes is the default and it is selected. If
you do not want the console to be started once the installation is
complete, click the check box to remove the selection. Click Next.
10. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

2.9 Silent console installation


1. Run the setup.exe from the <fix pack> directory as follows:

setup -options-template outputFileName.scr

2. Edit outputFileName.scr to change any installation settings.
3. To install:

setup -options outputFileName.scr -silent

To uninstall the entire client, not just the Fix Pack code:

_uninst\uninstall -silent

IMPORTANT: _uninst\uninstall -silent uninstalls the entire client
component code not just the Fix Pack code.

2.10 Console Software Package Blocks (SPB) installation:

Using software package blocks (SPBs), the fix pack for the console can
be distributed to endpoints in a Tivoli Managed Environment. Tivoli
Business Systems Manager 3.1 needs to be installed on the endpoints
before the fix pack can be distributed.
1. Enter tar -xvf TIV_BSM_3.1.0_FP0003_consolesSPB.tar to extract the
SPBs.
2. See Appendix D. Distributing the Console in a Tivoli Managed
Environment in the Tivoli Business Systems Manager 3.1 Installation
and Configuration Guide for SPB installation instructions.

Note: The fix pack install program does not allow you to change the
installation directories or server name, so there are no default
variables to change when you install SPBs.

The fix pack install program automatically locates the original
installation directory on the endpoint.

To remove the console using software distribution, remove the original
Tivoli Business Systems Manager 3.1 SPB. See Appendix D. Distributing
the Console in a Tivoli Managed Environment in the Tivoli Business
Systems Manager 3.1 Installation and Configuration Guide for
instructions. You should not remove the fix pack's SPB.

2.11 Tivoli Enterprise Console Event enablement component:

1. Unpack the file with the following command:
tar -xvf TIV_BSM_3.1.0_FP0003_itecEventEnablement.tar

2. Use the following information to install patch from the Tivoli
desktop:
a. You must have the install_product and super authorization roles to
successfully install this patch.
b. You should not have a running RIM_MS_SQL_prog on your RIM host
when you apply this patch.
c. Select Install -> Install Patch from the Desktop menu to display
the Install Patch dialog.
d. Click the Select Media button to display the File Browser dialog.
e. Enter the path to the directory containing the patch,
<fixpack>/itecEventEnablement/fp3, in the Path Name field.
f. Click the Set Media & Close button to return to the Install Patch
dialog.
g. The patch install list now contains the component name:
3.1.0-Tivoli_BSM_Event_Enablement-FP0003

h. Select the patch by clicking on it.
i. Select the clients to install this patch on.
j. Click Install to install the patch.

2.12 XML Toolkit:

If you previously installed the XML Toolkit as a separate component,
then complete these instructions to upgrade that function. Do not follow
these instructions if you are using the toolkit version that is
automatically installed on the database server.

1. Unpack the file with the following command:
tar -xvf TIV_BSM_3.1.0_FP0003_XMLToolkit.tar

The XML Toolkit is supported on a number of operating systems. Change
to the directory representing the proper operating system.
2. Run the setup file from the XMLtoolkit\<platform>directory.
3. From the panel that is displayed, select a language.
4. Click Next on the Welcome panel.
5. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
6. If you plan to use CCMDB discovery library books and want this
capability to be configured during installation of Fix pack 3, click
the appropriate selection and then click Next.
7. If you plan to use the CCMDB reader for discovery, enter the location
for discovery library books.
8. When asked if files that are being updated should be backed up first,
click the box if you would want the files to be backed up. Click
Next.
9. Summary information is displayed. Click Next to finish the
installation.
10. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.



2.13 Special configuration instructions for failover environment that
uses SQL 2000

IMPORTANT: If you are going to migrate to SQL 2005 immediately after
applying this Fix Pack, do not follow these instructions; instead
see 4.0, "Upgrading to SQL Server 2005 Enterprise Edition".

1. Apply the upgrade to the primary and secondary servers as previously
described in 2.8, "Installing the Fix Pack".
2. Reconfiguration of failover is required before re-starting the
failover environment. Run the configuration script fo_config with -G
option to regenerate the configuration template.
sh fo_config -G > fo.cfg

3. Modify the fo.cfg to fit your environment before running the
configuration script:
sh fo_config -f fo.cfg

4. Start SQLServerAgent on both primary and secondary servers, and
ensure that it is started.
5. From a Command Prompt on the primary database server, enter this
command to reinitialize Log Shipping in the proper direction:

sh fo_logship.ksh

For additional information, see 4.4, "Tivoli Business Systems Manager
Failover".

2.14 Tivoli Business Systems Manager Warehouse Enablement Pack 3.2.0.9
updates

To expand file TIV_BSM_3.1.0_FP0003_TDW_fix.tar:
1. Copy the file TIV_BSM_3.1.0_FP0003_TDW_fix.tar to your system.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_TDW_fix.tar

3. When installing this Fix Pack on the Tivoli Data Warehouse control
server, follow the procedure from the Installing and Configuring
Tivoli Data Warehouse version 1.2 Guide. This procedure is documented
in Chapter 8, Installing and upgrading warehouse packs. The required
configuration file (twh_install_props.cfg) is located in the
\tedw_apps\gtm directory.

2.15 OpenView adapter

To expand file TIV_BSM_3.1.0_FP0003_IMfOpenView.tar, unpack the file
with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_IMfOpenView.tar

2.15.1 OpenView Server:

1. Copy the Intelligent Monitor for OpenView install image from the <fix
pack> \IMfOpenView directory to the OpenView server.
2. Install the Intelligent Monitor for OpenView. Refer to the Tivoli
Business Systems Manager Installation and Configuration guide for
instructions on how to install the Intelligent Monitor for OpenView.
3. Configuration information is available in the file

IMfOpenView_readme*.htm

This file is located in the /usr/OV/doc directory on the HP OpenView
server.

3.0 Tivoli Business Systems Manager support for WebSphere Application
Server v6

This chapter provides information about the IBM Tivoli(R) Business
Systems Manager (TBSM) 3.1 product, support for running the TBSM Console
Server application on IBM WebSphere Application Server, Version 6.

Become familiar with the information in this chapter before you install
this support.

3.1 Introduction

TBSM 3.1 included and automatically installed IBM WebSphere Application
Server, Version 5.

TBSM 3.1 Fix Pack 3 provides support for running the TBSM Console Server
application in a WebSphere Application Server Version 6 environment.

This chapter includes:
* Instructions to migrate the TBSM Console Server from WebSphere
Application Server Version 5 to version 6.
* Upgraded scripts to allow TBSM Failover to correctly failover in a
WebSphere Application Server v6 environment.
* Enhancements to the TBSM Health Monitor, so that it can locate and
monitor WebSphere Application Server v6.

3.1.1 Terminology used in this chapter

v5 WebSphere Application Server Version 5. This version was
included with and automatically installed by the TBSM 3.1
installation program.

v6 WebSphere Application Server Version 6.1.0.11

3.1.2 Default installation directory for v5 and v6

The default installation directory for WebSphere Application Server is
not the same for v6 as it was for v5.

In v5 the default installation directory was:

c:\Program Files\WebSphere\AppServer

In v6 the default installation directory is:

c:\Program Files\IBM\WebSphere\AppServer

In the instructions that follow, be sure to note and use the correct
directories when running commands for v5 or v6.

3.2 Prerequisites

3.2.1 IBM Tivoli Business Systems Manager

* TBSM 3.1, with Fix Pack 2 or higher must be installed and fully
configured.
* The TBSM Console Server application must already be successfully
running on WebSphere Application Server, Version 5.0.

Important: Because of the configuration processing that occurs during
the TBSM 3.1 installation process, we do not provide
instructions for, nor support a 'bare-bones' installation of
the TBSM Console Server application on WebSphere Application
Server v6. You must have an already-operational TBSM 3.1
installation running on v5, and follow the migration
instructions in this chapter to upgrade it to a v6
installation.

3.2.2 IBM WebSphere Application Server, Version 6

This Fix Pack does not include v6 - you will need to obtain and install
a supported version of v6 before installing and configuring this support
for v6. See3.3, "Compatibility" for the list of supported v6 versions.

3.3 Compatibility

Fix Pack 3 support for WebSphere Application Server is compatible with
the following version of WebSphere Application Server.
* IBM WebSphere Application Server, Version 6.1.0.11 (on Windows only)

Note: No other WebSphere product type is supported. For example,
neither Network Deployment nor Community Edition is supported.

3.4 WebSphere Application Server Installation and Migration

WebSphere Application Server v6 must be installed on the same machine as
the current v5-based TBSM Console Server.

To get to IBM WebSphere Application Server, Version 6.1.0.11, do the
following:

3.4.1 1. Install WebSphere Application Server 6.1

Ensure that the previous version of WebSphere is not running before
installing WebSphere v6. The following information can assist in
determining how to respond to certain options on specific panels of the
v6 installation.

3.4.1.1 Sample Applications

The sample applications are not required by TBSM. It is okay to deselect
this option.

3.4.1.2 Installation Directory

Keep the default installation directory (c:\Program
Files\IBM\WebSphere\AppServer).

Note: The TBSM 3.1 installation program automatically installed v5 in
the following directory:
c:\Program Files\WebSphere\AppServer

In v6, the default installation directory has changed to
c:\Program Files\IBM\WebSphere\AppServer

This allows the two versions of WebSphere Application Server to
coexist on the same machine.

Important: Do not attempt to install v6 into the same directory in which
v5 was installed. You may not receive an error message during the
installation process; however, the new v6 might not migrate
correctly.

3.4.1.3 Disable Administrative Security

Important:: Be sure to deselect the Enable administrative security
checkbox on the Enable Administrative Security panel during the
installation.

Depending on your v5 configuration, administrative security might be
automatically re-enabled after the v5 to v6 migration process is
completed. If you want, you can use the WebSphere Administrative Console
and re-enable administrative security after the v5 to v6 migration
process is complete.

3.4.1.4 Node and Host names

If you perform a custom installation, you might be prompted for a Node
Name and Host Name. You should accept the default values. Do not use
tbsm31 as the Node name.

The installation will create a temporary default profile with these
default node and host name. Instructions in the following sections
explain how to create a new tbsm31 profile and delete the temporary
default profile.

3.4.2 2. Install WebSphere Application Server 6.1 Fix pack 11

You can download the fix pack and get installation instructions from the
WebSphere support site located at:

http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24016159

3.5 Create the tbsm31 profile

After the v6. installation is complete, you need to create a new profile
for TBSM 3.1. This profile will be named tbsm31 and will contain all of
the configuration information and files required to run the TBSM Console
Server application.

Note: The v6 installation process creates a default profile (named
"AppSrv01" ). This default profile should be deleted after the v5
to v6 migration is completed. See 3.7.2, "Delete the v6 default
profile", for instructions on deleting this default profile.

To create the tbsm31 profile:

3.5.1 v6

1. Start the Profile Management tool:

Start->All Programs->IBM WebSphere->Application Server v6->Profile
Management tool.

2. Welcome

Click Next.

3. Environment Selection:
* Select Application server..
* Click Next.

4. Profile Creation options:
* Select Advanced profile creation.
* Click Next.

5. Optional Application Deployment:
* Select Deploy the administrative console.
* Optionally, select Deploy the default application (this is not
required by TBSM)
* Click Next.

6. Profile Name and Location:


* Profile name: tbsm31
* Profile directory:
c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31

* Select Make this profile the default.
* Click Next.

7. Node and host names:

Node name: tbsm31

Host name: keep the default (the hostname of the current machine)

* Click Next.

8. Administrative Security:
* Deselect Enable administrative security.
* Click Next.

9. Port values assignment:
* Accept the default port assignments.
* Click Next.

10. Windows Service Definition:
* Select Run the Application Server process as a Windows service.
* If you use LDAP, select Log on as a local system account.
* If you use LocalOS, select Log on as a specified user account and
enter the desired user name and password.
* Startup type: select Automatic.
* Click Next.

11. Web Server Definition:
* Keep Create a Web server definition unselected.
* Click Next.

12. Profile Creation summary:
* Review the information in the summary.
* Click Create.

It could take a few minutes for the profile to be created.
* Once complete: On the panel that states, Profile creation complete,
click Finish.

3.6 Run the Migration wizard

The Migration wizard that is included in WebSphere Application Server,
will migrate all required files and configuration options from the v5
installation to the new v6 installation.

We recommend using the Migration Wizard to perform the migration from v5
to v6. However, you could use the v6-provided command line tools
instead. For details on running those commands, see 3.12, "Command line
alternatives to the v6 Migration wizard".

1. Run the Migration wizard by selecting Migration wizard from the First
steps application, or by opening a Command Prompt and running:
c:\Program Files\IBM\WebSphere\AppServer\bin\migration.bat

2. Click Next after reading information on the Welcome panel.
3. Detected versions of WebSphere Application Server:

Note: The existing v5 installation might not be detected by the
Migration wizard. If this is the case, you need to manually
provide the path to the v5 installation by doing the following:

a. Select Specify the installation location if your existing
product is not listed.
b. In the Installation root directory of the previous version
field, enter the location of the v5 server: C:\Program
Files\WebSphere\AppServer
c. Click Next.

4. Source profile selection:
a. Source Profile: select defaultInstance
b. Click Next.

5. Target profile selection:
a. Target Profile: select tbsm31.
b. Deselect Back up the target profile before migrating the source.
c. Click Next.

6. Migration backup directory:
a. Backup directory: Enter the name of a directory on a drive with at
least 100MB available space. For example: c:\TBSMProfileBackup.
b. Click Next.

7. Application migration settings:
a. Select Migrate and install the applications (this is the default).
b. Click Next.

8. Application migration settings:
a. Select Install the applications in the default directory of the
target version.
b. Click Next.

9. Port value assignment:
a. Select Use port values assigned to previous (source) installation.
b. Click Next.

10. Additional migration options:
a. Select Migrate to support script compatibility.
b. Click Next.

11. Migration summary:
a. Review the settings.
b. Click Next.

The migration will take several minutes.

The process is divided into two steps.
1. After the first step, review the output and click Next.
2. The second step could display some deprecation warnings. These may be
safely ignored. Any errors that appear in the output can be viewed by
opening the log files in the following directory:
c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\logs

or here

c:\TBSMProfileBackup\logs

where c:\TBSMProfileBackup is the profile backup directory you
specified in the Migration backup directory step of the Migration
wizard.
3. After the migration completes, click Next.
4. On the Migration Status panel, click Finish.

3.7 Post Migration Steps

After migration is successful, you should have two new v6 profiles:
* The default profile that was created during installation
* The new tbsm31 profile

You should also have three separate IBM WebSphere Application Server...
services in the Windows Services view:
* One v5 entry
* Two v6 entries

The steps in this section describe how to clean up the unused services
and profiles.

3.7.1 Remove the v5 Service

Remove the v5 service to eliminate conflicts between the v5 and v6
services.

Run the following commands to remove the v5 service.

c:\Program Files\WebSphere\AppServer\bin\WASService.exe -stop server1

c:\Program Files\WebSphere\AppServer\bin\WASService.exe -remove server1

Note: If you installed v5 using the TBSM 3.1 installation program and
accepted the default location, c:\Program
Files\WebSphere\AppServer was the installation directory for v5.

If you installed v5 to a different directory, replace c:\Program
Files\WebSphere\AppServer in the examples with the appropriate
directory.

3.7.1.1 Verification Steps

1. Open the Windows Services by selecting Start->All
Programs->Administrative Tools->Services.
2. Verify that the IBM WebSphere Application Server V5 - server1 service
no longer appears in the list of services. If the Services view was
open when you issued the remove command, refresh the view by
selecting Action->Refresh.

3.7.2 Delete the v6 default profile

The v6 installation process creates a default profile named AppSrv01. To
avoid confusion and potential problems in the future (for example,
accidentally starting the wrong server), you should delete the default
profile.



Run the following commands to remove the default profile:

1. Stop the server1 server:
cd c:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

stopServer.bat server1 -username <username> -password <password>

Note: The -username and -password parameters might not be required,
depending on your configuration.

2. Delete the profile:
cd c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin

manageprofiles.bat -delete -profileName AppSrv01

3.7.2.1 Verification Steps:

1. Open the Windows Services view by selecting Start->All
Programs->Administrative Tools- >Services
2. Verify that the only WebSphere Application Server service remaining
in the list is IBM WebSphere Application Server V6.1 - tbsm31. For
example:


Status Service Name Display Name

running IBMWAS61Service - tbsm31 IBM WebSphere Application Server V6.1 - tbsm31



3.7.3 Troubleshooting:

Even once the default profile is successfully deleted, the
Profiles->default menu items might still appear in the Start->All
Programs menu. You can safely delete these menu items.

If you encounter problems deleting the default profile, see the
information in the InfoCenter for instructions on how to manually remove
it:


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/i
nfo/aes/ae/tpro_removeprofile.html

3.7.4 Reboot

Reboot the system. The v6 service will automatically start.

3.7.5 Configure Security Settings

A few additional security settings must be configured in v6 before
running the TBSM Console Server application.

1. Open the WebSphere Administrative Console:

Start->All Programs->IBM WebSphere->Application Server
v6->Profiles->tbsm31->Administrative console

2. Set the Primary Administrative User Name
a. Expand the Security section in the tasks list, and select Secure
administration, applications, and infrastructure.
b. In the User account repository section of the Secure
administration, applications, and infrastructure panel, click the
Configure button.
c. The Secure administration, applications, and infrastructure page
opens. Enter the userid that is used for WebSphere server
administration in the Primary administrative user name field.
d. Click Apply.
e. On the Messages confirmation dialog, click Save to apply the
change to the master configuration.

3. Disable Java2 Security
a. Expand the Security section in the tasks list, then select Secure
administration, applications, and infrastructure.
b. In the Java 2 security section of the Secure administration,
applications, and infrastructure panel, make sure Use Java 2
security to restrict application access to local resources is not
selected.
c. Click Apply.
d. Click Save on the Messages confirmation panel.

4. Logout from the WebSphere Administrative Console.
5. Stop and restart the v6 Server.

3.8 Health Monitor support

In the following instructions:

<TBSM_DIR>
refers to the directory in which TBSM is installed (by default
the directory is c:\Program Files\Tivoli\tbsm).

<FIXPACK3_DIR>
refers to the temporary directory into which the Fix Pack is
extracted.

3.8.1 Installing this support on the Health Monitor

3.8.1.1 On the Health Monitor server machine

Invoke the following script to update the WebSphere Application Server
service name that Health Monitor should monitor:

cd <TBSM_DIR>\bin

sh updatewasservicenameforhmon.ksh -s "IBMWAS61Service - tbsm31"

The [-s was_service_name] is optional. If provided, the Health Monitor
will be configured with the specified service name. If not provided, the
WebSphere Application Server service name will be searched for in the
following order:
1. IBMWAS61Service - tbsm31
2. IBMWAS5Service - server1

After updating the registry items, the Health Monitor service will be
restarted to retrieve the updated information.

The following error messages may occur when running
updatewasservicenameforhmon.ksh:

GTMHM0006E: Display name not found for service: %1
A service name parameter was specified for which there is no corresponding
service display name.
The service name provided is invalid. The user should verify he input a valid
service name for the -s option.

GTMHM0007E: Health Monitor configuration failed to update key: %1
The registry could not be updated. This is a system problem.

GTMHM0008I: %1 already configured to Health Monitor as a service.
The WAS service name is already configured. No changes were made to
Health Monitor.

3.9 Finished migration

The migration of the TBSM Console Server application from v5 to v6 is
complete. No further configuration of TBSM or WebSphere Application
Server is necessary. Now it's okay to start the TBSM Services and logon
to the Java Consoles, Web Consoles and Executive Dashboards.

3.10 Post Installation information

3.10.1 Failover

The upgraded failover scripts provide support for the v6 service names,
which were changed between v5 and v6. These scripts are compatible with
both v5 and v6 installations.

None of the commands, parameters, or instructions for using these
scripts have changed, as a result of Fix Pack 3.

For further information, see "Chapter 6, The Failover Process" in the
IBM Tivoli Business Systems Manager 3.1 Administrator's Guide.

3.10.2 Health Monitor

After running the updatewasservicenameforhmon.ksh command to update the
WebSphere Application Server service name (using the procedure described
in 3.8.1.1, "On the Health Monitor server machine"), the Health Monitor
will automatically be restarted and will operate as before.



None of the commands, parameters, or instructions for using the Health
Monitor have changed.

For further information, see 'Using the Health Monitor' in Chapter 4 of
the IBM Tivoli Business Systems Manager 3.1 Administrator's Guide.

3.10.3 Starting and Stopping WebSphere Application Server

The following information can be helpful if you use the command line to
start and stop the v6 server.

Important: The location of the batch files used to manage the WebSphere
Application Server (for example, startServer.bat and
stopServer.bat) has changed from the location that was used in v5.

In v5, these batch files were located in: c:\Program
Files\WebSphere\AppServer\bin.

In v6, these batch files are located under the profiles\tbsm31
directory: c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin

The batch files underneath the profiles directory establish the
environment and then invoke batch files by the same name in the
c:\Program Files\IBM\WebSphere\AppServer\bin directory.

This location change can cause problems if you are not careful. For
example, there is a startServer.bat file located here:

c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin\startServer.bat

and one located here:

c:\Program Files\IBM\WebSphere\AppServer\bin\startServer.bat

When invoking the v6 command line scripts, you must invoke the ones in
the profiles\tbsm31\bin directory and not the ones in the AppServer\bin
directory.

The menu items found in the Windows Start menu invoke the correct batch
files in the profiles\tbsm31\bin directory, so you can use those menu
items to manage the server, instead of using the command line.

For example using Start->All Programs->IBM WebSphere->Application Server
V6->Profiles->tbsm31->Start the server invokes the startServer.bat file
in the correct directory.

3.10.3.1 To start the v6 server:

1. Start->All Programs->IBM WebSphere->Application Server
V6->Profiles->tbsm31->Start the server

or

c:\Program
Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin\startServer.bat
server1

You may need to provide -username and -password arguments, depending on
your configuration. For example:

c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin\startServer.bat
server1 -username <username> -password <password>

3.10.3.2 Verification Steps:

1. Open the Windows Services view by selecting: Start->All
Programs->Administrative Tools- >Services
2. Verify that the IBM WebSphere Application Server v6 service is
running.
3. Start the TBSM Java Console and logon to the TBSM Console Server.

3.11 Problem determination

3.11.1 Log Files

3.11.1.1 Migration Log Files

Migration Log Files can be found here:

c:\TBSMProfileBackup\logs\WASPreMigrationSummary.log

c:\TBSMProfileBackup\logs\WASPostMigrationSummary.log

where c:\TBSMProfileBackup is the profile backup directory you
specified in Step 6 of 3.6, "Run the Migration wizard".

Additional migration information can be found here:

c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\logs

3.11.1.2 TBSM Console Server Log Files

WebSphere Application Server v6 moved the application log files
underneath the individual profile directories. The TBSM Console Server
application log files are now located here: c:\Program
Files\IBM\WebSphere\AppServer\profiles\tbsm31\logs\TBSMServer1.log



3.11.2 Known Problems and Workarounds

3.11.2.1 Service does not stop if userid in soap.client.props file

Problem In some instances, the service will not start or stop if you
have specified the userid in the soap.client.props file.

Workaround
Use the command line startServer.bat and stopServer.bat
commands and provide the userid and password using the
-username and -password arguments on the command line.

3.12 Command line alternatives to the v6 Migration wizard

The v6 Migration wizard (described in 3.6, "Run the Migration wizard")
is the recommended tool for migrating from v5 to v6. However, if you
prefer to do the migration manually, v6 provides the WASPreUpgrade and
WASPostUpgrade commands.

These commands should be run on the TBSM Console Server machine.



Important: Ensure you call the versions of these commands that are
located in the profiles\tbsm31\bin directory.

3.12.1 WASPreUpgrade

This command backs up all of the v5 files and configuration. The syntax
of WASPreUpgrade is:

WASPreUpgrade.bat backupDirectory
currentWebSphereDirectory
[-traceString trace_spec [-traceFile file_name ]]


For TBSM, invoke it as follows:

cd 'c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin'

WASPreUpgrade.bat c:\TBSMProfileBackup c:\PROGRA~1\WebSphere\AppServer

If you receive an error

This command may take several minutes to complete. When finished, you
should see the following message:

MIGR0420I: The first step of migration completed successfully.

For further information on this command, see:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.base.doc/info/aes/ae/rmig_WASPreUpgrade.html

3.12.2 WASPostUpgrade

This command reads the backup created by the WASPreUpgrade command and
migrates the files and configuration to v6. It must be invoked after
successful completion of the WASPreUpgrade command. The syntax of
WASPostUpgrade is:

WASPostUpgrade.bat backupDirectory
[-oldProfile profile_name]
[-profileName profile_name]
[-scriptCompatibility true | false]
[-portBlock port_starting_number]
[-backupConfig true | false]
[-replacePorts true | false]
[-includeApps true | false | script]
[-keepAppDirectory true | false]
[-appInstallDirectory user_specified_directory]
[-traceString trace_spec [-traceFile file_name]]

For TBSM, invoke it as follows:

cd "c:\Program Files\IBM\WebSphere\AppServer\profiles\tbsm31\bin"

WASPostUpgrade.bat c:\TBSMProfileBackup -profileName tbsm31 -replacePorts true

This command may take several minutes to complete. When finished, you
should see the following message:

MIGR0271W: Migration completed successfully, with one or more warnings.

The warnings may be safely ignored.

For further information on this command, see:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.base.doc/info/aes/ae/rmig_WASPostUpgrade.html

4.0 Upgrading to SQL Server 2005 Enterprise Edition

Note: If you are running on Windows 2000, do NOT use Terminal Services
to remotely access the machine where the upgrade will be done. You
can use VNC (Virtual Network Computing) to remotely access the
machine.

Do the upgrade steps that are described in this chapter on the TBSM 3.1
Database Server and on the TBSM 3.1 History Server.

4.1 Prerequisites

* TBSM 3.1 at Fix Pack 2 or higher
* SQL Server 2000 Enterprise Edition

4.2 How to upgrade to SQL Server 2005

1. Ensure that all TBSM services are stopped.
2. The first panel that opens when installing SQL Server 2005 Enterprise
Edition is the End User License Agreement. If you accept the terms of
the license agreement, select I accept the licensing terms and
conditions and click Next.
3. The Microsoft SQL Server 2005 Setup panel lists the Microsoft
prerequisites. Click Install to install these prerequisites. After
the prerequisites are installed, click Next to continue.
4. When the Welcome to Microsoft SQL Server Installation Wizard opens,
click Next.
5. For System Configuration Check, make sure there are no error
messages. If you get a warning message about Microsoft Internet
Information Services (IIS), you can ignore the warning. Click Next.
6. Fill in pertinent information in the Registration Information panel.
Click Next.
7. In the Components to Install panel, select SQL Server Database
Services and Workstation Components, Books Online & Development
Tools. Click Next.
8. In the Instance name panel, keep the Default Instance selection.
Click Next.
9. In Existing Components panel, select SQL Server Database Services
8.xx.xxxx. Click Next.
10. In the Upgrade Logon Information panel, select SQL Server
Authentication Mode and enter the database userid and password. Click
Next.
11. On the Service Account panel, enter the username and password of
the domain for the system. Keep the default values for other items on
the panel. Click Next.
12. Click Next in the Error and Usage Report Setting panel.
13. Review the information on the Ready to Install panel, and then click
Install.
14. Once the Setup Progress panel completes with no errors, click Next.
15. Click Finish on the Completing Microsoft Sequel Server screen.

4.2.1 Apply Service Pack 2 for SQL Server 2005

Before proceeding to the next section, download and apply the latest
service pack (SP2) for SQL Server 2005 from the Microsoft Web site.

4.2.2 Reboot the system

Once the installation of Service Pack 2 is complete, reboot the system.

4.3 SQL 2005 Post-upgrade Steps

Ensure that the MSSQLSERVER service is running before proceeding to the
next section.

4.3.1 Apply the upgrade file for SQL 2005 on the Database server

Using the applyupgrade.ksh tool, run the upgrade file
3102tivbsmfp0003_2005.upg that is located in <TBSMInstallDir>/sql
directory, and make sure it finishes successfully with no errors.

1. At the command prompt, change the directory to: <TBSMInstallDir>\sql
2. Run the following command on the Database server:
sh ./ApplyUpgrade 3102tivbsmfp0003_2005.upg

4.3.2 Apply the upgrade file for SQL 2005 on the History server

Using the applyupgrade.ksh tool, run the upgrade file
3102tivbsmfp0003_2005.upg that is located in <TBSMInstallDir>/sql
directory, and make sure it finishes successfully with no errors.

1. At the command prompt, change the directory to: <TBSMInstallDir>\sql
2. Run the following command on the History server:
sh ./ApplyUpgrade -S <HistoryServerName> -U <database_username> -P
<database_password> 3102tivbsmfp0003_2005.upg

4.3.3 Upgrade job steps that use tokens in SQL Server 2005

Use of the TBSM product with Microsoft SQL Server 2005 is possible only
for users that have separately implemented details offered from the
Microsoft Knowledge Base article KB915845, which is offered from the
Microsoft support website.

The Microsoft product is licensed to you by its owner and not by IBM. It
is your responsibility to determine whether the license terms offered by
the product's owner are acceptable to you. YOUR USE OF THE MICROSOFT
PRODUCT AND ANY URL'S OR MATERIALS ON THIRD PARTY WEBSITES ("THIRD PARTY
MATERIALS") IS "AS IS", WITHOUT WARRANTY FROM IBM OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. TO THE EXTENT PERMITTED
BY LAW, IBM DISCLAIMS ALL LIABILITY FOR ANY CLAIMS ARISING OUT OF USE OF
THE THIRD PARTY MATERIALS.

4.3.3.1 Upgrade steps:

1. Stop SQL Server Agent (if running).
2. Open SQL Server Management Studio by going to All programs ->
Microsoft SQL Server 2005 -> SQL Server Management Studio, and then
connect to the server.
3. Click New Query located in the upper left corner of the screen.
4. Copy the SQL code in the Resolution section of the Microsoft
Knowledge Base article KB915845
(http://support.microsoft.com/kb/915845/) to the Query window in the
SQL Server Management Studio. Execute the SQL code to create the
stored procedure called sp_AddEscapeNoneToJobStepTokens.
5. Run the stored procedure sp_AddEscapeNoneToJobStepTokens on msdb
database by executing the following SQL in a new query window:
USE msdb
GO
EXEC sp_AddEscapeNoneToJobStepTokens
GO

6. Start SQL Server Agent

4.3.4 Check database integrity

Execute the following SQL to check the database for column values that
are not valid or that are out of range:

USE Object
GO
DBCC CHECKDB WITH DATA_PURITY
GO

Note: When executing this step, you might (in some cases) encounter one
of the following errors:
*
Msg 2511, Level 16, State 2, Line 1
Table error: Object ID 991811091, index ID 1, partition ID 346474308370432, alloc
unit ID 346474308370432 (type In-row data). Keys out of order on page (1:24563),
slots 14 and 15.

The error suggests that there is some allocation problem with
[index ID 1] in table [Object ID 991811091]. It can be fixed by
running DBCC DBREINDEX (that rebuilds the index) command on the
mentioned table index.

In the following example, substitute '<TableID> and <IndexID>
accordingly. In the error message above, <TableID> is 991811091
and <IndexID> is 1.

DECLARE @tblname NVARCHAR(64), @indname NVARCHAR(64)
SELECT @tblname = OBJECT_NAME(<TableID>)
SELECT @indname = name FROM sysindexes WHERE id = <TableID> AND
indid = <IndexID>
DBCC DBREINDEX(@tblname, @indname)

Remember to repeat this process for all similar errors, and
then re-run DBCC CHECKDB to check the validity of the column
values.

*
Msg 2508, Level 16, State 3, Line 2 The In-row data RSVD page count for
object "dynamic_object_create_path_detail", index ID 0, partition ID 100889916211200,
alloc unit ID 100889916211200 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
There are 3874 rows in 27 pages for object "dynamic_object_create_path_detail".
CHECKDB found 0 allocation errors and 1 consistency errors in table
'dynamic_object_create_path_detail' (object ID 1539457950).

This error can be fixed by running DBCC UPDATEUSAGE. For the
table in the example above, it would be run as follows:

DBCC UPDATEUSAGE ('Object', 'dynamic_object_create_path_detail')

Remember to repeat this process for all similar errors, and
then re-run DBCC CHECKDB to check the validity of the column
values.

4.3.5 Disabling Selected SQL Server 2005 Management Studio Options

Certain SQL Server 2005 Management Studio options must be manually
disabled for every Windows account that is used to run queries.

To disable these options, do the following steps:
1. Start the SQL Server 2005 Management Studio. Click Start -> All
Programs -> Microsoft SQL Server 2005 -> SQL Server Management
Studio.
2. From the SQL Server Management Studio window, click Tools -> Options.
Expand Query Execution, then expand SQL Server, and click Advanced.
3. Make sure the only check box selected is SET ARITHABORT. Clear the
SET CONCAT_NULL_YIELDS_NULL check box.
4. Click ANSI.
5. Clear all check boxes. Click OK.
6. Close SQL Server Management Studio.

4.3.6 Detach and attach databases

Note: This section applies to the database server only.

1. Ensure that the SQLSERVERAGENT and TBSM services are stopped before
detaching and attaching the databases.
2. To detach the databases, run:
detachdatabases.sql

located in <TBSMInstallDir/sql
3. To attach the databases, run:
attachdatabases.sql

located in <TBSMInstallDir/sql
4. Start the SQLSERVERAGENT and TBSM services.

4.3.7 Update statistics

Note: This section applies to the database server only.

The statistics of the database should be updated after migration:
* Run the Update Object Stats SQL job.

4.4 Tivoli Business Systems Manager Failover

The TBSM 3.1 failover scripts and stored procedures have been modified
to handle SQL Server 2005 changes. If you migrate to the SQL Server
2005, a new failover configuration is required even if the server roles
are unchanged. During failover configuration, the new stored procedures
are loaded into the SQL Server 2005 databases and the existing
procedures are updated. Options that are supported in the SQL
environment for the failover scripts remain the same.

If you apply Fix Pack 3 to TBSM 3.1 and continue in the SQL 2000 server
environment, it is not necessary to re-configure failover. Scripts and
stored procedures should continue to work as usual.

Failover script options remain the same, but there are noticeable
differences in initializing the log shipping and failover execution.
These differences are described in the following tables.

Table 1. Log shipping job names
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| TBSM Log Shipping Transaction | TBSM Log Shipping LSBackup_<dbname> |
| Log Backup | |
| TBSM Log Shipping | |
| Backup/Restore History Purge | |
| TBSM Log Shipping History | |
| Purge | |
+-------------------------------+-------------------------------------+
| TBSM Log Shipping Copy Job | TBSM Log Shipping |
| TBSM Log Shipping Load Job | LSCopy_<primaryServer>_<dbname> |
| TBSM Log Shipping Out of Sync | TBSM Log Shipping |
| Check | LSRestore_<primaryServer>_<dbname> |
| TBSM Log Shipping | TBSM Log Shipping |
| Backup/Restore History Purge | LSAlert_<SecondaryServer> |
| TBSM Log Shipping History | |
| Purge | |
+-------------------------------+-------------------------------------+

Table 2. Alert messages
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| Use Message ID 90051 | Use Message ID 14420 for Primary |
| | back up |
| | Use Message ID 14421 for Secondary |
| | copy and restore |
+-------------------------------+-------------------------------------+

Table 3. Log shipping monitoring
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| log_ship_entity_log | msdb.dbo.log_shipping_monitor_secon |
| log_ship_status | dary |
| | msdb.dbo.log_shipping_monitor_prima |
| | ry |
| | msdb..log_shipping_monitor_error_de |
| | tail |
| | msdb..log_shipping_monitor_history_ |
| | detail |
+-------------------------------+-------------------------------------+

Table 4. Failover script changes
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| fo_tlfchk.ksh | fo_tlfchk.ksh |
| fo_status.ksh | fo_status.ksh |
| fo_cmd_execute.ksh | fo_cmd_execute.ksh |
| fo_logship.ksh | fo_logship.ksh |
| fo_failover.ksh | fo_failover.ksh |
| load_fo_env.ksh | load_fo_env.ksh |
| fo_config.ksh | fo_config.ksh |
+-------------------------------+-------------------------------------+

Table 5. Stored procedure changes
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| asisp_enabledisable_job.sql | asisp_enabledisable_job.sql |
| asisp_disable_logship_jobs.sq | asisp_disable_logship_jobs.sql |
| l | |
+-------------------------------+-------------------------------------+

Table 6. New stored procedures
+-------------------------------+-------------------------------------+
| SQL Server 2000 | SQL Server 2005 |
+-------------------------------+-------------------------------------+
| | tbsm_logship_init_db.sql |
| | tbsm_logship_init.sql |
| | tbsm_logship_cleanup.sql |
| | tbsm_logship_cleanup_db.sql |
+-------------------------------+-------------------------------------+

4.4.1 Considerations for Failover

* Perform detachdatabases.sql and attachdatabases.sql before
configuring Failover. You should not issue these SQL commands after
log shipping has been initialized.
* The option to abort log shipping aborts log shipping on the database
server and the history server. If necessary, use the following SQL
command to bring the database out of read-only mode.
RESTORE DATABASE <databaseNname> WITH RECOVERY
EXEC master.dbo.sp_dboption <databaseNname>, 'trunc. log', 'true'

* Undo files that show up in the Secondary server logshipbackup
directory should not be manually deleted. These Undo files will be
removed automatically after the first log restore.
* Do Refresh before you check things in the SQL Server Management
Studio. The state of a database object is in constant change. They
will not be auto refreshed in your SQL Server Management Studio.
* Check both the SQL error log and the system Event Viewer log for
clues.
* The Alert job is running on the Secondary server. If the SQL Server
Agent on the Secondary server is not running, the alert message will
not be generated even if the two databases are out of synch.
* Windows Messenger service needs to be running for the Alert message
to be emitted.
* If the log(trn) file is missing or corrupted, you will see a message
similar to the following in the restore job log.
Message

2007-08-20 10:40:09.62 *** Error: The file 'D:\logshipbackup\Object\Object_20070820134510.trn'
is too recent to apply to the secondary database 'Object'.(Microsoft.SqlServer.Management.LogShipping) ***

2007-08-20 10:40:09.62 *** Error: The log in this backup set begins at LSN 23372000000004200001,
which is too recent to apply to the database. An earlier log backup that includes
LSN 23368000000006900001 can be restored.

RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***

2007-08-20 10:40:09.70 Searching for an older log backup file. Secondary Database: 'Object'

* You can either run the fo_tlfchk.ksh script to attempt to recover the
file, or manually examine and compare the logshipbackup directories
on the primary and the secondary servers and manually copy the
missing or corrupted file. If the copying attempt fails, then you
should reinitialize the log shipping.
* The disconnect_user option is enabled while setting up the restore
job on the secondary server. Connecting to the database in the SQL
Server Management Studio does not prevent the restore job from
completing successfully.
* You will get an error messages if you try to access the database
while the restore job is running. When you try the operation again at
a later time, the issue should be resolved.



Appendix A. APARs included in 3.1.0-TIV-BSM-FP0003

Fix Pack 3 incudes fixes for the following APARs:

OA15196 THE COMMAND BACKUPALLDATABASES DOES NOT BACKUP THE DATABASES

The msdb database is a system related database. TBSM does not
require msdb to be backed up/restored when
BackupAllDatabases/RestoreAllDatabases commands are run. You
can ignore the fact that the msdb backup is not created and
also ignore the message stating that the msdb could not be
restored at restore time.

TBSM maintains a default job copy of the TBSM added jobs within
tables in the Object database. Initially those tables have only
those jobs added by TBSM and not the jobs that the user might
have added or changed by using the SQL Server Enterprise
Manager. The default job list is updated automatically with the
latest information that is contained in the msdb database if a
customer detaches the database using the detachdatabases
procedure. The new default job list will be used the next time
the Object database is loaded into the system and the msdb is
re-populated. This mean that if you do not maintain a proper
backup of the msdb database, TBSM will restore (at a minimum) a
default job list that will allow it to run.

If you want to ensure that all of the information contained
within the msdb database is restored, make sure you have a
valid backup copy and that you restore the backup copy using
the methods outlined by Microsoft for such databases. The TBSM
software restores the minimum default level, which could be
that of initial install (plus TBSM added jobs).


OA15386 DATE COLUMN IN EVENTVIEWER NEEDS TO SHOW TIMEZONES INFORMATION

The fix for this APAR causes the database server event creation
time to display in the event viewer.


OA16190 GTM_C10_S020_PROCESS_RESOURCES_STAGING FAILING

The GTM_c10_s020_Process_Resources_Staging step fails with the
message:

= Unaltered SQL Stmt : "UPDATE GTM.stg_UPDATEattr SET twh_comp_id=
(SELECT r.comp_id FROM GTM.resourcer
WHERE r.cid = twh_cid AND r.id = twh_id)"
CDWEX8087E A general SQL error occurred: SQL_ERROR: 'ExecDirect'
2006.04.12 12:12:17.762 sqlState = 21000,
nativeErr = -811, errorMsg = [IBM][CLI Driver][DB2/NT] SQL0811N
The result of a scalar fullselect,
SELECT INTO statement, or VALUES INTO statement is more than one row.
SQLSTATE=21000.I h


OA16261 STEP GTM_M10_S030_LOAD_EVENT_STAGING FAILING WITH ERROR

The GTM_m10_s030_Load_Event_Staging step of the ETL processed
failed with a duplicate key insert error.


OA16400, OA16400.1
HEALTHMONITOR AND CL_HEALTHMONITOR DO NOT ALERT IF THERE ARE
MANY TRSTATE=2 IN CL_STAGE TABLE.

HealthMonitor and CL_HealthMonitor do not alert the user if
there are many trState=2 records queued up in the CL_stage
table.

Added a new column called Received Pending in the HealthMonitor
that alerts the user if the trState=2 records queue up beyond a
certain limit.


OA16493 OPTIMIZE PERFORMANCE OF ASISP_UPDATEOBJPATHCACHE JOB

The process to update the ObjPathCache was changed so that
resource path changes are processed once, and not re-evaluated
later in the same step.


OA16545 THE FLAG FOR MESSAGE AOF571I_SOFTDOWN CONTAINS INCORRECT FLAG

The flag for the message AOF571I_SOFTDOWN contains
AutomationStarted on instead of AutomationME off. This needs to
be updated via the MESSAGE_DESCRIPTION sqi.


0A16585 ERROR MESSAGE RECORDBATCHCURRENTSTATECHANGE TOO MANY ARGUMENTS
SPECIFIED

OA16685 GTM_C10_S060_PROCESS_REPORT_RESOURCES_STAGING FAILS

Number of failures during ETL step execution


OA16721 GTM_M10_S030_LOAD_EVENT_STAGING ENDING IN ERROR BECAUSE OF
DUPLICATE VALUES IN A CDW TABLE

OA16736 ERROR "GTMCI0005E EXCEPTION DATA: NO SUITABLE DRIVER"

Execution of the defineplacementrule.ksh script is failing with
the following resulting errors:
* GTMDC0010E Error accessing the TBSM database.
* GTMCI0005E Exception data: No suitable driver
* GTMCI0002I Command processing completed.

The command being executed is: sh defineplacementrule -S abc -U
tbsm -P xyz display -A


OA16853 DIST TBSM NOT HANDLING HSM CONSOLE MESSAGES CORRECTLY. ERROR =
'UNHANDLED EVENT HAS EXPIRED'

OA16939 IMPROVE PERFORMANCE OF CLEANING UP OLD EXCEPTIONS

This fix addresses performance related issues around the clean
up of SQL tables holding event, exception, message, and alert
state history data that is no longer needed for system
operation.

The jobs in this fix are already steps within scheduled jobs
that were created in Tivoli Business Systems Manager Version
3.1. As long as the cleanup jobs are already running enabled,
your installation will immediately begin using these new clean
up procedures.

To help with the Cleanup Event Viewer Tables job, an option was
added that truncates the table rather than deleting anything
older than a specific number of minutes. When deleting on
minutes, a delete is done on the table and this can be slow if
the table is large.

A new truncation option is enabled by modifying the job step
to, "EXEC asisp_cleanupEvtViewResultSets @trunc=1" and to
change the schedule to run the job every couple of hours,
rather than every 15 minutes.

The default is to continue to execute the job as it is done
today.


OA16976 WHEN A LOB IS CREATED USING THE IS NULL PATTERN AND THE ABS

OA17004 UNABLE TO EXTRACT THE DATE FROM THE EXPORT FILE USING
IMPORTLOBFROMXML

OA17067 TBSM DLA SUPPORT

OA17109 PROBLEM TICKET CREATION FAILS FOR TEC EV WITH EXT ATTRIBUTE

OA17165 The Staged Event Loader halted because it lost connection with
the SQL Server database.

OA17298 DUPLICATE CHEV EVENTS SHOWING IN THE REPORTING SYSTEM AND IN
TWH_MART WHEN SHORTCUTS EXIST

OA17340 ERROR IN THE ETL PROCESS THAT CAUSES SOME PATHS NOT TO BE
INSERTED INTO THE GTM.D_COMP_PATH TABLE

OA17346 TBSM INTERFACE WITH OMEGAMON 3.5 INCORRECT

OA17613 STATUS EVENTS NOT SENT TO TEC FROM TBSM

OA17871 DCR 239: TBSM 3.1 ON WAS 6.X

Adding support for TBSM 3.1 Fix Pack 2 to run on WAS 6.x.


OA17898 COLUMN INSTRID MISSING FROM THE CL_IDCACHE TABLE AFTER
INSTALLING FIXPACK 2

OA17913 MESSAGE GTM7911D DOES NOT UPDATE STATUS OF TBSM OMEGAMON
CONNECTION.

OA18037 ACK EVENTS FROM TEC TO TBSM DO NOT GET CORRECTLY PROCESSED




OA18072 TEC EVENTS NOT FORWARDED TO TBSM FOLLOWING NEW .RUL FILE LOADED

OA18094 MSSQL OBJECTS EXPORTED FROM TADDM NOT MAPPED IN TBSM

OA18104 STATUS, VIA EVENTS PROPAGATING IN UI INCORRECTLY

OA18170 NULLS VALUES RECEIVED INTO THE GEM_APMGENERICMSGS TABLE

OA18221 DATA NOT PROPERLY BEING DELETED FROM THE 'EVENT' TABLE CAUSING
THE OBJECT DATABASE TO KEEP GROWING

OA18234 TBSM CONSOLE NOT ACCESSIBLE, SQL ERRORS IN ERRORLOG

OA18248 MODULE GTMEDITB USING VARIABLE FIELD2 IN LOGIC AND DATATYPE

OA18290 ABS DISCOVERY PROCESS JOB PERFORMANCE TOO SLOW DURING FLOOD OF
NEW RESOURCES

The fix is to add a new column to the Pattern configuration and
allow the customer to identify Patterns that should not be
included in the ABS evaluation when resources are discovered
with that Pattern. This solves this problem because the NODEs
will be marked as "no evaluation" and avoid the performance
problem. There is no effect on processing of other resources or
patterns. The ABS configuration header will be upgraded to 1.4
to include the new column. The new column name is PatternUsage
in the Pattern section. It follows the Operand2 column.

The default behavior is to function as today. The user is
responsible to set the flag NOLOB in the PatternUsage to
indicate no evaluation. This gives the user the flexibility to
have different Patterns for a class. For example, some users
could have a Pattern for NODE with name LIKE"%test%" that does
not result in a Business System, and a Pattern for NODE with
name LIKE "%production%" that does result in a Business System.
The user would specify NOLOB in the Pattern for NODE with name
LIKE "%test%".

The user can use the NOLOB filter on any intermediate pattern
in the CriteriaToPattern set. For example, if there is a
CriteriaToPattern that relates G02R to NTSR to NLOC, there is
no need to process the NTSR. All the objects have to exist
before the CriteriaToPattern will be satisfied. In this
example, the G02R object must exist (which is a leaf node)
before the pattern evaluations are complete.


OA18323 EVENTS CLOSED IN TBSM, NOT REFLECTED IN TEC

OA18429 MAKE ATRULEUTILITY.KSH SCRIPT WORK WITH THE NOTE_OWNER

The default behavior is to allow the note_owner to be a label.

To require the note_owner be an existing TBSM console operator,
execute the following from the SQL Server Query Analyzer:

exec _SetSystemConfiguration NULL, NULL, 'REQUEST_AUTOTICKET',
'REQUEST_NOTEOWNER_ALLOW_LABEL', 'FALSE', 'CHAR'


OA18437 SHIFT REPORT DOES NOT END AT THE 'BEGINNING DATE/TIME' AS
SUPPOSED

The Shift Turnover report does not end at the Beginning
Date/Time values specified in the Reporting System.


OA18550 AE OTHER FIX COMPLETION UNKNOWN COMMAND TYPE "SSQL" ON STEP
19108

OA18556 AE OTHER FIX COMPLETION FAILURE ON CALL TO
CL_CACHEGENERICPARENTS BECAUSE THE INSTRID COLUMN IS MISSING

OA18650 OBSOLETE EXCEPTIONS AND MESSAGES REMAIN IN THE DATABASE

OA18652 ABSTEST RUNNING MORE THAN 16 HOURS WITH TEMPDB GROWING TO 75 GB
LEADING TO PROPAGATION NOT OCCURRING ON THE JAVA CONSOLE

OA18672 DETAILS SEARCH PATTERN AND TEC EVENT SEARCH PATTERN FIELDS
STANDARD SQL AND WILDCARD CHARACTERS (% AND *) NOT WORKING FINE

OA18675 AE OA18674 FIX COMPLETION BATCH MANAGEMENT SUMMARY VIEW NOT
AVAILABLE ANYMORE AFTER FIXPACK 2 INSTALLATION

OA18802 RODM REGISTRATION DOES NOT WORK AFTER FIX PACK 2

OA18822 THE DELETION OF BUSINESS SYSTEMS USING XML IS NOT WORKING
CORRECTLY

OA18843 NETVIEW EVENTS VIA TEC TO TBSM RECEIVE PRIMARY KEY VIOLATION

OA18874 OLD EVENTS ARE NOT CORRECTLY CLEARED IF HISTORY SERVER IS NOT
CONFIGURED

OA18917 EE CORES WHILE PROCESSING EVENTS

OA18932 CHANGE FILE PERMISIONS FOR THE TBSM FILES LOCATED IN THE
/TDS/EVENTSERVICE/CONFIG AND /TDS/EVENTSERVICE/DB SUBDIRS

OA19098 ABSTEST.KSH SCRIPT REPORTS TO ENQUEUE AN INCORRECT NUMBER OF
BUSINESS OBJECTS

OA19122 PATTERNUSAGE VALUES INCSO/NOLOB NOT RESULTING IN THE LOADED
CONFIGURATION OUTPUT

OA19183 NETVIEW ADAPTER & COMMON LISTENER OUT OF SYNC

Error messages will show up in the CommonListener logs that
indicate a problem. Possibilities include messages like:

ERROR: Unable to get registration records: null

or

ERROR: Unregistered SID:


OA19249 ERROR: 'INVALID OBJECT NAME 'EVCONTAINER_S' WITHIN TBSMSERVER
.LOG

An error shows up in the ConsoleServer log when an Admin logs
into the Java Console and opens the Executive Dashboard list
for the first time.


OA19329 EXTENDED ATTRIBUTES ARE LOST WHEN A DUPLICATE EVENT OF AN
EXISTING ONE IS UPDATED WITH -E PARAMETER

When sending events with the extended length TEC slot
attributes and an update is sent to the same event to update
some of the slots, the extended length attribute disappears
from the console.


OA19492 EIF SENDER DO NOT ENCLOSE IN QUOTES THE VALUE OF SLOT PROBE

Status event changes sent from TBSM to TEC fail with parsing
errors when the probe name contains a space character.


OA19681 SUPPORT FOR HP OPENVIEW V7

OA19805 NON-EXPIRED 'NAME' ATTRIBUTE IN THE TWG.COMPATTR TABLE

After applying 3.1.0.2-TIV-BSM-LA0185, the
GTM_m10_s010_Load_Resources_Staging step fails with the
following error message:

CDWEX8087E A general SQL error occurred:

SQL_ERROR: 'ExecDirect'


OA19911 HIERARCHICAL RESOURCE REPORTS

The Business System Resource Tree report displays the resources
in random order. The display should resemble the LOB tree
display.


OA19918 STAGEDEEVT TABLE NOT CLEARED

The StagedEEVT table is not cleared down after events are
processed.


OA19932 INVALID COLUMN NAME 'EXTENDED_ATTR

Certain reports do not work for customers who have single
server reporting system/database server setups (i.e. no history
server).


OA19955 EVENTS COMING FROM TEC ARE NOT CLOSED IF PREVIOUSLY SENT EVENTS
OPEN AND ACK ARRIVED

Two issues:
1. Sending a CLOSE event after an ACK event does not close the
ownership note for customers who have it setup to clear
alerts on ownership.
2. If an OPEN and ACK for the same event on the same resource
are processed in the same SEL batch, in the event viewer the
event is taken ownership of but the count is 2 when it
should only be 1 (the ownership event should not be
counted).


OA20015 TBSM 3.1 DISPLAY AND EVALUATE TEC EVENT DATE SLOT

Additional Documentation :

By default, the 'Enhanced Event Timestamp Support' function is
not enabled. The 2 primary functions for the timestamp are
optionally controlled through the following TBSM database table
SystemConfiguration settings:

EVALUATE_ORIGINATION_DATE
Users have the option of transforming the string form
of the localized event origination timestamps through
a user defined database stored procedure:
al_processEventTimestamp_custom.sql. The localized
timestamps from the various monitors could be
transformed to an epoch time that is consumable by
TBSM and can be used to represent the event as its
Date attribute, in place of the event reception time.
See the comments and samples in
al_processEventTimestamp_custom.sqlfor information on
how to customize the transformation of event
origination timestamps.

By default, the customer defined database stored
procedure, al_processEventTimestamp_custom.sql, used
for transforming localized event origination
timestamps, will not be called so that customers not
intending to use this function will not be impacted. A
database system configuration property will need to be
updated in order for the procedure for transforming
localized timestamps to be called. Property
EVALUATE_ORIGINATION_DATE in TBSM database table
SystemConfiguration must be set to '1' to enable the
function.

Customers will need to become familiar with the
different formats of the localized timestamp in events
that are being forwarded to TBSM from the various
agents and monitors. It is possible the format of an
event's timestamp may be different from operating
system to operating system and from machine to
machine.

Note: Before setting property
EVALUATE_ORIGINATION_DATE in TBSM database table
SystemConfiguration to '1', customers should
carefully consider whether custom code for
adjusting event timestamps, in
al_processEventTimestamp_custom.sql, is required
to accommodate time zone offsets and/or seasonal
time changes. Without adjusting event timestamps
for time zone offsets, an event's date attribute
will reflect a GMT time, since the string form
of localized event origination timestamp is not
relative to any particular time zone and does
not contain time zone offset information.


DISPLAY_ORIGINATION_DATE
By default, the new Origination date field will not
be displayed on the Event Details dialog to avoid
operator confusion between the existing Date field and
the new Origination date field. The
propertyDISPLAY_ORIGINATION_DATE in the TBSM database
table SystemConfiguration must be set to 1 to enable
displaying the new Origination date field. Using the
transformation function is not required to simply
display the raw string form of the localized event
origination timestamp.


OA20110 UNABLE TO LAUNCH OPERATIONAL TASK FROM BUSINESS SYSTEM

When the customer tries to launch an operational task, which is
a URL, from a LOB resource in the 'Resources in Maintenance'
View, where the URL contains the INSTANCEID of the resource,
the INSTANCEID does not get substituted with the actual value
in the first attempt of the launch but it gets substituted in
the second attempt.


OA20235 Failover scripts fail after FP2

After FP2, failover scripts fail in the following environment,
with 3 different ids in play:
1. User logged into the system to run the failover scripts is a
Windows Admin (no SQL authority)
2. The MSSQLServer and SQLServerAgent services run under an id
that is a Windows and SQL Admin
3. The SQL "sa" user is different than the above two ids, and
the SQL jobs run under this id

Also, the SQL jobs may not run after a failover has been
completed, even though they are 'enabled.'


OA20368 TBSM DOES NOT APPEAR TO ESCAPE THE # CHARACTER WHEN EXPANDING
ATTRIBUTE VARIABLES FOR URL LAUNCH

While using launch in context via the URL, if the customer
passes an attribute in the launch URL which contains the
character '#', TBSM truncates the # character and all the
information after the #.


OA20372 IHSTDMAI SHOULD NOT CRASH

The Event Enablement service terminates when data from a port
scanning tool is received.


OA20389 VIEW KCP:KCP_NAVIGATOR_1000 APPEARING IN TBSM BUSINESS VIEWS

Business View discovery for TEP Feed, discovers KCP:Navigator
view and creates a Business System for this view.


OA20501 SOME EVENTS ARE NOT SENT TO THE TBSM HISTORY DATABASE AND SO DO
NOT SHOW UP ON THE REPORTS

Some events which are in the event table in the database on the
Primary database server do not show up in the eventhist table
on the History server.


OA20623 PERFORMANCE TO MANAGE SINGLETONS EVENTS IN STAGEDEXCP TABLE
SHOULD BE IMPROVED

The Staged Event Loader runs slowly, on occasion. This
coincides with a large number of up/down singleton events
having been received by TBSM.

Processing of up/down singletons are a problem for the Staged
Event Loader, because asisp_processStagedEXCPs only processes
one of these at a time per resource, per iteration. Therefore
it can take a large number of calls to asisp_processStagedEXCPs
to process all events. This is outlined in the document Protect
TBSM against overflow of events coming from unstable resources
from the support web site.

The fix here does not reduce the number of iterations required
by asisp_processStagedEXCPs. But it improves the performance of
each iteration. Thus the overall process will be quicker. It is
still important to follow the instructions on the document
Protect TBSM against overflow of events coming from unstable
resources.


OA20632 REPORTS NOT VIEWABLE IN .TXT FORMAT

When the customer logs into the reporting system by using the
URL and launches a report using the various formats, all the
reports, except for the text report, get displayed in the right
hand frame of the browser window.


OA20684 THE MAKEMVSCOMPONENTS ON WINDOWS OS, IN CHINESE LANGUAGE,
DOESN'T WORK

When Chinese Windows OS is installed, the MakeMVSComponents.ksh
script does not generate the MVSIPSender service.

The -r (remove) option deletes the services and associated
registry entries.

It has been observed on a Chinese OS that the reg delete
command, run by the script, displays 'ERROR' in English, even
though the command is successful. An example of this is below.
This can be ignored as the command is successful.

Deleting registry entry for [ASIMVSIPOSListenerSvc-OMO6]...
\schinese2003\HKEY_LOCAL_MACHINE\SOFTWARE\Accessible Software,
Inc.\Access1\1.0\Components\ASIMVSIPOSListenerSvc\Instances\OMO6
xxxxxxx ERROR: xxxxxxx


OA20709 AN UPDATE FOR THE EVENTS JOB FAILING. THE UPDATE INDICATES
EVENT THOUGH THE JOB SHOWS FAILED, IT WAS ACTUALLY SUCCESSFUL.

The job Tep Receive Events

<soap server> <alias> reports as Failed, when 0 events are
returned from ITM.


OA20786 OPCLOAD DATABASE GROWING

There is no cleanup mechanism for the tables in the OPCLoad
database, and the database has grown very large for the
customer over the years.


OA20950 REPORT DISPLAYS THE LOB THAT THE REPORT WAS RUN OFF OF TWICE
WHEN YOU CHOOSE TO INCLUDE THE CHILDREN IN THE REPORT

The customer is seeing a resource in the Business System
Availability report that should not be included in the report.
Not only that, the resource shows up with the path of one of
the other resources included in the report.


OA20951 EXCEPTIONS WITH UNKNOWN ALERTSTATE/PRIORITIES ARE NEVER REMOVED

Exceptions with an AlertState of 0 (Unknown) and a Priority of
0 (Unknown) are never cleared from the database by the Delete
Old Exceptions job.


OA21208 WORKSPACES CASE DIFFERENCE BETWEEN _LONG_NAME AND _DATA COLUMN
IN CLOB_C TABLE CAN CAUSE UNEXPECTED RESULTS

Changes to a workspace name or user name cannot be saved.


OA21375 TBSM 3.1 SUPPORT FOR WINDOWS SERVER 2003 SERVICE PACK 2

SQL table files generated are not formatted correctly after the
installation of SP2 for Windows Server 2003.


OA21742 SOME TABLES NOT BEING MAINTAINED BY CLEANUP JOBS

Some tables in the Object database are not being maintained -
DeletedNote_C, ObjectStateHist, Acc1MsgInstance_C and
Acc1MsgInstance_A. These tables can grow large over time.


OA21811 APAR CREATION REGARDING RE-WRITE OF THE TBSM SAMPLE RULES FOR
THE TEC SERVER

OA21821 IF0012 FOR EE CAUSES EE TO HANG WHEN SENDING EVENTS TO TBSM

OA22288 MAINTENANCE VIEW RESOURCES WEREN'T CLEANUP DURING PHYSICAL
DELETION

If a resource is deleted when in Maintenance mode, it does not
get cleaned up from the MaintTrueState table, which causes it
to continue being displayed in a Managed Resources view.


OA22305 GTM_C10_S060_PROCESS_REPORT_RESOURCES_STAGING FAILS

GTM_c10_s060_Process_Report_Resources_Staging fails with the
following error:



Unaltered SQL Stmt : "update gtm.stg_new_comp as nc set
nc.stg_tcomp_id = ( select t.comp_id from twg.comp t where
t.comp_corr_val = nc.STG_TCOMPC_VAL) where nc.stg_tcomp_id is null"
CDWEX8087E A general SQL error occurred: SQL_ERROR:
'ExecDirect' 2007.07.17 00:21:35.706
sqlState = 21000, nativeErr = -811, errorMsg = [IBM]
CLI Driver][DB2/6000] SQL0811N


OA22410 GTM_M10_S020_PROCESS_RESOURCES_STAGING FAILS

GTM_c10_s020_Process_Resources_Staging fails with an error,
which in part is as follows:



Unaltered SQL Stmt : "insert into gtm.d_lob_link select
stg_src_tcomp_id, stg_dst_comp_id, 'gtm_lb', stg_reln_stdt,
SQL0530N


OA22418 SQL JOBS, SCHEDULES, ETC WERE NOT REPLICATED IN THE SECONDARY

OA22455 COMMON LISTENER ERROR: VIOLATION OF PRIMARY KEY CONSTRAINT
'PK__STAGEDEEVT__29833E99

OA22478 JOB 'ABS DISCOVERY' RUNNING FOR A LONG TIME




OA22602 URL IN THE MESSAGE SLOT OF A TBSM EVENT VIA TEC

Capability to launch URLs that appear in the description column
of the Web Console Event View.

In order to enable this function, you must update the TBSM
Database and the TBSM Console Server. This fix will only be
available after it has been manually enabled by the Customer
entering the following command into Query Analyzer: insert into
SystemConfiguration values ('Feature',
'WCDisplayURLHyperlinksInDescription', 1, 'INT') This fix can,
at any time, be disabled by running the following command, and
restarting the Console Server insert into SystemConfiguration
values ('Feature', 'WCDisplayURLHyperlinksInDescription', 0,
'INT') TBSM Console Server Update the ITBSMConsoleServer
application in WebSphere. Follow the steps below to do this on
the Tivoli Business Systems Manager Console Server: <LA> refers
to the directory where this Limited Availability fix resides
after you have extracted it from the tar file. <TivoliManager>
refers to the full path of the Tivoli Business Systems Manager
installation on the server. <was_path> refers to the full path
of where the WebSphere is installed. NOTE The Console Server
will be unavailable during the duration of the update.jacl
script. 1. Copy the gtmuiserver.ear file from this Limited
Availability fix to the <TivoliManager>\ConsoleServer
directory. 2. At the command prompt, change the directory to:
<TivoliManager>\ConsoleServer 3. Run the following command:
<was_user>\bin\wsadmin -f update.jacl -conntype SOAP -user
<was_user> -password <was_pw> Example: C:\Program
Files\Tivoli\tbsm\ConsoleServer> "C:\Program
Files\WebSphere\AppServer\bin\wsadmin" -f update.jacl -conntype
SOAP -user administrator -password pwd


OA22619 EVENTS NOT PROCESSED - ASISP_PROCESSSTAGEDTEPOUT

OA22630 UNABLE TO CLOSE CERTAIN SA390 ALERTS WITHIN TBSM

OA22660 WHEN CHANGING SOAP PASSWORD, GET ERROR 'COULD NOT FIND STORED
PROCEDURE 'TEP_SETUP_ADD_HDR'.'

Error Description: The query the customer can use to change the
soap uid/pwd is: EXEC tep_setup @action='PASSWORD',
@soap_server = 'crprchiisby', @soap_alias = 'DEV',
@soap_uid='op53029', @soap_pw='NEWPASSWORD' Obviously,
NEWPASSWORD should be changed to the password they want to set.
When running the above to change the password, you get the
following error -- Could not find stored procedure
'tep_setup_add_hdr'. Changed soap_pw for soap_uid op53029,
soap_server crprchiisby, soap_alias DEV. Local Fix: The
tep_set_up proc is calling the wrong procedure to update the
password. As a workaround, the customer can run the following
for this soap server to update the password: EXEC
tep_setup_add_soap_hdr @verbose=2, @soap_server =
'crprchiisby', @soap_alias = 'DEV', @soap_uid='op53029',
@soap_pw='NEWPASSWORD' We confirmed this workaround worked for
customer.


OA22847 STRUCTURE OF BUSINESS SYSTEM TREE REPORT DOES NOT MATCH
STRUCTURE OF BSV

The order of LOBS on the Business System Tree Report is
incorrect if the LOB tree contains shortcuts.

Also the shortnodeid was removed by a previous APAR as it is
incorrect. It is repopulated by this APAR now that the correct
order has been re-established.

The stored procedure uses the resourcepath from the
ObjPathCache table to sort the LOBs. However, for shortcut LOBs
the resourcepath in the ObjPathCache is the resourcepath of the
original LOB, not the shortcut.

For example, if LOB AAA exists under LOB 'LA Business Systems'
and a shortcut to AAA exists in 'NY Business Systems' then the
resourcepath of the shortcut in ObjPathCache is 'LA Business
Systems\AAA'.

shortnodeid can now be re-generated by this APAR using the
order of resourcepath.


OA23089 SCRIPT UPDATEWASSERVICENAMEFORHMON.KSH DOES NOT WORK

The updatewasservicenameforhmon.ksh script does not work if the
Health Monitor service is on a separate system than the WAS
service (which is common in a multi-server TBSM environment).
This was a script shipped with the WAS 6 LAFix.

Appendix B. Contacting Customer Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active
IBM software maintenance contract, and you must be authorized to submit
problems to IBM. The type of software maintenance contract that you need
depends on the type of product you have:
* For IBM distributed software products (including, but not limited to,
Tivoli, Lotus(R), and Rational(R) products, as well as DB2(R) and
WebSphere products that run on Windows(R) or UNIX(R) operating
systems), enroll in Passport Advantage(R) in one of the following
ways:
* Online: Go to the Passport Advantage Web page
(http://www.lotus.com/services/passport.nsf/WebDocs/
Passport_Advantage_Home) and click How to Enroll

* By phone: For the phone number to call in your country, go to the
IBM Software Support Web site and click the name of your
geographic region.

* For IBM eServer(TM) software products (including, but not limited to,
DB2 and WebSphere products that run in zSeries(R), pSeries(R), and
iSeries(TM) environments), you can purchase a software maintenance
agreement by working directly with an IBM sales representative or an
IBM Business Partner. For more information about support for eServer
software products, go to the IBM Technical Support Advantage Web page
.

If you are not sure what type of software maintenance contract you need,
call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other
countries, go to the contacts page of the IBM Software Support Handbook
on the Web and click the name of your geographic region for phone
numbers of people who provide support for your location.

B.1 Describe the problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include
all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently. To save time,
know the answers to these questions:

* What software versions were you running when the problem occurred?
* Do you have logs, traces, and messages that are related to the
problem symptoms? IBM Software Support is likely to ask for this
information.
* Can the problem be re-created? If so, what steps led to the failure?
* Have any changes been made to the system? (For example, hardware,
operating system, networking software, and so on.)
* Are you currently using a workaround for this problem? If so, please
be prepared to explain it when you report the problem.

B.2 Submit the problem to IBM Software Support

You can submit the problem in one of two ways:

* Online: Go to the "Submit and track problems" page on the IBM
Software Support site ). Enter your information into the appropriate
problem submission tool.
* By phone: For the phone number to call in your country, go to the
contacts page of the IBM Software Support Handbook on the Web
(techsupport.services.ibm.com/guides/contacts.html) and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or
inaccurate documentation, IBM Software Support creates an Authorized
Program Analysis Report (APAR). The APAR describes the problem in
detail. Whenever possible, IBM Software Support provides a workaround
for you to implement until the APAR is resolved and a fix is delivered.
IBM publishes resolved APARs on the IBM product support Web pages daily,
so that other users who experience the same problem can benefit from the
same resolutions.

Appendix C. Notices

This information was developed for products and services offered in the
U.S.A. IBM may not offer the products, services, or features discussed
in this document in other countries. Consult your local IBM
representative for information on the products and services currently
available in your area. Any reference to an IBM product, program, or
service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property
right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or
service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not give you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

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

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own
risk.

IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged,
should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related
to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.

C.1 Trademarks

IBM, the IBM logo, AIX(R), CICS(R), CICSPlex(R), DB2, developerWorks(R),
eServer, IMS(TM), iSeries, Lotus, MVS(TM), NetView(R), OMEGAMON(R),
Passport Advantage, pSeries, Rational, Redbooks, Tivoli, the Tivoli
logo, Tivoli Enterprise Console(R), WebSphere, z/OS, and zSeries are
trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both.

Linux(R) is a trademark of Linus Torvalds in the United States, other
countries, or both.

Microsoft, Windows NT(R), and Windows are registered trademarks of
Microsoft Corporation in the United States, other countries, or both.


| Java(TM) and all
| Java-based trademarks and
| logos are trademarks or
| registered trademarks of
| Sun Microsystems, Inc. in
| the United States, other
| countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

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

Prerequisites

Tivoli Business Systems Manager Version 3.1
Tivoli Business Systems Manager Version 3.1 Fix Pack 2 (3.1.0-TIV-BSM-FP0002)

URL LANGUAGE SIZE(Bytes)
FTP:3.1.0-TIV-BSM-FP0002 English 3848485
HTTP:3.1.0-TIV-BSM-FP0002 English 3848485

Installation Instructions

2.0 Installation and configuration

2.1 Prerequisite

TBSM v3.1 Fix Pack 3 has the following prerequisite:
* Tivoli Business Systems Manager 3.1, with Fix Pack 2 or higher.

2.2 Corequisite

TBSM v3.1 Fix Pack 3 has the following corequisite:
* Strongly recommended: IBM WebSphere Application Server 6.1.0.11

2.3 Hardware and software requirements

Refer to the IBM(R) Tivoli Business Systems Manager v3.1 Installation
and Configuration Guide for the hardware and software requirements for
installing Tivoli Business Systems Manager.

2.4 Backing up databases

Back up all databases before applying the Tivoli Business Systems
Manager v3.1 Fix Pack 3. It is critical to have valid database backups
taken prior to applying Fix Pack 3, as you might need them in the event
you want to reinstall the entire Fix Pack. The following 12 databases
should be backed up before applying this Fix Pack:
* ASIRuleSvc
* Meta
* msdb
* Object
* ObjectEvents
* ObjectQueues
* Resource Object Data Manager (RODM)
* RODMLoad
* WebServer
* OPCLoad
* History
* Adapter

Ensure that these backups exist and the backups were completed during
the same time frame. Typically, backups should be handled using a
database maintenance plan. Save the backups until Fix Pack 3 has been
successfully tested.

We recommend that you back up the databases again (into a new backup
file) after successful Fix Pack installation. In the event that you have
a hard failure of your system, taking this extra precaution saves you
the time required to re-apply the Fix Pack.

If you are applying the Tivoli Business Systems Manager Warehouse Pack,
ensure that backups of all IBM Tivoli Data Warehouse databases are
available before installing this Fix Pack.

2.5 Fix Pack 3 contents


* This readme file in two formats:
* 3.1.0-TIV-BSM-FP0003.readme.pdf
* 3.1.0-TIV-BSM-FP0003.readme (text file)

* 3.1.0-TIV-BSM-FP0003.tar

2.6 Before Installing the Fix Pack

Note: You should know that if you uninstall the Fix Pack you will be
removing the entire product, (either the server component code or
the client component code), not just the Fix Pack code.

* This Fix Pack could require up to 5 Gb of free space on your SQL
Server installation drive. Ensure that the free space is available
before applying this Fix Pack.
* Before applying the Fix Pack, make sure no shell scripts are running
in the background.
* Stop the following services and executables on all Tivoli Business
Systems Manager servers and clients:
* All Tivoli Business Systems Manager services
* SQLServerAgent (SQL server agent)
* MSSQLServer (SQL server)
* IIS Admin Service and World Wide Web Publishing Service (if
present)
* All IntelligentMonitor adapters and their daemons

Do not apply the console component of this Fix Pack without first
applying the base component.

This is not a cumulative Fix Pack. It must be applied on a Tivoli
Business Systems Manager v3.1, with Fix Pack 2 or higher.

2.6.1 Special Considerations


* This Fix Pack will create a new SQL job, Delete old OPC daily plans,
which will be disabled by default. If you are interested in using
this SQL job, you must manually enable it from the SQL Enterprise
Manager. It also has the @daystokeep parameter in the SQL job step
set to 60 days by default, which means any daily plan which is older
than 60 days will be deleted, alongwith all its corresponding data.
You may want to change the @daystokeep parameter to a much larger
number the first time the job is run (e.g. 365), as it may take a
long time to perform the initial cleanup if you have a large OPCLoad
database.
* For the fix for APAR OA21742, the cleanup of the additional tables
will occur with the running of the "Delete Old ObjectEvent Records"
and "Delete Old Closed Notes" SQL jobs.

If the cleanup of the ObjectStateHist table causes a performance
impact when the "Delete Old Closed Notes" job is run, change the job
step to run:

EXEC asisp_deleteOldNotes @trunc = 1

* For the fix for APAR OA22602, the capability will only be available
after it has been manually enabled by entering the following command
from SQL Query Analyzer on the database server, and restarting the
Console Server:
INSERT INTO SystemConfiguration VALUES
('Feature', 'WCDisplayURLHyperlinksInDescription', 1, 'INT')



This capability can be disabled at any time by running the following
command, and restarting the Console Server:

UPDATE SystemConfiguration SET propertyvalue = 0
WHERE groupname = 'Feature'
AND propertyname = 'WCDisplayURLHyperlinksInDescription'

* For the fix for APAR OA15386, by default, the new Date Received
column does NOT appear in the Event Viewer.

To enable display of the Date Received column, set the configuration
table property by using the SQL Server Query Analyser to connect to
the TBSM Object database. Once connnected, enter the following
command:

EXEC _SetSystemConfiguration @groupname='_GetEventViewerEvents',
@propertyname='DisplayDBServerCTime',
@propertyvalue=1,
@propertydatatype='INT'

To disable display of Date Received column, set the configuration
table property by using the SQL Server Query Analyzer to connect to
the TBSM Object database. Once connnected, enter the following
command:

EXEC _SetSystemConfiguration @groupname='_GetEventViewerEvents',
@propertyname='DisplayDBServerCTime',
@propertyvalue=0,
@propertydatatype='INT'

After you change the configuration table property value, you must
restart the Console Server and any connected consoles for the change
to take effect.

2.6.2 For your information

Notes:
1. Changes on the Object, Meta, RODM, and WebServer databases do not
show up on the History server until after the first backup has taken
place after the install.
2. To apply this Fix Pack in a failover environment
a. Stop SQLServerAgent on both primary and secondary servers, and
ensure that it is stopped.
b. Run the following script on the primary database server and
history server to gracefully abort the log shipping process :
sh fo_logship.ksh -A



Running this script stops the log shipping and brings the
secondary databases out of read-only mode.

If the database remains in the read-only mode, run the following
stored procedure from the SQL Query Analyzer on the secondary
(non-active) database server and the history server:

EXEC msdb..asisp_recover_databases

Configuration for Failover environment is located at 2.13, "Special
configuration instructions for failover environment that uses SQL
2000".

2.7 Extracting the Fix Pack

To expand file 3.1.0-TIV-BSM-FP0003.tar:
1. Copy the file 3.1.0-TIV-BSM-FP0003.tar to your system.
2. Unpack the file with the following command:

tar -xvf 3.1.0-TIV-BSM-FP0003.tar

This creates a directory called /3100TIVBSMFP0003 that includes the
following files:
* TIV_BSM_3.1.0_FP0003_base.tar
* TIV_BSM_3.1.0_FP0003_consoles.tar
* TIV_BSM_3.1.0_FP0003_consolesSPB.tar
* TIV_BSM_3.1.0_FP0003_IMfOpenView.tar
* TIV_BSM_3.1.0_FP0003_itecEventEnablement.tar
* TIV_BSM_3.1.0_FP0003_TDW_fix.tar
* TIV_BSM_3.1.0_FP0003_XMLToolkit.tar

.

2.8 Installing the Fix Pack

Note: In the following steps
* <fix pack> refers to the directory where this Fix Pack resides
after you extract it from the tar file.
* <TivoliManager> refers to the directory where Tivoli Business
Systems Manager is installed.

Important: If the database upgrade step fails for any reason during the
Fix Pack installation, do not rerun the install or do the upgrade
manually. Collect the install logs and contact IBM Service. The
install logs can be found in these 2 locations:
* The system temp directory. Enter cd %TEMP% to get to the system
temp directory. Send the install log from the system temp
directory.
* The <TivoliManager>/sql directory. From this directory type the
following 2 commands to package up the logs:
1. tar -cvf fp3_install_logs.tar *.log
2. gzip -c fp3_install_logs.tar < fp3_install_logs.tar.gz

2.8.1 On the Tivoli Business Systems Manager Database Server:


1. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

2. Change to the <baseServices> directory.
3. If you are running log shipping, stop it by issuing the following
command from the <TivoliManager>\bin directory.
sh fo_logship.ksh -A

4. Run the setup.exe file from the <baseServices> directory.
5. From the window that is displayed, select a language.
6. Click Next on the Welcome window.
7. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
8. After you read the list of services that will be stopped, click Next.
9. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
10. Click the box that represents the type of installation, either
distributed or distributed and z/OS(R).
11. A window is displayed while the Microsoft SQL Server service is
started. You can choose to upgrade databases automatically, as a part
of the installation.

If you choose not to upgrade the databases, the databases can be
upgraded manually after the installation by going to the
<TivoliManager>/sql directory and running

sh applyupgrade.ksh 3102tivbsmfp0003.upg
[ [-S<DBserver>] [-E | [[-U<DBuser>] [-P<DBpassword>]]] ]


Database parameters are as follows:

-S<DBserver>
Server where database resides. Default=[$tbsm_server]

-E Use trusted connection

-U<DBuser>
Database username. Default=[$tbsm_userid]

Otherwise, trusted connection used.


-P<DBpassword>
Database password. Default=[$tbsm_password]

If you choose to manually update the database, make sure the
MSSQLServer service is running before running the database upgrade
script from the command prompt.

Click Next.

12. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
updated on this server. Click Next to continue with the installation.
13. Status is displayed. The percentage completion bar is updated as
files are installed.

When the installation has finished, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

14. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.

If the upgrade is applied after the installation, instead of by the
installer, ensure the SQL agent is not running and all of the Tivoli
Business Systems Manager services have been stopped, including the
History server.

15. After the system has rebooted, ensure all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Database
Server have been restarted.

2.8.2 On the Tivoli Business Systems Manager History Server:


1. If it is not currently running, start MS SQL Server service.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

3. Change to the <baseServices> directory.
4. Run the setup.exe file from the <baseServices> directory.
5. From the window that is displayed, select a language and click OK.
6. Click Next on the Welcome window.
7. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
8. This panel lists the services that will be stopped. Click Next.
9. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
10. A window is displayed while the Microsoft SQL Server service is
started. You can choose to upgrade databases automatically, as a part
of the installation.

If you choose not to upgrade the databases and you are at 3.1 plus
Fix Pack 2 level, the databases can be upgraded manually after the
installation by going to the <TivoliManager>/sql directory and
running

sh applyupgrade.ksh 3102tivbsmhistfp0003.upg -S <HistoryServerName> -U
<SQLServerUserName> -P <SQLServerPassword>

Click Next.

11. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
upgraded on this server. Click Next to continue with the
installation.
12. Status is displayed. The percentage completion bar is updated as
files are installed.

When the installation has finished, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

13. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.
14. After the system has rebooted, ensure all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Database
Server have been restarted.

2.8.3 On each of the other Tivoli Business Systems Manager non-database
servers:


1. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_base.tar

2. Run the setup.exe file from the <baseServices> directory.
3. From the window that is displayed, select a language.
4. Click Next in the Welcome window.
5. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
6. This panel lists the services that will be stopped. Click Next.
7. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
8. For the Console server, supply the WebSphere Server userid and
password. Click Next.
9. If you have already upgraded to WAS 6, you will see a screen
prompting for the WebSphere 6.x profile. The name of the profile is
tbsm31. Click Next.
10. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed, as is each component that will be
upgraded on this server. Click Next.
11. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.
12. Reboot the machine before starting any services and running Tivoli
Business Systems Manager.
13. After the system has rebooted, restart all Tivoli Business Systems
Manager services on the Tivoli Business Systems Manager Server.

Note: If an error occurs installing the Console Server component, and
you need to run the update manually (for example, if the WebSphere
ID or password was entered incorrectly), do not rerun the Fix Pack
installer. Instead, run the following command from the
<TivoliManager>\Console Server, to update the console server:



"<WebSphere install dir>\AppServer\bin\wsadmin.bat"
-f update.jacl -conntype SOAP -user <UserID> -password <UserPswd>

If you are upgrading to WAS 6.1.0.11, go to 3.0, "Tivoli Business
Systems Manager support for WebSphere Application Server v6".

2.8.4 On each Tivoli Business Systems Manager client install:


1. Stop the console.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_consoles.tar

3. The console is supported on a number of operating systems. Change to
the directory representing the appropriate operating system. Run the
setup file from the consoleInstall\<platform> directory.
4. From the window that is displayed, select a language.
5. Click Next in the Welcome window.
6. Read the software license agreement. If you accept the terms of the
agreement, click the radio button to indicate that you accept the
terms and then click Next.
7. You are asked if files that are being updated should be backed up
first. Yes is the default and it is selected. If you do not want the
files to be backed up, click the check box to remove the selection.
Click Next.
8. A summary is displayed. The Tivoli Business Systems Manager
installation directory is listed. Click Next to continue with the
installation.
9. You are asked if you want the console to be started once the
installation is complete Yes is the default and it is selected. If
you do not want the console to be started once the installation is
complete, click the check box to remove the selection. Click Next.
10. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.

2.9 Silent console installation


1. Run the setup.exe from the <fix pack> directory as follows:

setup -options-template outputFileName.scr

2. Edit outputFileName.scr to change any installation settings.
3. To install:

setup -options outputFileName.scr -silent

To uninstall the entire client, not just the Fix Pack code:

_uninst\uninstall -silent

IMPORTANT: _uninst\uninstall -silent uninstalls the entire client
component code not just the Fix Pack code.

2.10 Console Software Package Blocks (SPB) installation:

Using software package blocks (SPBs), the fix pack for the console can
be distributed to endpoints in a Tivoli Managed Environment. Tivoli
Business Systems Manager 3.1 needs to be installed on the endpoints
before the fix pack can be distributed.
1. Enter tar -xvf TIV_BSM_3.1.0_FP0003_consolesSPB.tar to extract the
SPBs.
2. See Appendix D. Distributing the Console in a Tivoli Managed
Environment in the Tivoli Business Systems Manager 3.1 Installation
and Configuration Guide for SPB installation instructions.

Note: The fix pack install program does not allow you to change the
installation directories or server name, so there are no default
variables to change when you install SPBs.

The fix pack install program automatically locates the original
installation directory on the endpoint.

To remove the console using software distribution, remove the original
Tivoli Business Systems Manager 3.1 SPB. See Appendix D. Distributing
the Console in a Tivoli Managed Environment in the Tivoli Business
Systems Manager 3.1 Installation and Configuration Guide for
instructions. You should not remove the fix pack's SPB.

2.11 Tivoli Enterprise Console Event enablement component:

1. Unpack the file with the following command:
tar -xvf TIV_BSM_3.1.0_FP0003_itecEventEnablement.tar

2. Use the following information to install patch from the Tivoli
desktop:
a. You must have the install_product and super authorization roles to
successfully install this patch.
b. You should not have a running RIM_MS_SQL_prog on your RIM host
when you apply this patch.
c. Select Install -> Install Patch from the Desktop menu to display
the Install Patch dialog.
d. Click the Select Media button to display the File Browser dialog.
e. Enter the path to the directory containing the patch,
<fixpack>/itecEventEnablement/fp3, in the Path Name field.
f. Click the Set Media & Close button to return to the Install Patch
dialog.
g. The patch install list now contains the component name:
3.1.0-Tivoli_BSM_Event_Enablement-FP0003

h. Select the patch by clicking on it.
i. Select the clients to install this patch on.
j. Click Install to install the patch.

2.12 XML Toolkit:

If you previously installed the XML Toolkit as a separate component,
then complete these instructions to upgrade that function. Do not follow
these instructions if you are using the toolkit version that is
automatically installed on the database server.

1. Unpack the file with the following command:
tar -xvf TIV_BSM_3.1.0_FP0003_XMLToolkit.tar

The XML Toolkit is supported on a number of operating systems. Change
to the directory representing the proper operating system.
2. Run the setup file from the XMLtoolkit\<platform>directory.
3. From the panel that is displayed, select a language.
4. Click Next on the Welcome panel.
5. Read the software license agreement. If you accept the terms of the
agreement, click the button to indicate that you accept the terms and
then click Next.
6. If you plan to use CCMDB discovery library books and want this
capability to be configured during installation of Fix pack 3, click
the appropriate selection and then click Next.
7. If you plan to use the CCMDB reader for discovery, enter the location
for discovery library books.
8. When asked if files that are being updated should be backed up first,
click the box if you would want the files to be backed up. Click
Next.
9. Summary information is displayed. Click Next to finish the
installation.
10. When the installation is complete, a summary is presented,
indicating the state of the installation. Click Finish to exit the
installation wizard.



2.13 Special configuration instructions for failover environment that
uses SQL 2000

IMPORTANT: If you are going to migrate to SQL 2005 immediately after
applying this Fix Pack, do not follow these instructions; instead
see 4.0, "Upgrading to SQL Server 2005 Enterprise Edition".

1. Apply the upgrade to the primary and secondary servers as previously
described in 2.8, "Installing the Fix Pack".
2. Reconfiguration of failover is required before re-starting the
failover environment. Run the configuration script fo_config with -G
option to regenerate the configuration template.
sh fo_config -G > fo.cfg

3. Modify the fo.cfg to fit your environment before running the
configuration script:
sh fo_config -f fo.cfg

4. Start SQLServerAgent on both primary and secondary servers, and
ensure that it is started.
5. From a Command Prompt on the primary database server, enter this
command to reinitialize Log Shipping in the proper direction:

sh fo_logship.ksh

For additional information, see 4.4, "Tivoli Business Systems Manager
Failover".

2.14 Tivoli Business Systems Manager Warehouse Enablement Pack 3.2.0.9
updates

To expand file TIV_BSM_3.1.0_FP0003_TDW_fix.tar:
1. Copy the file TIV_BSM_3.1.0_FP0003_TDW_fix.tar to your system.
2. Unpack the file with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_TDW_fix.tar

3. When installing this Fix Pack on the Tivoli Data Warehouse control
server, follow the procedure from the Installing and Configuring
Tivoli Data Warehouse version 1.2 Guide. This procedure is documented
in Chapter 8, Installing and upgrading warehouse packs. The required
configuration file (twh_install_props.cfg) is located in the
\tedw_apps\gtm directory.

2.15 OpenView adapter

To expand file TIV_BSM_3.1.0_FP0003_IMfOpenView.tar, unpack the file
with the following command:

tar -xvf TIV_BSM_3.1.0_FP0003_IMfOpenView.tar

2.15.1 OpenView Server:

1. Copy the Intelligent Monitor for OpenView install image from the <fix
pack> \IMfOpenView directory to the OpenView server.
2. Install the Intelligent Monitor for OpenView. Refer to the Tivoli
Business Systems Manager Installation and Configuration guide for
instructions on how to install the Intelligent Monitor for OpenView.
3. Configuration information is available in the file

IMfOpenView_readme*.htm

This file is located in the /usr/OV/doc directory on the HP OpenView
server.

Please refer to the full README from the links below for complete installation instructions:

URL LANGUAGE SIZE(Bytes)
3.1.0-TIV-BSM-FP0003.README.pdf English 648995
3.1.0-TIV-BSM-FP0003.README English 114609

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is DD?
3.1.0-TIV-BSM-FP0003.tar 12/21/2007 English 809953280 FTP DD
3.1.0-TIV-BSM-FP0003.README.pdf 12/21/2007 English 648995 FTP DD
3.1.0-TIV-BSM-FP0003.README 12/21/2007 English 114609 FTP DD

Problems (APARS) fixed
OA15196, OA15386, OA16190, OA16261, OA16400, OA16493, OA16545, OA16585, OA16685, OA16721, OA16736, OA16853, OA16939, OA16976, OA17004, OA17067, OA17109, OA17110, OA17165, OA17298, OA17340, OA17346, OA17613, OA17871, OA17898, OA17913, OA18037, OA18072, OA18094, OA18104, OA18170, OA18221, OA18234, OA18248, OA18290, OA18323, OA18429, OA18437, OA18550, OA18556, OA18650, OA18652, OA18672, OA18675, OA18802, OA18822, OA18843, OA18874, OA18917, OA18932, OA19098, OA19122, OA19183, OA19249, OA19329, OA19492, OA19681, OA19805, OA19911, OA19918, OA19932, OA19955, OA20015, OA20110, OA20235, OA20368, OA20372, OA20389, OA20501, OA20623, OA20632, OA20684, OA20709, OA20786, OA20950, OA20951, OA21208, OA21375, OA21742, OA21811, OA21821, OA22288, OA22305, OA22410, OA22418, OA22455, OA22478, OA22602, OA22619, OA22630, OA22660, OA22847, OA23089

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Business Systems Manager

Software version:

3.1

Operating system(s):

Windows

Reference #:

4017202

Modified date:

2010-11-16

Translate my page

Machine Translation

Content navigation