IBM Tivoli Intelligent ThinkDynamic Orchestrator and IBM Tivoli Provisioning Manager Fix Pack, FP02 Readme

(C) Copyright IBM^(R) Corporation 2004. All rights reserved. May only be used pursuant to a Tivoli ^(R) Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the

IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

About this fix pack

This readme file contains the latest information about installing Tivoli Intelligent ThinkDynamic Orchestrator Fix Pack, Version 2.1.0.2 and Tivoli Provisioning Manager Fix Pack, Version 2.1.0.2.

The Automation Package Development Environment (APDE) included in this fix pack is an introduction to the new development environment. This readme provides beta documentation for this beta APDE product, and can be found by entering apde in the search box. This readme provides beta documentation for this beta APDE product. If you find a problem or have a suggestion about APDE features or the documentation in general, contact IBM through the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment forum located at: http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=373&cat;=15).

New in Fix Pack V 2.1.0.2

Fix pack V 2.1.0.2 includes:

Fixes addressed in V 2.2 and customer Authorized Program Analysis Reports (APARs):
For a detailed list of fixes and customer APARs included in this fix pack, refer to the file 2.1.0.2-TIV-TIO-FP02.DEFECTS or 2.1.0.2-TIV-TPM-FP02.DEFECTS.
To download the defects list:
1. Go to the IBM^(R) Support Web site: http://www.ibm.com/support
2. In the Support topics list, click Downloads and Drivers.
3. In the Browse product support section, under Software list, click Tivoli.
4. In the search box, enter the fix pack number:
  - For the Tivoli Intelligent ThinkDynamic Orchestrator Fix Pack V 2.1.0.2, enter:
    2.1.0.2-TIV-TIO-FP02.
  - For the Tivoli Provisioning Manager Fix Pack V 2.1.0.2, enter:
    2.1.0.2-TIV-TPM-FP02.
5. Click Search. The Download Results page is displayed.
6. On the Download Results page, depending on your search, one of the following links is displayed:
  - Tivoli Intelligent ThinkDynamic Orchestrator Fix Pack 2.1.0.2-TIV-TIO-FP02
  - Tivoli Provisioning Manager Fix Pack 2.1.0.2-TIV-TIO-FP02
7. Click on the displayed link. The corresponding page is displayed.
8. For a list of defects that are corrected by this fix pack, click on 2.1.0.2-TIV-TIO-FP02-DEFECTS (HTTP) or 2.1.0.2-TIV-TPM-FP02-DEFECTS (HTTP).

Product compatibility

Fix Pack V 2.1.0.2 supports all the hardware and software that is supported by Tivoli Intelligent ThinkDynamic Orchestrator V 2.1.0 and Tivoli Provisioning Manager V 2.1.0. In addition Fix pack V 2.1.0.2 now supports:

DB2 fix pack 7a for V8.2
WebSphere^(R) Application Server 5.1.1.2
AIX 5.3 64 bit POWER 5.
Red Hat Enterprise Linux 3.0 AS 32 bit xSeries Update 3.
SUSE Linux Enterprise Server 8 for Linux on xSeries.

Note:

Refer to the following guides for more information on how to install Tivoli Intelligent ThinkDynamic Orchestrator V 2.1.0 and Tivoli Provisioning Manager V 2.1.0 on:

AIX 5.3 64 bit POWER 5: See the chapters that refer to AIX in the Installation Guide for UNIX
Red Hat Enterprise Linux 3.0 AS 32 bit xSeries Update 3 and SUSE Linux Enterprise Server 8 for Linux on xSeries: See the chapters that refer to Linux Intel in the Installation Guide for Linux.

Pre-installation instructions

Complete the instructions in this section, before you install the fix pack.

Note:: Also ensure that your system meets the hardware and disk space and operating system requirements, as well as the other requirements such as the kernel parameter settings. For more information, refer the appropriate installation guides.

Multi-node environments

