![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains a cumulative list of new features introduced in the previous fix pack and the current fix pack.
No new features are provided with this fix pack.
The following new features and enhancements have been introduced in previous fix packs:
HP-UX support has been added for the Tivoli Gateway Component. This component can now be installed on HP-UX platforms using any of the installation mechanisms. The installation program, software package blocks, and images used for the installation are located in the TWG_HP directory on the IBM Tivoli Configuration Manager, Version 4.2 Fix Pack 3 CD (2 of 2). Interim fixes for Tivoli Resource Manager components include the compatibility for the new HP-UX support for the Tivoli Gateway component.
On Windows NT(R), 2000, and XP operating systems, the Web user can perform the install, uninstall and verify operations on a software package even if he is not logged on as administrator. See "Enabling User Context Switch" in Documentation notes, New Information, User's Guide for Deployment Services for more details.
You can make Web objects accessible to all users by eliminating the use of the IBM Tivoli Access Manager and IBM Tivoli Access Manager WebSEAL security mechanisms. Running the Web Interface without user restrictions to Web objects means that no authentication is performed when accessing Web objects. When publishing Web objects, the administrator can choose to not specify user information so that the object published can be accessed by all users. When starting the Web Interface, type the Web address for the Web Interface server in the following form for unrestricted access:
http://hostname/WebConsole/com.tivoli.webui.servlets.ConsoleMain
where, the host name represents the machine where WebSphere(R) is installed and configured. Connecting to the Web Interface server in this way allows access to all published Web objects. See "Unrestricted Access to Web Objects" in "New information contained in previous fix packs", User's Guide for Deployment Services for more details.
New tags added to swdis.ini permit mobile users to check the status of data retrieve operations. Add the following new tags to the Software Distribution configuration by using wswdcfg command on the source host where the retrieve operation initiates:
For the Activity Plan Editor and Change Manager graphical user interfaces, a search button has been added to browser dialogs that you use to select software packages, tasks, and targets. The search button permits you to search your Tivoli environment for specific objects.
To avoid corruption of the message file due to insufficient disk space during the reporting phase, the following limitations have been introduced:
Fix pack 1 releases an endpoint bundle to support Linux on PowerPC. To enable this feature you must install the following interim fixes on the Tivoli management region server:
The sharing_control keyword has been added to the software package properties. An existence check is performed on files and registry values. This avoids their deletion when the package is removed, if these objects were already present on the target prior to the distribution of the software package. See "Defect 34924" in "Documentation problems and corrections contained in previous fix packs", User's Guide for Software Distribution and Reference Manual for Software Distribution for more details.
A restart action can be defined to be performed during the commit of the package. See "APAR IY34938" in "Documentation problems and corrections contained in previous fix packs", Reference Manual for Software Distribution for more details.
The java plug-in can be automatically downloaded on the Web user's machine by adding the URLs to the webconsole.properties file and setting the value of the PLUGIN_AUTH_DOWNLOAD.ENABLED key to "true". See "Enable Java plug-in auto-download" in "New information contained in previous fix packs", User's Guide for Deployment Services for more details.
A new mechanism has been added to check if the reboot of machine has been performed. This means that if the package is in a "changing" status, Software Distribution behaves in the following ways:
A new '-r' option has been added to handle the 'no_chk_on_rm' SPO attribute:
Usage: wgetspop {-h | -j | -L | -m | -P | -r | -u} spobj_name
Usage:
wsetspop {[-h log_host] [-j log_mode] [-L log_path] [-m mail_id] [-P post_notice] [-r no_chk_on_rm] [-u log_uid]} spobj_name
For the wsetspop command, the acceptable values for the -r option are y/n. The default value for no_chk_on_rm is y (yes).
Before the introduction of this option, if a retrieve or send operation with a postscript was performed and the postscript returned an error code, the data moving operation completed as successful anyway. Using the "-B" option from the data moving command line, the retrieve and send operations correctly fail if a non-zero postscript exit code is returned.
You can customize the default path used by the Software Package Editor file browser dialog boxes, and the open and save dialog boxes, so that they always open in the path you specify. The default setting is speditor_dir\interp\classes, where, speditor_dir represents the directory where the Software Package Editor is installed, as defined in the swdis.ini file. Edit the speditor.ini file located in the speditor_dir\config directory. The structure of the file is simply as follows:
inipath=C:/tmp
where, C:/tmp represents the path used by the Software Package Editor.
Before the introduction of this feature, when Software Distribution runs on an endpoint for the first time, or if the endpoint name has been changed since the last Software Distribution operation, the section in the swdis.ini file that corresponds to the ep-label is created by cloning the contents of the section [#MOBILE], if it exists. If this section does not exist, a new prod_dir is created. With the implementation of this feature, the user can decide how the section that corresponds to the ep-label should be created when it does not exist, particularly if the endpoint has been renamed.
A new key has been added to the wswdcfg command: how_create_ep_section. The key can assume the following values:
[ Top of Page | Previous Page | Next Page | Contents ]