![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains problems and corrections for the following manuals of the IBM(R) Tivoli(R) Configuration Manager, Version 4.2.1 library, referring to previous fix packs:
The following information changes apply to the User's Guide for Software Distribution.
In Chapter 15. "Troubleshooting", section "Troubleshooting Process", add the following text as the first paragraph in Step 3:
When a software package is distributed to an endpoint, a check is performed on a subset of the actions contained in the package. If any of the checks on these actions fails, the package installation stops and no action is performed on the endpoint. The following is a list of the actions that are checked on the endpoint.
If all checks are successful, the package installation starts and the actions contained in the package are performed in the order in which they are listed.
If any actions fail for reasons other than those already explained, the package installation stops. All actions listed in the package before the failed one have already been performed on the endpoint.
You should install the software package in undoable mode, so you can return the system to its previous state if the installation fails.
In Chapter 11. "Configuring a Network Topology", section "Software Distribution Methods", add the following paragraph at the end of the section:
The methods most frequently used by Software Distribution are:
In Chapter 3 "Using the command line", in the section "Parameters of Software Distribution Operations", tables 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, replace every occurrence of the ExecuteTimeout parameter with ExecutionTimeout and every occurrence of the ExecuteTimeoutUnit parameter with ExecutionTimeoutUnit .
In Chapter 1 "Using Activity Planner", in the section "Defining the Activity Planner Engine Parameters", add the following keyword after the deep_gc_interval:
In Chapter 15. Troubleshooting, section "Troubleshooting the Software Package Editor GUI", add the following bullet after the first bullet:
2. To use the Software Package Editor on Windows XP systems, you must be a member of either the Administrators or Power Users group.
In Chapter 12 "Integrating the Tivoli Enterprise Console(R)", section "The tecad_sd.conf File", subsection "RetryInterval", change the sentence: "The default interval is 120 seconds." to read "The default is 1 second."
In Chapter 9 "Preparing a Software Package for Distribution", section "Change Management Operations", subsection "Installing the Appsample^1.0 Software Package", add the following note to the end of Step 5:
In Chapter 15, "Troubleshooting", section "Software Distribution Log", add the following note to the "Distributive" section:
In Chapter 9, "Preparing a Software Package for Distribution", section "Change Management Operations", subsection "Installing the Appsample^1.0 Software Package", step 5, add the following note after the first sentence:
Chapter 9, "Preparing a Software Package for Distribution", section "Change Management Operations", subsection "Installing the Appsample^1.0 Software Package", add the following sentence after the fourth sentence in step 5:
In addition, if the base and the version packages use the same file in the same directory, the packages must be in software package block (built) format, otherwise the whole file is distributed. Byte-level differencing uses dependency checking to verify if the base package has been installed on the target.
Chapter 13, add the following text at the end of the section "Monitoring the Results of Operations": For software packages containing restart actions, the report containing the result of the distribution is sent to the Tivoli server after a second operation is performed on the target.
In Chapter 1 "Overview of Software Distribution", in the section "Software Distribution Highlights", modify the Source and repair functionality item description as follows:
The repair functionality identifies which source and target objects have been modified or corrupted since the last successful installation of a software package, and rebuilds the software package with only these objects rather than installing the entire package again. The submission of a repair operation might take a long time if the check of objects modified or corrupted is run for a large number of endpoints.
In Chapter 12 "Integrating the Tivoli Enterprise Console", in the table "Software Distribution Tivoli Enterprise Console events" the description of the event SD_Operation_Failed should be modified as follows:
By default, severity = FATAL and sub_source = swdist. You can change the severity level to all levels allowed by Tivoli Enterprise Console: CRITICAL, MINOR, WARNING, HARMLESS, or UNKNOWN.
The following information changes apply to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
In Chapter 1 "Editing the Software Package Definition File", in the section "Software Package Name and Version", add the following sentence after the first list:
The length of the string that defines the name and version of a software package can vary depending on how you distribute it:
If you use Activity Planner, the maximum length of the string must be 128 characters. It includes name, delimiter, version (64 characters), and #region name.
If you do not use Activity Planner, the maximum length of the string must be 230 characters. It includes name, delimiter, and version (64 characters).
In Chapter 2. "Editing the Software Package Definition File", Table 11 "SPD File Attributes in File System Stanzas", add a second note to the explanation of the descend_dirs attribute:
In Chapter 1. "Editing the Software Package Definition File", section "System Actions", subsection "Restart", Table 38 "Software Package Definition File attributes of the restart stanza", replace the last bullet in the explanation of the force_restart attribute with the following text:
If the timeout attribute is greater than or equal to zero and the force_restart attribute is set to y, a soft reboot is invoked. If it fails, a hard reboot is performed after the timeout expires and when the gateway reconnects to the endpoint.
In Chapter 1. "Editing the Software Package Definition File", section "Attributes in the File System Stanzas", Table "SPD File attributes in file system stanzas", remove the following note from the explanation of the rename_if_locked attribute:
In Chapter 3, in the explanation of the wsetsps command, replace the two paragraphs following the Description heading with the following two paragraphs:
Make the following change to the Reference Manual for Software Distribution:
In the section "Server Commands", subsection "wsetsps", add the text "(not in Transactional mode)" to the command description so that it reads:
"Only the following operations are available:
In the section "Disconnected Target Commands", subsection "wdsetsps", add the text "(not in Transactional mode)" to the command description so that it reads:
"Only the following operations are available:
To apply the delta installation, the base and the version packages must have the same nested structure. The above operation is performed on the source host and generates a delta package that is sent to the target.
to:
To apply the delta installation, the base and the version packages must have the same nested structure. In addition, if the base and the version packages use the same file in the same directory, the packages must be in software package block (built) format, otherwise the whole file is distributed. The above operation is performed on the source host and generates a delta package that is sent to the target.
To apply the delta installation, the base and the version packages must have the same nested structure. Byte-level differencing uses dependency checking to verify that the base package has been installed.
to:
To apply the delta installation, the base and the version packages must have the same nested structure. In addition, if the base and the version packages use the same file in the same directory, the packages must be in software package block (built) format, otherwise the whole file is distributed. Byte-level differencing uses dependency checking to verify that the base package has been installed.
If you perform a transactional installation and select this option from the command line, the report containing the result of the distribution is sent to the Tivoli server after a second operation is performed on the target.
Chapter 3, replace the description of the -c option for the following commands with the text below:
Specifies the reboot options for the commit operations: n (not-in-a-reboot), which is the default, y (in-a-reboot), o (in-a-reboot), r (auto-reboot). For more information on these options, see Commit Operation.
The following information changes apply to theIBM Tivoli Configuration Manager: User's Guide for Deployment Services.
In Chapter 1 "Using Activity Planner", in the section "Before You Start", modify the sentence:
RIM_view or RIM_update role, depending on database operation.
as follows:
RIM_view and RIM_update roles.
In Chapter 1 "Using Activity Planner", in the section "Activity Planner Roles", modify the table "Activity Planner roles and operations" by adding in all the cells of the Required roles column the following roles:
RIM_view
RIM_Update
In Chapter 3, "Using the command line", section "Parameters of Software Distribution Operations", tables 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, replace every occurrence of the ExecuteTimeout parameter with ExecutionTimeout and every occurrence of the ExecuteTimeoutUnit parameter with ExecutionTimeoutUnit .
In Chapter 1, "Using Activity Planner", section "Defining the Activity Planner Engine Parameters", add the following keyword after the deep_gc_interval:
In Chapter 13, section Monitoring the Results of Operations, add the following information before the table:
The software packages distributed using Software Distribution are tracked in the Inventory database by the endpoint label, while the software packages distributed using the Web Interface are tracked by the workstation hostname. This condition can lead to a misalignment of information in the Inventory database if you install an endpoint on the Web Interface client workstation and distribute software packages to this workstation using Software Distribution. To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
In Chapter 13, section "Troubleshooting", subsection "Administrator on the Tivoli server" add the following problem after the last problem in this section:
Solution: To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
In Chapter 1 "Using Activity Planner", in the section "Before You Start", modify the sentence:
as follows:
In Chapter 1. Using Activity Planner, Understanding the Activity Planner Environment sub-section, Table 1. Activity Planner roles and operations, modify the table by adding the RIM_view and RIM_Update roles to all the cells in the Required Role column.
In Chapter 2, Table 2 "Subelements that define the activity plan", targets_computation row, add the following information:
If targets are defined at plan level and targets resolution is specified at plan submission, targets are calculated when the plan is submitted and inserted in ACT_STATUS_TGT. In case the target exists, the OID in the table is the current OID, otherwise it is ----.
In Chapter 2 "Using the Command Line", Table 3 "Subelements that define frequency information", targets_resolution row, add the following information:
If the targets resolution is at activity execution (targets_computation=a), the targets are evaluated when the activity starts.
The following information changes apply to the Planning and Installation manual.
In "Chapter 7. "Desktop Installation", section "Upgrading Tivoli Desktop for Windows", add the following note at the end of the chapter:
In "Chapter 2. Planning a Configuration Manager Environment", section "Using Configuration Management in Connected Tivoli Regions", replace the introductory sentence with the following:
This section discusses the requirements for running inventory scans, distributing software, and managing devices and users in connected Tivoli regions. If you plan to use IBM Tivoli Configuration Manager among Tivoli regions, the following conditions must be met:
In Chapter 5. "IBM Tivoli Configuration Manager Installation and Upgrade", section "Server Upgrade", add the following note to step 10:
In Chapter 7, "Desktop Installation", section "Desktop Installation", replace the paragraph:
The Desktop installation program installs Tivoli Desktop for Windows and the IBM Tivoli Configuration Manager administrative interfaces. This installation can be used on the following Windows operating systems only:
with the following two paragraphs:
The Desktop installation program installs Tivoli Desktop for Windows and the IBM Tivoli Configuration Manager administrative interfaces. This installation can be used on supported Windows operating systems only.
To install Tivoli Desktop for Windows on Windows Server 2003, open the Desktop directory on CD 3 of the IBM Tivoli Configuration Manager Desktop CD (cd3\desktop), then run setup.exe. When the Tivoli Desktop installation is complete, you can install components that are provided as SPBs (located in the directory cd3\SPB), using Software Distribution (see the section" Components Installed using Software Package Blocks" for more information).
In Chapter 1, section "IBM Tivoli Configuration Manager Components and Services", add the following information to the Software Distribution component description:
You must install the Software Distribution component on the Tivoli server before you can install either the Software Distribution or Software Distribution Gateway component on any managed node in the local Tivoli region.
In Chapter 1, at the end of section "IBM Tivoli Configuration Manager Components and Services", delete the following paragraph:
You must install these components on the Tivoli server before you can install them on a managed node or before you can install the associated gateway component on a gateway. For example, you must install the Software Distribution component on the Tivoli server before you can install either the Software Distribution or Software Distribution Gateway component on any managed node in the local Tivoli region.
The following information changes apply to the IBM Tivoli Configuration Manager: User's Guide for Inventory.
In Appendix B "Commands" replace the usage of the wloadiso command with the following usage:
wloadiso [-d { 1 | 2 | 3 }] -f filename | -l listfilename
and replace the description of the -f DAT file option with the following two options:
In Appendix B "Commands", section "wcollect", replace the description of the -n option with the following text:
In Appendix B "Commands", section "wcancelscan", replace the description of the Authorization sub-section with the following text:
Super and senior.
In Appendix B, add the following sentence for commands wdistinv and winvmgr, at the end of the wake_on_lan description:
If you set this option in an InventoryConfig profile, its value overrides the wake_on_lan keyword value.
In Appendix B, add the following sentence for commands wdistinv and winvmgr, add the following sentence at the end of the hidden description:
If you set this option in an InventoryConfig profile, its value overrides the hidden keyword value.
The following information changes apply to the Database Schema Reference.
In Chapter 5 "Configuration repository tables", in the section "History tables for Inventory", change the history table name H_INST_NATIVE_SWARE to the following name: H_INST_NATIV_SWARE.
In Chapter 3 "Configuration repository views" remove the following view names: DEV_STATUS_VIEW, H_EXPAND_CARD_VIEW and H_MEM_CARD_VIEW.
In Chapter 3 "Configuration repository views" add the following view name: H_DEV_CARD_VIEW.
The following information changes apply to the Release Notes(R).
In Chapter 2. "Installation and upgrade notes", Table 1 "Supported Tier 1 operating systems by components and services", make the following change:
Divide the table row "IBM AIX Versions 5.1, 5.2" into two separate rows; one row for Version 5.1, and one row for Version 5.2. Both rows have the same check marks to indicate that Server/Managed Node and Endpoint are supported. Version 5.1 also has a check mark for Gateway, but Version 5.2 does not, because it does not support Gateway.
In Chapter 3, "Software limitations, problems, and workarounds", section "Software limitations",subsection "Inventory", add the following information:
The trace files tmesdisn.trc where n is the file number, generated when you issue a command line command, can be written to only by the user who was logged in when the command was issued. If another user logs in and issues a command line command, the trace file content is printed to the standard output.
Workaround: Disable the tracing function, unless it is necessary. The tracing function is intended for debugging purposes. If enabled for extended periods of time, tracing can decrease performance and slow the processing of the product considerably. Alternatively, you can delete the trace files created by the previous user.
In the IBM Tivoli Configuration Manager version 4.2.1 Release Notes, Chapter 2 "Installation and upgrade notes", in the section "Web Gateway", replace the third bullet in the list of Web Gateway server prerequisites with the following text:
IBM WebSphere Application Server, Advanced Edition 4.0.3 and 4.0.6
In Chapter 3, section "Software Problems and Workarounds", sub-section "Software Distribution", add the following problem description and workaround:
Software Package Editor GUI does not start on a Terminal Server Windows 2003.
Workaround: Open Software Package Editor using the Tivoli desktop.
[ Top of Page | Previous Page | Next Page | Contents | ]