© Copyright IBM® Corporation 2010. 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). Tivoli Provisioning Manager for Software must be at version 5.1.1.2. A fix pack is not available for a Fast Start installation.
The enhancements and changes included in this fix pack are:
Tivoli Provisioning Manager for Software version 5.1.1.x has a more rigorous security standard than prior releases. As part of this standard, file permissions are more restrictive, for example a umask 022 enforcement with revocation of group write privileges has been implemented. This fix pack includes changes to enforce this higher level of security as part of the fix pack upgrade process. An option is available in the fix pack installer to bypass these steps and perform them at a later time.
Before starting with the installation of Tivoli Provisioning Manager for Software version 5.1.1.3, ensure that you set the umask value with 022 for the root profile. If this umask value is not set, the installation process does not complete successfully and displays an error message.
To fix the permissions of the already existing resources in your environment you can:
In both cases, a file containing the list of the resources needed to be fixed is generated automatically. This file is used each time you run the stand-alone script for fixing the resource permissions.
The file with the resource list is created by scanning the following directories on the Tivoli Provisioning Manager for Software server:
With this fix pack also a recovery script, named UndoFixWritePermissions.sh, is provided to be used for recovering the permission changes done to the resources, if necessary.
Both StandaloneFixWritePermissions.sh and UndoFixWritePermissions.sh scripts are located inside the fix pack image. After unpacking the files, the scripts are stored under the following directory:
unpack_root_directory/installer/utils
Running these scripts without any parameters will print out the usage information.
In environments where IBM Tivoli Application Dependency Discovery Manager (TADDM) is used as the primary tool for discovering IT assets and their configuration, Tivoli Provisioning Manager for Software provides a discovery configuration named Change And Configuration Management Database Discovery to extract data from Tivoli Application Dependency Discovery Manager and import it into Tivoli Provisioning Manager for Software. With Tivoli Provisioning Manager for Software version 5.1.1.2 or earlier versions, this integration was supported for Tivoli Application Dependency Discovery Manager version 7.1. For details about the Change and Configuration Management Database discovery, see the following Tivoli Provisioning Manager version 5.1.1 information center topic:
With this fix pack, the Tivoli Application Dependency Discovery Manager integration has been extended to support Tivoli Application Dependency Discovery Manager 7.1.2 or later versions. The Tivoli Application Dependency Discovery Manager Discovery is performed by running the discovery configuration named TADDM Discovery Using Rest. This discovery configuration uses the REST (Representational State Transfer) protocol, and does not require JAR files being copied from the Tivoli Application Dependency Discovery Manager server to the Tivoli Provisioning Manager for Software server. To run the discovery, see the following Tivoli Provisioning Manager version 5.1.1 information center topic:
You can now cancel a software distribution to all target computers, while the software package is already being distributed to the target computers. The feature provided is based on the four possible states that a target computer might have during the deployment of a software distribution.
| Current® state of your target computer | If you cancel the software distribution |
|---|---|
| Computer has not started downloading the job | Job is canceled with no effect on the computer |
| Computer has started downloading the job | Job is canceled with no effect on the computer |
| Computer has started processing the job | Job is canceled if the actual installation phase has not already started |
| Computer has terminated processing the job | Computer is rolled back to its previous state |
To cancel a software distribution, perform the following steps:
To enable this feature, ensure that the following new configuration parameter is set to true:
SDI.Cancel.Through
To set the new configuration parameter to true, perform these steps:
This feature is disabled by default. If you want to disable the feature later, ensure that you set the parameter to any value different from true.
Most Windows software signatures have been modified to correctly discover the 32-bit Windows systems against the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\.
According to the changes performed by Microsoft® on the wow64 emulator of the 64-bit Windows systems, it is now possible to discriminate between Windows 32-bit and Windows 64-bit scanned systems.
The signature definition for the following operating systems has been modified accordingly:
A post-installation step is required for the change to become effective because the XML files are installed by this fix pack, but not imported. Move to the %TIO_HOME%\tools directory and run the following command:
importSoftwareSignature.cmdá "C:\Programá Files\ibm\tivoli\tpm\xml\ samplebook\IBM-software-custom-signature.xml" true
You can now install a Tivoli common agent (TCA) locally on the target computer, as a standalone installation, with the required configuration to automatically discover the computer right after the agent installation. In this way, you can discover the agent in a quicker way without running the IBM Tivoli Common Agent Discovery from the Web interface.
This mechanism can only be used to run an initial discovery of an agent and does not keep track of its status changes.
To enable this feature, the following new configuration parameter must be set to true:
EnableAgentDiscovery
The default value is set to false.
You can enable the feature in two different ways:
After having installed the standalone Tivoli common agent you can still trigger manually the quicker discovery from the target computer by running the following command from the agent directory:
A software package block bundles all the resources, which are necessary to perform the actions contained in a software package, into a standard zipped format. When the software package block is distributed to a target computer, it is not stored on the target computer, but is unzipped in the target directory. The maximum size of a software package block is now 4 GB.
Tivoli Provisioning Manager for Software 5.1.1.3 embeds Common Inventory Technology (CIT) 2.6 which supports also Windows 2008. The CIT version is upgraded by running an agentless CIT scan on a target computer without Tivoli common agent installed, or upgrading the subagent on the target computer with Tivoli common agent installed. In both cases CIT is upgraded to version 2.6.
You can now define a compliance check caching value to the compliance group based on your business needs. For example, if the patch scan you perform is regularly running once every month, you can specify a caching value of one month for the patch compliance group. Log on to the Web Interface as TPM administrator, select the compliance group that you intend to modify, and on the Variables tab of the compliance group, you can add a new variable by performing the following steps:
When a scheduled compliance scan and check is triggered, after the scan is complete, the compliance check will be run only on those computers in the group where the time between the last compliance check and the current time exceeds the compliance check caching value that you have defined for the group. Therefore a new computer, which is added to the group, will be checked, while existing computers of the group might or might not be checked depending on the compliance check caching value.
The SPBHandler subagent has been disabled to write, to the RCA log and trace files, sensitive information transmitted to the subagent using the SRT parameters.
During the TADDM discovery, Tivoli Provisioning Manager for Software tries to detect all the Weblogic server parameters that are described in this section. One or more parameters might be unavailable at run time, for example when Tivoli Application Dependency Discovery Manager (TADDM) was previously unable to discover the parameters from the target computers. In this case, these parameters are not replicated into Tivoli Provisioning Manager for Software.
For the Weblogic server, the following attributes are now discovered:
Weblogic platform installation object
resource-name Vendor Guid deviceModelId
Weblogic server and administration server object
resource-name deviceModelId Guid RootDirectory ServerName IsAdminServer DomainName ConfigFileName ConfigFileURI CompleteHTTPMessageTimeout CompleteIIOPMessageTimeout CompleteT3MessageTimeout DefaultProtocol DefaultSecureProtocol DefaultTGIOPUser HelpPageURL IdleIIOPConnectionTimeout JavaCompiler: CmdLine JDBCLogFileName ListenThreadStartDelaySecs LoginTimeout LoginTimeoutMillis MaxHTTPMessageSize MaxIIOPMessageSize MaxT3MessageSize ServerStatus StdoutSeverityLevel TunnelingClientPingSecs ThreadPoolPercentSocketReaders TunnelingClientTimeoutSecs MaxIIOPMessageSize MaxT3MessageSize ZACPublishRoot HTTPDEnabled IIOPEnabled InstrumentStackTraceEnabled JDBCLoggingEnabled JMSDefaultConnectionFactoriesEnabled LogRemoteExceptionsEnabled NativeIOEnabled ReverseDNSAllowed SSL.KeyEncrypted SSL.SslPort SSL.SslEnabled SSL.TwoWaySslEnabled SSL.ServerCertificateChainFileName StdoutDebugEnabled StdoutEnabled TGIOPEnabled TunnelingEnabled ZACEnabled Process.CmdLine Process.CWD Process.Decrement Process.Env Process.DisplayName Process.Increment Process.InitialSize Process.MaxSize Process.MinSize Process.Size Process.WindowsServiceList
Weblogic Server J2EE deployed application software configuration data
resource-name J2EEAPPURI Guid
JDBC connection pool configuration data
resource-name URL MaxCapacity InitialCapacity JDBCDriverName JDBCCapacityIncrement PreparedStatementCacheSize RefreshMinutes SupportsLocalTransaction TestConnectionsOnReserve TestTableName TestConnectionsOnRelease ShrinkingEnabled ShrinkPeriodMinutes LoginDelaySeconds SupportsLocalTransaction JNDIName Guid JDBCConnectionURL JDBCConnectionMaxCapacity JDBCConnectionInitialCapacity
JDBC data source configuration data
databasePort connectionPool jndiName dbType databaseName oracleDBHost resource-name StreamChunkSize RowPrefetchEnabled RowPrefetchSize TwoPhaseCommitEnabled
JMS configuration data
resource-name JNDIName Destinations BytesMaximum BytesPagingEnabled BytesThresholdHigh BytesThresholdLow MessageMaximum MessagesPagingEnabled MessagesThresholdHigh PagingStore Store.DisplayName Guid
Version 5.1.1.3 (Fix Pack 3) includes fixes addressed in version 5.1.1.2 and customer Authorized Program Analysis Reports (APARs) from previous interim fixes.
There is no refresh installation included as part of this fix pack. Only an existing version 5.1.1.2 on any interim fix level can be upgraded to version 5.1.1.3. Migration from version 5.1 and version 5.1.1 to version 5.1.1.3 is not supported.
You must install and configure all components of Tivoli Provisioning Manager for Software version 5.1.1.2 before attempting the installation of Tivoli Provisioning Manager for Software 5.1.1.3. Thoroughly review the following list of installation prerequisites before you proceed with the installation.
If Tivoli Provisioning Manager for Software is already installed, you upgrade from version 5.1.1.2 to 5.1.1.3.
The fix pack can be applied to an existing regular installation of Tivoli Provisioning Manager for Software. 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.
Disk space requirements for the Tivoli Provisioning Manager for Software node are as follows:
| Location | Disk space requirements |
|---|---|
| Disk space for installation images | 2 GB |
| Disk space to extract files from installation images | 2.5 GB |
| Disk space for fix pack installation | 3.5 GB |
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 about 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 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.
Verify that the sample:all-objects access domain exists. If you removed this access domain after installing Tivoli Provisioning Manager for Software, you must re-create it before installing the fix pack.
db2 connect to database_name user database_user using passwordwhere:
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/xmlimport.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 default_automation_package automation package can cause problems during the fix pack installation and is therefore deleted during the installation. If you want to save a workflow that you created in the Web interface, perform the following steps:
Click Automation > Workflows
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.
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 must be in the same directory when the md5sum check is run.
For example, to validate the file 5.1.1.3-TIV-TPMFSW-Win32-FP0003.zip, run the command:
md5sum -c 5.1.1.3-TIV-TPMFSW-Win32-FP0003.md5
To verify the IBM Tivoli Directory Server on Windows:
To verify the status of the DB2 Universal Database, log in as Administrator on the DB2 Universal Database server.
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_pwd -TEMPDIR tempdirwhere:
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 successfully completed the installation of the fix pack on the Tivoli Provisioning Manager for Software server, you must upgrade older versions of the common agent on the target computers.
If you have depot servers defined in your environment, ensure that you follow this order when upgrading the common agents:
Tivoli Provisioning Manager for Software 5.1.1.3 supports upgrade paths from the following common agent levels:
You can upgrade the common agent from version 1.3.2.25 or version 1.3.2.29 to version 1.3.2.30 (Tivoli Provisioning Manager for Software 5.1.1.3) in one of the following ways:
The steps to upgrade the common agents using the Software Distribution Infrastructure (SDI) are:
| Name | Version | Installation Files |
|---|---|---|
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 AIX Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 HP-UX on Itanium® Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 HP-UX Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 Linux390 Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 Linux86 Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 LinuxPPC Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 Solaris Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 Solaris x86 Upgrade Installable |
| TCA-1.3.2.30 Upgrade | 1.3.2.30 | TCA-1.3.2.30 Windows Upgrade Installable |
The steps to upgrade the common agents using the deployment engine (DE) are:
If the Software Upgrade page does not load, perform the following steps:
The common agents installed from a Tivoli Provisioning Manager for Software server version 5.1.1.2 IF00002 or later are already at version 1.3.2.30. However, they must upgrade the subagents to reach version 1.3.2.30 at 5.1.1.3 level. Follows these steps to upgrade the required subagents for each target computer:
You can run the workflow as a Favorite Task for multiple computers or a group.
The following table lists the versions of the agent components installed with Tivoli Provisioning Manager for Software 5.1.1.3 common agent version 1.3.2.30:
| Component name | Component version |
|---|---|
| TCA-1.3.2.30 | 1.3.2.30 |
| TCA-Subagent CDS Axis | 1.3.2102 |
| TCA-Subagent CDS Client URL Handler | 1.3.2102 |
| TCA-Subagent CIT Scanner | 5.1.5 |
| TCA-Subagent Common Inventory Technology | 2.6.0.13 |
| TCA-Subagent DMS OSGi Client | 1.8.2 |
| TCA-Subagent DMS OSGi Client Extension for TPM | 1.8.2 |
| TCA-Subagent DMS OSGi Client Http Adaptor | 1.0.0 |
| TCA-Subagent DMS OSGi Client Https Adaptor | 1.0.0 |
| TCA-Subagent Event Administration | 5.1.1000 |
| TCA-Subagent JES | 5.1.3000 |
| TCA-Subagent SCM | 5.1.3 |
| TCA-Subagent SPBHandler | 5.1.1000 |
| TCA-Subagent SyncML Core | 2.5.0 |
| TCA-Subagent SyncML DM | 2.5.0 |
| TCA-Subagent Tivoli Provisioning Manager | 5.1.3000 |
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 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:
If you are applying the fix pack to a Tivoli Provisioning Manager for Software version 5.1.1.2 installation, refer to the following sources of documentation:
The following updates apply to the Installation Guides for Version 5.1.1.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Preinstallation Step 5: Set up required users which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for AIX → Preinstallation checklist for AIX → Preinstallation Step 5: Set up required users
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Preinstallation Step 5: Set up required users which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Linux on Intel → Preinstallation checklist for Linux on Intel → Preinstallation Step 5: Set up required users
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Preinstallation Step 5: Set up required users which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Solaris → Preinstallation checklist for Solaris → Preinstallation Step 5: Set up required users
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Required users and groups which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation guide for additional platforms: Linux AMD 64 (SLES 9 & Red Hat 4) → Part 1. Preinstallation checklist → Setting up required users and groups → Required users and groups
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Required users and groups which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation guide for additional platforms: Linux on iSeries, Linux on pSeries and Linux on zSeries → Part 1. Preinstallation checklist → Setting up required users and groups → Required users and groups
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Requirement verification by the installer which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for AIX → Recovering from installation errors → Requirement verification by the installer
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Requirement verification by the installer which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Linux on Intel → Recovering from installation errors → Requirement verification by the installer
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Requirement verification by the installer which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Solaris → Recovering from installation errors → Requirement verification by the installer
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Requirement verification by the preinstallation script which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation guide for additional platforms: Linux AMD 64 (SLES 9 & Red Hat 4) → Part 6. Recovering from installation errors → Troubleshooting installation errors → Requirement verification by the preinstallation script
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Requirement verification by the preinstallation script which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation guide for additional platforms: Linux on iSeries, Linux on pSeries and Linux on zSeries → Part 6. Recovering from installation errors → Troubleshooting installation errors → Requirement verification by the preinstallation script
the following information:
The umask must be set to 002 for the root user.
should be modified as follows:
The umask must be set to 022 for the root user.
In the Tivoli Provisioning Manager Installation Guide for Linux on Intel version 5.1.1 which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Linux on Intel
the following information should be added:
To install the Tivoli Common Agent (TCA) on Red Hat Linux 5 target computers, the following compatibility packs are required:
On Red Hat Linux (x86 32- and 64-bit) version 5 target computers ensure that the enhanced security is disabled and there is no firewall. Perform the following steps to verify and disable the enhanced security, and then install the common agent:
On Red Hat Enterprise Linux 5.0 64-bit operating systems, the 32-bit compatibility packages are required. You can verify that the 32-bit compatibility packages are installed by running the following command:
rpm -ql xorg-x11-deprecated-libs-6.8.2-1.EL.18
to display which files are installed with the specified RPM package.
If you have the 64-bit version installed, the following files are displayed:
If you have the 32-bit version installed, the following files are displayed:
If you have both versions installed, the following files are displayed:
In the Tivoli Provisioning Manager Installation Guide for Windows version 5.1.1 which can be found navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Windows
the following information should be added:
On Windows 2008 servers, the winCoreCompUpgrade.bat and solutionInstaller.bat files must be run from an administrator command window by performing the following steps:
In Chapter 2. Preinstallation checklist for Linux on System z, in section "Preinstallation Step 2: Verify operating system requirements" subsection "Required packages" the table "Required packages for Linux" needs to be modified as follows for the Red Hat operating system packages:
In the Tivoli Provisioning Manager version 5.1.1 information center topic Installing Cygwin manually, which can be found by navigating as follows:
Installing, configuring, and security → Performing a new installation → Installation Guide for Windows → Appendix D → Installing Cygwin manually
the following information should be added:
Install Cygwin just before installing the core components. During a middleware installation Cygwin might cause an installation failure.
The following updates apply to the Migration and Coexistence Guide for Version 5.1.1.
In Appendix B. Object Mappings, section "Software objects" in the "Software terminology" table, the following information:
should be modified as follows:
In Appendix E. Troubleshooting, section "Replication issues" the following information should be added:
If you perform an Inventory scan using Tivoli Configuration Manager collecting from the Tivoli endpoints data which includes Russian symbols, both Latin and Cyrillic characters, these are correctly displayed in the Tivoli Configuration Manager database.
After replicating the data to an English Tivoli Provisioning Manager server, the data displayed by the data model (DCM) might be truncated or missing. This is a product limitation due to the following reason: a cyrillic character might need more than one byte in the database.
The following updates apply to the information center.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Configuring parameters to software configuration templates, which can be found by navigating as follows:
Reference → Software catalog → Defining software in the software catalog → Software configuration templates → Configuring parameters
to the current paragraph:
Prerequisite: The parameter names correspond to the parameter names in the workflows that are used to install and configure the software. If you are creating a new parameter, ensure that the parameter is supported by the workflows for the software.
the following information should be added:
When you define the value for a new parameter, ensure that you do not use the comma “,” character inside the value.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Nesting software packages, which can be found by navigating as follows:
Developing automation → Software packages → Creating a software package → Nesting software packages
the entire topic should be removed from the information center.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Changing the agent registration password, which can be found by navigating as follows:
Installing, configuring, and security → Configuring the environment → Distribution in branch offices → Tivoli Common Agent Services → Agent registration → Modifying registration password
add to the current procedure a new step 10 as follows:
Step 10: Update the DMSSLConfig.properties file with the new password by following these steps:
su - tioadmin
In the Tivoli Provisioning Manager version 5.1.1 information center topic Uninstalling the common agent, which can be found by navigating as follows:
Installing, configuring, and security → Configuring the environment → Distribution in branch offices → Tivoli Common Agent Services → Uninstalling the common agent
add to the current topic the following three new subsections:
Uninstalling the common agent manually
You can also manually uninstall the common agent from a target computer by using the uninstaller in the home folder where the common agent was installed. To manually uninstall the common agent from the target computer:
0 | cygnus0317b | /opt/tivoli/ep1 | 1.3.0.5 | 0 | 1.4.2
| IBM Corp...
0 | cygnus0317b | /opt/tivoli/ep1 | 1.3.0.5 | 0 | 1.4.2
| IBM Corp...
The elements are located in:
From the tivoli subfolder, run the following command: rm -rf ep*.
If ep is the only subfolder in the /opt/tivoli folder, you can also run the following command from the /opt directory: rm -rf tivoli.
Manually uninstalling TivGUID
TivGUID is a shared component and you must ensure that no other component or product is using it before you remove it from the system.
To manually uninstall TivGUID, perform the following steps:
lslpp -L -c |grep tivguid
installp -u tivoli.tivguid
rpm -qa |grep guidand note the version number.
rpm -e TIVguid-version_number
rm -rf /opt/tivoli/guid
swlist |grep guid
swremove TIVguid
Manually uninstalling Common Inventory Technology (CIT)
If you want to completely remove all the files installed with the common agent, remove the TivGUID directory and the CIT directory.
To manually uninstall CIT, perform the following steps:
Add to the current Tivoli Provisioning Manager version 5.1.1 information center the following information:
If you change the host names or IP addresses on the target computers with Tivoli Common Agent (TCA) installed, to fully process these changes, run the following discoveries in the order specified:
In the Tivoli Provisioning Manager version 5.1.1 information center topic Software package formats, which can be found by navigating as follows:
Developing automation → Software packages → Software package formats
in the Software package block subsection, the following information:
The maximum size of a software package block is 2 GB.
should be modified as follows:
The maximum size of a software package block is 4 GB.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Defining configuration compliance checks for a group, which can be found by navigating as follows:
Managing computers, inventory, and compliance → Managing compliance → Compliance checks → Creating compliance checks → Defining configuration compliance checks for a group
the following information should be added:
When you create a compliance check for a group of computers, you can define a compliance check caching value to the compliance group based on your business needs.
To set a compliance check caching value to your compliance group, perform these steps:
In the Tivoli Provisioning Manager version 5.1.1 information center topic Downloading Windows Update Agent, which can be found by navigating as follows:
Getting started → Tutorials → Managing patches in small environments (Windows) → Part 1: Discovery → Downloading Windows Update Agent
replace the current step 2 of the procedure with the following information:
Find the appropriate workflow and click Actions > Run.
To download files for Windows 32-bit platforms, select the MS_SOA_GetWindowsUpdateAgent workflow.
To download files for both Windows 32-bit and 64-bit platforms, select the MS_SOA_GetWindowsUpdateAgents workflow.
In the Tivoli Provisioning Manager version 5.1.1 information center section Other common problems, which can be found by navigating as follows:
Troubleshooting and support → Known limitations → Other common problems
the following troubleshooting topic should be added:
Symptoms
If you leave the Alphablox data source password empty, when running any reports the operation ends with an error and no reports are generated.
The server.log file might contain the following error:
Application Manager: Could not load application applicationstudio_examples_email (null ( null )) (java.lang.NullPointerException) ... [ERROR] Web Application Server Adapter: java.lang.NullPointerException ...
While the console.log file might contain the following error:
ERROR [WebContainer : 1] (Location.java:626) struts.BaseDispatchAction: COPJEE101E An unexpected user interface error occurred null. com.thinkdynamics.kanaha.webui.UISystemException: COPJEE101E An unexpected user interface error occurred null.
This problem occurs using WebSphere 6 with Alphablox 8.4.
Resolving the problem
Have a non-empty string set as data source password.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Creating a virtual server template, which can be found by navigating as follows:
Getting started → Tutorials → Managing operating systems for AIX on pSeries → Part 2: Allocating a virtual server → Creating a virtual server template
the following step:
Click Virtual Storage Templates.
should be modified as follows:
Click Virtual Server Templates.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Installing patches from recommendations, which can be found by navigating as follows:
Getting started → Tutorials → Managing patches in large environments (Windows) → Part 4: Compliance → Installing patches
the following information (step 5 of the procedure):
Return to the Compliance page for the group, and access the Issues and Recommendations page again. The status for the issues is now either Implemented or Failed.
should be modified as follows:
Return to the Compliance page for the group, and access the Issues and Recommendations page again. The status for the issues is now either Implementing or Failed. A successful implementation of the recommendations does not change their state.
In the Tivoli Provisioning Manager version 5.1.1 information center topic Adding custom views for the report wizard, which can be found by navigating as follows:
Managing computers, inventory, and compliance → Reporting → Creating a new report → → Adding custom report views
the following information:
should be modified as follows:
In the Tivoli Provisioning Manager version 5.1.1 information center topic Audit reports, which can be found by navigating as follows:
Managing computers, inventory, and compliance → Reporting → Predefined reports → Audit reports
the current table:
Table 4. Audit 003 - What hardware changes were made by which user?
should be replaced by the following table:
| Output data | Description |
|---|---|
| Computer ID | The computer ID. |
| Computer Name | The name of the computer. |
| Hardware Name | The hardware name. |
| Type | The type of hardware. |
| Audit User Name | The user responsible for the hardware change. |
| Audit Time | The time that the hardware change occurred. |
| Operation | The type of hardware change that occurred. |
| Partitionable | Indicates if the hardware is partitionable. |
| Managed | Indicates if the hardware is managed. |
| Property | An additional property name. |
| Property Value | The additional property value. |
| Group Name | The group name that the hardware resource belongs to. |
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.
On Solaris, Web pages do not load and an Out of Memory error is reported in the j2ee/console.log file.
This is caused by an issue with the Sun Java™ Virtual Machine. For more information, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5077277
Open the Web Sphere Administrative Console and click Servers > Application servers > server1 > Process Definition > Java Virtual Machine. Change the Maximum Heap Size to 1024 and save the configuration change. Then restart the provisioning server.
Using Software Package Editor (SPE) on an AIX Tivoli Provisioning Manager server, when trying to save a software package block (SPB) file bigger than 2 GB, SPE displays the following error message:
DISSP6050E An error occurred while uploading the package. See the log for details.
On an AIX Tivoli Provisioning Manager server, create SPB files smaller than 2 GB.
When you install the common agent on UNIX endpoints, the installation might time out.
When trying to perform a Tivoli Common Agent installation (TCA) on UNIX endpoints, the following error message is displayed:
COPCOM116E The operation timed out.
If you are using the file /etc/hosts to resolve IP addresses, one possible cause might be that the file is not configured correctly.
Verify the /etc/hosts file. The file must include:
#IP address Fully Qualified Domain Name Short Name 10.0.0.12 river.example.com river 127.0.0.1 localhost.localdomain localhost
The Tivoli common agent (TCA) upgrade from version 1.3.2.25 to version 1.3.2.30 fails on target computers with Windows Vista and Windows 2008 installed, and displays the following error message:
COPTCA002E Unable to connect to the common agent endpoint running on computer hostname at IP port 9510. Ensure that the Tivoli Common Agent service is started and available.
Tivoli Provisioning Manager 5.1.1 or 5.1.1.1 does not support the Windows Vista and Windows 2008 as manage-to platforms. The TCA 1.3.2.25 installation on these platforms only adds the target computers in the Agent Manager database but does not install TCA locally on these computers.
After upgrading to Tivoli Provisioning Manager 5.1.1.3, ensure that you manually remove these computers from the Agent Manager database following these instructions:
RetrieveAgents.sh –dbPassword password [-exp y/n/a]
LogicallyDeleteAgents.sh –dbPassword password –me management element ID
PurgeAgents.sh –dbPassword password [-me ID]
The Tivoli common agent (TCA) 1.3.2.25 information is not updated on the Web interface for Linux target computers.
When Linux target computers, with common agent 1.3.2.25 installed, are discovered for the first time the agent information is not updated on the Web interface.
This issue can be resolved by performing the following steps:
agent.ssl.truststore.downloadinto:
agent.ssl.truststore.download = true
After canceling an SPB file installation on a target computer with Tivoli common agent (TCA) 1.3.2.30 installed, the partially downloaded files on the target computer are not deleted.
Manually remove the partially downloaded files that remain installed on the target computer from the following directories:
C:\Program Files\tivoli\ep\runtime\agent\subagest\cds\client\cache\files\1or
C:\Program Files\tivoli\ep\runtime\agent\subagest\cds\downloads\incomplete
/usr/tivoli/ep/runtime/agent/subagents/cds/client/cache/files/1or
/usr/tivoli/ep/runtime/agent/subagents/cds/downloads/incomplete
/opt/tivoli/ep/runtime/agent/subagents/cds/client/cache/files/1or
/opt/tivoli/ep/runtime/agent/subagents/cds/downloads/incomplete
/opt/tivoli/ep/runtime/agent/subagents/cds/client/cache/files/1or
/opt/tivoli/ep/runtime/agent/subagents/cds/downloads/incomplete
/opt/tivoli/ep/runtime/agent/subagents/cds/client/cache/files/1or
/opt/tivoli/ep/runtime/agent/subagents/cds/downloads/incomplete
If you distribute a second time, in a SDI infrastructure, a software product or a file, published on a depot server upgraded to version 5.1.1.3, to a SUSE Linux 9 or 10 target computer with Tivoli Common Agent upgraded to 5.1.1.3 associated to that depot server, the distribution fails.
From the Web interface, unpublish and then publish again on the depot server the software product or the file that you are trying to distribute again to the SUSE Linux 9 or 10 upgraded target computer, then perform the distribution.
After installing this fix pack (5.1.1.3) using the option to rectify file permissions, when performing a manual check of permission settings, the check shows that the profiles folder and the symbolic links contained in the WAS_HOME directory have group write permissions.
The profiles folder contained in the WAS_HOME directory is not affected by the file permission rectification, only the default sub directory will change. The symbolic links in WAS_HOME will show to have both group and others write permissions after the file permission rectification, which represents their default behavior.
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 APDE (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 APDE (Automation Package Development Environment) for writing workflows and creating automation packages for the Tivoli Provisioning Manager for Software products.
To access the forum:
The notices file in the license subdirectory has been updated for this release.
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 about 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:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
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 might not apply to you.
This information might 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 or changes in the product(s) or in 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 want 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:
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.
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml
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.