If you have the various Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager components distributed in a multi-node installation, the fix pack must be applied to the node where Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager resides. For example, for a custom two or three node installation, the fix pack would be applied to the application server node only.

Instructions for SUSE Linux Enterprise Server 8

If you are using SUSE Linux Enterprise Server 8 for Linux on xSeries. Patch 3 is required. It can be downloaded from the SUSE LINUX maintenance Web site: http://sdb.suse.de/en/psdb/html/ . If you have not downloaded from this site before, you will need to register.

Note:: The DB2 installation using the prerequisite software installer fails due to a port conflict. Ensure that the workaround provided in the section "On some Linux systems, the installation of DB2 using the graphical installer fails" is completed prior to installing the fix pack.

Creating a temporary directory

On the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server, create a temporary directory into which you will place the fix pack ZIP file.

To create the temporary directory, run the following command:

Logon as Administrator, on Windows^(R), from within Cygwin:
```
mkdir update_installer_dir
```
Logon as Root, on AIX^(R), Linux^(TM), or Solaris:
```
mkdir update_installer_dir
```

The directory must meet the following criteria:

Exists outside the Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation directory.
Includes at least 200 MB of free space to contain the fix pack after it is unzipped.
Includes read and write privileges.

Unzipping the fix pack

Complete the following instructions to unzip Fix Pack V 2.1.0.2. These instructions are applicable to all the operating systems supported by IBM for Fix Pack V 2.1.0.2.

Log on to the server as Administrator in Windows, or as root in Solaris, Linux or AIX.
Copy the fix pack package to update_installer_dir directory . The update_installer_dir is the directory in which you will unzip the fix pack ZIP file.
Unzip the fix pack ZIP file. Unzipping the file will create a new directory within the current directory to store the package contents. After you unpack the ZIP file, you can delete the ZIP file to free space in the directory if necessary.
If you unzip the file from Cygwin, ensure that the files under the update_installer_dir/installer directory have read and write permissions.

Uninstall the alteon-load-balancer.tcdriver

The alteon-load-balancer.tcdriver needs to be uninstalled, if installing Fix Pack, Version 2.1.0.2 on version of Tivoli Intelligent ThinkDynamic Orchestrator 2.1 or Tivoli Provisioning Manager 2.1.

Note:: If you are installing Fix Pack Version 2.1.0.2 on Fix Pack Version 2.1.0.1, then you do not need to perform this step.

To uninstall an automation package on Windows, run the following commands in a DOS window:

Log on as tioadmin.
Switch to the %TIO_HOME%\tools directory where %TIO_HOME% is the Tivoli Intelligent ThinkDynamic Orchestrator installation directory
To confirm that the alteon-load-balancer.tcdriver has not been installed:
```
%TIO_HOME%\tools\tc-driver-manager.cmd listAllstr
```
Run the following command, to uninstall the alteon-load-balancer.tcdriver, if it has been installed:
```
tc-driver-manager.cmd uninstallDriver alteon-load-balancer
```
To verify that the alteon-load-balancer.tcdriver has been removed, list all the drivers using the command:
```
%TIO_HOME%\tools\tc-driver-manager.cmd listAllstr
```

Note:: If the uninstallation is not successful, then review the additional information provided in the Nortel_Alteon.html in the directory: update_installer_dir\drivers where update_installer_dir is the directory in which you have unzipped the fix pack.

To uninstall an automation package on Solaris, AIX or Linux:

Log on as tioadmin.
Switch to the $TIO_HOME/tools directory where $TIO_HOME is the Tivoli Intelligent ThinkDynamic Orchestrator installation directory
To confirm that the alteon-load-balancer.tcdriver has not been installed:
```
$TIO_HOME/tools/tc-driver-manager.sh listAllstr
```
Run the following command, to uninstall the alteon-load-balancer.tcdriver, if it is installed:
```
tc-driver-manager.sh uninstallDriver alteon-load-balancer
```
To confirm that the alteon-load-balancer.tcdriver has been removed, list all the drivers using the command:
```
$TIO_HOME/tools/tc-driver-manager.sh listAllstr
```

