© Copyright IBM® Corporation 2008. All rights reserved. May only be used pursuant to a Tivoli® 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 fix pack only applies to a regular installation of Tivoli Provisioning Manager for Software (an installation with IBM WebSphere® Application Server as the application server). A fix pack is not available for a Fast Start installation.
Support for VMware Virtual Infrastructure 3.0 is provided with Tivoli Provisioning Manager for Software version 5.1.1.1. Tivoli Provisioning Manager for Software provides the required centralized management interface to control the VMware hardware interactions and implement an end-to-end software distribution and deployment strategy. This fix pack adds support for VMware's V-Motion technology through which Tivoli Provisioning Manager for Software can be used to initiate migration of VMware virtual machines from one host server to another.
For more information about how to use Tivoli Provisioning Manager for Software version 5.1.1.1 to manage and patch multiple virtual machines, refer to the VMware Virtual Infrastructure 3 using Tivoli Provisioning Manager document available in the IBM Open Process Automation Library at http://catalog.lotus.com/wps/portal/tpm.
Endpoints can now be configured to use the firewall components on networks that do not have user datagram protocol (UDP) broadcasting enabled. To enable this feature, a configuration file is used so that endpoints can locate the appropriate gateway service machine and associated service names for a given destination address.
To enable proxy firewall support without using UDP, you must create a file named proxy.conf in the $CA_HOME/runtime/agent/config (UNIX®) or %CA_HOME%\runtime\agent\config (Microsoft® Windows®) directory, where CA_HOME is the common agent installation directory.
The syntax of the proxy.conf file is:
targethost:targetport=proxyhost:proxyport ....
The following is a sample proxy.conf file in which the gateway service is running on a machine with the IP address 9.48.162.226, and the gateway manger is running on a machine with the IP address 9.48.162.4:
9.48.162.4:9045=9.48.162.226:9045 9.48.162.4:9046=9.48.162.226:9046 9.48.162.4:2100=9.48.162.226:2100 9.48.162.4:9511=9.48.162.226:9511 9.48.162.4:9512=9.48.162.226:9512 9.48.162.4:9513=9.48.162.226:9513 9.48.162.226:9045=9.48.162.226:9045 9.48.162.226:9046=9.48.162.226:9046 9.48.162.226:2100=9.48.162.226:2100 9.48.162.226:9511=9.48.162.226:9511 9.48.162.226:9512=9.48.162.226:9512 9.48.162.226:9513=9.48.162.226:9513
The proxy.conf file must also be copied to the $CA_HOME/runtime/agent/subagents/cds (UNIX) or %CA_HOME%\runtime\agent\subagents\cds (Windows) directory.
Tivoli Provisioning Manager for Software 5.1.1.1 provides an automation package that enables you to create, update, and delete large numbers of zones, regions, and depot servers using workflows and scripts. Before Fix Pack 3, the management of limited numbers of zones, regions, and depots was possible only through the Web interface.
The workflows and scripts provided with the DcdAdmin.tcdriver automation package refer to an .xml file that conforms with the dcdAdmin.dtd file, in which specific settings can be defined for the zones, regions, and depot servers that are used for the large-scale software distribution tasks. An extension to the automation package would include the ability to define isolated zones or exception depots, or configure depot access rules that can be used with specific attributes for the isolated zones. The elements defined in the dtd file cannot be imported through xml import; instead, workflows are provided to create, update, and delete zones, regions, and depot servers. A sample xml file, dcdAdminSample.xml, which you can customize according to your needs, is provided in the %TIO_HOME%\tools\DcdAdmin directory.
The DcdAdmin automation package provides a number of workflows and scripts.
Additional details about using the DcdAdmin automation package are available in the automation package documentation. To view the documentation:
The automation package documentation details are displayed.
Tivoli Provisioning Manager for Software 5.1.1.1 provides a new inventory report that can be run to verify which common agent version is installed on which target computer.
To perform the common agent upgrade as described in section Upgrading the common agent, you can create a dynamic group of computers that have version 1.3.2.14 of the common agent installed. To be able to create the dynamic group of computers for the upgrade, a particularization of this inventory report needs to be run, which identifies all of the target computers that have version 1.3.2.14 of the common agent installed.
To run the report that identifies the upgradable target computers:
Using this report, you can now click Manage Inventory > Groups, and then Edit > Add Group to create a dynamic group of computers that can be used for the common agent upgrade.
Sun Update Connection Enterprise is a software application that allows you to manage the complete lifecycle deployment for software in Solaris and Linux® environments. Tivoli Provisioning Manager for Software now provides integration with Sun Update Connection Enterprise, which reduces the time required to manage patches in these environments.
To use Tivoli Provisioning Manager for Software with Sun Update Connection Enterprise, you must install and configure a system dependency server in your environment.
For information on how to use Sun Update Connection Enterprise support in Tivoli Provisioning Manager for Software, refer to the documentation for Sun Update Connection Enterprise automation package, which is available from the Web interface. To access the automation package documentation:
If managing patches on Red Hat Linux computers, you can specify how long you want Tivoli Provisioning Manager for Software to wait when scanning for available patches.
To set the timeout:
If this variable is not specified, Tivoli Provisioning Manager for Software uses the value of 2400 seconds by default.
You can specify where the Common Inventory Technology software is to be installed when running a Tivoli Provisioning Manager for Software Inventory Discovery on computers that do not have the common agent installed.
To specify the installation path:
If these variables are not specified, Tivoli Provisioning Manager for Software uses the following paths by default:
Version 5.1.1.1 (Fix Pack 3) includes fixes addressed in Version 5.1.1.0 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:
Version 5.1.1.1 supports all the hardware and software that is supported by Tivoli Provisioning Manager for Software V 5.1.1.0
You must install and configure all components of Tivoli Provisioning Manager for Software version 5.1.0 plus Fix Pack 2, or Version 5.1.1.0 before attempting the installation of Fix Pack 5.1.1.1. Thoroughly review the following list of installation prerequisites before you proceed with the installation.
If Tivoli Provisioning Manager for Software is already installed, you can:
Disk space requirements for the Tivoli Provisioning Manager for Software node are as follows:
In a two-node configuration with Tivoli Directory Server as the directory server, the directory server node requires an additional 50 MB of disk space.
Ensure that you can run the workflow named no_operation. For instructions on how to run a workflow, refer to the Running workflows from the Web interface topic in the Tivoli Provisioning Manager for Software Version 5.1.1.0 information center.
To determine the Tivoli Provisioning Manager for Software version, in the Web interface, click the About link at the top right corner of the Welcome page.
db2 connect to database_name user database_user using password
where:
For example:
db2 connect to tc user tioadmin using pa55w0rd
db2 "select * from access_domain where name = 'sample:all-objects'"
<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE datacenter PUBLIC " -//Think Dynamics//DTD XML Import//EN" "xml import.dtd"> <datacenter> <access-domain name="sample:all-objects"> </access-domain> </datacenter>
%TIO_HOME%\tools\xmlimport.cmd file:path\sampleAccessDomain.xml
For each automation package that you have removed, ensure that the data model objects that were created by the automation package are also removed. For example, if you removed an automation package for a piece of software, any software catalog entries created by the automation package must also be removed. Information about the objects created by an automation package is in the xml subfolder of the automation package.
Alternatively, you can reinstall all provided automation packages that you removed before you begin the fix pack installation.
cancel-all-in-progress.cmd clean-up-deployment-requests.cmd
The command marks all the in-progress deployment requests as abandoned (failed). The log files cancel-all-in-progress.log and clean-up-deployment-requests.log are created with the results of the commands.
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:
After the fix pack installation, you can add the workflow back into Tivoli Provisioning Manager for Software 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.
Table 1. Tivoli Provisioning Manager for Software downloads
| Downloads available from the fix pack Web page. | ||
| Operating System | Tivoli Provisioning Manager for Software | Components |
|---|---|---|
| Windows
Upgrading from 5.1.0.2 |
5.1.0.2-TIV-TPMFSW-Win32-FP0003.zip |
5.1.0.2-TIV-Components-Win32-FP0003.zip, which includes: - CAS\AM_V13_WIN.zip - CDS\Win32\setup.exe - DMS\DMS_patch.zip - DMS\ProductUpdateInstaller61.zip |
| Windows
Upgrading from 5.1.1 |
5.1.1-TIV-TPMFSW-Win32-FP0001.zip |
5.1.1-TIV-Components-Win32-FP0001.zip, which includes: - CDS\Win32\setup.exe |
md5sum -c filename.md5
where filename.md5 is the name of the file that contains the md5 sum and the name of the filename.zip file. The md5 file must include only the .zip file name and not its full path.
The command calculates the md5 sum for the filename.zip file, automatically compares it with the value listed in the .md5 file, and returns OK if the values are the same. For this to work, the .zip and .md5 files should be in the same directory when the md5sum check is run.
For example, to validate the file 5.1.0.2-TIV-TPMFSW-Win32-FP0003.zip, run the command:
md5sum -c 5.1.0.2-TIV-TPMFSW-Win32-FP0003.md5
ibmdirctl -D cn=root -w password status
To verify the status of the DB2 Universal Database:
This readme file uses the following variables to represent directory
paths.
| Path variables | Definition | Default directory |
|---|---|---|
| AM_installdir | Installation directory for the agent manager | C:\Program Files\IBM\AgentManager |
| %DMS_HOME% | Installation directory for the device manager service | C:\Program Files\IBM\tivoli\tpm\DeviceManager |
| DB2_installdir | Installation directory for DB2 Universal Database |
C:\Program Files\IBM\SQLLIB |
| IDS_installdir | Installation directory for Tivoli Directory Server |
C:\Program Files\IBM\ldap |
| %WAS_HOME% | Installation directory for WebSphere Application Server |
C:\Program Files\IBM\WebSphere\AppServer |
| %TIO_HOME% | Installation directory for Tivoli Provisioning Manager for Software |
C:\Program Files\ibm\tivoli\tpmfsw |
| %TIO_LOGS% | Log file directory for Tivoli Provisioning Manager for Software |
C:\Program Files\ibm\tivoli\common\COP\logs |
winUpgrade.bat -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID -DBAdminPWD db_admin_pwdwhere
The first time that you start the product after installing the fix pack, the automation package migration process runs and updates the automation packages provided with Tivoli Provisioning Manager for Software:
The following main steps occur during the installation of the fix pack:
To recover from an installation error:
C:\Program Files\IBM\tivoli\common\ctgde\logs
%DMS_HOME%\log
%TIO_LOGS%\tcdrivermanager.log
%TIO_LOGS%\deploymentengine\console.log
After you have completed installation of the fix pack, you must upgrade older versions of the common agent. The common agent upgrade is from version 1.3.2.14, provided with Tivoli Provisioning Manager for Software 5.1.0.2 (Fix Pack 2), to version 1.3.2.25, provided with Tivoli Provisioning Manager for Software 5.1.1.0. The common agent must be upgraded on both the depot servers and the endpoints that are participating in the software distribution process.
In Fix Pack 3, the agent upgrade uses both the deployment engine for control of the upgrade process on the common agent, and the depots for scalable distribution of the package. The upgrade through the standalone installation of the common agent, which was provided with Tivoli Provisioning Manager for Software 5.1.0.2 (Fix Pack 2), is still available to use.
Refer to the information center for additional details about upgrading the common agent:
Subagents delivered with Tivoli Provisioning Manager for Software 5.1.0.2 also require an upgrade. With the installation of this upgrade, the new version of the Tivoli Provisioning Manager for Software server is backward compatible with agents running at the 5.1.0.2 level with all the 5.1.0.2 level subagents.
Table 3. Scalable distribution infrastructure components
| Component name | Component version |
|---|---|
| Tivoli Common Agent Services | 1.3.2.25 |
| Common Inventory Technology (CIT) | 2.4.1009 |
| Dynamic Content Delivery Client | 1.3.2100 |
| Dynamic Content Delivery Depot | 1.3.2100 |
| Dynamic Content Delivery Axis Export | 1.3.2100 |
| Tivoli Provisioning Manager OMA/DM OSGi Agent Extension | 1.8.1 |
| IBM Tivoli Provisioning Manager Job Execution Service | 5.1.1000 |
| Event Administration Service | 5.1.1000 |
| IBM Tivoli Intelligent Orchestrator CIT Scanner | 5.1.3 |
| SPBHandler | 5.1.1000 |
| IBM Tivoli Provisioning Manager Subagent | 5.1.1000 |
Table 4. Software modules and installables
| Software module | Software installable | Installable file name |
|---|---|---|
| TCA Subagents Upgrade | TCA-Subagents Windows Upgrade Installable | upgrade_subagents_511_windows.exe (self-extracting) |
| TCA Subagents Upgrade | TCA-Subagents Linux Intel® Upgrade Installable | upgrade_subagents_511_linux86.tar (tar file format) |
|
| TCA-Subagents Linux s390 Upgrade Installable | upgrade_subagents_511_linux_s390.tar (tar file format) |
|
| TCA-Subagents Linux PPC Upgrade Installable | upgrade_subagents_511_linux_ppc.tar (tar file format) |
|
| TCA-Subagents AIX® Upgrade Installable | upgrade_subagents_511_aix.tar (tar file format) |
|
| TCA-Subagents Solaris Intel Upgrade Installable | upgrade_subagents_511_solaris_ix86.tar (tar file) |
|
| TCA-Subagents Solaris Sparc Upgrade Installable | upgrade_subagents_511_solaris.tar (tar file format) |
|
| TCA-Subagents HP-UX PA RISC Upgrade Installable | upgrade_subagents_511_hp.tar (tar file format) |
|
| TCA-Subagents HP-UX Itanium® Upgrade Installable | upgrade_subagents_511_hp_ia64.tar (tar file format) |
| TCA-Subagents Generic Upgrade | TCA Generic Subagents Upgrade for Windows Installable | upgrade_subagents_511.exe (self-extracting) |
| TCA-Subagents Generic Upgrade | TCA-Subagents Generic Upgrade Installable | upgrade_subagents_511.tar (tar file format) |
| TCA-1.3.2.25 Upgrade | TCA-1.3.2.25 Upgrade Installable | upgrade.jar |
A single implementation of the SoftwareInstallable.Distribute logical device operation is assigned to each selected installable. To distribute all of the required packages, you simply select to distribute the required upgrade software package, and all the other packages are distributed automatically to the target systems.
The task is run against the specified target computers. Once the task is completed successfully, the common agents on all the selected target computers are upgraded to the 1.3.2.25 version.
If you have Tivoli Provisioning Manager for OS Deployment Embedded Edition installed, note that the version of Tivoli Provisioning Manager for OS Deployment Embedded Edition provided with Tivoli Provisioning Manager version 5.1.1.1 (Fix Pack 3) has been updated since Tivoli Provisioning Manager version 5.1.0.0. This updated version is the same as the one provided with Tivoli Provisioning Manager for Software version 5.1.0.1 (Fix Pack 1) and version 5.1.0.2 (Fix Pack 2).
If you upgraded from Tivoli Provisioning Manager for Software version 5.1.1.0 or if you already upgraded Tivoli Provisioning Manager for OS Deployment Embedded Edition in Tivoli Provisioning Manager for Software Fix Pack 1 or Fix Pack 2, no action is required.
If you did not upgrade Tivoli Provisioning Manager for OS Deployment Embedded Edition in Fix Pack 2, you can upgrade it following the procedure below. All of your existing operating system images are preserved during the upgrade.
To upgrade Tivoli Provisioning Manager for OS Deployment Embedded Edition to the latest version:
An existing Tivoli Provisioning Manager for Software computer that has been upgraded with the fix pack might have an updated architecture bus parameter for the operating system software configuration template. The default is value is 32-bit.
If the upgraded computer is a 64-bit computer, run the Windows Configuration Discovery again to populate the correct parameter value.
The Windows Configuration Discovery will discover the attributes of the computer.
To verify that the correct architecture bus parameter value was populated, perform the following steps:
The rollback feature, which allows you to bring a system back to a previous state, was introduced in Tivoli Provisioning Manager for Software version 5.1.1.0. For more information about this feature, refer to the Rollback topic in the Tivoli Provisioning Manager for Software version 5.1.1.0 information center.
If you have upgraded from version 5.1.1.0 and you want to keep the same behavior as version 5.1.1.0 (rollback enabled or disabled), no action is required.
If you have upgraded from version 5.1.0.2, the rollback feature is not enabled by default. To enable the rollback feature:
You have now enabled the rollback feature.
Additional Web Replay scenarios are available for you to use in Tivoli Provisioning Manager for Software. To download these Web Replay scenarios, go to the IBM Open Process Automation Library at http://catalog.lotus.com/tpm?NavCode=1TW10105F.
After downloading the packages, refer to the Web Replay online help for instructions on how to import and use the Web Replay scenarios in your environment. The Web Replay online help is available from the Tivoli Provisioning Manager for Software Web interface.
Note that the default value for the Sun.patchpro.patch.source global variable, which specifies the URL for the Sun patch server, has now changed to https://getupdates1.sun.com.
If you are applying Fix Pack 3 to a Tivoli Provisioning Manager for Software Version 5.1.1.0 installation, no action is required.
If you are applying Fix Pack 3 to a Tivoli Provisioning Manager for Software Version 5.1.0.2 installation, and if you want to use the new value for this variable, perform the following steps on the Web interface after applying Fix Pack 3:
Tivoli Provisioning Manager for Software will now use the new value for the Sun.patchpro.patch.source global variable to manage patches.
During the database schema migration, some property names and values change for the KANAHA component. If you are using these specific properties in your custom workflows, ensure that you migrate your workflows because the property names and values will be changed in the Tivoli Provisioning Manager for Software data model.
The following properties have changed:
|
| Version 5.1.0.2 only (no change from Version 5.1.1) | Version 5.1.1.1 |
|---|---|---|
| Name | memory.size | memory.size |
| Unit | Kilobytes | Bytes |
|
| Version 5.1.0.2 and Version 5.1.1 | Version 5.1.1.1 |
|---|---|---|
| Name | memoryModule.moduleSizeMB | memoryModule.moduleSize |
| Unit | Megabytes | Bytes |
|
| Version 5.1.0.2 and Version 5.1.1 | Version 5.1.1.1 |
|---|---|---|
| Name | memoryModule.maxModuleSizeMB | memoryModule.maxModuleSize |
| Unit | Megabytes | Bytes |
A new discovery configuration, called Patch Management Discovery For All Operating Systems, is now available. This generic discovery configuration calls the corresponding patch scan method based on the operating system on the endpoints.
If you are applying Fix Pack 3 to a Tivoli Provisioning Manager for Software Version 5.1.1.0 installation, no action is required.
If you are applying Fix Pack 3 to a Tivoli Provisioning Manager for Software Version 5.1.0.2 installation, and if you enabled access control for patch management in Fix Pack 2, you must set up access control for this new discovery configuration by following these steps:
Either if you are applying the fix pack to a Tivoli Provisioning Manager for Software Version 5.1.0.2 installation or a Tivoli Provisioning Manager for Software Version 5.1.1.0 installation, refer to the following sources of documentation:
The following updates apply to the information center.
Useful commands
This topic, which is available in the information center at Troubleshooting and support -> Known limitations -> Common agent troubleshooting -> Useful commands, needs to be corrected with the following information:
Uninstalling the common agent and subagents
uninstall.exe -silent -W CASInstall.forceUninstall=true
./uninstall -console
List the bundles and their state
agent cli deployer list bundles state
Retrieve all of the common agent logs
service.bat
service.sh
The CASservice.zip file will be created in the runtime/agent directory.
Requirements for common agent installation
This topic, which is available in the information center at Installing, configuring, and security -> Configuring the environment -> Distribution in branch offices -> Tivoli Common Agent Services -> Installing the common agent and subagents on the managed system -> Requirements, needs to be updated with the following information:
On HP-UX, adding the .hushlogin does not prevent the message of the day from interfering with the common agent upgrade. Instead, you need to perform the following operations:
Device manager service configuration
This topic, which is available in the information center at Troubleshooting and support -> Known limitations -> Device manager service -> Device manager service configuration, needs to be corrected with the following information:
To change the polling interval for WebSphere Application Server:
Security role mapping for the Discovery tabs
This topic, which is available in the information center at Security -> User security -> Users and security roles -> Adding users -> Security role mappings, needs to be updated with the following information:
The Initial Discovery page in the Web user interface navigation requires the Task-Edit security permission in order to perform actions on that page. The Task-Edit permission is assigned to the following predefined security roles:
Manually configuring read-only LDAP
This topic, which is available in the Tivoli Provisioning Manager for Software Version 5.1.0.2 information center at Security -> Certificate authentication -> Read-only LDAP, needs to be updated.
The following security roles names also need to be changed in the
ibm-application-bnd.xmi file:
| Previous Security Role Names | New Security Role Names |
|---|---|
| cn=InternalNetworkView,dc=ibm,dc=com | NetworkView |
| cn=InternalNetworkEdit,dc=ibm,dc=com | NetworkEdit |
| cn=InternalApplicationsAdminView,dc=ibm,dc=com | ApplicationsAdminView |
| cn=InternalApplicationsAdminEdit,dc=ibm,dc=com | ApplicationsAdminEdit |
| cn=InternalCustomerView,dc=ibm,dc=com | CustomerView |
| cn=InternalCustomerEdit,dc=ibm,dc=com | CustomerEdit |
| cn=InternalStorageView,dc=ibm,dc=com | StorageView |
| cn=InternalStorageEdit,dc=ibm,dc=com | StorageEdit |
| cn=InternalStorageTemplateView,dc=ibm,dc=com | StorageTemplateView |
| cn=InternalStorageTemplateEdit,dc=ibm,dc=com | StorageTemplateEdit |
| cn=InternalServiceCatalogView,dc=ibm,dc=com | ServiceCatalogView |
| cn=InternalServiceCatalogEdit,dc=ibm,dc=com | ServiceCatalogEdit |
| cn=InternalSubscriptionView,dc=ibm,dc=com | SubscriptionView |
| cn=InternalSubscriptionEdit,dc=ibm,dc=com | SubscriptionEdit |
| cn=InternalDistributedApplicationsManage,dc=ibm,dc=com | DistributedApplicationsManage |
For information about administering read-only LDAP servers, refer to the applicable product documentation:
SOAP services fail to start on Linux
This topic, which is available in the information center at Troubleshooting and Support -> Known limitations -> Installation problems, needs to be corrected with the information:
To resolve the problem when the SOAP services do not start automatically after the Tivoli Provisioning Manager for Software installation, 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
Perform the following steps to start the SOAP services:
-Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar \
to
-Xbootclasspath/a:$TIO_HOME/lib/jaasmodule.jar:$TIO_HOME/eclipse/plugins/com.ibm.pvcws.osgi/com.ibm.pvcws.osgi.props.jar \
Change
-noSplash -application launcher.CliLauncher \
to
-noSplash -clean -application launcher.CliLauncher \
At time of publication, the following problems and limitations were known.
As limitations and problems are discovered and resolved, the IBM Support team updates the online knowledge base. You can search the online support knowledge base to quickly find workarounds or solutions to problems that you experience.
During the upgrade from Tivoli Provisioning Manager for Software Fix Pack 2 to Fix Pack 3, the installation fails during the first step of the installation, the LDAP migration.
If this is a temporary problem, for example, if the LDAP connection is lost, resolve the problem and then follow the steps below to resume the installation.
Check the log files to see where the installation failed.
If the installation failed before or during Step 6, Enable global security, run the installer again, it will repeat the previous steps.
If the installation failed after Step 6, complete the following steps to manually configure this part of the Fix Pack installation:
$WAS_PROFILE_HOME/bin/stopServer.sh $TIO_SERVER -username <username> -password <password>
where <username> and <password> are your WebSphere Application Server username and password.
Error messages similar to the following are generated in the MC-DB-install.out file:
22.01.2008 20:00:36 EET com.ibm.tivoli.cds.install.database.DatabaseInstaller parseFile SQL statement --> DROP TABLE <table_name> 22.01.2008 20:00:36 EET com.ibm.tivoli.cds.install.database.DatabaseInstaller parseFile java.sql.SQLException: ORA-00942: table or view does not exist java.sql.SQLException: ORA-00942: table or view does not exist at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) [...]
During the common agent upgrade after the installation of the fix pack, the dynamic content delivery service checks to ensure that all database entities are created. Under some custom installations, a table was created but never used. In the current release, these tables have been added permanently with a new column definition. To ensure proper installation, the dynamic content delivery service attempts to delete the old table with the old format. In many cases, that table does not exist, therefore these error messages are generated.
You can ignore these error messages.
Error messages similar to the following are generated in the MC-DB-install.out file:
2/4/08 11:11:43 AM CST com.ibm.tivoli.cds.install.database.DatabaseInstaller parseFile SQL statement --> ALTER TABLE CDSSCHEMA.DEPOT_SERVER DROP COLUMN LOCAL_BW_KBPS 2/4/08 11:11:43 AM CST com.ibm.tivoli.cds.install.database.DatabaseInstaller parseFile COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL0104N An unexpected token "COLUMN" was found following "MA.DEPOT_SERVER DROP". Expected tokens may include: "CONSTRAINT". SQLSTATE=42601
During the upgrade of the dynamic content delivery management center, after the installation of the fix pack, the dynamic content delivery service checks to ensure that all database entities are created. Under some custom installations with older versions of DB2 Universal Database, the drop column syntax is not supported. This is a cleanup step and does not affect the stability of the overall system. In the future, you might run another version of DB2 Universal Database that supports this syntax and these steps will complete the cleanup.
You can ignore these error messages.
During the standalone installation of common agent version 1.3.2.25 in Fix Pack 3, an error is encountered when copying the binary files from a Linux Tivoli Provisioning Manager for Software server to a Windows computer using the SCP protocol. The common agent installation fails with the following error in the install.log:
Error getting service name: Error Number: 76 Path not found
Copy the binaries to a new location on the Windows computer, where the permissions are restored.
During the upgrade to Fix Pack 3, the dynamic content delivery installation on AIX might fail with the following error:
... Installing Content Delivery Service Upgrade, please wait... Error while installing Content Delivery Service Upgrade. See logs in /opt/ibm/tivoli/common/ctgde/logs for details.
The connections resume as soon as the Fix Pack 3 upgrade is done, and Tivoli Provisioning Manager for Software and the WebSphere Application Server are restarted.
Before upgrading the agents to the Fix Pack 3 level, if you choose to distribute the TCA-1.3.2.25 Upgrade Installable software definition prior to the upgrade, the distribution might fail with the following error:
COPTCA017E: tcaExecuteCommandSubagent Error executing command on endpoint: java.rmi.MarshalException: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the element content of the document.
Consider one of the following solutions:
During the Fix Pack 3 installation, the data migration might fail to populate the data model with custom software signatures, returning the following error:
ERROR The system failed to import software signatures. + '[' 1 -ne 0 ']' + printf '\nERROR: Failed to populate data center model with custom software signatures, exiting.\n' ERROR: Failed to populate data center model with custom software signatures, exiting. + exit 1
Back up your database before the Fix Pack 3 installation. If this problem is encountered, restore the database and run the fix pack installation again, which will resume at the data migration step.
The installation of the fix pack fails at the Packaging TCA upgrade... step, and the following error is displayed:
Error: Not enough free space for creating the image
1 file(s) moved.
ERROR: Failed to package TCA upgrade, exiting.
One of the scripts provided with the fix pack is incorrectly reporting the amount of disk space in the %TIO_HOME% directory.
Follow these steps:
set IMAGE_SIZE=100000
and replace with
set IMAGE_SIZE=100
IF not "%errorlevel%" == "0"
and replace with
IF not "%errorlevel%" == "1"
This problem applies to installations of Tivoli Provisioning Manager for Software Version 5.1.0 and Version 5.1.1.
DB2 installation stops before it is complete. On the computer where you are performing the installation, the configured node name is different than the configured host name.
The DB2 installation uses the uname -n command to obtain the node name of the computer. Typically, the node name is the same as the host name that is returned with the hostname command. Tivoli Provisioning Manager for Software installation requires that the host name and the node name of the computer are identical.
Check the value of the host name and node name. You must change the node name if it does not match the host name.
uname -S myserver
If managing patches on Windows computers, you might get the following error during the patch scanning operation:
ESR: <task name> > task failure. Cannot download new security updates. . Error message: COPDEX123E The workflow threw a ParsingFailure exception. The message is A Parsing Failure has occurred. xmlSource is located: <repository path>/wua/wsusscancab/update/package.xml. See attached for error details and workflow log.
The Microsoft Updates Discovery task fails when scanning the wsusscn2.cab file to retrieve the patches into the data model. This problem is caused by a change in the patches format in the .cab file.
If applying the fix pack to a Tivoli Provisioning Manager for Software Version 5.1.0.2 installation:
If applying the fix pack to a Tivoli Provisioning Manager for Software Version 5.1.1.0 installation:
For more information, refer to Microsoft Updates Discovery fails due to XML parse exception.
If you replicate an endpoint task from a Tivoli Configuration Manager environment, and submit the replicated endpoint task to target computers that have Tivoli Management Agent installed and also target computers that have Tivoli Common Agent installed, the endpoint task submission works on the Tivoli Management Agent computers, but it fails on the Tivoli Common Agent computers. The problem occurs only in an environment with mixed target computers, where Tivoli Management Agent and Tivoli Common Agent are installed, and only in the first 30 minutes after performing the replication. After 30 minutes, the problem does no longer occur.
On such environments, for computers that have Tivoli Common Agent installed, submit the replicated endpoint task at least 30 minutes after replicating the endpoint task.
You are managing patches in the AIX environment. When specifying the updates to scan for, you select Latest Level for the Maintenance Strategy Model field, to scan for both technology levels and service packs.
After following the steps in the information center to generate the patch recommendations, two recommendations are displayed for your endpoints:
If approving the recommendation to install only the technology level on the endpoint, both the technology level and the latest service pack for that technology level are installed on the endpoint.
If your computer has its own Operating Systems Patches and Updates compliance check, and it has also inherited one from a group it is a member of, then the same patch recommendations for it will be generated twice. If, for example, your computer has 20 patch recommendations due to the Operating Systems Patches and Updates compliance check being run, these issues will be actually be listed twice in the Recommendations tab (once for each check, and a total of 40 Patches issues will be listed in the General tab for the computer. If, however, you access, the Issues and Recommendations tab for a specific check, the patch recommendations will only be listed once.
You can either ignore the duplicate recommendations, or remove one of the Operating Systems Patches and Updates compliance checks and run the check again.
In Microsoft Internet Explorer, when creating a scenario with many steps, it takes a long time for Web replay to respond.
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 focused on installing, configuring and using the Automation Package Development Environment (APDE) for writing workflows and creating automation packages for the Tivoli Provisioning Manager for Software products.
To access the forum:
The following section includes important information about this document and its use.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not
grant you any license to these patents. You can send license inquiries,
in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the
IBM Intellectual Property Department in your country or send inquiries, in
writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one) and
(ii) the mutual use of the information which has been exchanged, should
contact:
IBM Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
AIX, DB2, DB2 Universal Database, IBM, the IBM logo, Tivoli, the Tivoli logo, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel and Itanium 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.