IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


New features

This section contains a cumulative list of new features introduced in the current fix pack and in the previous fix packs.

New features in this fix pack

There are no new features in this fix pack.

New features in previous fix packs

The following new features have been introduced in previous fix packs.

Table 3. Customer enhancement request references in previous fix packs
Modify cancel button on endpoint_notification panel Feature 55522
New 32-bit MRMBIOS.EXE Feature 180357
Cancel Force button and menu option for the Activity Plan Monitor graphical user interface (GUI). MR0509031922
SD_operation_failed event is customizable. MR0311035824
Security improvements for the software package definition (SPD) file. MR0205036850
Validation policy for Data Moving enabled. MR051603275
The Change Manager CLI command timeout is now customizable. Defect 49765
Mandatory date in End User Notification window. Feature 50710
Displaying the .jar files version Feature 55204
Pocket PC device agent feature OR1020043017
Defer time management for end user notification panel Feature 53373
Avoiding concurrent logins during critical distributions Feature 54613

Modify cancel button on endpoint_notification panel
With this feature you can close the new endpoint_notification panel in a different way. On the endpoint_notification panel, the X in the title bar of the panel has been removed, and the cancel button has been replaced by the Reset button, that resets the original values, if they have been changed. The only way to close the panel is to click OK.
New 32-bit MRMBIOS.EXE
With this feature the Windows 64-bit platforms support has been extended. The old 16-bit mrmbios.exe file has been now replaced by a 32-bit file having the same name, and using new device drivers. You can use the mrmbios.exe file to scan new platforms such as AMD 64 and Itanium 64. In order to have this support, the Framework Interim Fix 9 4.1.1-LCF-0024 or later needs to be installed.
Cancel Force button and menu option for the Activity Plan Monitor graphical user interface
A new Cancel Force button and menu option (Selected -> Cancel Force) have been added to the Activity Plan Monitor graphical user interface. With this, you can change the operation state of an activity plan to "Cancelled", even though submitted operations are not cancelled.

The Cancel Force button and menu option have the same functionality as the wcntpln -f command.

Note:
The Cancel Force button and menu option are displayed in English only.
SD_operation_failed event is customizable
You can now choose the level of alarm you want to display for failed operations. Specify FATAL, CRITICAL, MINOR, WARNING, HARMLESS, or UNKNOWN for the SD_operation_failed event in the tecad_sdnew.baroc file
Security improvements for the SPD file
On UNIX(R) platforms, when you export a software package to SPD format, you have read and write privileges to the package, while all other users have only read privileges. For this reason, the owner of the exported SPD file should be the same user who exports the software package.
Validation policy for Data Moving enabled
The sp_val_operation policy that validates the targets addressed by a change management operation, now also validates the targets addressed by a send or receive operation.
The Change Manager CLI command timeout is now customizable
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.
Mandatory date in End User Notification window
You can defer a distribution until a preset time, which is specified by the administrator and is out of the end user control. When this mandatory date has been reached, the distribution will be delivered immediately to the end user.
Displaying the .jar files version
With this feature you can display the version of installed .jar files, if available. You can start the command on Tivoli(R) servers and managed nodes after having set the Tivoli environment, as described below:
On UNIX operating systems:
. ./wjarversion.sh jarfile
On Windows(R) operating systems:
wjarversion.bat jarfile
where:
jarfile
Is the name of the .jar file for which you want to display the version. The following are the supported .jar files for this feature:
  • apm.jar
  • apm_utils.jar
  • swd_plugin.jar
  • tl_plugin.jar
Pocket PC device agent
With this feature you can easily reinstall the IBM(R) Agent application after a hard reset or when the battery dies, without having to install the application from scratch. To ensure a persistent one-click installation of the device agent, after a hard reset or when the battery dies, enable this feature.

Use the following procedure to enable the Pocket PC device agent feature when the IBM Agent application is already installed on the device:

  1. Copy on the source host in a temporary directory such as C:\temp the following three files from the directory CD2\PocketPC:
    • ceagent.arm.CAB
    • IBM_DeviceAgent.ini.sample
    • InstallAgent.lnk
  2. Rename the IBM_DeviceAgent.ini.sample file to IBM_DeviceAgent.ini
  3. Edit the IBM_DeviceAgent.ini file to uncomment and configure the keys
    mgmt.serveraddr=http://DMserver.domain.com/dmserver/WinceServlet 
    mgmt.delete_ini_after_processing=no
    mgmt.auth.user=user name
    where:
    DMserver.domain.com
    Is the hostname of the Tivoli Web Gateway Server workstation.
    mgmt.delete_ini_after_processing
    Prevents the IBM_DeviceAgent.ini file from being deleted after it is processed. It is set by default to no.
    user name
    Is the user ID.
  4. Edit the InstallAgent.lnk file and set the variable permanent_path to the permanent path on the device, such as IPAQ File Store.
  5. Copy the package Tivoli_PocketPC_ARM_Agent_Patch.v4.2.1.FP03.spd from the directory CD2\PocketPC to a temporary directory.
  6. Edit the package Tivoli_PocketPC_ARM_Agent_Patch.v4.2.1.FP03.spd by setting the value of the permanent_path and name variables. The permanent_path is the permanent path on the device, while the name is the path of the files (ceagent.arm.CAB, IBM_DeviceAgent.ini.sample, InstallAgent.lnk) on the source host, such as temp.
  7. Import the package.
  8. Distribute the package to the device. The package installs the files on a permanent path of the device.
    Note:
    During the Agent installation, you receive a message on the device asking if you want to install the IBM agent again. Click OK to confirm the installation.

In this way, after a hard reset or when the battery dies, you can reinstall the IBM Agent application by just clicking the InstallAgent.lnk file on the device.

Use the following procedure to enable the Pocket PC device agent feature when the IBM Agent application is installed on the device for the first time:

This package refreshes the files ceagent.arm.CAB and IBM_DeviceAgent.ini.sample on the Tivoli Web Gateway Server workstation.

To install and configure the device agent on WinCE with a persistent one-click installation, perform the following steps:

  1. Rename the IBM_DeviceAgent.ini.sample file to IBM_DeviceAgent.ini.
  2. Edit the IBM_DeviceAgent.ini file and set the mgmt.delete_ini_after_processing keyword to no.
  3. Copy the IBM_DeviceAgent.ini and the device agent installation package CAB file into the root of a persistent store path on the device, such as IPAQ File Store.
  4. Copy from the directory CD2\PocketPC the InstallAgent.lnk file to a temporary directory.
  5. Edit the InstallAgent.lnk file and set the variable permanent_path to the permanent path on the device.
  6. Copy from the directory CD2\PocketPC the InstallAgent.lnk file into the root of a persistent store path on the device.

In this way, after a hard reset or when the battery dies, you can reinstall the IBM Agent application by just clicking the InstallAgent.lnk file on the device.

Defer time management for end user notification panel
In the end user notification panel there are two fields to indicate the defer time. It is now possible to indicate the same time as a date and as a timestamp.
Avoiding concurrent logins during critical distributions
On Windows operating systems, you can use the concurrent login feature to prevent the end user from logging in to the workstation and performing a shutdown while a distribution is taking place. This feature guarantees that critical distributions are not interrupted. You can also define a maximum number of logins that can be performed during a distribution. In this case, the distribution is paused and restarts after the user logs off. For more information, see Implementing the concurrent login feature on page 43.

[ Top of Page | Previous Page | Next Page | Contents | ]