Last updated: November 27, 2007
This document contains information for Device Manager Version 2.0.0.1 Fix Pack 1.
This Readme includes the following information:
This Fix Pack includes corrections for the following problems:
The following JDBC error message during the device enrollment when auto-commit is turned on: com.tivoli.dms.common.DMCommonException: DYM2793E: An error occurred while attempting to commit SQL changes. See nested exception for details. : com.ibm.db2.jcc.a.SqlException: [ibm][db2][jcc][10114][10305] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode.
Out of Memory and Null Pointer Exception during job with thousands of devices.
Tablespace creation failure during the DMS configuration when trying to install TPM with remote database. Received error message: [sql] Failed to execute: CREATE USER TEMPORARY TABLESPACE TEMPTS_USER MANAGED BY SYSTEM USING('tc/tempspace_user') [logmsg] DYM8205E Create DB tablespaces failed with error /opt/ibm/tivoli/tpm/DeviceManager/config/actions/dms_db_config.xml:571: com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -298, SQLSTATE: 428B2, SQLERRMC: null
The same job runs for the second time if DMS server was rebooted while the endpoint was running the job.
WAS JVM heap size settings are being reset during the DMS configuration.
Two configuration properties were added to DMSconfig.properties file: instWASInitHeapSize and instWASMaxHeapSize.
Both properties are optional. If not set (blank) or missing the default values will be used (64 for instWASInitHeapSize and 256 for instWASMaxHeapSize).
Added the SO_TIMEOUT for the communication between central DMS server and federated servers.
Job results for some devices are missing in TPM UI view but the overall job status is "COMPLETED" - problem observed on federated DMS environment with thousands of clients.
The following installation related problems were also corrected: NOTE: When encountering any of these problems please download the new DMS installation image (build 20071107D or later)
HP-UX Itanium support added.
DMS installation failure on HP-UX because the DMS_hpuxia64defaults.rsp file is missing under defaults folder.
The uninstaller.bin file is missing under the "<DMS_HOME_DIR>/_uninst" directory
The "A suitable JVM could not be found" error during the DMS installation on HP-UX even when using the "-is:javahome <JAVA_HOME_DIR>" option.
Device Manager Fix Pack 1 requires the Product Update tool, which is included with the Device Manager Fix Pack.
The Product Update tool creates a backup of your configuration in case you need to remove the Fix Pack later. Before you install this Fix Pack, verify that you installed TPM 5.1
To install the Product Update tool, complete the following steps:
Windows:
C:\Program Files\IBM\Updatertool
AIX or Linux:
/usr/IBM/Updatertool
Solaris:
/opt/IBM/Updatertool
Fix Pack 1 requires that you install the Product Update tool.
The Fix Pack should be applied where the Device Manager product root was installed and configured. If Device Manager was installed to the Deployment Manager, then you install the Fix Pack at the Deployment Manager.
Before you install this Fix Pack, verify you have enough disk space:
/usr/IBM/DeviceManager /opt/IBM/DeviceManager C:\Program Files\IBM\DeviceManager
To install the Fix Pack, complete the following steps:
Windows:
C:\Program Files\IBM\Updatertool
AIX or Linux:
/usr/IBM/Updatertool
Solaris:
/opt/IBM/Updatertool
chmod +x update*.sh
Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.
Windows:
setupCmdLine.bat
AIX, Linux, or Solaris:
. ./setupCmdLine.sh
Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.
Navigate to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:
Windows:
preUpdate -user was_username -password was_password
AIX, Linux, or Solaris:
./preUpdate.sh -user was_username -password was_password
Windows:
C:\Program Files\IBM\Updatertool
AIX or Linux:
/usr/IBM/Updatertool
Solaris:
/opt/IBM/Updatertool
Note: The commands shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.
For example:
updateProduct -fixpack -installDir "dms_home" -fixpackDir "update_home" -install -fixpackID DMS_PTF_2001 -productID DMS -productVersion 2.0.0.0
Where dms_home represents the full path to the installation directory of Device Manager server.
Windows example:
updateProduct -fixpack -installDir "C:\Program Files\IBM\DeviceManager" -fixpackDir "C:\Program Files\IBM\Updatertool" -install -fixpackID DMS_PTF_2001 -productID DMS -productVersion 2.0.0.0
AIX or Linux example:
./updateProduct.sh -fixpack -installDir "/usr/IBM/DeviceManager" -fixpackDir "/usr/IBM/Updatertool" -install -fixpackID DMS_PTF_2001 -productID DMS -productVersion 2.0.0.0
Solaris example:
./updateProduct.sh -fixpack -installDir "/opt/IBM/DeviceManager" -fixpackDir "/opt/IBM/Updatertool" -install -fixpackID DMS_PTF_2001 -productID DMS -productVersion 2.0.0.0
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:
Windows:
postUpdate -user was_username -password was_password
AIX, Linux, or Solaris:
./postUpdate.sh -user was_username -password was_password
To remove Device Manager 2.0.0.1 Fix Pack 1, do the following steps:
Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.
Windows:
setupCmdLine.bat
AIX, Linux, or Solaris:
. ./setupCmdLine.sh
Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:
Windows:
preUpdate -user was_username -password was_password
AIX, Linux, or Solaris:
./preUpdate.sh -user was_username -password was_password
Windows:
C:\Program Files\IBM\Updatertool
AIX or Linux:
/usr/IBM/Updatertool
Solaris:
/opt/IBM/Updatertool
chmod +x update*.sh
Note: The command shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.
For example:
updateProduct -installDir "dms_home" -fixpack -uninstall -fixpackID DMS_PTF_2001 -fixpackDetails
Where dms_home represents the full path to the installation directory of Device Manager server.
Windows example:
updateProduct -installDir "C:\Program Files\IBM\DeviceManager" -fixpack -uninstall -fixpackID DMS_PTF_2001 -fixpackDetails
AIX or Linux example:
./updateProduct.sh -installDir "/usr/IBM/DeviceManager" -fixpack -uninstall -fixpackID DMS_PTF_2001 -fixpackDetails
Solaris example:
./updateProduct.sh -installDir "/opt/IBM/DeviceManager" -fixpack -uninstall -fixpackID DMS_PTF_2001 -fixpackDetails
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:
Windows:
postUpdate -user was_username -password was_password
AIX, Linux, or Solaris:
./postUpdate.sh -user was_username -password was_password
IBM, WebSphere are registered trademarks of the IBM Corporation in the United States, other countries, or both.
Microsoft, Active Directory, Exchange, Pocket PC, Internet Explorer, Windows, Windows 2003, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.
(c) Copyright International Business Machines Corporation 1994, 2005. All
rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.