IBM Tivoli Intelligent Orchestrator and IBM Tivoli Provisioning Manager Fix Pack, Readme
Copyright statement
About this fix pack
Pre-installation instructions
Installation of the fix pack
Post-installation steps
Uninstallation information
Installing Version 3.1 and Fix Pack, Version 3.1.0.2
Known problems and workarounds
Hints and tips
Contacting customer support
Notices and trademarks
First Edition September 2005
- Note:
- Before using this information and the product it supports, read the
information in the section "Notices and trademarks".
(C) Copyright IBM(R) Corporation 2005. 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.
This readme file contains the latest information about installing Tivoli
Intelligent Orchestrator Fix Pack, Version 3.1.0.2 and
Tivoli Provisioning Manager Fix Pack, Version
3.1.0.2.
This section provides more information on what is supported in the
V3.1.0.2:
- Windows Server Update Services (WSUS)
- Update Services is the next version of Software Update Services
(SUS). WSUS is an add-in component for Windows 2000 and Windows Server
2003 for deploying software updates to desktop and server machines running
Windows 2000, Windows XP, and Windows Server 2003. The Tivoli(R)
Intelligent Orchestrator or Tivoli Provisioning Manager installation includes
an automation package for WSUS.
- IBM Tivoli System Automation support
- Tivoli Intelligent Orchestrator and Tivoli Provisioning Manager
V3.1.0.2 are now integrated with IBM Tivoli System
Automation.
In V3.1.0.2, IBM Tivoli System Automation, Tivoli
Intelligent Orchestrator or Tivoli Provisioning Manager and DB2 work together
to ensure that a highly available failover environment is provided for DB2
applications. If there is any incident, the highly available failover
environment ensures that the workload of failed servers, organized in cluster
domains, can be taken over by standby servers, with minimum or zero
downtime. The other advantages of this integration are:
- Fast detection of incidents and problems in a network.
- Sophisticated knowledge of application components and their
relationships.
- Quick and consistent recovery of resources and application components in
the right order either on the same server or on another server within the
cluster.
- IBM Automation Package Development Environment (APDE) updates
-
The APDE is an eclipse plug-in that provides a development environment for
developingTivoli Intelligent Orchestrator and Tivoli Provisioning Manager
workflows and automation packages. V3.1.0.2 comes
with a new and improved version of the Rembo automation package as well as
other updates. To download the automation packages :
- Go to http://www.ibm.com/software/ondemandcatalog/automation.
- The IBM Automation Package Development Environment - eclipse plug-in can
be found by entering apde in the search box.
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. 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
Provisioning Manager and Tivoli Intelligent Orchestrator products.
To access the forum:
- Go to the Web site,http://www-128.ibm.com/developerworks/forums/tivoli_forums.jsp
- Click on the Tivoli Provisioning Manager and Intelligent Orchestrator
Automation Package Development Environment link on the Web sit
Fix pack V 3.1.0.2 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-FP0002.DEFECTS or
3.1.0.1-TIV-TPM-FP0002.DEFECTS.
To download the defects list:
- Go to the IBM(R) Support Web site:
http://www.ibm.com/support
- In the Support topics list, click Downloads and
Drivers.
- In the Browse product support section, under
Software list, click Tivoli.
- In the search box, enter the fix pack number:
- For the Tivoli Intelligent Orchestrator Fix Pack V
3.1.0.2, enter:
3.1.0.1-TIV-TIO-FP0002.
- For the Tivoli Provisioning Manager Fix Pack V
3.1.0.2, enter:
3.1.0.1-TIV-TPM-FP0002.
- Click Search. The Download Results page is
displayed.
- On the Download Results page, depending on your search, one of the
following links is displayed:
- Tivoli Intelligent Orchestrator Fix Pack
3.1.0.1-TIV-TIO-FP0002
- Tivoli Provisioning Manager Fix Pack
3.1.0.1-TIV-TIO-FP0002
- Click on the displayed link. The corresponding page is
displayed.
- For a list of defects that are corrected by this fix pack, click on
3.1.0.1-TIV-TIO-FP0002-DEFECTS (HTTP)
or 3.1.0.1-TIV-TPM-FP0002-DEFECTS
(HTTP).
Fix Pack V 3.1.0.2 supports all the hardware and
software that is supported by Tivoli Intelligent Orchestrator V
3.1.0 and Tivoli Provisioning Manager V
3.1.0.
If you have the various Tivoli Intelligent Orchestrator and Tivoli
Provisioning Manager components distributed in a multi-node installation, the
fix pack must be applied to the application server node where Tivoli
Intelligent Orchestrator or Tivoli Provisioning Manager 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 2.
Thoroughly review the following list of prerequisites for installation
before proceeding with the installation:
- Determine that the version of Tivoli Intelligent Orchestrator or Tivoli
Provisioning Manager installed on the machine is operational before you begin
the installation of Fix pack 2. The fix pack is compatible with the
following versions of Tivoli Intelligent Orchestrator or Tivoli Provisioning
Manager:
- Version 3.1.0.0
- Note:
- If you are installing Tivoli Intelligent Orchestrator Version 3.1 or
Tivoli Provisioning Manager 3.1 for the first time, you can choose to
initialize the database just once, during the Fix pack
3.1.0.2, post installation step. This will lessen
the time it takes to install the application. Follow the steps in the
section Installing Version 3.1 and Fix Pack, Version 3.1.0.2 to install Tivoli Intelligent Orchestrator Version
3.1 or Tivoli Provisioning Manager 3.1 and the fix pack,
V3.1.02. for each product.
- Version 3.1.0.1
- You must install and configure all components of Tivoli Intelligent
Orchestrator Version 3.1 or Tivoli Provisioning Manager 3.1
before attempting the installation of Fix pack V
3.1.0.2. This includes setting up the database
that you plan to use, LDAP, and so on.
This section provides a roadmap, a checklist and links to additional
information in the readme to assist you in installing Fix Pack V
3.1.0.2.
Use this road map to install Fix Pack V 3.1.0.2
successfully:
- Determine if you have the required CDs and hardware to install the Fix
Pack.
- Determine which operating system you are going to install the Fix Pack and
and which version. The Fix Pack supports all the previously supported
versions that Tivoli Intelligent Orchestrator V3.1 or Tivoli
Provisioning Manager V3.1 supported. For more information refer
to the section, Product compatibility.
- Complete the preinstallation instructions, while referring to the section,
Pre-installation instructions.
- Install the Fix pack for Tivoli Intelligent Orchestrator or Tivoli
Provisioning Manager, as described in the section, Installation of the fix pack.
- Complete the post-installation steps after you install the fix
pack. Read the information in the section, "Post-installation steps" for more information.
Use this checklist to ensure that you complete all the steps required in
the installation of the Fix Pack.
Table 1. Installation of the Fix Pack V3.1.0.2
Use this table below to refer to additional information in the
readme.
Table 2. Additional Information
The online help documentation is updated for Fix Pack V
3.1.0.2 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 and Tivoli Provisioning Manager 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:
- Go to http://www.ibm.com/software/tivoli/products/intell-orch/
- Click Technical documentation on the left.
- Select and save the information center plugin to a temporary directory on
your local system.
For Tivoli Provisioning Manager publications:
- Go to http://www.ibm.com/software/tivoli/products/prov-mgr/
- Click Technical documentation on the left.
- Select and save the information center plugin to a temporary directory on
your local system.
To install the updated source on your Tivoli Provisioning Manager or Tivoli
Intelligent Orchestrator server, follow the instructions below, according to
your operating system:
- AIX, Linux or Solaris
-
- Stop your Tivoli Provisioning Manager or Tivoli Intelligent Orchestrator
server
- Copy the downloaded plugin ZIP file from the temporary directory to
$TIO_HOME/help/eclipse/plugins
- Note down the ownership and permissions on the
com.ibm.tivoli.tio.doc
directory. For example, run this command from a command prompt:
ls -la com.ibm.tivoli.tio.doc
- Move the com.ibm.tivoli.tio.doc
directory to a backup location
- Unzip the plugin ZIP file
- Apply the ownership and permissions to the new directory and contents to
ensure it matches the original. For example:
chown tioadmin:Administrators com.ibm.tivoli.tio.doc
chmod -R 770 com.ibm.tivoli.tio.doc
- Navigate to
$TIO_HOME/help/eclipse/configuration/org.eclipse.help.base/
folder.
- Backup and delete the index folder. This will force a reindexing of
the files extracted above, or else you will not be able to search through the
updated files.
- Start your Tivoli Provisioning Manager or Tivoli Intelligent Orchestrator
server and confirm the updated Online Help is up and running.
- Windows
-
- Stop your Tivoli Provisioning Manager or Tivoli Intelligent Orchestrator
server
- Copy the downloaded plugin ZIP file from the temporary directory to
%TIO_HOME%\help\eclipse\plugins
- Note down the ownership and permissions on the
com.ibm.tivoli.tio.doc
directory.
For example:
- Right-click the folder that you want to check the ownership, and then
click Properties.
- Click the Security tab.
- Click the Advanced tab.
- Click the Owner tab. Note down the ownership.
- Move the com.ibm.tivoli.tio.doc
directory to a backup location
- Unzip the plugin ZIP file
- Apply the ownership and permissions to the new directory and contents to
ensure it matches the original.
- Navigate to
%TIO_HOME%\help\eclipse\configuration\org.eclipse.help.base
folder.
- Backup and delete the index folder. This will force a
re-indexing of the files extracted above, or else you will not be able
to search through the updated files.
- Start your Tivoli Provisioning Manager or Tivoli Intelligent Orchestrator
server and confirm the updated Online Help is up and running.
When you click on the Help button, on the user interface of
Tivoli Intelligent Orchestrator or Tivoli Provisioning Manager, 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.
- Note:
- To ensure proper printing of PDF publications, select the Fit to
page check box in the Adobe Acrobat Print window (which is available
when you click File > Print).
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.
You will need to upgrade the WebSphere Application Server
5.1.1.3, installed with Tivoli Intelligent Orchestrator
3.1 or Tivoli Provisioning Manager 3.1 to WebSphere Application
Server 5.1.1.5 . This cumulative fix is required
for all Windows, Linux, AIX or Solaris systems.
Follow the instructions below:
- Install the Cumulative Fix 5 on top of IBM WebSphere Application Server
Version 5.1.1. This collection of fixes for version
5.1.1 will update WebSphere Application Server to Version
5.1.1.5. The cumulative fix can be obtained from
http://www-1.ibm.com/support/docview.wss?uid=swg24009883.
Refer to the readme in the Web site for installation instructions.
- Install V5.1.1 Cumulative Fix 2 for SDKs on top of WebSphere
Application Server Version 5.1.1.5 and refer to the
readme on the Web site for installation instructions.
The Cumulative Fix 2 for SDKs can be obtained from :
- Note:
- Applying this cumulative fix on Microsoft Windows, Linux and AIX, will
upgrade your SDK to 1.4.2 Java Technology Edition SR2.
The cumulative fix for HP-UX will upgrade to
1.4.2.08. The cumulative fix for Solaris will
upgrade to 1.4.2_08-b03.
A new report named, Patch Compliance by Installation Progress,
has been added to Tivoli Intelligent Orchestrator and Tivoli Provisioning
Manager in FP0002. This report requires the values of some of the DB2
configuration parameters to be increased.
Increase the values of the following parameters for DB2:
- app_ctl_heap_sz: The Application control heap size
parameter specifies the maximum size, in 4-KB pages, for the application
control shared memory. The default value for the
APP_CTL_HEAP_SZ parameter is 128
- applheapsz: The Application heap size parameter value is
increased to ensure that there is enough storage in the application
heap.
- stmtheap: The Statement heap size configuration parameter
is used as a work space for the SQL compiler during compilation of an SQL
statement. Increasing the value of this parameter increases the size of
this work space.
To increase the value of the heap size of app_ctl_heap_sz
parameter in DB2, follow the instructions below:
- On Windows
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using app_ctl_heap_sz 256
- Restart DB2 for the changes to take effect
- On AIX, Solaris, Linux
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using app_ctl_heap_sz 256
- Restart DB2 for the changes to take effect
To increase the value of the heap size of applheapsz parameter
in DB2, follow the instructions below:
- On Windows
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using applheapsz 4096
- Restart DB2 for the changes to take effect
- On AIX, Solaris, Linux
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using applheapsz 4096
- Restart DB2 for the changes to take effect
To increase the value of the Statement heap size configuration parameter
(stmtheap) parameter in DB2, follow the instructions below:
- On Windows
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using STMTHEAP 3072
- Restart DB2 for the changes to take effect
- On AIX, Solaris, Linux
-
- At a DB2 prompt type the following command and press
Enter. Replace the variable,
DB2_DB_NAME with the name of the DB2 database.
db2 update db cfg for DB2_DB_NAME using STMTHEAP 3072
- Restart DB2 for the changes to take effect
On the Tivoli Intelligent Orchestrator server or Tivoli Provisioning
Manager server, create a temporary directory into which you will place the fix
pack ZIP file.
- Windows
-
To create the temporary directory, run the following command:
- AIX, Solaris and Linux
-
To create the temporary directory, run the following command:
The directory must meet the following criteria:
- Exists outside the Tivoli Intelligent 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.
Complete the following instructions to unzip Fix Pack V
3.1.0.2. These instructions are applicable to all
the operating systems supported by IBM for Fix Pack V
3.1.0.2.
- Windows
-
- Log on to the server as Administrator.
- Copy the fix pack package to temp\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.
- On AIX, Solaris and Linux
-
- Log on to the server as root .
- Copy the fix pack package to tmp/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.
Complete the following instructions to run the clean-up-deployment-requests
script. These instructions are applicable to all the operating systems
supported by IBM for Fix Pack V 3.1.0.2.
- Windows
-
- Start Tivoli Intelligent Orchestrator or Tivoli Provisioning
Manager. For more information, refer to the section, Administering
Tivoli Intelligent Orchestrator or Tivoli Provisioning Manager in the
Installation guide for Windows.
- Open a command window.
- Switch to the %TIO_HOME%\tools directory where
%TIO_HOME% is the Tivoli Intelligent Orchestrator installation
directory.
- Run the following command:
clean-up-deployment-requests.cmd
- On AIX, Solaris and Linux
-
- Start Tivoli Intelligent Orchestrator or Tivoli Provisioning
Manager. For more information, refer to the section, Administering
Tivoli Intelligent Orchestrator or Tivoli Provisioning Manager in the
Installation guide.
- Open a command window.
- Switch to the $TIO_HOME/tools directory where
$TIO_HOME is the Tivoli Intelligent Orchestrator installation
directory.
- Run the following command:
clean-up-deployment-requests.sh
This section describes the installation of the fix pack.
The section has instructions to install Fix Pack V
3.1.0.2 on a Windows system using the graphic installer
as well as using the silent installer.
To install Fix Pack V 3.1.0.2 on Windows systems using
the graphic installer:
- From a command prompt, log in to the Tivoli Intelligent Orchestrator
server or Tivoli Provisioning Manager server as Administrator
- Note:
- Open the command prompt from within Windows (either locally or using remote
desktop) but not remotely using SSH.
- Ensure that the database server is running.
- If your directory server is IBM Tivoli Directory Server, and is
running on a Windows operating system, then make the following changes to the
configuration file, ibmslapd.conf:
- Stop the IBM Tivoli Directory Server.
- Save a copy of the configuration file, ibmslapd.conf
located at C:\IBM\ldap\etc.
- Open the original file in a text editor and insert the following line in
the section that starts with dn: cn=Front End,
cn=Configuration:
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
- Restart the IBM Tivoli Directory Server.
- Ensure that the Tivoli Intelligent Orchestrator server or the Tivoli
Provisioning Manager server is stopped.
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- WAS_HOME variable
-
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
- JAVA_HOME variable
-
echo %JAVA_HOME%
The output would be similar to this:
C:\IBM\WebSphere\AppServer\java
- 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 Orchestrator or Tivoli Provisioning Manager
installation. To work around this limitation:
- In the Installation Directory box, if the installation
directory is not specified, select the Specify product information
check box.
- 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. Review the log files located in
%TIO_HOME%\logs\update directory for any errors.
To install Fix Pack V 3.1.0.2 on Windows systems using
the silent mode:
- From a command prompt, log in to the Tivoli Intelligent Orchestrator
server or Tivoli Provisioning Manager server as Administrator
- Note:
- Open the command prompt from within Windows (either locally or using remote
desktop) but not remotely using SSH.
- Ensure that the database server is running.
- If your directory server is IBM Tivoli Directory Server, is running on a
Windows operating system, then make the following changes to the configuration
file, ibmslapd.conf:
- Stop the IBM Tivoli Directory Server.
- Save a copy of the configuration file, ibmslapd.conf
located at C:\IBM\ldap\etc.
- Open the original file in a text editor and insert the following line in
the section that starts with dn: cn=Front End,
cn=Configuration:
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
- Restart the IBM Tivoli Directory Server.
- Ensure that the Tivoli Intelligent Orchestrator server or the Tivoli
Provisioning Manager server is stopped.
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- WAS_HOME variable
-
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
- JAVA_HOME variable
-
echo %JAVA_HOME%
The output would be similar to this:
C:\IBM\WebSphere\AppServer\java
- 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 following command
to to launch the installation using the silent mode:
updateSilent.bat -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example:
updateSilent.bat -fixpack -install "C:\Program Files\IBM\tivoli\thinkcontrol" tio31_fp2_win "C:\temp\update_installer_dir\installer"
- The system completes the installation. A successful installation
gives an error level of 0. Review the log files located in
%TIO_HOME%\logs\update directory for any errors.
The section has instructions to install Fix Pack V
3.1.0.2 on AIX(R) , Linux(TM), or Solaris systems
using the graphic installer as well as using the silent installer.
To install Fix Pack V 3.1.0.2 on AIX , Linux, or
Solaris systems using the graphic installer:
- Log in to the Tivoli Intelligent 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 Orchestrator server or the Tivoli
Provisioning Manager server is stopped.
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- WAS_HOME variable
-
echo $WAS_HOME
The WAS_HOME variable is the location of the WebSphere
Application Server and the output would be similar to this:
/usr/WebSphere/AppServer
- JAVA_HOME variable
-
echo $JAVA_HOME
The output would be similar to this:
/usr/WebSphere/AppServer/java
- 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 Orchestrator or Tivoli Provisioning Manager
installation. To work around this limitation:
- In the Installation Directory box, if the installation
directory is not specified, select the Specify product information
check box.
- 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. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
To install Fix Pack V 3.1.0.2 on AIX , Linux, or
Solaris systems using the silent mode:
- Log in to the Tivoli Intelligent 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 Orchestrator server or the Tivoli
Provisioning Manager server is stopped.
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- WAS_HOME variable
-
echo $WAS_HOME
The WAS_HOME variable is the location of the WebSphere
Application Server and the output would be similar to this:
/usr/WebSphere/AppServer
- JAVA_HOME variable
-
echo $JAVA_HOME
The output would be similar to this:
/usr/WebSphere/AppServer/java
- 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 the following command
to to launch the installation using the silent mode:
updateSilent.sh -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to install on AIX systems:
updateSilent.sh -fixpack -install /opt/IBM/tivoli/thinkcontrol tio31_fp2_aix /tmp/update_installer_dir/installer
- The system completes the installation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
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:
- 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 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.
- Log in as user tiodamin.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- Open a DOS command prompt.
- 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.
- To deploy the zip files, from a Windows command prompt, run the following
command:
postinstall.bat was_user was_pwd server base_DN
For example:
postinstall.bat wasadmin wasadmin server1 "dc=mycompany,dc=com"
Notes:
- At the Windows command prompt, replace the variables with the correct
values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server
- Note:
- The correct value for base_DN can be obtained from the XML tag
<root> in
%TIO_HOME%\config\user-factory.xml.
- The log files can be found in the directory:
%TIO_LOGS%\fixpack.
To complete the post installation procedure onLinux systems, follow the
instructions below to run the postinstall.sh script:
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 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.
- Log in as user root.
- Set the file size limit to 20000 as below:
ulimit -n 20000
- In the same session, change to tioadmin. If you are
using the su command to change totioadmin ensure that
you use su -. Note the hyphen after su.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- 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.
- To deploy the EAR (expanded archive) files and database schema change, run
the following command:
postinstall.sh was_user was_pwd server base_DN
For example:
postinstall.sh wasadmin wasadmin server1 "dc=mycompany,dc=com"
Notes:
- Replace the variables with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- The log files can be found in the directory:
$TIO_LOGS/fixpack.
- Note:
- Restart the system if you get an error similar to this and then reset the the
ulimit size as above after restarting the system.
Too many open files
To complete the post installation procedure on AIX or Solaris, follow the
instructions below to run the postinstall.sh script:
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 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.
- Change the timeout values in the file,
soap.client.props. Follow the instructions in
the section, Changing the timeout value on AIX and Solaris systems, only if you encounter a timeout related error while running
the postinstall.sh script
This section provides instructions on changing the
com.ibm.SOAP.requestTimeout property of the
soap.client.props file on AIX and Solaris
systems.
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.sh script:
- Open the soap.client.props file located in the
properties directory of the WebSphere Application Server profile.
- Specify the value of 1800 seconds for the property,
com.ibm.SOAP.requestTimeout as indicated
below.
- Note:
- The value that you choose depends on a number of factors such as the size and
the number of the applications that are installed on the server, the speed of
your machine, and the level of usage of your machine.
Table 3. com.ibm.SOAP.requestTimeout values
| Component
| Value
|
| Property
| com.ibm.SOAP.requestTimeout
|
| Data type
| Integer
|
| Range in seconds
| 0 to n
- Note:
- If the property is zero (0), the request never times out.
|
| Default
| 1800
|
- On AIX and Solaris systems, change the timeout value for
soap.client.props file. For more information,
refer to the section, "Changing the timeout value on AIX and Solaris systems".
- Log in as user tioadmin.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- 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.
- To deploy the EAR (expanded archive) files, run the following
command:
postinstall.sh was_user was_pwd server base_DN
For example:
postinstall.sh wasadmin wasadmin server1 "dc=mycompany,dc=com"
Notes:
- Replace the variables with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- The log files can be found in the directory:
$TIO_LOGS\fixpack.
Complete the following instructions to uninstall the fix pack.
Before you uninstall the fix pack:
- Ensure that the database server and the directory server are both
running.
- Stop the Tivoli Intelligent 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.
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.2 on Windows using
graphic uninstaller:
- From a command prompt, log in to the Tivoli Intelligent Orchestrator
server or Tivoli Provisioning Manager server as Administrator
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- Note:
- The WAS_HOME variable is the location of the WebSphere Application
Server and the JAVA_HOME variable is set to
WAS_HOME\java
- 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 Orchestrator or Tivoli Provisioning Manager
installation. To work around this limitation:
- In the Installation Directory box, if the installation
directory is not specified, select the Specify product information
check box.
- 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.
To uninstall Fix Pack V 3.1.0.2 on Windows using the
silent uninstaller:
- From a command prompt, log in to the Tivoli Intelligent Orchestrator
server or Tivoli Provisioning Manager server as Administrator
- On the Tivoli Intelligent Orchestrator server or the Tivoli Provisioning
Manager server, ensure that both the JAVA_HOME and
WAS_HOME environment variables are set.
- Note:
- The WAS_HOME variable is the location of the WebSphere Application
Server and the JAVA_HOME variable is set to
WAS_HOME\java
- 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 following command,
from a Windows Command prompt, to launch the uninstallation using the silent
mode:
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_fp2_win "C:\Program Files\IBM\temp\installer"
- The system completes the installation. A successful installation
gives an error level of 0. Review the log files located in
%TIO_HOME%\logs\update directory for any errors.
This section provides instructions on uninstalling the fix pack on
Linuxsystems using the graphic mode.
To uninstall Fix Pack V 3.1.0.2 on Linux
systems:
- Log in to the Tivoli Intelligent 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 Orchestrator or Tivoli Provisioning Manager
installation. To work around this limitation:
- In the Installation Directory box, if the installation
directory is not specified, select the Specify product information
check box.
- 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.
To uninstall Fix Pack V 3.1.0.2 on, Linux systems
using the silent mode:
- Log in to the Tivoli Intelligent 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 the following command
to to launch the uninstallation using the silent mode:
updateSilent.sh -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to uninstall the fix pack on AIX systems:
updateSilent.sh -fixpack -uninstall /opt/IBM/tivoli/thinkcontrol tio31_fp2_aix
- The system completes the uninstallation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
This section provides instructions on uninstalling the fix pack on AIX or
Solaris systems.
To uninstall Fix Pack V 3.1.0.2 on AIX or Solaris
systems using the graphic mode:
- Log in to the Tivoli Intelligent 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 Orchestrator or Tivoli Provisioning Manager
installation. To work around this limitation:
- In the Installation Directory box, if the installation
directory is not specified, select the Specify product information
check box.
- 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.
To uninstall Fix Pack V 3.1.0.2 on AIX or Solaris
using the silent mode:
- Log in to the Tivoli Intelligent 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 the following command
to to launch the uninstallation using the silent mode:
updateSilent.sh -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to uninstall the fix pack on AIX systems:
updateSilent.sh -fixpack -uninstall /opt/IBM/tivoli/thinkcontrol tio31_fp2_aix
- The system completes the uninstallation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
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:
- Log in to the Tivoli Intelligent Orchestrator server or the Tivoli
Provisioning Manager server as user tioadmin.
- Start the WebSphere Application Server.
- Run the command given below from a Cygwin command prompt:
"$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"
- Note:
- Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- Stop the WebSphere Application Server.
To redeploy the EAR files:
- Log in to the Tivoli Intelligent Orchestrator server or the Tivoli
Provisioning Manager server as user tioadmin.
- Start the WebSphere Application Server.
- Run the command given below:
"$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"
- Note:
- Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- Stop the WebSphere Application Server.
To redeploy the EAR files:
- Log in to the Tivoli Intelligent Orchestrator server or the Tivoli
Provisioning Manager server as user tioadmin.
- On Linux systems only, you will need to set the file size limit to 20000
as below:
ulimit -n 20000
- Start the WebSphere Application Server.
- Run the command given below:
"$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"
- Note:
- Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- Note:
- Restart the system if you get an error similar to this and then reset the the
ulimit size as above after restarting the system.
Too many open files
- Stop the WebSphere Application Server.
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
Version 3.1 or Tivoli Provisioning Manager 3.1 and Fix pack
V3.1.0.2
- Determine the type of network topology desired as described in the
section, "Supported server topologies and required CDs" in the Planning for
installation guide.
- Ascertain the type of installation desired as described in the section,
"Installation options" in the Planning for installation guide.
- Ascertain the hardware and software requirements for your Tivoli
Provisioning Manager installation as described in the section, "Planning the
requirements" in the Planning for installation guide.
- Complete the worksheets provided in the section "Installation planning" in
the Planning for installation guide.
- Install the system prerequisites for Tivoli Provisioning Manager as
described in the section, Part 2. Preparing for the
installation.
- While referring to the Installation guide, start the installation wizard
for Tivoli Intelligent Orchestrator V 3.1.0 or Tivoli
Provisioning Manager V 3.1.0 using the following command.
This option will prevent the initialization of the database by the
installer.
- Note:
- The commands given in the installation guide do not have the parameter to
suppress the initialization of the database, as in the example of the command,
provided in this readme.
- Windows
-
setupwin32.exe -P ProdFeat_Reinit.active="false"
- Linux on iSeries and pSeries
- Start the installer by typing the following command:
mount_point/setuplinuxppc.bin -P ProdFeat_Reinit.active="false"
- Linux on Intel
- Start the installer by typing the following command:
mount_point/setuplinux.bin -P ProdFeat_Reinit.active="false"
- AIX
- Start the installer by typing the following command:
mount_point/setupaix.bin -P ProdFeat_Reinit.active="false"
- Solaris
- Start the installer by typing the following command:
mount_point/setupsolarisSparc.bin -P ProdFeat_Reinit.active="false"
- Follow the instructions in the section, "Pre-installation instructions", in this readme to complete the preinstallation
instructions.
- Follow the instructions in the section, "Installation of the fix pack", in this readme to complete the fix pack installation
instructions.
- The database needs to be initialized in the post installation steps, since
the option not to initialize it was selected during the installation of Tivoli
Intelligent Orchestrator Version 3.1 or Tivoli Provisioning Manager
3.1. Ensure that you initialize the database using the
"init" option in the post installation script.
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 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.
- Change the timeout values in the file,
soap.client.props. Follow the instructions in
the section, Changing the timeout value on AIX and Solaris systems, only if you encounter a timeout related error while running
the postinstall.sh script
Complete the following instructions after you install the fix pack.
- Windows
- Follow the steps in the section below, to complete the required post
installation steps on Windows:
- Log in as user tiodamin.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- 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.
- To deploy the zip files, from a Windows command prompt, run the following
command:
postinstall.bat was_user was_pwd server base_DN init
For example:
postinstall.bat wasadmin wasadmin server1 "dc=mycompany,dc=com" init
Notes:
- The option init is used to initialize the database if it was
skipped during the installation of Tivoli Intelligent Orchestrator Version
3.1 or Tivoli Provisioning Manager Version 3.1
installation.
- At the Windows command prompt, replace the variables with the correct
values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server
- Note:
- The correct value for base_DN can be obtained from the XML tag
<root> in
%TIO_HOME%\config\user-factory.xml.
- The log files can be found in the directory:
%TIO_LOGS%\fixpack.
- AIX and Solaris
- Follow the steps in the section below, to complete the required post
installation steps on AIX and Solaris:
- On Solaris systems, change the timeout value for
soap.client.props file. For more information,
refer to the section, "Changing the timeout value on AIX and Solaris systems".
- Log in as user tioadmin.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- 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.
- To deploy the EAR (expanded archive) files, run the following
command:
postinstall.sh was_user was_pwd server base_DN init
For example:
postinstall.sh wasadmin wasadmin server1 "dc=mycompany,dc=com" init
Notes:
- The option init is used to initialize the database if it was
skipped during the installation of Tivoli Intelligent Orchestrator Version
3.1 or Tivoli Provisioning Manager Version 3.1
installation.
- Replace the variables with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- The log files can be found in the directory:
$TIO_LOGS\fixpack.
- Linux
- Follow the steps in the section below, to complete the required post
installation steps on Linux:
- Log in as user root.
- Set the file size limit to 20000 as below:
ulimit -n 20000
- In the same session, change to tioadmin. If you are
using the su command to change totioadmin ensure that
you use su -. Note the hyphen after su.
- Ensure that the database server and the directory server are
running.
- Ensure that the WebSphere Application Server is stopped.
- 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.
- To deploy the EAR (expanded archive) files and database schema change, run
the following command:
postinstall.sh was_user was_pwd server base_DN init
For example:
postinstall.sh wasadmin wasadmin server1 "dc=mycompany,dc=com" init
Notes:
- The option init is used to initialize the database if it was
skipped during the installation of Tivoli Intelligent Orchestrator Version
3.1 or Tivoli Provisioning Manager Version 3.1
installation.
- Replace the variables with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name. For
more information refer to the section, "Known problems and workarounds".
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- The log files can be found in the directory:
$TIO_LOGS/fixpack.
- Note:
- Restart the system if you get an error similar to this and then reset the the
ulimit size as above after restarting the system.
Too many open files
This section describes known limitations in this release of Tivoli
Intelligent Orchestrator V 3.1.0 and Tivoli Provisioning Manager
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.
After installation of the product, an LDAP update error may occur on AIX
due to a memory related problem. This file can be found in
/etc/security/limits.
To configure the AIX memory file setting:
root:
rss = -1
ldap:
data = -1
rss = -1
tioadmin:
data = -1
rss = -1
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 or Tivoli Provisioning
Manager server.
To prevent such errors from occurring:
- Check the .profile or /etc/profile file of
the user, for commands similar to the one below, before installing the agent
:
- Note:
- The command below is just a sample representation of the
.profile file.
if [ ! "$VUE" ]; then
# other terminal commands
tabs
fi
- If the commands exist in the .profile or
/etc/profile file , run the command below:
if [ ! "$VUE" ] && [[ -t 0 ]]; then
# other terminal commands
tabs
fi
- Note:
- If you have a terminal attached to the shell and are not using the Visual
User Environment , adding && [[ -t 0 ]] to the command,
ensures the successful run of the command.
- Install the agent using the Add Server Wizard. For more information
refer to the online help.
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:
- Stop the IBM Tivoli Directory Server.
- Save a copy of the configuration file, ibmslapd.conf
located at C:\IBM\ldap\etc.
- Open the original file in a text editor and insert the following line in
the section that starts with dn: cn=Front End,
cn=Configuration:
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
- Restart the IBM Tivoli Directory Server.
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:
- Login as tioadmin.
- Go to Start > Programs > Administrative tools.
- Start Local Security Policy Management console.
- In that console go to: Local Policies >User Rights
Assignment.
- Add tioadmin user to the Log on as service
property.
This section provides workarounds to problems that you might encounter
after the installation of the Fix pack and after running the post installation
scripts.
After running the postinstall.bat script on Windows or
running the postinstall.sh script on AIX, Linux or Solaris,
you may get an error message, similar to the example below:
1d2086c3 XARecoveryDat E WTRN0040W:
Object cannot be deserialized. The exception stack trace follows:
java.lang.reflect.InvocationTargetException
- Delete all the contents under the following directories:
- $WAS_HOME/partnerlog
- $WAS_HOME/tranlog
- Restart the WebSphere Application Server
Given below are the two probable situations where you might encounter this
problem:
- If the FP2 graphic installer is run successfully and you re- run
UpdateWizard or UpdateSilent to check if Fix Pack 2 is installed, then the TC
drivers do not get installed during the post-installation.
- If FP2 silent installer is run successfully and you re-run
UpdateWizard or UpdateSilent to check if Fix Pack 2 is installed, then the TC
drivers do not get installed during the post-installation.
- On Windows
-
- Go to directory to
update_installer_dir\installer\utils where
update_installer_dir is the directory in which you unzipped the fix
pack ZIP file.
- Locate the build-version.properties file.
- Open the file and determine the value for the
current.version entry.
- If the entry is 3.1.0.2, then make the following
changes:
- If you have Version 3.1.0.0 installed and are
installing Fix pack 2, then replace the entry
3.1.0.2 with
3.1.0.0
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
- If you have Version 3.1.0.1 installed and are
installing Fix pack 2, then replace 3.1.0.2
with 3.1.0.1
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
- On AIX, Solaris and Linux
-
- Go to directory to
update_installer_dir/installer/utils where
update_installer_dir is the directory in which you unzipped the fix
pack ZIP file.
- Locate the build-version.properties file.
- Open the file and determine the value for the
current.version entry.
- If the entry is 3.1.0.2, then make the following
changes:
- If you have Version 3.1.0.0 installed and are
installing Fix pack 2, then replace the entry
3.1.0.2 with
3.1.0.0.
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
- If you have Version 3.1.0.1 installed and are
installing Fix pack 2, then replace 3.1.0.2
with 3.1.0.1.
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 if
you are installing patches on your target machines.
The Tivoli Intelligent Orchestrator V 3.1 installation includes an
automation package for Microsoft Software Update Services (SUS). Before
you can begin managing patches, you must ensure that your infrastructure is
properly configured to work with Tivoli Intelligent Orchestrator for patch
management. The instructions for managing patches are provided in the
online help in the section, Scenarios, which discusses the
Patch Management Overview scenario.
Here are the summary of changes in Fix pack 2 for patch management:
- Earlier, in V3.1, you needed to run only the the
MBSA_Get_CAB workflow that used to copy the
mssecure.cab file and in turn call the
MS_SUS_Get_ApprovedItems workflow to obtain a list of approved
patches from the SUS server. The CIT scanner was used as a discovery
technology before installing the patch. You will now need to run the
MS_SUS_Get_ApprovedItems workflow separately after running the
MBSA_Get_CAB workflow and do not required the CIT scanner to run
the discovery.
- MBSA is used only for scanning target systems for missing patches in the
SUS patch management scenarios.
- Windows Update Agent (WUA) is used only for scanning target systems for
missing patches in the Windows Server Update Services (WSUS) patch management
scenarios.
- Note:
- You can continue to use the CIT scanner for inventory scans only, but in the
case of case of WSUS patch management, CIT is no longer relying on MBSA for
doing the inventory scans. Hence, to summarize, CIT is no longer used
for doing inventory scans in patch management scenarios in FP2.
To schedule Microsoft Baseline Security Analyzer configuration
updates:
- Get the Device ID of the SUS file repository
- Before you can schedule the MS_SUS_Get_ApprovedItems workflow,
you must first get the device id of the file repository as a parameter for the
workflow. The device ID of the SUS file repository is essentially the
numeric identifier of the device.
To get the device ID of the file repository, follow the steps below:
- In the navigation pane, click Inventory > Infrastructure Management >
File Repositories.
- Identify the SUS file repository and hover your mouse over it.
- The value of the device is displayed on a mouse-over. Note
down the value of the file repository.
- Schedule the MBSA_Get_CAB workflow
- To schedule the MBSA_Get_CAB workflow:
- In the navigation pane, click Configuration > Workflow
Scheduler.
- Click New.
- Schedule the MBSA_Get_CAB workflow:
- In the Name field, type a name for the workflow. Provide
a unique and meaningful name for the workflow or logical device operation so
that you can easily identify it later. For example, you could name this
item, "Update mssecure file".
- In the Start Time and End Time, sections, specify
the period when you want to run the workflow.
- Note:
- Select the start time to be a few minutes after the current time to schedule
this workflow. This will prevent the workflow from running immediately
and would allow some time for you to define the parameter, required for the
workflow.
- Specify how often to run the workflow in the Repeat Option
section.
- Select the MBSA_Get_CAB workflow.
- Click Save. The workflow is now created. Each
time the MBSA_Get_CAB workflow runs, it copies the
mssecure.cab file from the SUS server to the Tivoli
Intelligent Orchestrator server.
Next Steps: You will now need to schedule the
MS_SUS_Get_ApprovedItems workflow.
- Schedule the MS_SUS_Get_ApprovedItems workflow
- To schedule the MS_SUS_Get_ApprovedItems workflow:
- In the navigation pane, click Configuration > Workflow
Scheduler.
- Click New.
- In the New Scheduled Workflow window, specify the appropriate
options:
- In the Name field, type a name for the workflow. Provide
a unique and meaningful name for the workflow or logical device operation so
that you can easily identify it later. For example, you could name this
item, "Update msus".
- In the Start Time and End Time, sections, specify
the period when you want to run the workflow.
- Note:
- Select the start time to be a few minutes after the current time to schedule
this workflow. This will prevent the workflow from running immediately
and would allow some time for you to define the parameter, required for the
workflow.
- Specify how often to run the workflow in the Repeat Option
section.
- Select the MS_SUS_Get_ApprovedItems workflow.
- Click Save. The workflow is now created. Each
time the MS_SUS_Get_ApprovedItems workflow runs, the list of
approved patches from the SUS server is updated. The list of approved
items ensures that patch recommendations are only based on approved patches
Next Steps: Tivoli Intelligent Orchestrator creates the
scheduled item and displays the screen to add the parameters to the
workflow. You will now need to assign the device ID of the SUS file
repository as a parameter to the workflow.
- Add parameters to the MS_SUS_Get_ApprovedItems workflow
-
Once the workflow is scheduled , the parameters that are required for the
scheduled workflow are displayed under the Workflow Arguments list
in the Scheduled Workflow screen. To add the Device ID parameter to the
workflow:
- Identify the parameter, DeviceID, under the Workflow
Arguments list and click More > Edit.
- In the Edit Workflow Argument window, type the value for the device ID,
that you had obtained initially, while performing the steps in the section,
"Get the Device ID of the SUS file repository".
- Click Save. The parameter, device ID is updated with the
new value. The new value is applied the next time the scheduled
workflow runs.
Installing the Microsoft patch Q816093 causes a pop-up window to be
displayed. The pop-up Window is displayed if you run the patch
in a logged on session for example, using VNC or Terminal Services
Client.
This is because the some of the Java Patches from Microsoft do not get the
right parameters from Microsoft SUS Server. To continue with the
installation of the patch:
- Click OK on the pop-up window.
- Obtain the information, required for the patch, from the pop-up
window.
- Modify the Software Resource Templates for the patch as required.
If you are using trying to install the SUS patch on Windows 2000 endpoints,
you might see some errors if you do not have bash installed on the end
points.
To prevent such errors from occurring, you either need to have
installed:
This section provides workarounds to problems that you might encounter at
some instances while using Tivoli Intelligent Orchestrator V
3.1.0 or Tivoli Provisioning Manager 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:
- Stop: The deployment engine stops the deployment request
at the next low level workflow instruction.
- Forced stop: The deployment engine tries to stop the
deployment request immediately.
- Note:
- Using this option can cause undesirable results such as hanging processes,
open file handles.
Use the regular stop command to cancel a workflow to prevent this error
from occuring. To cancel a workflow, follow the instructions
below:
- Click View > Configuration and click Deployment
Requests.
- Search for the deployment request for the workflow that you want to
cancel.
- Click the Request ID of the workflow. The Execution Logs
page is displayed.
- In the search results, find the row that contains the deployment request
to cancel. In that row, click the More button.
- To stop the workflow at the next instruction, click Stop
Execution.
This section provides some limitations that you might encounter while using
Tivoli Intelligent Orchestrator V 3.1.0 or Tivoli Provisioning
Manager V 3.1.0.
Tivoli Intelligent Orchestrator or Tivoli Provisioning Manager 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 and Tivoli Provisioning Manager 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.
- Windows DB2 password requirements
-
- Windows 32-bit user names and passwords can contain 1 to 20
characters.
- Passwords cannot contain or special characters.
- Group and instance names can contain 1 to 8 characters.
- The DB2 usernames cannot be any of the following:
- USERS
- ADMINS
- GUESTS
- PUBLIC
- LOCAL
- The DB2 usernames and instance names cannot be any of the following:
- The DB2 usernames and instance names cannot include accented or special
characters.
- Windows 32-bit users, groups, or instance names can be any case.
- AIX, Solaris and Linux DB2 password requirements
-
- The username and password cannot be more than 8 characters long.
They cannot start with a numeric digit or end with $.
- Passwords cannot contain or special characters.
- Group and instance names can contain 1 to 8 characters.
- The DB2 usernames cannot be any of the following:
- USERS
- ADMINS
- GUESTS
- PUBLIC
- LOCAL
- The DB2 usernames and instance names cannot be any of the following:
- The DB2 usernames, instance names and passwords cannot include accented or
special characters.
- UNIX(R) users, groups, and instances names must be lowercase.
The application server name is required to run the
postinstall.bat script on Windows and
postinstall.sh script on UNIX and Linux systems. Use
the information below to determine your application name.
- Log on to the WebSphere Application Server administration console.
- In the left panel, expand Servers and select Application
Servers.
- In the main panel, you will see the Application Server name. By
default the name of the application server is server1.
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
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:
- IBM
- WebSphere(R)
- AIX
- DB2(R)
- DB2 Universal Database(TM)
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 and Intel 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 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.