[BESAdmin-Announcements] New Release: IBM Endpoint Manager for Software Use Analysis 2.2 patch 3 Now Available!

Wed Mar 26 11:11:41 PDT 2014

Software Use Analysis 2.2 patch 3

IBM is pleased to announce that patch 3 for IBM Endpoint Manager for 
Software Use Analysis 2.2 is available.
Site version updated:  47

This readme file provides information about patch 3 for Software Use 
Analysis version 2.2. Review this file thoroughly before you install or 
use the patch.

APARs fixed
The following table lists the APARs that are fixed in this patch. 
APAR
Symptoms
Behavior after applying the patch
Available since
IV51371
Documentation does not provide instructions for disabling SSL.
Documentation is updated to contain instructions for disabling SSL.
Patch 3
IV51377
During the import, the following message is written in the logs.
WARN: Datasource file itsitsearch_0_1011931.xml.bz2
raised an exception while reading from
http://<YOUR SERVER>:52311/UploadReplication?BaseDirectory
=1&Name=%5C31%5C1011931%5Citsitsearch_0_1011931.xml.bz2&sha1;=07
54BD3758952B765F8822102E92C888CB3F2E8&offset=0.
Error was received only 46 of 15068 bytes 
The problem occurs because a scan file is uploaded to the Endpoint Manager 
server during the ETL import. It causes the scan file signature to be 
different in the database and on the file system. After you install the 
patch, a scan file that is uploaded to the Endpoint Manager server during 
the ETL import is skipped. It is uploaded during the next import. Messages 
about skipped scan files are written in the log only when the log level is 
set to DEBUG.
Patch 3
IV51701
After you upgrade to Software Use Analysis 2.2, the post-installation 
phase fails with an unknown error.
Database name The user is not the owner of the specified database
The APAR is a duplicate of APAR IV50077 that was resolved in patch 1. 
Patch 3
IV52577
Upload of the catalog from Software Knowledge Base Toolkit to Software Use 
Analysis fails and the following message is displayed. 
Upload failed. The uploaded file is an older version 
than the current catalog
The problem occurs because the catalog that you uploaded during the 
initial import did not come from Software Knowledge Base Toolkit. If you 
want to use Software Knowledge Base Toolkit for catalog management, 
configure a catalog server before the initial import. Thus, you ensure 
that the catalog that is picked during the initial import comes from 
Software Knowledge Base Toolkit and there are no problems with catalog 
versions in the future. 
After you install the patch, information that is displayed on the initial 
import panel states that you should upload a catalog from Software 
Knowledge Base Toolkit if you want to use it for catalog management. 
Documentation is also updated to contain information that if you ran the 
initial import without configuring the catalog server, you can reinstall 
Software Use Analysis to solve the catalog versioning problem.
Patch 3
IV53737
The RPM scanner fails. 
The problem occurs because UNIX packages contain embedded HTML files that 
are incorrectly parsed during the scan. After you install the patch, the 
embedded HTML files are properly parsed and the scan succeeds. 
Patch 3
IV53838
Computers that are hard deleted from Endpoint Manager by using the 
Computer Remover or Audit Trail Cleaner are still displayed in Software 
Use Analysis. 
The problem occurs because the computer ID in Software Use Analysis is 
different from the computer ID in Endpoint Manager. After you install the 
patch, computer IDs are properly matched between the applications. 
Computers that are deleted from Endpoint Manager are not displayed in 
Software Use Analysis.
Patch 3
IV54936
During the installation of the Common Inventory Technology scanner on Red 
Hat Enterprise Linux 6.3, the installation status indicates a success. 
However, the scanner is not installed. 
The problem occurs because the fixlet for installing the Common Inventory 
Technology scanner incorrectly checks the scanner prerequisites. After you 
install the patch, prerequisites of the scanner are correctly checked and 
the installation is successful. 
Patch 3
IV55605
Catalog import fails and it is not possible to view reports. The problem 
occurs only when Software Use Analysis version 2.0 or 2.1 is upgraded to 
version 2.2. 
The problem occurs because some catalog entries are incorrectly handled 
during the import. After you install the patch, the problematic entries 
are handled properly.
Patch 3
IV55847
Software Use Analysis does not detect software that is supposed to be 
discovered by a filter signature. 
The problem occurs because two filter signatures are assigned to the same 
release of a software product. It causes signature matching to fail. After 
you install the patch, multiple filter signatures are handled correctly. 
Patch 3
IV56030
Documentation does not contain instructions for migrating computers from 
Software Use Analysis version 1.3 to version 2.2. 
Documentation is updated to contain information that versions 1.3 and 2.2 
can run side-by-side and that the value of the 
_BESClient_ArchiveManager_MaxArchiveSize parameter must be increased to 
properly upload scan results. 
Patch 3
IV56668
The software inventory tool scanner cannot be initiated on selected 
computers because the Initiate Scan fixlet fails. 
The problem occurs because the version of the software inventory tool 
scanner that is specified in the fixlet is incorrect. After you install 
the patch, the Initiate Scan fixlet checks for the correct version of the 
scanner and the scanner properly runs on the targeted computers. 
Patch 3

