Documentation and Online help plug-in updates
Installing Version 3.1 and Fix Pack, Version 3.1.0.3
Known problems and workarounds
First Edition December 2005
(C) Copyright IBM(R) Corporation 2005. All rights reserved. May only be used pursuant to a Tivoli(R) (R) Systems Software License Agreement, an IBM(R) 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.
This readme file contains the latest information about installing Tivoli Intelligent Orchestrator Fix Pack, Version 3.1.0.3.
This section provides more information on what is supported in the V3.1.0.3:
The APDE is an eclipse plug-in that provides a development environment for developing Tivoli Intelligent Orchestrator workflows and automation packages. V3.1.0.3 comes with a new and improved version of the following automation package as well as other updates.
To download the automation packages :
Fix pack V 3.1.0.3 includes fixes addressed in V 3.1 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 3.1.0.1-TIV-TIO-FP0003.DEFECTS or 3.1.0.1-TIV-TPM-FP0003.DEFECTS.
To download the defects list:
3.1.0.1-TIV-TIO-FP0003.
3.1.0.1-TIV-TPM-FP0003.
Fix Pack V 3.1.0.3 supports all the hardware and software that is supported by Tivoli Intelligent Orchestrator V 3.1.0.
If you have the various Tivoli Intelligent Orchestrator components distributed in a multi-node installation, the fix pack must be applied to the application server node where Tivoli Intelligent Orchestrator resides and not on the database or directory server nodes. For example, for a custom two or three node installation, the fix pack would be applied to the application server node only.
This topic describes the installation requirements for Fix pack 3.
Thoroughly review the following list of prerequisites for installation before proceeding with the installation:
To determine the version of Tivoli Intelligent Orchestrator:
Use the checklists below to ensure that you complete all the required steps to install the fix pack.
| Step | For more information, see the following section: | Insert a X in this column, after you complete each step |
|---|---|---|
| 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. |
|
| Determine the type of installation. |
|
|
| Cancel any workflows currently in progress | "Running the cancel-all-in-progress script" |
|
| Run the deployment requests script to clear any failed, deleted, or canceled workflows | "Running the deployment requests script" |
|
| Back up the DB2 database | The simplest form of the DB2 backup database command requires only that
you specify the alias name of the database that you want to back up:
db2 backup db sample For more information, refer to the section, |
|
Update the value of the following configuration parameters in
DB2(R):
|
This step needs to be performed only under these conditions:
|
|
| Install WebSphere Application Server Cumulative Fix 7 and the new Cumulative Fix 2 for SDKs | "Installing WebSphere Application Server Cumulative Fix 7" |
|
| Configure the IBM Tivoli Directory Server file if you have not installed the fix pack earlier. | "Required changes to the IBM Tivoli Directory Server configuration file" |
|
| Install IBM Tivoli Directory Server Fix pack 3 and Interim fix 1 | "Installing IBM Tivoli Directory Server Fix pack 3 and interim fix 1" |
|
Table 2. Installation of the Fix Pack V3.1.0.3
| Step | For more information, see the following section: | Insert a X in this column, after you complete each step |
|---|---|---|
| Create a temporary directory to place your Fix Pack zip files | "Creating a temporary directory" |
|
| Unzip the fix pack | "Unzipping the fix pack" |
|
| Ensure that the database server is running. | For instructions refer to, "Installing the fix on a Windows system". |
|
| Ensure that the Tivoli Intelligent Orchestrator server is stopped. | For instructions refer to, "Installing the fix on a Windows system". |
|
| Ensure that WebSphere Application Server is stopped. | For instructions refer to, "Installing the fix on a Windows system". |
|
| On the Tivoli Intelligent Orchestrator server, ensure that both the JAVA_HOME and WAS_HOME environment variables are set. | For instructions refer to, "Installing the fix on a Windows system". |
|
| Install the fix pack according to your operating system | For instructions to install on a Windows(R) system, go to "Installing the fix on a Windows system". |
|
Table 3. Post - installation of the Fix Pack V3.1.0.3
| Step | For more information, see the following section: | Insert a X in this column, after you complete each step |
|---|---|---|
| Ensure that the database server and the directory server are running. |
|
|
| Stop the Tivoli Intelligent Orchestrator 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 when Tivoli Intelligent Orchestrator server is stopped. |
|
|
| If you encounter a timeout related error while running the postinstall.bat script, change the timeout values in the file, soap.client.props, | Follow the instructions in the section, Changing the timeout value. |
|
| Open a DOS command prompt. |
|
|
| Complete the required post installation steps. | For instructions to complete the post installation steps on a Windows system, go to "Running the postinstall.bat script on Windows". |
|
Table 4. Post - installation of the Fix Pack V3.1.0.3
| Step | For more information, see the following section: | Insert a X in this column, after you complete each step |
|---|---|---|
| Download the help plug-ins | "Download the updated source" |
|
| Install the help plug-ins | "Installing the updated source" |
|
| Restart Tivoli Intelligent Orchestrator and ensure that you can view the updated source. | "Viewing the updated online help" |
|
Table 5. Additional Information
| Number | Component |
|---|---|
| 1. | "Uninstallation information" |
| 2. | "Known problems and workarounds" |
| 3. | "Hints and tips" |
| 4. | "Contacting customer support" |
Complete the following instructions to run the cancel-all-in-progress script, to cancel any workflows currently in progress:
cancel-all-in-progress.cmd
Complete the following instructions to run the clean-up-deployment-requests script, to clear any failed, deleted, or canceled workflows
clean-up-deployment-requests.cmd
Some reports requires the values of some of the DB2 configuration parameters to be increased and this section provides the required instructions for the same.
This step needs to be performed only under these conditions:
Increase the values of the following parameters for DB2 and restart the database or the changes to take effect:
Step 1: Increase the value of app_ctl_heap_sz
To increase the value of the heap size of app_ctl_heap_sz parameter in DB2, follow the instructions below:
db2 update db cfg for DB2_DB_NAME using app_ctl_heap_sz 256
Step 2: Increase the value of applheapsz
To increase the value of the heap size of applheapsz parameter in DB2, follow the instructions below:
db2 update db cfg for DB2_DB_NAME using applheapsz 4096
Step 3:Increase the value of stmtheap
To increase the value of the Statement heap size configuration parameter (stmtheap) parameter in DB2, follow the instructions below:
db2 update db cfg for DB2_DB_NAME using STMTHEAP 3072
You will need to upgrade the WebSphere Application Server 5.1.1.5, to WebSphere Application Server 5.1.1.7 . This cumulative fix is required for all Windows, Linux(R), AIX(R) or Solaris systems.
This collection of fixes for version 5.1.1 will update WebSphere Application Server to Version 5.1.1.7.
To download the WebSphere Application Server cumulative fix 5.1.1.7:
5.1.1.7
This section provides instructions on configuring the IBM Tivoli Directory Server.
Ensure that you complete the steps and make the required changes to the configuration file, ibmslapd.conf in this section, only if all the following conditions apply:
To configure the IBM Tivoli Directory Server:
ibm-slapdSetenv: SLAPD_OCHANDLERS=5
The section in the configuration file, to which the changes have been made, would look similar to the sample file below:
dn: cn=Front End, cn=Configuration cn: Front End ibm-slapdACLCache: TRUE ibm-slapdACLCacheSize: 25000 ibm-slapdEntryCacheSize: 25000 ibm-slapdFilterCacheBypassLimit: 100 ibm-slapdFilterCacheSize: 25000 ibm-slapdIdleTimeOut: 300 ibm-slapdSetenv: SLAPD_OCHANDLERS=5 ibm-slapdSetenv: DB2CODEPAGE=1208 objectclass: top objectclass: ibm-slapdConfigEntry objectclass: ibm-SlapdFrontEnd
IBM has identified a vulnerability that would allow unauthorized access to change, modify and delete directory data stored in IBM Tivoli Directory Server. While it is not believed that this vulnerability exists when the IBM Tivoli Directory Server is set to use SSL only and SSL Client Server authentication, it is strongly recommended that you update the IBM Tivoli Directory Server installation with the correct fix.
Update information
Identify the correct version of IBM Tivoli Directory Server and download the corresponding Interim Fix:
To download the IBM Tivoli Directory Server cumulative fix 5.2.0.3, Interim Fix 1:
5.2.0.3-TIV-ITDS-IF0001
This section describes the installation of the Tivoli Intelligent Orchestrator fix pack.
On the Tivoli Intelligent Orchestrator server , create a temporary directory into which you will place the fix pack ZIP file.
The directory must meet the following criteria:
To create the temporary directory, run the following command:
mkdir update_installer_dir
Complete the following instructions to unzip Fix Pack V 3.1.0.3.
The section has instructions to install Fix Pack V 3.1.0.3 on a Windows system using the graphic installer as well as using the silent installer.
To install Fix Pack V 3.1.0.3 on Windows systems using the graphic installer:
Use the serverStatus command to obtain the status of the WebSphere Application Server configured on the Tivoli Intelligent Orchestrator node.
The serverStatus command reads the configuration file for the specified application server and stops the server. You can run this command from the %WAS_HOME%\bin directory of a WebSphere Application Server installation.
The following example demonstrate the correct syntax:
%WAS_HOME%\bin\serverStatus server1 -user wasadmin -password wasadmin
echo %WAS_HOME%
The WAS_HOME variable is the location of the WebSphere Application Server and the output would be similar to this:
C:\IBM\WebSphere\AppServer
echo %JAVA_HOME%
The output would be similar to this:
C:\IBM\WebSphere\AppServer\java
C:\IBM\tivoli\thinkcontrol
To install Fix Pack V 3.1.0.3 on Windows systems using the silent mode:
Use the serverStatus command to obtain the status of the WebSphere Application Server configured on the Tivoli Intelligent Orchestrator node.
The serverStatus command reads the configuration file for the specified application server and stops the server. You can run this command from the %WAS_HOME%\bin directory of a WebSphere Application Server installation.
The following example demonstrate the correct syntax:
%WAS_HOME%\bin\serverStatus server1 -user wasadmin -password wasadmin
echo %WAS_HOME%
The WAS_HOME variable is the location of the WebSphere Application Server and the output would be similar to this:
C:\IBM\WebSphere\AppServer
echo %JAVA_HOME%
The output would be similar to this:
C:\IBM\WebSphere\AppServer\java
updateSilent.bat -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example:
updateSilent.bat -fixpack -install "C:\Program Files\IBM\tivoli\thinkcontrol" tio31_fp3_win "C:\temp\update_installer_dir\installer"
Complete the following instructions after you install the fix pack.
To complete the post installation procedure on Windows, follow the instructions below to run the postinstall.bat script.
Before you complete the post-installation steps:
In some situations, you may see a timeout if the command does not complete in a particular amount of time. This situation is caused by the SOAP connection (which is needed in order to run the process) not successfully connecting to the server. This is most likely caused by a network configuration problem or if the processor is very slow. This section provides instructions on changing the com.ibm.SOAP.requestTimeout property of the soap.client.props file, which would possibly provide a workaround to this situation.
The program default value for the request timeout is 180 seconds. Follow the instructions below to change the value to 1800, only if you encounter an timeout related error while running the postinstall.bat script:
Table 6. com.ibm.SOAP.requestTimeout values
| Component | Value |
|---|---|
| Property | com.ibm.SOAP.requestTimeout |
| Data type | Integer |
| Range in seconds | 0 to n
|
| Default | 1800 |
postinstall.bat was_user was_pwd server base_DN
For example:
postinstall.bat wasadmin wasadmin server1 "dc=mycompany,dc=com"
Notes:
The online help documentation is updated for Fix Pack V 3.1.0.3 and is available as a plug-in or on the information center.
Updates, corrections, and additional product information is available from the Tivoli Intelligent Orchestrator Web site. Ensure that you download the latest version of the product information after installing the product.
To properly update your Online help files to the most current level, follow the instructions below.
For Tivoli Intelligent Orchestrator publications:
To install the updated source on your Tivoli Intelligent Orchestrator server, follow the instructions below, according to your operating system:
For example:
When you click on the Help button, on the user interface of Tivoli Intelligent Orchestrator, the product information center displays. Use the navigation on the left to locate the publications that you want to use. PDF versions of the publications are also listed in the navigation on the left.
Product publications include information centers, release notes, installation guides, migration guide, problem determination guide and workflow developer's references.
Complete the following instructions to uninstall the fix pack.
Before you uninstall the fix pack:
This section contains information on uninstalling the fix pack using the graphic installer as well as using the silent uninstaller.
To uninstall Fix Pack V 3.1.0.3 on Windows using graphic uninstaller:
C:\IBM\tivoli\thinkcontrol
To uninstall Fix Pack V 3.1.0.3 on Windows using the silent uninstaller:
updateSilent.bat -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to uninstall the fix pack on Windows systems:
updateSilent.bat -fixpack -uninstall "C:\Program Files\IBM\tivoli\thinkcontrol" tio31_fp3_win "C:\Program Files\IBM\temp\installer"
After you have completed the uninstallation procedure, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server.
To redeploy the EAR files on Windows:
"$TIO_HOME/tools/was_deploy.sh" username password server base_DN
For Example:
"$TIO_HOME/tools/was_deploy.sh" wasadmin wasadmin server1 "dc=mycompany,dc=com"
Restore the database using the tools provided by the database vendor. If you restore the database, the information that existed prior to the fix pack installation will be restored.
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.
Follow the instructions below to install Tivoli Intelligent Orchestrator 3.1 and Fix pack V3.1.0.3. This is a fast-path option to install Tivoli Intelligent Orchestrator and the fix pack.
setupwin32.exe -P ProdFeat_Reinit.active="false"
Before you complete the post-installation steps:
Complete the following instructions after you install the fix pack.
postinstall.bat was_user was_pwd server base_DN init
For example:
postinstall.bat wasadmin wasadmin server1 "dc=mycompany,dc=com" init
Notes:
This section describes known limitations in this release of Tivoli Intelligent Orchestrator V 3.1.0. Where applicable and known, suggested workarounds are identified.
This section provides workarounds to problems that you might encounter during the installation of the Fix pack.
If you are using HP endpoints or managed systems, the .profile or the /etc/profile may contain some commands that are used to set the terminal session settings such as tabs. These commands disrupt the ability of the agent to send messages to the Tivoli Intelligent Orchestrator server.
To prevent such errors from occurring:
if [ ! "$VUE" ]; then # other terminal commands tabs fi
if [ ! "$VUE" ] && [[ -t 0 ]]; then # other terminal commands tabs fi
On Windows, if you have clients that are generating many connections to the server and the connections are being refused, the server might log error messages similar to the following to the ibmslapd.log file:
Feb 11 14:36:04 2004 Communications error: Exceeding 64 connections/OCH - dropping socket.
To solve this problem, do the following:
ibm-slapdSetenv: SLAPD_OCHANDLERS=5
The section in the configuration file, to which the changes have been made would look similar to the sample file below:
dn: cn=Front End, cn=Configuration cn: Front End ibm-slapdACLCache: TRUE ibm-slapdACLCacheSize: 25000 ibm-slapdEntryCacheSize: 25000 ibm-slapdFilterCacheBypassLimit: 100 ibm-slapdFilterCacheSize: 25000 ibm-slapdIdleTimeOut: 300 ibm-slapdSetenv: SLAPD_OCHANDLERS=5 ibm-slapdSetenv: DB2CODEPAGE=1208 objectclass: top objectclass: ibm-slapdConfigEntry objectclass: ibm-SlapdFrontEnd
If you continue to receive error messages, increase environment variable by 5 until you stop receiving error messages.
When starting Tivoli Intelligent Orchestrator V 3.1.0 from the Windows Services menu, the following error occurs:
Could not Start the IBM Tivoli Intelligent Orchestrator service on Local Computer Error 1069: The service did not start due to a logon failure
The tioadmin user has to be granted with Log On As Service privileges. To grant the privilege:
This section provides workarounds to problems that you might encounter after the installation of the Fix pack and after running the post installation scripts.
Given below are the two probable situations where you might encounter this problem:
After the changes have been made, the build-version.properties file would look similar to the sample file below:
current.version=3.1.0.0 build.number=1354 show.date=false
After the changes have been made, the build-version.properties file would look similar to the sample file below:
current.version=3.1.0.1 build.number=1354 show.date=false
This section provides workarounds to problems that you might encounter at some instances while using Tivoli Intelligent Orchestrator V 3.1.0.
When you manually associate a discovered software resource on a server with a software definition, the properties of the software stack, the software modules do not appear. Compliance checking also incorrectly defines the software stack as missing when the software stack is included in the server template.
Avoid associating software stacks or distributed applications with identified software resources on a server. You can only select a software product, patch, or operating system software definition.
Forcing a workflow to stop immediately while it is performing an operation can result in hanging processes, open file handles, and similar conditions.
There are several reasons that you might want to stop a workflow. For example, you might want to cancel a particular deployment request for workflow that is normally scheduled to run on a regular basis. In some situations, a workflow can get stuck in an "in-progress" state and never finish. Running a newly created workflow that has errors or abruptly shutting down the product while workflows are running are two examples that might cause a workflow to get stuck in an in-progress state.
If you need to stop a specific workflow, there are two ways to cancel it:
Use the regular stop command to cancel a workflow to prevent this error from occurring. To cancel a workflow, follow the instructions below:
This section provides some limitations that you might encounter while using Tivoli Intelligent Orchestrator V 3.1.0.
Tivoli Intelligent Orchestrator or the target servers cannot handle simultaneous remote SSH connections on Windows. This is a limitation of the operating system.
Due to this limitation on Windows, you may see an error message that is displayed, similar to this example below:
COPCOM123E This shell command error occurred: Exit value=2, Error stream="SCP copy file timed outbash:
line 39: syntax error near unexpected token `('bash: line 39: ` -re "\r\n(\[0-9]*)\r\n" {'", Result stream="<tio><throw exception="timeoutError">ERROR: Device not responding or unexpected response</throw></tio>". (retVal=-100) after overall duration 168704ms
Installing tcdrivers displays errors that do not disrupt the installation of the tcdriver itself. The error occurs only occasionally and do not affect the installation of the tcdriver, nor do they affect the functionality of the application.
Given below is a sample of part of of the log file, that is displayed occasionally when installing some tcdrivers. Ignore the error and continue with the installation.
log4j:ERROR Failed to flush writer
This section provides some hints and tips for using Tivoli Intelligent Orchestrator V 3.1.0.
Given below are the user ID and password requirements for DB2. Use these guidelines when installing the prerequisite software. Refer to the DB2 documentation for more information.
The application server name is required to run the postinstall.bat script on Windows and postinstall.sh script on UNIX(R) and Linux systems. Use the information below to determine your application name.
If you have any questions about this fix pack, call the IBM Support Center for your country. For example, in the USA call 1-800-IBM-SERV. For specific contact numbers for all countries, refer to the following Web site:
http://techsupport.services.ibm.com/guides/contacts.html
If you find a problem or have a suggestion about the Automation Package Development Environment features or the documentation in general, contact IBM through the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment forum. The forum is a technical discussion focussed on installing, configuring and using the Automation Package Development Environment (APDE) for writing workflows and creating automation packages for the Tivoli Intelligent Orchestrator products.
To access the forum:
The following section includes important information about this document and its use.
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
grant 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 may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
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 Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada
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.
The IBM logo and the following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both:
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a trademark of The Open Group in the United States, other countries, or both.
Pentium(R) and Intel(R) are trademarks of Intel Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft(R) and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.