Note:: If the uninstallation is not successful, then review the additional information provided in the Nortel_Alteon.html in the directory: update_installer_dir/drivers where update_installer_dir is the directory in which you have unzipped the fix pack.

zVM tc-driver installation instructions for the new managed-from platforms

This section provides a workaround for installing the fix pack on the following systems, in order to support the zVM tc-drivers.

AIX 5.3 64 bit POWER 5.
Red Hat Enterprise Linux 3.0 AS 32 bit xSeries Update 3.
SUSE Linux Enterprise Server 8 for Linux on xSeries.

The zVM tc-driver included in the fix pack does not support these new managed-from platforms. During the fix pack installation, when the zVM tc-driver is installed, some installation directories will not be found and the tc-driver installation process will be terminated.

To workaround this problem:

Go to the %TIO_HOME%/drivers directory of the current installation and delete the file zvm.tcdriver.
Go to the %TIO_HOME%/tools directory and run post-install command to continue installation of all new tc-drivers .

Note:: Updates will be made available to the Automation Catalog with this updated support. Monitor the Web site, http://www.developer.ibm.com/tivoli/workflow.html, for more information by searching on zSeries.

Installation of the fix pack

This section describes the installation of the fix pack.

Installing the fix on a Windows system

To install Fix Pack V 2.1.0.2 on Windows:

From a command prompt, log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as Administrator
Note:
The installer can only be run in a GUI mode. Open the command prompt from within Windows (either locally or using remote desktop) but not remotely using SSH.
Ensure that the database server and the directory server are both running.
Ensure that the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server is stopped.
On the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server, set the JAVA_HOME environment variable to WAS_HOME\java where WAS_HOME is the location of the WebSphere Application Server.
Change directory to update_installer_dir\installer where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
From update_installer_dir\installer, run the updatewizard.bat command to launch the installation wizard.
Select the correct language and click OK.
On the Welcome screen, click Next.
On the next screen, specify the installation root directory.
Note:
The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
2. Click Browse and select the appropriate installation root directory. For example:
```
C:\IBM\tivoli\thinkcontrol
```
Click Next until you are prompted to select an option.
Select Install fix packs and click Next.
The fix pack directory screen displays the default directory in which the fix pack package is unzipped. Verify that the fix pack package is in this directory and click Next.
On the fix pack selection screen, select the correct fix pack, and click Next.
Review the information on the review screen and then click Next. The summary screen is displayed.
On the summary screen, click Finish. The system completes the installation.

Installing the fix pack on AIX, Linux, or Solaris systems

To install Fix Pack V 2.1.0.2 on AIX , Linux, or Solaris systems:

Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as root.
Ensure that the database server and the directory server are both running.
Ensure that the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server is stopped.
Export the JAVA_HOME environment variable to WAS_HOME/java where WAS_HOME is the location of the WebSphere Application Server.
Ensure that the DISPLAY variable is set and confirm that the hostname of the server is correct.
Change directory to update_installer_dir/installer where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
From update_installer_dir/installer, run updateWizard.sh to launch the installation wizard.
Select the correct language and click OK.
Click Next on the Welcome page.
On the next screen, specify the installation root directory.
Note:
The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
2. Click Browse and select the appropriate installation root directory. For example:
```
/opt/IBM/tivoli/thinkcontrol
```
Click Next until you are prompted to select an option.
Select Install fix packs and click Next.
The fix pack directory screen displays the default directory in which the fix pack package is unzipped. Verify that the fix pack package is in this directory and click Next.
On the fix pack selection screen, select the correct fix pack, and click Next.
Review the information on the review screen and then click Next. The summary screen is displayed.
On the summary screen, click Finish. The system completes the installation.

Post-installation steps

Complete the following instructions after you install the fix pack.

Before you begin