Internal defects fixed
The following table lists internal defects that are fixed in this patch.

Defect number
Symptoms
Behavior after applying the patch
Available since
103260
You upgrade to Software Use Analysis version 2.2 and run the initial 
import. After the session times out, you are logged out and an error 
message is displayed. After you log in again, no further problems occur. 
When the session times out, you are logged out but the error message is no 
longer displayed. 
Patch 3
102580
You run the fixlet for installing the software inventory tool scanner on a 
relevant computer. The installation finishes successfully. However, when 
you try to run the scanner, it produces a file that has no content. 
The problem occurs because the fixlet for installing the software 
inventory tool scanner becomes relevant although the scanner prerequisites 
are not fulfilled. After you install the patch, scanner prerequisites are 
properly checked and it is not possible to run the installation fixlet on 
a computer that does not fulfil the requirements. 
Patch 3
101190
Exposure to known security vulnerabilities. The details are not provided 
in this readme file because of security best practices.
The known security vulnerabilities are resolved.
Patch 3
100069
The initial import fails.
The problem occurs because some columns in the database tables have null 
values. After you install the patch, information about columns that have 
null values is written in the log but the initial import finishes 
successfully. 
Patch 3
100065
The fixlet for installing the Common Inventory Technology scanner is never 
relevant on the 64-bit version of SUSE Linux Enterprise Server. 
The problem occurs because the logic of the fixlet cannot be met on a 
64-bit version of SUSE Linux Enterprise Server. After you install the 
patch, the logic of the fixlet is corrected, and you can install the 
Common Inventory Technology scanner on the abovementioned operating 
system. 
Patch 3
100064
Actions that run for a long time, for example Common Inventory Technology 
scans, block the Endpoint Manager infrastructure. 
The problem occurs because the actions do not run in the background. After 
you install the patch, long-running actions are performed in the 
background and the Endpoint Manager infrastructure is not blocked. 
Patch 3
100047
Fixlets for uninstalling the Common Inventory Technology and software 
inventory tool scanners do not remove all scanner settings from the 
targeted computers. It might cause data upload to fail when the scanners 
are reinstalled. 
The uninstallation fixlets remove all scanner settings from the targeted 
computers. 
Patch 3
100046
Installation of the Common Inventory Technology scanner fails on Red Hat 
Enterprise Linux 6.3 and 6.4. 
Installation of the scanner succeeds on Red Hat Enterprise Linux 6.3 and 
6.4. 
Patch 3
100044
Actions that are initiated by some fixlets succeed although they should in 
fact fail. 
The status of an action is correct and reflects the actual results.
Patch 3
99421
The usage property that is required for gathering application usage 
statistics is enabled when the software inventory tool scanner is 
installed. However, it is not disabled after the scanner is uninstalled. 
The usage property is disabled after the software inventory tool scanner 
is uninstalled. 
Patch 3
98268
The analysis that gathers application usage statistics is run too 
frequently which causes that the Endpoint Manager server is too busy. 
The frequency of running the Application Usage Statistics analysis is set 
to one day. 
Patch 3

Enhancements
The following table lists enhancements that are provided in this patch.

ID
Abstract
Description
Available since 
101900
Support for IBM® Endpoint Manager 9.1
Software Use Analysis can run on IBM Endpoint Manager version 9.1. 
Additionally, starting from patch 3, Software Use Analysis is compliant 
with SP 800-131a cryptographic standards.
Patch 3

Installing the patch
To obtain the upgrade installer, log in to the Endpoint Manager console, 
and click Sites > External Sites > IBM Software Inventory > TEM SUA 
Upgrade (2.2 patch 3).
To obtain a fresh installer for Software Use Analysis that already 
contains the fixes that are introduced in the patch, log in to the 
Endpoint Manager console, and click Sites > External Sites > IBM Software 
Inventory > Dashboards > Software Use Analytics.
Software Use Analysis patches are cumulative. To see the list of APARs and 
internal defects that were fixed in patch 3, see the attached 
sua_2.2_patch_3.html readme file. 

IEM Software Use Analysis Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20140326/e73489f0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sua_2.2_patch_3_readme.zip
Type: application/zip
Size: 69914 bytes
Desc: not available
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20140326/e73489f0/attachment.zip>