![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new information for the following manuals of the IBM(R) Tivoli(R) Configuration Manager, Version 4.2.1 library, contained in previous fix packs.
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Software Distribution.
In Chapter 9. "Preparing a Software Package Distribution", section "Executing Change Management Operations", subsection "Verify a Software Package", add the following paragraph as the final paragraph of the section:
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is equal to or greater than the date of the same file in the package. If the date of the file is older the date of the same file in the package, the operation fails. The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
and replace it with:
In Table 14. "Software Distribution Tivoli Enterprise Console events", add the following information to the Notes(R) section of the SD_Operation_Failed event:
You can change the severity level to CRITICAL, MINOR, or HARMLESS.
In Chapter 9 "Preparing a Software Package Distribution", section "Executing Change Management Operations", sub-section "Verify a Software Package", add the following paragraph as the final paragraph of the section:
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is the same or later than the date of the same file in the package. If the date of the file is older than the date of the same file in the package, the operation fails. The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
The following new information applies to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
In Chapter 2 "Performing Change Management Operations", in the section "Editing the Software Package Definition File", subsection Attributes in Windows(R) Registry Object Stanzas, Table 14, SPD file attributes for Windows registry objects, add the following note to the explanation of the add attribute:
To override this setting, add the __ALWAYS_ADD_WINREG_KEYS__ variable to the in swdis.var file and set it to YES or NO. If you set __ALWAYS_ADD_WINREG_KEYS__ to YES, parent registry keys are always created, irrespective of the setting specified for the add attribute.
In Chapter 2 "Performing Change Management Operations", section "Types of Change Management Operations", subsection "Verify Operation", add the following second paragraph before the note:
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is the same or later than the date of the same file in the package. If the date of the file is older than the date of the same file in the package, the operation fails. The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
In Chapter 3 "Using Commands" add the following MDist 2 token to the commands listed below:
Specifies whether the distribution fails on endpoints that cannot be reached for any reason. Supported values are true and false. The default value is false.
This token is to be added to the MDist 2 options for the following commands:
In Chapter 3 "Using Commands" add the following key to the wswdcfg command:
In Chapter 3 "Using Commands", in the description of the wspmvdata command add the following paragraph after the list in the Description section:
In the data moving architecture, data is moved between source hosts and endpoints and between one endpoint and multiple endpoints. A source host is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed. The source host corresponds to the origin system when send operations are performed, with the exception of send operations from one endpoint to multiple endpoints. During a retrieve operation, instead, the source host is the destination system.
Replace the description of the spre:src_prescript, spost:src_postscript, tpre:targ_prescript, tpost:targ_postscript options in the Options section, with the following descriptions:
Specifies a script to run on the origin system of the data file, before the data is transmitted. When sending data, the origin system must be a source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed, or an endpoint, when data is sent from one endpoint to one or more endpoints. When retrieving data, the origin list can include multiple Tivoli endpoints, files that store a list of endpoints, profile managers, or a combination of these. Where the -s option specifies a list of endpoints, the script runs on each endpoint.
Specifies a script to run on the origin system of the data file, before the data is transmitted. When sending data, the origin system must be a source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed, or an endpoint, when data is sent from one endpoint to one or more endpoints. When retrieving data, the origin list can include multiple Tivoli endpoints, files that store a list of endpoints, profile managers, or a combination of these. Where the -s option specifies a list of endpoints, the script runs on each endpoint.
Specifies a script to run on the destination system, before the data is transmitted. When retrieving data, the destination system must be a source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed, which afterwards redirects the data to the destination systems. When sending or deleting data, the destination list can include multiple Tivoli endpoints, files that store a list of endpoints, profile managers, or a combination of these. Where the -t option specifies a list of endpoints, the script runs on each endpoint.
Specifies a script to run on the destination system, before the data is transmitted. When retrieving data, the destination system must be a source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed, which afterwards redirects the data to the destination systems. During retrieve operations, the post-script on the origin system (an endpoint) runs before the data is sent to the destination system. When sending or deleting data, the destination list can include multiple Tivoli endpoints, files that store a list of endpoints, profile managers, or a combination of these. Where the -t option specifies a list of endpoints, the script runs on each endpoint.
In the "Scripts for Pre- and Post-processing" section, replace the first bulleted list with the following two lists:
In the "Scripts for Pre- and Post-processing" section, replace the descriptions for parameters 5 and 6 with the following descriptions:
Unique endpoint identifier. This parameter is only available for the post-processing script on the source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed.
Result of the operation on the endpoint. Possible results are 0 (success) and 1 (failure). This parameter is only available for the post-processing script on the source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed.
In the Scripts for Pre- and Post-processing section, replace the explanation for the example with the following explanation:
The destination system for this command is a source host and the source list includes two endpoints. The purpose of the merge.sh script is to create a single file on the source host system by merging the files that have been retrieved from the endpoints. The merge.sh script is performed as a post-processing script on the source host after the files have been retrieved from the specified endpoints.
In Chapter 3 "Using Commands", in the section wspmvdata, add the following section after the Scripts for Pre- and Post-processing section:
Sending Multiple Files: When you need to send several different files with similar names to different endpoints and each endpoint must receive only a specific file, you can use the $(ep_label) variable in the source file name. The $(ep_label) variable replaces the label of the endpoint.
The $(ep_label) variable is then resolved on each endpoint and the file named with the endpoint label is installed on the corresponding endpoint.
When you perform a send operation using this variable, an internal software package is created in the product_dir on the source host, that is a Tivoli managed node, functioning as a gateway or a repeater, where Software Distribution is installed. This software package contains all the files to be sent to the endpoints and a condition for each file which specifies on which endpoint each file must be installed. The software package is then sent to the target endpoints where the variable is resolved and the files installed.
You can specify the maximum size for the software package by setting the dms_send_max_spb_size key with the wswdcfg command. For more information on this command, refer to IBM Tivoli Configuration Manager: Reference Manual for Software Distribution. The default value for this key is 10,000 kilobytes. You can set this value to any integer equal to or lower than two gigabytes, which is the maximum size for a software package. The value defined on the Tivoli server is applied to the entire region, irrespective of the values defined on the source hosts, if any. Note that an amount of space at least equal to the value you specify must be available in the product_dir on the source host for the package to be created.
To calculate the precise value for the dms_send_max_spb_size key, you need to consider the total size of the files to be sent plus 2 kilobytes for each endpoint.
If you are working with interconnected regions, you must perform the following operations when sending multiple files:
This behavior allows you to manage endpoints with duplicate labels within interconnected regions.
The following command sends files data.ep1#sales-region.txt to endpoint ep1#sales-region, file data.ep1#resources-region.txt to endpoint ep1#resources-region, and file data.lab132782-ep.txt to endpoint lab132782-ep, registered to the same region where the source host is located.
wspmvdata -s @yoursourcehost -t @ep1#sales-region, @ep1#resources-region, @lab132782-ep -P sp:c:\source\ -P tp:c:\target data.$(ep_label).txt
When specifying the distribution list the pound (#) sign and region name must be specified only when the endpoint label is duplicate between one or more endpoints. Note that files data.ep1#sales-region.txt, data.ep1#resources-region.txt, and file data.lab132782-ep.txt must be present on the source host, otherwise the operation is not performed because the -F option has not been specified.
To determine the region to which the specified endpoint belongs, type the following two commands on the Tivoli server:
eid=`wlookup -r Endpoint endpoint_name | awk -F'.' '{print $1}'`
ep_region=`wlsconn | grep $eid | awk '{print $2}'`
where:
The results of the commands are returned to standard output. If the output returned is empty, the endpoint belongs to the region where the command was launched. If you have a large number of endpoints, you can insert this command in a script file. On Windows systems, these commands must be run in a bash shell. For more information on the wlookup and wlsconn commands, refer to Tivoli Management Framework: Reference Manual.
In the DataMovingRequests.1.log file, the information concerning the distributions to interconnected regions is logged according to the following criteria:
In Chapter 3 "Using Commands", in the section wswdcfg, add the following key after the continue_on_invalid_targets key:
Add the following note to each explanation of the from_fileserver option:
In Chapter 2 "Performing Change Management Operations", section "Types of Change Management Operations", sub-section "Verify Operation", add the following second paragraph before the note:
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is the same or later than the date of the same file in the package. If the date of the file is older than the date of the same file in the package, the operation fails. The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Deployment Services.
In Chapter 2 "Performing Activity Planner Operations", in the section "Selecting Targets for an Activity", add the following text to the first item in the list in step 4:
In Chapter 2 "Performing Activity Planner Operations", in the section "Scheduling Plans to execute within a time interval", add the following text in step 5 after the note:
If the plan contains activities which cannot be canceled, that is Tivoli Framework tasks or Software Distribution operations addressed to devices or users, a warning message is displayed. If you choose to submit the plan, and the Complete not after time expires, all activities are cancelled with the exception of Tivoli Framework tasks and Software Distribution operations addressed to devices or users.
In Chapter 3, section "Activity Plan Definition file", Table 2, add the following text to the description of the compl_not_after subelement:
If the plan contains activities which cannot be cancelled, that is Tivoli Framework tasks or Software Distribution operations addressed to devices or users, a warning message is displayed. If you choose to submit the plan, and the compl_not_after time time expires, all activities are cancelled with the exception of Tivoli Framework tasks and Software Distribution operations addressed to devices or users.
Also, replace the description of the cancel_at_cutoff subelement with the following text:
If set to n, the time specified by the compl_not_after attribute is ignored for those activities already in execution. If set to y, activities in execution when the compl_not_after time is reached are canceled. If the plan contains activities which cannot be cancelled, that is Tivoli Framework tasks or Software Distribution operations addressed to devices or users, a warning message is displayed. If you choose to submit the plan, and the compl_not_after time time expires, all activities are cancelled with the exception of Tivoli Framework tasks and Software Distribution operations addressed to devices or users.
2. Select either the Pause, Resume, Restart, Cancel, or Cancel Force option from the Selected menu.
Add the following information after the explanation of Cancel:
You can use Cancel Force to change the operation state of an activity plan to "cancelled", even when submitted operations are not cancelled. Cancel Force has the same functionality as the wcntpln -f command.
In Chapter 7 "Using the Command Line", in the section "Managing Reference Models" add the following paragraph after the bulleted list:
You can specify a timeout for CLI commands in Change Manager using the environment variable _CCM_CLI_TIMEOUT_=<seconds>. This is useful when you are using the wsyncrmod command to synchronize a reference model, because you can specify a timeout that gives wsyncrmod enough time to successfully complete. You can set the _CCM_CLI_TIMEOUT_ variable in the shell or in the setup_env file.
The following new information applies to the IBM Tivoli Configuration Manager: Messages and Codes.
In Chapter 5, create a new section after the "Components Installed" section, named "Component Prerequisites", and include the following text:
When using this installation, the following component prerequisites must be installed before starting the installation.
Component | Software to be installed as prerequisite |
---|---|
Tivoli Management Framework | None |
Web Interface | Tivoli Management Framework, Version 4.1, or later |
Activity Planner |
|
Change Manager |
|
Inventory and Inventory Gateway |
|
Resource Manager and Resource Manager Gateway |
|
Software Distribution and Software Distribution Gateway |
|
Enterprise Directory Query Facility |
|
Pristine Manager |
|
Pristine Manager Gateway | Tivoli Management Framework, Version 4.1, or later |
Software Package Editor |
|
When using this installation, the following component prerequisites must be installed before starting the installation.
Component | Software to be installed as prerequisite |
---|---|
Web Gateway database | DB2 |
Web Gateway server |
|
Web Infrastructure |
|
When using this installation, the following component prerequisites must be installed before starting the installation.
Component | Software to be installed as prerequisite |
---|---|
Tivoli Desktop for Windows | None |
Java components | None |
Activity Planner GUI | Java components |
Distribution Status console | Java components |
Change Manager GUI | Java components |
Inventory GUI | Java components |
Software Package Editor |
|
The following new information applies to the IBM Tivoli Configuration Manager: Messages and Codes.
In Chapter 8, in the section "DIS SE Messages", add the following messages after message DISSE0602E:
The file to be deleted is not found.
The submitted operation is not performed.
Verify that the name of the file or the path name are correct.
The software package you are trying to create and send cannot be built because there is either not enough space in the product_dir on the source host or the maximum size defined for the software package has been exceeded.
The operation is not performed.
Check that the space available in the product_dir on the source host is sufficient for creating the software package and verify the value defined for the maximum size of the software package. Add more space to the product_dir on the source host or increase the maximum size of the software package using the dms_send_max_spb_size option with the wswdcfg command. For more information on this option, refer to IBM Tivoli Configuration Manager: Reference Manual for Software Distribution. Note that two gigabytes is the maximum size for a software package.
[ Top of Page | Previous Page | Next Page | Contents ]