Before you complete the post-installation steps:

Back up the database using the backup utility that is provided with the database.
Ensure that the database server and the directory server are running.
Stop the Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager server. For detailed instructions on how to start and stop the servers in different environments, refer to the installation guide that is supplied with the product.

Configuring transaction log size in the WebSphere Application Server

Use this task to configure the Application Server's transaction log size. To configure the transaction log size for the WebSphere Application Server, complete the following steps:

Start WebSphere Application Server and log on to the Administrative console from your browser by typing: http://YOUR_HOSTNAME:9090/admin. Replace the variable YOUR_HOSTNAME with the host name of the application server.
Click Servers->Application Servers -> Server1 -> Transaction Service.
Select the Configuration tab, to display the transaction-related configuration properties.
Change the Transaction Log directory field to ;10M.
Note:
Ensure that there is a semicolon before the number ;10M.
Click OK.
Click Apply -> Save.
Stop and then restart the application server.

Post-installation on Windows

To complete the post installation procedure on Windows:

Running the postinstall.bat script

Follow the instructions below to run the postinstall.bat script.

Log in as user tiodamin.
Ensure that the database server and the directory server are running.
Ensure that the WebSphere Application Server is stopped.
Note:
If you have attempted to stop the WebSphere Application Server using the Services management console, but the WebSphere Application Server processes continue to run, refer the section Running the upd_service.bat script, for more information on how to stop the services.
To deploy the Zip files:
1. Change the directory to update_installer_dir\installer\utils where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
2. Run the command postinstall.bat was_user was_pwd command, where was_user is your WebSphere Application Server user name, and was_pwd is your WebSphere Application Server password. The post-installation operation will print the output to the console.
Note:
To redirect the output to a log file run the following command and replace the variable was_user with your WebSphere Application Server user name, and was_pwd with your WebSphere Application Server password:
```
postinstall.bat was_user was_pwd > postinstall.log
```

Running the upd_service.bat script

When you attempt to stop WebSphere Application Server using the Services management console, the system reports that the status of the service is Stopped, but the WebSphere Application Server processes continue to run. The upd_service.bat script updates the Windows registry to ensure that the username and password of the WebSphere Application Server match the actual values.

Note:: This script must be run once after installing the fix pack and after running the change_Password script.

To run the upd_service.bat script:

Ensure that all services on the server are stopped. Reboot the server if required.
From the DOS command window, run the following command:
```
%TIO_HOME%\tools\upd_service.bat
```
When prompted:
1. At the The Home folder of WAS [%WAS_HOME%]: prompt, press Enter to accept the default value.
2. At the The Home folder of TIO [%TIO_HOME%]: prompt, press Enter to accept the default value.
3. At the The name of the WAS server [server1]: prompt, press Enter to accept the default value.
4. At the The user name for the TIO services [.\tioadmin]: prompt, press Enter to accept the default value.
5. At the The password for the user tioadmin: prompt, type your Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager password.
6. At the The WAS user name [wasadmin]: prompt, type your WebSphere Application Server user name. (Typically, this value is wasadmin.)
7. At the The password for the WAS user wasadmin: prompt, type your WebSphere Application Server password. (Typically, this value is wasadmin.)

Post-installation on AIX, Linux, or Solaris

To complete the post installation procedure on AIX , Linux, or Solaris:

Running the postinstall.sh script

Follow the instructions below to run the postinstall.sh script:

Log in as user tiodamin.
Ensure that the database server and the directory server are running.
Ensure that the WebSphere Application Server is stopped.
To deploy the EAR (expanded archive) files and database schema change, follow these instructions below:
1. Change the directory to update_installer_dir/installer/utils where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
2. From update_installer_dir/installer, run the following command and replace the variable was_user with your WebSphere Application Server user name, and was_pwd with your WebSphere Application Server password. The post-installation operation will print the output to the console.
```
postinstall.sh was_user was_pwd
```
Note:
To redirect the output to a log file, run the following command and replace the variable was_user with your WebSphere Application Server user name, and was_pwd with your WebSphere Application Server password:
```
postinstall.sh was_user was_pwd > postinstall.log
```

