IBM Tivoli Intelligent Orchestrator Fix Pack 2, readme file for UNIX or Linux; Revised 2007/06/12
Copyright statement
About this fix pack
Preinstallation checklist
Installing the fix pack
Recovering from installation errors
Updates to the documentation
Uninstallation information
Known problems and workarounds
Appendix A: Manually backing up the installation
Appendix B: Common tasks
Contacting customer support
Notices and trademarks
- Note:
- Before using this information and the product it supports, read the
information in the section Notices and trademarks.
(C) Copyright IBM(R) Corporation 2007. 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
5.1.0.2.
- Important:
- The fix pack only applies to a regular installation of Tivoli Intelligent
Orchestrator (an installation with WebSphere(R) Application Server as the
application server). A fix pack is not available for a Fast Start
installation.
The following updates are included in Version
5.1.0.2.
Fix Pack 2 includes fixes addressed in Version 5.1.0.1
and customer Authorized Program Analysis Reports (APARs).
- Database schema documentation
- Tivoli Intelligent Orchestrator includes a large number of database
tables. For a subset of these tables, information on the table schema
and relationships is now available, to help you understand how the tables are
used in Tivoli Intelligent Orchestrator. For more information, see
"Database reference" in the
information
center.
- Agent enhancements
- This fix pack includes the following agent enhancements:
- Automated agent upgrade: Tivoli Intelligent Orchestrator
provides a new common agent upgrade method as part of the stand-alone
installation procedure. Depending on how you set a parameter in the
caInstall.rsp response file, and on whether or not the
common agent is already installed, the installation script automatically
performs a stand-alone installation or an upgrade of the common
agent. In addition, the stand-alone installer lets you enable an
OEM installation of the common agent. For more information, see
"Upgrading the common agent" in the
information
center.
- Agent footprint: The disk and memory footprints for the
common agent have been reduced to approximately 200 MB and 50 MB,
respectively.
- Tivoli Application Dependency Discovery Manager (TADDM) integration
enhancements
- Tivoli Application Dependency Discovery Manager (TADDM) discovers
resources from the Tivoli Change and Configuration Management Database,
including discovered computers, computer hardware and network resources,
operating systems, software components, and applications such as
DB2(R). You can run the discovery against a set of selected
components, or against multiple computers based on fully-qualified
computer names. The TADDM discovery configuration replaces the Tivoli
Intelligent Orchestrator discovery library reader discovery
configuration. For more information, see "Tivoli Application
Dependency Discovery Manager" in the
information
center.
- Patch automation on HP-UX and AIX(R) operating systems
- A new patch management scenario is available on the HP-UX 11i operating
system. For more information, see "Patch management in the
HP-UX environment" in the
information
center.
Tivoli Intelligent Orchestrator provides support for managing patches on
AIX Version 5.3. On this operating system, the discovery part of
the patch management scenario has been enhanced, which simplifies the endpoint
configuration. You no longer need to add software resources manually,
or set up an AIX software compliance stack. For more information, see
"Patch management in the AIX environment" in the information center.
- VMware automation
- A new VMware automation package is available. This package allows
you to manipulate VMware ESX Server 3.0 and VMware VirtualCenter
2.0 host platforms to perform the following operations:
create/destroy virtual machine, start/stop virtual machine, reboot virtual
machine, and discovery of Virtual Center, Host Platform and virtual
machines.
- Stand-alone Software Package Editor (SPE)
- The Software Package Editor (SPE) is now available as a stand-alone
Java(TM) Web Start application. You must set some properties in the
stand-alone SPE to ensure that it communicates properly with the Tivoli
Intelligent Orchestrator server.
Stand-alone SPE is supported on Windows(R), AIX, Linux(R),
and Solaris operating systems.
- SOAP commands enhancements
- You can now use SOAP commands to perform the following operations:
- Creating a software package.
- Importing and distributing a software package.
- Installing and uninstalling a software package.
- Other enhancements
-
- Ability to create, edit, and run endpoint tasks without requiring an
activity plan.
- When adding a hub or spoke server to the Tivoli Management Framework (TMF)
environment, you no longer need to specify whether hub or spoke. Both
of them are now identified as Tivoli Management region servers.
- New automation package (SWDDiscCLI.tcdriver) that
provides disconnected command line interface (CLI) commands on the Tivoli
Intelligent Orchestrator server and also a workflow to build software package
blocks (SPB) starting from software package definition (SPD) files.
- Enhanced automation package (TCAFromTMA.tcdriver) that
automates the migration of TMF endpoints to Tivoli Common Agents. This
automation package, which is now available on all supported operating systems,
has been enhanced to build common agent packages and refresh common agent
images.
Fix Pack 2 includes fixes addressed in Version 5.1 and customer
Authorized Program Analysis Reports (APARs).
For a detailed list of fixes and customer APARs included in this fix pack,
download the defects list:
- Go to the IBM Support Web site at http://www.ibm.com/support.
- Under Support topics, click Downloads and
drivers.
- In the Browse product support section, under
Software, click Tivoli.
- In the search box, enter 5.1.0-TIV-TIO-FP0002 and
click Search.
- On the Download page, click on the Tivoli Intelligent Orchestrator
Fix Pack 5.1.0-TIV-TIO-FP0002 link.
- Click on the 5.1.0-TIV-TIO-FP0002-DEFECTS (HTTP)
link.
Fix Pack 2 supports all the hardware and software that is supported by
Tivoli Intelligent Orchestrator V 5.1.0. You can apply
the fix pack to a version 5.1.0.0 or
5.1.0.1 installation.
- Fix pack applies to regular installations only
- You can only apply the fix pack to a regular installation of Tivoli
Intelligent Orchestrator (an installation with WebSphere Application Server as
the application server). A fix pack is not available for a Fast Start
installation.
- Software Package Editor compatibility
- Software Package Editor and the Tivoli Intelligent Orchestrator
installation must be both updated to Fix Pack 2 to work together
properly.
- Topology
- If you have 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 is installed and not on the
directory server node.
- Agent manager and common agent version
- The agent manager is updated when you install the fix pack. You
must also upgrade the common agent on all depot servers after you have applied
the fix pack.
- Command changes
- In previous versions of Tivoli Intelligent Orchestrator, the reinit and
reinit-exec commands were available to initialize the data model. These
commands have been deprecated in Tivoli Intelligent Orchestrator Version
5.1. In Version 5.1, the reinit-exec command is used by
the installer but it cannot be used to initialize the database. Running
the command will render your database unusable. To recover, it is
necessary to restore your database.
This readme file uses the following variables to represent directory
paths.
Table 1. Path variables
| Path variables
| Definition
| Default directory
|
| AM_installdir
| Installation directory for the agent manager
| /opt/IBM/AgentManager
|
| DB2_installdir
| Installation directory for DB2 Universal Database(TM)
|
AIX: /usr/opt/db2_08_01
Solaris and Linux: /opt/IBM/db2/V8.1
|
| IDS_installdir
| Installation directory for Tivoli Directory Server
|
/opt/IBM/ldap/V6.0
|
| $ORACLE_HOME
| Installation directory for Oracle
| $ORACLE_BASE/product/10.2.0.1.0
The value of $ORACLE_BASE is the directory in which
all Oracle software is installed, for example,
/u01/app/oracle.
|
| $WAS_HOME
| Installation directory for WebSphere Application Server
|
AIX: /usr/IBM/WebSphere/AppServer
Solaris and Linux: /opt/IBM/WebSphere/AppServer
|
| $TIO_HOME
| Installation directory for Tivoli Intelligent Orchestrator
|
/opt/IBM/tivoli/tio
|
| $TIO_LOGS
| Log file directory for Tivoli Intelligent Orchestrator
|
/var/ibm/tivoli/common/COP/logs
|
You must install and configure all components of Tivoli Intelligent
Orchestrator Version 5.1 before attempting the installation of Fix pack
V 5.1.0.2. Thoroughly review the following list of
prerequisites for installation before proceeding with the installation:
- Identify your current installation situation:
- New Tivoli Intelligent Orchestrator installation
- You must install Tivoli Intelligent Orchestrator 5.1 before you
install the fix pack. For a regular installation, refer to the
Tivoli Intelligent Orchestrator Installation Guide.
For Linux on iSeries(TM), pSeries(R), or zSeries(R) and Linux on
AMD, you must perform the installation manually. Refer to the
Tivoli Intelligent Orchestrator Installation Guide for additional
platforms for your operating system.
- New installation, DB2 required on a separate node (AIX only)
- You must perform a manual installation to use a topology with DB2 on a
separate node. Refer to the Tivoli Intelligent Orchestrator
Installation Guide for additional topologies on AIX: DB2 on a separate
node.
- Tivoli Intelligent Orchestrator is currently installed
- The fix pack can be applied to an existing regular installation of Tivoli
Intelligent Orchestrator. After verifying all the prerequisites
described in this section, you can install the fix pack. A fix pack is
not available for a Fast Start installation.
- Verify disk space requirements:
Table 2. Disk space requirements for the Tivoli Intelligent Orchestrator node
| Location
| Disk space requirements
|
| Disk space for installation images
| 2 GB
|
| Disk space to extract files from installation images
| 2.5 GB
|
| /
| 250 MB
|
| Temporary files: /tmp
| 600 MB
|
| /usr
| 50 MB
|
| /var
| 1 MB
|
| /home
| 100 MB
|
|
Tivoli Intelligent Orchestrator installation directory
The default location is: /opt/IBM/tivoli/tio
|
- AIX
- 5 GB
- Solaris
- 3.5 GB GB
- Linux
- 3.6 GB
|
| WebSphere Application Server installation directory
The default location is:
AIX: /usr/IBM/WebSphere/AppServer
Solaris and Linux: /opt/IBM/WebSphere/AppServer
| 650 MB
|
|
Agent manager installation directory:
usr/IBM/AgentManager
| 50 MB
|
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Verify the currently installed version of Tivoli Intelligent
Orchestrator. The fix pack is compatible with version
5.1.0.0 and 5.1.0.1.
To determine the version of Tivoli Intelligent Orchestrator:
- Go to the $TIO_HOME/config directory.
- Open the file named
build-version.properties.
- Verify the information in the field
current.version.
- Verify that Tivoli Intelligent Orchestrator is operational.
- Ensure that you can log in to Tivoli Intelligent Orchestrator.
- Ensure that you can run the workflow named no_operation, before
installing the fix pack. For instructions for running a workflow, see Running a workflow.
- If the workflow was successful, the deployment engine is working properly
and you can continue to the next step in this checklist.
- If the workflow does not run successfully, check the workflow log and
refer to the Tivoli Intelligent Orchestrator Problem Determination
Guide to resolve the error before you proceed with the fix pack
installation.
- Note:
- If you installed Tivoli Intelligent Orchestrator Fix Pack 1, you must start
Tivoli Intelligent Orchestrator at least once before you apply Fix Pack
2. The first time that you start the product after applying a fix pack,
the automation package migration process runs.
- Verify data model requirements
- Verify that no data model objects are associated with the default device
model. If there are data model objects associated with the default
device model, the default-device-model automation package cannot be
reinstalled and the fix pack installation will fail.
To check for associated objects:
- Connect to the database:
- DB2
-
db2 connect to database_name user database_user using password
- database_name
- The name of the Tivoli Intelligent Orchestrator database instance.
- database_user
- The user name of the database owner. The default is
db2inst1.
- password
- The database password for the database owner.
For example:
db2 connect to tc user db2inst1 using pa55w0rd
- Oracle
-
sqlplus sys/password@db_name as sysdba
- password
- The password for the user sys
- db_name
- The Tivoli Intelligent Orchestrator database name. The default
database name is tc.
- Run the following command to check for associated
objects:
db2 "select id from dcm_object where device_model_id = 1"
- If the command returns 0 records, there are no associated objects and no
further action is necessary for this requirement.
- If the command returns one or more records, you must disconnect objects
from the device model. Proceed to the next step.
- Save the output from the command in step 6a.ii so that you can connect the listed IDs in the output with the
data model after fix pack installation.
- Run the following command to disconnect the objects from the data
model.
db2 "update dcm_object set device_model_id = null where device_model_id = 1"
- Verify that the sample:all-objects access domain
exists. If you removed this access domain after installing Tivoli
Intelligent Orchestrator, you must recreate it before installing the fix
pack.
- Connect to the database as described in step 6a.i.
- Run the following SQL query:
select * from access_domain where name = 'sample:all-objects'
- If the command returns one record, then the access domain exists and no
further action is necessary for this requirement.
- If the command does not return any records, you must recreate the access
domain. Proceed to the next step.
- Create a new file called sampleAccessDomain.xml with the
following lines:
<datacenter>
<access-domain name="sample:all-objects">
</access-domain>
</datacenter>
- Import the file you created with the following command:
$TIO_HOME/tools/xmlimport.sh file:path/sampleAccessDomain.xml
- If you imported the sample data in venice.xml, you must
remove the sample boot server called Rembo. If this boot
server is in the data model during fix pack installation, the automation
package migration will fail. In the Web interface, click
Inventory > Infrastructure Management > Boot
Servers. Find the sample Rembo boot server and delete
it.
- To ensure successful installation of the language pack, ensure that the
user tioadmin has read, write, and execute permissions for all
directories under $TIO_HOME/tioprofile/installedApps/hostnameNode01Cell/TCEAR.ear/tcWebUI.war/CSH,
where hostname is the host name of the computer.
- Cancel all running workflows and clear failed, deleted, and canceled
workflows:
- Start Tivoli Intelligent Orchestrator. For more information, refer
to the section, Administering Tivoli Intelligent Orchestrator in
the Installation Guide.
- Open a command window.
- Go to the $TIO_HOME/tools directory.
- Run the following commands:
./cancel-all-in-progress.sh
./clean-up-deployment-requests.sh
The log files cancel-all-in-progress.log and
clean-up-deployment-requests.log are created with the
results of the commands.
- Check for /bin as an entry in the PATH
environment variable for the shell that you are using. If
/bin is defined towards the beginning of the list in the PATH
environment variable and the java command resolves with a path of
/bin/java, installation of the dynamic content delivery service
will fail.
- To confirm the location of Java, run the command:
which java
If this command is not available on your system, run the following command
instead:
type java
- If the returned value is /bin/java, run the following command
to display the contents of the PATH variable:
echo $PATH
- If the first part of the path is /bin, update the PATH variable
so that /bin does not resolve the java command.
There are several options for making this change:
- Move /bin to the end of the list of paths in the PATH
variable. Normally the java command will resolve to
/usr/bin/java.
- Create a symbolic link for /bin/java under another directory
and add that path to the front of the PATH variable. For example, if
you have a link in /usr/bin to the java command, ensure
that /usr/bin is at the front of the PATH variable or place
/usr/bin before /bin in the list of paths.
- Verify that .bash_profile or .profile
for the tioadmin user contains the following lines:
if [ -f full_installation_path/.TCprofile ]; then
. full_installation_path/.TCprofile
fi
where full_installation_path is the full path to the
Tivoli Intelligent Orchestrator installation directory. The default is
/opt/IBM/tivoli/tio. The $TIO_HOME variable cannot be substituted
because it is not yet defined.
For example:
if [ -f /opt/IBM/tivoli/tio/.TCprofile ]; then
. /opt/IBM/tivoli/tio/.TCprofile
fi
- Note:
- The required lines in bash_profile or .profile
will be missing if the default shell for the tioadmin user was
changed after a regular installation of Tivoli Intelligent
Orchestrator.
- If you have a Linux on zSeries installation of Tivoli Intelligent
Orchestrator and you disabled the Java Just-In-Time (JIT) compiler after
installation, you must enable the JIT compiler again and apply IBM Java SDK
Version 1.4.2, Service Release 8. This Java SDK update
fixes an issue with the reinit script that required you to disable
the JIT compiler. The Java SDK update must be installed to successfully
install the fix pack.
- Open the file $TIO_HOME/tools/setupCmdLine.sh and
comment out the following line:
export JITC_COMPILEOPT=NALL{org/eclipse/osgi/framework/internal/core/PackageAdminImpl}{doResolveBundles}
- Open the file $TIO_HOME/.tools/dcm/getdb.sh and
comment out the following line:
export JAVA_COMPILER=nojit
- Download the 31-bit zSeries (S/390(R)) version of the Java SDK Version
1.4.2, Service Release 8 from http://www.ibm.com/developerworks/java/jdk/linux/download.html.
This version of the download should be used for both 31-bit and (s390)
and 64-bit (s390x) installations.
- Install the Java SDK according to the Java SDK documentation. If an
older service release is already installed, force installation of Service
Release 8.
- Open the file $TIO_HOME/tools/setupCmdLine.sh and change
the value of JAVA_HOME to the directory where you installed the
Java SDK.
- Back up your installation:
- Perform a full backup of your current installation. See Backing up your installation.
- Save workflows that you created in the Web interface that you want to
keep. If you create a new workflow in the Web interface, the workflow
is saved in the data model and is associated with the automation package
called default_automation_package by default. A copy of the
workflow is not saved in the automation package file
default_automation_package.tcdriver.
The default_automation_package automation package can cause
problems during the fix pack installation and is therefore deleted during the
installation. If you want to save a workflow that you created in the
Web interface, perform the following steps:
- Click Automation > Workflows.
- Search for the workflow name.
- In the search results, click the workflow that you want to save.
- Click Edit > Export. The file is saved as a
.wkf file.
After the fix pack installation, you can add the workflow back into Tivoli
Intelligent Orchestrator by opening it in the workflow composer and compiling
the workflow. If you have multiple workflows to import, you can add
them to an automation package and install the automation package.
- Back up any customized automation package files in $TIO_HOME/drivers. Store the
files in a separate location and then delete the copies in $TIO_HOME/drivers. The fix pack
installation automatically migrates automation packages provided with the
product. The installation will fail if your customized automation
packages remain in the $TIO_HOME/drivers directory.
- Ensure that you have downloaded all the installation
files required for the fix pack:
Table 3. Tivoli Intelligent Orchestrator downloads
| Downloads available from the fix pack Web page.
|
| Operating System
| Tivoli Intelligent Orchestrator
| Agent Manager
| Dynamic Content Delivery Service
|
| AIX
|
5.1.0-TIV-TIO-AIX-FP0002-Enterprise.zip
|
AM_V13_AIX.tar
|
cds_images.zip
|
| Solaris
|
5.1.0-TIV-TIO-SOLARIS-FP0002-Enterprise.zip
|
AM_V13_SUN.tar
|
cds_images.zip
|
| Linux
|
5.1.0-TIV-TIO-LINUX-FP0002-Enterprise.zip
|
AM_V13_LIN.tar
|
cds_images.zip
|
AM_V13_LIN_PPC.tar
|
cds_images.zip
|
AM_V13_LIN_zSeries.tar
|
cds_images.zip
|
AM_V13_LIN.tar
|
cds_images.zip
|
Table 4. WebSphere Application Server download
| Download available from http://www.ibm.com/support/docview.wss?rs=180&uid=swg24014326
|
| Operating System
| WebSphere Application Server, Java SDK 1.4.2 Cumulative
Fix, SR6
|
| AIX
| 6.0.2-WS-WASJavaSDK-AixPPC32-FP00000017.tar
|
| Solaris
| 6.0.2-WS-WASJavaSDK-SolarisSparc-FP00000017.tar
|
| Linux
| 6.0.2-WS-WASJavaSDK-LinuxX32-FP00000017.tar
|
PPC Linux:
6.0.2-WS-WASJavaSDK-LinuxPPC32-FP00000017.tar
|
Linux on zSeries:
6.0.2-WS-WASJavaSDK-LinuxS390-FP00000017.tar
|
Linux on AMD 64:
6.0.2-WS-WASJavaSDK-LinuxX32-FP00000017.tar
|
- Verify your Tivoli Intelligent Orchestrator downloads by validating their
checksum values.
- Ensure that you have downloaded the file md5.txt from
the fix pack download page. This file contains the correct checksum
files for the downloads.
- For each download, run the following command. Record the returned
value for each file.
Linux or Solaris: md5sum filename
AIX: csum filename
where filename is the name of the file that you are
validating. Compare the returned value with the value
For example, to validate the file
5.1.0-TIV-TIO-LINUX-FP0002-Enterprise.zip, run
the command:
Linux or Solaris: md5sum 5.1.0-TIV-TIO-WIN-FP0002-Enterprise.zip
AIX: csum 5.1.0-TIV-TIO-WIN-FP0002-Enterprise.zip
- Compare the returned checksum values with the values in
md5.txt. If the values for a download do not match,
download the file again and then verify the checksum value.
- Create a temporary directory for the fix pack. In these
instructions, the directory is called fp_temp. The
temporary directory must meet these requirements:
- It exists outside the Tivoli Intelligent Orchestrator installation
directory.
- It includes at least 2 GB of free space to contain the fix pack after it
is unzipped.
- The root and tioadmin user must have read and write
permission to this directory.
- Extract the contents of the fix pack download to the temporary
directory. After you unpack the file, you can delete the zipped fix
pack download to free space in the directory if necessary.
- Place the agent manager image file in fp_temp/CAS
without extracting the contents.
- Extract the dynamic content delivery service setup file from
cds_images.zip.
AIX: aix/setup.bin
Solaris: solaris/setup.bin
Linux on Intel and Linux on AMD: linux/setup.bin
Linux PPC: linuxppc/setup.bin
Linux on zSeries: linuxzSeries/setup.bin
- Place the setup.bin file in fp_temp/CDS.
You can then delete cds_images.zip.
- Place the WebSphere Application Server Java SDK 1.4.2
Cumulative Fix SR6 file in fp_temp/JDK.
- Check the currently installed version of the Java runtime environment
installed with WebSphere Application Server.
- Change to the $WAS_HOME/java/bin directory.
- Run the following command:
./java -version
The following example shows the output of the command for the Java runtime
environment provided with a new installation of WebSphere Application Server
6.0.2. The fix pack installer will automatically update
your Java runtime environment, if required. You can compare the current
version information with the version information after the fix pack
installation to verify that the Java runtime environment was updated.
AIX
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142-20050609
(JIT enabled: jitc))
Solaris
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build
1.4.2_08-b03 20050517)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
IBM Java ORB build orb142-20050429
XML build XSLT4J Java 2.6.5
XML build XmlCommonsExternal 1.2.04
XML build XML4J 4.3.4
Linux on Intel(R) or Linux on AMD
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia321420-20040626
(JIT enabled: jitc))
Linux PPC
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxppc32142-20050609
(JIT enabled: jitc))
Linux on zSeries
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cx390142-20050609
(JIT enabled: jitc))
- Run the following command: chmod -Rf 755
fp_temp, where fp_temp is the temporary
directory that you created.
- Verify Tivoli Intelligent Orchestrator is stopped. For
instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Ensure that WebSphere Application Server is stopped too. For
instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Ensure that the Tivoli Intelligent Orchestrator database server and
directory server are still running. The database and directory server
must be running during the fix pack installation process to complete the
installation successfully.
- Tivoli Directory Server
- To verify the status of Tivoli Directory Server, run the following
command:
- AIX or Linux
-
ibmdirctl -D cn=root -w password status
- Solaris
-
ibmdirctl -D cn=root -w password -h hostname status
- DB2
-
To verify that DB2 is running:
- Switch to the DB2 instance owner. For example, if you are using the
default instance owner db2inst1, run the command:
su - db2inst1
- To start DB2, run the command:
db2start
DB2 is started if it is not running already. If DB2 is already
running, the following message is displayed:
SQL1026N The database manager is already active
- Oracle Database
-
- To verify the status of Oracle Database, log on to SQL*Plus. The
status of the database is displayed when you log on.
- To verify the status of the Oracle Database listener, run the following
command:
lsnrctl status
- Important:
- The fix pack installation makes changes to the database, directory server,
and files in the Tivoli Intelligent Orchestrator installation
directory. Since the fix pack affects multiple product components,
ensure that you create a backup image of the entire Tivoli Intelligent
Orchestrator computer using your standard backup tools and processes.
If you want to recover your current Tivoli Intelligent Orchestrator
installation, or if you encounter an error during installation, you can use
this backup to restore your current installation without Fix Pack 2.
Before you begin back up of the database, ensure that all running workflows
are stopped, and then stop Tivoli Intelligent Orchestrator.
- Ensure that Tivoli Intelligent Orchestrator is running. For
instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Stop all running workflows.
- Change to the $TIO_HOME/tools directory.
- From the command prompt, run the following commands:
./cancel-all-in-progress.sh
./clean-up-deployment-requests.sh
The log files cancel-all-in-progress.log and
clean-up-deployment-requests.log are created with the
results of the commands.
- Stop Tivoli Intelligent Orchestrator.
- Stop all running applications on the Tivoli Intelligent Orchestrator
computer.
Tivoli Intelligent Orchestrator uses data on the directory server for
authentication and authorization services. In Tivoli Intelligent
Orchestrator Version 5.1, all roles and user information are stored on
the directory server. If your directory server is on a separate
computer, ensure that you back up your Tivoli Intelligent Orchestrator data on
the directory server. If you need to restore your current Tivoli
Intelligent Orchestrator installation without Fix Pack 2, the corresponding
directory server data can also be restored on the directory server.
You can use tools provided with Tivoli Directory Server to back up your
directory server data for Tivoli Intelligent Orchestrator.
- On the computer where Tivoli Directory Server is installed, stop Tivoli
Directory Server. Run the following command:
- AIX or Linux
-
ibmdirctl -D cn=root -w password stop
- Solaris
-
ibmdirctl -D cn=root -w password -h hostname stop
where password is the password for the root
DN and hostname is the host name of the directory server
computer.
To verify that Tivoli Directory Server is stopped, run the following
command:
- AIX or Linux
-
ibmdirctl -D cn=root -w password status
- Solaris
-
ibmdirctl -D cn=root -w password -h hostname status
- Create the directory where you want to store the backup. For
example /home/backup.
- Ensure that the ldapinst user has read, write, and execute
permissions for the directory that you created. To grant permissions
for the directory /home/backup, run the command chmod 777
/home/backup.
- Change to the IDS_installdir/sbin directory.
- Run the following command to backup the directory server:
idsdbback -k path
where path is the full path where you want to store
the backup. For example:
idsdbback -k /home/backup
A message similar to the following example is displayed.
You have chosen to perform the following actions:
GLPDBB029I The database and configuration files for directory server instance
'ldapinst' will be backed up to '/home/backup'.
Do you want to....
(1) Continue with the above actions, or
(2) Exit without making any changes:
- Type 1 to confirm the backup.
- Start Tivoli Directory Server. The directory server must be running
to run the fix pack installer. To start the administration daemon run
the command:
ibmdiradm
If you need to restore your backed up directory server data, you can use
tools provided with Tivoli Directory Server to perform the task.
- Stop Tivoli Directory Server. Run the following command:
- AIX or Linux
-
ibmdirctl -D cn=root -w password stop
- Solaris
-
ibmdirctl -D cn=root -w password -h hostname stop
where password is the password for the root
DN and hostname is the host name of the directory server
computer.
To verify that Tivoli Directory Server is stopped, run the following
command:
- AIX or Linux
-
ibmdirctl -D cn=root -w password status
- Solaris
-
ibmdirctl -D cn=root -w password -h hostname status
- Change to the IDS_installdir/sbin directory.
- Run the following command to restore the directory server data:
idsdbrestore -k path
where path is the full path where the backup data is
stored.
idsdbrestore -k /home/backup
A message similar to the following example is displayed.
You have chosen to perform the following actions:
GLPDBR026I The database and configuration files for directory server instance
'ldapinst' will be restored from files in directory '/home/backup'.
Note: The data in the currently configured database will be overwritten and will be
lost. The schema files and directory key stash file currently configured will be
overwritten. Unless the -r option was specified the configuration file and
configuration key stash file will also be overwritten.
Do you want to....
(1) Continue with the above actions, or
(2) Exit without making any changes:
- Type 1 to confirm that you want to restore the data.
If you are using Oracle as the database and you have changed the password
for the CDSSCHEMA user, you must perform the following steps before installing
the fix pack:
- Change the password for the CDSSCHEMA user to the default value,
tivoli:
- Ensure that Tivoli Intelligent Orchestrator is started. For
instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Log on to the WebSphere Application Server administration console.
For instructions, see Starting the administrative console.
- Select Resources > JDBC Providers.
- Select server1 for the scope and click Apply.
- In the list of JDBC providers, click CDSJDBCProvider.
- Click Additional Properties > Data sources >
CDSDataSource.
- Click Related Items > J2EE Connector Architecture (J2C)
authentication data entries.
- Click CDSDataAuth. The user CDSSCHEMA should
be displayed with the password ******.
- Note:
- The user name CDSSCHEMA must be in uppercase letters.
- Change the password to tivoli and click
Apply.
- Click Save, and then click Save again.
- Install the fix pack. For more information, see Installing the fix pack.
- Change the password for the CDSSCHEMA user back to the value that you
want, using the instructions in Step 1.
After installing Tivoli Intelligent Orchestrator, it is recommended that
you change the default passwords.
- The changePassword command provided with Tivoli Intelligent
Orchestrator Version 5.1.0.0 or
5.1.0.1 does not update the default wasadmin
password in WebSphere Application Server correctly. This problem is
fixed in Version 5.1.0.2.
- If you change the wasadmin password, the password must be
changed in WebSphere Application Server, Tivoli Directory Server, and DB2
Alphablox. This applies to Version 5.1.0.0,
5.1.0.1, and 5.1.0.2.
If you are using Version 5.1.0.0 or
5.1.0.1, perform the following steps:
- Log on as tioadmin.
- Verify that WebSphere Application Server is started. For
instructions, see Common tasks for WebSphere Application Server.
- Change to the $TIO_HOME/tioprofile/bin
directory.
- Run the following command to change the password in WebSphere Application
Server:
./wasadmin.sh -user wasadmin -password wasadmin -f "$TIO_HOME/tools/wasadminPwdUpdate.jacl" new_pwd
where new_pwd is the new password for the user
wasadmin.
- Create a text file called updateWasadminPwd.ldif in a
temporary directory such as /tmp. The file must contain the
following four lines:
dn: cn=wasadmin,dc=ibm,dc=com
changetype: modify
replace: userPassword
userPassword: new_pwd
where new_pwd is the new password for the user
wasadmin.
- Change the wasadmin password in the directory server.
For Tivoli Directory Server, change to the IDS_installdir/bin directory and run the
following command. In this example, the file you created is stored in
/tmp.
./idsldapmodify -D cn=root -w root_pwd -b -r -i /tmp/updateWasadminPwd.ldif
where root_pwd is the password for the directory
server.
- Continue with the additional steps for DB2 Alphablox described
below.
For Version 5.1.0.0, 5.1.0.1, and
5.1.0.2, change the password in DB2 Alphablox:
- Stop WebSphere Application Server with the old password. For
instructions, see Common tasks for WebSphere Application Server.
- Change the wasadmin password in DB2 Alphablox:
- Change to the $TIO_HOME/db2alphablox/repository/servers/AlphabloxAnalytics
directory.
- In the Server.properties file, locate the line:
ws.admin.password.protected=<protected_pwd>
where protected_pwd is your old password in an encrypted
format.
- Change this line to:
ws.admin.password=<plain_pwd>
where plain_pwd is your new password in plain text.
- Start WebSphere Application Server. For instructions, see Common tasks for WebSphere Application Server.
- In a Web browser, open the DB2 Alphablox console:
https://hostname:9045/AlphabloxAdmin/home/
where hostname is the host name of the computer where
WebSphere Application Server is installed.
- In the console, click Alphablox Admin Pages >
Administration > General > System.
- Change Message History Size from 100 to 101 and save the
change. Alphablox automatically encrypts the password in the
Server.properties file.
- Ensure that you meet all the requirements as described in Preinstallation checklist.
- Ensure that the directory and database are running. For
instructions on checking the status of applications, see Appendix B: Common tasks.
- Ensure that Tivoli Intelligent Orchestrator and WebSphere Application
Server are stopped. For instructions, see Common tasks for Tivoli Intelligent Orchestrator and Common tasks for WebSphere Application Server.
- Log in to the Tivoli Intelligent Orchestrator computer as
root.
- Run the following command:
export TERM=ansi
- Change to the fp_temp directory.
- If you are installing on AIX or Solaris, open the file
unixUpgrade.sh in a text editor and change the following
line:
- Find
- chown -Rf :tivoli $TIO_LOGS $CDS_LOGS
- Replace with
- chown -Rf root:tivoli $TIO_LOGS $CDS_LOGS
- Run the following command:
- Note:
- Installation options are case-sensitive.
To perform the full fix pack installation, run the upgrade script with
the application server and database passwords.
unixUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBRuntimePWD runtime_pwd -DBAdminPWD admin_pwd
- was_adminID
- The WebSphere Application Server administrator ID. The default is
wasadmin.
- was_admin_pwd
- The WebSphere Application Server administrator password. The
default is wasadmin.
- runtime_pwd
- Specify the database user password that was used to install Tivoli
Intelligent Orchestrator.
- admin_pwd
- Specify the database instance owner password that was used to install
Tivoli Intelligent Orchestrator.
- When the installation is complete, verify that the Java SDK
1.4.2 SR6 update for WebSphere Application Server was
installed.
- Change to the $WAS_HOME/java/bin directory.
- Run the command ./java -version. The following
version number is displayed in the output if the update was successful:
- AIX: ca142ifx-20061116
- Solaris: 1.4.2_12-b03
- Linux on Intel: cxia32142ifx-20061121
- Linux PPC: cxppc32142ifx-20061121
- Linux on AMD: j9xa64142ifx-20061121
- Linux on zSeries: cx390142ifx-20061121
The log file for the update is located in $WAS_HOME/logs/update/6.0.2-WS-WASJavaSDK-platform-FP00000017.
- If Tivoli Intelligent Orchestrator is installed on
Solaris and you are using Oracle as the database, you must change the default
password that is set for the user CDSSCHEMA.
- Start Tivoli Intelligent Orchestrator. For startup instructions,
see Common tasks for Tivoli Intelligent Orchestrator.
The first time that you start the product after installing the fix pack,
the automation package migration process runs and updates automation packages
provided with Tivoli Intelligent Orchestrator.
- Note:
- During the migration process, the deployment engine is not available to run
workflows. Wait until the __master_tcdriver_update workflow
has finished running before you perform other actions.
- Log on to the WebSphere Application Server administration console.
For instructions, see Starting the administrative console.
- Select Resources > JDBC Providers.
- Select server1 for the scope and click Apply.
- In the list of JDBC providers, click CDSJDBCProvider.
- Click Additional Properties > Data sources >
CDSDataSource.
- Click Related Items > J2EE Connector Architecture (J2C)
authentication data entries.
- Click CDSDataAuth. The user CDSSCHEMA should
be displayed with the password ******.
- Note:
- The user name CDSSCHEMA must be in uppercase letters.
- Change the password to a new valid password and click
Apply.
- Click Save, and then click Save again.
- Restart Tivoli Intelligent Orchestrator so that the changes take
effect. For stop and start instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Log on to the computer as root.
- Run the command su - oracle.
- Change password inside Oracle environment:
- Connect to database. Replace password with the
password for the user sys and db_name with the
Tivoli Intelligent Orchestrator database name. The default database
name is tc.
sqlplus sys/password@db_name as sysdba
- Specify the new password with the following command:
alter user CDSSCHEMA identified by new_password;
Replace new_password with the new password that you
created in step 10i.
- Verify your changes:
sqlplus CDSSCHEMA/new_password@db_name
- Start Tivoli Intelligent Orchestrator. For startup instructions,
see Common tasks for Tivoli Intelligent Orchestrator.
The first time that you start the product after installing the fix pack,
the automation package migration process runs and updates automation packages
provided with Tivoli Intelligent Orchestrator.
- Note:
- During the migration process, the deployment engine is not available to run
workflows. Wait until the __master_tcdriver_update workflow
has finished running before you perform other actions.
- Verify that you can log on to the dynamic content delivery service
console. If the message The specified username or password is
incorrect is displayed, this might indicate that SOAP services were not
started. Check the log file $TIO_LOGS/soap/desoap_start.log.
To fix the SOAP services, see SOAP services fail to start.
- For updates from Version 5.1.0.1 to 5.1.0.2:
- If you modified the file $TIO_HOME/tools/run-desoap.sh
during Fix Pack 1 installation to fix the SOAP services, you must make the
change described in SOAP services fail to start again after installing Fix Pack 2.
- If you disconnected data model objects from the
default device model in step 6 of Installation requirements, you can now reconnect the objects.
- Connect to the database using the same command that you used in step 6 of Installation requirements.
- Run the following command to connect the objects.
db2 "update dcm_object set device_model_id = 1 where id in (id1, id2, ...)"
Replace id1, id2, ... with a
list of the object IDs separated by commas. Use the object IDs that you
saved in step 6 of Installation requirements.
- If you created customized automation packages, you must load them
separately after Tivoli Intelligent Orchestrator automation packages are
migrated.
- Stop Tivoli Intelligent Orchestrator. For instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- For each automation package that you want to load, copy the directory
$TIO_HOME/eclipse_FP1/plugins/package_name
to $TIO_HOME/eclipse/plugins, where
package_name is the name of the customized automation
package.
- Start Tivoli Intelligent Orchestrator so that the customized automation
packages are loaded.
Use the following procedure to upgrade IBM Tivoli Provisioning Manager for
OS Deployment Embedded Edition to the latest version. All of your
existing operating system images are preserved during the upgrade.
In Tivoli Intelligent Orchestrator Version 5.1, IBM Tivoli
Provisioning Manager for OS Deployment Embedded Edition was called Rembo
Toolkit 4.0.
To upgrade IBM Tivoli Provisioning Manager for OS Deployment Embedded
Edition:
- Click Inventory > Manage Inventory >
Computers and find the computer that has the IBM Tivoli
Provisioning Manager for OS Deployment Embedded Edition server
installed.
- Click on the computer name and select the Software tab.
- Next to TPM for OS Deployment EE, click Actions >
Upgrade. The upgrade will take a few moments to
complete.
- Note:
- In Tivoli Intelligent Orchestrator Version 5.1, the software name to
upgrade is Rembo Toolkit 4.0.
The concurrency level determines the number or parallel deployments that
are permitted within a task. Before Fix Pack 2, the default level was
set to 1. The fix pack installer changes the currently configured value
to 5. If you were using a different concurrency level before applying
the fix pack, you should reconfigure the concurrency level.
- Log on to the Tivoli Intelligent Orchestrator Web interface.
- Click System Management > Global Settings.
- On the Variables tab, locate the default concurrency
level variable and click Actions >
Properties.
- Change the value and click Save.
This section describes important updates to endpoints for Fix Pack
2.
After you have completed installation of the fix pack, you must upgrade
older versions of the common agent to version
1.3.2.11. The common agent must be upgraded on
both the depot servers and the endpoints that are participating in the
software distribution process.
Either one of the following older common agent versions can be
upgraded:
- 1.3.0.26, provided with Tivoli Intelligent
Orchestrator 5.1.
- 1.3.1.13, provided with Tivoli Intelligent
Orchestrator 5.1.0.1 (Fix Pack 1).
Use the following procedure to upgrade the common agent on multiple
computers. Refer to the topic "Upgrading the common agent" in
the
information center for additional details about
upgrading the common agent.
- Ensure that enough free disk space is available on endpoints for the
upgrade.
- 80 MB in the tivoli/ep directory
- 180 MB in the agent directory for temporary files.
- Log on to the Tivoli Intelligent Orchestrator Web interface.
- Click Task Management > Favorite Tasks.
- In the Table Filtering list, select Workflow Task, and then
click Create. Follow the instructions in the wizard to
create your workflow task:
- On the Introduction page, click Next.
- On the Select Workflow page, type a name and a description for your task,
and then select the TCA_Device_Upgrade.wkf workflow. Click
Next.
- On the Define Workflow Parameters page, select DeviceID.
Click Next.
- Review your choices on the Summary page, and click
Finish.
- Run the favorite task that you have just created:
- On the Favorite Tasks page, in the task list, find the workflow task that
you have created. In that row, click Actions >
Run. Follow the instructions in the wizard to run the task
on multiple endpoints.
- On the Select Target Systems page, select the target endpoints for the
task. Click Next.
- On the Favorite Task Parameters page, edit the task parameters as
required. Click Next.
- On the Schedule page, select Now to run the task immediately,
or schedule the task to run at a specified date and time. Specify the
notification settings for the task, and then click Next.
- Review your choices on the Summary page and click
Finish.
If Automation Package Developer Environment is installed in Eclipse on a
separate computer, perform the following steps to upgrade it.
- Ensure that Eclipse is not running.
- Copy the archive file $TIO_HOME/tools/apde.zip to the
remote computer.
- Extract the contents of the archive file to the directory where Automation
Package Developer Environment is installed. For example
/opt/apde. The contents of the archive file are placed in
the eclipse/plugins subdirectory.
- Start Eclipse with the -clean option so that the plug-in
changes are applied:
./eclipse -clean
- Exit Ecplise.
The following automation packages are replaced during fix pack
installation.
- zVM.tcdriver
- The fix pack installation uninstalls this automation package and installs
zVM_Server.tcdriver to replace it.
- AIX_FIX.tcdriver
- This automation package is obsolete and is replaced by
AIX_PATCH.tcdriver. To remove the any data model
objects used by the AIX_FIX.tcdriver, run the
CleanUP_AIX_FIXMigrateDCM_5_1_0_1 workflow after the fix pack
installation. For instructions on running a workflow, see Running a workflow.
After you have installed the fix pack, you must reinstall automation
packages that you have created or customized. If you have made changes
to data model objects that are imported by an automation package since
installing it in Version 5.1.0.0, you can create
migration workflows to automate the required changes to the data model
objects.
For more information, see "Migrating customized automation
packages" in the
information center.
The following main steps occur during installation of the fix pack:
- Installation of fix pack files.
- Post-installation configuration such as migration of directory
server data and migration of automation packages.
- Upgrade of the agent manager.
- Upgrade of the dynamic content delivery service.
The fix pack uninstaller can revert the changes made in step 1, but it
cannot revert any of the changes made after that step. An uninstaller
is not available for the other steps. If an installation error occurs
during any of these steps, restore the backup of Tivoli Intelligent
Orchestrator that you created before you applied the fix pack, and then try
the fix pack installation again.
To recover from an installation error:
- Record any error messages that you received and address the errors.
- Check the log files for information about the error and possible recovery
actions.
- Fix pack installer
- $TIO_HOME/logs/update
- Data migration
- $TIO_LOGS/fixpack
- WebSphere Application Server
- $WAS_HOME/logs/update
- The agent manager
- The AM_installdir/logs
directory.
- The dynamic content delivery service
- The default location for the dynamic content delivery service logs
is:
/opt/ibm/tivoli/common/ctgde/logs
- Check Known problems and workarounds for possible installation errors and recovery
actions.
- Restore the system image that you created for the Tivoli Intelligent
Orchestrator computer in Backing up your installation using your standard backup tools and processes.
- If your directory server is on a separate computer, ensure that you also
restore your backed up directory server data as described in Backing up directory server data.
- Apply the fix pack again.
For information about uninstalling, see Uninstallation information.
During fix pack installation, the following automation packages are
uninstalled:
- default_automation_package.tcdriver is uninstalled to
prevent workflow name conflicts with the original workflows provided with
Tivoli Intelligent Orchestrator.
- discovery-library.tcdriver and
zVM.tcdriver (obsolete)
If one of these automation packages cannot be uninstalled because it is not
currently installed, an error message similar to the following example appears
in postinstall.log. You can ignore this error message.
2007-03-16 02:23:27,592 ERROR COPTDM172E An error occurred when the system uninstalled the "zvm" driver because the driver status must be installed.
During fix pack installation, the Tivoli Intelligent Orchestrator
information center is updated to Version 5.1.0.2.
You can also view the updated Tivoli Intelligent Orchestrator information center.
The following subsections highlight additional important changes to the
documentation.
Updated Tivoli Intelligent Orchestrator publications are available in the
fix pack image in the GA_guide subdirectory.
The preinstallation checklists for installation of Tivoli Intelligent
Orchestrator Version 5.1.0.0 are also updated and are
available in the updated Tivoli Intelligent Orchestrator Installation
Guide or as standalone checklists in preinstall subdirectory
of the fix pack image.
In Chapter 15, Installing Tivoli Intelligent Orchestrator,
section To install Tivoli Intelligent Orchestrator, complete these
steps:
- For the second bullet of Note 1 (after Step 25), the command export
JITC_COMPILEOPT should be written (and run) as all in one line, not
two.
- For the fourth bullet of Note 1 (after Step 25), the command
TIO_HOME/tools/reinit.sh should be replaced with
$TIO_HOME/tools/reinit.sh.
- For Note 2 (after Step 25), the command
TIO_HOME/tools/reinit.sh should be replaced with
$TIO_HOME/tools/reinit.sh.
In Chapter 19, Device Manager Installation, section
Installing the Device Manager, Step 6, the command
./install.sh -options DMS_lindefaults.rsp
should be replaced with
./install.sh -options defaults/DMS_lindefaults.rsp
In Appendix A, Uninstalling Agent Manager, this information
should be added: If there is no uninstall.bin file,
you can uninstall agent manager with this command:
/opt/IBM/WebSphere/AppServer/java/jre/bin/java -jar /opt/IBM/AgentManager/_uninst/uninstall.jar
The DCMUpdate command that is used to update the properties of
an object in the data model must use propertyID rather than
DCM_Object_ID for the update.
In the "Conditional statements" topic in the information center, the last example should be replaced
with:
In the following example, the value of propertyID determines if a the
Property_Name property exists and belongs to Server_ID. If the property
is not found, it is added to the data model. If the property exists,
the value is updated.
var propertyID = DCMQuery(/property[@key=$Label_Key AND @componentid=$Component_Id AND @dcmobjectid=$Server_ID])
if Jython(not propertyID) then
DCMInsert parent = DCMQuery(/server[@id=$Server_ID]) <<EOI
<property component="$componentName" name="$Property_Name" value="$Property_Value" />
EOI
#--
else
DCMUpdate parent = DCMQuery(/property[@id=$propertyID]) <<EOU
<property component="$componentName" name="$Property_Name" value="$Property_Value" />
EOU
#--
endif
In the "Updating objects" topic in the
information
center, the example provided in Step 5 should be replaced with:
#Workflow to update the properties of a software stack
#Name worklfow, define locale workflow
workflow test_update_property LocaleInsensitive
#determine the componentID
var componentID = DCMQuery(/kanahacomponent[@name=$componentName])
#determine the stack software moduleID
var stackSoftwareModuleID = DCMQuery(/StackSoftwareModule [@name="Windows2000"])
#Updates the subnet mask to the IP address
#using the DCMUpdate command
var propertyID = DCMQuery(/property[@key="snmp.community.read" AND @componentid=$componentID AND @dcmobjectid=$stackSoftwareModuleID])
DCMUpdate parent = DCMQuery(/property[@id=$propertyID]) <<EOF
<property name="snmp.community.read" value="admin" component="$componentName" >
EOF
The Patch management link on the Tutorials page on the Web
interface and the Show me link in the "Managing patches in
large environments" topic in the information center installed with Fix
Pack 2 point to incorrect files. To fix these links:
- Change to the $TIO_HOME/help/eclipse/com.ibm.etools.viewlet.doc
directory.
- Create a subdirectory called swf.
- Extract the file TPM51FP2_PatchMgmt_viewlet_swf.html
from the file doc.zip to the swf
directory.
- Open the file TPM51FP2_PatchMgmt_viewlet_swf.html in a
text editor.
- Find and replace the following text:
Find: Patch_management_FINAL_DRAFT.swf
Replace with: TPM51FP2_PatchMgmt_viewlet.swf
- Make a copy of the modified file
TPM51FP2_PatchMgmt_viewlet_swf.html and save it as
TPM51FP2_PatchMgmt_viewlet_viewlet_swf.html in the
swf directory.
- From the $TIO_HOME/help/eclipse/com.ibm.etools.viewlet.doc
directory, add both the TPM51FP2_PatchMgmt_viewlet_swf.html
and TPM51FP2_PatchMgmt_viewlet_viewlet_swf.html files to
doc.zip. Ensure that information about the relative
path (swf) is included when you add the file.
- If you have already started Tivoli Intelligent Orchestrator, clear the
information center cache and restart Tivoli Intelligent Orchestrator:
- Stop Tivoli Intelligent Orchestrator.
- Change to the $TIO_HOME/help/configuration
directory.
- Delete all files except config.ini.
- Start Tivoli Intelligent Orchestrator.
When you start Tivoli Intelligent Orchestrator again, the animation is
available from the Tutorials page on the Web interface and the "Managing
patches in large environments" tutorial in the information center.
This section describe how to uninstall files installed by the fix pack
installer. This process only reverts files installed by the fix pack
installer. It does not revert migrated data or upgraded core
components.
- If you only need to revert the changes made by the fix pack installer, use
the information in this section.
- If the fix pack installation performed any additional steps after running
the fix pack installer, the only way to revert all changes is to restore your
backup of the Tivoli Intelligent Orchestrator installation before you applied
the fix pack. For more information, see Recovering from installation errors.
Before you uninstall the fix pack:
To uninstall the fix pack:
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Ensure that the database server and the directory server are both
running. For instructions, see Appendix B: Common tasks.
- Export the $JAVA_HOME environment variable to $WAS_HOME/java.
- Ensure that the DISPLAY variable is set and confirm that the
hostname of the server is correct.
- Change directory to fp_temp/installer where
fp_temp is the directory in which you unzipped the fix
pack ZIP file.
- From fp_temp/installer, run the following command to
launch the uninstallation using the silent mode:
updateSilent.sh -fixpack -uninstall $TIO_HOME fixpackID fp_temp/installer
where fixpackID is the fix pack ID for the appropriate
operating system:
- Linux
- tio51_fp2_linux_Enterprise
- AIX
- tio51_fp2_aix_Enterprise
- Solaris
- tio51_fp2_solaris_Enterprise
For example, to uninstall the fix pack from a Linux system:
updateSilent.sh -fixpack -uninstall /opt/ibm/tivoli/tio tio51_fp2_linux_Enterprise /tmp/fp-temp/installer
- 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:
- Log in to the Tivoli Intelligent Orchestrator server as user
tioadmin.
- Start the WebSphere Application Server. For instructions, see Common tasks for WebSphere Application Server.
- Run the command given below:
"$TIO_HOMEtools/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. For instructions, see Common tasks for WebSphere Application Server.
To redeploy the EAR files:
- Log in to the Tivoli Intelligent Orchestrator server as user
tioadmin.
- On Linux systems only, set the file size limit to 20000 as below:
ulimit -n 20000
- Start the WebSphere Application Server. For instructions, see Common tasks for 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 "Too many open
files". After the system has restarted, set the ulimit size as
stated above, then try Step 4 again.
- Stop the WebSphere Application Server. For instructions, see Common tasks for WebSphere Application Server.
This section describes known limitations in this release of Tivoli
Intelligent Orchestrator. 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.
Installation of the dynamic content delivery service fails because the
location of Java cannot be found by the installer. In the log file
/opt/ibm/tivoli/common/ctgde/logs/cds_upgrade.txt, the error
description looks like the following example:
INSTALLER_PATH=/extra/ibm/tivoli/tio/CDS/scripts/./setup.binChecking the environment variables specifed in the JVM files to find the JVM...
Verifying... /bin/java -cp /tmp/istemp7613004171417/Verify.jarVerify java.vendor java.versionVerification passed for / using the JVM file /tmp/istemp7613004171417/relative_to_upgrade.jvm.
JavaHome is not resolved correctly in the jvm file /tmp/istemp7613004171417/relative_to_upgrade.jvm.
Failed to launch the application.
This error occurs when Java is installed in /bin/java and
/bin is in the path listed in the PATH variable. To fix the
error, update the PATH variable so that the java command does not
resolve to the /bin directory.
- To confirm the location of Java, run the command:
which java
If this command is not available on your system, run the following command
instead:
type java
- If the returned value is /bin/java, run the following command
to display the contents of the PATH variable:
echo $PATH
- If the first part of the path is /bin, update the PATH variable
so that /bin does not resolve the java command.
There are several options for making this change:
- Move /bin to the end of the list of paths in the PATH
variable. Normally the java command will resolve to
/usr/bin/java.
- Create a symbolic link for /bin/java under another directory
and add that path to the front of the PATH variable. For example, if
you have a link in /usr/bin to the java command, ensure
that /usr/bin is at the front of the PATH variable or place
/usr/bin before /bin in the list of paths.
- Run the fix pack installer again using the
unixUpgrade.sh command with the -CDS
option. When you use the -CDS option, the
installation process will start from the dynamic content delivery service
installation step.
unixUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBRuntimePWD runtime_pwd -DBAdminPWD admin_pwd -CDS
- was_adminID
- The WebSphere Application Server administrator ID. The default is
wasadmin.
- was_admin_pwd
- The WebSphere Application Server administrator password. The
default is wasadmin.
- runtime_pwd
- Specify the database user password that was used to install Tivoli
Intelligent Orchestrator.
- admin_pwd
- Specify the database instance owner password that was used to install
Tivoli Intelligent Orchestrator.
SOAP services should start automatically after Tivoli Intelligent
Orchestrator installation. If the message The specified username
or password is incorrect is displayed when you try to log on to the
dynamic content delivery service console and SOAP services do not start
successfully, check $TIO_LOGS/soap/desoap_start.log for
either of the following exceptions:
Caused by: java.lang.NoClassDefFoundError: com/ibm/pvcws/proxy/Logger
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:810)
at org.eclipse.osgi.framework.adaptor.core.DefaultClassLoader.defineClass
(DefaultClassLoader.java:370)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.defineClass
(EclipseClassLoader.java:233)
or
Caused by: java.util.MissingResourceException: Can't find bundle for base name
com.ibm.pvcws.proxy.wsosgimessages, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.
java:825)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:794)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:532)
at com.ibm.pvcws.proxy.WsosgiMessages.<clinit>(WsosgiMessages.java:32)
... 39 more
To manually start the SOAP services:
- Stop Tivoli Intelligent Orchestrator. For instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Open the file called $TIO_HOME/tools/run-desoap.sh and
edit the following lines:
Original: -Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar \
New: -Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar:$TIO_HOME/
eclipse/plugins/com.ibm.pvcws.osgi/com.ibm.pvcws.osgi.props.jar \
Original: -noSplash -application launcher.CliLauncher \
New: -noSplash -clean -application launcher.CliLauncher \
- Start Tivoli Intelligent Orchestrator. For instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Verify that the SOAP services started by checking the
$TIO_LOGS/soap/desoap_start.log.
When you run the unixUpgrade.sh script, an error message
might be displayed:
ERROR: unable to determine the installation location of CDS, exiting.
To fix the error:
- Find the location of the vpd.script file on your
system. This location must contain the path
/cds_manager/Gen1/_vpddb/.
- In the unixUpgrade.sh file, locate the section:
# environment checks & initialization
- In that section, locate the CDS_VPD_FILE variable that
corresponds to the operating system you are running (AIX, Solaris, or Linux)
and change its value to the location found in Step 1.
- Save and close the file.
- Run the updated unixUpgrade.sh script again.
If the TERM environment variable is not set on your system, or
is set to a value other than vt100 or xterm, the
unixUpgrade.sh script might fail.
To work around this problem:
- Set the TERM environment variable on your system to the
following value:
export TERM=ansi
- Remove the following directories:
$TIO_HOME/drivers and
$TIO_HOME/eclipse
- Rename the following directories:
$TIO_HOME/drivers_FP1 to
$TIO_HOME/drivers and
$TIO_HOME/eclipse_FP1 to
$TIO_HOME/eclipse
- Run the unixUpgrade.sh script again.
After starting Tivoli Intelligent Orchestrator for the first time,
deployment requests for workflows remain in the Create state and do
not run.
The first time that you start Tivoli Intelligent Orchestrator after the
applying the fix pack, the deployment engine runs a workflow to migrate
automation packages provided with the product to the current fix pack
level. During this migration process, the deployment engine does not
accept any other deployment requests.
When the migration process is complete, the deployment engine starts to
process deployment requests in the queue.
If the migration process fails, the deployment engine will not start and
workflows will not run. You must restore your backup of Tivoli
Intelligent Orchestrator and try to apply the fix pack again.
In environments that contain Tivoli Management Framework (TMF) endpoints,
no errors are reported when an old version of Windows Update Agent (WUA) is
installed on the endpoints. After scanning for missing patches, Tivoli
Intelligent Orchestrator reports success even though some endpoints do not
have the minimum required version of WUA installed.
Before scanning for missing patches, ensure that the latest version of WUA
is installed on the endpoints. For information on how to install WUA,
see the "Installing WUA on endpoints" topic in the information center.
When attempting to install certain Windows patches, the installation
reports success, but the Windows Update Agent (WUA) scan does not find the
patch installed and therefore does not add it to the Software tab for that
computer. This problem typically appears when attempting to install
patches that have been superseded by newer ones. This known issue is
caused by a WUA problem.
Avoid approving or installing Windows patches that have been
superseded.
If the Track traffic setting is set to Yes for the
Windows Firewall compliance check, and you are running the check on
an endpoint that is using Windows Native Firewall, the following
recommendation may be generated even if the firewall is active:
Change the value of the "Track traffic" setting for the firewall software "Windows Native Firewall" to match the compliant value "true".
You can ignore this recommendation.
A user with the software operator role is unable to view the Publish
feature on the Web interface.
To allow the user to publish files to depot servers, assign the permission
Depot - Manage to the software operator role:
- Click System Management > Manage Security >
Security Roles.
- Click on the Depot - Manage permission in the Available
Permissions list and click Add.
- Save your changes.
Software distribution and installation might fail for users that do not
have the Device.ManagerSoftware permission on all of the
selected target computers.
To be able to successfully distribute and install software products using
the Software Management > Install > Software
Products option, the user must have the
Device.ManagerSoftware permission on all of the selected
target computers. If the user does not have this permission on one of
the selected target computers, the software distribution and installation
might fail on all of the targets.
To assign a static IP address to a Windows 2000 computer, the network
interfaces of the target computer must be physically connected and
network-enabled. Interfaces that are not enabled on the network
will not be fully configured.
This limitation is caused by a known issue with Windows 2000. For
more information, refer to article KB815322 on the Microsoft(R) Web
site.
If you receive the following error when you try to retrieve a list of
packages in Software Package Editor, here is some additional information about
the error and how to diagnose it.
DISSP6047E An error occurred while retrieving the list of packages. See the log for details.
Explanation: An error occurs when you try to retrieve the
list of packages by selecting Open > Open from
repository. This problem is caused by communication problems, and the
operation is not performed.
Verify the following conditions:
- The connection to Tivoli Intelligent Orchestrator by checking the
hostname, the port, and the URL configured on the Preferences page of the
Eclipse-based Software Package Editor. Try to ping the host using the
configured hostname and port from the Software Package Editor computer.
- The presence of a firewall. Ensure that the firewall is not
blocking connections on the Tivoli Intelligent Orchestrator port.
- Tivoli Intelligent Orchestrator is up and running. For information
about checking status, see Common tasks for Tivoli Intelligent Orchestrator.
For additional details, see the workflow log in the Tivoli Intelligent
Orchestrator Web Interface, and the swdisGUI.tr1 and
swdisGUI.tr2 trace files. If you are using the
Eclipse-based Software Package Editor, you can find these trace files in the
Eclipse installation directory. If you are using the Web Start Software
Package Editor, you can find these trace files in the Web Start cache memory
directory.
When you exclude targets from an activity plan at the plan level using a
target file, the excluded targets are displayed when you submit the
plan. This behavior is a limitation of the user interface and does not
affect the way that the activity plan is processed.
Registration of device manager endpoints causes an OutOfMemory
error. The error appears in the WebSphere Application Server log file
$TIO_HOME/tioprofile/logs/server1/SystemOut.log.
Reduce the maximum number of open connections and change the heap
size.
- Log on to the WebSphere Application Server administration console
at:
https://hostname:9043/ibm/console/logon.jsp
- Change the number of open connections.
- Click Servers > Application servers >
server_name > Ports.
- Click View associated transports for the appropriate
port.
- Change the Maximum open connections setting to
2500.
- Change the maximum heap size:
- Click Servers > Application servers >
server_name > Process Definition > Java
Virtual Machine.
- Change the Maximum Heap Size setting to 1024
MB.
Files that have been published to a depot server might be lost when the
common agent and subagents are upgraded on that depot server.
Consequently, the distribution and installation of the published files to
endpoints fail with a "File not found" error.
Before upgrading the common agent and subagents on the depot server,
unpublish all files from the depot and ensure that all tasks are
completed. Then, upgrade the common agent on the depot server, publish
the files again, and distribute and install files on the endpoints.
If you use platform-dependent variables when you specify the path of the
source files contained in a software package block (SPB) built on UNIX(R)
or Linux, and you download this SPB file on Windows, the SPB file might get
corrupted. The same behavior occurs if you build the SPB file on a
Windows and you download it on UNIX or Linux.
If you are using a Windows XP computer as your Microsoft patch download
server, you may receive an Out of Disk Error when attempting to download the
32-bit version of Windows 2003 Service Pack 2.
Install the service pack manually:
- Using the Package Path provided in the Software Installable
page for the patch, download the service pack manually to a location on the
Tivoli Intelligent Orchestrator server. The following location is
recommended:
$TIO_HOME/repository/wua/updates/<installable_ID>, where
<installable_ID> is the software installable ID. For
example, if the installable ID is 3603, the path is
$TIO_HOME/repository/wua/updates/3603.
- In the Software Installable page, click Edit >
Properties.
- Set the Installable Path to the relative path of the location
from Step 1, for example, /wua/updates/3603.
- Set File Repository to LocalFileRepository and click
Save.
As an alternative to installing the service pack manually, use Windows
Server 2003 or Windows 2000 Server as the operating system on the Microsoft
patch download server.
When you run an inventory scan with the Use software signatures
option, the Solaris operating system may not be discovered or listed in the
Software tab for your target machine.
This may occur because the Solaris operating system revision is not covered
in the current Solaris signature that is available in the Tivoli Intelligent
Orchestrator software signature catalogue. This is a known problem with
the Tivoli Intelligent Orchestrator software signature scan.
To work around this problem, you need to manually create a Solaris
signature based on the information reported by your Solaris machine.
To create a Solaris operating system signature and associate it with a
software definition:
- Check the Solaris information on your Solaris target machine.
- Log on to the Solaris target machine.
- From the command line, run the following command to check the operating
system level: pkginfo -l SUNWcsr
- You may see the following output from the command line:
-bash-3.00# pkginfo -l SUNWcsr
PKGINST: SUNWcsr
NAME: Core Solaris, (Root)
CATEGORY: system
ARCH: sparc
VERSION: 11.10.0,REV=2006.02.21.15.53
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: core software for a specific instruction-set architecture
PSTAMP: on10-patch20060403161831
INSTDATE: Mar 30 2007 14:18
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 447 installed pathnames
48 shared pathnames
13 linked files
108 directories
86 executables
5982 blocks used (approx)
- A signature can be created based on the concatenation of these
strings: NAME:Core Solaris, (Root), VERSION:
11.10.0,REV=2006.02.21.15.53
and VENDOR: Sun Microsystems, Inc. You must include a
white space between each of the strings. For example, a signature
string can be created as follows: Core Solaris, (Root)
11.10.0,REV=2006.02.21.15.53 Sun
Microsystems, Inc.
- Add a new Solaris signature to the $TIO_HOME\xml\samplebook\IBM-software-custom-signature.xml
file as shown below:
<Signature name="Solaris 10 revision 2006.02.21.15.53">
<Metadata>
<version>2006.04.26.11.16.43</version>
<schemaVersion>1.0</schemaVersion>
<component>
<hdType>OS</hdType>
<hd>SOLARIS</hd>
<os>SOLARIS</os>
<name>Solaris</name>
<version>10</version>
</component>
</Metadata>
<Platforms>
<Platform type="SOLARIS"/>
</Platforms>
<Variable name="IS_INSTALLED" export="true">
<PackageInfoEqual provider="os" code="SUNWcsr"
value="Core Solaris, (Root) 11.10.0,REV=2006.02.21.15.53 Sun Microsystems, Inc." />
</Variable>
</Signature>
- Save your changes, then load the new signature into Tivoli Intelligent
Orchestrator by running the following commands:
- For Windows: cd %TIO_HOME%\xml\samplebook\, then
"%TIO_HOME%\tools\importSoftwareSignature.cmd"
IBM-software-custom-signature.xml true
- For other platforms: cd $TIO_HOME/xml/samplebook, then
$TIO_HOME/tools/importSoftwareSignature.sh
IBM-software-custom-signature.xml true
- To associate the newly created signature with a Solaris definition:
- Log on to Tivoli Intelligent Orchestrator.
- Click Software Management > Manage Software Catalogue
> Software Signatures.
- Select Solaris as your Operating System and then search for the
signature name (for example, Solaris 10 revision
2006.02.21.15.53).
- Click the Actions button, then Associate Software
Definition.
- In the Search field, type Solaris and find the
correct Solaris definition to associate with the newly created
signature.
- Save your changes.
A known issue on Solaris platforms affects patch management in the Solaris
environment. For more information, go to http://sunsolve.sun.com/search/document.do?assetkey=1-26-101688-1.
When scanning for missing patches for the first time, if selecting
Latest for current TL as the Maintenance Strategy Model,
the discovery scan finds a missing patch called AIX_Latest.
After installing the patch on the endpoints and receiving confirmation that it
installed successfully, subsequent scans find the AIX_Latest patch
missing again.
This known limitation is caused by a Service Update Management Assistant
(SUMA) issue.
If you do not have the ability to create a complete image of your Tivoli
Intelligent Orchestrator computer, follow the information in this section to
back up your database and save the current Tivoli Intelligent Orchestrator and
core component installation directories.
- Note:
- A full Tivoli Intelligent Orchestrator image is the supported backup
method.
Before you begin to back up or restore the database, ensure that all
running workflows are stopped, and then stop Tivoli Intelligent
Orchestrator.
- Log on as tioadmin.
- Ensure that Tivoli Intelligent Orchestrator is running. For
instructions see Common tasks for Tivoli Intelligent Orchestrator.
- Stop all running workflows.
- Change to the $TIO_HOME/tools directory.
- From the command prompt, run the following commands:
./cancel-all-in-progress.sh
./clean-up-deployment-requests.sh
The log files cancel-all-in-progress.log and
clean-up-deployment-requests.log are created with the results of the
commands.
- Stop Tivoli Intelligent Orchestrator. For instructions see Common tasks for Tivoli Intelligent Orchestrator.
- Stop all running applications on the Tivoli Intelligent Orchestrator
server.
To back up the database:
- Ensure that you have completed the steps in Before backing up or restoring the database.
- Open the file $TIO_HOME/config/dcm.xml to
verify the database name and user name. The name element
contains an alias for the database name, and the username element
contains the user name. This information is specified Tivoli
Intelligent Orchestrator installation.
- Change the user to your DB2 instance owner. For example, if the
instance owner is db2inst1, run the command:
su - db2inst1
- Run the following command to check for other running applications:
db2 list applications
- If the command lists other applications, run the following command to
disconnect them:
db2 force applications all
- If you are not connected to the database, use the db2 connect
command to connect to the database.
- Back up the database with the following command:
db2 backup db db_name user user_name using password to location
- db_name
- The name of the database.
- user_name
- The user name of the user performing the backup.
- password
- The password used to authenticate the user name.
- location
- The location that the database backup will be stored.
- The full path of the location is required. The specified directory
must already exist.
- The instance owner user must have write permissions to the specified
path.
- Consider saving the backup in a location that is accessible from the
Tivoli Intelligent Orchestrator computer so that you do not need to transfer
the backup to a second location when you are performing backup and restore
operations.
For example:
db2 backup db TC user db2inst1 using pa55w0rd to /home/db2inst1/backup
- If you did not select a target directory that is accessible to the Tivoli
Intelligent Orchestrator computer, transfer the backup to an accessible
location.
A backup has been created and can be used to restore the Tivoli Intelligent
Orchestrator database when it is required.
To restore the database:
- Ensure that you have completed the steps in Before backing up or restoring the database.
- Open the file $TIO_HOME/config/dcm.xml to
verify the database name and user name. The name element
contains an alias for the database name, and the username element
contains the user name. This information is specified in the Tivoli
Intelligent Orchestrator installation.
- Change the user to your DB2 instance owner. For example, if the
instance owner is db2inst1, run the command:
su - db2inst1
- Run the following command to check for other running applications:
db2 list applications
- If the command lists other applications, run the following command to
disconnect them:
db2 force applications all
- End the DB2 session with the command db2 terminate.
- Stop DB2 with the command db2stop.
- Stop all DB2 interprocess communication with the command
ipclean.
- Start DB2 with the command db2start.
- Delete and uncatalog the existing database with the command:
db2 drop db db_name
where db_name is the name of the database. For
example:
db2 drop db TIOINTER
- Attach to the local host alias with the command:
db2 attach to LHOST0 user user_name using password
For example:
db2 attach to LHOST0 user db2inst1 using pa55w0rd
- Restore the backed up database with the command:
db2 restore db db_name user user_name using password from location
- db_name
- The name of the database.
- user_name
- The user name of the user restoring the database.
- password
- The password used to authenticate the user name.
- location
- The location where the backup is stored. The full path of the
location is required.
For example:
db2 restore db tc user db2inst1 using pa55w0rd from /home/db2inst1/backup
The Tivoli Intelligent Orchestrator database has been restored. The
database backup remains in place so that you can restore the database whenever
it is required.
To back up the database:
- Ensure that you have completed the steps in Before backing up or restoring the database.
- Switch to the user tioadmin.
- Open the file $TIO_HOME/config/dcm.xml to
verify the database name and user name. The name element
contains an alias for the database name, and the username element
contains the user name. This information is specified Tivoli
Intelligent Orchestrator installation.
- Switch the user to Oracle.
- Connect to the database as sys with the following
command:
sqlplus "sys/think4me@name as sysdba"
where name is the database name.
- Run the following command to locate all the Oracle data
files that need to be backed up:
select name from v$datafile;
A list of .dbf files is returned. Record the locations of
these files. When you restore the database, you will need to know the
location of these files.
- Ensure that the Oracle database instance and listener are offline.
For instructions for checking the status, see Common tasks for Oracle.
- Create a backup directory in a convenient location.
- Copy the .dbf files identified in step 6 and the entire $ORACLE_HOME/dbs directory to the backup
directory that you created.
- Create a text file in the backup directory and with the locations of each
.dbf file.
- Bring the Oracle database instance and listener back online. For
instructions, refer to your Oracle documentation.
A backup has been created and can be used to restore the Tivoli Intelligent
Orchestrator database when it is required.
To restore the database:
- Ensure that you have completed the steps in Before backing up or restoring the database.
- Switch to the user tioadmin.
- Open the file $TIO_HOME/config/dcm.xml to
verify the database name and user name. The name element
contains an alias for the database name, and the username element
contains the user name. This information is specified Tivoli
Intelligent Orchestrator installation.
- Switch to the user oracle.
- Connect to the database as the sys user with the following
command:
sqlplus "sys/think4me@name as sysdba"
where name is the database name.
- Run the following command to locate all the Oracle data files that are
currently in use.
select name from v$datafile;
A list of .dbf files is returned.
- Ensure that the Oracle database instance and listener are offline.
For instructions for checking the status, see Common tasks for Oracle.
- Delete the listed .dbf files.
- Delete the $ORACLE_HOME/dbs directory.
- Change the current work directory to the backup directory that was created
during the backup.
- Get the locations of the .dbf files from the text file that was
created during the backup.
- Copy the .dbf files locations listed in the text file.
- Copy the entire backed up dbs directory to $ORACLE_HOME.
- Bring Oracle database instance and listener back online. For
instructions, refer to your Oracle documentation.
- Start Tivoli Intelligent Orchestrator. For instructions see Common tasks for Tivoli Intelligent Orchestrator.
The Tivoli Intelligent Orchestrator database has been restored. The
database backup remains in place so that you can restore the database whenever
it is required.
Follow the instructions in Backing up directory server data.
Back up the following directories before you apply the fix pack so that you
can recover the files at a later time or if you encounter errors during
installation.
- Tivoli Intelligent Orchestrator installation directory
- This directory contains Tivoli Intelligent Orchestrator and files for
dynamic content delivery service. The default location is:
/opt/IBM/tivoli/tio
- Note:
- If you installed the dynamic content delivery service in a different
directory, ensure that you back up that directory.
- Agent Manager installation directory
- The default location is:/opt/IBM/AgentManager
This appendix describes common tasks for starting and stopping
applications.
You can check the status of Tivoli Intelligent Orchestrator and stop and
start Tivoli Intelligent Orchestrator.
- Verify the following requirements:
- Change to the $TIO_HOME/tools directory.
- Run the appropriate command:
- Check status
-
tioStatus.sh wasadmin_username wasadmin_password
- Start Tivoli Intelligent Orchestrator
-
./tio.sh start wasadmin_username wasadmin_password
- Stop Tivoli Intelligent Orchestrator
-
./tio.sh stop wasadmin_username wasadmin_password
- Note:
- After stopping the provisioning server, some WebSphere client Java(TM)
processes may still be running. To manually stop these Java processes
before restarting the provisioning server, run the command pkill -9
java.
The following parameters are used in the commands:
- wasadmin_username
- The WebSphere Application Server administrator user name. The
default is wasadmin.
- wasadmin_password
- The password for the specified user name.
To run a workflow from the Web interface:
- Click Automation > Workflows.
- Search for the workflow name. The search results are
displayed.
- In the search results, find the row with the workflow to run. In
that row, click the Actions menu icon, and then click
Run The Input Parameter for Workflow window is displayed.
- Click Run in the Input Parameter for Workflow window.
- Check the results of the workflow. Click Automation >
Workflow Status to view workflow status.
The following steps describe tasks for the WebSphere Application Server
profile for Tivoli Intelligent Orchestrator, tioprofile.
- Change to the directory $TIO_HOME/tioprofile/bin.
- Run the appropriate command:
- Check status
-
./serverStatus.sh server1 -username wasadmin_username -password wasadmin_password
- Start WebSphere Application Server
-
./startServer.sh server1
- Stop WebSphere Application Server
-
Stop the profile tioprofile:
./stopServer.sh server1 -username wasadmin_username -password wasadmin_password
./startServer.sh server1
The following parameters are used in the commands:
- wasadmin_username
- The WebSphere Application Server administrator user name. The
default is wasadmin.
- wasadmin_password
- The password for the specified user name.
- Start the WebSphere Application Server.
- Enable cookies in the Web browser that you use to access the
administrative console in order for the administrative console to work
correctly.
- Open a browser window and enter the following URL:
https://hostname:9043/ibm/console
where hostname is the fully-qualified domain
name of the computer where the application server is running. For
example:
https://tpmserver.example.com:9043/ibm/console
- Log in with your WebSphere Application Server user ID and password.
The default user ID is wasadmin.
Use the following commands to check server status and to start and stop the
server. For more information, refer to the Tivoli Directory Server
documentation.
Checking Tivoli Directory Server status
ibmdirctl -D cn=root -w password -h hostname status
Starting Tivoli Directory Server
ibmdirctl -D cn=root -w password start
Stopping Tivoli Directory Server
ibmdirctl -D cn=root -w password stop
The following subsections describe common tasks for DB2:
To verify that DB2 is running, you can run the db2start
command.
- Switch to the DB2 instance owner. For example, if you are using the
default instance owner db2inst1, run the command.
su - db2inst1
- Run the command to start DB2:
db2start
DB2 is started if it is not running already. If DB2 is already
running, the following message is displayed.
SQL1026N The database manager is already active
To start a DB2 instance:
- Log on as the instance owner. The default instance owner for the
Tivoli Intelligent Orchestrator database instance is
db2inst1.
- Run the following command from the command line:
db2start
To stop DB2:
- Stop Tivoli Intelligent Orchestrator. For instructions, see Common tasks for Tivoli Intelligent Orchestrator.
- Log on as the instance owner. The default instance owner for the
Tivoli Intelligent Orchestrator database instance is
db2inst1.
- Display all applications and users that are connected to the specific
database that you want to stop. To ensure that no vital or critical
applications are running, list applications. You need SYSADM,
SYSCTRL, or SYSMAINT authority for this.
- Force all applications and users off the database. You require
SYSADM or SYSCTRL authority to force users.
- To stop the instance type using the command line, enter:
db2stop
- Note:
- The db2stop command can only be run at the server. No
database connections are allowed when running this command; however, if
there are any instance attachments, they are forced off before the instance is
stopped.
- To verify the status of Oracle Database, log on to SQL*Plus. The
status of the database is displayed when you log on.
- To verify the status of the Oracle Database listener, run the following
command:
lsnrctl status
For information about starting and stopping Oracle, refer to your Oracle
documentation.
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:
- Go to 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 site.
The following section includes important information about this document
and its use.
Table 5. Revisions
| Created/Revised by
| Date of Creation/Update
| Summary of Changes
|
| DR
| June 1, 2007
| Document created
|
| NY
| June 12, 2007
| Updates to disk space requirements and fix pack installation instructions
for APAR IY99859
|
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.
AIX, DB2, DB2 Universal Database, IBM, eServer(TM), iSeries, pSeries,
zSeries, POWER(TM), the IBM logo, Passport Advantage(R), Tivoli, the
Tivoli logo, Lotus(R), Rational(R), and WebSphere are trademarks or
registered trademarks of International Business Machines Corporation in the
United States, other countries, or both.
Intel, Itanium(R), and Pentium(R) are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States,
other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft and Windows are registered trademarks of Microsoft Corporation in
the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and
other countries.
Other company, product, and service names may be trademarks or service
marks of others.