IBM Tivoli Intelligent Orchestrator Fix Pack 1, Readme
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
Manually backing up the installation
Manually installing the fix pack
Contacting customer support
Notices and trademarks
First Edition, December 2006
- Note:
- Before using this information and the product it supports, read the
information in the section "Notices and trademarks".
(C) Copyright IBM(R) Corporation 2006. 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.1.
- 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.
- Note:
- The Tivoli Intelligent Orchestrator information center will not be available
until the end of January. You can refer to the
Tivoli
Provisioning Manager information center for information about using all
features of the product except for features specific to Tivoli Intelligent
Orchestrator such as capacity on demand. The fix pack download page
will be updated with more information when the Tivoli Intelligent Orchestrator
information center is available.
The following updates are included in Version
5.1.0.1:
- Coexistence with Tivoli Configuration Manager
-
If you are an existing Tivoli Configuration Manager customer you can
continue using the Tivoli Management Framework infrastructure while taking
advantage of the capabilities of Tivoli Intelligent Orchestrator. This
capability is to bring your existing Tivoli Management Framework
infrastructure within the management of the Tivoli Intelligent Orchestrator
provisioning server. A stepped process is supported so that you can
gradually start to work with the Tivoli Intelligent Orchestrator interfaces
while maintaining your Tivoli Management Framework environment. When
you are ready, you can make a plan to gradually migrate to a full
implementation of Tivoli Intelligent Orchestrator.
Support for coexistence was added to Tivoli Provisioning Manager for
Software Version 5.1 and is included in Tivoli Intelligent Orchestrator
5.1.0.1 when you apply the fix pack.
- Note:
- The Fast Start installation does not support coexistence with Tivoli
Configuration Manager.
For information about setting up coexistence, refer to the following
information:
- Upgraded agent manager and common agent
- This fix pack includes an update to agent manager and the common
agent.
- The agent manager is updated during the fix pack installation.
- You must upgrade the common agent on depot servers and endpoints after you
have installed the fix pack. For more information, see Upgrading the common agent.
- Tivoli Provisioning Manager for OS Deployment Embedded Edition
- The fix pack includes updates to Rembo Toolkit which is now available as
Tivoli Provisioning Manager for OS Deployment Embedded Edition. Updates
include:
- Tivoli Provisioning Manager for OS Deployment Embedded Edition is
globalized
- Static IP support for imaging
- Support for 32-bit and 64-bit images
You can perform the upgrade after applying the fix pack. For more
information, see Upgrading Rembo Toolkit.
- Installation on AIX(R) with a separate DB2(R) node
- You can install Tivoli Intelligent Orchestrator with DB2 on a separate
computer. To install in this topology, you must manually install Tivoli
Intelligent Orchestrator. For more information, refer to the
Tivoli Intelligent Orchestrator Installation Guide for additional
topologies on AIX: DB2 on a separate node.
- Wake on LAN capability
- Wake on LAN provides the ability to start a computer that is currently
turned off. You can configure Tivoli Intelligent Orchestrator to send a
wake on LAN command to an endpoint. For more information, see
"Setting up Wake on LAN" in the
information
center.
- Simple software distribution for Linux(R) and UNIX(R)
- Simple software product distribution support for Linux and UNIX target
computers has been added to the existing Windows(R) support that was
available in Version 5.1.0.1. For more
information, see "Simple software product distribution" in the information center.
- File distribution
- You can use file distribution to copy files in a specified file repository
to selected target endpoints without installing them. For more
information, see "Distributing files" in the information center.
- Device manager federated agent
- If you use branch office distribution, a device manager federated agent
can be deployed in each branch or subsection of an environment.
Endpoints can be configured to poll the device manager federated agent in the
branch to ask for jobs and will send results to the same server. The
device manager federated agents report status and receive new jobs from the
device manager federator on the Tivoli Intelligent Orchestrator server.
- Local common agent installation
- You can create an image for the common agent and then use the image and
response file to install the common agent locally on an endpoint. After
the agent is installed, you can use discovery to update Tivoli Intelligent
Orchestrator with information about the installed agent. For more
information, see "Installing the common agent and subagents using a
standalone installation" in the
information
center.
- Client certificate authentication
- A self-signed client user certificate can be used to authenticate to
Tivoli Intelligent Orchestrator. Using this certificate allows users to
skip the default form-based login authentication that normally prompts
them for the user ID and password. Client certificate based
authentication can only be used if the Tivoli Intelligent Orchestrator was
installed using the regular installer and read-only LDAP has been
configured. This feature is not supported with the Fast Start
installation. For more information, see "Read-Only Lightweight
Directory Access Protocol" in the
information
center.
- Activity Plan Editor
- The Activity Plan Editor plans enable you to define a group of activities
in the Activity Plan Editor, submit the plan to run, and monitor the progress
of the plan. Activities are single operations that are performed on a
set of targets at specified times. Operations include tasks, software
distribution, and inventory operations. Activities contained in a plan
can have dependencies associated with them which define circumstances under
which the activity is executed. The execution of the operation defined
in the activity is performed by the application to which the operation
belongs. The group of activities forms the activity plan.
- Discovery enhancements
- Enhancements to discovery include:
- Ability to interface directly to the Change and Configuration Management
Database rather than exporting a discovery book and importing it into Tivoli
Intelligent Orchestrator.
- Ability to discovery more information about WebSphere Application Server
and DB2 so that Tivoli Intelligent Orchestrator can provide additional control
over these applications. For example, you can use Tivoli Intelligent
Orchestrator to start and stop instances or capture an existing installation
and deploy another installation with the same configuration.
- Enhancements to the information imported from the Change and Configuration
Management Database for some hardware resources.
- Support for performing SMB discovery using a Windows domain
account.
- Firewall traversal
- Tivoli Intelligent Orchestrator provides a built-in proxy relay collector
that you can use if the Tivoli Intelligent Orchestrator servers are separated
from endpoints by one or more intermediary networks because of firewall
policies or address space concerns. For more information, see
"Using a proxy relay collector for communication behind a firewall" in
the
information center.
- Tivoli IT Service Management integration
- If you have Tivoli IT Service Management, you can work with Tivoli
Intelligent Orchestrator by integrating parts of its user interface into your
existing product. For more information, see "Tivoli IT Service
Management integration" in the
information
center.
- Client-based remediation Beta for patch management
- Client-based remediation uses a "patch policy", and remediation is
initiated by the endpoint, instead of Tivoli Intelligent Orchestrator.
Client-based remediation is available as a Beta for deployment to Windows
endpoints only.
Fix pack V 5.1.0.1 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,
refer to the file 5.1.0-TIV-TIO-FP0001.DEFECTS
or 5.1.0-TIV-TPM-FP0001.DEFECTS.
To download the defects list:
- Go to the IBM Support Web site:
http://www.ibm.com/support
- In the Support topics list, click Downloads and
Drivers.
- In the Browse product support section, under
Software list, click Tivoli.
- In the search box, enter the fix pack number:
- For the Tivoli Intelligent Orchestrator Fix Pack V
5.1.0.1, enter:
5.1.0-TIV-TIO-FP0001.
- For the Tivoli Provisioning Manager Fix Pack V
5.1.0.1, enter:
5.1.0-TIV-TPM-FP0001.
- Click Search. The Download Results page is
displayed.
- On the Download Results page, depending on your search, one of the
following links is displayed:
- Tivoli Intelligent Orchestrator Fix Pack
5.1.0-TIV-TIO-FP0001
- Tivoli Provisioning Manager Fix Pack 5.1.0-TIV-TPM-FP0001
- Click on the displayed link. The corresponding page is
displayed.
- For a list of defects that are corrected by this fix pack, click on
5.1.0-TIV-TIO-FP0001-DEFECTS (HTTP) or
5.1.0-TIV-TPM-FP0001-DEFECTS (HTTP).
Fix Pack V 5.1.0.1 supports all the hardware and
software that is supported by Tivoli Intelligent Orchestrator V
5.1.0. The following considerations apply to the fix pack
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
- When Software Package Editor is updated with Tivoli Intelligent
Orchestrator Fix Pack 1, you cannot use these applications to connect with a
Tivoli Intelligent Orchestrator 5.1 installation that has not been
updated with Fix Pack 1.
- 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.
- Coexistence with Tivoli Configuration Manager
- The Fast Start installation does not support coexistence with Tivoli
Configuration Manager.
- Agent manager and common agent version
- The agent manager is updated when you install Fix Pack 1. You must
also upgrade the common agent on all depot servers after you have applied the
fix pack.
- Reports
- Reports are updated during the fix pack installation, and some reports are
deprecated after the fix pack is installed. The reports remain for your
reference. You cannot run the reports, but you can view the SQL query
for the reports and manually make changes to the SQL query, if
required.
Deprecated reports are removed during an upgrade between major releases of
Tivoli Intelligent Orchestrator.
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.1. This includes setting up the database
that you plan to use, LDAP, and so on. Thoroughly review the following
list of prerequisites for installation before proceeding with the
installation:
- Identify your current installation situation:
- First time 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..
- Important:
- The Tivoli Intelligent Orchestrator Installation Guide has been
updated with a preinstallation checklist to help you to verify all
installation requirements as well as recovery information for possible
installation errors. The checklist for each operating system is
included in the Fix Pack 1 download in the preinstall_checklist
subfolder.
For Linux on iSeries, pSeries, or zSeries 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.
- First time 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.
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Verify that the currently installed version of Tivoli Intelligent
Orchestrator is operational before you begin the installation of Fix pack
1. The fix pack is compatible with version
5.1.0.0.
To determine the version of Tivoli Intelligent Orchestrator:
- Go to $TIO_HOME/config, where TIO_HOME is the Tivoli
Intelligent Orchestrator installation directory.
- Open the file named,
build-version.properties.
- Verify the information in the field,
current.version.
- Ensure that you can log in to Tivoli Intelligent Orchestrator and run the
workflow named no_operation, before installing the fix pack.
If the workflow runs successfully, this verifies that the deployment engine in
Tivoli Intelligent Orchestrator is working properly.
- Cancel all running workflows and clear failed, deleted, and canceled
workflows.
- AIX, Solaris and Linux
-
- Start Tivoli Intelligent Orchestrator. For more information, refer
to the section, Administering Tivoli Intelligent Orchestrator in
the Installation Guide.
- Open a command window.
- Switch to the $TIO_HOME/tools directory where
$TIO_HOME is the Tivoli Intelligent Orchestrator installation
directory.
- Run the following command:
./cancel-all-in-progress.sh
./clean-up-deployment-requests.sh
- 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.
- Perform a full backup of your current installation. See Backing up your installation.
- 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:
| Operating System
| Tivoli Intelligent Orchestrator
| Agent Manager
| Dynamic Content Delivery Service
|
| Windows
| 5.1.0-TIV-TIO-WIN-FP0001.zip
| AM_V13_WIN.zip
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. win32\setup.exe.
|
| AIX
| 5.1.0-TIV-TIO-AIX-FP0001.zip
| AM_V13_AIX.tar
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. (aix/setup.bin)
|
| Solaris
| 5.1.0-TIV-TIO-SOLARIS-FP0001.zip
| AM_V13_SUN.tar
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. (solaris/setup.bin)
|
| Linux
| 5.1.0-TIV-TIO-LINUX-FP0001.zip
| AM_V13_LIN.tar
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. (linux/setup.bin)
|
| PPC Linux (AM_V13_LIN_PPC.tar)
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. (linuxppc/setup.bin)
|
| Linux on zSeries (AM_V13_LIN_zSeries.tar)
| Dynamic Content Delivery (cds_images.zip)
Unzip the file to a temp directory. (linuxzSeries/setup.bin)
|
- 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.
- Place the dynamic content delivery service image file for your operating
system (setup.bin) in fp_temp/CDS.
- 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.
- Ensure that WebSphere Application Server is stopped too.
Use the serverStatus command to obtain the status of the
WebSphere Application Server profile for Tivoli Intelligent
Orchestrator. The stopServer command stops the
server.
- Change to the $TIO_HOME/tioprofile/bin directory, where
$TIO_HOME is the Tivoli Intelligent Orchestrator installation
directory.
- Run the command:
stopServer app_server -username was_adminID -password password
- app_server
- The name of the application server. The default is
server1.
- was_adminID
- The WebSphere Application Server administrator user name. The
default is wasadmin
- password
- The WebSphere Application Server administrator password for the specified
user name.
- Ensure that the Tivoli Intelligent Orchestrator database 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.
- 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 perform create a backup image of the entire Tivoli Intelligent
Orchestrator computer using your standard backup tools and processes.
If the directory server is on a separate computer, also ensure that you back
up the directory server data on that computer as described in Backing up directory server data.
If you want to recover your current Version 5.1.0.0
installation, or if you encounter an error during installation, You can use
this backup to restore your current installation without the fix pack.
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.
- 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
- 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.0.0, 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 Tivoli Intelligent Orchestrator Version
5.1.0.0 installation, the backed up 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
- Change to the tds_installdir/sbin, where
tds_installdir is the directory where Tivoli Directory
Server is installed.
- 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
'tioadmin' 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.
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 tds_installdir/sbin, where
tds_installdir is the directory where Tivoli Directory
Server is installed.
- 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
'tioadmin' 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.
- Ensure that you meet all the requirements as described in Preinstallation checklist.
Ensure that the directory server and database are running, and that Tivoli
Intelligent Orchestrator and WebSphere Application Server are stopped.
- Log in to the Tivoli Intelligent Orchestrator computer as root
- Change to the fp_temp directory.
- Run the appropriate 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.
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.
- Ensure that Tivoli Intelligent Orchestrator is started.
- Log on to the WebSphere Application Server administration console.
- Select Resources > JDBC Providers.
- Select server1 for the scope, the click
Apply.
- In the list of JDBC providers below, click CDSJDBCProvider
- Click Additional Properties > Data
sourcesCDSDataSource.
- Click Related Items > J2EE Connector Architecture (J2C)
authentication data entries
- Click CDSDataAuth. The user CDSSCHEMA should
be displayed with the password ******.
- Change the password to a new valid password, and then click
Apply.
- Click Save, and then click Save again.
- Restart server Tivoli Intelligent Orchestrator so that the changes take
effect.
- 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 9.
- Verify your changes:
- Connect to the database with the new password:
sqlplus CDSSCHEMA/new_password@db_name
- Log on to the dynamic content delivery service console.
This section describes important updates to apply to depot servers and
endpoints after installing Fix Pack 1.
You must upgrade the common agent on all depot servers and endpoints after
installing Fix Pack 1. The instructions in this section are an update
to the information center topic "Upgrading the common agent".
To upgrade the common agent, you must uninstall existing installed agents
and then install the new common agent.
- Important:
- As you perform the upgrade, ensure that you select the correct software when
you uninstall the old common agent and then install the new common
agent.
- Version 5.1.0.0
- Tivoli Common Agent Stack for TPM V5.1
- Version 5.1.0.1
- Tivoli Common Agent Stack
Upgrading the common agent on depot servers
If you are using depot servers, upgrade the depot servers before you
upgrade endpoints.
- Verify that a service access point other than the Common Agent service
access point (SAP) exists on each depot server. This service access
point must support the Device.ExecuteCommand command.
- Remove the common agent from depot servers. You can use the
Uninstall Software Products page or use the uninstaller in the home directory
where the common agent was installed. The common agent for Tivoli
Intelligent Orchestrator Version 5.1.0.0 is Tivoli
Common Agent Stack for TPM V5.1.
- Uninstall each depot server:
- Click Inventory > Infrastructure Management >
Depots.
- Next to the depot server, click Delete.
- Add each depot server that you removed.
- Click Inventory > Infrastructure Management >
Depots.
- Click Edit > Add Depot.
- Specify the appropriate options and then click Save. If
you were using the depot services agent before you removed the depot, ensure
the Install the depot agent services option is selected.
Upgrading the common agent on endpoints
After you have upgraded depot servers, upgrade the common agent on
endpoints.
- Verify that a service access point other than the Common Agent service
access point (SAP) exists on each endpoint. This service access point
must support the Device.ExecuteCommand command.
- Uninstall the existing common agent. You can use the Uninstall
Software Products page or use the uninstaller in the home directory where the
common agent was installed. The common agent for Tivoli Intelligent
Orchestrator Version 5.1.0.0 is
TCA-1.3.0.26.
- Install the new common agent. The following steps describe how to
install the default common agent from the Web interface:
- Note:
- The default common agent does not include the client-based remediation
subagent. To install the common agent with client-based
remediation subagent, you must use the Install Software Stacks page and select
the TCA with Client Based Remediation Stack as the software stack
to install.
To install the default common agent:
- In the navigation pane, click Software Management >
Install > Common Agent.
- Follow the instructions on the Install Common Agent page:
- Type a relevant name for the common agent installation task.
- Select the common agent software stack for the task. The new common
agent stack is called Tivoli Common Agent Stack.
- Select the Show computers missing any selected software box to filter the
target computers based on missing software.
- Select one or more target computers for the task.
- If required, select the Credentials check box and specify the credentials
for creating a Remote Execution and Access (RXA) service access point on each
target computer. If no default service access points (SSH or RXA) exist
on the target computers, you can specify here the credentials for an RXA
service access point that will be created on each target computer.
- Schedule the task to run immediately or at a specified time.
- Configure the notification settings for the task.
- Save as favorite task, if needed.
- Click Submit.
The new version of the Rembo Toolkit is now available as Tivoli
Provisioning Manager for OS Deployment Embedded Edition. These
instructions will help you upgrade your Rembo Toolkit to the latest
version. All of your existing operating system images are preserved
during this upgrade.
The instructions will help you upgrade your existing Rembo Toolkit to
Tivoli Provisioning Manager for OS Deployment Embedded Edition if the
following are true:
- You were using an existing Tivoli Intelligent Orchestrator 5.1
installation before applying fix pack.
- You have one or more Rembo Toolkit 4.0 boot servers installed using
Tivoli Intelligent Orchestrator and you have images that were captured with
the Rembo server.
- Note:
- When you installed Fix Pack 1, the rembo.tcdriver automation package
was installed and the data for all of the Rembo data model objects were
automatically migrated.
To upgrade your Rembo Toolkit to Tivoli Provisioning Manager for OS
Deployment Embedded Edition:
- Navigate to Inventory > Manage Inventory >
Computers and find the computer that has the Rembo Toolkit
installed.
- Click on the computer name.
- Click the Software tab.
- Next to Rembo Toolkit 4.0, Actions >
Upgrade.
The Rembo Toolkit is updated. The software installation now appears
as TPM for OS Deployment EE.
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.
To update an automation package:
- Create the migration workflows that will perform the data model
changes. In the workflows, include the data model queries to make the
required changes for your automation package. The workflows must not
require any input parameters to run.
- Create an <update> section in the file
TC-INF/tc-driver.xml for your automation package. The
following example shows a section for an update to an automation package at
the Tivoli Intelligent Orchestrator Version 5.1.0.0
level.
<update version="5.1.0.1">
<item name="workflow/Migrate/RemoveOldObjects_MigrateDCM_5_1_0_1.wkf" action="update-workflow" />
<item name="workflow/Migrate/InsertNewObjects_MigrateDCM_5_1_0_1.wkf" action="update-workflow" />
</update>
- In the <update> element, specify the Tivoli Intelligent
Orchestrator version for this update. For migration workflow that
update the automation package for Fix Pack 1, use the value
5.1.0.1.
- Create an <item> element for each migration workflow for the
specified version.
- Consider using a naming convention for your migration workflows.
The example uses MigrateDCM_5_1_0_1 at the end of the migration
workflow file names.
- Consider storing the migration workflows in a separate directory.
For example, workflows/Migrate.
- The value for the action attribute is always
update-workflow.
- Save your changes to tc-driver.xml and repackage the
automation package.
- Install the updated automation package. The migration workflows are
registered with Tivoli Intelligent Orchestrator. They are added to a
master update workflow called __master_tcdriver_udpate_.
This workflow runs when the deployment engine starts.
- Restart Tivoli Intelligent Orchestrator so that the deployment engine is
restarted.
When the deployment engine starts, it runs the workflow
__master_tcdriver_udpate_ and runs the migration workflows that are
registered. During this migration process, the deployment engine does
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 stops. Check
the workflow execution log for the deployment request for the
__master_tcdriver_udpate_ workflow and correct any errors in the
migration workflow that failed. To view workflow execution logs from
the Web interface:
- Click Automation > Workflow Status.
- Search for the __master_tcdriver_udpate_ workflow.
- Click the workflow execution ID for the
__master_tcdriver_udpate_ workflow in the search results.
The log for the workflow execution is displayed.
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, it therefore recommended that you restore your
backup of Tivoli Intelligent Orchestrator 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
- The agent manager
- The logs subdirectory of the agent manager installation
directory. The default agent manager installation directory is:
/opt/IBM/AgentManager
- The dynamic content delivery service
- The default location for the dynamic content delivery service logs
is:
/opt/ibm/tivoli/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.
- Try to apply the fix pack again.
For information about the fix pack installer, see Uninstallation information.
The information center is updated for Tivoli Intelligent Orchestrator
Version 5.1.0.1. You can view the updated Tivoli
Intelligent Orchestrator information center on ibm.com, or you can
download the latest version of the product information after installing the
product.
- Note:
- The Tivoli Intelligent Orchestrator information center will not be available
until the end of January. You can refer to the
Tivoli
Provisioning Manager
Information updates for
information about using all features of the product except for features
specific to Tivoli Intelligent Orchestrator such as capacity on demand.
The fix pack download page will be updated with more information when the
Tivoli Intelligent Orchestrator information center is available.
- Go to
Information updates page in the information
center.
- Follow the instructions on the page.
The following subsections highlight additional important changes to the
documentation.
The Tivoli Intelligent Orchestrator Installation Guide has been
updated with a preinstallation checklist to help you to verify all
installation requirements as well as recovery information for possible
installation errors.
- The checklist for each operating system is included in the Fix Pack 1
download in the preinstall_checklist subfolder.
- You can view the complete updated installation guides in the latest information center.
In Chapter 2, "Creating a coexistence environment", the section
"Step 2: Installing patches on the IBM Tivoli Management Framework
environment" describes installation of fixes, including the Software
Distribution Server fix. Before applying the Software Distribution
Server fix, ensure that you have stopped the Tivoli Intelligent Orchestrator
server.
If you are using an image to perform a standalone installation, note the
following updates apply to the information center topic "Installing the
common agent and subagents using a standalone installation". This
information does not apply to an installation of the common agent from the Web
interface.
- Note:
- For Tivoli Intelligent Orchestrator Version 5.1.0.1,
client-based remediation is available as a Beta for deployment to Windows
endpoints only.
When you create an image of the common agent, the image contains all
subagents by default. If you do not want to use client-based
remediation you must remove the subagent from the image before you use install
it on an endpoint.
To remove the subagent for client-based remediation from the image,
delete the following files from the subagents subfolder of the
image.
com.ibm.tivoli.tpm.compliance.remediation.subagent.jar
com.ibm.tivoli.tpm.compliance.remediation.commons.jar
If you are distributing a truststore file with installation of the common
agent, you must update the scripts install.bat (for Windows
endpoints) and install.sh (for UNIX or Linux endpoints) to
copy the truststore file to the correct location on endpoints. Perform
the following steps:
- Verify settings in the response file
caInstall.rsp.
- Add the following commands at the beginning of the scripts. If are
not installing the common agent in the default location, replace
c:\program files\tivoli\ep\cert and
/opt/tivoli/ep/cert with the correct full path.
- install.bat
-
mkdir "c:\program files\tivoli\ep\cert"
copy d:\windows\cert\agentTrust.jks "c:\program files\tivoli\ep\cert"
- install.sh
-
mkdir -p /opt/tivoli/ep/cert
cp /media/cdrom/linux86/cert/agentTrust.jks /opt/tivoli/ep/cert
In addition to the common agent installation requirements described in
"Requirements for common agent installation" in the information
center, there is an additional requirement for installation on an HP-UX
endpoint.
The libc library must include support for IPv6. If you do
not have a current version of the libc library, apply patch
HP-UX patch PHCO_24400. For more information and to download the
patch, see: http://www.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_24400.
In the information center, the requirements for installing the common agent
state that 150 MB of space is required in the installation location,
/usr or /opt.
Most of the common agent installation files and the subagents are installed
in the /usr directory. The Common Inventory Technology (CIT)
subagent is installed in /opt and requires approximately 30 MB of
disk space.
- Note:
- For Tivoli Intelligent Orchestrator Version 5.1.0.1,
client-based remediation is available as a Beta for deployment to Windows
endpoints only.
If the Tivoli Intelligent Orchestrator server is running on Linux or UNIX
or does not have Internet access, you can use a Windows gateway computer to
act as a proxy for communication with the Windows Server Update
Services.
- Set up a Windows computer as your gateway.
- The computer must be defined in the Tivoli Intelligent Orchestrator data
model.
- Cygwin 1.5.10 or higher must be installed. Packages
for SSH and Wget must be installed.
- SSH credentials must be configured for the computer.
- Define the computer as the gateway in Tivoli Intelligent
Orchestrator.
- In the navigation pane, click System Management > Global
Settings.
- Click the Variables tab.
- Find the variable wsus-download-sever-name.
- Set the value of the variable to the name of the gateway server (the value
of the Name field).
- If the operating system for the gateway computer is not defined in the
data model, add a software resource for it.
- Navigate to Inventory > Manage Inventory >
Computers.
- Find the gateway computer and click its name in the search results.
- Click the Software tab.
- Click Edit > Add Software Installation.
- In the Name field, type the name of the operating
system.
- In the Software Definition list, select the software definition
that matches the operating system on the gateway computer.
- Specify any other required options and then click Save.
- Add a variable to the gateway computer to identify it as the proxy
server:
- In the navigation pane, search for the computer using the Find
field and click its name in the search results.
- Click the Variables tab.
- Add the variable wsus-proxy-server-enabled and set the value to
true. This variable determines if download through the proxy
is required or not. Since we are running all operations (cab file
download, cab file extraction, etc) on a remote Windows computer, all relevant
info has to be attached to this computer.
- Add the variable wsus-download-proxy-server-ip and specify the
proxy server IP.
- The remote Windows system server must have an HTTP SAP with WUA context
that will hold all relevant information on proxy server, such as the proxy
port, proxy user name, and proxy password.
For a regular installation, the users tioappadmin and
tioadmin are created. The tioappadmin user is the
default administrator user in the Web interface and has all permissions for
all objects in the data model.
If you are performing a Fast Start installation, only the
tioadmin user is created. The tioadmin user is
not assigned to an access group by default, so you must assign the permissions
to the user. To assign all permissions for all objects in the data
model:
- Log on to the Web interface with the user tioadmin.
- Click System Management > Manage Users.
- Click the tioadmin user.
- Select Edit > Assign Access Permissions.
- Under Available Access Groups, select sample:all-objects
- Under Available Permissions, select
sample:all-permissions
- Click Save.
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. See Recovering from installation errors for more information.
Before you uninstall the fix pack:
- Ensure that the database server and the directory server are both
running.
- Stop the Tivoli Intelligent Orchestrator server. For detailed
instructions on how to start and stop the servers in different environments,
refer to the installation guide that is supplied with the product.
- Ensure that the WebSphere Application Server is stopped.
To uninstall Fix Pack V 5.1.0.1 on, Linux systems
using the silent mode:
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Ensure that the database server and the directory server are both
running.
- Export the JAVA_HOME environment variable to
WAS_HOME/java where WAS_HOME is
the location of the WebSphere Application Server.
- Ensure that the DISPLAY variable is set and confirm that the
hostname of the server is correct.
- Change directory to 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 [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to uninstall the fix pack on AIX systems:
./updateSilent.sh -fixpack -uninstall /opt/ibm/tivoli/tio tpm51_fp1_aix
- The system completes the uninstallation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
To uninstall Fix Pack V 5.1.0.1 on AIX or Solaris
using the silent mode:
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Ensure that the database server and the directory server are both
running.
- Export the JAVA_HOME environment variable to
WAS_HOME/java where WAS_HOME is
the location of the WebSphere Application Server.
- Ensure that the DISPLAY variable is set and confirm that the
hostname of the server is correct.
- Change directory to 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 [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to uninstall the fix pack on AIX systems:
./updateSilent.sh -fixpack -uninstall /opt/ibm/tivoli/tio tio31_fp3_aix
- The system completes the uninstallation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
After you have completed the uninstallation procedure, you must redeploy
the EAR (expanded archive) files on the WebSphere Application Server.
To redeploy the EAR files:
- Log in to the Tivoli Intelligent Orchestrator server as user
tioadmin.
- Start the WebSphere Application Server.
- Run the command given below:
"$TIO_HOME/tools/was_deploy.sh" username password server base_DN
For Example:
"$TIO_HOME/tools/was_deploy.sh" wasadmin wasadmin server1 "dc=mycompany,dc=com"
- Note:
- Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- Stop the WebSphere Application Server.
To redeploy the EAR files:
- Log in to the Tivoli Intelligent Orchestrator server as user
tioadmin.
- On Linux systems only, you will need to set the file size limit to 20000
as below:
ulimit -n 20000
- Start the WebSphere Application Server.
- Run the command given below:
"$TIO_HOME/tools/was_deploy.sh" username password server base_DN
For Example:
"$TIO_HOME/tools/was_deploy.sh" wasadmin wasadmin server1 "dc=mycompany,dc=com"
- Note:
- Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user
name
- was_pwd with your WebSphere Application Server
password
- server with the Application server name
- base_DN with the Base Distinguished Name
of the Application server. The correct value for base_DN can
be obtained from the XML tag <root> in
$TIO_HOME/config/user-factory.xml.
- Note:
- Restart the system if you get an error similar to this and then reset the
ulimit size as above after restarting the system.
Too many open files
- Stop the WebSphere Application Server.
This section describes known limitations in this release of Tivoli
Intelligent Orchestrator V 5.1.0. Where applicable and
known, suggested workarounds are identified.
This section provides workarounds to problems that you might encounter
during the installation of the Fix pack.
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/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.
For an installation on Linux, you cannot log on to the dynamic content
delivery service console and the message The specified username or
password is incorect is displayed. In addition, SOAP services do
not start successfully. One the following messages appears in
$TIO_LOGS/soap/desoap_start.log.
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)
:
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
Perform the following actions:
- Log on as tioadmin.
- Stop Tivoli Intelligent Orchestrator.
- Create the directory $TIO_HOME/patch.
- Copy the file
$TIO_HOME/eclipse/plugins/com.ibm.pvcws.osgi.jar
to
$TIO_HOME/patch/com.ibm.pvcws.osgi.props.jar.
- In
$TIO_HOME/patch/com.ibm.pvcws.osgi.props.jar
remove all files except for properties files that start with
wsosgimessages. After the change, 14 files remain in the jar
file.
- Edit the file $TIO_HOME/tools/run-desoap.sh and modify
these lines:
Original: -Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar \
Change: -Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar:$TIO_HOME/patch/com.ibm.pvcws.osgi.props.jar \
Original: -noSplash -application launcher.CliLauncher \
Change: -noSplash -clean -application launcher.CliLauncher \
- Start Tivoli Intelligent Orchestrator and try to log on to the dynamic
content delivery service console again.
- Verify Web services started in the file
$TIO_LOGS/soap/desoap_start.log.
When you try to rerun the fix pack installation
unixUpgrade.sh or the post-installation script
postinstall.sh, an error message is displayed.
- Error about the eclipse directory
-
ERROR: Need to clean up /opt/ibm/tivoli/tio/eclipse before running post-install, exiting.
- Error about installing an automation package
-
ERROR COPCOM140E An unexpected error /opt/ibm/tivoli/tpm/xml/jumpstart_sample_for_Sparc.xml (The file access permissions do not allow the specified action.) occurred.
ERROR COPTDM150E An error occurred while the system installed the driver "jumpstart".
To fix the error about the eclipse directory, remove the
$TIO_HOME/eclipse directory before you run the fix pack
installation or post-installation script again.
To fix the error about automation package installation, you must manually
change the file permissions to 755 for the file that caused the
file permission error before you try to run the post-installation
script again. For example, if the file permissions for
jumpstart_sample_for_Sparc.xml caused the error during
migration of the Jumpstart automation package, run the following
commands:
cd $TIO_HOME/xml
chmod 755 jumpstart_sample_for_Sparc.xml
Also ensure that you remove the $TIO_HOME/eclipse directory
before you run the post-installation 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 Fix Pack 1, the deployment engine runs a workflow to migrate
automation packages provided with the product to the Fix Pack 1 level.
During this migration process, the deployment engine does 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. You must restore your Tivoli Intelligent Orchestrator and try to
apply the fix pack again.
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 Web site.
When you run Rembo Hardware discovery on a Sunfire 4200 AMD Opteron
computer with multiple network interfaces, more than one network interface is
has the Netboot Enabled option selected for network booting, but
only one network interface is physically connected. The
cpu.family attribute is also identified as Intel.
You can manually fix the information that was incorrectly
discovered.
- Navigate to Inventory > Manage Inventory >
Computers and find the Sunfire 4200 AMD Opteron computer.
- Disable network booting for one of the network interfaces:
- Expand Network Resources and find the network interface.
- In the row with the network interface, click Actions >
Properties.
- Clear the Netboot Enabled check box, and then click
Save.
- Correct the type of CPU identified by the discovery:
- Expand Hardware Resources.
- Find the cpu.family property and change its value to
AMD.
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 definition on in the Preferences page of the
Eclipse-based Software Package Editor.
- The presence of a firewall.
- Tivoli Intelligent Orchestrator is up and running.
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.
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.
To back up the database:
- Ensure that you followed the steps in Before backing up or restoring the installation.
- 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.
- 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 followed the steps in Before backing up or restoring the installation.
- 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
- 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.
- Attach to the database with the command:
db2 attach to db_name user user_name using password
- 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.
- Attach to the local host alias with the command:
db2 attach to LHOST0 user user_name using password
- Delete and uncatalog the existing database with the following command
db2 drop db db_name
where db_name is the name of the database.
- Restore the backed up database with the following 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.
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 followed the steps in Before backing up or restoring the installation.
- 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.
- 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.
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 followed the steps in Before backing up or restoring the installation.
- 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.
- 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.
- Start 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 section describes the manual installation of the Tivoli Intelligent
Orchestrator fix pack.
- Note:
- Only regular installation of the fix pack with
unixUpgrade.sh is officially supported.
To install Fix Pack V 5.1.0.1 using the silent
mode:
- Ensure that you meet all the requirements as described in Preinstallation checklist.
- On the Tivoli Intelligent Orchestrator server, ensure that both the
JAVA_HOME and WAS_HOME environment variables are
set.
- WAS_HOME variable
-
echo $WAS_HOME
The WAS_HOME variable is the location of the WebSphere
Application Server and the output would be similar to this:
/usr/WebSphere/AppServer
- JAVA_HOME variable
-
echo $JAVA_HOME
The output would be similar to this:
/usr/WebSphere/AppServer/java
- Log in to the Tivoli Intelligent Orchestrator server as
root.
- Source $TIO_HOME/.TCprofile, where
$TIO_HOME is the Tivoli Intelligent Orchestrator
installation directory.
- Change directory to fp_temp directory.
- Run the following command:
./updateSilent.sh -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]
For example, to install on AIX systems:
./updateSilent.sh -fixpack -install /opt/ibm/tivoli/tio tpm51_fp1_aix /fp_temp/installer
- The system completes the installation. A successful installation
gives an error level of 0. Review the log files located in
$TIO_HOME/logs/update directory for any errors.
Complete the following instructions after you install the fix pack.
- Back up the database from your fix pack installation using the backup
utility that is provided with the database.
- Log on as root.
- Ensure that the database server and the directory server are
running.
- Stop the Tivoli Intelligent Orchestrator server.
- Ensure that the WebSphere Application Server is stopped when the Tivoli
Intelligent Orchestrator server is stopped.
- Change the directory to
fp_temp\installer\utils.
- Run the following command:
./postinstall.sh was_user was_pwd server base_DN
- 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.
For example:
./postinstall.sh wasadmin wasadmin server1 "dc=mycompany,dc=com"
The log files for the post-installation script can be found in
the directory: $TIO_LOGS/fixpack.
- Note:
-
- Run the following command:
chmod -Rf 755 fp_temp
where fp_temp is the temporary directory where you
extracted the fix pack installer.
- Run the command
. $TIO_HOME/tools/setupCmdLine.sh
.
- Export JAVA_HOME=$WAS_HOME/java, where
$WAS_HOME is the WebSphere Application Server installation
directory.
- For a Solaris system with Oracle as the database, add the root
user to the group dba by editing /etc/group file.
- Update the Tivoli common agent services:
- Change to the fp_temp/CAS directory.
- Extract the contents of the agent manager image.
- Run the following command:
- AIX
-
setupaix.bin -is:javahome $JAVA_HOME -silent -W CASInstall.InstallType="upgrade" -W CASInstall.DBRuntimePassword="runtime_pwd" -W CASInstall.DBAdminPassword="admin_pwd" -W CASInstall.StartAfterReboot="False" -W CASInstall.StartAfterInstall="False"
- Linux
-
setuplinux.bin -is:javahome $JAVA_HOME -silent -W CASInstall.InstallType="upgrade" -W CASInstall.DBRuntimePassword="runtime_pwd" -W CASInstall.DBAdminPassword="admin_pwd" -W CASInstall.StartAfterReboot="False" -W CASInstall.StartAfterInstall="False"
- Solaris with DB2 as the database
-
setupsolarisSparc.bin -is:javahome $JAVA_HOME -silent -W CASInstall.InstallType="upgrade" -W CASInstall.DBRuntimePassword="runtime_pwd" -W CASInstall.DBAdminPassword="admin_pwd" -W CASInstall.StartAfterReboot="False" -W CASInstall.StartAfterInstall="False"
- Solaris with Oracle as the database
-
setupsolarisSparc.bin -is:javahome $JAVA_HOME -silent -W CASInstall.InstallType="upgrade" -W CASInstall.DBRuntimePassword="runtime_pwd" -W CASInstall.DBAdminPassword="admin_pwd" -W CASInstall.StartAfterReboot="False" -W CASInstall.StartAfterInstall="False" -W
CASInstall.DBProvideAdminCredentials="true" -W CASInstall.DBAdminUserID="sysdba_userID" -W CASInstall.DBRuntimeUserID="runtime_userID"
- 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.
- Copy setup.exe from fp_temp/CDS to
cds_installdir/scripts.
- Change to the cds_installdir/scripts directory, where
cds_installdir is the dynamic content delivery service
installation directory.
- Run the following command:
./setup.bin -silent -is:log /tmp/cds_upgrade.txt -V LICENSE_ACCEPT_BUTTON="true" -V CDS_DB_PASSWORD="runtime_pwd"
- runtime_pwd
- Specify the database user password that was used to install Tivoli
Intelligent Orchestrator.
- Stop WebSphere Application Server with the following command:
- Change to the $TIO_HOME/tioprofile/bin directory, where
$TIO_HOME is the Tivoli Intelligent Orchestrator installation
directory.
- Run the command:
stopServer app_server -username was_adminID -password password
- app_server
- The name of the application server. The default is
server1.
- was_adminID
- The WebSphere Application Server administrator user name. The
default is wasadmin
- password
- The WebSphere Application Server administrator password for the specified
user name.
- Change the owner of the WebSphere Application Server profile with the
following command:
chown tioadmin:tioamin $TIO_HOME/tioprofile
- Stop and restart Tivoli Intelligent Orchestrator.
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 the Web site,http://www-128.ibm.com/developerworks/forums/tivoli_forums.jsp
- Click on the Tivoli Provisioning Manager and Intelligent Orchestrator
Automation Package Development Environment link on the Web site.
The following section includes important information about this document
and its use.
This information was developed for products and services offered in the
U.S.A.
IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or service may
be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used
instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not
grant you any license to these patents. You can send license inquiries,
in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the
IBM Intellectual Property Department in your country or send inquiries, in
writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS
IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials
for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one) and
(ii) the mutual use of the information which has been exchanged, should
contact:
IBM Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada
Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.
The following terms are trademarks or registered trademarks of
International Business Machines Corporation in the United States or other
countries or both:
- IBM
- Tivoli
- The Tivoli logo
- WebSphere
- AIX
- DB2
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
UNIX is a trademark of The Open Group in the United States, other
countries, or both.
Java(TM) and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or
both.
Microsoft(R) and Windows are trademarks or registered trademarks of
Microsoft Corporation in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks
of others.