Uninstallation information

Complete the following instructions to uninstall the fix pack.

Before you begin

Before you uninstall the fix pack:

Ensure that the database server and the directory server are both running.
Stop the Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager server. For detailed instructions on how to start and stop the servers in different environments, refer to the installation guide that is supplied with the product.
Ensure that the WebSphere Application Server is stopped.

Uninstalling the fix on a Windows system

To uninstall Fix Pack V 2.1.0.2 on Windows:

From a command prompt, log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as Administrator
On the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server, set the JAVA_HOME environment variable to WAS_HOME\java where WAS_HOME is the location of the WebSphere Application Server.
Change the directory to update_installer_dir\installer where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
From update_installer_dir\installer, run the updatewizard.bat command to launch the installation wizard.
Select the correct language and click OK.
On the Welcome screen, click Next.
On the next screen, specify the installation root directory.
Note:
The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
2. Click Browse and select the appropriate installation root directory. For example:
```
C:\IBM\tivoli\thinkcontrol
```
Click Next until you are prompted to select an option.
Select Uninstall fix packs and click Next.
The name of the installed fix pack package is displayed. Verify that the specified fix pack package is the one that you want to uninstall, and click Next.
On the fix pack selection screen, select the correct fix pack, and click Next.
On the review screen, in the Name box click Next.
On the summary screen, click Finish. The system completes the uninstallation.

Redeploying the expanded archive files

After you have completed the uninstallation procedure using the graphical interface, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server. To redeploy the EAR files:

Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server as user tioadmin.
Start the WebSphere Application Server.
From a DOS command prompt, run the following command:
```
$TIO_HOME/tools/was_deploy.sh username password"
```
Note:
The default value for username and password is wasadmin.
Stop the WebSphere Application Server.

Reinstalling the automation packages

After you redeploy the expanded archive files, you must reinstall the automation packages.

Run %TIO_HOME%\tools\post-install.cmd. This script installs all automation packages into the %TIO_HOME%\drivers directory. If you added any automation packages to this directory, they will be installed when you run the script.

Note:: Consider removing any automation packages that you added to the %TIO_HOME%\drivers directory to prevent "not installed" error messages from appearing when you run this script. The script will process for approximately one hour, as the system loads the automation packages.

Uninstalling the fix pack on AIX, Linux, or Solaris systems

To uninstall Fix Pack V 2.1.0.2 on AIX , Linux or Solaris:

Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as root.
Ensure that the database server and the directory server are both running.
Export the JAVA_HOME environment variable to WAS_HOME/java where WAS_HOME is the location of the WebSphere Application Server.
Ensure that the DISPLAY variable is set and confirm that the hostname of the server is correct.
Change directory to update_installer_dir/installer where update_installer_dir is the directory in which you unzipped the fix pack ZIP file.
From update_installer_dir/installer, run updateWizard.sh to launch the installation wizard.
Select the correct language and click OK.
On the Welcome screen, click Next.
On the next screen, specify the installation root directory.
Note:
The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
2. Click Browse and select the appropriate installation root directory. For example:
```
/opt/IBM/tivoli/thinkcontrol
```
Click Next until you are requested to select an option.
Select Uninstall fix packs and click Next.
The name of the installed fix pack package is displayed. Verify that the specified fix pack package is the one that you want to uninstall, and click Next.
On the fix pack selection screen, select the correct fix pack, and click Next.
On the review screen, in the Name box click Next.
On the summary screen, click Finish. The system completes the uninstallation.

Redeploying the expanded archive files

After you have completed the uninstallation procedure using the graphical interface, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server. To redeploy the EAR files:

Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server as user tioadmin.
Start the WebSphere Application Server.
At a command prompt, run the following script:
```
$TIO_HOME/tools/was_deploy.sh username password 
```
Note:
The default value for username and password is wasadmin.
Stop the WebSphere Application Server.

Reinstalling the automation packages

After you redeploy the expanded archive files, you must reinstall the automation packages. To reinstall the automation packages:

Run $TIO_HOME/tools/deinitdb.sh
Run $TIO_HOME/tools/post-install.sh start. This script installs all automation packages into the $TIO_HOME/drivers directory. If you added any automation packages to this directory, they will be installed when you run the script.
Note:
Consider removing any automation packages that you added to the $TIO_HOME/drivers directory to prevent "not installed" error messages from appearing when you run this script. The script will process for approximately one hour, as the system loads the automation packages.

Restoring the database

Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager cannot determine or predict whether the database should be restored after you uninstall the fix pack.

If you restore the database to the information that existed before the fix pack was installed, the information that was recorded when you installed the fix pack will be deleted.

The decision to restore the database is, therefore, largely affected by the business needs of the enterprise. The database administrator and the appropriate corporate representatives should discuss whether or not the enterprise needs to keep the information that was recorded when you installed the fix pack. If you need that information, do not restore the database. If you do not need the information, it might be appropriate to restore the database.

Known limitations, problems, and workarounds

This section describes known defects in this release of Tivoli Intelligent ThinkDynamic Orchestrator V 2.1.0 and Tivoli Provisioning Manager V 2.1.0. Where applicable and known, suggested workarounds are identified.

On Linux systems, embedded messaging broker does not shut down

Description of the problem

When shutting down WebSphere Application Server, the last entry in the SystemOut.log file is:

[date time CDT] 1a87ba29 JMSEmbeddedPr A MSGS0054I: Stopping the Broker

Also, a Java core file :javacore29282.1054144121.txt is created at approximately the same time [date at timeTIFILENAME] as the embedded messaging broker tries to shut down.

When WebSphere Application Server shuts down, the embedded messaging broker does not shut down properly, due to an outdated libstdc++ file.

Workaround

Upgrade Linux to the latest Service Pack (a minimum of Service Pack 3 is required), which includes the fix for the libstdc++ file.

On some Linux systems, the installation of DB2 using the graphical installer fails

Description of the problem

The graphical installation process selects port number 50000 by default. However, this port is already assigned by the system.

Workaround

You can work around this problem in one of two ways. The first way is to manually install DB2 without using the graphical installer. To follow this workaround, refer to the DB2 installation documentation.

The second way is to modify the db2server.txt file so that the graphical install process will function properly. To follow this workaround:

Start the graphical installer and follow the panels to the prompts for DB2 instance owner and the DB2 password. You will then be prompted for the directory location of the DB2 workgroup server package.
Before you enter the directory location, you must correct the port number conflict:
1. Open /opt/IBM/db2/V8.1/pics/db2server.txt
2. In the db2server.txt file, locate the line:
```
db2inst1.PORT_NUMBER = 50000
```
3. Change the port number from 50000 to 50001.
4. Save the file.
Return to the graphical installer and enter the directory location of the DB2 workgroup server package and continue the graphical install process.

On some Linux RedHat 3.0 systems, Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager does not shut down

Description of the problem

When stopping a Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager, a java.lang.Exception occurs. The error would look similar to the example shown below:

Note:: Some lines may be split in two, with the second line indented, for presentation purposes only.

%TIO-I-STOP, stop TPM
java.lang.Exception: 
Timeout waiting for file /opt/IBM/tivoli/thinkcontrol/help/eclipse
/workspace/.metadata/.connection
Eclipse is not running.
  at java.lang.Throwable.<init>(Throwable.java:52)
  at java.lang.Throwable.<init>(Throwable.java:66)
  at org.eclipse.help.internal.standalone.EclipseConnection.renew
	(EclipseConnection.java:119)
  at org.eclipse.help.internal.standalone.EclipseController.sendHelpCommand
   (EclipseController.java:93)
  at org.eclipse.help.internal.standalone.EclipseController.shutdown
   (EclipseController.java:62)
  at org.eclipse.help.internal.standalone.StandaloneInfocenter.executeCommand
	(StandaloneInfocenter.java:72)
  at org.eclipse.help.internal.standalone.StandaloneInfocenter.main
	(StandaloneInfocenter.java:49)
  at org.eclipse.help.standalone.Infocenter.main
	(Infocenter.java:99)
./tio.sh: line 260: kill: (24293) - No such process
TPM shutdown completed.
Review /opt/IBM/tivoli/thinkcontrol/logs/tpm_stop.log for any errors

Workaround

Set the following environment variable before stopping Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager and then run the tio.sh stop command:

export LD_ASSUME_KERNEL=2.4.19

On some Solaris systems running Oracle, entries missing after running reinit

Description of the problem

After running reinit on Oracle on Solaris systems, entries in the Administration console are missing. The error is generated because the reinit command does not drop the CDB user (and all its tables) before the creation.

Workaround

Before running the reinit command, run the following commands:

sqlplus <adminusername>/<password>@<your db name>. Replace the variables accordingly:
- <adminusername> with your Oracle database user name
- <password> with your Oracle database password
- <your db name> with the name of your database
drop user cdb cascade
Re-run reinit

Installation fails on Windows systems

Description

Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager Fix Pack, FP02, fails to install on a Windows system, when logged in as Administrator.

Workaround

If you have initially installed Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager V2.1 as tioadmin, then ensure that you install the Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager Fix Pack, FP02, as tioadmin. Installing the fix pack as Administrator will fail the installation.

Problems with reinstallation on Windows systems

Description

On attempting to reinstall FP02, after an uninstallation, the Update Installation Wizard displays the Partially installed icon.

Workaround

The fix pack did not uninstall all the required files. Manually remove the following files and restart the machine.

%TIO_HOME%\properties\version\tio20_fp2_<platform>.ptf
%TIO_HOME%\properties\version\history\tio20_fp2_<platform>.ptfApplied
%TIO_HOME%\properties\version\history\tio20_fp2_<platform>.ptfDriver

Shutting down Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager with pending transactions or workflows may causes errors

Description

When Tivoli Intelligent ThinkDynamic Orchestrator 2.1 or Tivoli Provisioning Manager 2.1. is shut down with pending or in-progress workflows and then restarted, the workflows may no longer respond or the application may fail to restart.

Workaround

Follow the instructions below for the workaround:

Shut down Tivoli Intelligent ThinkDynamic Orchestrator 2.1 or Tivoli Provisioning Manager 2.1.
Run the script tio.sh with the "clean" parameter.
Restart the system.

Documentation updates

This section includes updates to the documentation that was shipped with Tivoli Intelligent ThinkDynamic Orchestrator 2.1 and Tivoli Provisioning Manager 2.1.

Workflow updates

This section includes updates to workflows.

SOAP commands for checking the status of workflows

The SOAP commands for running workflows have been updated. You will now be able to query the status of the workflow that is being run using the SOAP command: DeploymentRequestStatusService. These commands are useful when you want to test workflows in a test application environment. You can run this SOAP command from the GUI or from the command line. The deployment status code has the following values:

0: Unknown
1: In-progress
2: Cancelled
3: Success
4: Failed
5: Created

Checking status of workflows from the GUI

To run DeploymentRequestStatusService from the GUI:

Open your Web browser to and type in this URL. Replace the variable hostname with the fully-qualified domain name of the server. :
```
http://hostname:9080/tcWebUI/
```
From SOAP command line, enter the appropriate SOAP command to query the workflow.

The following different states of the workflows can be queried using the appropriate SOAP commands:

To get the workflow request status

Replace the variable requestID with the requestID generated by the workflow

DeploymentRequestStatusService  findDeploymentStatus requestID

To check if the workflow request is successful